gofasta version

Prints a multi-line version block: the CLI version, the Go toolchain the binary was compiled with, and the OS/architecture pair it was built for. It is the block to paste into a bug report, and the quickest way to confirm which binary is actually first on your PATH.

Usage

gofasta version

The command takes no flags of its own. The root command’s global flags apply, including --json.

Example

$ gofasta version
gofasta v0.1.10
Go:      go1.25.0
OS/Arch: darwin/arm64

version versus --version

Two surfaces, two audiences:

Because gofasta version may grow additional lines, do not parse it. Use --version — or better, --json — when a machine reads the result.

JSON output

$ gofasta version --json
{
  "gofasta": "v0.1.10",
  "go": "go1.25.0",
  "os": "darwin",
  "arch": "arm64"
}

These four field names are a stable contract that agents and scripts consume; they will not be renamed. Note that os and arch are separate fields here, while the text form joins them with a slash.

How the version string is derived

The version comes from the release tag when the binary was built from a tagged release, and from Go’s runtime/debug build info otherwise. What you see tells you how the binary got onto your machine:

A leading v is added for semver-like strings that lack one, so the output is consistent regardless of how the tag was injected.

Checking the installed version matches what you expect

After an upgrade, a shell that has cached the old executable’s inode will keep reporting the previous version. If gofasta version disagrees with what you just installed, run hash -r (bash / zsh) or open a new terminal, then check which binary is being resolved:

which gofasta
gofasta --version

A mismatch between the two usually means a second copy is earlier on your PATH — commonly /usr/local/bin/gofasta from the install script shadowing ~/go/bin/gofasta from go install, or the reverse.