On November 19, 2026, Cloudflare published a new retention rule for Workers and Pages. Workers versions and Pages deployments are now kept for 30 days. After that they are deleted, unless they are among the project's 100 most recent or are what is currently live. The running application is not affected. What goes away are the old versions, the URLs tied to them and, on Pages, the ability to roll back to those deployments.
What disappears after 30 days
On Workers, a version is created every time you upload code or change settings or secrets. According to the documentation, a version older than 30 days is deleted if it is not among the Worker's 100 most recent and is not serving any share of traffic, which includes both versions in a gradual deployment. When that happens, it disappears from the dashboard and API lists, and its Version URL stops working, including aliases created with --preview-alias. An alias does not protect the version. Deployment history remains, but shows the version as deleted. Deploy, gradual deployment and rollback already accepted only the 100 most recent versions.
On Pages the rule is the same, with one detail that matters more: production and preview deployments count together toward the 100 limit. A deleted deployment leaves the list, its unique <hash>.<project>.pages.dev URL stops responding, and you can no longer roll back to it. The only production deployment always kept is the current one.
Who feels the change
Projects with few deployments per month will barely notice, because the 100 most recent are kept even past 30 days. The effect shows up in two cases.
The first is a project with many deployments. On a Pages project where every pull request creates a preview, 100 deployments may cover only a few weeks of work. After 30 days, a production deployment that fell outside the 100 most recent no longer works as a rollback point from the dashboard.
The second is a team that uses these URLs as a record. A staging link sent to a client, a link pasted into an acceptance ticket or a delivery document: all of these now expire. For an agency or consultancy that keeps a preview URL as proof of what was approved, the link will break after 30 days if the project has had more than 100 deployments since.
What to do now
Cloudflare recommends replacing Version URLs with Worker Previews when reviewing branches and pull requests. A preview URL always serves the latest deployment of that branch, and the reason for the recommendation goes beyond retention: Version URLs run with production bindings, meaning they reach the same databases, queues and services bound to the live Worker. That risk was already the point of A safe preview must isolate connected resources, and the new rule is one more reason not to rely on Version URLs for review.
For anything that needs to last, the record has to live outside the platform. Keeping the commit or tag of each approved delivery lets you rebuild that version from the repository once the URL is gone. The same applies to rollback: if a busy project's rollback plan counts on returning to a two-month-old deployment from the dashboard, it needs to plan for a fresh deployment from Git instead.
The announcement sets no deadline, because the rule already applies. The most urgent review is of links shared outside the team, since those are the ones that will break without anyone noticing.
What the announcement does not say
The changelog and documentation pages mention no transition period and do not say whether versions already older than 30 days on November 19 were deleted all at once. They also do not distinguish between plans: the rule appears with no Enterprise exception and no option to export a version before deletion. The documentation states that KV, R2, Durable Objects and D1 state was never part of versions, so that data is not affected by the cleanup.
If your company is weighing something similar, reach me on LinkedIn or WhatsApp.