Downgrade to windows-2022 to keep using VS2022#1984
Merged
nullsystem merged 1 commit intoJun 11, 2026
Conversation
See: actions/runner-images#14017 As it stands, if we keep on using windows-2025 every builds from now on will end up using VS2026 and it's hard crashing at the moment: https://developercommunity.visualstudio.com/t/MSVC-v1451-Linker-Crash-in-IncrCalcPtrs/11090307 2026-06-10 main branch build run: https://github.com/NeotokyoRebuild/neo/actions/runs/27300329689 This crash may only be for a short duration and VS2026 updates but still I think VS2026 is too new and isn't ready yet.
Rainyan
approved these changes
Jun 10, 2026
sunzenshen
approved these changes
Jun 11, 2026
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.
Description
See: actions/runner-images#14017
As it stands, if we keep on using windows-2025 every builds from now on will end up using VS2026 and it's hard crashing at the moment:
https://developercommunity.visualstudio.com/t/MSVC-v1451-Linker-Crash-in-IncrCalcPtrs/11090307
2026-06-10 main branch build run:
https://github.com/NeotokyoRebuild/neo/actions/runs/27300329689
This crash may only be for a short duration and VS2026 updates but still I think VS2026 is too new and isn't ready yet.
Toolchain