Philippe Serhal

I'm closing this since there hasn't been any activity in over a year. Feel free to start a new thread on https://answers.netlify.com/ if you need more support.

Hi @benjamin-fleet 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. (I checked and it has the updated logo.)

Interesting, thanks for sharing @kristof-kasa. I'm not aware of such a bug, and you're right that this is not an expected behaviour. Can you share a minimal reproduction please? 🙏🏼

Hi @elliottsj @kaf-lamed-beyt 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...

For the record, as far as I know this was still an issue.

This is still relevant.

This is still relevant.

Hi @Garciat, thanks for the great bug report! Coincidentally we _just_ merged a change to that code that uses the native `pipeline`: https://github.com/netlify/cli/pull/7096. May I give you a ping here...

Superseded by v5 rewrite.