Website: regenerated pages are saved again
Since Next.js 16.4, the website stores the pages it regenerates in a folder its service was not allowed to write to. Every regeneration therefore failed to be saved, with 300 to 900 errors per day, with no visible effect since pages kept being served from memory. The folder is now writable and recreated empty at every deployment.
- Commit
- cf8827f
- Build
- Build success · Target murloc-site
- Cause: the website service runs in a read-only environment, except for its data folders; the new Next.js 16.4 cache folder was not one of them.
- Fix: this folder is now writable for the service, and deployment recreates it empty so that a page from a previous version of the website is never served.
- Checked after the restart: no more errors, 36 regenerated pages saved.