Skip to content

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

Closed
codeql-ci-app[bot] wants to merge 2 commits into
mainfrom
runner-images/add-windows-2022-d16694cbb6a8de4a
Closed

codeql-ci-app[bot] wants to merge 2 commits into
mainfrom
runner-images/add-windows-2022-d16694cbb6a8de4a

Conversation

@codeql-ci-app

@codeql-ci-app codeql-ci-app Bot commented Nov 11, 2026

Copy link
Copy Markdown

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 (actions/runner-images#14254), and their first brownout (23 March 2027) is more than four weeks away. macOS 14 is retired (actions/runner-images#15226, actions/runner-images#13518), and the check doesn't use it.

Required checks: This PR adds a check to the runner-images matrix. 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 --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 merges.

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

@github-actions github-actions Bot added the size/S Should be easy to review label Nov 11, 2026
@henrymercer henrymercer changed the title Runner images: Run the runner-images check on windows-2022 Test of the runner images agentic workflow (please ignore) Nov 11, 2026
@henrymercer

Copy link
Copy Markdown
Contributor

Closing: this was a test of an agentic workflow, which targeted main by mistake.

@henrymercer
henrymercer deleted the runner-images/add-windows-2022-d16694cbb6a8de4a branch November 11, 2026 17:14
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

size/S Should be easy to review

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant