chore: bump deps and add overrides to address security alerts#165
Open
vredchenko wants to merge 1 commit intomainfrom
Open
chore: bump deps and add overrides to address security alerts#165vredchenko wants to merge 1 commit intomainfrom
vredchenko wants to merge 1 commit intomainfrom
Conversation
Resolves all 47 GitHub code scanning alerts on pnpm-lock.yaml. Direct devDep bumps: - @babel/core, preset-env/react/typescript -> 7.29.x - @storybook/* and storybook -> 8.6.18 - eslint -> 9.39.x - rollup -> 4.60.2 pnpm overrides for transitive dependencies that direct bumps cannot resolve: - postcss, vite, brace-expansion (1.x and 2.x), picomatch (2.x and 4.x), yaml (1.x and 2.x), flatted, minimatch (3.x and 9.x), rollup, ajv (6.x and 8.x), markdown-it, qs, js-yaml, @babel/runtime, @babel/helpers, webpack, esbuild, serialize-javascript, @tootallnate/once, uuid, svgo pnpm audit now reports no vulnerabilities. Build, type check, lint, tests (205 passing), and storybook build all succeed.
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
1 participant
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Summary
Resolves all 47 open GitHub code scanning alerts on
pnpm-lock.yamlforsci-react-ui. After these changespnpm auditreports no known vulnerabilities, and build, type check, lint, all 205 tests, and storybook build still succeed.Branched fresh off
main(separate from existing PR #141).What changed
Direct devDep bumps
@babel/core7.26.0 → 7.29.0@babel/preset-env7.26.0 → 7.29.2@babel/preset-react7.25.9 → 7.28.5@babel/preset-typescript7.26.0 → 7.28.5@storybook/*8.4.4 → 8.6.18 (fixes CVE-2026-27148, CVE-2025-68429 instorybookitself)eslint9.17.0 → 9.39.0 (pulls patched@eslint/plugin-kit)rollup4.27.3 → 4.60.2pnpm.overridesaddedFor transitive deps that cannot be reached via direct bumps:
^8.0.0^7.0.0^1.1.0,^2.0.0^2.0.0,^4.0.0^1.0.0,^2.0.0^3.0.0^3.0.0,^9.0.0^4.0.0^6.0.0,^8.0.0^14.0.0>=6.13.0 <6.14.0,^6.14.0^4.1.0^7.0.0^5.0.0>=0.24.0 <0.25.0^6.0.0^2.0.0^9.0.0^2.0.0The pre-existing
lodashoverride is kept.Test plan
pnpm installresolves cleanly (only pre-existing@mui/x-date-pickers/@jsonforms/material-rendererspeer warnings remain — unrelated to this PR)pnpm lint:tscpassespnpm lintpassespnpm buildsucceedspnpm test— 205 passing, 1 skipped (unchanged)pnpm storybook:buildsucceedspnpm auditreports no known vulnerabilities