# 1. Connection check: the methods this deployment serves
get_session, list_sessions, create_session, delete_session, async_get_session, async_list_sessions, async_create_session, async_delete_session, async_add_session_to_memory, async_search_memory, async_save_artifact, async_load_artifact, async_list_artifact_keys, async_delete_artifact, async_list_versions, async_list_artifact_versions, async_get_artifact_version, stream_query, async_stream_query, streaming_agent_run_with_events

# 2. Conversation 1, in a new session
# 3 s
session 7832467459528458240
> I run shipctl 1.x. How do I undo release r42 in production?
# 5 s
call   read_page {"page":"rollback"}
result read_page
answer In shipctl 1.x, use the `shipctl release revert` command:

```bash
shipctl release revert r42 --env production
```

*(Or simply `shipctl release revert r42` if production is the default environment).*

Note that database migrations are not rolled back automatically—if r42 ran a migration, you must deploy a new migration to reverse it.

# 3. Add the finished session to Memory Bank
{"output":null}
memories after about 25 s: ["I run shipctl 1.x."]

# 4. Conversation 2, in another new session
> How do I undo the last production release?
# 6 s
call   load_memory {"query":"shipctl major version"}
call   read_page {"page":"rollback"}
result load_memory
result read_page
answer Since you are on **shipctl 1.x**, run:

```bash
shipctl release revert <release-id>
```

Specify the release identifier you want to revert back to (you can find previous releases with `shipctl releases`).

Note that database migrations are not automatically rolled back—if the release ran a migration, you'll need to deploy a reverse migration.