Docs
Command reference

acton up

Reference manual for the acton up command

Synopsis

acton up [options] [version]

Description

Download and install a published Acton release for the current target triple.

By default, stable builds update to the latest stable release. Trunk builds stay on the trunk channel unless --stable is passed explicitly.

The updater fetches release metadata from GitHub, downloads the matching archive and SHA256 checksum, verifies the checksum, and replaces the current binary.

Options

Update Options

<version>

Specific version tag to install.

Conflicts with:

--trunk, --stable, --list, --rollback

--trunk

Install the most recent trunk release.

Conflicts with:

--stable, --list, version, --rollback

--stable

Install the latest stable release.

Conflicts with:

--list, version, --trunk, --rollback

--force

Install the selected release even if Acton is already up to date.

Conflicts with:

--list, --rollback

--rollback

Roll back to the previous version from a local backup.

Available since: trunk
Conflicts with:

version, --trunk, --stable, --force, --list

--list

List available release tags and exit.

Conflicts with:

version, --trunk, --stable, --force, --rollback

Display Options

--color<when>

Control when to use colored output.

Possible values:

auto, always, never

Default:

auto

Project Options

--manifest-path<path>
Pass-through:

Accepted as a global Acton option for CLI consistency.

This command does not require an existing project manifest for its primary workflow. It remains mutually exclusive with --project-root.

Conflicts with:

--project-root

--project-root<path>
Pass-through:

Accepted as a global Acton option for CLI consistency.

This command does not require an existing project root for its primary workflow. It remains mutually exclusive with --manifest-path.

Conflicts with:

--manifest-path

Release Source

Acton queries GitHub release metadata and assets from ton-blockchain/acton.

If GITHUB_TOKEN is set, Acton uses it for authenticated GitHub API requests.

Installation Flow

When installing a release, Acton:

  • selects the archive matching the current target triple
  • downloads the archive and its .sha256 file
  • verifies the SHA256 digest
  • unpacks the archive
  • keeps a copy of the replaced binary next to it, named acton-<version>
  • atomically replaces the current acton binary

acton up --list is read-only and skips download or replacement.

Interactivity

  • --force bypasses the usual up-to-date short-circuit for the selected release
  • up-to-date checks and --list can succeed without making local changes

Channel Selection

  • acton up on a stable build updates to the latest stable release
  • acton up on a trunk build stays on trunk
  • acton up --stable switches a trunk build back to stable
  • acton up --trunk switches to the trunk channel
  • acton up <version> installs the explicit version even if it is older or newer than the current one

Rollback

acton up --rollback restores the most recently modified backup from the directory of the current binary and works fully offline. It never downloads anything and never creates or overwrites backups, so running it again is a no-op once the restored version is current.

Available since: trunk

Exit Status

  • 0: The requested release information was listed, Acton was already up to date, the selected version was installed successfully, or the previous version was rolled back.
  • 1: Release lookup failed, checksum verification failed, archive replacement failed, or no backup was available to roll back.

Examples

  1. Update to the latest stable release:

    acton up
  2. Switch to the trunk channel:

    acton up --trunk
  3. Install a specific version:

    acton up 1.0.0
  4. List available releases:

    acton up --list
  5. Reinstall the currently selected channel version:

    acton up --force
  6. Update to the latest stable release explicitly:

    acton up --stable
  7. Roll back to the previous version:

    acton up --rollback

See Also

Last updated on

On this page