tapid upgrade

Why Tapid currently uses the public installer instead of an in-client self-update command.

Status

tapid upgrade is still not part of the current CLI. The incomplete command was removed from the latest release rather than shipped as a partial self-update flow, so running it returns an unrecognized-subcommand error.

The release and installer work you may have seen improved the public installation path. It did not add an in-client updater: release authorization, artifact verification, rollback protection, and interrupted-replacement recovery still need to be designed and exercised together before that command is exposed.

Current upgrade path

Use the version-tagged installer below to install the latest stable release again. Re-running that installer is the supported upgrade path. It checks the archive against its SHA256SUMS entry and stages the binary before replacing the existing installation.

Install Tapid 0.0.9

Download the installer from the version tag, inspect it, and run it with the same explicit version.

macOS and Linux

$ (
$ installer="$(mktemp)" || exit 1
$ trap 'rm -f "$installer"' EXIT HUP INT TERM
$ curl -fsSL https://raw.githubusercontent.com/LimeTip/tapid/v0.0.9/scripts/install.sh -o "$installer" || exit 1
$ if command -v less >/dev/null 2>&1; then
$   less "$installer" || exit 1
$ else
$   cat "$installer" || exit 1
$ fi
$ sh "$installer" --version v0.0.9
$ )

Windows PowerShell

$ $installer = Join-Path $env:TEMP "tapid-install.ps1"
$ Invoke-WebRequest https://raw.githubusercontent.com/LimeTip/tapid/v0.0.9/scripts/install.ps1 -OutFile $installer
$ Get-Content $installer
$ & powershell.exe -NoProfile -ExecutionPolicy Bypass -File $installer -Version v0.0.9
$ Remove-Item $installer

To install another specific published version, use that release's version-tagged installer instructions in the repository. Do not treat a source checkout, mutable branch, or successful download as independent release authentication.

Not currently supported

There is no tapid upgrade syntax or working self-update flag to document.
The current installer uses HTTPS and GitHub release checksums, but does not claim an independent signing trust root.
Re-running the installer is a replacement install, not an authenticated in-process upgrade transaction.