Learn how to provide information to Sentry about your releases to determine regressions and resolve issues quickly.

A release is a version of your code deployed to an environment. When you notify Sentry about a release, you can easily identify new issues and regressions, determine whether an issue was resolved, and monitor the health of your newly deployed app. The Releases page provides a visualization of your releases. It presents adoption of releases from the past 24 hours and provides a high-level view of:

  • Each release version (a short version of the release name without the hash)
  • The associated project
  • The adoption stage of each release
  • The authors of each commit
  • The percentage of crash-free users
  • The percentage of crash-free sessions

Crash and app hang detection are not available for watchOS.

View of the release index page showing each version of projects related to the release and the project details.

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

Each release links to one or more projects. If a release has multiple projects, Sentry will duplicate the release data in relation to each one. From this page, you can also click any release to go to Release Details for more information.

Releases offer significant additional features when fully configured:

We recommend notifying Sentry about a new release before deploying it. But if you don't, Sentry will automatically create a release entity in the system the first time it sees an event with that release identifier.

You don't need a repository integration for any of these features, though we recommend installing one as part of an automated release option for efficiency.

With releases, you can associate commits, which keeps track of the commits that were used in a release.

You can resolve issues quickly using the Release Details page to view which commits were used to create a release as the list of authors of those commits.

Release health provides insight into the impact of crashes and bugs as it relates to your user's experience and reveals trends with each new issue. Monitor release health by observing user adoption, usage of the application, percentage of crashes, and session data. You can explore the health of a release more closely in the Release Details page.

You can view release health data either from the Issue Details page by selecting the commit ID listed under Last Seen", or from the Releases page.

If you'd like to mark an issue as resolved in both a current and a future release, you can do so by resolving it in a release via the dropdown on the issue details page.

There are several options for resolving a release issue. If you'd like to leave the issue unresolved and be notified of it the next time any event is seen in a release, click the main "Resolve" button. But if you'd like to ignore the release issue until it's seen again in your current or next release, you can select "Resolved In The next release" or "Resolved In The current release" from the dropdown.

View of the resolve issue dropdown options on issue details.

The "Resolved in the current release" option records the current release that's displayed in the UI. New events for the release issue are compared against the recorded release version to determine if the issue should unresolve. If the release version is using semver, the issue will be marked as unresolved if the release is from a semver version that's greater than the resolved version. If the release is not using semver, the release creation dates will be compared.

The "Resolved in the next release" option works in a similar way to resolved in the current release. But because we can't record the resolution version since it hasn't been created yet, we record the current release version and update it when a newer release is created.

The "Resolved in a commit" option allows you to wait for a release with the specified commit to be created. Once the release is created, new events get checked against the release version or release date. If the new events are from a newer release, the issue gets marked as a regression and appears in your For Review tab to be triaged.

Help improve this content
Our documentation is open source and available on GitHub. Your contributions are welcome, whether fixing a typo (drat!) or suggesting an update ("yeah, this would be better").