In one week, 2025-07-29, or slightly later, I plan to update the uv package from 0.7.22 to 0.8.0 or a later 0.8.x release[1] in Fedora Rawhide, 42, and 41. I also plan to ship the same update to the EPEL10 leading branch, currently EPEL 10.1.

In upstream’s words, “Since we released uv 0.7.0 in April, we've accumulated various changes that improve correctness and user experience, but could break some workflows. This release contains those changes; many have been marked as breaking out of an abundance of caution. We expect most users to be able to upgrade without making changes.” The exact changes are documented in the release notes for 0.8.0[2].

For stable releases Fedora 42 and 41, this update is permitted under a permanent exception to the Updates Policy[3]; for the EPEL10 leading branch, it is permitted under a semi-permanent exception for versions up to 1.0[4]. For EPEL “stable” branches (epel10.0), current policy does not allow SemVer-breaking updates of uv or of the library-only Rust packages upon which it depends, so uv 0.6.17 will continue to be the final uv release in EPEL10.0 for the foreseeable future.

Four packages in Fedora now depend on uv: fawltydeps, hatch, python-build, and python-tox-uv. A quick impact check using local mock builds did not reveal any incompatibilities.

I will also update python-uv-build[5], the new uv-based build backend, to the same version as uv. This package is still Rawhide-only for now. As long as nothing yet depends on it, I prefer to allow a little time for the ecosystem to work out any kinks before locking us into a particular minor release in stable branches.

– Ben Beasley (FAS: music)

[1] https://src.fedoraproject.org/rpms/uv/pull-request/67

[2] https://github.com/astral-sh/uv/releases/tag/0.8.0

[3] https://pagure.io/fesco/issue/3262

[4] https://pagure.io/epel/issue/317#comment-958123

[5] https://src.fedoraproject.org/rpms/python-uv-build/pull-request/6
-- 
_______________________________________________
devel mailing list -- devel@lists.fedoraproject.org
To unsubscribe send an email to devel-le...@lists.fedoraproject.org
Fedora Code of Conduct: 
https://docs.fedoraproject.org/en-US/project/code-of-conduct/
List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines
List Archives: 
https://lists.fedoraproject.org/archives/list/devel@lists.fedoraproject.org
Do not reply to spam, report it: 
https://pagure.io/fedora-infrastructure/new_issue

Reply via email to