Repository navigation
docs: install with @testmuai/rook@latest; npm needs Node 20+ - #49
Merged
samyakLambda merged 1 commit intoOct 9, 2026
Merged
Conversation
Without a tag, npm installs the newest release whose engines admit the user's Node, so on Node 20 `npm install -g @testmuai/rook` kept users on 0.1.0 (AA-450). Spelling out @latest installs the current release on any Node. Since 0.1.7 the npm package runs on its bundled Node 24 and declares Node 20+, so the README's Node 22 floor for npm was stale. - README: npm install block uses @latest; npm needs Node.js 20 or newer. - samples/industry-agents: native-ci.md, the standalone-docs generator, and the eight demo native-ci.md files it generated. Co-Authored-By: Claude Opus 5.5 (1M context) <noreply@anthropic.com>
vaibhavarora27
requested review from
gauravBansal06 and
vipulkv
as code owners
October 9, 2026 08:19
samyakLambda
approved these changes
Oct 9, 2026
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
2 participants
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.
WHAT
Every user-facing npm install command in this repo now reads
npm install -g @testmuai/rook@latest, and the README says the npm route needs Node.js 20 or newer instead of 22. Fixes AA-450 (internal tracker).WHY
Without a version or tag, npm installs the newest release whose
enginesfield admits the Node running npm, not the newest release overall. Until 0.1.7, only@testmuai/rook@0.1.0declared Node>=20, so on Node 20npm install -g @testmuai/rooksilently kept users on 0.1.0. 0.1.7 fixed the package (it now declares>=20and runs on its bundled Node 24). Spelling out@latestin the docs installs the current release on any Node, now and if a future floor change ever hits the same npm behaviour.The README's "npm needs Node.js 22 or newer to install and launch" became untrue with 0.1.7, which installs on Node 20 and runs
rookon the bundled runtime.CHANGES
README.md
npm install -g @testmuai/rook→npm install -g @testmuai/rook@latest.samples/industry-agents
docs/native-ci.md: install command uses@latest.scripts/standalone-docs.mjs: the generated "Install the published CLI (…)" sentence uses@latest.demos/01–08/docs/native-ci.md: the same sentence, edited to match the generator exactly (all 8 compared line for line). Each file changes one line. I didn't regenerate the editions withbuild-standalone.mjs, since that rewrites whole demo folders.Not changed, deliberately
CHANGELOG.md: history; line 9 describes this fix itself.README.md:213: "rook-skillneeds Node.js 22+" is correct;@testmuai/rook-skilldeclares>=22.samples/industry-agents: those are the sample apps' own requirement, not rook's.scripts/test-skill-flags.sh: developer-only test hints..claude/,.agents/,skill-installer/skills/): they link toREADME.md#install, which this PR fixes.COMPATIBLE/DEPLOY
Fully backward compatible, no deploy steps: documentation and generated sample docs only, with no code or package changes.
@latestresolves to the same release the bare command gives on Node 22+. The npm package page picks up the README on the next CLI release, because the release workflow publishes this repo's README with the package.🤖 Generated with Claude Code