Bump vulnerable packages to unblock 3.x CI#3054
Merged
Merged
Conversation
Three known-vulnerable package versions were breaking restore/build: - OpenTelemetry.* 1.14.0 in Quartz.Examples.AspNetCore: hard NU1902 errors (GHSA-g94r-2vxg-569j on .Api, GHSA-mr8r-92fq-pj8p and GHSA-q834-8qmm-v933 on .Exporter.OpenTelemetryProtocol). Bumped the four directly-referenced packages — .Exporter.Console, .Exporter.OpenTelemetryProtocol, .Exporter.Zipkin, .Extensions.Hosting — to 1.15.3 (latest stable). - NuGet.Packaging 6.12.1 transitively pulled in by Nuke.Common 10.1.0 in build/_build.csproj: NU1901 (low, GHSA-g4vj-cjjj-v7hg). Added an explicit PackageReference pinning 7.3.1. - System.Security.Cryptography.Xml 9.0.0 transitively pulled in via the same path: NU1903 (high, GHSA-37gx-xxp4-5rgx and GHSA-w3x6-4m5h-cxqf). Added an explicit PackageReference pinning 10.0.7. The two transitive overrides are commented as removable once Nuke.Common ships a release that bumps them itself. Verified: dotnet build Quartz.slnx -c Release now succeeds with zero warnings and zero errors (was: 3 NU1902 errors blocking restore). Co-Authored-By: Claude Opus 4.7 (1M context) <[email protected]>
|
6 tasks
This was referenced Apr 27, 2026
Merged
Closed
Closed
3 tasks
This was referenced May 12, 2026
This was referenced May 20, 2026
This was referenced Jun 1, 2026
This was referenced Jun 8, 2026
This was referenced Jun 21, 2026
This was referenced Jun 28, 2026
This was referenced Jul 5, 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
1 participant
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.
Summary
Three known-vulnerable package versions were breaking restore/build on
3.x:OpenTelemetry.Exporter.ConsoleOpenTelemetry.Exporter.OpenTelemetryProtocolOpenTelemetry.Exporter.ZipkinOpenTelemetry.Extensions.HostingOpenTelemetry.Api(transitive)NuGet.Packaging(transitive via Nuke.Common)System.Security.Cryptography.Xml(transitive via Nuke.Common)The
OpenTelemetry.*bumps go insrc/Quartz.Examples.AspNetCore/Quartz.Examples.AspNetCore.csproj(direct references). The other two are transitive deps ofNuke.Common 10.1.0inbuild/_build.csproj, so they get explicit<PackageReference>overrides — annotated as removable once Nuke.Common ships a release that bumps them itself.OpenTelemetry.Apiisn't directly referenced; pulling the four exporter/extension packages forward to 1.15.3 brings .Api 1.15.3 along transitively.Why now
OpenTelemetry.Exporter.OpenTelemetryProtocol 1.14.0triggersNU1902errors during restore (it's a direct reference, soWarningsAsErrorspromotes the moderate-severity warning to a build break). That blocks every PR's CI restore on3.x, including the in-flight #3053 (Quartz.Redis rename).The two transitive overrides in
build/_build.csprojclean up theNU1901/NU1903warnings that show up on every job that restores the build project — annoying noise rather than a hard break, but worth fixing while we're here, especially since one of them (System.Security.Cryptography.Xml) is high severity.Test plan
dotnet restore build/_build.csproj— clean, no NU1901/NU1903dotnet restore src/Quartz.Examples.AspNetCore/...— clean, no NU1902dotnet build Quartz.slnx -c Release— succeeds with 0 warnings, 0 errors (was: 3 NU1902 errors blocking restore)🤖 Generated with Claude Code