fix(deps): update starters

[renovate]

This PR contains the following updates:

Package	Change	Age	Confidence
@types/node (source)	^22.18.10 → ^22.19.7
@types/react (source)	^18.3.20 → ^18.3.27
gatsby (source, changelog)	^5.15.0 → ^5.16.0
gatsby-plugin-catch-links (source)	^5.15.0 → ^5.16.0
gatsby-plugin-emotion (source)	^8.15.0 → ^8.16.0
gatsby-plugin-feed (source)	^5.15.0 → ^5.16.0
gatsby-plugin-manifest (source)	^5.15.0 → ^5.16.0
gatsby-plugin-mdx (source)	^5.15.0 → ^5.16.0
gatsby-plugin-sitemap (source)	^6.15.0 → ^6.16.0
gatsby-source-filesystem (source)	^5.15.0 → ^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

gatsbyjs/gatsby (gatsby-plugin-catch-links)

v5.16.0

Compare Source

🧾 Release notes

Bug Fixes

• use more explicit node.js version range #​39398 (c355640)

Other Changes

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

gatsbyjs/gatsby (gatsby-plugin-emotion)

v8.16.0

Compare Source

🧾 Release notes

Bug Fixes

• use more explicit node.js version range #​39398 (c355640)

Other Changes

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

gatsbyjs/gatsby (gatsby-plugin-feed)

v5.16.0

Compare Source

🧾 Release notes

Features

• support React 19 #​39306 (9e39c05)

Bug Fixes

• use more explicit node.js version range #​39398 (c355640)

Other Changes

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

gatsbyjs/gatsby (gatsby-plugin-manifest)

v5.16.0

Compare Source

🧾 Release notes

Bug Fixes

• use more explicit node.js version range #​39398 (c355640)

Other Changes

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

gatsbyjs/gatsby (gatsby-plugin-mdx)

v5.16.0

Compare Source

🧾 Release notes

Features

• support React 19 #​39306 (9e39c05)

Other Changes

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

gatsbyjs/gatsby (gatsby-plugin-sitemap)

v6.16.0

Compare Source

🧾 Release notes

Features

• support React 19 #​39306 (9e39c05)

Bug Fixes

• use more explicit node.js version range #​39398 (c355640)

Other Changes

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

gatsbyjs/gatsby (gatsby-source-filesystem)

v5.16.0

Compare Source

🧾 Release notes

Bug Fixes

• use more explicit node.js version range #​39398 (c355640)

Other Changes

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

---

Configuration

📅 Schedule: Branch creation - "before 10am on the first day of the month" in timezone GMT, 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.

👻 Immortal: This PR will be recreated if closed unmerged. Get config help if that's undesired.

---

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

---

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

[changeset-bot]

⚠️ No Changeset found

Latest commit: 67c76b2

Merging this PR will not cause a version bump for any packages. If these changes should not result in a new version, you're good to go. If these changes should result in a version bump, you need to add a changeset.

This PR includes no changesets

When changesets are added to this PR, you'll see the packages that this PR includes changesets for and the associated semver types

Click here to learn what changesets are, and how to add one.

Click here if you're a maintainer who wants to add a changeset to this PR

[netlify]

✅ Deploy Preview for gatsby-themes canceled.

Name	Link
🔨 Latest commit	67c76b2
🔍 Latest deploy log	https://app.netlify.com/projects/gatsby-themes/deploys/697ea17bda748400080b7eac