Releases & Health

A release is a version of your code that is deployed to an environment. When you give Sentry information about your releases, you can:

  • Determine 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

Additionally, releases are used for applying source maps to minified JavaScript to view original, untransformed source code.

Bind the Version

Include a release ID (often called a "version") when you configure your client SDK. This ID is commonly a git SHA or a custom version number.

The release name cannot:

  • contain newlines, tabulator characters, forward slashes(/) or back slashes(\)
  • be (in their entirety) period (.), double period (..), or space ( )
  • exceed 200 characters
  release: "my-project-name@2.3.12",

A common way to do this with JavaScript in a Node/npm environment would be to use the process.env.npm_package_version like so:

  release: "my-project-name@" + process.env.npm_package_version,

How you make the version available to your code is up to you. For example, you could use an environment variable that is set during the build process.

This tags each event with the release value. We recommend that you tell Sentry about a new release before deploying it, as this will unlock a few more features as discussed in our documentation about releases. 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 ID.

After configuring your SDK, you can install a repository integration or manually supply Sentry with your own commit metadata. Read our documentation about setting up releases for further information about integrations, associating commits, and telling Sentry when deploying releases.

Release Health

Monitor the health of releases by observing user adoption, usage of the application, percentage of crashes, and session data. Release health will provide insight into the impact of crashes and bugs as it relates to user experience, and reveal trends with each new issue through the release details, graphs, and filters.

The SDK will automatically manage the start and end of the sessions when the SDK is initialized.

To benefit from the health data, you must use at least version 1.4.0 of the React Native SDK and enable the collection of the release health data in the initialization options of the SDK.

We mark the session as an error if the SDK captures an event that contains an exception (this includes manually captured errors) or an unhandled promise rejection, but for unhandled errors and native crashes (Android and iOS), they will be marked as crashed.

  autoSessionTracking: true

By default, the SDK sends sessions. To disable this toggle the flag enableAutoSessionTracking to false.

The session terminates once the application is in the background for more than 30 seconds. To change the timeout, use the option sessionTrackingIntervalMillis. For example:

import * as Sentry from "@sentry/react-native";

  dsn: "",
  enableAutoSessionTracking: true,
  // Sessions close after app is 10 seconds in the background.
  sessionTrackingIntervalMillis: 10000,

For more details, see the full documentation on Release Health.

You can edit this page on GitHub.