kamakiri rollback

Usage

kamakiri rollback <deploy_id> [--no-wait]

<deploy_id> is one of the ids kamakiri deploys lists. The rollback restores that deploy’s files, redirects and headers without uploading anything, and purges the CDN cache when a CDN is configured.

$ kamakiri rollback 20260919-165349-736
Rolled back to 20260919-165349-736
✓ live: https://my-site.kamakiri-pages.jp
$ kamakiri rollback 20260919-165349-736
20260919-165349-736 にロールバックしました
✓ 公開中: https://my-site.kamakiri-pages.jp

It waits the way kamakiri deploy waits: it returns once a visitor gets the restored deploy, and a cache flush only you can unblock stops it with a ✗ line in the same way.

--no-wait returns as soon as the rollback is accepted. The → line it prints is the site’s address, not a sign that it serves the restored deploy yet, and kamakiri status shows the progress.

A deploy that is already live

Asking for the deploy being served changes nothing and does not wait.

$ kamakiri rollback 20260919-165349-736
Deploy 20260919-165349-736 is already live.
$ kamakiri rollback 20260919-165349-736
デプロイ 20260919-165349-736 は既に公開中です。

A deploy that cannot be restored

An id the site does not keep is refused as not found, whether it never existed or has been pruned.

A deploy whose _redirects or _headers holds a rule the service no longer allows cannot be rolled back to. Deploy the same files again with that rule corrected.

Exit status