[erikzrekz]

Part of ENG-2633 (project: Docs analytics-driven improvements). Builds on #91, now merged.

Why

Release notes are the #2 page on docs.radiustech.xyz (80 views, Sep 26 – Oct 26), but they cover the network only, and the newest entry is 2026-09-28. Since then:

• the SDK has shipped 0.4.0 to 0.7.0,
• the CLI 0.3.1 to 0.6.0,
• the skills plugin 0.0.2 to 0.2.2.

None of that reached the page. Most traffic arrives as pasted links (61% direct), and 43% of it is on phones, so each release needs its own link that works there.

What changes

Skills changelog (1ef942d)

• New plugins/radius/CHANGELOG.md, backfilled from 0.0.2 to 0.2.2 using the versions as they landed on main. I checked each entry against its diff.
• scripts/validate_plugin.py fails CI when the manifest version has no ## <version> (<YYYY-MM-DD>) entry, a heading is malformed, or entries aren't newest first.
• AGENTS.md and the root README gain the rule.
• The changelog isn't release content, so no plugin version bump.

Generated page and feed (022e955, e8b54d6)

• scripts/generate-release-notes.ts writes docs/pages/release-notes.mdx and public/release-notes.xml. Both are gitignored.
• prebuild, predev, docs:validate and docs:markdown-audit run it.

Section	Source	Rule
Radius Network	release-notes/network.md	Moved from the page unchanged; written by hand
radius-sdk, radius-cli	their CHANGELOG.md (Changesets)	A version appears once its <pkg>@<version> tag exists, dated by the tag, so the docs never announce what isn't on npm. Major / Minor / Patch become Breaking changes / New / Fixes. A minor change with bold text starting "Breaking" (**Breaking:**, **Breaking for installs:**) goes under Breaking. "Updated dependencies" becomes one Uses radius-sdk@x.y.z. line. Links to npm and the GitHub release.
Radius skills	plugins/radius/CHANGELOG.md	One section per version

• Layout: one timeline, newest first. Each release is a ## <date>: <product> <version> heading, so #2026-10-27-radius-sdk-070 is a stable link to share. A table at the top links the latest release of each product.
• Headlines: each change's first sentence is bolded, as written.
• Page description: names the latest release (now "Latest: radius-sdk 0.7.0 (2026-10-27). Add Radius to an x402 server you already run."), so link previews and llms.txt show what's new.
• Missing tags fail the build. A checkout without release tags errors instead of quietly dropping the SDK and CLI. docs.yml now checks out with fetch-depth: 0 and fetch-tags: true, like docs-deploy.yml.
• CI additions: docs.yml runs the new tests (pnpm test:release-notes) and also triggers on packages/cli/CHANGELOG.md.

Sharing and measurement (16c67fc)

• <link rel="alternate" type="application/atom+xml"> on every page.
• _headers serves the feed as application/atom+xml.
• The Worker from docs: record agent fetches of pages and agent files, serve Markdown on request (Workers Logs + Analytics Engine) #91 records feed fetches in docs_agent_fetches.
• Anchor fix (every page): a link to a heading now scrolls it below both fixed bars. Vocs offsets headings for the top nav only, so the "On this page" bar covered a shared release.

Up to date with main (aee3b3d)

• Merged main, which brings in docs: record agent fetches of pages and agent files, serve Markdown on request (Workers Logs + Analytics Engine) #91, Let the Version Packages PR run CI; install x402 peers in skills #89 and the Version Packages release (radius-sdk 0.7.0 and radius-cli 0.6.0, tagged 2026-10-27). No conflicts.
• Both new versions are on the page. That release also showed the old Breaking rule missed "Breaking for installs:", fixed in e8b54d6.

Why not Vocs's built-in ::changelog: it reads GitHub Releases from one repo and renders through a client component. It has no per-product anchors, network notes, skills or feed.

Verification

On e8b54d6:

• From packages/docs, all pass: format:check, lint, typecheck:docs, docs:validate (0 errors, 0 warnings, including the generated page), test:skills, test:release-notes (10 tests), docs:markdown-audit, build, docs:agent-check and docs:sitemap-check.
• python3 scripts/validate_plugin.py --base-ref origin/main passes. With a malformed heading, or the current version removed from the changelog, it fails as intended (checked on 1ef942d).
• Built output:
  • 32 releases: 7 network, 7 SDK, 7 CLI, 11 skills.
  • Every heading anchor matches the built HTML ids.
  • The feed has 32 entries.

On 16c67fc:

• Markdown version, llms.txt and sitemap: /release-notes.md, the llms.txt line and the sitemap entry are present.
• Feed format: the feed parses as Atom, with unique ids and the required elements.
• wrangler dev + Playwright, 390 px and 1280 px: no horizontal overflow, and an anchor link lands below both fixed bars on phone, desktop and 1600 px. It did not before the CSS fix.
• Feed fetches return application/atom+xml and are recorded as agent fetch. noindex still applies on workers.dev hosts.

For the reviewer

• When new entries go live: production picks them up on the next docs deploy, either after an npm release or a docs-only deploy run by hand. The deploy that followed the 0.7.0 / 0.6.0 release ran from main without this PR, so the live page shows the new entries only after the next deploy.
• Network notes: none have been written since 2026-09-28. This PR keeps the section and its format but doesn't invent entries. They need a source from the network team.
• Follow-ups (not here): a per-release OG image; KPIs for release-notes views, social referrers and feed fetches in the weekly report.

🤖 Generated with Claude Code

https://claude.ai/code/session_012M6NrUBhuq32wQaTAVbWn7

[github-actions]

Docs preview: https://pr-92-radius-docs.radius-technology-systems.workers.dev (e8b54d6)

[github-actions]

⚠️ No Changeset found

Latest commit: e8b54d6

Merging this PR will not cause a version bump for any packages. If these changes should not result in a new version, you're good to go. If these changes should result in a version bump, you need to add a changeset.

This PR includes no changesets

When changesets are added to this PR, you'll see the packages that this PR includes changesets for and the associated semver types

Click here to learn what changesets are, and how to add one.

Click here if you're a maintainer who wants to add a changeset to this PR