Skip to content

Canonicalize compatible-release specifier ties - #1428

Draft
zaniebot wants to merge 1 commit into
mainfrom
zb/canonicalize-compatible-release-specifier-ties
Draft

zaniebot wants to merge 1 commit into
mainfrom
zb/canonicalize-compatible-release-specifier-ties

Conversation

@zaniebot

Copy link
Copy Markdown
Collaborator

VersionSpecifiers can compare equivalent lists differently when ~= constraints have equal versions but different release lengths. The sorter breaks version ties only by operator, omitting the distinction added in astral-sh#18960. Use VersionSpecifier::Ord for the tie-break so list equality stays consistent, while preserving version-first ordering and stable ties for semantically equal specifiers.

@zaniebot zaniebot added risk:1 Negligible risk of localized mistakes that are obvious and easy to correct. priority:2 Important: bounded correctness, release reliability, committed work, or proven performance gains. size:1 Small: one localized behavior with straightforward tests or documentation checks. labels Sep 11, 2026
@zaniebot zaniebot added the project:maintainer-followups Maintainer follow-up work label Oct 9, 2026

This branch has not been deployed

No deployments
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

priority:2 Important: bounded correctness, release reliability, committed work, or proven performance gains. project:maintainer-followups Maintainer follow-up work risk:1 Negligible risk of localized mistakes that are obvious and easy to correct. size:1 Small: one localized behavior with straightforward tests or documentation checks.

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants