chore(deps): security bumps - #4083
Conversation
…isories Pin patched versions via root Yarn resolutions for known GHSA/CVE fixes. Bump the @data-client/react qs test dependency into the patched 6.16 range. Co-authored-by: Nathaniel Tucker <me@ntucker.me>
|
|
The latest updates on your projects. Learn more about Vercel for GitHub. |
|
Size Change: 0 B Total Size: 81 kB ℹ️ View Unchanged
|
Codecov Report✅ All modified and coverable lines are covered by tests. Additional details and impacted files@@ Coverage Diff @@
## master #4083 +/- ##
=======================================
Coverage 97.84% 97.84%
=======================================
Files 156 156
Lines 3057 3057
Branches 612 612
=======================================
Hits 2991 2991
Misses 18 18
Partials 48 48 ☔ View full report in Codecov by Harness. 🚀 New features to boost your workflow:
|
In-range advisories (browserslist, js-yaml, nanoid, @humanfs/node) stay patched via the lockfile. qs still needs a resolution because express/body-parser request ~6.15.1. Co-authored-by: Nathaniel Tucker <me@ntucker.me>
|
Staff review — LGTM / FOLLOW_UP-only (no CHANGE_THIS_PR) Security-scoped, not a Renovate sweep. One justified new resolution ( FOLLOW_UP (after merge, not this PR): close Renovate #4079 ( Hold merge until Bugbot + CI are green. Squash when ready. |
Pins patched versions for known npm/GHSA advisories. This is a security-only bump — not a broad minor/patch Renovate sweep.
Supersedes #4079 (
qs6.15.3 → 6.16.0). Standalone example Dependabot PRs (todo-app/github-app/nextjs) are left alone; those apps are not yarn workspaces.Motivation
yarn npm audit --recursivereported several real GHSA/CVE findings in the workspace lockfile. Existing resolutions already covertar,serialize-javascript,dompurify,socks,uuid, andsigstore. This PR adds the remaining actionable patches that do not require a published-package major.Solution
Only one new root resolution:
qs(>=6.16.0). Express /body-parserrequestqs@~6.15.1, so Yarn will not take 6.16.0 from the lockfile alone.Everything else is an in-range lockfile pin (parent ranges already allow the patched release). No published runtime dependency majors. No changeset.
qsbrowserslistbaseline-browser-mapping@humanfs/nodejs-yamlnanoidBrowserslist 4.28.9 also refreshed its usual data deps (
caniuse-lite,electron-to-chromium,node-releases,update-browserslist-db).@humanfs/node0.16.8 pulled@humanfs/core0.19.2.Intentionally not bumped
decode-uri-component0.2.2 (viaquery-string@7/ React Navigation)0.5.0; forcing it would break CJSquery-string@7.image-size1.0.2 (via Metro 0.84)<=2.0.2, latest is 2.0.2). A community fork would force 2.x onto Metro 1.x.pacote15.2.0 (viarollup-plugin-filesize)>=21.5.1(major). Already have 21.5.1 elsewhere in the tree; forcing it on the v15 consumer is a breaking jump.Audit summary (workspace, after)
Actionable GHSA items above are cleared. Remaining
yarn npm audithits are the skipped packages plus deprecation warnings.Standalone examples (
todo-app,github-app,nextjs) keep their own npm lockfiles; Dependabot already has browserslist / fast-uri / postcss-selector-parser / svgo PRs for those.Testing
qs@6.16.0,js-yaml@4.3.2,nanoid@3.3.18,browserslist@4.28.9load successfullypackages/react(same resolved versions)