Skip to content

ci: bump release workflow to Node 24#5

Merged
stevensacks merged 2 commits intomainfrom
ci/node-24
Apr 27, 2026
Merged

ci: bump release workflow to Node 24#5
stevensacks merged 2 commits intomainfrom
ci/node-24

Conversation

@stevensacks
Copy link
Copy Markdown
Contributor

Summary

Switches the release workflow from Node 22 to Node 24 and removes the now-unnecessary npm self-upgrade step.

Why

Node 22.22.2's bundled npm 10 has a self-upgrade regression — even with `--force`, `npm install -g npm@latest` fails:

```
npm error code MODULE_NOT_FOUND
npm error Cannot find module 'promise-retry'
```

We need npm ≥11.5.1 for Trusted Publishing's OIDC token exchange. Node 24 ships npm 11+ as the default, no upgrade needed.

The package's runtime requirement (`engines.node: >=22.19.0`) is unaffected — tsup still emits with target `node22`, only the CI runtime is on a newer Node.

🤖 Generated with Claude Code

stevensacks and others added 2 commits April 27, 2026 23:07
Drops the npm self-upgrade step. Node 22.22.2's bundled npm 10 has a
self-upgrade regression (Cannot find module 'promise-retry' during
arborist rebuild) that prevents installing a Trusted-Publishing-capable
npm at runtime, even with --force. Node 24 ships npm 11+ natively
which already has the OIDC token exchange path.

Co-Authored-By: Claude Sonnet 4.6 <noreply@anthropic.com>
# Conflicts:
#	.github/workflows/release.yml
@stevensacks stevensacks merged commit 5309116 into main Apr 27, 2026
1 check passed
@stevensacks stevensacks deleted the ci/node-24 branch April 27, 2026 14:13
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