docs: prepare 0.2.0 release narrative#99
Merged
Conversation
Reframe the contract docs from the `0.1.x` beta line to the upcoming
`0.2.x` stable line ahead of cutting v0.2.0 as the first stable release.
- `RELEASE.md`: replace the inaccurate "original 0.1.0 release
established the baseline" claim (no `v0.1.0` tag, GitHub release, or
npm version ever existed) with an accurate statement that the `0.1.x`
beta line established the baseline and `0.2.0` is the first stable
cut on top of it.
- `ROADMAP.md`, `README.md`, `design/ARCHITECTURE.md`: substitute
`0.1.x` → `0.2.x` in the "current release line" narrative sentences.
Historical references (e.g. "pre-`0.1.0` release-readiness milestone"
on `design/ARCHITECTURE.md:43`) are left alone.
- `CHANGELOG.md`: add a Notes section to the Unreleased block
documenting that `protocolVersion` intentionally stays at `0.1.0` —
the upcoming release is additive over the `0.1.x` envelope contract
and does not change the public JSON shape; only the package version
moves to `0.2.0`.
The `[Unreleased]` header itself is intentionally not renamed to
`[v0.2.0] - <date>` in this PR. That rename belongs in the
release-prep commit so the Release Changelog workflow's
"does this version header already exist?" check sees a coherent state
across the version-bump.
`dogfood/CATALOG.md:27` ("Current release-signoff bundle for the
`0.1.0` bar.") is also intentionally not touched here; it should be
updated in the follow-up PR that adds the fresh `v0.2.0`-era
release-readiness dogfood bundle.
Change-Id: Iacd16a123d491b6fa87748c6aa405afe9a8318a1
Signed-off-by: Thomas Kosiewski <tk@coder.com>
This was referenced May 13, 2026
Merged
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
1 participant
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Summary
Reframes the contract docs from the
0.1.xbeta line to the upcoming0.2.xstable line ahead of cutting v0.2.0 as the first stable release.This is Step 1 of a multi-step v0.2.0 release-readiness sequence. It lands first so the version-bump PR (Step 3) is purely mechanical.
Why
0.2.0and not0.1.0?No
v0.1.0tag, GitHub release, or npm version has ever existed — the package shipped0.1.1-beta.0through0.1.1-beta.4directly, and npmlatestis still stuck at0.1.1-beta.2. Cutting0.2.0as the first stable sidesteps the "did 0.1.0 ever exist" mismatch and avoids version-going-backwards optics. Narrative becomes "0.1.x was the beta line; 0.2.0 is the first stable."Changes
RELEASE.md: replace the inaccurate "original0.1.0release established the baseline" sentence with an accurate statement that the0.1.xbeta line established the baseline and0.2.0is the first stable cut.ROADMAP.md,README.md,design/ARCHITECTURE.md:0.1.x→0.2.xin the "current release line" sentences. Historical references like "pre-0.1.0release-readiness milestone" are left alone.CHANGELOG.md: add a Notes section to the Unreleased block documenting thatprotocolVersionintentionally stays at0.1.0— the upcoming release is additive over the0.1.xenvelope contract and does not change the public JSON shape; only the package version moves to0.2.0.Intentionally not in this PR
[Unreleased]header rename to[v0.2.0] - <date>: reserved for the release-prep commit (Step 3) so the Release Changelog workflow's existing-header check sees a coherent state across the version-bump.dogfood/CATALOG.md:27("Current release-signoff bundle for the0.1.0bar."): belongs in the follow-up PR that adds the freshv0.2.0-era release-readiness dogfood bundle on supported Node. The existing week-9 bundle was captured on Node v22.19.0 withdoctor result.ok: false, so the catalog row will be repointed when the new bundle lands.docs/RELEASE-PROCESS.mdworked examples using0.1.1: illustrative and version-agnostic; deferred.Test plan
npm run format:check(oxfmt) — clean across 1149 filesRELEASE.mdlines 3-4🤖 Generated with Claude Code