[v3-2-test] Shift constraints-version-check staleness coloring by --c…#65252
Merged
Conversation
…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>
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.
…ooldown-days (#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)
Was generative AI tooling used to co-author this PR?
{pr_number}.significant.rst, in airflow-core/newsfragments. You can add this file in a follow-up commit after the PR is created so you know the PR number.