Skip to content

chore(deps): bump all NuGet references to latest stable + fix release job#67

Merged
StuartMeeks merged 2 commits into
mainfrom
fix/release-nbgv-allow-downgrade
Jul 1, 2026
Merged

chore(deps): bump all NuGet references to latest stable + fix release job#67
StuartMeeks merged 2 commits into
mainfrom
fix/release-nbgv-allow-downgrade

Conversation

@StuartMeeks

@StuartMeeks StuartMeeks commented Jul 1, 2026

Copy link
Copy Markdown
Owner

Why

Two things, both dependency-maintenance:

  1. The v1.1.0 release run failed at Install Nerdbank.GitVersioning CLI:

    The requested version 3.9.50 is lower than existing version 3.10.85.
    

    The windows-latest runner now preinstalls nbgv 3.10.85, and dotnet tool install --version 3.9.50 refuses to downgrade. Fixed by pinning nbgv to the latest stable 3.10.85 (in sync with the Nerdbank.GitVersioning package) and adding --allow-downgrade as insurance against future runner drift.

  2. Refresh all NuGet references to latest stable (per request). Packages already at latest are untouched (Microsoft.WindowsAppSDK 2.2.0, the Microsoft.Extensions/Microsoft.Data.Sqlite 10.0.9 line, Velopack, xunit, etc.).

Bumps

Package From To
Nerdbank.GitVersioning 3.9.50 3.10.85
Markdig 1.2.0 1.3.2
Microsoft.Web.WebView2 1.0.3967.48 1.0.4022.49
Microsoft.Windows.SDK.BuildTools 10.0.28000.1839 10.0.28000.2270
Spectre.Console 0.56.0 0.57.1
Microsoft.NET.Test.Sdk 18.6.0 18.7.0

Spectre.Console.Cli stays at 0.55.0 — no newer stable exists yet; it still builds and tests clean against Spectre.Console 0.57.1.

Testing

  • Core 245 / Execution 61 / Importer 66 tests pass.
  • Full solution builds clean on the Windows head (WinUI/XAML), 0 warnings.

Release follow-up

A tag-triggered workflow runs the workflow file at the tagged commit, so once this merges I'll move v1.1.0 onto the new main HEAD (which includes the CI fix) and re-trigger the release. These deps therefore ship in 1.1.0 — changelog updated accordingly.

🤖 Generated with Claude Code

StuartMeeks and others added 2 commits July 1, 2026 07:50
…version

The windows-latest runner now preinstalls a newer nbgv (3.10.85) than the
version this workflow pins (3.9.50, kept in sync with the Nerdbank.GitVersioning
package), and `dotnet tool install` refuses to downgrade, failing the release
job before it builds. Add --allow-downgrade so the exact pinned version installs
regardless of what the runner ships.

Co-Authored-By: Claude Opus 4.8 (1M context) <noreply@anthropic.com>
Pin nbgv to the latest stable (3.10.85, matching the hosted runner) and keep the
release CLI in sync via the same version plus --allow-downgrade, fixing the
release job that broke when the runner preinstalled a newer nbgv. Also refresh
the remaining out-of-date packages to their latest stable:

  Markdig                          1.2.0        -> 1.3.2
  Microsoft.Web.WebView2           1.0.3967.48  -> 1.0.4022.49
  Microsoft.Windows.SDK.BuildTools 10.0.28000.1839 -> 10.0.28000.2270
  Spectre.Console                  0.56.0       -> 0.57.1
  Microsoft.NET.Test.Sdk           18.6.0       -> 18.7.0

Spectre.Console.Cli stays at 0.55.0 (no newer stable). All test suites pass and
the full solution builds clean on the Windows head.

Co-Authored-By: Claude Opus 4.8 (1M context) <noreply@anthropic.com>
@StuartMeeks StuartMeeks changed the title fix(ci): allow nbgv downgrade in the release job chore(deps): bump all NuGet references to latest stable + fix release job Jul 1, 2026
@StuartMeeks StuartMeeks merged commit 946fdca into main Jul 1, 2026
6 checks passed
@StuartMeeks StuartMeeks deleted the fix/release-nbgv-allow-downgrade branch July 1, 2026 07:59
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