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
When the web client connects to an older server, the composer banner says Server update available. Its tooltip only shows server 0.0.42 → 0.0.43. Users have to update before they can find out what the update brings.
The desktop app already solves this for its own updates. Its release notes popover shows "What's changed", grouped by version, with links to GitHub.
Proposal
Reuse the desktop mechanism on web instead of building a new one:
Move the desktop release notes parser to @t3tools/shared/releaseNotes. Desktop keeps a thin wrapper, so its behavior and tests do not change.
Lift the sidebar popover's list into a shared ReleaseNotesPanel web component.
Turn "Server update available" into a click popover. It shows the old version line and the target release's notes.
The old server cannot know about newer releases, so the client fetches one release by tag from the GitHub API. The fetch runs only when the popover opens and is cached for the session. It needs no server or contract change, so it works the same over local, relay, and tunnel connections. If GitHub is unreachable, the popover falls back to the version line.
reacted with thumbs up emoji reacted with thumbs down emoji reacted with laugh emoji reacted with hooray emoji reacted with confused emoji reacted with heart emoji reacted with rocket emoji reacted with eyes emoji
Uh oh!
There was an error while loading. Please reload this page.
Problem
When the web client connects to an older server, the composer banner says Server update available. Its tooltip only shows
server 0.0.42 → 0.0.43. Users have to update before they can find out what the update brings.The desktop app already solves this for its own updates. Its release notes popover shows "What's changed", grouped by version, with links to GitHub.
Proposal
Reuse the desktop mechanism on web instead of building a new one:
@t3tools/shared/releaseNotes. Desktop keeps a thin wrapper, so its behavior and tests do not change.ReleaseNotesPanelweb component.The old server cannot know about newer releases, so the client fetches one release by tag from the GitHub API. The fetch runs only when the popover opens and is cached for the session. It needs no server or contract change, so it works the same over local, relay, and tunnel connections. If GitHub is unreachable, the popover falls back to the version line.
A working implementation is on djfbryant/t3code@feat/web-server-update-release-notes. I will open it as a PR for reference; feel free to close it if you would rather take this another way.
All reactions