Runtime 0.8.12
Upgrade safely
Back up first, choose the correct release channel, and check the node after updating. 0.8.12 is the current regular release; plain rh update installs it.
Back up and choose a channel
For SQLite, stop the node before copying ~/.rivethub/memory.sqlite, or use SQLite’s backup command while it runs. Back up config, users file and the configured wiki directory too. For Postgres, dump and restore as a superuser; forced row-level security prevents an ordinary table owner’s dump. Back up each wiki scope’s git repository. Operations reference has the exact procedures.
$ rh version$ rh update0.8.7 was the first regular release; the builds before it were prereleases. Stable is the default, so plain rh update installs the latest regular release and refuses an automatic downgrade. Beta chooses the highest published version including prereleases; pass --channel beta each time, because the channel is not remembered. An rh older than 0.8.7 may need --channel beta once, or the one-line installer again, to reach it. Pinning a tag deliberately selects that release:
$ rh update --version v0.8.12The updater checks release checksums and runs the new migrator before replacing binaries. It keeps rh.previous and rivethub-migrate.previous beside the new binaries. On Linux it restarts a service or a detached node, preserving the detached node’s bind flags. On macOS, pass --no-restart and restart the node yourself. --no-restart leaves restart to you. A hub with cloud disabled fetches GitHub releases.
$ rh status$ rh doctorStandalone: 0.8.3 to 0.8.4
After backing up, run rh update. The released upgrade was tested from 0.8.3: SQLite migrations apply, both binaries are replaced, and the command restarts a detached node or rivethub.service. Captured data stays intact; a new session captures and can be recalled. A second update says it is up to date.
Updating again from 0.8.4 with the service: on Linux, an rh update run by 0.8.4 that installs a release rewrites rivethub.service to start rh (deleted), which systemd cannot run. The update exits normally and the node stays down. This is fixed in 0.8.5: an update run by 0.8.5 or newer leaves the unit as it is, and rh status names the repair when a unit is in that state. Run rh service restart afterwards: it rewrites the unit and starts the node. Hooks keep their sessions while the node is down and deliver them once it is back. The update from 0.8.3 is not affected, and neither is a node without the service.
Check rh version, rh status and rh doctor, then capture a short session and inspect its actual memory_search result. For service installs, check rh service status too.
Datahub: schema 62 to 75
0.8.4 requires Postgres schema 75, up from 62 in 0.8.3. A migration from 62 to 75 passed a three-person hub rehearsal. Back up as a superuser and back up every wiki scope before migrating; use the backup and migration procedures in Operations reference.
Use the new release’s migrator against the intended datahub database:
$ rivethub-migrate postgres --url "$RIVETHUB_PG_URL"You can use --config FILE instead. Check the resulting schema:
$ rivethub-migrate status postgresrh update runs the new migrator against the configured backend before swapping binaries and restarting the node. Services never migrate on start and refuse a schema behind their requirement. Check rh doctor and rh db status --url <url> against this database. Migrations are forward-only: restoring an old binary does not undo them; use a compatible backup if a rollback is required.
Earlier upgrade notes
- 0.8.0 to 0.8.1: credentials are required on loopback. Owner tokens work only directly on loopback with a loopback Host and no forwarded headers. Team drop routes are off until enabled; share login changed to OAuth device sign-in, so sign in again. Receive now holds flagged bundles with exit 3.
- 0.8.1 to 0.8.2: local TLS capture authentication was fixed. After upgrading, run
rh capture spool --requeue-dead; the next hook retries saved batches. - 0.8.2 to 0.8.3: standalone service units now use the right command and init enables them. 0.8.4 repairs older generated units automatically; see the service guide. The updater now handles nodes without a unit and guards against automatic downgrades. Reconnect OpenCode to install its embedded capture plug-in.
The upgrades through 0.8.3 kept Postgres schema 62; 0.8.4 requires the migration to 75 above. Operations reference contains the full upgrade notes.
Need a hand?
Check the troubleshooting guide or ask with a redacted report.