You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
{{ message }}
Repository navigation
Commit ba6a667
Browse filesBrowse the repository at this point in the historyBrowse files
fix(web): outdated servers can be updated even when the client can't connect
A v2 client refuses to open a session with a protocol-1 (v1) server, so
the only update path, server.updateServer over that session, was
unreachable. Users saw "Client not supported" with no way forward.
The self-update RPCs have the same wire shape in both protocols. When the
server is the outdated side, the unsupported row in Settings now offers
Update: it authorizes the socket without the protocol gate, calls only
the update RPCs, waits for the host descriptor to report a compatible
protocol, then clears the block and switches the environment back on.
Co-Authored-By: Claude Opus 5.5 (1M context) <[email protected]>
0 commit comments