uv: 0.7.14 -> 0.7.15

[Prince213]

Release notes: https://github.com/astral-sh/uv/releases/tag/0.7.15

Things done

• Built on platform(s)
  • x86_64-linux
  • aarch64-linux
  • x86_64-darwin
  • aarch64-darwin
• For non-Linux: Is sandboxing enabled in nix.conf? (See Nix manual)
  • sandbox = relaxed
  • sandbox = true
• Tested, as applicable:
  • NixOS test(s) (look inside nixos/tests)
  • and/or package tests
  • or, for functions and "core" functionality, tests in lib/tests or pkgs/test
  • made sure NixOS tests are linked to the relevant packages
• Tested compilation of all packages that depend on this change using nix-shell -p nixpkgs-review --run "nixpkgs-review rev HEAD". Note: all changes have to be committed, also see nixpkgs-review usage
• Tested basic functionality of all binary files (usually in ./result/bin/)
• Nixpkgs 25.11 Release Notes (or backporting 24.11 and 25.05 Nixpkgs Release notes)
  • (Package updates) Added a release notes entry if the change is major or breaking
• NixOS 25.11 Release Notes (or backporting 24.11 and 25.05 NixOS Release notes)
  • (Module updates) Added a release notes entry if the change is significant
  • (Module addition) Added a release notes entry if adding a new NixOS module
• Fits CONTRIBUTING.md, pkgs/README.md, maintainers/README.md and other contributing documentation in corresponding paths.

---

Add a 👍 reaction to pull requests you find important.

[GaetanLepage]

nixpkgs-review result

Generated using nixpkgs-review.

Command: nixpkgs-review pr 419921 --skip-package-regex home-assistant.*
Commit: f2729d852c04e595b3e7051f87f65403b695a8bf

---

x86_64-linux

✅ 50 packages built:

• hatch
• hatch.dist
• prefect
• prefect.dist
• private-gpt
• private-gpt.dist
• python312Packages.ffmpy
• python312Packages.ffmpy.dist
• python312Packages.gradio
• python312Packages.gradio-client
• python312Packages.gradio-client.dist
• python312Packages.gradio-pdf
• python312Packages.gradio-pdf.dist
• python312Packages.gradio.dist
• python312Packages.private-gpt
• python312Packages.private-gpt.dist
• python312Packages.smolagents
• python312Packages.smolagents.dist
• python312Packages.txtai
• python312Packages.txtai.dist
• python312Packages.uv
• python312Packages.uv-build
• python312Packages.uv-build.dist
• python312Packages.uv.dist
• python313Packages.ffmpy
• python313Packages.ffmpy.dist
• python313Packages.gradio
• python313Packages.gradio-client
• python313Packages.gradio-client.dist
• python313Packages.gradio-pdf
• python313Packages.gradio-pdf.dist
• python313Packages.gradio.dist
• python313Packages.homeassistant-stubs
• python313Packages.homeassistant-stubs.dist
• python313Packages.private-gpt
• python313Packages.private-gpt.dist
• python313Packages.smolagents
• python313Packages.smolagents.dist
• python313Packages.txtai
• python313Packages.txtai.dist
• python313Packages.uv
• python313Packages.uv-build
• python313Packages.uv-build.dist
• python313Packages.uv.dist
• rembg
• rembg.dist
• uv
• windmill
• zotify
• zotify.dist

[bengsparks]

@Prince213 I'm not at my laptop, so checking this is difficult, but this is the first time I've noticed that the backport label is on.

What version is uv in 25.05 at, and have there been any breaking changes to the CLI between these versions?

[bengsparks]

@Prince213 alright, checking commit messages on origin/release-25.05 states that uv: 0.7.3 -> 0.7.4 was the last commit made, and a cursory glance over the CHANGELOG for versions of uv since then 0.7.4 made nothing jump out, so this looks OK.
@GaetanLepage do you have an opinion on this? Should we backport the changes to the Python module as well, that switch out maturin for hatchling?

[GaetanLepage]

@Prince213 alright, checking commit messages on origin/release-25.05 states that uv: 0.7.3 -> 0.7.4 was the last commit made, and a cursory glance over the CHANGELOG for versions of uv since then 0.7.4 made nothing jump out, so this looks OK. @GaetanLepage do you have an opinion on this? Should we backport the changes to the Python module as well, that switch out maturin for hatchling?

I see no reason for not doing it. If you have some spare time, please go for it.
If we start backporting uv updates, I would indeed recommend also backporting the switch to hatchling.

[bengsparks]

Wait a second, doesn't this backport break the Python module? @GaetanLepage @Prince213

In release-25.05, python3Packages.uv inherits dontUseCmakeConfigure from pkgs.uv, which will break when you backport this PR, as this was removed only in #407665, which targetted uv 0.7.4.
Backporting would have to be done manually, with both python3Packages.uv and pkgs.uv being backported in the same PR, or python3Packages.uv first.

[bengsparks]

PR looks fine, backport requires more discussion at this moment.

[nixpkgs-ci]

Backport failed for release-25.05, because it was unable to cherry-pick the commit(s).

Please cherry-pick the changes locally and resolve any conflicts.

git fetch origin release-25.05
git worktree add -d .worktree/backport-419921-to-release-25.05 origin/release-25.05
cd .worktree/backport-419921-to-release-25.05
git switch --create backport-419921-to-release-25.05
git cherry-pick -x f2729d852c04e595b3e7051f87f65403b695a8bf

[Prince213]

Hi @bengsparks and @GaetanLepage thanks for the merge.

Until recently I've been paying little efforts into backporting PRs as I'm a {nixos,nixpkgs}-unstable user, even for those that are acceptable for releases and I'm trying to change that.

A quick search for the word `break' didn't find any results so it should be okay to backport the changes.

I see that #420015 has been merged already. What else needs to be done?

[GaetanLepage]

Hi @bengsparks and @GaetanLepage thanks for the merge.

Until recently I've been paying little efforts into backporting PRs as I'm a {nixos,nixpkgs}-unstable user, even for those that are acceptable for releases and I'm trying to change that.

A quick search for the word `break' didn't find any results so it should be okay to backport the changes.

I see that #420015 has been merged already. What else needs to be done?

Now we should be able to backport the updates indeed.

[Prince213]

Okay I'll handle the backports.