Updates

Bikube checks GitHub for a newer release by itself and offers it in the sidebar. On macOS and with the AppImage it downloads and installs the update for you; with the .deb it takes you to the release to download it. This page explains each step.

How Bikube checks

Bikube looks for the latest release at launch and every four hours. To check now, open Settings, About, and click Check for Updates, or on macOS pick Bikube › Check for Updates… in the menu bar. The popup that opens says what it found: Bikube is up to date, an update, or Couldn't check for updates with the reason.

When there is a newer version, Update Available: 0.9.2 shows at the bottom of the sidebar, above Settings. Click it for the update's version, size and release date, its View Release Notes link, and three buttons.

Install and Relaunch

On macOS (Apple silicon) and with the AppImage, Bikube downloads the update as soon as it finds it; the button shows Downloading… 42%. It then checks the file against the SHA-256 checksum GitHub publishes for it, and the button becomes Install and Relaunch.

Install and Relaunch quits Bikube, replaces the app it runs from, and opens the new version. When cards or shells are running it asks first: Bikube quits, installs the update and opens again. 2 terminals are running and will be stopped. As with any quit, every running terminal stops; your board, kept output and agents' sessions stay, so opening a card afterwards resumes its agent.

• On macOS, Bikube replaces the inside of its own Bikube.app, so it updates in Applications on a standard (non-administrator) account too.
• An AppImage is replaced where it is, so it needs a folder you can write.

Later

Later hides the update until the next launch, or until you check for updates yourself. An update that has already downloaded installs the next time you quit Bikube (the popup says Or it installs when you quit Bikube.).

Skip

Skip ignores that version: Bikube doesn't offer it again, only a newer one. You can still get it with Check for Updates, where its button reads Download Update.

Installs that link to the release

With the .deb, and with any copy of Bikube it can't replace (such as an AppImage in a folder you can't write), Bikube doesn't install updates itself. The popup says This copy of Bikube can't replace itself and its button is Download, which opens the release page. Install the new .deb as before (see Install):

sudo apt install ./bikube-<version>-amd64.deb

If an automatic download fails, the popup shows why and its button also becomes Download.

Not ready yet

Right after a release is published, its files may still be uploading. The popup then reads The download for 0.9.2 isn't ready yet with a disabled Not Ready Yet button, and Bikube checks again in a few minutes.