fix(deps): update svgo to 4.0.2 - #17531
Open
danilloestrela wants to merge 5 commits into
Open
Conversation
🦋 Changeset detectedLatest commit: 56d3ca5 The changes in this PR will be included in the next version bump. This PR includes changesets to release 399 packages
Not sure what this means? Click here to learn what changesets are. Click here if you're a maintainer who wants to add another changeset to this PR |
danilloestrela
force-pushed
the
fix/svgo-4.0.2
branch
from
July 28, 2026 05:52
5396159 to
221a5c6
Compare
Author
|
Guys, updating on this regard. The test broke but it is green, not a problem with the code itself |
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.
Changes
Bumps
svgofrom^4.0.1to^4.0.2inpackages/astro, resolving GHSA-2p49-hgcm-8545 (high), which affectssvgo >=4.0.0 <4.0.2.The
^4.0.1range already allows the patched release, so this might look redundant. It isn't: a lockfile entry only gets re-resolved once it stops satisfying the range, so any project that already hassvgo@4.0.1written to its lockfile keeps installing the vulnerable version. Raising the minimum is what actually propagates the patch downstream. I ran into this on an Astro site wherebun auditstill reports the advisory viaastro › svgo@4.0.1on a current install.svgois only declared inpackages/astro/package.json, so that's the whole change.One thing worth knowing: the lockfile still resolves a second
svgo@4.0.1under@astrojs/netlify, viaipx. Nothing inpackages/astrocan reach that one, so it would have to be fixed upstream inipx.Testing
pnpm run buildis green (32/32), and the SVG tests pass:core-image-svg,svg-deduplicationandcontent-collection-tla-svg, 20/20.core-image-svg-in-islanddoes fail, but it already fails onmainwithout this patch, with the same number on both sides:got 1694 bytesagainst the 1500 byte budget. So it isn't caused by this bump. Flagging it in case it isn't already known.Docs
Not needed, no behavior change.