Documentation
¶
Overview ¶
Command release-notes prints the CHANGELOG.md section for a tag, so a release carries the notes that were written for it rather than a generated list of commit subjects.
It is also the release preflight: it fails, before anything is published, when the section is missing, empty, or still says "unreleased". Dating the heading is the last edit before tagging, and this is what enforces it.
go run ./cmd-dev/release-notes v0.4.2 > notes.md
The tag may be given with or without the leading v. Sections look like `## 0.4.2 — 2026-08-12`; the version token is matched and the rest of the heading left free-form, so `— unreleased` is a valid intermediate state that this command rejects at release time.
The sibling vscode-infinite-pm repo does the same job in scripts/release-notes.ts; this is the Go rewrite of it, because ipm-tools has no Node toolchain.
Source Files