This issue requests that the EPEL steering committer consider whether to grant ruff the same Updates Policy exception as uv in EPEL.

The two packages are very similar in several ways. Both already have permanent Updates Policy exceptions in Fedora, with the justification that they are primarily used by human developers rather than for building other packages and systems, and that holding the packages at older versions would cause much more harm to users – by allowing them to fall behind the Python packaging ecosystem, and by denying access to their rapidly-expanding features – than would be caused by exposing users to occasional minor breaking changes. Both are by the same developers, and both have a history of careful upstream design and relatively minor breaking changes across SemVer boundaries.

In https://pagure.io/epel/issue/317, the steering committee chose to grant uv a semi-permanent exception for incompatible updates in leading EPEL branches, with the the condition that the exception must be revisited when the package reaches version 1.0. This issue requests that ruff be treated the same way.

If the requested exception is granted, I expect to use it to update ruff to 0.12.x or ideally 0.13.x in the EPEL10 leading branch within the next few weeks.