potiuk opened a new pull request, #65233: URL: https://github.com/apache/airflow/pull/65233
Shifts the staleness thresholds used by `breeze release-management constraints-version-check` by `--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_days` and `30 + 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? - [X] Yes — Claude Code (Opus 4.6) Generated-by: Claude Code (Opus 4.6) following [the guidelines](https://github.com/apache/airflow/blob/main/contributing-docs/05_pull_requests.rst#gen-ai-assisted-contributions) -- This is an automated message from the Apache Git Service. To respond to the message, please log on to GitHub and use the URL above to go to the specific comment. To unsubscribe, e-mail: [email protected] For queries about this service, please contact Infrastructure at: [email protected]
