Repository navigation
chore(deps): refresh vulnerable transitive dependencies in the lockfile - #5154
Merged
Merged
Conversation
|
Found potential problems with the pull request:
|
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.
Motivation
The repo has 170 open Dependabot alerts on
yarn.lock. All of them are in dev tooling, the example app and the docs site; none is in the published package. This refreshes vulnerable transitive packages to fixed releases inside their existing ranges, with nopackage.jsonchange.yarn npm auditgoes from 200 advisories (8 critical, 111 high) to 55 (2 critical, 22 high).Related issue
None.
Screenshots / Videos
None, a lockfile-only change.
Test plan
yarn lintyarn typecheckyarn test --maxWorkers=2yarn prepackyarn example expo export --platform allyarn --cwd docs build