[{"data":1,"prerenderedAt":18},["ShallowReactive",2],{"release:0.3.2":3},{"version":4,"title":5,"description":6,"date":7,"url":8,"markdownPath":9,"prerelease":10,"html":11,"newer":12,"older":15},"0.3.2","L4 0.3.2","This release lets a Cloudflare Server keep Cloudflare access and update itself. Landing, Shell, installer, Server, portable runtime and Docs share 0.3.2. It stays on the server-v2 lineage with no new migrations, so a…","2026-10-29","\u002Fchangelog\u002Fv0.3.2","\u002Fchangelog\u002Fv0.3.2.md",false,"\u003Cp>This release lets a Cloudflare Server keep Cloudflare access and update itself. Landing, Shell, installer, Server, portable runtime and Docs share \u003Cstrong>0.3.2\u003C\u002Fstrong>. It stays on the \u003Ccode>server-v2\u003C\u002Fcode> lineage with no new migrations, so a 0.3.x Server can update in place. Customer Servers update only when their operator chooses an update.\u003C\u002Fp>\n\u003Ch2 id=\"servers-update-themselves\">\u003Ca class=\"heading-anchor\" href=\"#servers-update-themselves\">Servers update themselves\u003C\u002Fa>\u003C\u002Fh2>\n\u003Cul>\n\u003Cli>Installing or updating through the official installer now offers \u003Cstrong>Keep Cloudflare access on this Server\u003C\u002Fstrong>, on by default. After the Server runs the new version, the installer hands its Cloudflare access to the Server and forgets it. For safety, run each Server in its own Cloudflare account; a free account is enough.\u003C\u002Fli>\n\u003Cli>Settings → Deployment → Updates shows that access, lets you disconnect it, or connect it with an API token from a pre-filled Cloudflare link.\u003C\u002Fli>\n\u003Cli>With that access, \u003Cstrong>Back up and update\u003C\u002Fstrong> runs on the Server itself: it verifies the release, backs up to the separate backup bucket and reads the backup back, uploads, and lets the new version confirm itself. You can close the page; \u003Cstrong>Retry update\u003C\u002Fstrong> resumes after the verified backup.\u003C\u002Fli>\n\u003Cli>After an update, Settings offers to load the new interface if your browser still shows the old one.\u003C\u002Fli>\n\u003Cli>The official installer remains available. Its update screen no longer spins before it starts or claims an upload that has not happened, and it retries release downloads that GitHub rate-limits.\u003C\u002Fli>\n\u003Cli>Release notes in Updates are formatted instead of shown as raw Markdown.\u003C\u002Fli>\n\u003C\u002Ful>\n\u003Ch2 id=\"chatgpt\">\u003Ca class=\"heading-anchor\" href=\"#chatgpt\">ChatGPT\u003C\u002Fa>\u003C\u002Fh2>\n\u003Cul>\n\u003Cli>Pasting the sign-in address again now confirms a finished connection or shows the real reason it failed, instead of saying the attempt expired. After a failure the form asks for a fresh sign-in.\u003C\u002Fli>\n\u003C\u002Ful>\n\u003Ch2 id=\"update-to-this-release\">\u003Ca class=\"heading-anchor\" href=\"#update-to-this-release\">Update to this release\u003C\u002Fa>\u003C\u002Fh2>\n\u003Cp>Update from Settings → Deployment → Updates as before and keep \u003Cstrong>Keep Cloudflare access on this Server\u003C\u002Fstrong> checked. Keep that tab open until it finishes; from the next release on, the Server updates from its own Settings.\u003C\u002Fp>\n",{"title":13,"url":14},"L4 0.3.3","\u002Fchangelog\u002Fv0.3.3",{"title":16,"url":17},"L4 0.3.1","\u002Fchangelog\u002Fv0.3.1",1793335826981]