[{"data":1,"prerenderedAt":18},["ShallowReactive",2],{"release:0.2.16":3},{"version":4,"title":5,"description":6,"date":7,"url":8,"markdownPath":9,"prerelease":10,"html":11,"newer":12,"older":15},"0.2.16","L4 0.2.16","This release fixes the Cloudflare Factory image published in 0.2.15 and preserves setup choices through authorization. Landing, Shell, installer, Server, portable runtime and Docs share 0.2.16. Existing customer Servers…","2026-10-27","\u002Fchangelog\u002Fv0.2.16","\u002Fchangelog\u002Fv0.2.16.md",false,"\u003Cp>This release fixes the Cloudflare Factory image published in 0.2.15 and preserves setup choices through authorization. Landing, Shell, installer, Server, portable runtime and Docs share \u003Cstrong>0.2.16\u003C\u002Fstrong>. Existing customer Servers stay pinned until their operator chooses an update.\u003C\u002Fp>\n\u003Cul>\n\u003Cli>Factory image layers are compressed exactly once. The builder handles both classic Docker tar exports and already-compressed containerd exports. Before publication, the release verifies the compressed descriptors, readable tar contents and each uncompressed \u003Ccode>diff_id\u003C\u002Fcode> against the image config. The double-gzipped 0.2.15 image fails this check even when its download checksums match.\u003C\u002Fli>\n\u003Cli>The Factory installer keeps the selected compute size, command timeout and process limit across the Cloudflare redirect in the same browser tab, scoped to the selected account and Worker. The resource summary follows the chosen size.\u003C\u002Fli>\n\u003Cli>GitHub App setup explains how to recover when GitHub sudo\u002FMFA loses the submitted manifest. Preparing again checks for a completed connection first and generates fresh setup state, without retrying a credential exchange or automatically creating another App.\u003C\u002Fli>\n\u003C\u002Ful>\n\u003Cp>No Server SQL migration is required. Durable Object migration \u003Ccode>v5-factory-executor\u003C\u002Fcode> is unchanged. Published releases and earlier migrations remain immutable.\u003C\u002Fp>\n\u003Cp>For a Cloudflare Server whose Factory activation failed on 0.2.15: back up and update the Server to 0.2.16, provision Factory again through \u003Ccode>\u002Fcreate\u003C\u002Fcode> to select the corrected published image, then activate it in Settings → Repositories. Keep any existing Task source and backup destinations. Provisioning does not upgrade the Cloudflare plan.\u003C\u002Fp>\n",{"title":13,"url":14},"L4 0.2.17","\u002Fchangelog\u002Fv0.2.17",{"title":16,"url":17},"L4 0.2.15","\u002Fchangelog\u002Fv0.2.15",1793335827134]