vatsrahul1001 opened a new pull request, #71173: URL: https://github.com/apache/airflow/pull/71173
Backport of #71171 to `v3-3-test`. Moves the CI image-cache refresh into a standalone `refresh-image-registry-cache.yml` that can't be cancelled by the next push (push and manual runs are grouped separately), forces all Python versions, removes the "Early" cache job from the regular build, and splits the manual constraints refresh into `refresh-constraints.yml`. This speeds up v3-3-test's cold `linux/amd64` builds. ### Reconciliation note This wasn't a clean cherry-pick. An earlier backport (#71167) had accidentally landed a *draft* of this work on `v3-3-test` under the old filename `refresh-image-cache.yml`, which main never had. This backport therefore: - **replaces** that stray draft — recorded as a rename `refresh-image-cache.yml` -> `refresh-image-registry-cache.yml`, so the branch ends with exactly one cache-refresh workflow (matching main); - aligns the branch-agnostic files (`additional-ci-image-checks.yml`, `update-constraints-on-push.yml`, `refresh-constraints.yml`, both `dev/*.md`, plus the referenced image) **byte-for-byte with main**; - keeps the legitimate branch-specific content in `ci-amd.yml` / `ci-arm.yml` (only the 7 shared inputs are removed, identically in both — `check-ci-workflows-in-sync` passes) and in `test_selective_checks.py` (which keeps v3-3-test's base plus the one cache test). `CI_AMD_PLATFORM` / `CI_ARM_PLATFORM` do not exist on `v3-3-test`, so the test import from main was intentionally not carried over. Verified locally: all pre-commit hooks pass (yamllint, zizmor, lychee, markdownlint, `check-ci-workflows-in-sync`), and the kept `test_all_python_versions_with_all_versions_label` test passes. ##### Was generative AI tooling used to co-author this PR? - [X] Yes — Claude Code (Opus 4.8) Generated-by: Claude Code (Opus 4.8) 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]
