Freeze node/npm version to work around package-lock bug #335
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
|
Looks like |
|
@calvn I think it is due to |
swenson
force-pushed
the
fix-lock
branch
2 times, most recently
from
ee154cd
to
807d32a
Compare
Node 16.14.2 thinks the `package-lock.json` is out of sync when it is not. npm/cli#4660
swenson
changed the title
|
Okay, this should be good now. Tests will fail here though for some reason. |
calvn
approved these changes
Jun 15, 2022
|
Thanks! |
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.
Bug is here: npm/cli#4660
Tests passed here: https://github.com/hashicorp/vault-action/runs/6908644514