chore: restore semantic-release in package-lock.json #652
Conversation
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
Member
Author
|
@aduh95 PTAL |
Member
Author
Actually, I'm going to go ahead and land this. In the hopefully-unlikely event that we want to revert, hey, it's git, we can do that. |
Member
Author
|
Looking at our GitHub Actions logs, we've been erroring out with EGITNOPERMISSION for a long time. |
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.
SHA1-Hulud makes me definitely not want to be responsible for failing to pin versions of semantic-release, etc. Updating package-lock.json might have extra annoying steps to keep
npm ciworking, but it is still possible. Like I did here.