release/21.x: [CI][Github] Switch windows to server 2022 (#148743)

[llvmbot]

Backport 3248a6d

Requested by: @boomanaiden154

[llvmbot]

@cmtice What do you think about merging this PR to the release branch?

[llvmbot]

@llvm/pr-subscribers-github-workflow

Author: None (llvmbot)

Changes

Backport 3248a6d

Requested by: @boomanaiden154

---

Full diff: https://github.com/llvm/llvm-project/pull/149128.diff

1 Files Affected:

• (modified) .github/workflows/premerge.yaml (+1-1)

diff --git a/.github/workflows/premerge.yaml b/.github/workflows/premerge.yaml
index f7a48304b82b0..ff63355222065 100644
--- a/.github/workflows/premerge.yaml
+++ b/.github/workflows/premerge.yaml
@@ -76,7 +76,7 @@ jobs:
     if: >-
         github.repository_owner == 'llvm' &&
         (github.event_name != 'pull_request' || github.event.action != 'closed')
-    runs-on: llvm-premerge-windows-runners
+    runs-on: llvm-premerge-windows-2022-runners
     defaults:
       run:
         shell: bash

[boomanaiden154]

@tru The plan is to use the new premerge CI to test changes to the release branch, right?

We're planning on backporting any changes that we're making in main to make sure the release branch CI still works, assuming that is actually the plan.

[cmtice]

@cmtice What do you think about merging this PR to the release branch?

SGTM.

[tru]

@tru The plan is to use the new premerge CI to test changes to the release branch, right?

We're planning on backporting any changes that we're making in main to make sure the release branch CI still works, assuming that is actually the plan.

Yes please.

[github-actions]

@boomanaiden154 (or anyone else). If you would like to add a note about this fix in the release notes (completely optional). Please reply to this comment with a one or two sentence description of the fix. When you are done, please add the release:note label to this PR.