[PR #1386] Bump svgo from 3.3.2 to 4.0.0 #1385

New issue

Open

opened 2026-03-03 14:43:26 +03:00 by kerem · 0 comments

kerem commented

2026-03-03 14:43:26 +03:00

Owner

📋 Pull Request Information

Original PR: https://github.com/lipis/flag-icons/pull/1386
Author: @dependabot[bot]
Created: 6/23/2025
Status: 🔄 Open

Base: main ← Head: dependabot/npm_and_yarn/svgo-4.0.0

📝 Commits (1)

c5f498a Bump svgo from 3.3.2 to 4.0.0

📊 Changes

2 files changed (+31 additions, -31 deletions)

View changed files

📝 package.json (+1 -1)
📝 yarn.lock (+30 -30)

📄 Description

Bumps svgo from 3.3.2 to 4.0.0.

Release notes

Sourced from svgo's releases.

v4.0.0

Illustration by Vukory

It's been just over a year since our first release candidate, but I believe we can now release SVGO v4.0.0 with confidence! Thank you to all contributors who tested our RC builds and reported issues back up, this really smoothed out the process.

We actually wanted to do the release sooner, but it was a challenge to find the right time to publish a major release, since that means setting time aside to support users through migrations, helping downstream projects migrate, being available to fix or document things that users found to have an unexpected impact by this release, etc. I appreciate everyone's patience, and now that this is done, we can hopefully increase the pace of development again and tackle that backlog of old bugs. ^-^'

Breaking Changes

Please refer to the Migration Guide from v3 to v4 for a more concise version! This section is more verbose as it delves into the motivation of changes too.

Dropped Support for Node.js v14

Node.js v14 is no longer supported by the Node.js team, including security support, since 30 April 2023. Node.js v16 is no longer supported either, but as some are still using it, we'll save dropping support for Node.js v16 for the next major release.

This allows us to update our dependencies to more recent versions and to access more modern Node.js APIs.

Node.js v14 may still work at the time of this release, but we'll no longer be testing against v14 from now on.

Default Plugins

Both removeViewBox and removeTitle have been disabled by default. Both have been major pain points for users and don't make sense to enable in most cases. Other libraries wrapping SVGO have also been disabling these plugins by default, such as Docusaurus and SVGR.

removeViewBox removes the scalability of SVGs.

removeTitle reduces accessibility, which preserving accessibility is more important than optimization.

If you would like either of these plugins enabled, you can do so by configuring it in the SVGO config, see the README for more context, however please read the warnings described in the documentation of the plugins first:
  export default {
    plugins: [
      'preset-default', // built-in plugins enabled by default
+     'removeViewBox',
+     'removeTitle',
    ],
  };
removeScriptElement → removeScripts

The removeScriptElement plugin has been renamed to removeScripts, to more accurately reflect what the plugin does. It does not only remove the <script> tag, but also event handlers and script URIs from links.

To migrate, amend your SVGO config to refer to removeScripts instead if you use that plugin.

... (truncated)

Commits

71e1f05 chore: prepare v4 stable release (#2143)
4078c13 chore: increment version to v4.0.0-rc.5 (#2142)
cb3eea8 fix(#2140): SVGO fails with ERR_UNSUPPORTED_ESM_URL_SCHEME on Windows (#2141)
2582096 chore(deps): bump streetsidesoftware/cspell-action from 6 to 7 (#2139)
e1252fa deps: drop yarn/releases directory (#2138)
feb9b5e fix(convertColors): use currentColor instead of currentcolor (#2137)
e645d71 performance: small optimization when parsing svgs (#2133)
26d059f fix: invoke mapNodesToParents lazily (#2132)
b761d1b feat: add editor namespace for Boxy SVG (#2008)
31328bc chore: add krita namespace to list of editor namespaces (#2131)
Additional commits viewable in compare view

Dependabot will resolve any conflicts with this PR as long as you don't alter it yourself. You can also trigger a rebase manually by commenting @dependabot rebase.

Dependabot commands and options

You can trigger Dependabot actions by commenting on this PR:

@dependabot rebase will rebase this PR
@dependabot recreate will recreate this PR, overwriting any edits that have been made to it
@dependabot merge will merge this PR after your CI passes on it
@dependabot squash and merge will squash and merge this PR after your CI passes on it
@dependabot cancel merge will cancel a previously requested merge and block automerging
@dependabot reopen will reopen this PR if it is closed
@dependabot close will close this PR and stop Dependabot recreating it. You can achieve the same result by closing it manually
@dependabot show <dependency name> ignore conditions will show all of the ignore conditions of the specified dependency
@dependabot ignore this major version will close this PR and stop Dependabot creating any more for this major version (unless you reopen the PR or upgrade to it yourself)
@dependabot ignore this minor version will close this PR and stop Dependabot creating any more for this minor version (unless you reopen the PR or upgrade to it yourself)
@dependabot ignore this dependency will close this PR and stop Dependabot creating any more for this dependency (unless you reopen the PR or upgrade to it yourself)

_{🔄 This issue represents a GitHub Pull Request. It cannot be merged through Gitea due to API limitations.}

## 📋 Pull Request Information **Original PR:** https://github.com/lipis/flag-icons/pull/1386 **Author:** [@dependabot[bot]](https://github.com/apps/dependabot) **Created:** 6/23/2025 **Status:** 🔄 Open **Base:** `main` ← **Head:** `dependabot/npm_and_yarn/svgo-4.0.0` --- ### 📝 Commits (1) - [`c5f498a`](https://github.com/lipis/flag-icons/commit/c5f498a87f69862ce92818cf24017a116d2979fe) Bump svgo from 3.3.2 to 4.0.0 ### 📊 Changes **2 files changed** (+31 additions, -31 deletions) <details> <summary>View changed files</summary> 📝 `package.json` (+1 -1) 📝 `yarn.lock` (+30 -30) </details> ### 📄 Description Bumps [svgo](https://github.com/svg/svgo) from 3.3.2 to 4.0.0. <details> <summary>Release notes</summary> <p><em>Sourced from <a href="https://github.com/svg/svgo/releases">svgo's releases</a>.</em></p> <blockquote> <h2>v4.0.0</h2> <p><img src="https://github.com/user-attachments/assets/cba49a60-dbcd-477a-8f37-bd08cfd574c3" alt="Banner celebrating the release of SVGO v4.0.0. Includes the SVGO mascot drawing on a chalkboard with the changes in default plugins. For example, removeViewBox was moved from default plugins to available plugins." /></p>  <p><em>Illustration by <a href="https://github.com/Vukory">Vukory</a></em></p>  <p>It's been just over a year since our first release candidate, but I believe we can now release SVGO v4.0.0 with confidence! Thank you to all contributors who tested our RC builds and reported issues back up, this really smoothed out the process.</p> <p>We actually wanted to do the release sooner, but it was a challenge to find the right time to publish a major release, since that means setting time aside to support users through migrations, helping downstream projects migrate, being available to fix or document things that users found to have an unexpected impact by this release, etc. I appreciate everyone's patience, and now that this is done, we can hopefully increase the pace of development again and tackle that backlog of old bugs. ^-^'</p> <h2>Breaking Changes</h2> <p>Please refer to the <a href="https://svgo.dev/docs/migrations/migration-from-v3-to-v4/">Migration Guide from v3 to v4</a> for a more concise version! This section is more verbose as it delves into the motivation of changes too.</p> <h3>Dropped Support for Node.js v14</h3> <p>Node.js v14 is no longer supported by the Node.js team, including security support, since 30 April 2023. Node.js v16 is no longer supported either, but as some are still using it, we'll save dropping support for Node.js v16 for the next major release.</p> <p>This allows us to update our dependencies to more recent versions and to access more modern Node.js APIs.</p> <p>Node.js v14 <em>may</em> still work at the time of this release, but we'll no longer be testing against v14 from now on.</p> <h3>Default Plugins</h3> <p>Both removeViewBox and removeTitle have been disabled by default. Both have been major pain points for users and don't make sense to enable in most cases. Other libraries wrapping SVGO have also been disabling these plugins by default, such as <a href="https://docusaurus.io/">Docusaurus</a> and <a href="https://react-svgr.com/">SVGR</a>.</p> <ul> <li>removeViewBox removes the scalability of SVGs.</li> <li>removeTitle reduces accessibility, which preserving accessibility is more important than optimization.</li> </ul> <p>If you would like either of these plugins enabled, you can do so by configuring it in the SVGO config, see the <a href="https://github.com/svg/svgo?tab=readme-ov-file#configuration">README</a> for more context, however please read the warnings described in the documentation of the plugins first:</p> <pre lang="diff"><code> export default { plugins: [ 'preset-default', // built-in plugins enabled by default + 'removeViewBox', + 'removeTitle', ], }; </code></pre> <h3>removeScriptElement → removeScripts</h3> <p>The removeScriptElement plugin has been renamed to removeScripts, to more accurately reflect what the plugin does. It does not only remove the <code><script></code> tag, but also event handlers and script URIs from links.</p> <p>To migrate, amend your SVGO config to refer to <code>removeScripts</code> instead if you use that plugin.</p>  </blockquote> <p>... (truncated)</p> </details> <details> <summary>Commits</summary> <ul> <li><a href="https://github.com/svg/svgo/commit/71e1f05a7efdb667ff61df53f621e8f3e48076fc"><code>71e1f05</code></a> chore: prepare v4 stable release (<a href="https://redirect.github.com/svg/svgo/issues/2143">#2143</a>)</li> <li><a href="https://github.com/svg/svgo/commit/4078c137836321131c223b95249914acbdc676a1"><code>4078c13</code></a> chore: increment version to v4.0.0-rc.5 (<a href="https://redirect.github.com/svg/svgo/issues/2142">#2142</a>)</li> <li><a href="https://github.com/svg/svgo/commit/cb3eea80ba5d7990dd25a1b7e4182367d85a65b9"><code>cb3eea8</code></a> fix(<a href="https://redirect.github.com/svg/svgo/issues/2140">#2140</a>): SVGO fails with ERR_UNSUPPORTED_ESM_URL_SCHEME on Windows (<a href="https://redirect.github.com/svg/svgo/issues/2141">#2141</a>)</li> <li><a href="https://github.com/svg/svgo/commit/25820964ad339b00d1fe57988985c206158bb4bf"><code>2582096</code></a> chore(deps): bump streetsidesoftware/cspell-action from 6 to 7 (<a href="https://redirect.github.com/svg/svgo/issues/2139">#2139</a>)</li> <li><a href="https://github.com/svg/svgo/commit/e1252fa4880627d27fd6f17d29efb07acbedfcac"><code>e1252fa</code></a> deps: drop yarn/releases directory (<a href="https://redirect.github.com/svg/svgo/issues/2138">#2138</a>)</li> <li><a href="https://github.com/svg/svgo/commit/feb9b5e0690d3d2ca4fed82030a39c934ea543b3"><code>feb9b5e</code></a> fix(convertColors): use currentColor instead of currentcolor (<a href="https://redirect.github.com/svg/svgo/issues/2137">#2137</a>)</li> <li><a href="https://github.com/svg/svgo/commit/e645d715d5dd96657ae5dc291975f6d674583105"><code>e645d71</code></a> performance: small optimization when parsing svgs (<a href="https://redirect.github.com/svg/svgo/issues/2133">#2133</a>)</li> <li><a href="https://github.com/svg/svgo/commit/26d059f3d7d50f520cedee8b1b38293a41f09bfe"><code>26d059f</code></a> fix: invoke mapNodesToParents lazily (<a href="https://redirect.github.com/svg/svgo/issues/2132">#2132</a>)</li> <li><a href="https://github.com/svg/svgo/commit/b761d1b0dbee292b30662879ea704d0d3f3de651"><code>b761d1b</code></a> feat: add editor namespace for Boxy SVG (<a href="https://redirect.github.com/svg/svgo/issues/2008">#2008</a>)</li> <li><a href="https://github.com/svg/svgo/commit/31328bc473d7cb2ec0c8179c864cbaf34f3c390a"><code>31328bc</code></a> chore: add krita namespace to list of editor namespaces (<a href="https://redirect.github.com/svg/svgo/issues/2131">#2131</a>)</li> <li>Additional commits viewable in <a href="https://github.com/svg/svgo/compare/v3.3.2...v4.0.0">compare view</a></li> </ul> </details> <br /> [![Dependabot compatibility score](https://dependabot-badges.githubapp.com/badges/compatibility_score?dependency-name=svgo&package-manager=npm_and_yarn&previous-version=3.3.2&new-version=4.0.0)](https://docs.github.com/en/github/managing-security-vulnerabilities/about-dependabot-security-updates#about-compatibility-scores) Dependabot will resolve any conflicts with this PR as long as you don't alter it yourself. You can also trigger a rebase manually by commenting `@dependabot rebase`. [//]: # (dependabot-automerge-start) [//]: # (dependabot-automerge-end) --- <details> <summary>Dependabot commands and options</summary> <br /> You can trigger Dependabot actions by commenting on this PR: - `@dependabot rebase` will rebase this PR - `@dependabot recreate` will recreate this PR, overwriting any edits that have been made to it - `@dependabot merge` will merge this PR after your CI passes on it - `@dependabot squash and merge` will squash and merge this PR after your CI passes on it - `@dependabot cancel merge` will cancel a previously requested merge and block automerging - `@dependabot reopen` will reopen this PR if it is closed - `@dependabot close` will close this PR and stop Dependabot recreating it. You can achieve the same result by closing it manually - `@dependabot show <dependency name> ignore conditions` will show all of the ignore conditions of the specified dependency - `@dependabot ignore this major version` will close this PR and stop Dependabot creating any more for this major version (unless you reopen the PR or upgrade to it yourself) - `@dependabot ignore this minor version` will close this PR and stop Dependabot creating any more for this minor version (unless you reopen the PR or upgrade to it yourself) - `@dependabot ignore this dependency` will close this PR and stop Dependabot creating any more for this dependency (unless you reopen the PR or upgrade to it yourself) </details> --- <sub>🔄 This issue represents a GitHub Pull Request. It cannot be merged through Gitea due to API limitations.</sub>