Skip to main content
Skip to main content

b version

List all versions. If arguments are given, it shows the version of the specified binaries. Also displays env file status including remote update checks.

Alias

  • v

Usage

b version [binary...] [flags]

Examples

Show all versions

Run without arguments to see the version of b, all binaries, and all env entries in your b.yaml.

b version

Example output:

b version v0.5.0

Binaries:
jq jq-1.7 (latest: jq-1.7.1, update available)
kubectl v1.28.0 (up to date)

Envs:
github.com/org/infra v2.0 @ abc1234 (up to date)
github.com/org/shared-config latest @ def4567 → ghi8901 (update available)

Show specific binary version

Pass a binary name to see its version.

b version jq

Show multiple binary versions

b version jq kubectl helm

Show only local versions

The --local flag prevents b from checking for new remote versions (both binary and env).

b version --local

Check if versions are up to date

The --check flag can be used in scripts to verify if binaries are up to date. It will exit with a non-zero status code if any binary is outdated.

# Check if all versions are up to date (exit code based)
b version --quiet --check

# Check specific binaries
b version jq kubectl --check

Env remote checks

For each env entry in b.yaml, b version uses git ls-remote to check if the pinned commit in b.lock matches the latest commit on the remote. This tells you at a glance whether upstream has changed since your last sync.

Use --local to skip remote checks (useful offline or in CI).

Flags

FlagDescription
--checkCheck if versions are up to date (exit code based)
-h, --helphelp for version
--localOnly show local versions, no lookup for new versions

Global Flags

FlagDescription
-c, --config stringPath to configuration file (current: /home/fentas/github/fentas/b/.bin/b.yaml)
--forceForce operations, overwriting existing binaries
-q, --quietQuiet mode
-v, --versionPrint version information and quit
Was this section helpful?