chore(deps): update gatsby monorepo

[renovate]

This PR contains the following updates:

Package	Change	Age	Confidence
gatsby (source, changelog)	5.14.1 -> 5.15.0
gatsby-plugin-utils (source)	4.14.0 -> 4.15.0

---

Release Notes

gatsbyjs/gatsby (gatsby)

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/[email protected]@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 [email protected]: The engine "node" is incompatible with this module. Expected version "20 || >=22". Got "18.6.0"

Full Changelog: https://github.com/gatsbyjs/gatsby/compare/[email protected]@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/[email protected]@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/[email protected]@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/[email protected]@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/[email protected]@5.14.2

gatsbyjs/gatsby (gatsby-plugin-utils)

v4.15.0

Compare Source

🧾 Release notes

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

---

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.

👻 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.

[codecov]

Codecov Report

✅ All modified and coverable lines are covered by tests.
✅ Project coverage is 99.56%. Comparing base (b179e7f) to head (46abae2).
⚠️ Report is 3 commits behind head on master.

Additional details and impacted files

@@           Coverage Diff           @@
##           master     #178   +/-   ##
=======================================
  Coverage   99.56%   99.56%           
=======================================
  Files          15       15           
  Lines         918      918           
  Branches      219      219           
=======================================
  Hits          914      914           
  Misses          4        4           

☔ View full report in Codecov by Sentry.
📢 Have feedback on the report? Share it here.

🚀 New features to boost your workflow:

• ❄️ Test Analytics: Detect flaky tests, report on failures, and find test suite problems.
• 📦 JS Bundle Analysis: Save yourself from yourself by tracking and limiting bundle sizes in JS merges.