Skip to main content

Documentation Index

Fetch the complete documentation index at: https://mintlify.com/ton-blockchain/acton/llms.txt

Use this file to discover all available pages before exploring further.

acton up downloads and installs Acton CLI releases from GitHub. It fetches the release archive matching your current platform, verifies the SHA256 checksum, and replaces the running binary in place. By default, stable builds update to the latest stable release and trunk builds stay on the trunk channel — but you can switch channels, pin to a specific version, or list all available releases at any time.

​
Synopsis

acton up [VERSION] [OPTIONS]

​
Options

FlagTypeDefaultDescription
VERSIONstring—Specific version tag to install (e.g. 1.2.0)
--trunkflag—Install the most recent trunk (bleeding-edge) release
--stableflag—Install the latest stable release
--forceflag—Reinstall even if already up to date
--listflag—List available release tags and exit (read-only)
VERSION, --trunk, --stable, and --list are mutually exclusive. Use exactly one at a time.

​
Channel selection

Acton tracks which channel you are on and defaults to the appropriate update behaviour:
Current buildCommandResult
Stableacton upUpdate to latest stable
Trunkacton upUpdate to latest trunk
Eitheracton up --stableSwitch to / update latest stable
Eitheracton up --trunkSwitch to / install latest trunk
Eitheracton up 1.2.0Install that exact version regardless of channel

​
Trunk builds

Trunk builds are the bleeding-edge development channel. They receive features and fixes before the stable release, but may contain regressions or breaking changes. Use trunk for early access and testing; prefer stable for production projects.
Trunk builds are released continuously from the main branch. They are suitable for:
  • Testing upcoming features before the stable release
  • Reporting bugs against the latest development state
  • Contributors who need the freshest toolchain

​
Installation flow

When installing a release, acton up:
  1. Fetches release metadata from ton-blockchain/acton on GitHub
  2. Selects the archive matching your current target triple (OS + architecture)
  3. Downloads the archive and its .sha256 checksum file
  4. Verifies the SHA256 digest — aborts if verification fails
  5. Unpacks the archive and replaces the current acton binary
If GITHUB_TOKEN is set in the environment, Acton uses it for authenticated GitHub API requests (higher rate limits). --list is read-only and performs no download or replacement.

​
Pinning a version in Acton.toml

Projects can pin the required Acton CLI version in Acton.toml. When a version mismatch is detected, Acton prints an error with the install command:
Acton.toml
[toolchain]
acton = "1.2.0"
Install the pinned version from the project root: 
acton up 1.2.0

​
Examples

acton up

​
Exit status

  • 0 — release information was listed, Acton was already up to date, or the selected version was installed successfully
  • 1 — release lookup failed, checksum verification failed, or binary replacement failed

​
See Also

Build docs developers (and LLMs) love

Get started for freeTalk to us