Skip to content

chore(deps): bump socket.io, gatsby, gatsby-plugin-canonical-urls, gatsby-plugin-manifest, gatsby-plugin-offline, gatsby-plugin-react-helmet, gatsby-plugin-sitemap, gatsby-source-filesystem and gatsby-transformer-sharp#432

Open
dependabot[bot] wants to merge 1 commit into
mainfrom
dependabot/npm_and_yarn/multi-67127a15d3

Conversation

@dependabot

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

Copy link
Copy Markdown
Contributor

Bumps socket.io to 4.8.3 and updates ancestor dependencies socket.io, gatsby, gatsby-plugin-canonical-urls, gatsby-plugin-manifest, gatsby-plugin-offline, gatsby-plugin-react-helmet, gatsby-plugin-sitemap, gatsby-source-filesystem and gatsby-transformer-sharp. These dependencies need to be updated together.

Updates socket.io from 3.1.1 to 4.8.3

Release notes

Sourced from socket.io's releases.

socket.io@4.8.3

Bug Fixes

  • do not throw when calling io.close() on a stopped server (9581f9b)

Dependencies

socket.io-client@4.8.3

There were some minor bug fixes on the server side, which mandate a client bump.

Dependencies

socket.io-parser@3.4.4

This release includes a fix for CVE-2026-33151. Please upgrade as soon as possible.

Bug Fixes

  • add a limit to the number of binary attachments (719f9eb)

socket.io-parser@3.3.5

This release includes a fix for CVE-2026-33151. Please upgrade as soon as possible.

Bug Fixes

  • add a limit to the number of binary attachments (9d39f1f)

socket.io-parser@4.2.6

This release includes a fix for CVE-2026-33151. Please upgrade as soon as possible.

Bug Fixes

  • add a limit to the number of binary attachments (b25738c)

socket.io-parser@4.2.5

This release contains a bump of debug from ~4.3.1 to ~4.4.1.

socket.io@4.8.2

The url.parse() function is now deprecated and has been replaced by new URL() (see 8af7019).

Bug Fixes

  • call adapter.init() when creating each namespace (f3e1f5e)
  • improve io.close() function (#5344) (bb0b480)

... (truncated)

Commits
  • 9978574 chore(release): socket.io@4.8.3
  • e9e5bed chore(release): socket.io-client@4.8.3
  • 9581f9b fix(sio): do not throw when calling io.close() on a stopped server
  • 579d43f refactor: remove unused files
  • ee9aac3 chore(release): socket.io-parser@4.2.5
  • 968277c chore(release): socket.io-adapter@2.5.6
  • 2bf16bd chore(release): engine.io-client@6.6.4
  • ad61607 docs(eio): fix link in the release notes
  • dd71792 chore(release): socket.io@4.8.2
  • bb0b480 fix(sio): improve io.close() function (#5344)
  • Additional commits viewable in compare view
Maintainer changes

This version was pushed to npm by GitHub Actions, a new releaser for socket.io since your current version.


Updates gatsby from 2.32.13 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-canonical-urls from 2.10.0 to 5.16.0

Release notes

Sourced from gatsby-plugin-canonical-urls'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-canonical-urls'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-canonical-urls

5.14.0 (2024-11-06)

🧾 Release notes

Note: Version bump only for package gatsby-plugin-canonical-urls

5.13.1 (2024-01-23)

Note: Version bump only for package gatsby-plugin-canonical-urls

5.13.0 (2023-12-18)

🧾 Release notes

Note: Version bump only for package gatsby-plugin-canonical-urls

5.12.0 (2023-08-24)

🧾 Release notes

Note: Version bump only for package gatsby-plugin-canonical-urls

5.11.0 (2023-06-15)

🧾 Release notes

Note: Version bump only for package gatsby-plugin-canonical-urls

5.10.0 (2023-05-16)

🧾 Release notes

... (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
  • 17baffb chore(release): Publish next pre-minor
  • 5f44fcd chore(changelogs): update changelogs (#39156)
  • 2c75bc5 chore(changelogs): update changelogs (#38821)
  • 94b2482 chore(release): Publish next
  • Additional commits viewable in compare view
Maintainer changes

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


Updates gatsby-plugin-manifest from 2.12.1 to 5.16.0

Release notes

Sourced from gatsby-plugin-manifest'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-manifest'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-manifest

5.14.0 (2024-11-06)

🧾 Release notes

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

5.13.1 (2024-01-23)

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

5.13.0 (2023-12-18)

🧾 Release notes

Chores

5.12.3 (2023-10-26)

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

5.12.2 (2023-10-20)

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

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
  • 17baffb chore(release): Publish next pre-minor
  • 5f44fcd chore(changelogs): update changelogs (#39156)
  • 2c75bc5 chore(changelogs): update changelogs (#38821)
  • 94b2482 chore(release): Publish next
  • Additional commits viewable in compare view
Maintainer changes

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


Updates gatsby-plugin-offline from 3.10.2 to 6.16.0

Release notes

Sourced from gatsby-plugin-offline's releases.

gatsby-source-wordpress@7.13.5 and 6 more...

2024-08-26

Updated packages

  • gatsby-source-wordpress@7.13.5
  • gatsby-remark-responsive-iframe@6.13.2
  • gatsby-remark-prismjs@7.13.2
  • gatsby-remark-images@7.13.2
  • gatsby-remark-images@6.13.2
  • gatsby-remark-graphviz@5.13.2
  • gatsby-remark-copy-linked-files@6.13.2
  • gatsby-plugin-offline@6.13.3

What's Changed

See full release notes: gatsbyjs/gatsby#39070

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

... (truncated)

Changelog

Sourced from gatsby-plugin-offline's changelog.

6.16.0 (2026-01-26)

🧾 Release notes

Features

Bug Fixes

Other Changes

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

6.15.0 (2025-08-27)

🧾 Release notes

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

6.14.0 (2024-11-06)

🧾 Release notes

Bug Fixes

6.13.3 (2024-08-26)

Bug Fixes

6.13.2 (2024-04-10)

Bug Fixes

6.13.1 (2024-01-23)

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

6.13.0 (2023-12-18)

🧾 Release notes

... (truncated)

Commits
Maintainer changes

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


Updates gatsby-plugin-react-helmet from 3.10.0 to 6.16.0

Release notes

Sourced from gatsby-plugin-react-helmet'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)

Changelog

Sourced from gatsby-plugin-react-helmet's changelog.

6.16.0 (2026-01-26)

🧾 Release notes

Bug Fixes

Other Changes

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

6.15.0 (2025-08-27)

🧾 Release notes

Note: Version bump only for package gatsby-plugin-react-helmet

6.14.0 (2024-11-06)

🧾 Release notes

Note: Version bump only for package gatsby-plugin-react-helmet

6.13.1 (2024-01-23)

Note: Version bump only for package gatsby-plugin-react-helmet

6.13.0 (2023-12-18)

🧾 Release notes

Note: Version bump only for package gatsby-plugin-react-helmet

6.12.0 (2023-08-24)

🧾 Release notes

Note: Version bump only for package gatsby-plugin-react-helmet

6.11.0 (2023-06-15)

🧾 Release notes

Note: Version bump only for package gatsby-plugin-react-helmet

6.10.0 (2023-05-16)

🧾 Release notes

... (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
  • 17baffb chore(release): Publish next pre-minor
  • 5f44fcd chore(changelogs): update changelogs (#39156)
  • 2c75bc5 chore(changelogs): update changelogs (#38821)
  • 94b2482 chore(release): Publish next
  • Additional commits viewable in compare view
Maintainer changes

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


Updates gatsby-plugin-sitemap from 2.12.0 to 6.16.0

Release notes

Sourced from gatsby-plugin-sitemap's releases.

gatsby-source-wordpress@7.13.5 and 6 more...

2024-08-26

Updated packages

  • gatsby-source-wordpress@7.13.5
  • gatsby-remark-responsive-iframe@6.13.2
  • gatsby-remark-prismjs@7.13.2
  • gatsby-remark-images@7.13.2
  • gatsby-remark-images@6.13.2
  • gatsby-remark-graphviz@5.13.2
  • gatsby-remark-copy-linked-files@6.13.2
  • gatsby-plugin-offline@6.13.3

What's Changed

See full release notes: gatsbyjs/gatsby#39070

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

... (truncated)

Changelog

Sourced from gatsby-plugin-sitemap's changelog.

6.16.0 (2026-01-26)

🧾 Release notes

Features

Bug Fixes

Other Changes

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

6.15.0 (2025-08-27)

🧾 Release notes

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

6.14.0 (2024-11-06)

🧾 Release notes

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

6.13.1 (2024-01-23)

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

6.13.0 (2023-12-18)

🧾 Release notes

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

6.12.3 (2023-10-26)

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

6.12.2 (2023-10-20)

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

6.12.1 (2023-10-09)

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

... (truncated)

Commits
Maintainer changes

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


Updates gatsby-source-filesystem from 2.11.1 to 5.16.0

Release notes

Sourced from gatsby-source-filesystem'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...
Description has been truncated

@dependabot dependabot Bot added dependencies javascript Pull requests that update javascript code labels Jul 16, 2026
@dependabot
dependabot Bot force-pushed the dependabot/npm_and_yarn/multi-67127a15d3 branch 3 times, most recently from d0f77cd to 5f18ef5 Compare July 16, 2026 15:53
@jimmyandrade jimmyandrade self-assigned this Jul 16, 2026
@jimmyandrade

Copy link
Copy Markdown
Member

Blocked in oldest-PR triage: this grouped bump includes Gatsby and multiple Gatsby plugins, so it is part of the same Gatsby major migration path as #421/#413. Not merging as an isolated dependency PR.

@dependabot
dependabot Bot force-pushed the dependabot/npm_and_yarn/multi-67127a15d3 branch 2 times, most recently from 503c79b to 3287d62 Compare July 16, 2026 16:20
@dependabot
dependabot Bot force-pushed the dependabot/npm_and_yarn/multi-67127a15d3 branch from 3287d62 to 6269a51 Compare July 16, 2026 16:32
…tsby-plugin-manifest, gatsby-plugin-offline, gatsby-plugin-react-helmet, gatsby-plugin-sitemap, gatsby-source-filesystem and gatsby-transformer-sharp

Bumps [socket.io](https://github.com/socketio/socket.io) to 4.8.3 and updates ancestor dependencies [socket.io](https://github.com/socketio/socket.io), [gatsby](https://github.com/gatsbyjs/gatsby), [gatsby-plugin-canonical-urls](https://github.com/gatsbyjs/gatsby/tree/HEAD/packages/gatsby-plugin-canonical-urls), [gatsby-plugin-manifest](https://github.com/gatsbyjs/gatsby/tree/HEAD/packages/gatsby-plugin-manifest), [gatsby-plugin-offline](https://github.com/gatsbyjs/gatsby/tree/HEAD/packages/gatsby-plugin-offline), [gatsby-plugin-react-helmet](https://github.com/gatsbyjs/gatsby/tree/HEAD/packages/gatsby-plugin-react-helmet), [gatsby-plugin-sitemap](https://github.com/gatsbyjs/gatsby/tree/HEAD/packages/gatsby-plugin-sitemap), [gatsby-source-filesystem](https://github.com/gatsbyjs/gatsby/tree/HEAD/packages/gatsby-source-filesystem) and [gatsby-transformer-sharp](https://github.com/gatsbyjs/gatsby/tree/HEAD/packages/gatsby-transformer-sharp). These dependencies need to be updated together.


Updates `socket.io` from 3.1.1 to 4.8.3
- [Release notes](https://github.com/socketio/socket.io/releases)
- [Changelog](https://github.com/socketio/socket.io/blob/main/CHANGELOG.md)
- [Commits](https://github.com/socketio/socket.io/compare/3.1.1...socket.io@4.8.3)

Updates `gatsby` from 2.32.13 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.32.13...gatsby@5.16.1)

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

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

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

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

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

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

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

---
updated-dependencies:
- dependency-name: gatsby
  dependency-version: 5.16.1
  dependency-type: direct:production
- dependency-name: gatsby-plugin-canonical-urls
  dependency-version: 5.16.0
  dependency-type: direct:production
- dependency-name: gatsby-plugin-manifest
  dependency-version: 5.16.0
  dependency-type: direct:production
- dependency-name: gatsby-plugin-offline
  dependency-version: 6.16.0
  dependency-type: direct:production
- dependency-name: gatsby-plugin-react-helmet
  dependency-version: 6.16.0
  dependency-type: direct:production
- dependency-name: gatsby-plugin-sitemap
  dependency-version: 6.16.0
  dependency-type: direct:production
- dependency-name: gatsby-source-filesystem
  dependency-version: 5.16.0
  dependency-type: direct:production
- dependency-name: gatsby-transformer-sharp
  dependency-version: 5.16.0
  dependency-type: direct:production
- dependency-name: socket.io
  dependency-version: 4.8.3
  dependency-type: indirect
...

Signed-off-by: dependabot[bot] <support@github.com>
@dependabot
dependabot Bot force-pushed the dependabot/npm_and_yarn/multi-67127a15d3 branch from 6269a51 to d53eea9 Compare July 16, 2026 17:00
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

blocked dependencies javascript Pull requests that update javascript code

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant