Skip to content

Bump Node to 24 LTS so the release job's npm supports trusted publishing - #170

Merged
RodrigoHamuy merged 4 commits into
mainfrom
trusted-publishing-oidc
Jul 18, 2026
Merged

Bump Node to 24 LTS so the release job's npm supports trusted publishing#170
RodrigoHamuy merged 4 commits into
mainfrom
trusted-publishing-oidc

Conversation

@RodrigoHamuy

@RodrigoHamuyRodrigoHamuy commented Jul 18, 2026•
edited
Loading

Copy link
Copy Markdown
Owner

The release job fails with EBADENGINE (failing run): the npm install -g npm@latest step now resolves to npm 12, which doesn't support the Node 22.17.1 pinned in .nvmrc.

Instead of juggling npm versions in CI, bump .nvmrc to Node 24.18.0 (latest LTS), which bundles npm ≥ 11.5.1 — new enough for trusted publishing — and drop the global npm upgrade step from the release workflow entirely.

🤖 Generated with Claude Code

RodrigoHamuyand others added 2 commits July 18, 2026 12:16
@RodrigoHamuy
Migrate npm publishing to Trusted Publishing (OIDC)
66154e5
@RodrigoHamuy@claude
Pin npm upgrade to v11 in release workflow
a135757
npm@latest is now npm 12, which requires Node >= 22.22.2 and fails
EBADENGINE on the Node 22.17.1 pinned in .nvmrc. npm 11 supports
trusted publishing (>= 11.5.1) and runs on Node ^20.17.0 || >=22.9.0.
Co-Authored-By: Claude Fable 5 <noreply@anthropic.com>
@changeset-bot

changeset-botBot commented Jul 18, 2026•
edited
Loading

Copy link
Copy Markdown

⚠️ No Changeset found

Latest commit: fe296a0

Merging this PR will not cause a version bump for any packages. If these changes should not result in a new version, you're good to go. If these changes should result in a version bump, you need to add a changeset.

This PR includes no changesets

When changesets are added to this PR, you'll see the packages that this PR includes changesets for and the associated semver types

Click here to learn what changesets are, and how to add one.

Click here if you're a maintainer who wants to add a changeset to this PR

@codesandbox-ci

codesandbox-ciBot commented Jul 18, 2026•
edited
Loading

Copy link
Copy Markdown

This pull request is automatically built and testable in CodeSandbox.

To see build info of the built libraries, click here or the icon next to each commit SHA.

Latest deployment of this branch, based on commit fe296a0:

SandboxSource
example-mapboxConfiguration
example-maplibreConfiguration
storiesConfiguration

@RodrigoHamuy@claude
Use Node 24 LTS instead of upgrading npm in CI
3a860ce
Node 24.18.0 bundles npm >= 11.5.1, which is all trusted publishing
needs, so drop the global npm upgrade step from the release workflow.
Co-Authored-By: Claude Fable 5 <noreply@anthropic.com>
@RodrigoHamuyRodrigoHamuy changed the title Pin npm upgrade to v11 in release workflowBump Node to 24 LTS so the release job's npm supports trusted publishingJul 18, 2026
@RodrigoHamuy@claude
Merge origin/main, keeping Node 24 and no npm upgrade step
fe296a0
Co-Authored-By: Claude Fable 5 <noreply@anthropic.com>
@RodrigoHamuy
RodrigoHamuy merged commit 6e23328 into mainJul 18, 2026
3 checks passed
@RodrigoHamuy
RodrigoHamuy deleted the trusted-publishing-oidc branch July 18, 2026 11:43
Sign up for freeto join this conversation on GitHub. Already have an account? Sign in to comment

Reviewers

No reviews

Assignees

No one assigned

Labels

None yet

Projects

None yet

Milestone

No milestone

Development

Successfully merging this pull request may close these issues.

1 participant

@RodrigoHamuy