fix: upgrade vulnerable direct dependencies - #6153
Merged
colinhacks merged 4 commits intoSep 12, 2026
Merged
Conversation
This branch was successfully deployed
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
2 participants
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.
This upgrades two high-severity direct dependencies identified by the CVE Lite dependency audit in PR #6152.
nextinpackages/docsis upgraded from 15.5.15 to 15.5.18, andvitein the root workspace is upgraded from 7.3.2 to 7.3.5. Both are the minimum safe versions confirmed by the OSV advisory database. The scan found 25 total findings across the lockfile; these two are the direct dependencies where a targeted upgrade is possible without touching transitive parent chains.All 339 test files and 3,811 tests pass after the upgrades. The pnpm lockfile is updated in the same commit.