Updates
The desktop app updates itself. It tells you when a new version is out, and it downloads and installs it only when you ask. The web UI that you run from source has nothing to update; pull the repository and restart it instead.
How the app checks
Section titled “How the app checks”The app checks for a new version 15 seconds after it starts, and every four hours after that. It never downloads on its own.
When a new version is out, you see it in three places:
- A vX.Y.Z available button beside the version at the top of the sidebar. Click it to open Settings › Updates.
- The Status row in Settings › Updates.
- Download update vX.Y.Z in the command palette.
To check at once, run Check for updates from the command palette, or click Check now in Settings › Updates.
Install an update
Section titled “Install an update”- Click Download vX.Y.Z in Settings › Updates, or run Download update vX.Y.Z from the palette. The status row shows the progress.
- When the download is done, the sidebar button changes to Restart to update. Click it, or run Restart to update from the palette.
If you quit the app after a download instead, the update installs as the app quits.
Your sessions keep running in tmux while the app restarts.
Platform notes
Section titled “Platform notes”- macOS: the update installs without a prompt.
- Linux AppImage: the app replaces the AppImage file in place. Keep it in a directory you can write to.
- Linux deb: the app installs the new package with
dpkgwhen it quits, and asks for your password.
After an update, mocante also updates the small helper program it keeps on each remote host the next time it connects to that host. You do not need to do anything.
Update channels
Section titled “Update channels”Pick a channel in Settings › Updates › Update channel, or run Update channel: Stable or Update channel: Beta from the palette.
| Channel | What you get |
|---|---|
| Stable | Tagged releases. This is the default for a release you download from the Latest release on GitHub. |
| Beta | Release candidates, before they become stable. |
| This branch | Test builds of one feature branch. Only a build made from a branch offers this channel. |
Each build starts on the channel it was built for. A beta download starts on Beta, and a branch build follows its own branch.
When you switch channel, the app can go back to a lower version. For example, if you move from Beta to Stable, you get the current stable release even when its version number is lower than the beta you run.
Branch builds
Section titled “Branch builds”A branch build gets each new build of its branch as an update. When the branch has no builds left, for example after it is merged, the app follows Stable for the rest of that run and says so in Settings › Updates. It tries the branch again at the next launch.
See your version
Section titled “See your version”Settings › Updates shows your version and which channel it was built for, such as “v0.28.1, a stable build.” The version also shows at the top of the sidebar.
When an update fails
Section titled “When an update fails”If a check or a download fails, the Status row reads “Update check failed:” followed by the reason. See troubleshooting for what to do.