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 is resolved in the next release, and apply source maps or other mapping files. 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

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:

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.

Apply Source Maps or Other Debug Files

Releases are required to apply source maps (for our JavaScript SDK) or other debug files, so that you can view source code context obtained from stack traces in their original untransformed form. This is useful for debugging files that are processed — that is bundled, minified, transpiled, compiled, or otherwise obfuscated by tools like Webpack, Terser, or the C++ compiler — from a higher-level language.

Enable Suspect Commits

With releases, you can identify suspect commits, which help predict which commit caused an issue and who is likely responsible. Sentry uses commit metadata from your source code repositories to identify the suspect commits.

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.

Track Release Health

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.

Learn More

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").