[Snyk] Security upgrade @google-cloud/datastore from 2.0.0 to 8.0.0 - #16
[Snyk] Security upgrade @google-cloud/datastore from 2.0.0 to 8.0.0#16philvarner-snyk wants to merge 1 commit into
Conversation
The following vulnerabilities are fixed with an upgrade: - https://snyk.io/vuln/SNYK-JS-NODEFORGE-15789771 - https://snyk.io/vuln/SNYK-JS-NODEFORGE-15789767 - https://snyk.io/vuln/SNYK-JS-NODEFORGE-15789769 - https://snyk.io/vuln/SNYK-JS-NODEFORGE-15789773 - https://snyk.io/vuln/SNYK-JS-BRACEEXPANSION-15789759
|
This is a very large upgrade, spanning 6 major versions from Key Breaking Changes:
Due to the extensive gap between versions, other undocumented API changes and behavioral modifications are highly likely. Source: Changelog Recommendation: Before merging, you must verify that your production environment runs a supported version of Node.js (18 or newer is recommended). A thorough review and testing of your application's integration with the Datastore client is essential to identify and address any other potential API or behavioral changes.
|
⛔ Snyk checks have failed. 1 issues have been found so far.
💻 Catch issues earlier using the plugins for VS Code, JetBrains IDEs, Visual Studio, and Eclipse. |
Snyk has created this PR to fix 5 vulnerabilities in the npm dependencies of this project.
Snyk changed the following file(s):
package.jsonVulnerabilities that will be fixed with an upgrade:
SNYK-JS-NODEFORGE-15789771
SNYK-JS-NODEFORGE-15789767
SNYK-JS-NODEFORGE-15789769
SNYK-JS-NODEFORGE-15789773
SNYK-JS-BRACEEXPANSION-15789759
Breaking Change Risk
Important
Note: You are seeing this because you or someone else with access to this repository has authorized Snyk to open fix PRs.
For more information:
🧐 View latest project report
📜 Customise PR templates
🛠 Adjust project settings
📚 Read about Snyk's upgrade logic
Learn how to fix vulnerabilities with free interactive lessons:
🦉 Improper Verification of Cryptographic Signature