V0.41.1
Name:v0.41.1Status:complete

v0.41.1 — Readable release notes

The changelog on the site is now a list of short summaries, one per release, saying what each release is for. Every release has its own page with the specs and bugs behind it as drawers and the full list of changes (SPEC-176). This release also fixes plan validate --against, which missed an ID collision with anything main created after a branch split off (BUG-040), and plan create milestone, which named the file after the title instead of the version (BUG-041).

Not enough history yet — burndown needs at least one completed day of activity.

Progress 4/4 work items

Relationships

Related 7

Work Items

Done 4
WORK-641 main
The changelog generator merges handwritten release notes and collapses changeset detail
scripts/generate-changelog.mjs writes site/content/releases.md as one flat list of changeset bullets per version. This item gives the changelog the shape SPEC-176 describes: an index of summaries at /releases, and a page per release with drawers and the full list of changes (D4, revised while implementing this item).
high moderate
9/9 criteria
WORK-642 main
Every ref in a release note resolves to a plan entity
refrakt validate --deep passes a page containing {% ref "SPEC-99999" /%}. Only the site build reports it, as one "entity not found" warning among hundreds. A mistyped ID in a release note would therefore ship as a dead drawer.
medium simple
4/4 criteria
WORK-643 main
A command drafts a release note from the milestone
Handwritten notes tend to stop after a few releases unless writing one is close to free. This command writes everything but the opening sentences.
medium simple
6/6 criteria
WORK-644 main
Backfill release notes and review milestone fallbacks
Once the generator handles notes, the existing page needs content in the summary slot where the milestone fallback is missing or reads badly. See the migration table in SPEC-176.
medium simple
5/5 criteria