> For the complete documentation index, see [llms.txt](https://docs.flxbl.io/flxbl/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.flxbl.io/flxbl/codev/ci-cd/overview-2.md).
# Releases
The Releases page showing deployed releases across domains
The Releases page is your record of what is actually deployed. Every release candidate that has been promoted through the [Release action](/flxbl/codev/ci-cd/managing-release-candidates.md#release), approved, and deployed appears here.
Think of this as your deployment history — organized by domain and linked to the exact work items and package versions that were deployed.
## What you see
Releases are grouped by domain, just like release candidates. For each release you can see:
* When it was deployed
* Which work items were included (with cumulative totals so you can see the full scope)
* The exact package versions that were deployed
* Which environments it was deployed to
The stats bar shows how many domains have releases, the total count, how many were deployed this week, and the age of the oldest release.
## Releases vs. release candidates
Release candidates live on the **Release Candidates** page and represent what is *ready* to deploy. Releases live here and represent what *has been* deployed.
Once a release candidate is approved and deployed, it appears on this page. The release candidate itself remains visible on the Release Candidates page with an updated DEPLOYED TO indicator.
## Creating a hotfix from a release
If you need to patch something that is already in production, click the patch action on the release row. This works the same way as [patching from a release candidate](/flxbl/codev/ci-cd/managing-release-candidates.md#patch) — it creates a hotfix branch from the exact state of that release.
## Rolling back to an earlier release
If a release caused a problem, you can return an environment to an earlier release using the rollback action on the release row. codev checks whether the rollback is cleanly reversible before re-deploying, and steers you to a forward patch when it isn't. See [Rolling back a release](/flxbl/codev/ci-cd/rollback.md).
## Related
* [Rolling back a release](/flxbl/codev/ci-cd/rollback.md)
* [Release Candidates: Review and deploy candidates](/flxbl/codev/ci-cd/overview-1.md)
* [Managing Release Candidates: Release, Sandbox, Patch actions](/flxbl/codev/ci-cd/managing-release-candidates.md)
* [Builds: How packages are built](/flxbl/codev/ci-cd/overview.md)
---
# Agent Instructions
This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com.
## Querying This Documentation
If you need additional information that is not directly available in this page, you can query the documentation dynamically by asking a question.
Perform an HTTP GET request on the current page URL with the `ask` query parameter, and the optional `goal` query parameter:
```
GET https://docs.flxbl.io/flxbl/codev/ci-cd/overview-2.md?ask=&goal=
```
`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is optional and describes the broader end goal you are ultimately trying to accomplish on behalf of the user. GitBook uses it to tailor the answer towards what is most useful for that goal.
The response will contain a direct answer to the question and relevant excerpts and sources from the documentation.
Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.