Skip to content

Bump svgo, @svgr/webpack, gatsby and gatsby-plugin-sharp#237

Open
dependabot[bot] wants to merge 1 commit into
masterfrom
dependabot/npm_and_yarn/multi-0c170b9c6a
Open

Bump svgo, @svgr/webpack, gatsby and gatsby-plugin-sharp#237
dependabot[bot] wants to merge 1 commit into
masterfrom
dependabot/npm_and_yarn/multi-0c170b9c6a

Conversation

@dependabot

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

Copy link
Copy Markdown
Contributor

Bumps svgo to 3.3.4 and updates ancestor dependencies svgo, @svgr/webpack, gatsby and gatsby-plugin-sharp. These dependencies need to be updated together.

Updates svgo from 1.3.2 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
  • 72a2388 Merge commit from fork
  • bbab162 deps: upgrade to sax v1.5.0
  • c4dc2be chore: increment version to v3.3.2
  • 252b28c chore: increment version to 3.2.0 (#1919)
  • 8644cf3 feat(convertPathData): convert c to q (#1892)
  • 2661dac fix(convertTransform): fix scale and rotate on skew + refactors (#1916)
  • f6a2ca2 chore: improve jest tests with more precise assertions (#1912)
  • db05c57 chore: Use idiomatic Jest patterns to assert exceptions (#1909)
  • 433dcef refactor(convertPaths): clean up plugin (#1913)
  • f238d6a feat(convertPathData): allow converting q to t in more cases (#1889)
  • Additional commits viewable in compare view
Maintainer changes

This version was pushed to npm by sethiii, a new releaser for svgo since your current version.


Updates @svgr/webpack from 4.3.3 to 8.1.0

Release notes

Sourced from @​svgr/webpack's releases.

v8.1.0

Bug Fixes

  • cli: fix default dimensions, prettier & svgo (571d5c8)
  • config: prefer cli config over rc config (#845) (8b97248)
  • react-native: fix duplicate import (#894) (e612b6a)

Features

  • esm: add support for svgo.config.cjs (#879) (ae91e2e)

v8.0.1

Bug Fixes

v8.0.0

Bug Fixes

  • parseObject error causes website broken (05f2946)

Features

  • types: change SVGProps from import to import type (#853) (095f021)
  • add snake_case filename option (#857) (428b0c7)
  • make index template more flexible (#861) (003009c)

BREAKING CHANGES

  • index template now receives an array of objects containing both the created component path (path) and the original SVG path (originalPath)

v7.0.0

Features

... (truncated)

Changelog

Sourced from @​svgr/webpack's changelog.

8.1.0 (2023-08-15)

Bug Fixes

  • cli: fix default dimensions, prettier & svgo (571d5c8)
  • config: prefer cli config over rc config (#845) (8b97248)
  • react-native: fix duplicate import (#894) (e612b6a)

Features

  • esm: add support for svgo.config.cjs (#879) (ae91e2e)

8.0.1 (2023-05-09)

Bug Fixes

8.0.0 (2023-05-09)

Bug Fixes

  • parseObject error causes website broken (05f2946)

Features

  • add snake_case filename option (#857) (428b0c7)
  • make index template more flexible (#861) (003009c)
  • types: change SVGProps from import to import type (#853) (095f021)

BREAKING CHANGES

  • index template now receives an array of objects containing both the created component path (path) and the original SVG path (originalPath)

... (truncated)

Commits

Updates gatsby from 2.17.17 to 5.16.1

Release notes

Sourced from gatsby's releases.

gatsby@5.16.1

What's Changed

Full Changelog: https://github.com/gatsbyjs/gatsby/compare/gatsby@5.16.0...gatsby@5.16.1

gatsby@5.16.0

What's Changed

React 19

[!NOTE] 🔐 As of January 26 2026, none of the React 19 security vulnerabilities affect Gatsby.

🚀 React 19 is here!

React 19 is now officially supported by Gatsby and all gatsby- packages maintained by the Gatsby team.

This is not a breaking change. You can safely upgrade to this release while staying on React 18.

All packages' peer dependencies on react and react-dom have been extended from ^18.0.0 to ^18.0.0 || ^19.0.0.

All existing stable Gatsby functionality is intended to now work with React 19.

PR: gatsbyjs/gatsby#39306

Upgrade Guide

[!WARNING] Community plugins may not have been updated yet to support React 19, so please check their repository for the current status. All plugins managed by the Gatsby team (in the gatsbyjs/gatsby repository) have been updated.

To upgrade to React 19, first upgrade gatsby and all your dependencies that start with gatsby- to the latest version. (Check out this guide if you need help with that.)

[!TIP] If you use npm 7 or higher you’ll want to use the --legacy-peer-deps option. For example, if you use gatsby and gatsby-plugin-postcss:

npm install --legacy-peer-deps gatsby@latest gatsby-plugin-postcss@latest

Then, follow the React 19 upgrade guide. No other changes are required.

Please note:

... (truncated)

Commits
Maintainer changes

This version was pushed to npm by serhalp-netlify, a new releaser for gatsby since your current version.


Updates gatsby-plugin-sharp from 2.3.4 to 5.16.0

Release notes

Sourced from gatsby-plugin-sharp's releases.

gatsby@5.16.0

What's Changed

React 19

[!NOTE] 🔐 As of January 26 2026, none of the React 19 security vulnerabilities affect Gatsby.

🚀 React 19 is here!

React 19 is now officially supported by Gatsby and all gatsby- packages maintained by the Gatsby team.

This is not a breaking change. You can safely upgrade to this release while staying on React 18.

All packages' peer dependencies on react and react-dom have been extended from ^18.0.0 to ^18.0.0 || ^19.0.0.

All existing stable Gatsby functionality is intended to now work with React 19.

PR: gatsbyjs/gatsby#39306

Upgrade Guide

[!WARNING] Community plugins may not have been updated yet to support React 19, so please check their repository for the current status. All plugins managed by the Gatsby team (in the gatsbyjs/gatsby repository) have been updated.

To upgrade to React 19, first upgrade gatsby and all your dependencies that start with gatsby- to the latest version. (Check out this guide if you need help with that.)

[!TIP] If you use npm 7 or higher you’ll want to use the --legacy-peer-deps option. For example, if you use gatsby and gatsby-plugin-postcss:

npm install --legacy-peer-deps gatsby@latest gatsby-plugin-postcss@latest

Then, follow the React 19 upgrade guide. No other changes are required.

Please note:

  • Some new React 19 features may not be available yet via Gatsby.
  • Gatsby Partial Hydration, an experimental feature for three years now, is known to be incompatible with React 19 at this time. If you rely on this feature, do not upgrade to React 19.

New features

Gatsby now supports React 19's new root error callbacks.

... (truncated)

Changelog

Sourced from gatsby-plugin-sharp's changelog.

5.16.0 (2026-01-26)

🧾 Release notes

Bug Fixes

Other Changes

  • Revert "chore(release): Publish next pre-minor" (3539ec8)

5.15.0 (2025-08-27)

🧾 Release notes

Note: Version bump only for package gatsby-plugin-sharp

5.14.0 (2024-11-06)

🧾 Release notes

Bug Fixes

  • update dependency fs-extra to ^11.2.0 #38727 (cb33fe5)
  • update dependency async to ^3.2.5 for gatsby-plugin-sharp #38721 (a30811a)

5.13.1 (2024-01-23)

Note: Version bump only for package gatsby-plugin-sharp

5.13.0 (2023-12-18)

🧾 Release notes

Chores

5.12.3 (2023-10-26)

Note: Version bump only for package gatsby-plugin-sharp

5.12.2 (2023-10-20)

Note: Version bump only for package gatsby-plugin-sharp

5.12.1 (2023-10-09)

Chores

... (truncated)

Commits
  • 92d6c67 chore(release): Publish
  • 3539ec8 Revert "chore(release): Publish next pre-minor"
  • c355640 fix: use more explicit node.js version range (#39398)
  • aea34d8 chore(release): Publish next pre-minor
  • c03a920 chore(changelogs): update changelogs (#39364)
  • 32f2d1e chore(release): Publish next pre-minor
  • baa1b8e chore(release): Publish next
  • 17baffb chore(release): Publish next pre-minor
  • 5f44fcd chore(changelogs): update changelogs (#39156)
  • 2c75bc5 chore(changelogs): update changelogs (#38821)
  • Additional commits viewable in compare view
Maintainer changes

This version was pushed to npm by serhalp-netlify, a new releaser for gatsby-plugin-sharp since your current version.


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 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.

@dependabot
Bump svgo, @svgr/webpack, gatsby and gatsby-plugin-sharp
39f3de5 
Bumps [svgo](https://github.com/svg/svgo) to 3.3.4 and updates ancestor dependencies [svgo](https://github.com/svg/svgo), [@svgr/webpack](https://github.com/gregberge/svgr), [gatsby](https://github.com/gatsbyjs/gatsby) and [gatsby-plugin-sharp](https://github.com/gatsbyjs/gatsby/tree/HEAD/packages/gatsby-plugin-sharp). These dependencies need to be updated together.


Updates `svgo` from 1.3.2 to 3.3.4
- [Release notes](https://github.com/svg/svgo/releases)
- [Commits](svg/svgo@v1.3.2...v3.3.4)

Updates `@svgr/webpack` from 4.3.3 to 8.1.0
- [Release notes](https://github.com/gregberge/svgr/releases)
- [Changelog](https://github.com/gregberge/svgr/blob/main/CHANGELOG.md)
- [Commits](gregberge/svgr@v4.3.3...v8.1.0)

Updates `gatsby` from 2.17.17 to 5.16.1
- [Release notes](https://github.com/gatsbyjs/gatsby/releases)
- [Changelog](https://github.com/gatsbyjs/gatsby/blob/master/CHANGELOG.md)
- [Commits](https://github.com/gatsbyjs/gatsby/compare/gatsby@2.17.17...gatsby@5.16.1)

Updates `gatsby-plugin-sharp` from 2.3.4 to 5.16.0
- [Release notes](https://github.com/gatsbyjs/gatsby/releases)
- [Changelog](https://github.com/gatsbyjs/gatsby/blob/master/packages/gatsby-plugin-sharp/CHANGELOG.md)
- [Commits](https://github.com/gatsbyjs/gatsby/commits/gatsby-plugin-sharp@5.16.0/packages/gatsby-plugin-sharp)

---
updated-dependencies:
- dependency-name: svgo
  dependency-version: 3.3.4
  dependency-type: indirect
- dependency-name: "@svgr/webpack"
  dependency-version: 8.1.0
  dependency-type: direct:production
- dependency-name: gatsby
  dependency-version: 5.16.1
  dependency-type: direct:production
- dependency-name: gatsby-plugin-sharp
  dependency-version: 5.16.0
  dependency-type: direct:production
...

Signed-off-by: dependabot[bot] <support@github.com>
@dependabot dependabot Bot added dependencies Pull requests that update a dependency file javascript Pull requests that update javascript code labels Jul 24, 2026
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Reviewers

No reviews

Assignees

No one assigned

Labels

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

Projects

None yet

Milestone

No milestone

Development

Successfully merging this pull request may close these issues.

0 participants