dependabot[bot] opened a new pull request, #5347:
URL: https://github.com/apache/linkis/pull/5347

   Bumps [svgo](https://github.com/svg/svgo) from 3.0.2 to 3.3.3.
   <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>v3.3.3</h2>
   <h2>What's Changed</h2>
   <h3>Dependencies</h3>
   <ul>
   <li>Migrates from our unsupported fork of sax (<a 
href="https://www.npmjs.com/package/@trysound/sax";><code>@​trysound/sax</code></a>)
 to the upstream version of sax (<a 
href="https://www.npmjs.com/package/sax";>sax</a>).</li>
   </ul>
   <h3>Bug Fixes</h3>
   <ul>
   <li>No longer throws error when encountering comments in DTD.</li>
   </ul>
   <h2>Metrics</h2>
   <p>Before and after of the browser bundle of each respective version:</p>
   <table>
   <thead>
   <tr>
   <th></th>
   <th>v3.3.2</th>
   <th>v3.3.3</th>
   <th>Delta</th>
   </tr>
   </thead>
   <tbody>
   <tr>
   <td>svgo.browser.js</td>
   <td>910.9 kB</td>
   <td>912.9 kB</td>
   <td>⬆️ 2 kB</td>
   </tr>
   </tbody>
   </table>
   <h2>Support</h2>
   <p>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.</p>
   <p>Consider reading our <a 
href="https://svgo.dev/docs/migrations/migration-from-v3-to-v4/";>Migration 
Guide from v3 to v4</a> which should ease the process.</p>
   <h2>v3.3.2</h2>
   <h2>Notice</h2>
   <p>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.</p>
   <p>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 <code>removeViewBox</code> by default.</p>
   <p>Before the v4.0.0 release, I'll put more focus on testing and use release 
candidates, just to make the release go smoothly! 👍🏽</p>
   <p>Sorry for the headache, and thank you for your patience.</p>
   <h2>v3.3.1</h2>
   <h2>Notice</h2>
   <p>SVGO v3.3.0, which was meant to migrate to ESM without breaking CJS 
support, unfortunately broke CJS projects. There was a mistake with exports, so 
the <code>loadConfig</code> function wasn't available in the CJS bundle and 
lead to issues for many users.</p>
   <p>Thanks to everyone who raised the issue, and to <a 
href="https://github.com/nuintun";><code>@​nuintun</code></a> who submitted a 
pull request to resolve it so quickly.</p>
   <p>I apologize for letting that breaking change through, and will aim to do 
better. Namely, by adding more tests to cover our exports, and any other public 
interface in general for each distribution of SVGO, so this doesn't happen 
again.</p>
   <p>SVGO v3.3.1 should resolve the issue for CJS projects, but if you 
encounter anything else, do let us know by opening an issue on GitHub.</p>
   <h2>v3.3.0</h2>
   <h2>Deprecated</h2>
   <!-- raw HTML omitted -->
   </blockquote>
   <p>... (truncated)</p>
   </details>
   <details>
   <summary>Commits</summary>
   <ul>
   <li><a 
href="https://github.com/svg/svgo/commit/bbab162534d89654ac51c30dd6e62d7163b48a5e";><code>bbab162</code></a>
 deps: upgrade to sax v1.5.0</li>
   <li><a 
href="https://github.com/svg/svgo/commit/c4dc2bee9756140ffc74c045fd864b4bb2525cf3";><code>c4dc2be</code></a>
 chore: increment version to v3.3.2</li>
   <li><a 
href="https://github.com/svg/svgo/commit/252b28c4bf20f3165f08529ea32d753a251b11be";><code>252b28c</code></a>
 chore: increment version to 3.2.0 (<a 
href="https://redirect.github.com/svg/svgo/issues/1919";>#1919</a>)</li>
   <li><a 
href="https://github.com/svg/svgo/commit/8644cf36e8839a3dc3c6a90f8eec62c25fbc68a6";><code>8644cf3</code></a>
 feat(convertPathData): convert c to q (<a 
href="https://redirect.github.com/svg/svgo/issues/1892";>#1892</a>)</li>
   <li><a 
href="https://github.com/svg/svgo/commit/2661dacc249958471d10cfb887eba3c87728ce3a";><code>2661dac</code></a>
 fix(convertTransform): fix scale and rotate on skew + refactors (<a 
href="https://redirect.github.com/svg/svgo/issues/1916";>#1916</a>)</li>
   <li><a 
href="https://github.com/svg/svgo/commit/f6a2ca20d6472cb0f2b18dadd626d6db092f8767";><code>f6a2ca2</code></a>
 chore: improve jest tests with more precise assertions (<a 
href="https://redirect.github.com/svg/svgo/issues/1912";>#1912</a>)</li>
   <li><a 
href="https://github.com/svg/svgo/commit/db05c5782a02b3c137800cb04098bb1ef5b552bf";><code>db05c57</code></a>
 chore: Use idiomatic Jest patterns to assert exceptions (<a 
href="https://redirect.github.com/svg/svgo/issues/1909";>#1909</a>)</li>
   <li><a 
href="https://github.com/svg/svgo/commit/433dcefd646edba35b015fc4f567077a79d1d8ee";><code>433dcef</code></a>
 refactor(convertPaths): clean up plugin (<a 
href="https://redirect.github.com/svg/svgo/issues/1913";>#1913</a>)</li>
   <li><a 
href="https://github.com/svg/svgo/commit/f238d6a213a499deed31895d7ebbf139eb9996c5";><code>f238d6a</code></a>
 feat(convertPathData): allow converting q to t in more cases (<a 
href="https://redirect.github.com/svg/svgo/issues/1889";>#1889</a>)</li>
   <li><a 
href="https://github.com/svg/svgo/commit/967d2f1e1452a7c0adf952a9d676416eb31680c9";><code>967d2f1</code></a>
 deps: update css-tree and clean ts-ignores (<a 
href="https://redirect.github.com/svg/svgo/issues/1911";>#1911</a>)</li>
   <li>Additional commits viewable in <a 
href="https://github.com/svg/svgo/compare/v3.0.2...v3.3.3";>compare view</a></li>
   </ul>
   </details>
   <details>
   <summary>Maintainer changes</summary>
   <p>This version was pushed to npm by <a 
href="https://www.npmjs.com/~sethiii";>sethiii</a>, a new releaser for svgo 
since your current version.</p>
   </details>
   <br />
   
   
   [![Dependabot compatibility 
score](https://dependabot-badges.githubapp.com/badges/compatibility_score?dependency-name=svgo&package-manager=npm_and_yarn&previous-version=3.0.2&new-version=3.3.3)](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 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)
   You can disable automated security fix PRs for this repo from the [Security 
Alerts page](https://github.com/apache/linkis/network/alerts).
   
   </details>


-- 
This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL above to go to the specific comment.

To unsubscribe, e-mail: [email protected]

For queries about this service, please contact Infrastructure at:
[email protected]


---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]

Reply via email to