Set Up

Setting up releases fully is a multi-step process, and is adaptable to your organization's needs.

Configure Your SDK

With your SDK configured to provide a release identifer and enable session tracking, you can monitor both releases and release health.

Notify Sentry

Notifying Sentry of a release enables auto discovery of which commits to associate with a release and identifies what we consider "the most recent release" when searching in In addition, telling Sentry of a release helps identify new issues, regressions, and whether an issue is resolved in the next release. You do not need a repository integration for any of these features, though we recommend installing a repository integration for efficiency.

The behavior of a few features depends on whether a project is using semantic or time-based versioning.

  • Regression detection
  • release:latest

We automatically detect whether a project is using semantic or time-based versioning based on:

  • If ≤ 2 releases total: we look at most recent release.
  • If 3-10 releases total: if any of the most recent 3 releases is semver, project is semver.
  • If 10+ releases: if any of the most recent 3 releases is semver, and 3 out of the most recent 10 releases is semver, then the project is semver.

Using Release Automation

If you're using Release Automation, let Sentry know you’ve deployed by sending an additional request after creating a release:

sentry-cli releases --org ORGANIZATION_SLUG deploys VERSION new -e ENVIRONMENT

NOTE: Make sure you have a token properly configured.

You can also use our API to create a deploy.


When you notify Sentry that you've deployed a release to a new environment, we can automatically send an email to Sentry users who have committed to the release being deployed.

release ui

Enable Suspect Commits

With an additional repository integration or manual commits, you can also track suspect commits.

  1. Installing a repository integration (this step is optional, but highly recommended)
  2. Associating commits to a release by adding to your release management script when you build a release.
Help improve this content
Our documentation is open source and available on GitHub. Your contributions are welcome, whether fixing a typo (drat!) to suggesting an update ("yeah, this would be better").