fix(release): bump.mjs keeps ROADMAP's Now marker in sync#54
Merged
Conversation
Every auto-release bumped package.json/CHANGELOG/etc. but left ROADMAP.md's "## Now" version marker untouched, so `forge docs check`'s roadmap-freshness guard went stale after the very release that should have satisfied it — requiring a manual follow-up fix each time (as just happened twice, for v0.12.0 and v0.12.1). applyBump() now rewrites just that one line via the new bumpRoadmapNow(), leaving every other version mention in the doc alone. Also corrects the current drift: ROADMAP said v0.12.1, package.json is already v0.12.2, so `forge docs check` was failing on master.
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
scripts/bump.mjs'sapplyBump()bumpspackage.json,CHANGELOG.md,CITATION.cff, etc. on every release, but never touchedROADMAP.md's## Nowversion marker — soforge docs check's roadmap-freshness guard went stale immediately after the release that should have satisfied it. This caused the exact CI failures fixed in docs(research): formal synthesis paper unifying substrate + e2e framework #52/fix(pages): don't let empty Unreleased section blank the status page changelog #53 (twice, for v0.12.0 and v0.12.1).bumpRoadmapNow(roadmap, newVersion)helper that rewrites only the## Now (...)line's version, leaving every other version mention in the doc (e.g.v0.5.0under "Shipped") untouched. Wired intoapplyBump().v0.12.1,package.jsonis alreadyv0.12.2—forge docs checkwas failing on master before this fix.Test plan
node --test test/bump.test.js— 25/25 pass, including 2 new tests forbumpRoadmapNow(updates only the Now line; no-op when no Now heading) and updatedapplyBumpfixture assertions coveringROADMAP.mdnpm test— 659/660 pass (1 pre-existing unrelated flake, reproduces identically on master without this change)npx biome check— cleannpm run typecheck— cleannode src/cli.js docs check— clean (was failing before this change)🤖 Generated with Claude Code