uv: 0.5.6 -> 0.5.7

[MisileLab]

https://github.com/astral-sh/uv/releases/tag/0.5.7

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/)
• 25.05 Release Notes (or backporting 24.11 and 25.05 Release notes)
  • (Package updates) Added a release notes entry if the change is major or breaking
  • (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.

---

Add a 👍 reaction to pull requests you find important.

[MisileLab]

https://gist.github.com/GrahamcOfBorg/22243fd0f313dfe40aba0f44afeb56bd
this error derived from #362375 (comment), not uv's fault

[GaetanLepage]

I was able to build uv and uv.tests on all platforms. Thanks :)

[dotlambda]

No need to target staging(-next) with such a low rebuild count.

[GaetanLepage]

No need to target staging(-next) with such a low rebuild count.

Yes, in general, you are right. However, in this case:

• Previous updates to uv had been made to staging[-next], so this one couldn't be done on master directly
• The reason for it is legit: changing uv affects home-assistant and its >1k test packages. I started moving uv update PRs to staging after recommendations by the staging team itself.

[dotlambda]

• The reason for it is legit: changing uv affects home-assistant and its >1k test packages. I started moving uv update PRs to staging after recommendations by the staging team itself.

Home Assistant tests are very lightweight. They won't overload Hydra.

[GaetanLepage]

Home Assistant tests are very lightweight. They won't overload Hydra.

Ok good to know. staging people recommended targetting staging at the time. Testing was painful because I was using the US-based ARM builder and it took several hourse because of the transfer times.

[adisbladis]

The large rebuild count is because of #155060.

[MisileLab]

• The reason for it is legit: changing uv affects home-assistant and its >1k test packages. I started moving uv update PRs to staging after recommendations by the staging team itself.

Home Assistant tests are very lightweight. They won't overload Hydra.

I (recommended) target staging(#354450), because large rebuild but also restricted breaking release because of 24.11 release.