🚨 [security] Update mysql2 2.3.3 → 3.10.0 (major) #109
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
![depfu[bot]](https://avatars.githubusercontent.com/in/715?s=60&v=4){kind=small}
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.
🚨 Your current dependencies have known security vulnerabilities 🚨
This dependency update fixes known security vulnerabilities. Please see the details below and assess their impact carefully. We recommend to merge and deploy this as soon as possible!
Here is everything you need to know about this upgrade. Please take a good look at what changed and the test results before merging this pull request.
What changed?
✳️ mysql2 (2.3.3 → 3.10.0) · Repo · Changelog
Security Advisories 🚨
🚨 mysql2 vulnerable to Prototype Pollution
🚨 MySQL2 for Node Arbitrary Code Injection
🚨 mysql2 Remote Code Execution (RCE) via the readCodeFor function
🚨 mysql2 cache poisoning vulnerability
🚨 mysql2 vulnerable to Prototype Poisoning
Release Notes
Too many releases to show here. View the full release notes.
Commits
See the full diff on Github. The new version differs by more commits than we can show here.
Release Notes
2.1.0 (from changelog)
Does any of this look wrong? Please let us know.
Commits
See the full diff on Github. The new version differs by 7 commits:
2.1.0chore: update changelogfix: issue where `clear()` is still keeping references to the elements (#47)refactor: performance optimizations for toArray and fromArray (#46)Additional benchmarks (#45)Bump node-fetch from 2.6.1 to 2.6.7 (#41)refactor: optimized growth and array copy (#43)Release Notes
5.2.3
5.2.2
5.2.1
5.2.0
5.1.0
5.0.1
5.0.0
Does any of this look wrong? Please let us know.
Commits
See the full diff on Github. The new version differs by 26 commits:
fix: Reorder module exports in package.json (#122)fix: Separate ESM/CJS TS definitions (#121)fix: Add `types` to `exports` in package.json (#111)feat: Add ctz and clz methods (#105)Fix link to releasesAdd more build instructionsFix README formattingAdd various instructionsIndicate that isPositive includes zero, fixes #100feat: Add an UMD fallback (#104)Move NaN/Infinity check below unsigned setup in fromStringfix: Always return matching signed/unsigned zeroes, fixes #72Switch to daily releasesMAJOR: Switch to ESM / modernizeDon't sign-extend unsigned input in fromInt(). (#94)README: high parameter in constructor is optionalAdd license headerImplement rotate left and right (#61)Update typescript definitions (#74)Fix link to wasm sources (#67)Make isLong a TypeScript type guard (#63)Add TypeScript typings (#60)Fix issues with closure-compiler in ADVANCED mode (#57)Rename wasm.wast to wasm.wat (#54)Mention WebAssembly in README, fixes #51Add npm badge🗑️ pseudomap (removed)
👉 No CI detected
You don't seem to have any Continuous Integration service set up!
Without a service that will test the Depfu branches and pull requests, we can't inform you if incoming updates actually work with your app. We think that this degrades the service we're trying to provide down to a point where it is more or less meaningless.
This is fine if you just want to give Depfu a quick try. If you want to really let Depfu help you keep your app up-to-date, we recommend setting up a CI system:
* [Circle CI](https://circleci.com), [Semaphore ](https://semaphoreci.com) and [Github Actions](https://docs.github.com/actions) are all excellent options. * If you use something like Jenkins, make sure that you're using the Github integration correctly so that it reports status data back to Github. * If you have already set up a CI for this repository, you might need to check your configuration. Make sure it will run on all new branches. If you don’t want it to run on every branch, you can whitelist branches starting with `depfu/`.Depfu will automatically keep this PR conflict-free, as long as you don't add any commits to this branch yourself. You can also trigger a rebase manually by commenting with
@depfu rebase.All Depfu comment commands
Go to the Depfu Dashboard to see the state of your dependencies and to customize how Depfu works.