Update Roslyn, and package versions to match Roslyn#13028
Merged
davidwengier merged 9 commits intomainfrom Apr 10, 2026
Merged
Conversation
This was referenced Apr 10, 2026
davidwengier
added a commit
that referenced
this pull request
Apr 14, 2026
davidwengier
added a commit
to dotnet/roslyn
that referenced
this pull request
Apr 28, 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
2 participants
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.
In advance of bringing the Razor repo into Roslyn, we need to align on package versions. These are the version updates where Roslyn was ahead of Razor, plus updating Roslyn itself, so we can be sure dependent package updates are all in correctly, and we can unskip some tests that were waiting on a new version.
Roslyn side: dotnet/roslyn#83109