Skip to main content
Live. This area is documented as current, user-reliable behavior.

​
Goal

Install a release through a supported channel and verify the resulting executable.

​
Prerequisites

  • Homebrew on macOS, Scoop on Windows, or cosign for the signed release installers
  • An amd64 or arm64 system running macOS, Linux, or Windows

​
Workflow

1
Choose the package channel for your operating system.
2
Install the CLI without bypassing signature or checksum verification.
3
Run stackshift version to confirm the installed build.
4
Use the same package manager, or the verified self-updater, for future releases.

​
Homebrew on macOS

The public StackShift tap installs a formula from the signed release source archive. Homebrew installs its Go build dependency automatically.

​
Scoop on Windows

​
Signed installer on macOS or Linux

The installer requires an exact release tag and cosign. It verifies the Sigstore bundle for checksums.txt, then verifies the selected archive SHA-256 digest.

​
Signed installer on Windows

​
Check and apply updates

The self-updater supports macOS, Linux, and Windows on amd64 and arm64. It requires cosign, verifies the release workflow identity and checksum, and requires --yes before replacing the current executable.

​
Expected result

stackshift version prints the release version, commit, and build date for your platform.

​
Common failures

  • cosign is missing when using an installer or self-update.
  • The requested version is not an exact vMAJOR.MINOR.PATCH release tag.
  • The current executable is in a location the user cannot replace.
  • A package-manager shell has not refreshed PATH after installation.

StackShift CLI overview

Install the CLI, authenticate securely, select a project, and run the first customer API workflow.

Diagnostics, completion, and troubleshooting

Check version compatibility, produce sanitized diagnostics, install completion, and resolve common failures.