Title: Cloudflare ISR keeps previous deployment KV entries w/o expiration/cleanup · Issue #856 · voidzero-dev/void · GitHub
Open Graph Title: Cloudflare ISR keeps previous deployment KV entries w/o expiration/cleanup · Issue #856 · voidzero-dev/void
X Title: Cloudflare ISR keeps previous deployment KV entries w/o expiration/cleanup · Issue #856 · voidzero-dev/void
Description: After deploying a new version of a Void app directly to Cloudflare, ISR correctly starts using a new cache prefix, but the previous deployment's entries remain in ISR_CACHE without expiration. That means that repeated deployments will ac...
Open Graph Description: After deploying a new version of a Void app directly to Cloudflare, ISR correctly starts using a new cache prefix, but the previous deployment's entries remain in ISR_CACHE without expiration. That...
X Description: After deploying a new version of a Void app directly to Cloudflare, ISR correctly starts using a new cache prefix, but the previous deployment's entries remain in ISR_CACHE without expiration. ...
Opengraph URL: https://github.com/voidzero-dev/void/issues/856
X: @github
Domain: github.com
{"@context":"https://schema.org","@type":"DiscussionForumPosting","headline":"Cloudflare ISR keeps previous deployment KV entries w/o expiration/cleanup","articleBody":"After deploying a new version of a Void app directly to Cloudflare, ISR correctly starts using a new cache prefix, **but the previous deployment's entries remain in `ISR_CACHE` without expiration**.\n\nThat means that repeated deployments will accumulate persistent cache storage.\n\n## Environment\n\n- `void`, `@void/vue` and `@void/isr`: **1.9.1**.\n- Native Void Pages app deployed directly to the application's own Cloudflare accoun\n- ISR enabled (in my case, most pages have freshness intervals of up to 3,600 seconds).\n- The same writer behavior is present on upstream `main` at [`6c276f13b244d3a36aaee6301ad011bd287b5728`](https://github.com/voidzero-dev/void/commit/6c276f13b244d3a36aaee6301ad011bd287b5728).\n\n## Reproduction\n\nThe following isolates the behavior observed in a deployed application; it does not require application-specific data:\n\n1. Configure a public page with ISR enabled, for example:\n\n ```ts\n import { defineConfig } from 'void/config';\n\n export default defineConfig({\n routing: {\n isr: true,\n revalidate: 60,\n },\n });\n ```\n\n2. Deploy version A directly to Cloudflare and request the page to populate ISR.\n3. List the provisioned `ISR_CACHE` namespace. The response entry is stored under a deployment-specific prefix:\n\n ```text\n __void_direct__/isr/v3/\u003cA>/\u003chost>/\u003cpath>\n ```\n\n The listed metadata contains freshness information, but the key has no `expiration`.\n4. Build and deploy version B, then request the same page. A new entry is written under `\u003cB>`; A's entry remains stored.\n5. Stop requesting version A and inspect the namespace again after its freshness interval. There is no configured physical expiry or obsolete-deployment sweep to reclaim A's entries. Repeating deployments adds further prefixes.\n\n## Actual behavior and impact\n\nIn a read-only investigation of my app:\n\n- Cloudflare analytics reported approximately **5.1 GB** of KV storage on November 16, 2026, through 13:30 UTC.\n- A later complete namespace listing at **13:56–13:57 UTC** returned **91,966 unique keys, none with expiration**.\n- These comprised **91,913 ISR entries across 52 deployment prefixes**, plus **53 host-registry entries**.\n- Only **408** of the scanned ISR entries belonged to the build then receiving production traffic. The remaining **91,505** belonged to noncurrent prefixes (some may still be useful for rollback).\n\n## Expected behavior\n\nA supported way to bound the lifetime of framework-owned ISR storage, covering both response entries and host registrations. This could be a retention policy distinct from freshness, retirement cleanup, or a combination.\n\nThe policy should:\n\n- Preserve a useful stale-while-revalidate/stale-on-error window. Setting physical expiry equal to the freshness TTL would remove that behavior.\n- Protect active deployments, rollbacks and deployment transitions; avoid deleting every previous prefix immediately after deployment.\n- Handle host registration renewal if registry entries expire, including long-lived isolates.\n- Explain how existing nonexpiring entries can be reclaimed safely after a fix.","author":{"url":"https://github.com/TheAlexLichter","@type":"Person","name":"TheAlexLichter"},"datePublished":"2026-11-16T14:26:06Z","url":"https://github.com/voidzero-dev/void/issues/856"}
| react-profiling | 0 |
| react-import-map | react,react-dom,react-dom/client,react-dom/profiling,react-is,react/compiler-runtime,react/jsx-dev-runtime,react/jsx-runtime,scheduler@b8488ee2c322 |
| route-pattern | /_view_fragments/issues/show/:user_id/:repository/:id/issue_layout(.:format) |
| route-controller | voltron_issues_fragments |
| route-action | issue_layout |
| fetch-nonce | v2:07aff7ff-5507-d4df-1a30-eaa6abb0d521 |
| current-catalog-service-hash | 81bb79d38c15960b92d99bca9288a9108c7a47b18f2423d0f6438c5b7bcd2114 |
| request-id | B228:28C247:6502F:88CA1:6AFBA413 |
| html-safe-nonce | ec4a5d77d614aa6b550488330cc4b1360962c919ac16ca7446dde6fd65220bd1 |
| visitor-payload | eyJyZWZlcnJlciI6IiIsInJlcXVlc3RfaWQiOiJCMjI4OjI4QzI0Nzo2NTAyRjo4OENBMTo2QUZCQTQxMyIsInZpc2l0b3JfaWQiOiIyNzgwMDI3NzMyODYyMTQ5NjUxIiwicmVnaW9uX2VkZ2UiOiJpYWQiLCJyZWdpb25fcmVuZGVyIjoiaWFkIn0= |
| visitor-hmac | c8997d5d36ce4c5660e1c72a55f332be252dc0a00c87264befb91215579d24c6 |
| hovercard-subject-tag | issue:6423371011 |
| github-keyboard-shortcuts | repository,issues,copilot |
| google-site-verification | Apib7-x98H0j5cPqHWwSMm6dNU4GmODRoqxLiDzdx9I |
| octolytics-url | https://collector.github.com/github/collect |
| analytics-location | / |
| fb:app_id | 1401488693436528 |
| apple-itunes-app | app-id=1477376905, app-argument=https://github.com/_view_fragments/issues/show/voidzero-dev/void/856/issue_layout |
| twitter:image | https://opengraph.githubassets.com/d3658bf168e0ea5d967b3c01a1fb506b50b825f43bc1398a52544b15ba47117f/voidzero-dev/void/issues/856 |
| twitter:card | summary_large_image |
| og:image | https://opengraph.githubassets.com/d3658bf168e0ea5d967b3c01a1fb506b50b825f43bc1398a52544b15ba47117f/voidzero-dev/void/issues/856 |
| og:image:alt | After deploying a new version of a Void app directly to Cloudflare, ISR correctly starts using a new cache prefix, but the previous deployment's entries remain in ISR_CACHE without expiration. That... |
| og:image:width | 1200 |
| og:image:height | 600 |
| og:site_name | GitHub |
| og:type | object |
| og:author:username | TheAlexLichter |
| hostname | github.com |
| expected-hostname | github.com |
| None | 03e5090f0cea887cafa036e3af34d7c668d83b5e9e9e03df72a90efb49b69cdf |
| turbo-cache-control | no-preview |
| go-import | github.com/voidzero-dev/void git https://github.com/voidzero-dev/void.git |
| octolytics-dimension-user_id | 149750581 |
| octolytics-dimension-user_login | voidzero-dev |
| octolytics-dimension-repository_id | 1164437080 |
| octolytics-dimension-repository_nwo | voidzero-dev/void |
| octolytics-dimension-repository_public | true |
| octolytics-dimension-repository_is_fork | false |
| octolytics-dimension-repository_network_root_id | 1164437080 |
| octolytics-dimension-repository_network_root_nwo | voidzero-dev/void |
| turbo-body-classes | logged-out env-production page-responsive |
| disable-turbo | false |
| browser-stats-url | https://api.github.com/_private/browser/stats |
| browser-errors-url | https://api.github.com/_private/browser/errors |
| release | 41f00295b9a35dca977890ab83b22788ab211dc8 |
| ui-target | full |
| theme-color | #1e2327 |
| color-scheme | light dark |
| react-app-name | issues |
Links:
Viewport: width=device-width