Skip to content

Set Node 24 floor for corbits-memory - #42

Merged
TheGreatAxios merged 2 commits into
mainfrom
cl-8539-set-node-24-floor-for-corbitsmemory
Sep 21, 2026
Merged

TheGreatAxios merged 2 commits into
mainfrom
cl-8539-set-node-24-floor-for-corbitsmemory

Conversation

@TheGreatAxios

Copy link
Copy Markdown
Contributor

Sets engines.node to >=24 (existing Bun >=1.2.0 floor untouched), adds a Node 24 CI job (setup-node matrix, tsc --noEmit, npm pack --dry-run), and states the Node 24 floor in README requirements. Verified: bun run typecheck, bun run test (481 pass), npm pack --dry-run. CL-8539.

@TheGreatAxios

Copy link
Copy Markdown
Contributor Author

Review

Verdict: approve with nits. MERGEABLE. CI: test plus new node (24) job both green. No prior reviews.

Does what CL-8539 asks: engines.node: ">=24", README “Requires Bun 1.2+ and Node 24+”, CI setup-node@24 → npm install → npx tsc --noEmit → npm pack --dry-run. It does not run tests under Node.

Should-fix (hygiene this diff introduced): the Node job has no lockfile (bun.lock only), so npm install --no-audit --no-fund can drift. tsconfig "types": ["bun"] means this is a Node-hosted typecheck of a Bun package, not a Node runtime proof. Fine vs the ticket; don’t over-read the badge.

Conflicts with #37 on README Requirements. Merge this first if both stay open, then rewrite #37’s Requirements so the Node floor survives.

Add engines.node >=24 alongside the existing Bun floor, cover Node 24 in CI, and state the floor in README. CL-8539.
Do not clobber the sidecar product line. engines.node >=24 is for Node-side
tooling; native Node does not load extensionless TypeScript source.
@TheGreatAxios
TheGreatAxios force-pushed the cl-8539-set-node-24-floor-for-corbitsmemory branch from c3b843c to dd4091b Compare September 21, 2026 01:26
@TheGreatAxios
TheGreatAxios merged commit a24e564 into main Sep 21, 2026
2 checks passed
@TheGreatAxios
TheGreatAxios deleted the cl-8539-set-node-24-floor-for-corbitsmemory branch September 21, 2026 04:17
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.

1 participant