chore(deps): update dependency gatsby to v5.16.0

[renovate]

This PR contains the following updates:

Package	Change	Age	Confidence
gatsby (source, changelog)	5.13.6 → 5.16.0

---

Release Notes

gatsbyjs/gatsby (gatsby)

v5.16.0

Compare Source

What's Changed

• feat: support React 19 by @​serhalp in #​39306
• feat: support Node.js 24 by @​serhalp in #​39380 and #​39398
• fix(deps): bump body-parser to resolve qs vulnerability warning by @​serhalp in #​39396
• chore(docs,starters): remove misc. outdated, invalid, or misleading instructions by @​serhalp in #​39363

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: #​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.
  • Notably, the new document metadata hoisting feature is disabled in Gatsby, as it conflicts with the existing Gatsby Head API
• 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.

Users can export onCaughtError and onUncaughtError from their gatsby-browser.js to handle errors caught by error boundaries and uncaught errors respectively:

// gatsby-browser.js

export const onCaughtError = ({ error, errorInfo }) => {
  // e.g. send to an error tracking service
  myErrorTracker.reportError(error, { extra: errorInfo })
}

export const onUncaughtError = ({ error, errorInfo }) => {
  // e.g. send to an error tracking service
  myErrorTracker.captureException(error, { extra: errorInfo })
}

In development, these errors also appear in Gatsby's Fast Refresh error overlay. These callbacks are only invoked in React 19.

Node.js 24

Node.js 24 is now officially supported by Gatsby.

PR: #​39380 and #​39398

Notable bugfixes & improvements

• gatsby, gatsby-source-drupal:
  • fix(deps): bump body-parser to resolve qs vulnerability warning by @​serhalp in #​39396
• chore: remove misc. outdated, invalid, or misleading contributor instructions by @​serhalp in #​39363

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

v5.15.0

Compare Source

What's Changed

• fix: support node 22 by @​serhalp in #​39349
• fix(gatsby): update socket.io to address vulnerable subdeps by @​serhalp in #​39352

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 #​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!

• @​pajosieg made their first contribution in #​39169
• @​johnmurphy01 made their first contribution in #​39324
• @​shrisoundharyaa made their first contribution in #​39286

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

v5.14.6

Compare Source

2025-08-06

What's Changed

• fix: don't treat timestamps as dynamic paths (#​39340) by @​gatsbybot in #​39341
• fix: use forked devcert to avoid pulling transitive deps from its @​types/* deps (#​39343) by @​gatsbybot in #​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

v5.14.5

Compare Source

2025-06-19

What's Changed

• fix: ensure rendering engine has vendored libvips (#​39317) by @​gatsbybot in #​39320

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

v5.14.4

Compare Source

2025-06-06

What's Changed

• fix(deps): upgrade multer to resolve 3 security vulnerabilities (#​39307) by @​gatsbybot in #​39308

Full Changelog: https://github.com/gatsbyjs/gatsby/compare/gatsby@5.14.3...gatsby@5.14.4

v5.14.3

Compare Source

2025-04-09

What's Changed

• fix: Align types of rootNodeMap during root node tracking (#​39262) by @​gatsbybot in #​39270

Full Changelog: https://github.com/gatsbyjs/gatsby/compare/gatsby@5.14.2...gatsby@5.14.3

v5.14.2

Compare Source

2025-04-07

What's Changed

• fix: pin isNonNullType is not defined with webpack>=5.99.0 (#​39264) by @​gatsbybot in #​39265

Full Changelog: https://github.com/gatsbyjs/gatsby/compare/gatsby@5.14.1...gatsby@5.14.2

v5.14.1

Compare Source

v5.14.0: v5.14.0

Compare Source

This release focused on performance improvements and security fixes.

What's Changed

• minor docs improvements: #​38816, #​39052, #​39133, #​39060
• security fixes:
  • bump gh-pages: #​39089
  • bump underscore: #​39092
  • bump thenify: #​39095
  • bump axios: #​39101 #​39118
  • bump ejs: #​39093
  • bump set-getter: #​39091
  • bump express: #​39099
  • bump express: #​39098
  • bump css-what: #​39107
  • bump rollup: #​39112 #​39115
  • bump body-parser: #​39097 #​39132
  • bump webpack-dev-middleware: #​39106
  • bump path-to-regexp: #​39096
• [gatsby, create-gatsby, gatsby-cli, gatsby-dev-cli, gatsby-plugin-gatsby-cloud, gatsby-plugin-page-creator] perf: disable telemetry reporting #​39137

See full release notes

v5.13.7: v5.13.7

Compare Source

2024-07-12

What's Changed

• fix(gatsby-adapter-netlify): support monorepos (#​39005) by @​gatsbybot in #​39037

See full release notes: #​39046

---

Configuration

📅 Schedule: Branch creation - At any time (no schedule defined), Automerge - At any time (no schedule defined).

🚦 Automerge: Disabled by config. Please merge this manually once you are satisfied.

♻ Rebasing: Whenever PR becomes conflicted, or you tick the rebase/retry checkbox.

🔕 Ignore: Close this PR and you won't be reminded about this update again.

---

• If you want to rebase/retry this PR, check this box

---

This PR was generated by Mend Renovate. View the repository job log.