Update sqlite3 to v4.0.0 #56
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
[skip ci]
[skip ci]
|
I'm sorry that this took a long time to look at - I actually did not get a notification about it, I'll merge it in tonight |
|
published to npm! |
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.
There's a prototype pollution vulnerability in
[email protected]introduced through an obsolete version ofnode-pre-gypmore info on which can be found here: https://snyk.io/test/npm/sqlite3/3.1.13Updating to
[email protected]fixes this vulnerability: https://snyk.io/test/npm/sqlite3/4.0.0.As far as I've checked,
v4.0.0doesn't seem to introduce any breaking change that requires any changes tonode-sqlite. So, this PR shouldn't break any thing.I've bumped the version & updated the changelog as well, please verify them as well.