Repository navigation
chore(deps): refresh lockfile for open security alerts - #660
Merged
Merged
Conversation
Move one docs dependency and four transitive dependencies to the newest versions inside their existing ranges. No package.json changes.
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.
Six of the eight open Dependabot alerts have patched releases inside the ranges the dependent packages already allow, but
pnpm-lock.yamlstill pinned the vulnerable versions.This moves one docs dependency and four transitive dependencies to the newest versions inside their existing ranges, which clears those six alerts. Only
pnpm-lock.yamlchanges. #546 tracks the WASM allocator alert, and the last alert has no patched release.