Skip to content

Conversation

renovate[bot]
Copy link
Contributor

@renovate renovate bot commented Aug 11, 2025

This PR contains the following updates:

Package Change Age Confidence
gatsby (source, changelog) 5.14.5 -> 5.15.0 age confidence
gatsby-plugin-manifest (source) 5.14.0 -> 5.15.0 age confidence
gatsby-plugin-offline (source) 6.14.0 -> 6.15.0 age confidence
gatsby-plugin-react-helmet (source) 6.14.0 -> 6.15.0 age confidence
gatsby-plugin-sass (source) 6.14.0 -> 6.15.0 age confidence
gatsby-plugin-sharp (source) 5.14.0 -> 5.15.0 age confidence
gatsby-transformer-sharp (source) 5.14.0 -> 5.15.0 age confidence

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.

⚠️ 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!

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

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.


  • If you want to rebase/retry this PR, check this box

This PR was generated by Mend Renovate. View the repository job log.

@renovate renovate bot requested a review from itzsaga as a code owner August 11, 2025 04:57
@renovate renovate bot enabled auto-merge (squash) August 11, 2025 04:57
Copy link
Contributor Author

renovate bot commented Aug 11, 2025

Branch automerge failure

This PR was configured for branch automerge. However, this is not possible, so it has been raised as a PR instead.


  • Branch has one or more failed status checks

@renovate renovate bot force-pushed the renovate/gatsby-monorepo branch from c52bd0d to 9a0b529 Compare August 19, 2025 16:52
Copy link

cloudflare-workers-and-pages bot commented Aug 19, 2025

Deploying slack-list with  Cloudflare Pages  Cloudflare Pages

Latest commit: 17f607b
Status: ✅  Deploy successful!
Preview URL: https://1e254f63.slack-list.pages.dev
Branch Preview URL: https://renovate-gatsby-monorepo.slack-list.pages.dev

View logs

@renovate renovate bot force-pushed the renovate/gatsby-monorepo branch from 9a0b529 to 17f607b Compare August 31, 2025 10:28
@renovate renovate bot changed the title fix(deps): update dependency gatsby to v5.14.6 fix(deps): update gatsby monorepo Aug 31, 2025
Copy link

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

0 participants