Update and pin reusable workflows, drop msvc-dev-cmd workflow and switch to windows-2025-vs2026#228
Merged
Merged
Conversation
Signed-off-by: William Kearney <william.kearney@uni-potsdam.de>
Closes TopoToolbox#219 Starting from VS 2026, we don't seem to need to set up the developer command prompt. The windows-latest images will change fully to VS 2026 some time in June 2026, but for now, we can compile on windows-2025-vs2026. Signed-off-by: William Kearney <william.kearney@uni-potsdam.de>
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
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.
Closes #219
Starting from VS 2026, we don't seem to need to set up the developer
command prompt. The windows-latest images will change fully to VS 2026
some time in June 2026, but for now, we can compile on
windows-2025-vs2026.