Skip to content

chore: bump Aspire 13.3.1 → 13.4.6 to clear MessagePack advisories - #579

Merged
jeremydmiller merged 1 commit into
mainfrom
chore/bump-aspire-messagepack
Jul 29, 2026
Merged

chore: bump Aspire 13.3.1 → 13.4.6 to clear MessagePack advisories#579
jeremydmiller merged 1 commit into
mainfrom
chore/bump-aspire-messagepack

Conversation

@jeremydmiller

Copy link
Copy Markdown
Member

Every restore emitted eleven NU1902/NU1903 warnings for MessagePack 2.5.192, reached transitively via Aspire.HostingKubernetesClient. One is high severity (GHSA-vh6j-jc39-fggf, GHSA-hv8m-jj95-wg3x); the rest are moderate. All eleven are patched in 2.5.301 on the 2.x line.

Fixed at the source, not pinned

Aspire 13.4.6 brings KubernetesClient 19.0.2, which depends on MessagePack 2.5.302 — already past the patched floor. No direct MessagePack reference needed.

13.3.1 13.4.6
KubernetesClient 18.0.13 19.0.2
MessagePack 2.5.192 ⚠️ 2.5.302
MessagePack.Annotations 2.5.192 2.5.302

Why not the other two options

  • A direct PackageReference would add a dependency JasperFx.Aspire doesn't use to the shipped package's dependency graph, purely to force a floor.
  • CentralPackageTransitivePinningEnabled pins every transitive that has a PackageVersion entry. This repo pins Microsoft.Extensions.* at 9.0.0/10.0.0 while Aspire pulls newer ones (Microsoft.Extensions.AI.Abstractions 10.3.0), so it risked silently downgrading Aspire's own dependencies.

Verification

Restore is free of NU1902/NU1903 across the whole solution. All 51 Aspire tests pass; full ./build.sh test green.

🤖 Generated with Claude Code

Every restore emitted eleven NU1902/NU1903 warnings for MessagePack 2.5.192,
reached transitively through Aspire.Hosting -> KubernetesClient. One is high
severity (GHSA-vh6j-jc39-fggf, GHSA-hv8m-jj95-wg3x); the rest are moderate. All
eleven are patched in 2.5.301 on the 2.x line.

Fixed at the source rather than by pinning. Aspire 13.4.6 brings
KubernetesClient 19.0.2, which depends on MessagePack 2.5.302 -- already past
the patched floor, so no direct MessagePack reference is needed.

The two alternatives were both worse. A direct PackageReference would add a
dependency JasperFx.Aspire does not use to the shipped package's dependency
graph. CentralPackageTransitivePinningEnabled would pin every transitive that
has a PackageVersion entry, and this repo pins Microsoft.Extensions.* at
9.0.0/10.0.0 while Aspire pulls newer ones (Microsoft.Extensions.AI.Abstractions
10.3.0), so it risked downgrading Aspire's own dependencies.

Restore is now free of NU1902/NU1903 across the solution. All 51 Aspire tests
pass; full suite green.

Co-Authored-By: Claude Opus 5 (1M context) <noreply@anthropic.com>
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant