Repository navigation
ci: pin npm to v11 in release workflow - #185
Merged
Merged
Conversation
npm@latest is now v12, which errors (EUNKNOWNCONFIG) on unknown CLI flags. pnpm 10 delegates `pnpm publish` to the npm CLI and forwards `--git-checks`, so `changeset publish` failed to publish plist@5.0.1. npm 11 (>=11.5.1) still supports OIDC trusted publishing.
|
|
The latest updates on your projects. Learn more about Vercel for GitHub.
|
This branch was successfully deployed
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
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.
Problem
The Release run on
master(06a11b4, "Version Packages") failed to publishplist@5.0.1:The workflow installs
npm@latest, which is now npm 12, and npm 12 errors on unknown CLI flags.changeset publishrunspnpm publish, and pnpm 10 hands off to the npm CLI and passes--git-checksalong to it.Fix
Pin npm to v11. npm 11.5.1 and later still supports OIDC trusted publishing, which this workflow relies on.
After this merges, the push to
masterwill re-run Release, and 5.0.1 should publish because it still isn't on npm.