Skip to content

[release/10.0] Update dependencies from dotnet/icu - #136068

Open
dotnet-maestro[bot] wants to merge 3 commits into
release/10.0from
darc-release/10.0-17081cd7-4f10-4f21-9870-1a8e6f480805
Open

dotnet-maestro[bot] wants to merge 3 commits into
release/10.0from
darc-release/10.0-17081cd7-4f10-4f21-9870-1a8e6f480805

Conversation

@dotnet-maestro

@dotnet-maestro dotnet-maestro Bot commented Oct 19, 2026 •

Copy link
Copy Markdown
Contributor

This pull request updates the following dependencies

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

On relative base path root
Microsoft.NETCore.Runtime.ICU.Transport From Version 10.0.0-rtm.26505.2 -> To Version 10.0.0-rtm.26517.2
@github-actions github-actions Bot added the area-codeflow for labeling automated codeflow label Oct 19, 2026
@azure-pipelines

Copy link
Copy Markdown
Azure Pipelines:
Successfully started running 3 pipeline(s).
13 pipeline(s) were filtered out due to trigger conditions.
There may be pipelines that require an authorized user to comment /azp run to run.

ViveliDuCh added a commit that referenced this pull request Oct 21, 2026
Fixes #136232 <!-- Issue Number -->

main PR #135749 <!-- Link to PR if any that fixed this in the main
branch. -->

# Description

<!-- Give a brief summary of the issue and how the pull request is
fixing it. -->

Update `MicrosoftNativeQuicMsQuicSchannelVersion` from 2.5.11 to 2.5.12,
applying the dependency change from #135883 to release/10.0. The
corresponding release/9.0 change is #135884.

The shared version property updates both the Windows product package and
functional-test package references. No audit suppressions or
managed-code changes are included.

# Customer Impact

<!-- What is the impact to customers of not taking this fix? -->

Public release/10.0 Windows builds fail restore with NU1902 because
Microsoft.Native.Quic.MsQuic.Schannel 2.5.11 is affected by
GHSA-2mxg-prvg-9jfg (CVE-2026-85790). Version 2.5.12 is the patched
release.

This removes the MsQuic blocker also seen in #136068, but does not
address the independent System.Security.Cryptography.Pkcs 9.0.6 audit
failures tracked in #136231.

# Regression

<!-- Is this fixing a problem that was introduced in the most recent
release, ie., fixing a regression? -->

An advisory against the existing native dependency causes NuGet audit
warnings to fail restore under the existing warnings-as-errors policy.
This is not a managed-code regression.

# Testing

<!-- What kind of testing has been done with the fix. -->

Commands were run on Windows x64 with the repository SDK 10.0.111:

- Before the change, `.\dotnet.cmd restore
.\src\libraries\System.Net.Quic\src\System.Net.Quic.csproj
/p:TargetOS=windows /p:TargetArchitecture=x64 --no-cache -v:quiet`
failed with NU1902 for Schannel 2.5.11.
- After the change, the same restore command passed (exit 0), and
project.assets.json resolved
Microsoft.Native.Quic.MsQuic.Schannel/2.5.12.
- `.\dotnet.cmd build
.\src\libraries\System.Net.Quic\src\System.Net.Quic.csproj
/p:TargetOS=windows /p:TargetArchitecture=x64 -v:quiet` passed with 0
warnings and 0 errors.
- `.\dotnet.cmd build /t:test
.\src\libraries\System.Net.Quic\tests\FunctionalTests\System.Net.Quic.Functional.Tests.csproj
/p:TargetOS=windows /p:TargetArchitecture=x64 -v:quiet` failed before
test execution: "The shared framework must be built before the local
targeting pack can be consumed." No functional tests ran.
- As a separate blocker check, `.\dotnet.cmd restore
.\src\tasks\Crossgen2Tasks\Crossgen2Tasks.csproj /p:TargetOS=windows
/p:TargetArchitecture=x64 --no-cache -v:quiet` failed with the existing
Pkcs 9.0.6 NU1902/NU1903 errors. The assets graph shows this dependency
comes from NuGet.Packaging/7.0.3-rc.46203.

A full main-branch baseline was explicitly waived for this
dependency-only change. No full runtime/libraries build or functional
test run was completed.

# Risk

<!-- Please assess the risk of taking this fix. Provide details backing
up your assessment. -->

Low: a one-line native dependency patch-version bump, matching the
version already used by main, release/8.0, and release/9.0. Targeted
restore and compilation passed; native runtime behavior remains
unverified locally because the functional tests could not start.

# Package authoring no longer needed in .NET 9

IMPORTANT: Starting with .NET 9, you no longer need to edit a NuGet
package's csproj to enable building and bump the version.
Keep in mind that we still need package authoring in .NET 8 and older
versions.

Co-authored-by: Copilot <223556219+Copilot@users.noreply.github.com>
Copilot-Session: 792c8703-3703-4180-975a-9b86d809b48a
On relative base path root
Microsoft.NETCore.Runtime.ICU.Transport From Version 10.0.0-rtm.26505.2 -> To Version 10.0.0-rtm.26552.2

This branch has not been deployed

No deployments
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

area-codeflow for labeling automated codeflow

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant