chore(deps): override vulnerable js-yaml versions - #924
Merged
Conversation
frahlg
added
the
no-changeset
frahlg
marked this pull request as ready for review
August 16, 2026 12:28
Member
Author
|
@codex review |
|
Codex Review: Didn't find any major issues. Swish! Reviewed commit: ℹ️ About Codex in GitHubYour team has set up Codex to review pull requests in this repo. Reviews are triggered when you
If Codex has suggestions, it will comment; otherwise it will react with 👍. Codex can also answer questions or update the PR. Try commenting "@codex address that feedback". |
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
1 participant
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.
Pin both js-yaml lines used by Changesets to their fixed releases: 3.15.1 and 4.3.1. This is dev-only release tooling; FTW runtime has no npm production vulnerability. Before: npm audit reported 14 transitive findings, including one high. After: npm audit reports 0. Changesets status works, 339 web tests pass, and full make verify passes. This should carry the no-changeset label because it does not ship runtime behavior; #824 will regenerate its lockfile version hunk after merge.