epel-announce March 2025

epel-announce@lists.fedoraproject.org

1 participants
1 discussions

EPEL-ANNOUNCEUpdating uv from 0.5.31 to 0.6.3 in EPEL10, with some breaking changes
by Ben Beasley 10 Mar '25

10 Mar '25

I have just issued updates for the Python package and project manager uv, from version 0.5.31 to version 0.6.3, in both EPEL10 branches (10.0 and 10.1)[1][2]. This package follows semantic versioning[3], and there are a few breaking changes from 0.5.x to 0.6.x. This update therefore follows the policy for incompatible upgrades[4] and has obtained the approval of the EPEL steering committee[5]. The developers of uv have been very strict about defining and tracking potential breaking changes, and it is likely that most users will not need to change anything at all. Upstream writes: There have been 31 releases and 1135 pull requests since 0.5.0, our last release with breaking changes. As before, 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 upstream changelogs for the 0.6.0 release contain a complete, detailed list of breaking changes and their possible implications for uv users[6]. By policy, these updates will remain in testing for at least one week regardless of karma, and I will send a follow-up announcement when I manually push them to stable. [1] https://bodhi.fedoraproject.org/updates/FEDORA-EPEL-2025-978102e56a [2] https://bodhi.fedoraproject.org/updates/FEDORA-EPEL-2025-67e00f28cd [3] https://semver.org/ [4] https://docs.fedoraproject.org/en-US/epel/epel-policy-incompatible-upgrades/ [5] https://pagure.io/epel/issue/317 [6] https://github.com/astral-sh/uv/blob/0.6.3/CHANGELOG.md#breaking-changes

1 1

2025

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

epel-announce March 2025