[{"data":1,"prerenderedAt":18},["ShallowReactive",2],{"release:0.2.17":3},{"version":4,"title":5,"description":6,"date":7,"url":8,"markdownPath":9,"prerelease":10,"html":11,"newer":12,"older":15},"0.2.17","L4 0.2.17","This release completes recovery for a Cloudflare Factory that was provisioned with an earlier image but never activated. Landing, Shell, installer, Server, portable runtime and Docs share 0.2.17. Existing customer…","2026-10-27","\u002Fchangelog\u002Fv0.2.17","\u002Fchangelog\u002Fv0.2.17.md",false,"\u003Cp>This release completes recovery for a Cloudflare Factory that was provisioned with an earlier image but never activated. Landing, Shell, installer, Server, portable runtime and Docs share \u003Cstrong>0.2.17\u003C\u002Fstrong>. Existing customer Servers stay pinned until their operator chooses an update.\u003C\u002Fp>\n\u003Cul>\n\u003Cli>After updating the Server, provisioning can replace its unused Factory image and limits only when its database has no Cloudflare Factory Node and no retained Task source. Existing Nodes, including paused ones, and retained source keep their pinned provider. A provisioning marker serializes this repair against activation and remains closed after a failure until provisioning succeeds. The installer requires the immutable Server artifact to advertise this protection.\u003C\u002Fli>\n\u003Cli>The existing Container application is reconciled through a Cloudflare rollout, then checked for the selected image, size and namespace before activation is allowed. A foreign namespace or different scheduling policy requires inspection. No Task source, Server data or backup destination is deleted.\u003C\u002Fli>\n\u003Cli>Settings → Repositories offers \u003Cstrong>Review Factory provisioning\u003C\u002Fstrong> when Factory resources exist but activation has not created a Node.\u003C\u002Fli>\n\u003Cli>The release picker bypasses old browser cache entries. Cloudflare's official zone now respects the application's cache headers, so the release list uses its intended five-minute cache. A completed update no longer asks you to keep waiting for verification.\u003C\u002Fli>\n\u003C\u002Ful>\n\u003Cp>The single-compressed image layers and semantic publication checks from 0.2.16 remain in place. Published 0.2.15 and 0.2.16 assets are unchanged.\u003C\u002Fp>\n\u003Cp>For failed 0.2.15 Factory activation: update the Server to \u003Cstrong>0.2.17\u003C\u002Fstrong> with a verified backup, open \u003Cstrong>Review Factory provisioning\u003C\u002Fstrong>, confirm the desired resources, provision again and activate Factory. A Server with an existing Factory Node or Task source must preserve\u002Fexport that source and explicitly configure another provider; this release does not replace active authority.\u003C\u002Fp>\n\u003Cp>No Server SQL or Durable Object migration is required. The existing \u003Ccode>server-v1\u003C\u002Fcode> lineage and \u003Ccode>v5-factory-executor\u003C\u002Fcode> migration are unchanged.\u003C\u002Fp>\n",{"title":13,"url":14},"L4 0.2.18","\u002Fchangelog\u002Fv0.2.18",{"title":16,"url":17},"L4 0.2.16","\u002Fchangelog\u002Fv0.2.16",1793335827119]