Prepare build to windows-2022 GitHub action image #585
Conversation
This file contains 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
alexarchambault
force-pushed
the
windows-2022
branch
from
73241b3
to
2a3ee46
Compare
alexarchambault
changed the title
alexarchambault
force-pushed
the
windows-2022
branch
from
2a3ee46
to
65b43ae
Compare
alexarchambault
force-pushed
the
windows-2022
branch
from
65b43ae
to
ca1f786
Compare
romanowski
approved these changes
Jan 28, 2022
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.
Seems
windows-latestis supposed to becomewindows-2022soon, I just want to check if everything runs fine on it.