Skip to content
Open
Changes from all commits
Commits
File filter

Filter by extension

Filter by extension

Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
21 changes: 21 additions & 0 deletions docs/product/releases/usage/disable-auto-release-creation.mdx
Original file line number Diff line number Diff line change
@@ -0,0 +1,21 @@
---
title: Disable Release Creation
sidebar_order: 50
description: "Learn how to stop Sentry from automatically creating releases from ingested events so you can manage releases yourself."
---

<Alert level="info">

This feature is currently in early access. To access it, enable the Early Adopter flag in your [organization settings](https://sentry.io/orgredirect/organizations/:orgslug/settings/).

</Alert>

By default, Sentry creates a release the first time it sees a new release identifier in ingested events. If you'd rather manage releases yourself, you can turn this off in **Project Settings > General Settings > Event Settings** by disabling **Enable release auto-creation from telemetry**.

When this setting is disabled:

- Sentry no longer creates releases from ingested events.
- Events are still ingested as normal. If the release doesn't already exist, the event just won't have an associated release.
- Events still associate with releases that already exist, so you keep creating releases explicitly, for example using the [Sentry CLI](/cli/releases/).

Copy link
Copy Markdown
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Suggested change
- Events still associate with releases that already exist, so you keep creating releases explicitly, for example using the [Sentry CLI](/cli/releases/).
- Events still associate with releases that already exist, and you can keep creating releases explicitly, for example using the [Sentry CLI](/cli/releases/).


This is useful when you want release names to match exactly what your deploy pipeline creates and don't want extra releases generated from telemetry.
Loading