Say, in the changelog, what happens to it at 0.9.0
A note to whoever cuts the first public release, left where they will be looking rather than in a plan they may not have open: at 0.9.0 everything above the fold collapses into one entry saying "first public release" with the headline features under it. The reasoning, so it does not read as vandalism later: every version below 0.9.0 was released nowhere. Their entries are notes to ourselves about getting ready — a formatter pin, a runner label, a workflow that fired on the wrong branches. None of it is news to somebody arriving on launch day, and a changelog that opens with a fortnight of housekeeping buries the thing they came for. Co-Authored-By: Claude Opus 5 (1M context) <noreply@anthropic.com>
This commit is contained in:
1 parent
2ea8f9fb83
commit
8cc1cae213
1 file changed
+8
@@ -7,6 +7,14 @@ numbers follow [Semantic Versioning](https://semver.org/spec/v2.0.0.html) — wi
|
||||
SemVer itself makes for a leading zero: while the major version is `0`, a **minor** bump is
|
||||
allowed to change behaviour, not just add to it.
|
||||
|
||||
<!--
|
||||
At 0.9.0 — the first public release — everything below collapses into a single entry
|
||||
reading "first public release", with the headline features under it. Nobody arriving at
|
||||
a project on its launch day wants a changelog of the fortnight before it: the versions
|
||||
under 0.9.0 were never released anywhere, and their entries are notes to ourselves about
|
||||
getting ready. Keep the dates and the tags; replace the prose.
|
||||
-->
|
||||
|
||||
## [Unreleased]
|
||||
|
||||
## [0.2.1] — 2026-09-07
|
||||
|
||||
Reference in new issue
Block a user