Skip yanked newer versions in constraints-version-check#65236
Merged
eladkal merged 1 commit intoapache:mainfrom Apr 14, 2026
Merged
Skip yanked newer versions in constraints-version-check#65236eladkal merged 1 commit intoapache:mainfrom
eladkal merged 1 commit intoapache:mainfrom
Conversation
…rent When a newer release has been yanked from PyPI it must not be proposed as an upgrade candidate. The check now treats a release as "does not exist" when all of its files are yanked, so yanked versions are ignored when picking the latest version (with or without cooldown), counting versions behind, and determining whether a package has any newer release since the constraints file was generated.
potiuk
requested review from
amoghrajesh,
ashb,
bugraoz93,
choo121600,
ephraimbuddy,
gopidesupavan,
jason810496,
jedcunningham,
jscheffl and
vatsrahul1001
as code owners
boring-cyborg
bot
added
area:dev-tools
backport-to-v3-2-test
eladkal
approved these changes
Apr 14, 2026
bugraoz93
approved these changes
Apr 14, 2026
Contributor
Backport failed to create: v3-2-test. View the failure log Run detailsNote: As of Merging PRs targeted for Airflow 3.X In matter of doubt please ask in #release-management Slack channel.
You can attempt to backport this manually by running: cherry_picker d1d313a v3-2-testThis should apply the commit to the v3-2-test branch and leave the commit in conflict state marking After you have resolved the conflicts, you can continue the backport process by running: cherry_picker --continueIf you don't have cherry-picker installed, see the installation guide. |
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
3 participants
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
A yanked release must never be proposed as an upgrade candidate by
breeze release-management constraints-version-check. This change treats a release as "does not exist" when PyPI reports that all of its files are yanked, so yanked versions are ignored when:diff-constraintsmode).The pinned version itself is never filtered — only versions being evaluated as "newer than current".
Was generative AI tooling used to co-author this PR?
Generated-by: Claude Code (Opus 4.6) following the guidelines