Skip to content

[feature/net11-scouting] Update dependencies from dotnet/arcade#20068

Open
dotnet-maestro[bot] wants to merge 9 commits into
feature/net11-scoutingfrom
darc-feature/net11-scouting-8f15bbbc-f998-45d1-8fc5-d5fdf25a6f7a
Open

[feature/net11-scouting] Update dependencies from dotnet/arcade#20068
dotnet-maestro[bot] wants to merge 9 commits into
feature/net11-scoutingfrom
darc-feature/net11-scouting-8f15bbbc-f998-45d1-8fc5-d5fdf25a6f7a

Conversation

@dotnet-maestro

Copy link
Copy Markdown
Contributor

This pull request updates the following dependencies

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

NatElkins and others added 3 commits July 9, 2026 16:09
…tors (#20017)

Compiler-generated occurrence names (name@line-N) are allocated from process-wide
counters on CompilerGlobalState that accumulate across compilations. When a warm
checker re-emits the same project in-process, an unchanged closure therefore gets a
different occurrence suffix than the previous emit, so consumers that align generated
names across compilations (Edit-and-Continue delta emission, #19941)
cannot match them.

Add an internal ResetCompilerGeneratedNameState to NiceNameGenerator (clears the
per-(name, file) occurrence counters), StableNiceNameGenerator (clears the cached
stable names and the inner counters), and an aggregate on CompilerGlobalState that
resets all three generators, restoring the fresh-process name layout. Callers must
ensure no compilation is concurrently generating names.

No in-tree caller yet; the consumer is the hot reload emit path in #19941.
Covered by unit tests proving drift without reset, exact replay after reset, and that
the stable-name cache itself is cleared.
…0709.10 (#20051)

On relative base path root
Microsoft.Build , Microsoft.Build.Framework , Microsoft.Build.Tasks.Core , Microsoft.Build.Utilities.Core From Version 18.10.0-preview-26358-03 -> To Version 18.10.0-1.26359.10

Co-authored-by: dotnet-maestro[bot] <dotnet-maestro[bot]@users.noreply.github.com>
…719.1

On relative base path root
Microsoft.DotNet.Arcade.Sdk From Version 11.0.0-beta.26330.1 -> To Version 11.0.0-beta.26369.1
dotnet-maestro Bot and others added 6 commits July 21, 2026 10:18
* Update dependencies from https://github.com/dotnet/msbuild build 20260710.4
On relative base path root
Microsoft.Build , Microsoft.Build.Framework , Microsoft.Build.Tasks.Core , Microsoft.Build.Utilities.Core From Version 18.10.0-1.26359.10 -> To Version 18.10.0-1.26360.4

* Update dependencies from https://github.com/dotnet/msbuild build 20260713.4
On relative base path root
Microsoft.Build , Microsoft.Build.Framework , Microsoft.Build.Tasks.Core , Microsoft.Build.Utilities.Core From Version 18.10.0-1.26359.10 -> To Version 18.10.0-1.26363.4

* Update dependencies from https://github.com/dotnet/msbuild build 20260714.11
On relative base path root
Microsoft.Build , Microsoft.Build.Framework , Microsoft.Build.Tasks.Core , Microsoft.Build.Utilities.Core From Version 18.10.0-1.26359.10 -> To Version 18.10.0-1.26364.11

* Update dependencies from https://github.com/dotnet/msbuild build 20260715.6
On relative base path root
Microsoft.Build , Microsoft.Build.Framework , Microsoft.Build.Tasks.Core , Microsoft.Build.Utilities.Core From Version 18.10.0-1.26359.10 -> To Version 18.10.0-1.26365.6

* Update dependencies from https://github.com/dotnet/msbuild build 20260716.8
On relative base path root
Microsoft.Build , Microsoft.Build.Framework , Microsoft.Build.Tasks.Core , Microsoft.Build.Utilities.Core From Version 18.10.0-1.26359.10 -> To Version 18.10.0-1.26366.8

* Update dependencies from https://github.com/dotnet/msbuild build 20260717.5
On relative base path root
Microsoft.Build , Microsoft.Build.Framework , Microsoft.Build.Tasks.Core , Microsoft.Build.Utilities.Core From Version 18.10.0-1.26359.10 -> To Version 18.10.0-1.26367.5

* Update dependencies from https://github.com/dotnet/msbuild build 20260719.1
On relative base path root
Microsoft.Build , Microsoft.Build.Framework , Microsoft.Build.Tasks.Core , Microsoft.Build.Utilities.Core From Version 18.10.0-1.26359.10 -> To Version 18.10.0-1.26369.1

* Update dependencies from https://github.com/dotnet/msbuild build 20260720.18
On relative base path root
Microsoft.Build , Microsoft.Build.Framework , Microsoft.Build.Tasks.Core , Microsoft.Build.Utilities.Core From Version 18.10.0-1.26359.10 -> To Version 18.10.0-1.26370.18

---------

Co-authored-by: dotnet-maestro[bot] <dotnet-maestro[bot]@users.noreply.github.com>
* Update dependencies from https://github.com/dotnet/roslyn build 20260709.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

* Fix NU1605 package downgrades from Roslyn 5.10.0-1.26359.4 bump

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>

* Fix MSB3277 assembly conflicts from new Roslyn VS SDK 18.9 deps

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>

* Fix runtime VS assembly load failures in legacy VS unit tests

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>

* Fix flaky AOT CI build: pass -ci to disable UpdateXlfOnBuild

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>

* Update dependencies from https://github.com/dotnet/roslyn build 20260709.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

* Update dependencies from https://github.com/dotnet/roslyn build 20260713.9
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.26363.9

* Update dependencies from https://github.com/dotnet/roslyn build 20260714.9
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.26364.9

* Update dependencies from https://github.com/dotnet/roslyn build 20260715.2
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.26365.2

* Update dependencies from https://github.com/dotnet/roslyn build 20260715.3
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.26365.3

---------

Co-authored-by: dotnet-maestro[bot] <dotnet-maestro[bot]@users.noreply.github.com>
Co-authored-by: Copilot <copilot@github.com>
Co-authored-by: Copilot <223556219+Copilot@users.noreply.github.com>
… Build ID 3013177 (#20023)

Co-authored-by: Copilot <copilot@github.com>
…ata_Desktop Batch1)

The prior build failed only in Batch1 with a SignTool 'file used by another
process' lock on FSharp.Compiler.Service...nupkg; the identical build+pack+sign
steps in Batch2 and Batch3 succeeded, so this is a transient signing race in the
Arcade SignTool, not a code regression.

Co-authored-by: Copilot <223556219+Copilot@users.noreply.github.com>
…outing-8f15bbbc-f998-45d1-8fc5-d5fdf25a6f7a
The main->feature/net11-scouting merge bumped Roslyn to 5.10.0-1.26365.3,
whose packages transitively require System.Collections.Immutable,
System.Composition and System.Reflection.Metadata >= 10.0.8. eng/Versions.props
re-pinned those (plus System.Diagnostics.DiagnosticSource) to 10.0.2 via
SystemPackagesVersion, overriding the 10.0.8 values that flow from dotnet/runtime
through Maestro in eng/Version.Details.props. Because that override is imported
after Version.Details.props, it won, producing 'Detected package downgrade ...
10.0.8 to 10.0.2' NU1605 errors across 36 projects and failing the build.

Remove the stale override so the Maestro-managed versions (10.0.8) are the single
source of truth, matching how main handles these packages.

Co-authored-by: Copilot <223556219+Copilot@users.noreply.github.com>
@github-actions github-actions Bot added the AI-Tooling-Check-Bypassed Tooling check: non-fork PR, not diff-analyzed label Jul 21, 2026
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.

2 participants