fix: upgrade package-lock.json #136
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
|
btw, I used a "fix" commit in order to trigger a new patch level. I thought that would be good since Christian's previous change fixed some vulnerabilities. |
dpopp07
approved these changes
May 10, 2021
ibm-devx-sdk
pushed a commit
that referenced
this pull request
May 10, 2021
## [2.10.4](v2.10.3...v2.10.4) (2021-05-10) ### Bug Fixes * upgrade package-lock.json ([#136](#136)) ([1780894](1780894))
|
🎉 This PR is included in version 2.10.4 🎉 The release is available on: Your semantic-release bot 📦🚀 |
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.
This PR updates package-lock.json back to v2 (npm v7.x). Otherwise, there shouldn't be any actual changes to dependency versions. An
npm auditrun in my local sandbox yielded 0 vulnerabilities (knock on wood!).