Bump from windows-2019 to windows-2022 in CI #290
Closed
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
The windows-2019 image is no longer supported by GitHub Actions.
Collaborator
Author
|
Closing after gh-294 |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
1 participant
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-2019 image is no longer supported by GitHub Actions.
In gh-289 I found that the Windows build failed because of a new version of the setup-msys2 action. Looking into that I discovered that the GitHub actions windows-2019 runners will not be available by the end of the month (in a week!). Bumping to windows-2025 didn't work so we'll try windows-2022.
If this works then the msys2 issue still remains but we have another few years before needing to bump the Windows version.