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

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

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

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

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

2025-04-09

What's Changed

• feat(gatsby-source-wordpress): support wp-graphql@2 (#39263) by @gatsbybot in #39269

Full Changelog: https://github.com/gatsbyjs/gatsby/compare/gatsby-source-wordpress@7.14.0...gatsby-source-wordpress@7.15.0

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

2025-01-02

What's Changed

• [possibly breaking] feat!(gatsby-source-shopify): upgrade from Shopify API version 2022-04 to 2024-04 (#39082) by @serhalp in #39082

Full Changelog: https://github.com/gatsbyjs/gatsby/compare/gatsby-source-shopify@8.14.1...gatsby-source-shopify@9.0.0

2024-12-20

What's Changed

• fix(gatsby-link): fix navigate method type by @pajosieg in #39169

Full Changelog: https://github.com/gatsbyjs/gatsby/compare/gatsby-link@5.14.0...gatsby-link@5.14.1

2014-12-13

What's Changed

• feat: update to ESM compatible version of CTF library (#39178) by @gatsbybot in #39185

Full Changelog: https://github.com/gatsbyjs/gatsby/compare/gatsby-source-contentful@8.14.0...gatsby-source-contentful@8.15.0