An update screen has to answer two different questions: which version is running here, and what has actually been published? A tag pushed to GitHub is not enough to answer the second question. A failed release workflow can leave a tag behind without producing a GitHub Release.
AIClaw 3.11.5 adds an About page that brings the installed version, an update check, and recent release notes into settings. The useful part is how it keeps local version information and remote release history independent.
Read the installed version locally
The About view asks the existing Electron bridge for the application version. It separately loads release notes through a read-only IPC endpoint. A failed history request therefore does not prevent the page from showing the local version.
The Check for updates button uses the existing update action. It does not infer update availability from the list of release notes. That keeps browsing release history separate from deciding whether a newer version is available.
Show releases, not every tag
The release-notes reader requests the project’s public GitHub Releases endpoint with a ten-second timeout. It accepts only entries explicitly marked as neither drafts nor prereleases, with a published timestamp and a tag matching the stable vX.Y.Z form.
The implementation requests the first ten API results, filters them, and returns at most ten notes. That is a bounded recent history, not a complete archive: if the first page contains prereleases, the resulting list can have fewer than ten entries. A tag with no published release never enters this list.
Each accepted entry contains the tag, publication time, note body, and a release link. The link is constructed from the fixed AIClaw repository address and validated tag rather than copied from a response-provided URL. Note bodies are capped at 100,000 characters per entry and displayed through the existing Markdown renderer.
Keep failure distinct from an empty history
The page has separate loading, failure, and empty states. A failed HTTP request or an invalid top-level response stays an error; it is not converted into an empty list that could misleadingly suggest there are no releases. The failure state provides a retry button. A published entry without a note body gets its own “no release notes” message.
This is still an online history view. It does not provide an offline archive, paginate through every past release, or prove that a downloaded installer has been exercised on a particular machine.
Evidence and scope
The release-note tests cover stable-release filtering, fixed-repository links, and preservation of HTTP and invalid-response errors. The desktop smoke suite also checks that the About page displays the application version and release notes.
The 3.11.5 release notes report a passing local make check, including 381 work UI checks, plus release-note tests under Node 22 in a Linux container. Those checks are distinct from live acceptance of every installer. The GitHub Release itself is now publicly published.
A small About page can make version support less ambiguous: the installed version comes from the application, the history comes from published releases, and a network failure remains visible as a network failure.
