Versioning
Versioning
Stackie uses Semantic Versioning (MAJOR.MINOR.PATCH)
with channel-specific pre-release suffixes for canary and edge builds.
Version formats
| Channel | Format | Example |
|---|---|---|
stable | MAJOR.MINOR.PATCH | 1.0.1 |
canary | MAJOR.MINOR.PATCH-canary.BUILD | 1.0.1-canary.2455 |
edge | MAJOR.MINOR.PATCH-edge.BUILD+COMMIT | 1.0.1-edge.2457+abc1234 |
| dev build | MAJOR.MINOR.PATCH-dev+COMMIT | 1.0.1-dev+abc1234 |
The BUILD component is the GitHub Actions run number. The +COMMIT suffix
is the first seven characters of the git commit SHA at build time.
Checking your version
From the command line:
stackie --version
From the dashboard, the version is displayed in the bottom-right corner of
the home page as v1.0.1 for release builds or [abc1234] for dev builds.
Version in API responses
The daemon reports its version in the HTTP API. The /version endpoint
returns:
{
"Version": "1.0.1",
"Channel": "stable",
"GitCommit": "abc1234",
"BuildNumber": "2455",
"BuildTime": "2026-03-23T12:00:00Z"
}
The Channel field is omitted from the dashboard badge when the channel is
stable, so the badge only appears for canary and edge builds.
Dev builds
When stackied is not running from ~/.stackie/bin/ (i.e., launched
directly from a development checkout), it runs in dev mode:
- The tray icon turns red.
- The version displayed is
[gitcommit]rather thanv1.0.1. - Automatic updates are disabled.
Dev mode is detected automatically — no configuration is needed.
See also
- Release Channels — which channel is right for you
- Updates — how the update system works