Update roslyn to 5.11.0-1.26379.2 - #9592
Merged
Merged
Conversation
Co-authored-by: Copilot <223556219+Copilot@users.noreply.github.com>
Co-authored-by: Copilot <223556219+Copilot@users.noreply.github.com>
Contributor
There was a problem hiding this comment.
Pull request overview
Bumps the Roslyn component version used by the VS Code C# extension to 5.11.0-1.26379.2, and records the update (with notable upstream items) in the extension changelog.
Changes:
- Update the default Roslyn version from
5.10.0-1.26376.1to5.11.0-1.26379.2. - Add a new
CHANGELOG.mdentry under2.147.xdescribing the Roslyn update and highlighting included upstream fixes/optimizations.
Show a summary per file
| File | Description |
|---|---|
| package.json | Updates the extension’s default Roslyn version to 5.11.0-1.26379.2. |
| CHANGELOG.md | Adds a 2.147.x changelog entry documenting the Roslyn version bump and key upstream PRs. |
Copilot's findings
- Files reviewed: 2/2 changed files
- Comments generated: 0
dibarbet
approved these changes
Jul 29, 2026
Co-authored-by: David Barbet <dibarbet@gmail.com>
dibarbet
approved these changes
Jul 29, 2026
Contributor
There was a problem hiding this comment.
Copilot's findings
Comments suppressed due to low confidence (2)
test/vscodeLauncher.ts:24
- This function receives an
envobject but checksprocess.env.CODE_VERSIONinstead, which makes it harder for callers to override the VS Code version via the provided env. Usingenv.CODE_VERSIONalso keeps the log message consistent (and fixes the typo in "overriden").
if (process.env.CODE_VERSION) {
console.log(`VSCode version overriden to ${process.env.CODE_VERSION}.`);
vscodeVersion = process.env.CODE_VERSION;
}
test/vscodeLauncher.ts:20
- The comment says the VS Code version is pinned due to macOS test issues, but the current default pins all platforms to 1.130. If the intent is only to work around macOS legs, keep other platforms on 'insiders' (or whatever default you want) to preserve broader coverage.
// Normally we test against 'insiders' but have pinned to a previous release due to
// issues in the MacOS test legs.
let vscodeVersion = '1.130';
- Files reviewed: 3/3 changed files
- Comments generated: 0 new
peterwald
reviewed
Jul 29, 2026
| let vscodeVersion = 'insiders'; | ||
| // Normally we test against 'insiders' but have pinned to a previous release due to | ||
| // issues in the MacOS test legs. | ||
| let vscodeVersion = '1.130'; |
Member
There was a problem hiding this comment.
I believe the fix for this is to upgrade @vscode/test-electron to 3.1.0. We ran into this in vs-green as well.
Member
Author
There was a problem hiding this comment.
Will give that a shot. Thanks!
Contributor
There was a problem hiding this comment.
Copilot's findings
Comments suppressed due to low confidence (1)
package.json:146
- This PR is titled/described as a Roslyn update, but it also bumps
@vscode/test-electronto a new major version (and in the lockfile this brings a higher minimum Node engine). Please either split this dependency upgrade into a separate PR or update the PR description to explicitly call out why this is needed as part of the Roslyn update, since it can affect how contributors run/diagnose tests locally.
"@vscode/test-electron": "^3.1.0",
- Files reviewed: 2/3 changed files
- Comments generated: 0 new
dibarbet
approved these changes
Jul 29, 2026
peterwald
approved these changes
Jul 29, 2026
Contributor
There was a problem hiding this comment.
Copilot's findings
Comments suppressed due to low confidence (1)
CHANGELOG.md:14
- This PR also updates the bundled Source Test Discovery version (defaults.testDiscovery), but the changelog entry for 2.147.x only mentions the Roslyn bump. Please add a changelog bullet for the test discovery update so the release notes reflect all component-version changes.
* Honour C# new line settings in Razor auto insert (PR: [#84632](https://github.com/dotnet/roslyn/pull/84632))
* Update Roslyn to 5.10.0-1.26376.1 (PR: [#9584](https://github.com/dotnet/vscode-csharp/pull/9584))
- Files reviewed: 2/3 changed files
- Comments generated: 0 new
dibarbet
approved these changes
Jul 29, 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.
View Complete Diff of Changes
SyntaxNodeActions for union declarations and its members (PR: #84604)