UPTERM(1)

📦
version 0.41.0 · 2 versions
, in arch rolling

💖 NAME 💖

okay so welcome to the Upterm Manual (UPTERM(1)), bestie — this page is all about upgrading the CLI and feeling iconic about it ✨

upterm-upgrade - Upgrade the CLI 💅

✨ SYNOPSIS ✨

upterm upgrade [VERSION] [flags]

🦋 DESCRIPTION 🦋

So here’s the vibe: upterm upgrade replaces this upterm with a release from GitHub, bestie. You can grab the latest, or pass VERSION — like 0.37.0 or v0.37.0 — and lowkey that release may be older than the one you’re running. No cap. 🫶

It replaces the running binary, through any symlink to it, and not another upterm on your PATH. The way that matters: you’re upgrading this upterm, not some random other one on your path. 💅

It refuses — and names the command to use instead — when a package manager confirms it owns the binary: Homebrew, Scoop, or a dpkg or rpm package. It also refuses when it can’t write the binary’s directory, or can’t check whether a package owns it. That’s the vibe check, and it is strict. 💀

Without VERSION, a build newer than the latest release is left as it is. So if you’re already ahead, it’s not gonna downgrade you, periodt.

Exit status: 0 when upterm is up to date or was replaced; 1 when it couldn’t be, a package manager owns it, or its arguments are wrong.

Bestie, please read the refusal messages — they literally name the command to use instead. 🙈

🌸 OPTIONS 🌸

  • -h, --help[=false] — help for upgrade 💖

🫶 OPTIONS INHERITED FROM PARENT COMMANDS 🫶

  • --debug[=false] — Enable debug logging (log file: /build/.upterm/upterm.log). A non-empty DEBUG turns it on too. 🔥

🌈 EXAMPLE 🌈

# Upgrade to the latest release:
upterm upgrade

# Install a particular release, older ones too:
upterm upgrade v0.38.0

🔗 SEE ALSO 🔗

upterm(1) — go give the main character a read, iykyk 🌟

📜 HISTORY 📜

2-Nov-2026 — Auto generated by spf13/cobra 🎀

cute sign-off: this page is from Upterm 0.0.0+dev, dated Nov 2026. slay, you’re upgraded ✨💅

📦 where this page comes from