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, whether an issue is resolved in the next release, and apply source maps.
Releases also offer significant additional features when you fully configure your SDK:
- Determine the issues and regressions introduced in a new release
- Predict which commit caused an issue and who is likely responsible
- Resolve issues by including the issue number in your commit message
- Receive email notifications when your code gets deployed
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.
The Releases page provides a high-level view of:
- Each release version
- 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
Each release links to one project. If a release has multiple projects, Sentry will duplicate the release data in relation to each project.
The page presents adoption of the release from the past 24 hours.
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 view release health data either from the Issue Details page by selecting the commit ID listed under Last Seen, or from the Releases page.
Suspect commits predict which commit caused an issue and who is likely responsible. Sentry uses commit metadata from your source code repositories to identify the suspect commit.
You can resolve issues quickly using the Issue Details page to view suspect commits as well as the list of authors of those commits. In addition, we can automatically assign or alert the issue owner, based on your organization's ownership rules.