[github-actions]

Important

A maintainer should review these changes before approving this pull request's workflow runs.

This PR was opened automatically by the Update runner images workflow.

Changes

• Added ubuntu-24.04-arm to the runner-images PR check (pr-checks/checks/runner-images.yml) and regenerated .github/workflows/__runner-images.yml.
  • Based on: the Available Images README entry "Ubuntu 24.04 Arm64 | arm64 | ubuntu-24.04-arm". It isn't marked as preview or deprecated, and no announcement deprecates or retires it. The check didn't run on it and didn't exclude it.

No other changes were needed. The other images in the README are either already in the check or excluded for the reasons given in its header comment. The existing Ubuntu 22.04 deprecation comment (actions/runner-images#14254, with brownouts from 23 March 2027) is still accurate, and the first brownout is more than four weeks away.

Note

This PR adds a check (the ubuntu-24.04-arm job of the runner-images check). Before merging, a maintainer needs to update the required checks by running pr-checks/sync-checks.ts with --ref set to this PR's head commit, first without --apply and then with it.

Risk assessment

For internal use only. Please select the risk level of this change:

• Low risk: Changes are fully under feature flags, or have been fully tested and validated in pre-production environments and are highly observable, or are documentation or test only.

Which use cases does this change impact?

Environments:

• Testing/None - This change does not impact any CodeQL workflows in production.

How did/will you validate this change?

• End-to-end tests - I am depending on PR checks (i.e. tests in pr-checks).

If something goes wrong after this change is released, what are the mitigation and rollback strategies?

• Development/testing only - This change cannot cause any failures in production.

How will you know if something goes wrong after this change is released?

• Other - This change only affects PR checks. Failures would show up in this repository's CI.

Are there any special considerations for merging or releasing this change?

• Special considerations - A maintainer needs to update the required checks before merging (see above).

Merge / deployment checklist

• Confirm this change is backwards compatible with existing workflows.
• Consider adding a changelog entry for this change.
• Confirm the readme and docs have been updated if necessary.

Generated by Update runner images · copilot · opus · ~42 AIC · ⌖ ~37 AIC · ⊞ 4.8K · ◷