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, 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
- Receiving 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.
After configuring your SDK and notifying Sentry, you can view information about the release, such as new issues and regressions introduced in the release.
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.
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.