chore(release): use Node 24 instead of upgrading npm at runtime#43
Open
sdserranog wants to merge 1 commit into
Open
chore(release): use Node 24 instead of upgrading npm at runtime#43sdserranog wants to merge 1 commit into
sdserranog wants to merge 1 commit into
Conversation
Node 24 bundles npm >= 11.5.1, which supports OIDC trusted publishing natively, so the explicit 'npm install -g npm@latest' step is no longer needed. Simpler and faster.
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.
Follow-up cleanup to #41.
Node 24 bundles npm ≥ 11.5.1, which supports OIDC trusted publishing natively. So instead of installing npm at runtime (
npm install -g npm@latest, restored in #41), we just pinnode-version: 24and let the bundled npm handle the OIDC exchange. Simpler and a little faster — no global npm reinstall on every release.Behavior is unchanged; this only removes the workaround now that the Node version provides a new-enough npm.