Skip to content

build(deps): Bump socket.io, gatsby, gatsby-plugin-canonical-urls, gatsby-plugin-catch-links, gatsby-plugin-manifest, gatsby-plugin-offline, gatsby-plugin-react-helmet, gatsby-plugin-sass, gatsby-plugin-sharp, gatsby-plugin-sitemap, gatsby-plugin-typescript, gatsby-remark-autolink-headers, gatsby-remark-copy-linked-files, gatsby-remark-images, gatsby-remark-prismjs, gatsby-source-filesystem, gatsby-transformer-remark, gatsby-transformer-yaml and babel-plugin-remove-graphql-queries#7

Open
dependabot[bot] wants to merge 1 commit intomainfrom
dependabot/npm_and_yarn/multi-1f9169cff1
Open

Conversation

@dependabot
Copy link

@dependabot dependabot bot commented on behalf of github Sep 23, 2025

Bumps socket.io to 4.8.1 and updates ancestor dependencies socket.io, gatsby, gatsby-plugin-canonical-urls, gatsby-plugin-catch-links, gatsby-plugin-manifest, gatsby-plugin-offline, gatsby-plugin-react-helmet, gatsby-plugin-sass, gatsby-plugin-sharp, gatsby-plugin-sitemap, gatsby-plugin-typescript, gatsby-remark-autolink-headers, gatsby-remark-copy-linked-files, gatsby-remark-images, gatsby-remark-prismjs, gatsby-source-filesystem, gatsby-transformer-remark, gatsby-transformer-yaml and babel-plugin-remove-graphql-queries. These dependencies need to be updated together.

Updates socket.io from 3.1.1 to 4.8.1

Release notes

Sourced from socket.io's releases.

socket.io@4.8.1

Due to a change in the bundler configuration, the production bundle (socket.io.min.js) did not support sending and receiving binary data in version 4.8.0. This is now fixed.

Dependencies

socket.io-client@4.8.1

Bug Fixes

  • bundle: do not mangle the "_placeholder" attribute (ca9e994)

Dependencies

socket.io-client@4.8.0

Features

Custom transport implementations

The transports option now accepts an array of transport implementations:

import { io } from "socket.io-client";
import { XHR, WebSocket } from "engine.io-client";
const socket = io({
transports: [XHR, WebSocket]
});

Here is the list of provided implementations:

Transport Description
Fetch HTTP long-polling based on the built-in fetch() method.
NodeXHR HTTP long-polling based on the XMLHttpRequest object provided by the xmlhttprequest-ssl package.
XHR HTTP long-polling based on the built-in XMLHttpRequest object.
NodeWebSocket WebSocket transport based on the WebSocket object provided by the ws package.
WebSocket WebSocket transport based on the built-in WebSocket object.
WebTransport WebTransport transport based on the built-in WebTransport object.

Usage:

Transport browser Node.js Deno Bun

... (truncated)

Commits
  • 91e1c8b chore(release): socket.io@4.8.1
  • 8d5528a chore(release): socket.io-client@4.8.1
  • 71387e5 refactor(sio-client): reexport transports from the engine
  • aead835 refactor(sio): make Namespace._fns private (#5196)
  • 029e010 chore(release): engine.io-client@6.6.2
  • 4ca6ddb docs(nuxt): update example with latest version
  • ca9e994 fix(sio-client): do not mangle the "_placeholder" attribute
  • 4865f2e fix(eio-client): prevent infinite loop with Node.js built-in WebSocket
  • d4b3dde ci: use Node.js 22
  • 3b68658 chore: bump @​fails-components/webtransport to version 1.1.4 (dev)
  • Additional commits viewable in compare view

Updates gatsby from 3.14.6 to 5.15.0

Release notes

Sourced from gatsby's releases.

gatsby@5.15.0

What's Changed

Node.js 22

This release formally introduces Node.js 22 support, which is officially tested and supported going forward.

If you wish to use Node.js 22 with Gatsby, we highly recommend using the latest 22.x release, as there are known issues with some older 22.x versions that Gatsby is unable to work around at this time.

⚠️ Known Issue: gatsby develop fails with Node.js 22.7.0, 22.8.0, and 22.9.0

There is a critical bug in Node.js (nodejs/node#55145?) affecting versions 22.7.0, 22.8.0, and 22.9.0 that causes gatsby develop to fail with the error reported in gatsbyjs/gatsby#39068.

👉🏼 To avoid this, use Node.js 22.10.0 or later. (You can also use 22.6.0 or earlier.)

⚠️ Known Issue: Page loads may hang in dev with experimental DEV_SSR enabled and Node.js ≥22.14.0 (or ≥20.19.0)

This will not affect most users.

A change landed in Node.js 20.19.0 and 22.14.0 results in requests to the gatsby develop dev server to occasionally hang for 15 seconds. This can only occur if you have opted in to the experimental DEV_SSR flag.

👉🏼 To avoid this, disable the experimental DEV_SSR flag. (You can also downgrade to Node.js 22.13.1 or earlier, 20.18.3 or earlier, or 18.x.)

New Contributors

Thank you!

Full Changelog: https://github.com/gatsbyjs/gatsby/compare/gatsby@5.14.6...gatsby@5.15.0

gatsby@5.14.6

2025-08-06

What's Changed

  • fix: don't treat timestamps as dynamic paths (#39340) by @​gatsbybot in gatsbyjs/gatsby#39341
  • fix: use forked devcert to avoid pulling transitive deps from its @types/* deps (#39343) by @​gatsbybot in gatsbyjs/gatsby#39345
    • This fixes npm install errors/warnings with Node.js 18 that look like error glob@11.0.3: The engine "node" is incompatible with this module. Expected version "20 || >=22". Got "18.6.0"

Full Changelog: https://github.com/gatsbyjs/gatsby/compare/gatsby@5.14.5...gatsby@5.14.6

gatsby@5.14.5

2025-06-19

... (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 3.14.0 to 5.15.0

Release notes

Sourced from gatsby-plugin-canonical-urls's releases.

gatsby@5.15.0

What's Changed

Node.js 22

This release formally introduces Node.js 22 support, which is officially tested and supported going forward.

If you wish to use Node.js 22 with Gatsby, we highly recommend using the latest 22.x release, as there are known issues with some older 22.x versions that Gatsby is unable to work around at this time.

⚠️ Known Issue: gatsby develop fails with Node.js 22.7.0, 22.8.0, and 22.9.0

There is a critical bug in Node.js (nodejs/node#55145?) affecting versions 22.7.0, 22.8.0, and 22.9.0 that causes gatsby develop to fail with the error reported in gatsbyjs/gatsby#39068.

👉🏼 To avoid this, use Node.js 22.10.0 or later. (You can also use 22.6.0 or earlier.)

⚠️ Known Issue: Page loads may hang in dev with experimental DEV_SSR enabled and Node.js ≥22.14.0 (or ≥20.19.0)

This will not affect most users.

A change landed in Node.js 20.19.0 and 22.14.0 results in requests to the gatsby develop dev server to occasionally hang for 15 seconds. This can only occur if you have opted in to the experimental DEV_SSR flag.

👉🏼 To avoid this, disable the experimental DEV_SSR flag. (You can also downgrade to Node.js 22.13.1 or earlier, 20.18.3 or earlier, or 18.x.)

New Contributors

Thank you!

Full Changelog: https://github.com/gatsbyjs/gatsby/compare/gatsby@5.14.6...gatsby@5.15.0

gatsby@5.14.6

2025-08-06

What's Changed

  • fix: don't treat timestamps as dynamic paths (#39340) by @​gatsbybot in gatsbyjs/gatsby#39341
  • fix: use forked devcert to avoid pulling transitive deps from its @types/* deps (#39343) by @​gatsbybot in gatsbyjs/gatsby#39345
    • This fixes npm install errors/warnings with Node.js 18 that look like error glob@11.0.3: The engine "node" is incompatible with this module. Expected version "20 || >=22". Got "18.6.0"

Full Changelog: https://github.com/gatsbyjs/gatsby/compare/gatsby@5.14.5...gatsby@5.14.6

gatsby@5.14.5

2025-06-19

... (truncated)

Changelog

Sourced from gatsby-plugin-canonical-urls's changelog.

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

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

5.9.0 (2023-04-18)

🧾 Release notes

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

5.8.0 (2023-03-21)

🧾 Release notes

... (truncated)

Commits
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-catch-links from 3.14.0 to 5.15.0

Release notes

Sourced from gatsby-plugin-catch-links's releases.

gatsby@5.15.0

What's Changed

Node.js 22

This release formally introduces Node.js 22 support, which is officially tested and supported going forward.

If you wish to use Node.js 22 with Gatsby, we highly recommend using the latest 22.x release, as there are known issues with some older 22.x versions that Gatsby is unable to work around at this time.

⚠️ Known Issue: gatsby develop fails with Node.js 22.7.0, 22.8.0, and 22.9.0

There is a critical bug in Node.js (nodejs/node#55145?) affecting versions 22.7.0, 22.8.0, and 22.9.0 that causes gatsby develop to fail with the error reported in gatsbyjs/gatsby#39068.

👉🏼 To avoid this, use Node.js 22.10.0 or later. (You can also use 22.6.0 or earlier.)

⚠️ Known Issue: Page loads may hang in dev with experimental DEV_SSR enabled and Node.js ≥22.14.0 (or ≥20.19.0)

This will not affect most users.

A change landed in Node.js 20.19.0 and 22.14.0 results in requests to the gatsby develop dev server to occasionally hang for 15 seconds. This can only occur if you have opted in to the experimental DEV_SSR flag.

👉🏼 To avoid this, disable the experimental DEV_SSR flag. (You can also downgrade to Node.js 22.13.1 or earlier, 20.18.3 or earlier, or 18.x.)

New Contributors

Thank you!

Full Changelog: https://github.com/gatsbyjs/gatsby/compare/gatsby@5.14.6...gatsby@5.15.0

gatsby@5.14.6

2025-08-06

What's Changed

  • fix: don't treat timestamps as dynamic paths (#39340) by @​gatsbybot in gatsbyjs/gatsby#39341
  • fix: use forked devcert to avoid pulling transitive deps from its @types/* deps (#39343) by @​gatsbybot in gatsbyjs/gatsby#39345
    • This fixes npm install errors/warnings with Node.js 18 that look like error glob@11.0.3: The engine "node" is incompatible with this module. Expected version "20 || >=22". Got "18.6.0"

Full Changelog: https://github.com/gatsbyjs/gatsby/compare/gatsby@5.14.5...gatsby@5.14.6

gatsby@5.14.5

2025-06-19

... (truncated)

Changelog

Sourced from gatsby-plugin-catch-links's changelog.

5.15.0 (2025-08-27)

🧾 Release notes

Note: Version bump only for package gatsby-plugin-catch-links

5.14.0 (2024-11-06)

🧾 Release notes

Note: Version bump only for package gatsby-plugin-catch-links

5.13.1 (2024-01-23)

Note: Version bump only for package gatsby-plugin-catch-links

5.13.0 (2023-12-18)

🧾 Release notes

Note: Version bump only for package gatsby-plugin-catch-links

5.12.0 (2023-08-24)

🧾 Release notes

Note: Version bump only for package gatsby-plugin-catch-links

5.11.0 (2023-06-15)

🧾 Release notes

Note: Version bump only for package gatsby-plugin-catch-links

5.10.0 (2023-05-16)

🧾 Release notes

Note: Version bump only for package gatsby-plugin-catch-links

5.9.0 (2023-04-18)

🧾 Release notes

Note: Version bump only for package gatsby-plugin-catch-links

5.8.0 (2023-03-21)

🧾 Release notes

... (truncated)

Commits
Maintainer changes

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


Updates gatsby-plugin-manifest from 3.14.0 to 5.15.0

Release notes

Sourced from gatsby-plugin-manifest's releases.

gatsby@5.15.0

What's Changed

Node.js 22

This release formally introduces Node.js 22 support, which is officially tested and supported going forward.

If you wish to use Node.js 22 with Gatsby, we highly recommend using the latest 22.x release, as there are known issues with some older 22.x versions that Gatsby is unable to work around at this time.

⚠️ Known Issue: gatsby develop fails with Node.js 22.7.0, 22.8.0, and 22.9.0

There is a critical bug in Node.js (nodejs/node#55145?) affecting versions 22.7.0, 22.8.0, and 22.9.0 that causes gatsby develop to fail with the error reported in gatsbyjs/gatsby#39068.

👉🏼 To avoid this, use Node.js 22.10.0 or later. (You can also use 22.6.0 or earlier.)

⚠️ Known Issue: Page loads may hang in dev with experimental DEV_SSR enabled and Node.js ≥22.14.0 (or ≥20.19.0)

This will not affect most users.

A change landed in Node.js 20.19.0 and 22.14.0 results in requests to the gatsby develop dev server to occasionally hang for 15 seconds. This can only occur if you have opted in to the experimental DEV_SSR flag.

👉🏼 To avoid this, disable the experimental DEV_SSR flag. (You can also downgrade to Node.js 22.13.1 or earlier, 20.18.3 or earlier, or 18.x.)

New Contributors

Thank you!

Full Changelog: https://github.com/gatsbyjs/gatsby/compare/gatsby@5.14.6...gatsby@5.15.0

gatsby@5.14.6

2025-08-06

What's Changed

  • fix: don't treat timestamps as dynamic paths (#39340) by @​gatsbybot in gatsbyjs/gatsby#39341
  • fix: use forked devcert to avoid pulling transitive deps from its @types/* deps (#39343) by @​gatsbybot in gatsbyjs/gatsby#39345
    • This fixes npm install errors/warnings with Node.js 18 that look like error glob@11.0.3: The engine "node" is incompatible with this module. Expected version "20 || >=22". Got "18.6.0"

Full Changelog: https://github.com/gatsbyjs/gatsby/compare/gatsby@5.14.5...gatsby@5.14.6

gatsby@5.14.5

2025-06-19

... (truncated)

Changelog

Sourced from gatsby-plugin-manifest's changelog.

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

5.12.0 (2023-08-24)

🧾 Release notes

Bug Fixes

5.11.0 (2023-06-15)

🧾 Release notes

... (truncated)

Commits
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 4.14.0 to 6.15.0

Release notes

Sourced from gatsby-plugin-offline's releases.

gatsby@5.15.0

What's Changed

Node.js 22

This release formally introduces Node.js 22 support, which is officially tested and supported going forward.

If you wish to use Node.js 22 with Gatsby, we highly recommend using the latest 22.x release, as there are known issues with some older 22.x versions that Gatsby is unable to work around at this time.

⚠️ Known Issue: gatsby develop fails with Node.js 22.7.0, 22.8.0, and 22.9.0

There is a critical bug in Node.js (nodejs/node#55145?) affecting versions 22.7.0, 22.8.0, and 22.9.0 that causes gatsby develop to fail with the error reported in gatsbyjs/gatsby#39068.

👉🏼 To avoid this, use Node.js 22.10.0 or later. (You can also use 22.6.0 or earlier.)

⚠️ Known Issue: Page loads may hang in dev with experimental DEV_SSR enabled and Node.js ≥22.14.0 (or ≥20.19.0)

This will not affect most users.

A change landed in Node.js 20.19.0 and 22.14.0 results in requests to the gatsby develop dev server to occasionally hang for 15 seconds. This can only occur if you have opted in to the experimental DEV_SSR flag.

👉🏼 To avoid this, disable the experimental DEV_SSR flag. (You can also downgrade to Node.js 22.13.1 or earlier, 20.18.3 or earlier, or 18.x.)

New Contributors

Thank you!

Full Changelog: https://github.com/gatsbyjs/gatsby/compare/gatsby@5.14.6...gatsby@5.15.0

gatsby@5.14.6

2025-08-06

What's Changed

  • fix: don't treat timestamps as dynamic paths (#39340) by @​gatsbybot in gatsbyjs/gatsby#39341
  • fix: use forked devcert to avoid pulling transitive deps from its @types/* deps (#39343) by @​gatsbybot in gatsbyjs/gatsby#39345
    • This fixes npm install errors/warnings with Node.js 18 that look like error glob@11.0.3: The engine "node" is incompatible with this module. Expected version "20 || >=22". Got "18.6.0"

Full Changelog: https://github.com/gatsbyjs/gatsby/compare/gatsby@5.14.5...gatsby@5.14.6

gatsby@5.14.5

2025-06-19

... (truncated)

Changelog

Sourced from gatsby-plugin-offline's changelog.

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

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

6.12.3 (2023-10-26)

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

6.12.2 (2023-10-20)

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

6.12.1 (2023-10-09)

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

6.12.0 (2023-08-24)

... (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 4.14.0 to 6.15.0

Release notes

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

gatsby@5.15.0

What's Changed

Node.js 22

This release formally introduces Node.js 22 support, which is officially tested and supported going forward.

If you wish to use Node.js 22 with Gatsby, we highly recommend using the latest 22.x release, as there are known issues with some older 22.x versions that Gatsby is unable to work around at this time.

⚠️ Known Issue: gatsby develop fails with Node.js 22.7.0, 22.8.0, and 22.9.0

There is a critical bug in Node.js (nodejs/node#55145?) affecting versions 22.7.0, 22.8.0, and 22.9.0 that causes gatsby develop to fail with the error reported in gatsbyjs/gatsby#39068.

👉🏼 To avoid this, use Node.js 22.10.0 or later. (You can also use 22.6.0 or earlier.)

⚠️ Known Issue: Page loads may hang in dev with experimental DEV_SSR enabled and Node.js ≥22.14.0 (or ≥20.19.0)

This will not affect most users.

A change landed in Node.js 20.19.0 and 22.14.0 results in requests to the gatsby develop dev server to occasionally hang for 15 seconds. This can only occur if you have opted in to the experimental DEV_SSR flag.

👉🏼 To avoid this, disable the experimental DEV_SSR flag. (You can also downgrade to Node.js 22.13.1 or earlier, 20.18.3 or earlier, or 18.x.)

New Contributors

Thank you!

Full Changelog: https://github.com/gatsbyjs/gatsby/compare/gatsby@5.14.6...gatsby@5.15.0

gatsby@5.14.6

2025-08-06

What's Changed

  • fix: don't treat timestamps as dynamic paths (#39340) by @​gatsbybot in gatsbyjs/gatsby#39341
  • fix: use forked devcert to avoid pulling transitive deps from its @types/* deps (#39343) by @​gatsbybot in gatsbyjs/gatsby#39345
    • This fixes npm install errors/warnings with Node.js 18 that look like error glob@11.0.3: The engine "node" is incompatible with this module. Expected version "20 || >=22". Got "18.6.0"

Full Changelog: https://github.com/gatsbyjs/gatsby/compare/gatsby@5.14.5...gatsby@5.14.6

gatsby@5.14.5

2025-06-19

... (truncated)

Changelog

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

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

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

6.9.0 (2023-04-18)

🧾 Release notes

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

6.8.0 (2023-03-21)

🧾 Release notes

... (truncated)

Commits
  • e3d0717 chore(release): Publish
  • 17baffb chore(release): Publish next pre-minor
  • 5f44fcd chore(changelogs): update changelogs (#39156)
  • 2c75bc5 chore(changelogs): update changelogs (#38821)
  • 94b2482 chore(release): Publish next
  • 196618a chore(release): Publish next
  • 4f8c065 chore(changelogs): update changelogs (#38769)
  • eed07f3 chore(release): Publish next pre-minor
  • db248ab chore(changelogs): update changelogs (#38526)
  • e6e2fb4 chore(release): Publish next pre-minor
  • A...

    Description has been truncated

@dependabot
build(deps): Bump socket.io, gatsby, gatsby-plugin-canonical-urls, ga…
50d6a30 
…tsby-plugin-catch-links, gatsby-plugin-manifest, gatsby-plugin-offline, gatsby-plugin-react-helmet, gatsby-plugin-sass, gatsby-plugin-sharp, gatsby-plugin-sitemap, gatsby-plugin-typescript, gatsby-remark-autolink-headers, gatsby-remark-copy-linked-files, gatsby-remark-images, gatsby-remark-prismjs, gatsby-source-filesystem, gatsby-transformer-remark, gatsby-transformer-yaml and babel-plugin-remove-graphql-queries

Bumps [socket.io](https://github.com/socketio/socket.io) to 4.8.1 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-catch-links](https://github.com/gatsbyjs/gatsby/tree/HEAD/packages/gatsby-plugin-catch-links), [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-sass](https://github.com/gatsbyjs/gatsby/tree/HEAD/packages/gatsby-plugin-sass), [gatsby-plugin-sharp](https://github.com/gatsbyjs/gatsby/tree/HEAD/packages/gatsby-plugin-sharp), [gatsby-plugin-sitemap](https://github.com/gatsbyjs/gatsby/tree/HEAD/packages/gatsby-plugin-sitemap), [gatsby-plugin-typescript](https://github.com/gatsbyjs/gatsby/tree/HEAD/packages/gatsby-plugin-typescript), [gatsby-remark-autolink-headers](https://github.com/gatsbyjs/gatsby/tree/HEAD/packages/gatsby-remark-autolink-headers), [gatsby-remark-copy-linked-files](https://github.com/gatsbyjs/gatsby/tree/HEAD/packages/gatsby-remark-copy-linked-files), [gatsby-remark-images](https://github.com/gatsbyjs/gatsby/tree/HEAD/packages/gatsby-remark-images), [gatsby-remark-prismjs](https://github.com/gatsbyjs/gatsby/tree/HEAD/packages/gatsby-remark-prismjs), [gatsby-source-filesystem](https://github.com/gatsbyjs/gatsby/tree/HEAD/packages/gatsby-source-filesystem), [gatsby-transformer-remark](https://github.com/gatsbyjs/gatsby/tree/HEAD/packages/gatsby-transformer-remark), [gatsby-transformer-yaml](https://github.com/gatsbyjs/gatsby/tree/HEAD/packages/gatsby-transformer-yaml) and [babel-plugin-remove-graphql-queries](https://github.com/gatsbyjs/gatsby/tree/HEAD/packages/babel-plugin-remove-graphql-queries). These dependencies need to be updated together.


Updates `socket.io` from 3.1.1 to 4.8.1
- [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.1)

Updates `gatsby` from 3.14.6 to 5.15.0
- [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@3.14.6...gatsby@5.15.0)

Updates `gatsby-plugin-canonical-urls` from 3.14.0 to 5.15.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.15.0/packages/gatsby-plugin-canonical-urls)

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

Updates `gatsby-plugin-manifest` from 3.14.0 to 5.15.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.15.0/packages/gatsby-plugin-manifest)

Updates `gatsby-plugin-offline` from 4.14.0 to 6.15.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.15.0/packages/gatsby-plugin-offline)

Updates `gatsby-plugin-react-helmet` from 4.14.0 to 6.15.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.15.0/packages/gatsby-plugin-react-helmet)

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

Updates `gatsby-plugin-sharp` from 3.14.3 to 5.15.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.15.0/packages/gatsby-plugin-sharp)

Updates `gatsby-plugin-sitemap` from 4.10.0 to 6.15.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.15.0/packages/gatsby-plugin-sitemap)

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

Updates `gatsby-remark-autolink-headers` from 4.11.0 to 6.15.0
- [Release notes](https://github.com/gatsbyjs/gatsby/releases)
- [Changelog](https://github.com/gatsbyjs/gatsby/blob/master/packages/gatsby-remark-autolink-headers/CHANGELOG.md)
- [Commits](https://github.com/gatsbyjs/gatsby/commits/gatsby-remark-autolink-headers@6.15.0/packages/gatsby-remark-autolink-headers)

Updates `gatsby-remark-copy-linked-files` from 4.11.0 to 6.15.0
- [Release notes](https://github.com/gatsbyjs/gatsby/releases)
- [Changelog](https://github.com/gatsbyjs/gatsby/blob/master/packages/gatsby-remark-copy-linked-files/CHANGELOG.md)
- [Commits](https://github.com/gatsbyjs/gatsby/commits/gatsby-remark-copy-linked-files@6.15.0/packages/gatsby-remark-copy-linked-files)

Updates `gatsby-remark-images` from 5.11.0 to 7.15.0
- [Release notes](https://github.com/gatsbyjs/gatsby/releases)
- [Changelog](https://github.com/gatsbyjs/gatsby/blob/master/packages/gatsby-remark-images/CHANGELOG.md)
- [Commits](https://github.com/gatsbyjs/gatsby/commits/gatsby-remark-images@7.15.0/packages/gatsby-remark-images)

Updates `gatsby-remark-prismjs` from 5.11.0 to 7.15.0
- [Release notes](https://github.com/gatsbyjs/gatsby/releases)
- [Changelog](https://github.com/gatsbyjs/gatsby/blob/master/packages/gatsby-remark-prismjs/CHANGELOG.md)
- [Commits](https://github.com/gatsbyjs/gatsby/commits/gatsby-remark-prismjs@7.15.0/packages/gatsby-remark-prismjs)

Updates `gatsby-source-filesystem` from 3.14.0 to 5.15.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.15.0/packages/gatsby-source-filesystem)

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

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

Updates `babel-plugin-remove-graphql-queries` from 3.14.0 to 5.15.0
- [Release notes](https://github.com/gatsbyjs/gatsby/releases)
- [Changelog](https://github.com/gatsbyjs/gatsby/blob/master/packages/babel-plugin-remove-graphql-queries/CHANGELOG.md)
- [Commits](https://github.com/gatsbyjs/gatsby/commits/babel-plugin-remove-graphql-queries@5.15.0/packages/babel-plugin-remove-graphql-queries)

---
updated-dependencies:
- dependency-name: socket.io
  dependency-version: 4.8.1
  dependency-type: indirect
- dependency-name: gatsby
  dependency-version: 5.15.0
  dependency-type: direct:production
- dependency-name: gatsby-plugin-canonical-urls
  dependency-version: 5.15.0
  dependency-type: direct:production
- dependency-name: gatsby-plugin-catch-links
  dependency-version: 5.15.0
  dependency-type: direct:production
- dependency-name: gatsby-plugin-manifest
  dependency-version: 5.15.0
  dependency-type: direct:production
- dependency-name: gatsby-plugin-offline
  dependency-version: 6.15.0
  dependency-type: direct:production
- dependency-name: gatsby-plugin-react-helmet
  dependency-version: 6.15.0
  dependency-type: direct:production
- dependency-name: gatsby-plugin-sass
  dependency-version: 6.15.0
  dependency-type: direct:production
- dependency-name: gatsby-plugin-sharp
  dependency-version: 5.15.0
  dependency-type: direct:production
- dependency-name: gatsby-plugin-sitemap
  dependency-version: 6.15.0
  dependency-type: direct:production
- dependency-name: gatsby-plugin-typescript
  dependency-version: 5.15.0
  dependency-type: direct:production
- dependency-name: gatsby-remark-autolink-headers
  dependency-version: 6.15.0
  dependency-type: direct:production
- dependency-name: gatsby-remark-copy-linked-files
  dependency-version: 6.15.0
  dependency-type: direct:production
- dependency-name: gatsby-remark-images
  dependency-version: 7.15.0
  dependency-type: direct:production
- dependency-name: gatsby-remark-prismjs
  dependency-version: 7.15.0
  dependency-type: direct:production
- dependency-name: gatsby-source-filesystem
  dependency-version: 5.15.0
  dependency-type: direct:production
- dependency-name: gatsby-transformer-remark
  dependency-version: 6.15.0
  dependency-type: direct:production
- dependency-name: gatsby-transformer-yaml
  dependency-version: 5.15.0
  dependency-type: direct:production
- dependency-name: babel-plugin-remove-graphql-queries
  dependency-version: 5.15.0
  dependency-type: direct:development
...

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 Sep 23, 2025
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