Before submitting
Area
apps/web
Steps to reproduce
- Run the macOS desktop app on an older nightly build (example:
0.0.32-nightly.20260802.980).
- Connect to an environment whose server is on a newer nightly (example:
0.0.32-nightly.20260803.985).
- Open a conversation so the version-drift banner appears.
Expected behavior
The banner should recognize that the client is behind the server, tell the user to update this app, and offer an Update client action that runs the desktop updater. It must not offer updating/downgrading the server to the older client version.
Actual behavior
The banner title says "Client and server versions differ" and the body/CTA tell the user to Update server so they stay in sync. Clicking that action would target the client's older version on the newer server.
Example copy observed:
Client 0.0.32-nightly.20260802.980 is connected to … server 0.0.32-nightly.20260803.985. Update the … server so they stay in sync.
[Update server]
Impact
Major degradation or frequent failure
The CTA is inverted and can push a server downgrade when the desktop client simply needs an update.
Version or commit
0.0.32-nightly.20260802.980 client vs 0.0.32-nightly.20260803.985 server
Environment
macOS desktop app (nightly), connected to a remote/local server on a newer nightly
Workaround
Manually update/restart the macOS app (Check for Updates / install the newer desktop build) and ignore the "Update server" button.
Before submitting
Area
apps/web
Steps to reproduce
0.0.32-nightly.20260802.980).0.0.32-nightly.20260803.985).Expected behavior
The banner should recognize that the client is behind the server, tell the user to update this app, and offer an Update client action that runs the desktop updater. It must not offer updating/downgrading the server to the older client version.
Actual behavior
The banner title says "Client and server versions differ" and the body/CTA tell the user to Update server so they stay in sync. Clicking that action would target the client's older version on the newer server.
Example copy observed:
Impact
Major degradation or frequent failure
The CTA is inverted and can push a server downgrade when the desktop client simply needs an update.
Version or commit
0.0.32-nightly.20260802.980client vs0.0.32-nightly.20260803.985serverEnvironment
macOS desktop app (nightly), connected to a remote/local server on a newer nightly
Workaround
Manually update/restart the macOS app (Check for Updates / install the newer desktop build) and ignore the "Update server" button.