Upgrade
ubik upgrade fetches the latest release, verifies its SHA256, and swaps the binaries in place. Explicit and one-shot, never automatic.
ubik upgrade updates the binary in place. It is explicit and one-shot: ubik
never auto-updates and never checks for updates at runtime, so a running
pipeline's binary is untouched until you upgrade and restart it.
Check first
--check reports whether a newer release exists and downloads nothing.
ubik upgrade --checkubik is up to date (v0.0.5).Upgrade
ubik upgradeIt reads SHA256SUMS from the release channel, fetches this platform's tarball,
verifies the checksum, and atomically renames the new ubik and ubik-engine
over the old. A checksum mismatch installs nothing. A live engine keeps its inode
until it restarts, so an upgrade never disturbs a running pipeline.
The channel
The channel is https://getubik.dev/releases/latest, a stable directory serving
the newest release's tarballs and their SHA256SUMS. The tarball names carry the
version; the hashes pin the download.
curl -s https://getubik.dev/releases/latest/SHA256SUMS08bdf5547bca84b9a7cd1fa0987c418d0644417655f2b581466fa41d426cb342 ubik-0.0.5-darwin-arm64.tar.gz
239fce1ef936943fa79cd6ee2121059c42292e8e362bf65c502e5ad480f71ed8 ubik-0.0.5-linux-amd64.tar.gz
efba8984b3f5c4049f0f36a121b1a8f709a50d4771ca639f15a19c240d95ce07 ubik-0.0.5-linux-arm64.tar.gzOverride the channel with UBIK_RELEASE_BASE to point at a mirror, an internal
channel or a GitHub release.
UBIK_RELEASE_BASE=https://mirror.internal/ubik ubik upgradebrew and pip update themselves
A brew install or pip install ubik-sql updates through its own package
manager, not through ubik upgrade. Use ubik upgrade for the tarball install
from the download page.
Upgrading a pipeline
Because a running engine holds its own inode, an upgrade does not touch a live pipeline. Restart it to pick up the new binary; it resumes from its checkpoint, losing and double-counting nothing (see exactly-once).
ubik upgrade
ubik pipeline stop orders
ubik pipeline start orders