Skip to content

Use Node 22 in publish workflow - #10

Merged
truongwp merged 2 commits into
masterfrom
fix-publish-node-version
Aug 10, 2026
Merged

truongwp merged 2 commits into
masterfrom
fix-publish-node-version

Conversation

@truongwp

Copy link
Copy Markdown
Collaborator

npm@latest is now 12.x, which requires Node >= 22.22.2. The publish workflow was pinned to Node 20 (npm 10.8.2), so the npm upgrade step failed with EBADENGINE and provenance could not be attached.

Aligns the publish workflow with ci.yml, which already uses Node 22.

truongwp and others added 2 commits August 11, 2026 02:26
npm@latest is now 12.x, which requires Node >= 22.22.2. The publish
workflow was pinned to Node 20 (npm 10.8.2), so the npm upgrade step
failed with EBADENGINE and provenance could not be attached.

Aligns the publish workflow with ci.yml, which already uses Node 22.

Co-Authored-By: Claude Opus 5 <noreply@anthropic.com>
The lockfile had drifted to 0.4.0 while package.json moved to 0.5.1.
Cosmetic only — npm ci does not validate the root version field and
the published version is read from package.json — but it keeps the
lockfile usable for tracing releases.

Co-Authored-By: Claude Opus 5 <noreply@anthropic.com>
@truongwp
truongwp merged commit 82940ef into master Aug 10, 2026
1 check passed
@truongwp
truongwp deleted the fix-publish-node-version branch August 10, 2026 19:30
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