The GitHub Actions job "Tests (AMD)" on 
airflow.git/feat/ci-arm-push-stable-providers has succeeded.
Run started by GitHub user potiuk (triggered by potiuk).

Head commit for run:
c370e80e96510d3628c4ef53b31084704110d949 / Jarek Potiuk <[email protected]>
ci: also build ARM on pushes to release-prep / providers branches

Until now, post-merge pushes to v[0-9]+-[0-9]+-test and
providers-*/v* branches only triggered the AMD wrapper
(`ci-amd.yml`); ARM coverage on those branches was limited to the
cron-driven canary. Add the same `push:` block to `ci-arm.yml`
so both architectures build whenever a release-prep / providers
branch advances.

`main` is intentionally NOT in the ARM push list — main pushes
stay AMD-only via `ci-amd.yml` and ARM main coverage continues
to come from the canary cron. This avoids doubling the ARM
runner load on the high-traffic main branch while still surfacing
ARM regressions on every release-prep / providers commit.

Knock-on changes:
- ci-amd.yml: reorder `pull_request:` to come before `push:` so
  the AMD-only schedule + pull_request remains a contiguous block
  for the strip mechanism in `check-ci-workflows-in-sync`. Same
  comment text added to its `push:` block as ci-arm.yml's so
  the two read identically.
- check_ci_workflows_in_sync.py: drop the `push:` block from
  `AMD_ONLY_BLOCK` (push is now shared between both wrappers and
  therefore must not be stripped from either side). Update item 3
  in the docstring to reflect the new trigger split.
- README.md and generated/PYPI_README.md: add the ARM badge to
  the 3.x row alongside AMD (Main row already had both).

Generated-by: Claude Code (Opus 4.7)

Report URL: https://github.com/apache/airflow/actions/runs/25636813833

With regards,
GitHub Actions via GitBox


---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]

Reply via email to