heavy-duty/ceremony
7
0
Fork 2
Code Issues 1 Pull requests Projects Releases 8 Packages Wiki Activity Actions

README: point the two new anchors at the lines that carry the claim

Browse source 
version_is_dev's range started one line in, past the signature comment
that states the -dev-only rule; and the npm range stopped at L112,
before the npm pkg set / npm install --package-lock-only lines it was
cited for. L68-L76 and L114-L115.
This commit is contained in:
cndgrr 2026-08-04 21:40:41 +00:00
parent 052c8734b9
commit 05e977814f
1 changed files with 2 additions and 2 deletions
Show stats Download patch file Download diff file Expand all files Collapse all files

4
README.md
View file

@ -514,7 +514,7 @@ in this catalog whose remedy is a manual bump, not a re-run.
Two senses of *bare* meet here, and the gap between them is the **rc release
path** — the one door an operator actually walks through. decide calls a
version bare when it is not `-dev`
([version_is_dev](lib/version.sh#L69-L76) matches that suffix and nothing
([version_is_dev](lib/version.sh#L68-L76) matches that suffix and nothing
else), so row 6 admits a transition to `1.2.3-rc1`, and a labeled rc ceremony
is designed to ship ([lib/decide.sh](lib/decide.sh#L108-L110)).
`version_next_dev` means `^[0-9]+\.[0-9]+\.[0-9]+$`. An rc sits between the
@ -532,7 +532,7 @@ rows 1–2 send `-dev` to a no-op, and the tag door never bumps.
[L106](lib/version.sh#L106): the package-json backend needs npm to write —
`npm pkg set version=` plus a lockfile-only `npm install`
([L102–L112](lib/version.sh#L102-L112)), never `npm version`, which would tag
([L114–L115](lib/version.sh#L114-L115)), never `npm version`, which would tag
— and the runner has none. The read path fails the
same way one step earlier (`node is required…`, above), so a run reaching
*this* message got past the read — set up node/npm in the caller.