Conversation
all deps have upgraded to address the vulnerability https://security.snyk.io/vuln/SNYK-JS-SEMVER-3247795
jmsjtu
approved these changes
Aug 27, 2025
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.
Running
yarn install(before):Running
yarn install(after):We originally pinned semver to patch a vulnerability. That was a while ago, and all of our dependencies now used patched versions, so the pin is no longer necessary. And it makes
yarn installway less noisy! You can verify that this is safe by runningyarn auditand seeing that semver is not listed, or by runningyarn why semverand seeing that all installed versions are not vulnerable.Note that some of our dependencies still try to pull in a version of
http-cache-semanticsthat has a vulnerability, so we can't remove that pin. We can update the pin to the latest version, though. Just for fun.Details
Does this pull request introduce a breaking change?
Does this pull request introduce an observable change?
GUS work item