chore(safe): upgrade form-data to 4.0+ to fix CVE-2023-50498 QA-237 - #2
chore(safe): upgrade form-data to 4.0+ to fix CVE-2023-50498 QA-237#2zzzboo wants to merge 1 commit into
Conversation
WalkthroughThe Changes
Estimated code review effort🎯 1 (Trivial) | ⏱️ ~2 minutes Poem
Note ⚡️ Unit Test Generation is now available in beta!Learn more here, or try it out under "Finishing Touches" below. ✨ Finishing Touches🧪 Generate unit tests
Thanks for using CodeRabbit! It's free for OSS, and your support helps us grow. If you like it, consider giving us a shout-out. 🪧 TipsChatThere are 3 ways to chat with CodeRabbit:
SupportNeed help? Create a ticket on our support page for assistance with any issues or questions. CodeRabbit Commands (Invoked using PR comments)
Other keywords and placeholders
CodeRabbit Configuration File (
|
There was a problem hiding this comment.
Actionable comments posted: 0
🧹 Nitpick comments (1)
vue/package.json (1)
39-42: Verify lock-file regeneration and minimum npm version foroverrides.Adding the root-level
overridesblock is the correct way to force-upgradeform-data, but two practical follow-ups are required:
- Regenerate & commit
package-lock.json(ornpm-shrinkwrap.json) so CI/CD and downstream consumers actually receiveform-data@^4.0.0. Without the updated lock-file, the vulnerable version may still be installed.- Ensure the toolchain runs on npm ≥ 8.3 (when
overridesgraduated from “experimental”). Otherwise the directive is silently ignored.
• Consider adding anenginesfield to enforce this:"private": true, + "engines": { + "npm": ">=8.3.0" + },Please confirm that both items are handled; otherwise the CVE fix may not propagate.
upgrade form-data to 4.0+ to fix CVE-2023-50498
Summary by CodeRabbit