Rollback

Binary rollback is safe only when the older release supports the current schema. When a migration has crossed that boundary, restore the matching pre-upgrade archive instead.

Binary-only rollback

curl -fsSL https://trestle.dev/update.sh | sh -s -- --rollback

1. Stop the failed release.
2. Confirm the older version accepts the current schema.
3. Restore the retained executable and start once.
4. Verify version, readiness and critical workflows.

Data rollback

1. Stop Trestle and preserve the failed data directory for investigation.
2. Run restore preflight against the pre-upgrade archive.
3. Restore offline into a new owner-only directory.
4. Start the matching older binary against that directory.