fix: repin js-yaml to 4.2.0 — 4.3.0 is gone from npm and breaks fresh installs#6131
Open
MuhammadFarhantahir wants to merge 1 commit into
Open
Conversation
npm install pm2 (7.0.2 / 7.0.3) fails with ETARGET because the exact-pinned js-yaml@4.3.0 no longer exists on the registry; the newest published version is 4.2.0, which is also the release GHSA-h67p-54hq-rp68 called for (Unitech#6122). Co-Authored-By: Claude Fable 5 <noreply@anthropic.com>
|
|
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
2 participants
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.
npm install pm2fails with ETARGET on 7.0.2/7.0.3 because the exact-pinnedjs-yaml@4.3.0no longer exists on the registry; the newest published version is 4.2.0, which is also the release GHSA-h67p-54hq-rp68 called for (#6122).Fixes #6130
🤖 Generated with Claude Code