fix glob peer dependency vulnerability #3294
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
…At the time of this commit there weren't available updates to the core dependencies that rely on glob
pvighi
approved these changes
Nov 27, 2025
Contributor
|
looks ok to me in CODE |
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 does this change?
Forces an update to the peer dependency
glob, this is in order to fix the following vulnerability: https://github.com/guardian/gateway/security/dependabot/123Unfortunately at the time of creating this pr there weren't available updates to the core dependencies that rely on glob, so we had to make changes to the lock file (using
pnpm up glob) in order to force the glob version.