Open
Conversation
✅ Deploy Preview for calendar-gatsby ready!
To edit notification comments on pull requests, go to your Netlify project configuration. |
3030776 to
940b19c
Compare
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
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.
This PR contains the following updates:
5.15.0→5.16.1Release Notes
gatsbyjs/gatsby (gatsby)
v5.16.1Compare Source
What's Changed
<title>not updatingdocument.titleby @serhalp and @pieh in #39382Full Changelog: https://github.com/gatsbyjs/gatsby/compare/gatsby@5.16.0...gatsby@5.16.1
v5.16.0Compare Source
What's Changed
body-parserto resolveqsvulnerability warning by @serhalp in #39396React 19
🚀 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
reactandreact-domhave been extended from^18.0.0to^18.0.0 || ^19.0.0.All existing stable Gatsby functionality is intended to now work with React 19.
PR: #39306
Upgrade Guide
To upgrade to React 19, first upgrade
gatsbyand all your dependencies that start withgatsby-to the latest version. (Check out this guide if you need help with that.)Then, follow the React 19 upgrade guide. No other changes are required.
Please note:
New features
Gatsby now supports React 19's new root error callbacks.
Users can export
onCaughtErrorandonUncaughtErrorfrom theirgatsby-browser.jsto handle errors caught by error boundaries and uncaught errors respectively: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:body-parserto resolveqsvulnerability warning by @serhalp in #39396Full Changelog: https://github.com/gatsbyjs/gatsby/compare/gatsby@5.15.0...gatsby@5.16.0
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.
🔕 Ignore: Close this PR and you won't be reminded about this update again.
This PR was generated by Mend Renovate. View the repository job log.