chore: update Node.js version to 24.0.0 across configuration files#1230
Merged
Conversation
|
|
The latest updates on your projects. Learn more about Vercel for GitHub.
|
Contributor
🧪 Storybook is successfully deployed!
|
Contributor
🏋️ Size limit report
Click here if you want to find out what is changed in this build |
…on hosted runners
Contributor
📦 NPM canary releaseDeployed canary version 0.0.0-canary-4c90a81. |
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
1 participant
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Note
Medium Risk
Bumps the required Node major for all contributors and CI, and changes npm publish behavior on release workflows—worth validating canary and release publishes once.
Overview
Raises the project’s Node baseline from 22 to 24 by pinning
.nvmrcto 24.18.0, settingpackage.jsonengines.nodeto>=24.0.0, and bumping@types/nodeto ^24.0.0 (lockfile refresh included).Contributor docs (
README.md,CONTRIBUTING.md,AGENTS.md) now state Node >= 24.0.0.In
.github/workflows/publish.yml, both canary and release jobs drop thenpm install -g npm@lateststep. Comments note Node 24 already ships npm 11.5.1+ for OIDC trusted publishing and that global npm upgrades can break the runner’s npm tree (e.g. missing sigstore). The verify step now also logsnode --version.Reviewed by Cursor Bugbot for commit 8122841. Bugbot is set up for automated code reviews on this repo. Configure here.