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.…