[{"data":1,"prerenderedAt":18},["ShallowReactive",2],{"release:0.3.17":3},{"version":4,"title":5,"description":6,"date":7,"url":8,"markdownPath":9,"prerelease":10,"html":11,"newer":12,"older":15},"0.3.17","L4 0.3.17","This release keeps a Server clear of Telegram's controls when the Telegram Shell opens it. Landing, Shell, installer, Server, portable runtime and Docs share 0.3.17. It stays on the server-v2 lineage and adds no…","2026-11-03","\u002Fchangelog\u002Fv0.3.17","\u002Fchangelog\u002Fv0.3.17.md",false,"\u003Cp>This release keeps a Server clear of Telegram's controls when the Telegram Shell opens it. Landing, Shell, installer, Server, portable runtime and Docs share \u003Cstrong>0.3.17\u003C\u002Fstrong>. It stays on the \u003Ccode>server-v2\u003C\u002Fcode> lineage and adds no migrations. Customer Servers update only when their operator chooses an update.\u003C\u002Fp>\n\u003Ch2 id=\"telegram\">\u003Ca class=\"heading-anchor\" href=\"#telegram\">Telegram\u003C\u002Fa>\u003C\u002Fh2>\n\u003Cul>\n\u003Cli>The Shell now tells a Server how much room Telegram's controls and the device take, and the Server keeps that through reloads. Before, a Server's header could sit under Close and the menu button.\u003C\u002Fli>\n\u003Cli>To get this, a Server must run 0.3.17 and be opened again from the Shell.\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>A Cloudflare Server that keeps Cloudflare access updates from Server settings → Deployment → Updates by itself. A Docker Server updates by its image tag in Coolify or Docker Compose; the VPS installer uses \u003Ccode>llll upgrade\u003C\u002Fcode>.\u003C\u002Fp>\n",{"title":13,"url":14},"L4 0.3.18","\u002Fchangelog\u002Fv0.3.18",{"title":16,"url":17},"L4 0.3.16","\u002Fchangelog\u002Fv0.3.16",1793693065958]