OpenParable
Skip to content
← Back to skills

Verify Releases

Testing & Quality
verify-releases

Verify Releases is an Agent Skill for testing & quality published in the dotnet/core repository on GitHub: a SKILL.md instruction file an AI agent can load to do this task.

Validate releases and release links: URL liveness, file hashes, CDN latest.version files, and aka.ms redirect targets. Uses release-notes verify and generate commands against the local release-notes directory. USE FOR: validate the latest release, validate release links, validating that all download links return HTTP 200, verifying SHA512 hashes match downloaded content, checking CDN latest.version files match releases.json, checking aka.ms redirects point to the correct download URLs, regenerating releases-index.json and releases.md after source data changes. DO NOT USE FOR: editing releases.json or release.json (edit source data directly), graph regeneration (use update-release-graph skill), supported-os changes (use update-supported-os skill).

View on GitHub ↗
QUICK START

How to use this skill

Bring this guide into your coding agent with a prompt tailored to the tool you use.

  1. Open your project in Codex.
  2. Copy and paste the prompt below.
  3. Review files and risks before approving any action.
Prompt to paste
Inspect the Agent Skill at https://github.com/dotnet/core/blob/HEAD/.github/skills/verify-releases/SKILL.md and all supporting files. Report provenance, permissions, scripts, dependencies, and security risks. Propose an exact installation into .agents/skills/verify-releases, but wait for my approval before writing files or running scripts.

Copying this prompt does not install or run the skill. Review third-party files before use.

Verify Releases

Validate .NET release data in release-notes/ using the release-notes CLI tool. This skill checks that download URLs are live, file hashes match, CDN latest.version files are current, and aka.ms redirects resolve correctly.

Prerequisites

release-notes

The release-notes tool is published to GitHub Packages. The public dotnet-release tool is now for browsing release data and CVEs.

# Install
dotnet tool install -g release-notes \
  --add-source https://nuget.pkg.github.com/richlander/index.json

# Verify — must show "verify releases" in usage output
release-notes

Note: GitHub Packages requires authentication even for public repositories. If you get a 401 error, configure credentials:

dotnet nuget add source https://nuget.pkg.github.com/richlander/index.json \
  --name github-richlander \
  --username USERNAME \
  --password "$GITHUB_TOKEN" \
  --store-password-in-clear-text

Version check: If the tool usage output does not include verify releases in its command list, the installed version is too old. Update with:

dotnet tool update -g release-notes \
  --add-source https://nuget.pkg.github.com/richlander/index.json

Commands

Verify all supported versions (full — with hash verification)

Downloads every binary and verifies SHA512 hashes against releases.json. This is the most thorough check and takes several minutes.

release-notes verify releases release-notes

Verify all supported versions (quick — skip hashes)

Checks URL liveness, CDN latest.version, and aka.ms redirects only. Much faster — typically under 30 seconds.

release-notes verify releases release-notes --skip-hash

Verify a specific major version

release-notes verify releases 10.0 release-notes
release-notes verify releases 10.0 release-notes --skip-hash

Verify a specific patch release

release-notes verify releases 10.0.5 release-notes

What gets verified

CheckDescriptionSkippable?
URL livenessHTTP HEAD on every download URL in the latest patch of each supported version's releases.jsonNo
SHA512 hashesDownloads each binary and computes SHA512, compares against releases.json hashYes (--skip-hash)
CDN latest.versionFetches CDN latest.version files for SDK, Runtime, and ASP.NET Core Runtime; compares against releases.jsonNo
aka.ms redirectsFollows aka.ms short URLs and verifies they redirect to the correct download URLNo

Exit codes

CodeMeaning
0No issues found — all checks passed
2Issues found — markdown report written to stdout

Timing expectations

ScenarioExpected duration
All versions, --skip-hash10–30 seconds
Single version, --skip-hash5–15 seconds
All versions, with hashes3–10 minutes (downloads all binaries)
Single version, with hashes1–3 minutes

CRITICAL: Never cancel the verification command early. Hash verification downloads large binaries and needs time to complete. Set your timeout to at least 10 minutes for full hash verification.

Process

1. Check tool version

Confirm release-notes is installed and has the verify releases command:

release-notes

The usage output must include release-notes verify releases [version] [path] [--skip-hash]. If it does not, update the tool (see Prerequisites).

2. Run verification

For a standard validation (recommended for release sign-off):

cd ~/git/core
release-notes verify releases release-notes

For a quick check during development:

release-notes verify releases release-notes --skip-hash

3. Interpret results

If exit code is 0: All checks passed. Report the results as a summary table.

If exit code is 2: The tool prints a markdown report to stdout listing all failures. Common issues:

IssueLikely causeFix
URL returns non-200Binary not yet published to CDNWait for CDN propagation, or fix URL in releases.json
Hash mismatchWrong hash in releases.json, or file was republishedRe-download and recompute hash, update releases.json
CDN latest.version mismatchCDN hasn't been updated for the new releaseWait for CDN update, or escalate
aka.ms redirect wrongShort URL not yet updatedUpdate aka.ms redirect configuration

4. Report results

Present a summary table with per-version results:

## .NET Release Link Verification Report

**Date:** YYYY-MM-DD
**Tool:** `release-notes` vX.Y.Z
**Command:** `release-notes verify releases release-notes`

| Version | Latest Release | Download URLs | SHA512 Hashes | CDN latest.version | aka.ms | Status |
|---------|---------------|---------------|---------------|-------------------|--------|--------|
| .NET 11.0 | `11.0.0-preview.2` | 82/82 ✅ | 81/81 ✅ | ✅ | 1/1 ✅ | **Pass** |
| .NET 10.0 | `10.0.5` | 85/85 ✅ | 84/84 ✅ | ✅ | 1/1 ✅ | **Pass** |
| .NET 9.0 | `9.0.14` | 56/56 ✅ | 53/53 ✅ | ✅ | 1/1 ✅ | **Pass** |
| .NET 8.0 | `8.0.25` | 55/55 ✅ | 53/53 ✅ | ✅ | 1/1 ✅ | **Pass** |

**Total:** 278 URLs verified, 271 hashes verified, all CDN and aka.ms checks passed.

When --skip-hash is used, omit the SHA512 Hashes column and note it in the report.

Regenerating legacy files

After verifying releases, you may also want to regenerate the legacy index and markdown:

# Regenerate releases-index.json
release-notes generate releases-index release-notes

# Regenerate releases.md
release-notes generate releases release-notes

# Lint the generated markdown
npx markdownlint --config .github/linters/.markdown-lint.yml release-notes/releases.md

Common mistakes

MistakeCorrection
Cancelling verification earlyNever cancel — hash downloads need time. Wait for completion.
Running with outdated tool versionCheck that usage shows verify releases. Update if needed.
Ignoring exit code 2Exit code 2 means issues were found. Read the stdout report.
Only running --skip-hash for release sign-offFull hash verification should be run before signing off a release.
Running from wrong directoryRun from the repo root so release-notes resolves correctly.