Server

History and rollback.

Inspect verified deployments and rebuild an earlier Git commit.

History and rollback

Inspect recent verified deployments or rebuild an earlier commit from configured branch history.

Recent history#

›shis history example-com

渋み shis (shibumi-server)

2026-08-12T09:03:07Z webhook succeeded 55a26db5c43a 42182ms

2026-08-12T08:44:19Z rollback succeeded 4e5f3223b71d 38914ms

2026-08-12T08:31:02Z webhook failed a15c9e2d773f health 27546ms

3 recent records

shis history example-com
渋み  shis (shibumi-server)
success|2026-08-12T09:03:07Z  webhook  succeeded  55a26db5c43a  42182ms
success|2026-08-12T08:44:19Z  rollback  succeeded  4e5f3223b71d  38914ms
warn|2026-08-12T08:31:02Z  webhook  failed  a15c9e2d773f  health  27546ms
outro|3 recent records

Machine-readable form:

shis history example-com --json

Each app keeps latest 100 records in mode-0600 JSONL. Records contain timestamp, app ID, full commit, operation kind, result, verified GitHub delivery ID, failed stage, and duration when available.

History never stores webhook payloads, signatures, secrets, or request headers.

Roll back by SHA#

shis rollback example-com 4e5f322

SHA may contain 7 to 40 lowercase hexadecimal characters. Git must resolve prefix uniquely. Shibumi fetches configured branch, resolves full commit, and requires commit to be its ancestor. Unknown, ambiguous, or unrelated commits fail before deployment.

Rollback runs normal resource checks, Compose validation, build, optional tests, startup, health checks, status updates, and history recording. It rebuilds source rather than trusting mutable tags.

Use --yes only for confirmed automation:

shis rollback example-com 4e5f322 --yes

Receiver pauses during rollback and restarts afterward, preventing webhook deployment from racing operator action.