Skip to content

0.21.0: records at v0.21.0, and a blog that announces it - #8

Merged
sdogruyol merged 2 commits into
mainfrom
site/0.21.0-blog
Nov 9, 2026
Merged

sdogruyol merged 2 commits into
mainfrom
site/0.21.0-blog

Conversation

@sdogruyol

Copy link
Copy Markdown
Collaborator

Re-records wasm, diagnostics, the agent loop, highlighting and the stdlib at v0.21.0 (08ce6c1cb), and adds /blog/ with the 0.21.0 announcement, an RSS feed at /blog/rss.xml, and a home-page link to the post for the current release.

Post quotations of the release notes are read from CHANGELOG.md at the release tag by scripts/notes.mjs; src/lib/posts.ts refuses a post for a release CHANGELOG.md does not state or dated before it.

Local: npm run build (all gates: prose, links, budget, no-transcription), npm run check (0 errors), bench/website_citations.py — green against IYI_REPO at v0.21.0.

A post is the one page on the site about a moment rather than about the tree
as it is. src/content/blog holds them; a post that names its release is
refused when CHANGELOG.md states no such release or the post predates it
(src/lib/posts.ts), and what it quotes of the release's notes
scripts/notes.mjs reads out of CHANGELOG.md at the release's tag, so a later
edit to the changelog does not move a sentence in an announcement.
ReleaseNote sets a quoted block with the lines it came from.

/blog/ lists the posts, /blog/<slug>/ is a BlogPosting with its
datePublished, /blog/rss.xml is built from the same list, and the masthead,
the breadcrumbs and llms.txt name the section. The home page links the post
that announces the current release, when there is one. The anchored headings
lessons used move to src/components so a post's prose gets them too.

New budget rows for /blog/ and /blog/*/, adopted from the measured build.
@sdogruyol
sdogruyol merged commit 1ab8014 into main Nov 9, 2026
2 checks passed
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