Skip to content

Fix multipart runtime advisories - #5

Merged
LQ458 merged 1 commit into
mainfrom
fix/multer-runtime-advisories
Jul 23, 2026
Merged

Fix multipart runtime advisories#5
LQ458 merged 1 commit into
mainfrom
fix/multer-runtime-advisories

Conversation

@LQ458

@LQ458 LQ458 commented Jul 23, 2026

Copy link
Copy Markdown
Owner

Summary

  • upgrade Multer from the deprecated 1.x line to the patched 2.2.0 release
  • retain the existing storage, field, file-count, type, and size constraints
  • update the dependency status and changelog with the verified runtime-advisory reason
  • normalize both npm lockfiles to the official npm registry

Verification

  • npm ci --registry=https://registry.npmjs.org
  • focused multipart/auth/media tests: 13 passed
  • npm run verify: 39 backend tests, 20 frontend tests, strict lint, and production build passed
  • root full and production audits: zero known advisories
  • client production audit: zero known advisories; the documented CRA development tree remains unchanged

Boundaries

  • no API, database, media, Nginx, or production-service changes
  • no deployment is included

@LQ458
LQ458 merged commit 89d51d4 into main Jul 23, 2026
2 checks passed
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant