Bump version of node-persist #201
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
bhamail
approved these changes
Jun 4, 2020
DarthHater
pushed a commit
that referenced
this pull request
Jun 4, 2020
## [4.0.18](v4.0.17...v4.0.18) (2020-06-04) ### Bug Fixes * Bump node-persist version ([#201](#201)) ([144e370](144e370))
|
🎉 This PR is included in version 4.0.18 🎉 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.
Thanks to: simonlast/node-persist#123 we can bump node-persist and get away from an upstream vulnerability in
minimistThis pull request makes the following changes:
3.1.0fornode-persistnpm i, audited with IQIt relates to the following issue #s:
cc @bhamail / @DarthHater / @allenhsieh / @ken-duck