Skip to content

Move Aspire to 13.6.5, for GHSA-f7vh-h5g3-7jrh - #13

Merged
sadeqabuhattem merged 2 commits into
mainfrom
chore/aspire-13.6.5
Nov 14, 2026
Merged

sadeqabuhattem merged 2 commits into
mainfrom
chore/aspire-13.6.5

Conversation

@sadeqabuhattem

@sadeqabuhattem sadeqabuhattem commented Nov 14, 2026 •

Copy link
Copy Markdown
Member

What

Moves Aspire from 13.6.4 to 13.6.5:

  • the 8 Aspire pins in Directory.Packages.props;
  • the AppHost's Aspire.AppHost.Sdk;
  • a Security entry in the changelog.

Why

GHSA-f7vh-h5g3-7jrh (CVE-2026-120006) is a
high-severity elevation-of-privilege advisory for Aspire.Hosting and Aspire.Hosting.AppHost below
13.6.5. NuGet's audit treats it as an error, so dotnet restore (CI's first step) fails on 13.6.4.
Only the local AppHost uses Aspire; no shipped package depends on it, so nothing that consumes the library
is affected.

Microsoft.Extensions.* for the AppHost

Aspire 13.6.5 needs Microsoft.Extensions.* 10.0.14 or later. With every project pinned at 10.0.12,
transitive pinning made the AppHost's restore a downgrade error (NU1109). The pins now split on
IsShippedLibrary (added to src/Directory.Build.props, which had no such flag), the way Media's already do:

  • shipped libraries keep 10.0.12, so their dependency floors are unchanged (checked by packing them);
  • tests, samples and the AppHost take 10.0.14.

Verified locally

  • dotnet restore --force-evaluate (fresh vulnerability data) and a Release build of the whole
    solution, AppHost included: 0 warnings, 0 errors.
  • Tests in Release: UnitTests 210, ProviderTests 63, ApiTests 51 (each on net8.0 and net10.0),
    IntegrationTests 158. All pass.

Also: Coverage Gate's action ref

A second commit pins danielpalme/ReportGenerator-GitHub-Action to the full commit SHA its 5 tag
points at (5f3701a…, v5.6.0). GitHub Actions now refuses the ref 5 because it reads like a
shortened commit SHA, so Coverage Gate failed while setting up, before any coverage step ran. That
would fail on main today too; the gate runs exactly the action it ran before.

Merge with the others

The same bump is going into the other DotNetBoost repositories. They share one Aspire.AppHost.Sdk
version so they can build in one local workspace, so these should merge close together.

🤖 Generated with Claude Code

sadeqabuhattem and others added 2 commits November 14, 2026 20:22
Aspire.Hosting and Aspire.Hosting.AppHost below 13.6.5 carry a high-severity
elevation-of-privilege advisory (CVE-2026-120006). NuGet's audit treats it as an
error, so restore fails, and CI with it. Only the local AppHost uses Aspire; no
shipped package depends on it.

Aspire 13.6.5 also needs Microsoft.Extensions.* 10.0.14, which transitive pinning
turned into a downgrade error for the AppHost. Tests, samples and the AppHost now
take 10.0.14; the shipped packages keep their 10.0.12 floor, so nothing that
consumes them has to move.

Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
GitHub Actions now refuses the ref `5`: it reads like a shortened commit SHA,
which it no longer accepts, so Coverage Gate failed while downloading its
actions, before any coverage step ran. The SHA is the commit the `5` tag points
at (v5.6.0), so the gate runs exactly the action it ran before.

Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
@sadeqabuhattem
sadeqabuhattem merged commit 75b9016 into main Nov 14, 2026
10 checks passed
@sadeqabuhattem
sadeqabuhattem deleted the chore/aspire-13.6.5 branch November 14, 2026 19:26
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