Shift constraints-version-check coloring by --cooldown-days#65233
Merged
potiuk merged 1 commit intoApr 14, 2026
Conversation
Package time spent inside the cooldown window no longer counts against staleness, so a release that just cleared the cooldown is still reported as "new" instead of flipping to "warning" immediately. The shifted thresholds are reflected in the row status labels and footer summary.
potiuk
requested review from
amoghrajesh,
ashb,
bugraoz93,
choo121600,
ephraimbuddy,
gopidesupavan,
jason810496,
jedcunningham,
jscheffl and
vatsrahul1001
as code owners
eladkal
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 0e0aaed 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. |
potiuk
added a commit
to potiuk/airflow
that referenced
this pull request
Apr 14, 2026
…ooldown-days (apache#65233) Package time spent inside the cooldown window no longer counts against staleness, so a release that just cleared the cooldown is still reported as "new" instead of flipping to "warning" immediately. The shifted thresholds are reflected in the row status labels and footer summary. (cherry picked from commit 0e0aaed) Co-authored-by: Jarek Potiuk <jarek@potiuk.com>
1 task
potiuk
added a commit
that referenced
this pull request
Apr 14, 2026
…ooldown-days (#65233) (#65252) Package time spent inside the cooldown window no longer counts against staleness, so a release that just cleared the cooldown is still reported as "new" instead of flipping to "warning" immediately. The shifted thresholds are reflected in the row status labels and footer summary. (cherry picked from commit 0e0aaed)
vatsrahul1001
pushed a commit
that referenced
this pull request
Apr 15, 2026
…ooldown-days (#65233) (#65252) Package time spent inside the cooldown window no longer counts against staleness, so a release that just cleared the cooldown is still reported as "new" instead of flipping to "warning" immediately. The shifted thresholds are reflected in the row status labels and footer summary. (cherry picked from commit 0e0aaed)
vatsrahul1001
pushed a commit
that referenced
this pull request
Apr 15, 2026
…ooldown-days (#65233) (#65252) Package time spent inside the cooldown window no longer counts against staleness, so a release that just cleared the cooldown is still reported as "new" instead of flipping to "warning" immediately. The shifted thresholds are reflected in the row status labels and footer summary. (cherry picked from commit 0e0aaed)
vatsrahul1001
pushed a commit
that referenced
this pull request
Apr 15, 2026
…ooldown-days (#65233) (#65252) Package time spent inside the cooldown window no longer counts against staleness, so a release that just cleared the cooldown is still reported as "new" instead of flipping to "warning" immediately. The shifted thresholds are reflected in the row status labels and footer summary. (cherry picked from commit 0e0aaed)
vatsrahul1001
pushed a commit
that referenced
this pull request
Apr 15, 2026
…ooldown-days (#65233) (#65252) Package time spent inside the cooldown window no longer counts against staleness, so a release that just cleared the cooldown is still reported as "new" instead of flipping to "warning" immediately. The shifted thresholds are reflected in the row status labels and footer summary. (cherry picked from commit 0e0aaed)
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
2 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.
Shifts the staleness thresholds used by
breeze release-management constraints-version-checkby--cooldown-days, so that time a package spent in the cooldown window (during which it is intentionally ignored by the check) no longer counts against its staleness.Previously, a release that had just cleared the cooldown could flip straight from "not considered" to "🔶 warning" on the next run, because the 5d/30d thresholds were absolute. With this change the thresholds become
5 + cooldown_daysand30 + cooldown_days, so a package that just became eligible is still reported as "📢 new". The row status labels and the footer summary reflect the shifted thresholds as well.No behavior change when
--cooldown-days=0.Was generative AI tooling used to co-author this PR?
Generated-by: Claude Code (Opus 4.6) following the guidelines