Repository navigation
fix: update vulnerable development dependencies - #65
Merged
Merged
Conversation
Bundle ReportBundle size has no change ✅ |
Codecov Report✅ All modified and coverable lines are covered by tests. 📢 Thoughts on this report? Let us know! |
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
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.
The development toolchain locks vulnerable versions of nine packages reported by Dependabot, including Vitest Browser Mode file-access bugs, PostCSS source map disclosure and Undici HTTP handling issues. Update their resolved versions and raise the existing Undici/PostCSS overrides so fresh installs use patched dependencies.
The current advisory floors are higher than those in the email digest. npm audit also reports additional vulnerabilities in the same packages, so the update covers those fixes too.
Align
@vitest/browser-playwrightand@vitest/coverage-v8at 4.1.11 to preserve their exact peer requirements. Refresh compatible transitive dependencies without adding packages or changing the library API, React peer range or application source.Validation:
pnpm install --frozen-lockfile,git diff --check,pnpm lintandpnpm format:check: passed.pnpm audit: 36 vulnerabilities before the update, 0 afterward. A separate lockfile version check covers every resolved copy of all nine affected packages.CI=true pnpm test:coverage:unit: 136 tests passed; 99.49% line coverage.CI=true pnpm test:storybook: 20 tests passed in Chromium.pnpm build,pnpm test:package-smoke,pnpm test:react-compat,pnpm test:react-compat:matrixandCI=true pnpm build:sb: passed, including React 16, 17, 18 and 19 smoke checks.from. Ordinary cache parsing, brace expansion and explicit/adjacent source maps still work.The focused reproductions cover representative advisories. Remaining version-based findings are verified through the complete lockfile check and audit rather than individual exploit reproductions. Dependabot will re-evaluate the default branch after merge.