~/.stampede. Most releases need nothing else, but some move the store to a new schema at first start, and that step is one way: the older binary then refuses the store as newer than itself. The procedure below works for every release and makes the way back explicit.
Procedure
Run every step as the service user, with no request running. Read the release’s entry in the release notes first for its behaviour changes.1
Download and verify
Download the new Do not continue unless the check prints
stampede-linux-x86_64 and SHA256SUMS into a fresh directory, and compare the sha256 with the value in the release notes:stampede-linux-x86_64: OK and the sha256 matches the release notes.2
Stop the workers
3
Keep the old binary and back up the home
4
Install the new binary
config.toml that holds a key it does not know, so add new keys only after the new binary is installed.5
Reinstall the units
service install rewrites the units for the new version and starts the workers. A plain restart keeps the old unit files. Every worker should show running.6
Check the installation
FAIL. See Services and doctor for each row../install.sh --name NAME with the newer tree replaces the binary and reruns service install. Stop the workers and back up the home first in the same way.
Rollback
When the release did not move the schema:stampede service uninstall webhook with the newer binary still installed and check that the unit is gone. An older binary cannot run or remove a webhook unit.
Store schema and configuration changes
The migration runs on the first start of the new binary, whichever command starts first.
Behaviour changes per release
Runs in flight
A run recorded by an older binary may be refused automatic resume after the upgrade when the release changed what the run’s access means or what tools it has. It is refused rather than resumed under different rules. Finish or conclude long runs (stampede runs conclude RUN_ID) before upgrading if you need them to complete.
Going back to an older binary has a similar limit: a run recorded by a newer version can carry state the older binary reads as corrupt. Finish or conclude those runs before downgrading.