Bumps the npm_and_yarn group with 1 update in the / directory: [svgo](https://github.com/svg/svgo). Updates `svgo` from 3.3.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> </blockquote> </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>See full diff in <a href="https://github.com/svg/svgo/compare/v3.3.2...v3.3.3">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=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 <dependency name> major version` will close this group update PR and stop Dependabot creating any more for the specific dependency's major version (unless you unignore this specific dependency's major version or upgrade to it yourself) - `@dependabot ignore <dependency name> minor version` will close this group update PR and stop Dependabot creating any more for the specific dependency's minor version (unless you unignore this specific dependency's minor version or upgrade to it yourself) - `@dependabot ignore <dependency name>` will close this group update PR and stop Dependabot creating any more for the specific dependency (unless you unignore this specific dependency or upgrade to it yourself) - `@dependabot unignore <dependency name>` will remove all of the ignore conditions of the specified dependency - `@dependabot unignore <dependency name> <ignore condition>` will remove the ignore condition of the specified dependency and ignore conditions You can disable automated security fix PRs for this repo from the [Security Alerts page](https://github.com/SwissDataScienceCenter/renku-blog/network/alerts). </details> Signed-off-by: dependabot[bot] <support@github.com> Co-authored-by: dependabot[bot] <49699333+dependabot[bot]@users.noreply.github.com>