Skip to content
GitHub

bino update

The bino update command allows you to easily upgrade both your bino CLI installation and the template engine to the latest available versions from GitHub Releases.

bino update

When you run bino update, the CLI will update two components:

  1. Check GitHub Releases for a newer version of bino.
  2. Compare the latest version with your currently installed version.
  3. If a newer version is available, download the appropriate binary for your operating system and architecture.
  4. Verify the download integrity by checking the SHA-256 checksum against checksums.txt published in the release.
  5. Replace the current bino binary with the new version.

If the checksum verification fails, the update is aborted and your current installation remains unchanged.

After updating the CLI, bino update also checks for template engine updates:

  1. Query GitHub Releases for the latest template engine version.
  2. Compare with the latest locally installed version (if any).
  3. If a newer version is available (or no version is installed), download it.

The template engine is cached in ~/.bn/cdn/bn-template-engine/ and multiple versions can coexist. By default, bino uses the latest installed version unless a specific version is pinned in bino.toml.

Checking for CLI updates (current: v0.36.0)...
CLI is already up to date.

Checking for template engine updates (current: v0.36.0)...
Downloading template engine v0.37.0...
Successfully updated template engine from v0.36.0 to v0.37.0

If both components are already up to date:

Checking for CLI updates (current: v0.37.0)...
CLI is already up to date.

Checking for template engine updates (current: v0.37.0)...
Template engine is already up to date.

bino automatically checks for updates in the background once every 24 hours when you run any command. If a new version is available, a notification will be printed to the standard error output (stderr) after the command completes.

Example notification:

Update available: 0.1.0 -> 0.2.0
Run 'bino update' to upgrade.

This check is non-blocking and will not delay your command execution.

Automatic update checks are disabled when:

  • The CI environment variable is set (e.g., CI=1 in GitHub Actions, GitLab CI, etc.).
  • The BINO_DISABLE_UPDATE_CHECK environment variable is set to any non-empty value.

This is useful for CI/CD pipelines, air-gapped environments, or IDE integrations where network access should be avoided.