potiuk opened a new pull request, #66664: URL: https://github.com/apache/airflow/pull/66664
## Summary Backport of #66348 (merged 2026-05-07, commit [\`8f93637\`](https://github.com/apache/airflow/commit/8f9363715516dd5b8c5c1bafe007a84fa5122390)) to \`v3-2-test\`. Splits the combined \`ci-amd-arm.yml\` workflow into two thin wrappers (\`ci-arm.yml\` for the canary cron + \`ci-amd.yml\` for per-PR pushes) calling a reusable \`_ci-pipeline.yml\`. Adds the \`check-ci-workflows-in-sync\` prek hook to keep the two wrappers in lockstep. See the source PR for full motivation. ## Conflicts resolved during cherry-pick Three conflicts plus one post-resolve drift fix: 1. **\`README.md\`** — both branches updated the badge table; took the cherry-pick's side because v3-2-test's HEAD still pointed at \`v3-1-test\`-branch badges (stale from when the branch was cut). 2. **\`generated/PYPI_README.md\`** — same pattern as \`README.md\`, same resolution. 3. **\`dev/update_github_branch_config.py\`** — modify/delete: file was deliberately removed on \`v3-2-test\`, kept it deleted (the backport doesn't need it). 4. **\`ci-arm.yml\` aligned to v3-2-test's \`ci-amd.yml\`** — the new \`check-ci-workflows-in-sync\` hook flagged two divergences after the rename: - Removed \`run-remote-logging-opensearch-e2e-tests\` outputs (2 places) — \`v3-2-test\` already removed those tests. - Bumped \`slackapi/slack-github-action\` from \`v3.0.1\` → \`v3.0.3\` (3 places) — \`v3-2-test\` already had the newer pin. ## Test plan - [x] Cherry-pick clean; pre-commit (incl. the new \`check-ci-workflows-in-sync\` hook) passes locally - [x] mypy-dev hook fails locally only — pre-existing (\`dev/airflow_mypy/\` plugin reference exists in \`dev/pyproject.toml\` on both \`main\` and \`v3-2-test\` but the directory isn't checked in; CI installs it via \`uv sync\`) - [ ] Wait for CI on \`v3-2-test\` 🤖 Generated with [Claude Code](https://claude.com/claude-code) (Opus 4.7, 1M context) -- 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]
