In approximately one week, I plan to update the ruff package to version
0.15.x in stable branches F43 and F42. This means that Ruff will now
format Python code according to the 2026 edition of its style guide,
including newly stabilized lint rules and behaviors. Please see the
release notes[1] and blog post[2] for more details on
potentially-breaking changes. I impact-checked dependent packages in
each branch to make sure that none of these changes will cause FTBFS or
FTI issues. This update is permitted under an existing permanent
exception to the Updates Policy in Fedora[3][4]. Ruff 0.15.0 is already
in Rawhide and will be branched into F44 today.
At around the same time, I will update ruff to 0.15.x in the EPEL10
leading branch (currently EPEL10.2), as allowed by a corresponding
exception for EPEL[5], limited to leading branches and to versions
through 1.0. No further approvals are needed for this update, but I do
plan to follow the usual announcement and testing procedure for
incompatible upgrades in EPEL[6].
[1] https://github.com/astral-sh/ruff/releases/tag/0.15.0
[2] https://astral.sh/blog/ruff-v0.15.0
[3]
https://docs.fedoraproject.org/en-US/fesco/Updates_Policy/#_other_packages
[4] https://pagure.io/fesco/issue/3197
[5] https://pagure.io/epel/issue/350
[6]
https://docs.fedoraproject.org/en-US/epel/epel-policy-incompatible-upgrades/#process_for_incompatible_upgrades
--
_______________________________________________
devel mailing list -- [email protected]
To unsubscribe send an email to [email protected]
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/[email protected]
Do not reply to spam, report it:
https://forge.fedoraproject.org/infra/tickets/issues/new
