generated from netlify/build-plugin-template
-
Couldn't load subscription status.
- Fork 19
fix(deps): update dependency gatsby to v5.15.0 #827
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Open
Conversation
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
✅ Deploy Preview for netlify-plugin-gatsby-demo-v5 ready!
To edit notification comments on pull requests, go to your Netlify project configuration. |
✅ Deploy Preview for netlify-plugin-gatsby-demo ready!
To edit notification comments on pull requests, go to your Netlify project configuration. |
@renovate
renovate
bot
force-pushed
the
renovate/gatsby-monorepo
branch
from
August 19, 2025 11:44
c743320 to
cf2d6a8
Compare
@renovate
renovate
bot
force-pushed
the
renovate/gatsby-monorepo
branch
from
August 27, 2025 20:39
cf2d6a8 to
bf16bfb
Compare
@renovate
renovate
bot
changed the title
(削除) fix(deps): update dependency gatsby to v5.14.6 (削除ここまで)
(追記) fix(deps): update dependency gatsby to v5.15.0 (追記ここまで)
Aug 27, 2025
@renovate
renovate
bot
force-pushed
the
renovate/gatsby-monorepo
branch
from
September 25, 2025 17:30
bf16bfb to
3071e72
Compare
@renovate
renovate
bot
force-pushed
the
renovate/gatsby-monorepo
branch
from
October 21, 2025 20:09
3071e72 to
6355cf4
Compare
✅ Deploy Preview for netlify-plugin-gatsby-demo-v5 ready!
To edit notification comments on pull requests, go to your Netlify project configuration. |
✅ Deploy Preview for netlify-plugin-gatsby-demo ready!
To edit notification comments on pull requests, go to your Netlify project configuration. |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
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.
Uh oh!
There was an error while loading. Please reload this page.
This PR contains the following updates:
5.14.5->5.15.0Release Notes
gatsbyjs/gatsby (gatsby)
v5.15.0Compare 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 developfails 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 developto 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_SSRenabled 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 developdev server to occasionally hang for 15 seconds. This can only occur if you have opted in to the experimentalDEV_SSRflag.👉🏼 To avoid this, disable the experimental
DEV_SSRflag. (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/gatsby@5.14.6...gatsby@5.15.0
v5.14.6Compare Source
2025年08月06日
What's Changed
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
Configuration
📅 Schedule: Branch creation - Between 12:00 AM and 03:59 AM, only on Monday ( * 0-3 * * 1 ) (UTC), Automerge - At any time (no schedule defined).
🚦 Automerge: Enabled.
♻ Rebasing: Whenever PR becomes conflicted, or you tick the rebase/retry checkbox.
🔕 Ignore: Close this PR and you won't be reminded about these updates again.
This PR was generated by Mend Renovate. View the repository job log.