Philippe Serhal

@joebentaylor1995 It sounds like you're describing a different issue. Please open a new issue or use our [support forums](https://answers.netlify.com/). Keep in mind we've released v5 of the runtime which works...

Hi @ryanwalters The team at Netlify have now released the new `v5` Next.js runtime which has support for both pages and app router, on-demand and time-based revalidation, automatic fine-grained cache...

Hi @bradlc The team at Netlify have now released the new `v5` Next.js runtime which has support for both pages and app router, on-demand and time-based revalidation, automatic fine-grained cache...

Superseded by v5.

Hi folks. We will be shipping full Node.js 22 support as soon as we can. I can't share a specific timeline, but this and React 19 support are our main...

Hey folks, while working on the Node.js 22 PR support I discovered it actually appears to fully work just fine. The issue here is that there's a bug (presumably [this...

FYI [email protected] officially supports Node.js 22: https://github.com/gatsbyjs/gatsby/releases/tag/gatsby%405.15.0

@emmron This PR is very large and unwieldy, updates unrelated code, and it isn't clear to me what it's solving. To be honest it looks like it may even have...

Thank you for sharing your solution with the community @rosszurowski! Though we aren't actively investing in new features or low-priority bug fixes, Gatsby is still maintained. If you open a...

Awesome, thank you! For the record, there is a response [here](https://github.com/gatsbyjs/gatsby/issues/38696#issuecomment-1817064739) and a blog post [here](https://www.netlify.com/blog/developing-gatsby-enhancing-stability-and-reliability/).