Skip to content

[main] Update dependencies from dotnet/roslyn#20052

Open
dotnet-maestro[bot] wants to merge 7 commits into
mainfrom
darc-main-ff3273b8-b033-408e-afdf-48672ece29e0
Open

[main] Update dependencies from dotnet/roslyn#20052
dotnet-maestro[bot] wants to merge 7 commits into
mainfrom
darc-main-ff3273b8-b033-408e-afdf-48672ece29e0

Conversation

@dotnet-maestro

@dotnet-maestro dotnet-maestro Bot commented Jul 10, 2026

Copy link
Copy Markdown
Contributor

This pull request updates the following dependencies

From https://github.com/dotnet/roslyn

  • Dependency Updates:
    • From 5.10.0-1.26358.9 to 5.10.0-1.26359.5
      • Microsoft.CodeAnalysis
      • Microsoft.CodeAnalysis.Compilers
      • Microsoft.CodeAnalysis.CSharp
      • Microsoft.CodeAnalysis.EditorFeatures
      • Microsoft.CodeAnalysis.EditorFeatures.Text
      • Microsoft.CodeAnalysis.ExternalAccess.FSharp
      • Microsoft.CodeAnalysis.Features
      • Microsoft.VisualStudio.LanguageServices

…709.4

On relative base path root
Microsoft.CodeAnalysis , Microsoft.CodeAnalysis.Compilers , Microsoft.CodeAnalysis.CSharp , Microsoft.CodeAnalysis.EditorFeatures , Microsoft.CodeAnalysis.EditorFeatures.Text , Microsoft.CodeAnalysis.ExternalAccess.FSharp , Microsoft.CodeAnalysis.Features , Microsoft.VisualStudio.LanguageServices From Version 5.10.0-1.26358.9 -> To Version 5.10.0-1.26359.4
@github-actions

Copy link
Copy Markdown
Contributor

✅ No release notes required

@github-actions github-actions Bot added the AI-Tooling-Check-Bypassed Tooling check: non-fork PR, not diff-analyzed label Jul 10, 2026
Copilot and others added 6 commits July 10, 2026 11:17
The new Roslyn build adds a net472 dependency on Microsoft.VisualStudio.SDK
18.9.496-Preview and bumps its runtime deps to 10.0.8, causing package
downgrade errors:
- System.Collections.Immutable / System.Reflection.Metadata / System.Composition
  now required >= 10.0.8 (were pinned to 10.0.2)
- VS interops (OLE/Shell/TextManager.Interop) required >= 18.9.438
- Microsoft.VisualStudio.Threading required >= 18.7.19

The three interop packages are decoupled from the shared shell package
version since the VS SDK pins them newer than the other shell packages.

Co-authored-by: Copilot <223556219+Copilot@users.noreply.github.com>
The new Roslyn Microsoft.CodeAnalysis.ExternalAccess.FSharp (net472) now
depends on Microsoft.VisualStudio.SDK 18.9.496 and its coherent 18.9.x VS
package set, pulling newer transitive assemblies than fsharp's 18.0.x Shell
packages. This caused MSB3277 (assembly version conflicts) across the
vsintegration projects for:
- System.Diagnostics.DiagnosticSource (10.0.2 vs 10.0.8)
- Microsoft.VisualStudio.Validation (17.13 vs 18.7.1)
- StreamJsonRpc (2.23 vs 2.26.5)
- Microsoft.ServiceHub.Framework (4.9 vs 4.10.128)
- Microsoft.VisualStudio.RpcContracts (17.15.25 vs 18.9.453)

Bump DiagnosticSource to 10.0.8 (coherent with the other runtime deps) and
pin the four remaining transitive packages to the exact versions Roslyn
pulls, so all vsintegration projects resolve them coherently.

Co-authored-by: Copilot <223556219+Copilot@users.noreply.github.com>
The Roslyn 5.10.0-1.26359.4 bump pulls Microsoft.VisualStudio.SDK 18.9.496 which transitively upgrades the editor assemblies (Microsoft.VisualStudio.Text.*, .Editor) to 18.9.123 and Shell.15.0 to 18.9.x. Two runtime-only breaks remained after the earlier NU1605/MSB3277 build-time fixes, both surfacing as a ReflectionTypeLoadException in the VsMocks MEF catalog that failed all ~1959 legacy VS unit tests:

1. Microsoft.VisualStudio.Platform.VSEditor is not pulled transitively, so it stayed pinned at 18.0.404-preview and its implementation types no longer bind against the newer Text.Internal 18.9.123 interfaces. Pin VSEditor to 18.9.123 to match.

2. Shell.15.0 18.9.x references Microsoft.VisualStudio.SolutionPersistence at runtime without declaring it as a NuGet dependency; deploy it next to the VS unit-test host (scoped to test projects to keep it out of the VSIX).

Co-authored-by: Copilot <223556219+Copilot@users.noreply.github.com>
The Build_And_Test_AOT_Windows job runs '.\Build.cmd -pack' without -ci, so ContinuousIntegrationBuild is not set. Arcade then enables UpdateXlfOnBuild, which flakily fails with 'MSB4057: The target UpdateXlf does not exist' on FSharp.Core (the classic_metadata leg failed while the identical compressed_metadata leg passed). Every other CI job builds via CIBuildNoPublish.cmd/cibuild.sh, which pass -ci. Add -ci here for consistency so ContinuousIntegrationBuild=true and UpdateXlfOnBuild stays disabled.

Co-authored-by: Copilot <223556219+Copilot@users.noreply.github.com>
…709.5

On relative base path root
Microsoft.CodeAnalysis , Microsoft.CodeAnalysis.Compilers , Microsoft.CodeAnalysis.CSharp , Microsoft.CodeAnalysis.EditorFeatures , Microsoft.CodeAnalysis.EditorFeatures.Text , Microsoft.CodeAnalysis.ExternalAccess.FSharp , Microsoft.CodeAnalysis.Features , Microsoft.VisualStudio.LanguageServices From Version 5.10.0-1.26358.9 -> To Version 5.10.0-1.26359.5
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

AI-Tooling-Check-Bypassed Tooling check: non-fork PR, not diff-analyzed

Projects

Status: New

Development

Successfully merging this pull request may close these issues.

0 participants