Conversation
Resolves two Dependabot alerts published after the previous sweep, both dev-only and transitive: - js-yaml 4.3.0 -> 4.3.1 (high, GHSA-5p4m-2wfm-xmqj), via semantic-release -> cosmiconfig - postcss 8.5.19 -> 8.5.26 (moderate, GHSA-fxqj-rqcc-2cmp), via vitest -> vite Both patches fall inside the existing caret ranges and each package has a single major branch in the tree, so a bare-name resolution is enough — yarn expands it to `**/name` on its own.
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.
Closes the two Dependabot alerts that surfaced right after #15 was merged.
Both advisories were published after this repository's previous scan (3 and 6
August), so they are unrelated to that change — the rescan simply picked them
up. Both are
developmentscope and transitive.js-yamlsemantic-release -> cosmiconfigpostcssvitest -> viteBoth patches fall inside the existing caret ranges (
^4.1.0,^8.5.16) andeach package has exactly one major branch in the tree, so bare-name
resolutions suffice here — yarn expands those to
**/nameitself. Noper-path pinning was needed, unlike
undiciin #15.build:again rather thanfix:, to keep semantic-release from publishing arelease for a dev-dependency-only change.
Verification
yarn buildpasses.yarn test— 55 tests across 12 files, all passing.