This repository has been archived by the owner on Nov 13, 2023. It is now read-only.
Quick fix for an NPM regression/issue #838
Merged
Conversation
This file contains 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
Signed-off-by: Timothy Johnson <timothy.johnson@broadcom.com>
zFernand0
approved these changes
Jun 8, 2022
KevinLoesch1
approved these changes
Jun 8, 2022
Signed-off-by: Timothy Johnson <timothy.johnson@broadcom.com>
|
The issue was introduced in npm@8.11.0 and fixed in npm@8.12.1. On Windows, updating or downgrading the npm version isn't enough to fix the issue (see npm/cli#4989), so a better workaround for now seems to be locking down the Node.js versions. |
t1m0thyj
added
the
release-patch
github-actions
bot
removed
the
release-patch
|
Release succeeded for the The following packages have been published:
Powered by Octorelease 馃殌 |
Sign up for free
to subscribe to this conversation on GitHub.
Already have an account?
Sign in.
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.
Attempt 2 馃檪