Repository navigation
fix: Patch high-severity advisories in the blog CMS - #35
Conversation
The Strapi SDK pins several transitive dependencies to exact vulnerable versions, so a plain install cannot move them and Dependabot reports seven high alerts. Overrides re-resolve each one to its lowest patched version. Key features/changes: - Override undici 8.12.2, nodemailer 10.1.4, webpack-dev-middleware 7.4.6, @graphql-tools/utils 12.0.2 and zod to the project's own version - Hold zod at 3.25.76 under koa-body and koa-session, which crash on v4 - Raise the Node floor to 22.19.0, which undici 8 requires Carries the change first proposed in #29, rebuilt on main so the new CI build runs on it.
|
Detail for reviewers.
|
|
Warning Polylane could not verify the production impact of this pull request. Both files are dependency pins. The live CMS answers 200 and datum.net/blog still serves its articles; forced @graphql-tools/utils 12 keeps a CJS entry and exports every module v10 had. No CMS telemetry exists here: GCP lookups for cms/strapi workloads returned empty. Also considered · 5 refuted
Dependency changes
…and 1 more dependency change not shown. Analysed against 1 cloud account and 1 repository
Polylane could not find the cloud resources this repository manages, so this review looked at the entire cloud account. Connect this repository to its resources and the next review will focus on exactly what this code deploys to. Polylane analysed Rate this review: 👍 helpful · 👎 not helpful · 😕 confusing |
The blog CMS has 10 open high-severity Dependabot alerts, and this clears 9 of them. High-severity
npm auditfindings drop from 33 to 10, and every one left traces to the zod v3 copy that koa-session and koa-body need until upstream supports zod v4.Supersedes #29, rebuilt on main so the CI build from #32 runs on it.
Test plan
npm auditreports 10 high and 0 critical, down from 33 high on main