Rollback and Versions

When the stage/prod pipeline is active, every release to production creates a versioned snapshot of your app. You can list those snapshots at any time and roll back your running production image to any previous one — without touching your database or any other state.

What rollback does and does not do: Rollback reverts the running container image to a previously released version. It does not roll back database migrations, file storage, or any other persistent state. If you need to undo data changes, those must be handled separately.

Prerequisites

At least one release to production must have been made before there is anything to roll back to.

Listing Available Versions

Use the get-myapp-versions tool to see which versions have been released to production for a given app.

Example prompt to your AI agent:

List available versions for my app myappname

The tool returns a list of version tags (e.g. v1.0.0, v1.1.0, v1.2.0) along with the git commit each tag points to and the timestamp when that version was released to production. The entry marked as the current version is what is running now.

Rolling Back to a Previous Version

Use the rollback-myapp-prod tool to revert the production app to any version from the list above.

Example prompt to your AI agent:

Roll back myappname to the previous version

You can also target a specific version tag:

Roll back myappname to v1.1.0

The agent pins the production app to the specified version tag and restarts it. The stage app is not affected; it continues tracking the main branch as usual. Once the rollback completes, the agent confirms the version now running in production.

To return to the latest release after a rollback, run a new release:

Release the current stage to production for my app called myappname

Stage/Prod State After Rollback

After a rollback, get-agentic-sdlc-status reflects the change:

Field Value after rollback
currentProdVersion The version tag you rolled back to
currentStageVersion Unchanged; still tracks main