rollback: HTTP 200 · answered
To undo a staging deployment in shipctl 3.5, list known releases with `shipctl releases --env staging`. Then run `shipctl rollback --env staging --to RELEASE_ID`.

To deploy a staging release with shipctl 3.5, run `shipctl deploy --env staging --release RELEASE_ID`. Confirm the release with `shipctl status --env staging`.
rotate-token: HTTP 200 · answered
To rotate an API token in shipctl 3.5, create a replacement with `shipctl token create --name rotation`. Update the application's secret store and check a request before revoking the old token with `shipctl token revoke TOKEN_ID`.

Never put an API token in documentation, a shell history or a support message. These instructions use TOKEN_ID as a placeholder, not a credential.
previous-version: HTTP 200 · answered
In shipctl 3.4, deploy with `shipctl deploy staging --tag RELEASE_ID`. Check the result with `shipctl status staging`. Version 3.5 replaces positional environments with `--env`.

In shipctl 3.4, undo a staging deployment with `shipctl rollback staging RELEASE_ID`. Check the active release with `shipctl status staging`.
production: HTTP 200 · answered
Production deployment requires a reviewed release and approval from the on-call maintainer. A maintainer runs `shipctl deploy --env production --release RELEASE_ID --approval APPROVAL_ID`.

If production health checks fail, the maintainer follows the approved rollback runbook and records the release ID in the incident. A reader token cannot retrieve this collection.
repeat-rollback: HTTP 200 · answered
To undo a staging deployment in shipctl 3.5, list known releases with `shipctl releases --env staging`. Then run `shipctl rollback --env staging --to RELEASE_ID`.

To deploy a staging release with shipctl 3.5, run `shipctl deploy --env staging --release RELEASE_ID`. Confirm the release with `shipctl status --env staging`.
unknown: HTTP 200 · abstain
I could not find supporting documentation for that question in this collection and version.
reader-denied: HTTP 403 · Collection access denied
Provider: extractive. Saved 7 real HTTP activities.
