Skip to content

Bump svgo from 3.2.0 to 3.3.4 - #6085

Open
dependabot[bot] wants to merge 1 commit into
developfrom
dependabot/npm_and_yarn/svgo-3.3.4
Open

Bump svgo from 3.2.0 to 3.3.4#6085
dependabot[bot] wants to merge 1 commit into
developfrom
dependabot/npm_and_yarn/svgo-3.3.4

Conversation

@dependabot

@dependabot dependabot Bot commented on behalf of github Jul 23, 2026

Copy link
Copy Markdown
Contributor

Bumps svgo from 3.2.0 to 3.3.4.

Release notes

Sourced from svgo's releases.

v3.3.4

What's Changed

Security

Support

SVGO v3 is not officially supported, please consider upgrading to SVGO v4 instead. We've backported this fix as there are security implications, but there is no commitment to do this for more complex changes in future.

Consider reading our Migration Guide from v3 to v4 which should ease the process.

v3.3.3

What's Changed

Dependencies

  • Migrates from our unsupported fork of sax (@​trysound/sax) to the upstream version of sax (sax).

Bug Fixes

  • No longer throws error when encountering comments in DTD.

Metrics

Before and after of the browser bundle of each respective version:

v3.3.2 v3.3.3 Delta
svgo.browser.js 910.9 kB 912.9 kB ⬆️ 2 kB

Support

SVGO v3 is not officially supported, please consider upgrading to SVGO v4 instead. We've backported this fix as there are security implications, but there is no commitment to do this for more complex changes in future.

Consider reading our Migration Guide from v3 to v4 which should ease the process.

v3.3.2

Notice

An update on what happened with v3.3.0 and v3.3.1. While we have retained CJS support, the migration to ESM has changed the acceptable ways to import SVGO, in ways that users depended on before. This effectively made SVGO v3 a breaking change.

Rather than resolve or workaround these differences, we've opted to release SVGO v3.3.2, which is effectively a revert to v3.2.0, and deprecate versions v3.3.0 and v3.3.1. We'll then proceed to work on releasing v4 which will document the breaking changes, and feature further breaking changes that were slated for v4, like disabling removeViewBox by default.

Before the v4.0.0 release, I'll put more focus on testing and use release candidates, just to make the release go smoothly! 👍🏽

Sorry for the headache, and thank you for your patience.

v3.3.1

... (truncated)

Commits


Note

Low Risk
Dev-only transitive dependency with no app code changes; the update is primarily security and parser dependency fixes for the SVG build pipeline.

Overview
Bumps the dev dependency svgo from 3.2.0 to 3.3.4 (lockfile only), pulled in through react-native-svg-transformer / @svgr/plugin-svgo for SVG optimization at build time.

The new release replaces the fork @trysound/sax with upstream sax and includes security hardening in removeScriptElement (case-insensitive JavaScript URI handling and namespace-aware script handling). No application source changes.

Reviewed by Cursor Bugbot for commit 49a329f. Bugbot is set up for automated code reviews on this repo. Configure here.

@dependabot dependabot Bot added dependencies Pull requests that update a dependency file javascript Pull requests that update javascript code labels Jul 23, 2026
@dependabot
dependabot Bot force-pushed the dependabot/npm_and_yarn/svgo-3.3.4 branch 3 times, most recently from 04a34d9 to 32f22e3 Compare July 27, 2026 21:39
Bumps [svgo](https://github.com/svg/svgo) from 3.2.0 to 3.3.4.
- [Release notes](https://github.com/svg/svgo/releases)
- [Commits](svg/svgo@v3.2.0...v3.3.4)

---
updated-dependencies:
- dependency-name: svgo
  dependency-version: 3.3.4
  dependency-type: indirect
...

Signed-off-by: dependabot[bot] <support@github.com>
@dependabot
dependabot Bot force-pushed the dependabot/npm_and_yarn/svgo-3.3.4 branch from 32f22e3 to 49a329f Compare July 27, 2026 23:05
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

dependencies Pull requests that update a dependency file javascript Pull requests that update javascript code

Projects

None yet

Development

Successfully merging this pull request may close these issues.

0 participants