github-actions[bot] opened a new pull request, #73385: URL: https://github.com/apache/airflow/pull/73385
After every provider release wave the `Deps *:constraints` jobs doubled for three or four days and then recovered on their own. The constraints are resolved under uv's `exclude-newer` cooldown with the per-package overrides in the root pyproject.toml, where Airflow's own distributions are exempt, so a fresh provider wave lands in the constraints the same day. The check had its own 4-day cooldown applied to every package, so for those days the pin was newer than "latest" and a plain equality check counted it as outdated. With `--explain-why` every such package then cost a full `uv sync` that tried to pin it to the *older* version and reported that the pin did not take effect. On 2026-09-15 that was 37 providers and about 12 extra minutes per job, with nothing to act on. The check now reads `[tool.uv.exclude-newer-package]` and applies the same rules: no cooldown for exempt distributions, a moved cutoff where one is configured. A pin that is still ahead of "latest" counts as up to date, so no explanation runs for it either. (cherry picked from commit 7da73c89cb0133164f65d6189df97e23dc9292dd) Co-authored-by: Jarek Potiuk <[email protected]> Generated-by: Claude Opus 5 -- 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]
