OpenNext writes every deploy to a new folder in R2 and never removes the old ones. How we found the live build, what we deleted, and what a model got wrong.
An R2 cache for OpenNext keeps growing because each deploy writes into a fresh folder named after that release, and nothing in the adapter ever deletes a previous folder. To clean it safely you must learn which release currently serves traffic, spare it together with a few recent neighbours, and run the deletion as a dry run before the real thing. On one Cloudflare account that removed about 41 GB.
Read the full report on AISkills402: https://aiskills402.com/blog/opennext-r2-cache-old-builds-cleanup
Top comments (0)