ci: Remove deprecated windows-2025 runner#2114
Open
lgritz wants to merge 1 commit intoAcademySoftwareFoundation:mainfrom
Open
ci: Remove deprecated windows-2025 runner#2114lgritz wants to merge 1 commit intoAcademySoftwareFoundation:mainfrom
lgritz wants to merge 1 commit intoAcademySoftwareFoundation:mainfrom
Conversation
We test on 3 Windows runner configurations currently -- Windows 2022 with VS2022, Windows 2025 with VS2022, and Windows 2025 with VS2026. GitHub says the middle one will go away imminently (actually, it won't "break", but it will redirect to Windows 2025 with VS2026, which we already test). So take it out of our lineup, it's just waste. Signed-off-by: Larry Gritz <lg@larrygritz.com>
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.
We test on 3 Windows runner configurations currently -- Windows 2022 with VS2022, Windows 2025 with VS2022, and Windows 2025 with VS2026. GitHub says the middle one will go away imminently (actually, it won't "break", but it will redirect to Windows 2025 with VS2026, which we already test). So take it out of our lineup, it's just waste.