Skip to content

Add cooldown period to upgrade-important-versions check#63606

Merged
potiuk merged 1 commit intoapache:mainfrom
potiuk:worktree-parsed-strolling-mango
Mar 14, 2026
Merged

Add cooldown period to upgrade-important-versions check#63606
potiuk merged 1 commit intoapache:mainfrom
potiuk:worktree-parsed-strolling-mango

Conversation

@potiuk
Copy link
Member

@potiuk potiuk commented Mar 14, 2026

Add UPGRADE_COOLDOWN_DAYS env var to upgrade_important_versions.py so
the 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?
  • Yes — Claude Code (Claude Opus 4.6)

Generated-by: Claude Code (Claude Opus 4.6) following the guidelines

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>
@boring-cyborg boring-cyborg bot added area:dev-tools backport-to-v3-1-test Mark PR with this label to backport to v3-1-test branch labels Mar 14, 2026
@potiuk potiuk merged commit e49d6c0 into apache:main Mar 14, 2026
107 of 108 checks passed
@potiuk potiuk deleted the worktree-parsed-strolling-mango branch March 14, 2026 17:19
@github-actions
Copy link

Backport failed to create: v3-1-test. View the failure log Run details

Note: As of Merging PRs targeted for Airflow 3.X
the committer who merges the PR is responsible for backporting the PRs that are bug fixes (generally speaking) to the maintenance branches.

In matter of doubt please ask in #release-management Slack channel.

Status Branch Result
v3-1-test Commit Link

You can attempt to backport this manually by running:

cherry_picker e49d6c0 v3-1-test

This should apply the commit to the v3-1-test branch and leave the commit in conflict state marking
the files that need manual conflict resolution.

After you have resolved the conflicts, you can continue the backport process by running:

cherry_picker --continue

If you don't have cherry-picker installed, see the installation guide.

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

Labels

area:dev-tools backport-to-v3-1-test Mark PR with this label to backport to v3-1-test branch

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants