Skip to content

Release 0.4.0; run CI on Node 22 - #12

Merged
lonetis merged 2 commits into
mainfrom
claude/zen-newton-l04mve
Nov 9, 2026
Merged

lonetis merged 2 commits into
mainfrom
claude/zen-newton-l04mve

Conversation

@lonetis

@lonetis lonetis commented Nov 9, 2026 •

Copy link
Copy Markdown
Owner

What

  1. Release 0.4.0. Bumps the version in package.json, package-lock.json, the exported version constant (src/index.ts) and the MCP server's reported version (src/mcpServer.ts). Merging this to main makes the Publish workflow release 0.4.0 to npm and GitHub Packages. It ships:
  2. CI on Node 22. .github/workflows/ci.yml moves from Node 20 to Node 22.

Why

  • 0.4.0 rather than 0.3.1: the default edit behaviour changes (see above), which calls for a minor bump in 0.x. Also, 0.3.1 was published and then unpublished on npm (it is in the registry's time map but not in versions), and npm never allows an unpublished version number to be reused, so publishing it would fail.
  • Node 22: vitest 5 (since Fix audited dependencies, keep cookie requests on the Overleaf origin, safer live tests #11) supports ^22.12.0 || ^24.0.0 || >=26.0.0. CI on Node 20 works today but is outside that range, and Node 20 is end-of-life. publish.yml already uses Node 24. The runtime floor in package.json (engines.node >= 20) is unchanged.

Tested

On Node 22.23: npm ci, npm run typecheck, npm run build, npm test → 114 passed, 25 skipped (live tests, no session). dist/index.js exports version 0.4.0; npm pack --dry-run → claudeleaf-0.4.0.tgz, 54 files.

Note: the Publish runs for the two merges just before this PR failed without starting their npm job (no logs). The cause is not visible through the API; check the run page if the release run fails the same way.

🤖 Generated with Claude Code

https://claude.ai/code/session_016k8nQbcXiTztFcEngHqwxs

vitest 5 (dev dependency since the audit upgrade) supports Node ^22.12 || ^24 || >=26;
CI was still on Node 20, which works today but is outside vitest's supported range
and past end-of-life.

Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
Claude-Session: https://claude.ai/code/session_016k8nQbcXiTztFcEngHqwxs
Releases what landed since 0.3.0:

- tracked changes: list a document's pending suggestions (SDK
  listTrackedChanges, CLI `changes`, MCP overleaf_list_tracked_changes),
  and refuse by default any edit that would touch one
  (TrackedChangeConflictError; override with overwriteTrackedChanges /
  --overwrite-tracked-changes) (#10)
- security: cookie-carrying REST requests stay on the Overleaf origin;
  @modelcontextprotocol/sdk ^1.32.2 and zod ^4, npm audit clean (#11)

A minor bump rather than 0.3.1: the default edit behaviour changes, and
0.3.1 was published and then unpublished on npm, so that number can
never be reused.

Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
Claude-Session: https://claude.ai/code/session_016k8nQbcXiTztFcEngHqwxs
@lonetis lonetis changed the title ci: run checks on Node 22 Release 0.4.0; run CI on Node 22 Nov 9, 2026
@lonetis
lonetis marked this pull request as ready for review November 9, 2026 18:33
@lonetis
lonetis merged commit 4f9e55a into main Nov 9, 2026
2 checks passed
@chatgpt-codex-connector

chatgpt-codex-connector Bot commented Nov 9, 2026 •

Copy link
Copy Markdown
Codex Review Summary: ✅ Completed

This comment shows the latest Codex review activity on this pull request.

Review Status Commit Review trigger
📝 Code Review ✅ Completed 2026-11-09T18:34:18.358008Z 3da9497 Draft marked ready
🔒 Security Review ✅ Completed 2026-11-09T18:35:11.448646Z 3da9497 Draft marked ready
ℹ️ About Codex in GitHub

Your team has set up Codex to review pull requests in this repo. Reviews are triggered when you

  • Open a pull request for review
  • Mark a draft as ready
  • Comment "@codex review" or "@codex security review".

Codex reacts with 👀 while any review is running, comments if it has suggestions, and reacts with 👍 once all reviews finish with no findings.

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