[Snyk] Security upgrade cloudinary from 1.30.0 to 2.7.0#35
Conversation
The following vulnerabilities are fixed with an upgrade: - https://snyk.io/vuln/SNYK-JS-CLOUDINARY-10495740
There was a problem hiding this comment.
💡 Codex Review
Here are some automated review suggestions for this pull request.
ℹ️ About Codex in GitHub
Your team has set up Codex to review pull requests in this repo. Reviews are triggered when you
- Open a pull request for review
- Mark a draft as ready
- Comment "@codex review".
If Codex has suggestions, it will comment; otherwise it will react with 👍.
Codex can also answer questions or update the PR. Try commenting "@codex address that feedback".
| "cloudinary": "^2.7.0", | ||
| "compression": "^1.7.4", |
There was a problem hiding this comment.
Avoid breaking peer dependency tree
Bumping cloudinary to ^2.7.0 means the repo’s dependency tree no longer satisfies the peer dependency declared by multer-storage-cloudinary@4.0.0, which still requires cloudinary@^1.21.0 (see package-lock.json lines 739‑744). On npm 7+ this mismatch causes npm install to abort with ERESOLVE unable to resolve dependency tree, so the application can’t even be installed or built after this commit. Either keep cloudinary on a 1.x release or upgrade/remove multer-storage-cloudinary to a version that supports Cloudinary 2.x before making this change.
Useful? React with 👍 / 👎.
Snyk has created this PR to fix 1 vulnerabilities in the npm dependencies of this project.
Snyk changed the following file(s):
package.jsonpackage-lock.jsonVulnerabilities that will be fixed with an upgrade:
SNYK-JS-CLOUDINARY-10495740
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:
🦉 Learn about vulnerability in an interactive lesson of Snyk Learn.