> ## Documentation Index
> Fetch the complete documentation index at: https://help.the-meridian.ai/llms.txt
> Use this file to discover all available pages before exploring further.

# Build history

Build history is the record of every deployment for an app: what was built, from which commit, whether it succeeded, and where its logs live.

## What each entry shows

Each deployment lists its status, the environment it targeted, the trigger, timing, and who started it. Open one to see:

* the **git ref and sha** it was built from,
* the **build** (image tag and digest) it produced,
* the **Cloud Run revision** it released,
* links to its **build and runtime logs**,
* its **event stream**: the step-by-step timeline of the deploy.

Because Meridian deploys [by digest](/deployment), every entry points at the exact image that ran, which is what makes a [rollback](/deployment#rollback) to a previous release deterministic.

## Retention

Build history is kept for **7 days on Lite, 30 days on Pro**, and as agreed on Enterprise. It comes with the plan: a [hosting upgrade](/add-ons) does not change it. Older deployments and releases are removed along with their images and Cloud Run revisions, so they can no longer be rolled back to.

Always kept, whatever their age: the image each environment is running (including one promoted from staging to production), the latest release to roll back to, and the images of open pull request previews. Every other image of the app older than the window is deleted once a day, including builds that never deployed and closed previews.


This documentation is built and hosted on [Mintlify](https://mintlify.com), a developer documentation platform.