potiuk opened a new pull request, #71137: URL: https://github.com/apache/airflow/pull/71137
The early cache push was gated to `schedule` and `workflow_dispatch`, so it never ran for a merge into a release branch. Those branches are built by `push` only, and their other refresh path — the Regular cache push in `finalize-tests.yml` — sits behind the whole test matrix. A branch whose CI is failing therefore never refreshes its image cache at all, and the staler the cache gets the slower every build on it becomes, which makes it harder to get green again. `v3-3-test` has been in exactly that state: its last successful canary push run was 2026-07-28, so its registry cache is eight days old, and every build against it — including release-constraints runs — pays for it. `main` is unaffected either way. It is not built on push, so it keeps refreshing through the scheduled canary. Pull requests stay excluded. `canary-run` is also true for a PR carrying the `canary` label, and pushing cache from an unmerged branch is not something a label should authorise — so the condition matches the one the Regular cache push already uses. ##### Was generative AI tooling used to co-author this PR? - [X] Yes — Claude Opus 5 (1M context) Generated-by: Claude Opus 5 (1M context) 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]
