ci(npm-publish): pin npm@11 due to sigstore packaging issue - #72
Merged
Conversation
damyanpetev
added
the
github_actions
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.
Latest Node 24-s ship with npm versions that satisfy the requirements for OIDC now:
However the Update step picked up 12.0.0 stable presumably and failed:
https://github.com/IgniteUI/igniteui-grid-lite/actions/runs/29032081040/job/86167229872#step:11:11
That seems to be related to npm/cli#9722
While the update step should be unnecessary atm, leaving in as a safety net, just in case a node 24 release picks it up before the above issue is fixed.