Switch to windows-2022 runner tag
#126
Open
Conversation
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
The
windows-latesttag currently points to Windows Server 2022 but it will be migrating to point to Windows Server 2025 starting on September 2 2025We can keep using the existing runner by switching to the
windows-2022tag. This runner will have another 3 years of support and we can migrate in the future under less of a crunch. Please don't feel you have to accept this PR if you would rather make the switch now, I'm just trying to make sure maintainers are aware and not surprised like we all were with the ubuntu-latest changes.Details about the runner change, and what other software changes are being made alongside, are documented here:
It looks like the build here is broken for other reasons. I'm still going to open the PR just as an FYI though