> ## Documentation Index
> Fetch the complete documentation index at: https://docs.cloudthinker.io/llms.txt
> Use this file to discover all available pages before exploring further.

# Release Risk

> Check every release tag before it ships, share one verdict with the team, and hold the deploy while a blocker is open.

Release Risk tells your team whether a release can ship. Push a tag, and CloudThinker reads every change since the last release, gives one verdict, tells the team, and holds the deploy while a blocker is open.

## Why use it

* **Know before you deploy.** Each release reads **Blocked** or **Clear to ship**, with the reason behind every blocker.
* **One decision for the whole team.** The report, your chat channel and your CI show the same verdict.
* **The deploy waits when it should.** A `cloudthinker/release` check on the tag stays closed while a blocker is open.
* **Fixes come with the report.** CloudThinker can fix a blocker, or review a change nobody reviewed.

## Prerequisites

* A repository turned on in [Review setup](https://docs.cloudthinker.io/guide/code-review/setup.md), on GitHub, GitLab, Bitbucket or Azure DevOps, with tag events sent to CloudThinker ([Configure webhooks](https://docs.cloudthinker.io/guide/code-review/provider-auth.md#configure-webhooks)).
* The workspace **Admin** role to change settings, analyze, fix or ship anyway. Everyone else can read reports and download the PDF. See [roles](https://docs.cloudthinker.io/guide/security/roles.md).
* To tell the team, a [Slack](https://docs.cloudthinker.io/guide/slack-integration.md), [Microsoft Teams](https://docs.cloudthinker.io/guide/teams-integration.md) or [Google Chat](https://docs.cloudthinker.io/guide/google-chat-integration.md) connection.

## Turn on release checks

**1. Open Releases**

Go to **Review → Releases** and click **Auto-check off**.

**2. Check every new tag**

Turn on **Check every new tag**. Each pushed tag now gets its own report, and the deploy waits while it's blocked.

**3. Pick where the team hears about it**

Under **Post results to**, pick a channel, then click **Turn on**. When a report is ready, CloudThinker posts the verdict, the first blocker and a link to the report.

**Success state:** the button reads **Auto-check on**, and your next tag appears as **Analyzing**.

## Analyze a release by hand

To check a release, branch or commit without pushing a tag, click **Analyze release** on **Review → Releases** and choose the repository. **Not released yet** is preselected when the default branch has unreleased changes; you can also pick a tag or search for a branch or commit. CloudThinker compares it with the previous release, and **Change** picks another base. Click **Analyze**. The report is ready in about 5 minutes, and you can leave the page.

## Read the verdict

**Review → Releases** opens on the **Blocked** tab, beside **Clear to ship** and **All**. Each release shows one status:

| Status | What it means | Deploy check |
| - | - | - |
| Analyzing | CloudThinker is checking the release | Waiting |
| Blocked | At least one blocker is open | Closed |
| Clear to ship | No blocker is open | Open |
| Shipped anyway | An Admin shipped past an open blocker, with a note | Open |
| Analysis failed | The analysis stopped before it finished | None |
| Replaced | A newer report on the same release replaced this one | Read the newer report |

Open a release for its report:

* **Blockers**: what to fix before you ship, plus items **To watch** during rollout.
* **Findings**: the open review findings of the release's merge requests.
* **What's shipping**: release notes and every merge request, grouped by area of the codebase.

## Fix or ship

Each open blocker carries one main action:

| Action | What happens |
| - | - |
| **Check** | CloudThinker reviews a merge request nobody reviewed, then checks the release again |
| **Fix** | CloudThinker fixes that blocker. Follow it in Chat |
| **Mark resolved** | Record that you dealt with it. **Reopen** undoes it |

**Fix all blockers** works through every open blocker at once. When the last blocker is resolved, the release turns **Clear to ship**. A blocker for an unreviewed change also clears on its own once that change is reviewed.

To ship anyway, open the **⋯** menu and click **Ship anyway**. Answer **Why is it safe to ship?** and confirm. The gate opens, and the release shows who shipped it and why. The same menu holds **Download PDF**.

## Make the deploy wait

Each analyzed tag's commit gets a `cloudthinker/release` commit status. It reads pending during the analysis, failed while the release is **Blocked**, and success once it's **Clear to ship** or **Shipped anyway**. On GitLab it appears as an external job in the commit's pipeline.

Have your deploy job wait until that status reads success. It updates whenever the verdict changes, so resolving the last blocker or shipping anyway turns it green without a new tag.

## How it works

1. **A tag arrives.** You push a tag, or someone clicks **Analyze release**.
2. **CloudThinker reads the release.** It compares it with the previous release and reads the real diff and each merge request's review.
3. **One verdict lands.** The report lists blockers and items to watch, with the evidence and how to fix each one.
4. **Everyone sees it.** The deploy check updates and your team channel gets the verdict.

## Troubleshooting

> [accordion] A new tag has no report
>
> Check that **Review → Releases** shows **Auto-check on**, that the repository is turned on in Review, and that your provider sends tag events ([Configure webhooks](https://docs.cloudthinker.io/guide/code-review/provider-auth.md#configure-webhooks)). To check that tag now, click **Analyze release** and pick it.

> [accordion] The release shows Analysis failed
>
> The analysis stopped before it finished. Open the release and click **Analyze again**.

> [accordion] The cloudthinker/release check doesn't show in CI
>
> The check is added to tags only, not to branch or commit analyses. If the check still doesn't appear, make sure the Git connection can write commit statuses, and update its access in [Review setup](https://docs.cloudthinker.io/guide/code-review/setup.md) if needed.

> [accordion] Nobody was notified
>
> On **Review → Releases**, open **Auto-check on** and check that **Post results to** names a channel. If it says **Connect Slack, Teams or Google Chat**, connect one first. Results post once per tag report.

## Related

> [card] [Pipeline Analysis](https://docs.cloudthinker.io/guide/code-review/pipelines.md)
>
> Get a root cause for every failed CI run

> [card] [Review overview](https://docs.cloudthinker.io/guide/code-review/overview.md)
>
> See everything Review does across your repositories

> [card] [Configure webhooks](https://docs.cloudthinker.io/guide/code-review/provider-auth.md#configure-webhooks)
>
> Send tag events from your Git provider

> [card] [Slack integration](https://docs.cloudthinker.io/guide/slack-integration.md)
>
> Connect the channel that receives release results


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