Skip to content

ci: bump release workflow to Node 24 #5

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Merged
stevensacks merged 2 commits into from
Apr 27, 2026
Merged

ci: bump release workflow to Node 24 #5

Changes from all commits
Commits
Show all changes
2 commits
Select commit Hold shift + click to select a range
535ea0f
ci: bump release workflow to Node 24 (ships npm 11+)
stevensacks Apr 27, 2026
b2c471c
Merge remote-tracking branch 'origin/main' into ci/node-24
stevensacks Apr 27, 2026
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
12 changes: 5 additions & 7 deletions .github/workflows/release.yml
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -27,16 +27,14 @@ jobs:

- uses: actions/setup-node@v4
with:
node-version: 22
# Node 24 ships npm 11+, which has the OIDC token exchange
# required for npm Trusted Publishing. Node 22 ships npm 10
# and that bundled npm has a self-upgrade regression that
# prevents installing a newer npm at runtime.
node-version: 24
cache: pnpm
registry-url: https://registry.npmjs.org

- name: Upgrade npm to a Trusted-Publishing-capable version (>=11.5.1)
# `--force` avoids the well-known MODULE_NOT_FOUND from npm's
# self-upgrade rebuild step (e.g. promise-retry) when modules
# unload mid-install.
run: npm install -g npm@latest --force

- run: pnpm install --frozen-lockfile

- run: pnpm typecheck
Expand Down
Loading