version

Introduction

splent version shows the versions your workspace runs, with a fingerprint. Two workspaces with the same fingerprint run the same versions, so paste it when you report a bug or compare two machines.

splent version

SPLENT workspace snapshot
────────────────────────────────────────────────────────
  CLI            1.49.0
  Framework      1.30.0      ✔ compatible
  Python         3.13.18
  Product        my_first_app  0.0.1

  Features declared in pyproject:
  ├── splent_feature_auth              @v1.19.4            ✔ in cache
  ├── splent_feature_notes             editable            ✔ workspace root
  └── splent_feature_profile           @v1.4.2             ✔ in cache
────────────────────────────────────────────────────────
  Fingerprint  cf65705b

Reading the snapshot

Line	Shows
CLI, Framework	The version this Python runs. For an editable install, the version in its checkout’s `pyproject.toml`. `unknown` when neither is found
`✔ compatible`	The CLI and the framework share their major version. Otherwise `✖ mismatch`
Python	The running interpreter
Product	The selected product and its version, or `(not selected)`
Features	Each entry of `[tool.splent].features`, pinned or `editable`, and whether it was found `in cache`, at the `workspace root` or `not found`
Fingerprint	Eight characters hashed from every version above, the Python patch level included

features_dev and features_prod are not listed.

Getting JSON for a script

splent version --json

{
  "cli": "1.49.0",
  "framework": "1.30.0",
  "python": "3.13.18",
  "compatible": true,
  "product": {
    "name": "my_first_app",
    "version": "0.0.1",
    "found": true
  },
  "features": [
    {
      "name": "splent_feature_notes",
      "version": null,
      "location": "workspace",
      "ref": "splent-io/splent_feature_notes"
    }
  ],
  "warning": null,
  "fingerprint": "cf65705b"
}

location is cache, workspace or missing. With no product selected, product is null and features is empty.

Advanced

When SPLENT_APP names a directory that does not exist, the text shows ✖ not found and the JSON has "found": false. When the product’s pyproject.toml is not valid TOML, the command prints the parser error in place of the features, puts it in warning, and still exits 0.

Reference

Option	Description
`--json`	Print JSON, for CI and scripts