Skip to content

chore: require Node.js >=22 - #54

Merged
ThoughtProof merged 1 commit into
mainfrom
cursor/require-node-22-4d75
Oct 10, 2026
Merged

ThoughtProof merged 1 commit into
mainfrom
cursor/require-node-22-4d75

Conversation

@ThoughtProof

@ThoughtProof ThoughtProof commented Oct 10, 2026 •

Copy link
Copy Markdown
Owner

Summary

Declares Node.js >=22 for pot-cli 0.8.12 (unreleased). A lockfile-less install on Node 20 resolves better-sqlite3@^12.8.0 to 12.11.1, whose prebuilt binaries start at Node 22, so Node 20 falls back to node-gyp and fails without a toolchain. Node 20 is EOL.

  • package.json sets "engines": { "node": ">=22" }. @pot-sdk2/bridge stays at 1.2.0. The better-sqlite3 range stays ^12.8.0.
  • package-lock.json root entry updated with npm install --package-lock-only on Node 22.
  • Changelog note under the existing ## [0.8.12] - Unreleased heading.
  • README does not state a Node version requirement, so it is unchanged.
  • .github/workflows/package-smoke.yml already runs tests on Node 22. It is the only workflow.

No version bump, publish, or tag.

Test plan

  • Node 22.14.0: npm ci, npm run build, npm run test:package (2/2), npm run test:plan (337/337), npm run test:rv (20/20), npm run check:boundaries
  • Node 20.20.2: npm install of pot-cli-0.8.12.tgz emits EBADENGINE for pot-cli@0.8.12 (required: { node: '>=22' }, current: { node: 'v20.20.2', npm: '10.8.2' }). Warning only; install exit code 0.
Open in Web Open in Cursor 

better-sqlite3 prebuilt binaries are published only for Node >=22, and Node 20 is EOL.

Co-authored-by: Raul Jäger <raul@thoughtproof.ai>
@ThoughtProof
ThoughtProof marked this pull request as ready for review October 10, 2026 07:21
@ThoughtProof
ThoughtProof merged commit d438404 into main Oct 10, 2026
1 check passed
@ThoughtProof
ThoughtProof deleted the cursor/require-node-22-4d75 branch October 12, 2026 10:41
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants