Upgrade command#

Usage:
  zyn upgrade [--channel stable|edge | --version VERSION] [--check] [--json]

Install or check Zyn releases without changing projects.

Example:
  zyn upgrade --channel edge

Documentation: zyn docs cli/upgrade

Upgrade a bootstrap-managed Zyn installation on Linux or macOS:

zyn upgrade
zyn upgrade --check

zyn upgrade uses the saved channel, initially stable. --check reports availability without downloading a bundle or changing the installation. Run as a user with write access to the installation; the command never invokes sudo.

Choose a channel or version#

zyn upgrade --channel edge
zyn upgrade --version 1.2.3

--channel stable|edge saves the choice for this installation after a successful upgrade, not in the project. --version accepts an optional leading v and leaves the saved channel unchanged. Ordinary upgrades refuse downgrades; use an explicit channel or version to downgrade. A promoted stable release may still report its embedded edge version.

Installation#

For a first install, or to replace a source-built or unmanaged copy, follow Getting started. Downloads and upgrades require no token. Legacy ZYN_TOKEN values and saved download-token files are ignored and are not sent to the download origin.

Automation#

zyn upgrade --check --json

Commands do not prompt. --json emits one JSON object and a newline. Results include schema_version: 1, status, previous_version, installed_version, target_version, and channel. Statuses are updated, up_to_date, and update_available (check only). Errors include schema_version: 1, status: "error", and code.

Exit status is 0 for success, including checks finding an available update; 1 for operational failures; and 2 for invalid arguments. Use the JSON status to distinguish an available update from a no-op.