Skip to content

Instantly share code, notes, and snippets.

@richlander
Last active April 14, 2026 22:48
Show Gist options
  • Select an option

  • Save richlander/ecddb24c37f748d0e599511719185a9b to your computer and use it in GitHub Desktop.

Select an option

Save richlander/ecddb24c37f748d0e599511719185a9b to your computer and use it in GitHub Desktop.
Latest .NET release verification report (2026-04-14)

.NET Release Verification Report

  • Date: 2026-04-14
  • Tool: local Dotnet.Release.Tools build from ~/git/dotnet-release
  • Command: dotnet run --project src/Dotnet.Release.Tools -- verify releases /Users/rich/git/core/release-notes --skip-hash
  • Exit code: 2

Outcome

The updated verifier no longer reports false SDK feature-band failures for .NET 9.0 and .NET 8.0. The remaining issues are limited to unresolved .NET 11.0 preview aka.ms redirects and .NET 10.0 CDN/aka.ms drift.

Note

This was a post-fix quick rerun with --skip-hash. The earlier full verification already confirmed that download URLs were live and SHA512 values matched for the latest supported releases.

Version Latest release URLs checked CDN mismatches aka.ms mismatches Result
.NET 11.0 11.0.0-preview.3 82 0 44 Fail
.NET 10.0 10.0.5 85 3 45 Fail
.NET 9.0 9.0.15 58 0 0 Pass
.NET 8.0 8.0.26 58 0 0 Pass

Totals

  • URLs checked: 283
  • CDN latest.version mismatches: 3
  • aka.ms redirect mismatches: 89
  • Failed links in inventory below: 92

Findings

1. The SDK feature-band verifier bug is fixed

The .NET 9.0 and .NET 8.0 sections are now clean. The old false expectations like 9.0.2xx -> 9.0.313 and 8.0.3xx -> 8.0.420 no longer appear because banded SDK links are now compared against the matching band payloads from release metadata.

2. .NET 11.0 preview aka.ms aliases are still unresolved

Both the major-version aliases like aka.ms/dotnet/11.0/... and the feature-band aliases like aka.ms/dotnet/11.0.xx/... currently redirect to Bing instead of the preview payload URLs in release metadata.

3. .NET 10.0 repo metadata lags the CDN and aka.ms targets

The 10.0 latest.version files are ahead of the repo metadata, and the corresponding major-version aka.ms links resolve to the newer payloads:

  • SDK: CDN and aka.ms point to 10.0.202, while releases.json still has 10.0.201
  • Runtime: CDN and aka.ms point to 10.0.6, while releases.json still has 10.0.5
  • ASP.NET Core Runtime: CDN and aka.ms point to 10.0.6, while releases.json still has 10.0.5

The 10.0.xx SDK feature-band aliases are also unresolved right now and redirect to Bing.

Representative mismatches

Area Example
11.0 preview redirect aka.ms/dotnet/11.0/dotnet-sdk-linux-arm.tar.gz -> Bing instead of dotnet-sdk-11.0.100-preview.3.26207.106-linux-arm.tar.gz
11.0 feature-band redirect aka.ms/dotnet/11.0.xx/dotnet-sdk-linux-x64.tar.gz -> Bing instead of dotnet-sdk-11.0.100-preview.3.26207.106-linux-x64.tar.gz
10.0 CDN drift SDK CDN 10.0.202 vs repo 10.0.201; Runtime/CDN 10.0.6 vs repo 10.0.5
10.0 feature-band redirect aka.ms/dotnet/10.0.xx/dotnet-sdk-linux-x64.tar.gz -> Bing instead of dotnet-sdk-10.0.201-linux-x64.tar.gz
9.0/8.0 post-fix result No remaining failures in the quick verifier

Bottom line

The verifier fix is working: .NET 9.0 and .NET 8.0 no longer report bogus SDK band errors. What remains are real external publishing issues for .NET 11.0 preview aliases and .NET 10.0 repo/CDN/aka.ms alignment.

Complete clickable failed-link inventory

Every failed URL from the corrected post-fix run is listed below as a direct markdown link.

.NET 11.0 aka.ms redirects (44 failed link(s))
.NET 10.0 CDN latest.version (3 failed link(s))
.NET 10.0 aka.ms redirects (45 failed link(s))

___BEGIN___COMMAND_DONE_MARKER___0

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