jira update¶
- Usage:
jira update [flags] - Aliases:
up
Update the running binary to the latest release. The install channel is detected from the binary itself: a Homebrew install runs brew upgrade through its tap, a release-archive install is replaced in place (checksum-verified, rollback-safe), while Scoop, mise, and go install binaries are owned by their installer — the command reports the exact update command to run instead of touching them.
--dry-run resolves the channel and latest release and reports whether an update is available without changing anything. A live self-replace requires --force in headless, agent, or --no-input mode; an interactive terminal proceeds without a confirmation prompt — running the command is the consent. A from-source build has no update channel and fails with guidance.
Safety¶
--dry-run¶
Report channel and latest release without updating
--force¶
Confirm replacing the running binary
Output fields¶
With --output json, the response envelope's data object carries these fields. Run jira agent schema for the full machine-readable schema.
| Field | Type | Description |
|---|---|---|
channel |
string | |
current |
string | |
dry_run |
boolean | |
hint |
string | |
latest |
string | |
managed |
boolean | |
update_available |
boolean | |
updated |
boolean |
Examples¶
- Report the channel and latest release without changing anything
- Non-interactive (agent / script) update