Repository navigation
fix(deps): patch follow-redirects and seroval advisories - #83
Merged
Merged
Conversation
follow-redirects 1.16.1 is affected by GHSA-mrwp-f3q8-3g9p and seroval 1.6.8 by GHSA-9wx9-5pv9-3349 and GHSA-f86p-h4j2-7qgj. Both parents already allow the fixed versions, so only the lockfiles move.
🟢 Tier S · Ready to mergeUpdates the
📂 Walkthrough · 3
Reviewed |
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
Patches newly published advisories by moving lockfile entries only. No
package.jsonranges change.appwrite/package-lock.jsonfunctions/rejectProject/package-lock.jsonpackage-lock.jsonpackage-lock.jsonWhy these versions
follow-redirects comes in through axios (
^1.16.0), sonpm update follow-redirects --package-lock-onlywas enough in both subprojects.seroval comes in through the TanStack Start/Router packages (
^1.6.7). I stayed on the 1.6.x patch line at 1.6.12 instead of the 1.7.6 that a plain update picks. 1.7.6 is two days old, and 1.6.12 clears both advisories while respecting the repo's 7-day Dependabot cooldown.glob and minimatch do not appear in any lockfile in this repo, so nothing changes for them.
Verification
npm ciin the root,appwrite/andfunctions/rejectProject/: 0 vulnerabilities eachnpm run buildin the root passes