Fix blocked Dependabot security updates - #338
Merged
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
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.
Dependabot security updates fail with
security_update_not_possiblefor js-yaml, SVGO, qs, and postcss-selector-parser. This updates the lockfile to patched releases and adds the resolutions needed to unblock the older transitive dependencies.@svgr/webpackto 6.5.1, compatible with the existing Webpack 5 setup, removing SVGO v1 and using SVGO 2.8.4.Validation: frozen offline Yarn install, lint, all 7 unit tests, production build, and prerendering passed. All 14 browser tests passed across runs; the SEO and UI specs required a retry with a longer command timeout and video disabled after a timeout and Chromium renderer crash. Browser tests used port 3187 because port 3000 was occupied.
Checked the updated lockfile against all 17 open GitHub alerts for these four packages: no installed versions remain in their affected ranges. This addresses those packages, not the repository's entire security-alert backlog. Existing js-yaml PR #327 targets 3.15.1 and is superseded by this update.