causet version

Print the version, Git commit, and build timestamp for the installed Causet CLI.

Usage

causet version

Example output

Causet CLI v0.1.0

Commit: a1b2c3d
Built:  2026-07-06T18:42:15Z

Development builds

Running a binary built locally from source (without release ldflags) reports development sentinels:

Causet CLI dev

Commit: none
Built:  unknown

This is expected for local development. Only binaries produced by the release pipeline contain real version metadata.

Compiler version

The bundled causet-compiler binary reports the same metadata via --version:

causet-compiler --version
# or
causet-compiler version

Causet Compiler v0.1.0

Commit: a1b2c3d
Built:  2026-07-06T18:42:15Z

The CLI and compiler always ship as a matched pair. See Version compatibility below.

Version compatibility

Before every compilation the CLI verifies that the compiler reports the same version as itself. If the versions differ, the CLI exits with an error and explains the mismatch:

Error: version mismatch: CLI is v0.1.0 but compiler is v0.2.0

The CLI and compiler must be the same version.
Re-install Causet to get a matched pair:

  https://docs.causet.io/getting-started/install

⚠️

The CLI will never silently continue if versions are mismatched. A mixed installation is always a configuration error.

Where version information comes from

Binary	Source
CLI (`causet`)	Go linker flags injected at build time: `-X internal/version.Version=…`
Compiler (`causet-compiler`)	JAR manifest attributes: `Implementation-Version`, `Build-Commit`, `Build-Date`

Both values originate from the same Git tag. No version numbers are hardcoded in source — see the Release Process for the full pipeline.

causet doctor — also reports cli version as part of its health checks
Release Process — how the Git tag flows into both binaries

What is Causet?