fix(deps): pin body-parser 2.4.0 and node-forge 1.4.3 #345
No reviewers
Labels
No labels
dependencies
major
security-pin
No milestone
No project
No assignees
1 participant
Notifications
Due date
No due date set.
Dependencies
No dependencies set
Reference
trails-cool/trails!345
Loading…
Reference in a new issue
No description provided.
Delete branch "security-pin-body-parser-node-forge"
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
Two security pins in
pnpm-workspace.yamloverrides, for findings on the Vulnerability Dashboard (#168):body-parser@react-router/serve>express>body-parsernode-forge@expo/cli>@expo/code-signing-certificatesBoth pins stay inside the range the consumer asks for (
express@5.3.0wants^2.3.0,@expo/code-signing-certificates@0.0.7wants^1.4.0), so neither moves a consumer onto a different API line. The old "NOT PINNED: node-forge … no patched release exists" comment is replaced, because fixes shipped (1.4.1 on 2026-10-27, 1.4.3 on 2026-11-04).Verification
body-parserandnode-forgeentries.pnpm audit: 26 findings (9 high) before → 4 after (0 high):deepmerge,esbuild,glob,minimatch.pnpm typecheck,pnpm lint,pnpm test: pass locally.pnpm test:e2e. CI's E2E and Journal Image Smoke Test exercise express with the newbody-parser.body-parseradvisory was in practice.Remaining on #168 after this
esbuild0.18.20: deliberately not pinned, documented inpnpm-workspace.yaml.glob,minimatch: the fixes are new majors (14.x, 11.x) that the jest and Sentry build tooling do not accept.Risk and rollback
body-parser2.4.0 is a minor release in the production request path; the risk is a behaviour change in body parsing. Revert the commit to roll back.pnpm-lock.yaml, socd-apps.ymldeploys journal and planner.🤖 Generated with Claude Code