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 7cce227
Browse filesBrowse the repository at this point in the historyBrowse files
fix(web): compare client and server versions as semver, not strings
The client compared its version to the server's with string inequality, so a
nightly build on either side never matched a stable one and the skew banner
fired constantly. The comparison was also direction-blind: a server newer than
the client raised a "server update available" banner whose arrow pointed
backwards.
Versions now compare as semver on their core major.minor.patch. Same core means
compatible, so nightly-versus-stable no longer warns, and a server ahead of the
client returns no mismatch at all since every consumer of that result only knows
how to tell users to update their server. Unparseable versions keep the old
string-inequality behavior.
Model: Claude Opus 5, harness: T3 Code.
0 commit comments