fix: update form-data lockfile resolution#1573
Conversation
|
Important Review skippedReview was skipped due to path filters ⛔ Files ignored due to path filters (1)
CodeRabbit blocks several paths by default. You can override this behavior by explicitly including those paths in the path filters. For example, including ⚙️ Run configurationConfiguration used: defaults Review profile: CHILL Plan: Pro Run ID: You can disable this status message by setting the Use the checkbox below for a quick retry:
✨ Finishing Touches🧪 Generate unit tests (beta)
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. Comment |
|
MERGE_SUMMARY Implemented dependency alert remediation for #1548. Summary:
Verification:
|
06d629a to
766428a
Compare
🔨 Build Complete - Ready for Testing!📦 Download Build Artifact (Recommended)Download the zip build, upload to WordPress and test:
🌐 Test in WordPress Playground (Very Experimental)Click the link below to instantly test this PR in your browser - no installation needed! Login credentials: |
🔨 Build Complete - Ready for Testing!📦 Download Build Artifact (Recommended)Download the zip build, upload to WordPress and test:
🌐 Test in WordPress Playground (Very Experimental)Click the link below to instantly test this PR in your browser - no installation needed! Login credentials: |
Summary
package-lock.jsonso the transitiveform-datapackage resolves to4.0.6.hasownmetadata required by the updatedform-datalockfile entry.Testing
node -e "const fs=require('fs'); const lock=JSON.parse(fs.readFileSync('package-lock.json','utf8')); const fd=lock.packages['node_modules/form-data']; console.log(JSON.stringify({version: fd && fd.version}, null, 2)); process.exit(fd && fd.version === '4.0.6' ? 0 : 1);"npm audit --jsonparsed withform-data=null(remaining audit findings are unrelated existing dependencies)git diff --checknpm run lint:js(fails on existing unrelated asset lint errors)npm run lint:css(fails on existing unrelatedassets/css/admin.cssdisabled-rule error)Resolves #1548