fix(deps): resolve qs security advisory (VOI-KANEO-75) #210
No reviewers
Labels
No labels
bug
dependencies
duplicate
enhancement
help wanted
invalid
javascript
question
symphony
wontfix
No milestone
No project
No assignees
1 participant
Notifications
Due date
No due date set.
Dependencies
No dependencies set
Reference
backmeupplz/voicy!210
Loading…
Reference in a new issue
No description provided.
Delete branch "voi-kaneo-75-resolve-qs-advisory"
Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?
Summary
Dependency path and compatibility decision
Express 4.22.1 required qs ~6.14.0, which blocked Dependabot below the fixed 6.15.2 floor. Express 4.22.2 changes that upstream requirement to qs ~6.15.1 and keeps body-parser on the compatible 1.20.x line. The regenerated lockfile therefore selects qs 6.15.3 for every production path without a Yarn resolution or out-of-range override.
This deliberately stays on Express 4 rather than taking the Express 5 major migration. It preserves Voicy's current runtime baseline while using the smallest upstream-supported patch that admits the security fix. The route proof starts the real Voicy Express app and verifies the worker JSON/auth response and Stripe raw-body rejection behavior.
Validation
The Mongo-backed worker API proof was not run locally because the Docker daemon and local mongod are unavailable; the new no-DB compatibility proof covers the Express middleware and both mounted route groups.
Easypanel readiness
No environment or schema changes are required. The existing Nixpacks install/build commands will consume the reviewed frozen lockfile. After merge and Easypanel redeploy, production must be checked to confirm express 4.22.2 and qs 6.15.3 are installed before VOI-KANEO-75 can be completed.