Add cooldown period to upgrade-important-versions check#63606
Merged
potiuk merged 1 commit intoapache:mainfrom Mar 14, 2026
Merged
Add cooldown period to upgrade-important-versions check#63606potiuk merged 1 commit intoapache:mainfrom
potiuk merged 1 commit intoapache:mainfrom
Conversation
When UPGRADE_COOLDOWN_DAYS is set, the upgrade check will not fail if there was a recent "Upgrade important" commit within the cooldown period. This prevents noisy CI failures when versions were recently addressed. The CI workflow sets a 4-day cooldown matching the existing prek autoupdate cooldown. Co-Authored-By: Claude Opus 4.6 (1M context) <noreply@anthropic.com>
jscheffl
approved these changes
Mar 14, 2026
Backport failed to create: v3-1-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 e49d6c0 v3-1-testThis should apply the commit to the v3-1-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
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.
Add
UPGRADE_COOLDOWN_DAYSenv var toupgrade_important_versions.pysothe CI upgrade check only fails when no "Upgrade important" commit has
been merged within the configured number of days. The CI workflow sets
a 4-day cooldown, matching the existing
prek autoupdate --cooldown-days 4.This reduces noisy CI failures right after an upgrade PR is merged while
a new version is released for one of the tracked packages.
Was generative AI tooling used to co-author this PR?
Generated-by: Claude Code (Claude Opus 4.6) following the guidelines