Test of the runner images agentic workflow (please ignore) - #4319

Maintainers: Please review these changes before approving this PR's workflow runs.

This PR keeps the runner-images PR check in sync with the runner images README.

Changes:

• Added windows-2022 to the runner-images check. The README's Available Images table lists "Windows Server 2022 | x64 | windows-2022". The check didn't run on it or exclude it, and none of the open Announcement issues in actions/runner-images deprecate or retire it. I regenerated .github/workflows/__runner-images.yml with npx tsx sync.ts.

I found no other changes to make:

• The Ubuntu 22.04 images already have a retirement comment that links to [Ubuntu] The Ubuntu 22 based runner images will begin deprecation on September 17th and will be fully unsupported by April 17th for GitHub Actions and Azure DevOps actions/runner-images#14254. Their first brownout (23 March 2027) is more than four weeks away.
• macOS 14 has been retired ([macOS] macOS 14 Sonoma retirement: GitHub Actions and ADO arm64 on November 2; ADO Intel on November 23 actions/runner-images#13518, [macOS] Azure DevOps macOS 14 Intel runners extended through November 23, 2026 actions/runner-images#15226), and the check doesn't use it.
• Test of the runner images agentic workflow (please ignore) #4315 proposed the same change. It was closed only because it targeted main by mistake.

Required checks: This PR adds a check to the runner-images matrix. Before this PR is merged, 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 --apply.

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 - CI failures.

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

• Special considerations - The required checks need to be updated with pr-checks/sync-checks.ts (see above) before this PR is merged.

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 · ~50 AIC · ⌖ ~37 AIC · ⊞ 4.8K · ◷