[{"data":1,"prerenderedAt":18},["ShallowReactive",2],{"release:0.2.19":3},{"version":4,"title":5,"description":6,"date":7,"url":8,"markdownPath":9,"prerelease":10,"html":11,"newer":12,"older":15},"0.2.19","L4 0.2.19","This release improves Factory execution recovery and protects pending chat messages during a browser reload. Landing, Shell, installer, Server, portable runtime and Docs share 0.2.19. Customer Servers update only when…","2026-10-27","\u002Fchangelog\u002Fv0.2.19","\u002Fchangelog\u002Fv0.2.19.md",false,"\u003Cp>This release improves Factory execution recovery and protects pending chat messages during a browser reload. Landing, Shell, installer, Server, portable runtime and Docs share \u003Cstrong>0.2.19\u003C\u002Fstrong>. Customer Servers update only when their operator chooses an update.\u003C\u002Fp>\n\u003Cp>Factory reads bounded command input directly from the stdin stream, including Linux socket-backed input. The Server also uses a streaming bridge with existing pinned workspace images, so an existing Node can keep its reviewed image and retained Task source. Helper stderr is drained separately from its JSON protocol. Interrupted execution records a safe failure stage and code without exposing command output or replaying an uncertain operation. An operator must review an uncertain result; updating does not retry it automatically.\u003C\u002Fp>\n\u003Cp>Factory provisioning preserves Worker observability settings, including an explicit operator choice to disable them, and uses the standard Server defaults when no settings exist. Existing Nodes, source authority and backup destinations remain protected.\u003C\u002Fp>\n\u003Cp>While a chat message is awaiting acknowledgement, reloading or closing the page now invokes the browser's unsaved-changes warning. Staying on the page retains the pending message for the existing reconnect flow; its original identifier prevents duplicate delivery. The warning is removed after all pending messages are acknowledged or the channel is closed. Pending messages are not stored on disk, so choosing to leave can still discard them.\u003C\u002Fp>\n\u003Cp>The provisioning and artifact fixes from 0.2.16–0.2.18 remain included. Published releases are unchanged. No Server SQL or Durable Object migration is required.\u003C\u002Fp>\n",{"title":13,"url":14},"L4 0.2.20","\u002Fchangelog\u002Fv0.2.20",{"title":16,"url":17},"L4 0.2.18","\u002Fchangelog\u002Fv0.2.18",1793335827064]