Repository navigation
fix(deps): update follow-redirects to 1.16.2 for GHSA-mrwp-f3q8-3g9p - #527
Merged
Merged
Conversation
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.
What
A lockfile-only update of
follow-redirectsfrom 1.16.1 to 1.16.2, a transitive production dependency. GHSA-mrwp-f3q8-3g9p (high) was published against 1.16.0 to 1.16.1, so thenpm audit --omit=dev --audit-level=highstep in CI now fails on every API PR, including #524, #525 and #526.Checks
npm audit --omit=dev --audit-level=high: exit 0 (two moderate findings remain inglobandminimatchunder dev tooling, below the gate)npm run typecheck,npm run lint: cleannpm run test:run: 2536 passedMerging this first lets the other open API PRs go green on a rerun.