fix(deps): update gatsby monorepo #672
Open
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
This PR contains the following updates:
5.14.5
->5.15.0
5.14.0
->5.15.0
6.14.0
->6.15.0
6.14.0
->6.15.0
6.14.0
->6.15.0
5.14.0
->5.15.0
5.14.0
->5.15.0
Release Notes
gatsbyjs/gatsby (gatsby)
v5.15.0
Compare Source
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.
gatsby develop
fails with Node.js 22.7.0, 22.8.0, and 22.9.0There 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.)
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 experimentalDEV_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/[email protected]@5.15.0
v5.14.6
Compare Source
2025-08-06
What's Changed
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
gatsbyjs/gatsby (gatsby-plugin-manifest)
v5.15.0
Compare Source
🧾 Release notes
Note: Version bump only for package gatsby-plugin-manifest
gatsbyjs/gatsby (gatsby-plugin-offline)
v6.15.0
Compare Source
🧾 Release notes
Note: Version bump only for package gatsby-plugin-offline
gatsbyjs/gatsby (gatsby-plugin-react-helmet)
v6.15.0
Compare Source
🧾 Release notes
Note: Version bump only for package gatsby-plugin-react-helmet
gatsbyjs/gatsby (gatsby-plugin-sass)
v6.15.0
Compare Source
🧾 Release notes
Note: Version bump only for package gatsby-plugin-sass
gatsbyjs/gatsby (gatsby-plugin-sharp)
v5.15.0
Compare Source
🧾 Release notes
Note: Version bump only for package gatsby-plugin-sharp
gatsbyjs/gatsby (gatsby-transformer-sharp)
v5.15.0
Compare Source
🧾 Release notes
Note: Version bump only for package gatsby-transformer-sharp
Configuration
📅 Schedule: Branch creation - At any time (no schedule defined), Automerge - At any time (no schedule defined).
🚦 Automerge: Enabled.
♻ 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.
This PR was generated by Mend Renovate. View the repository job log.