---
title: "Set Up"
description: "Learn about setting up your SDK to enable Releases and to monitor release health."
url: https://docs.sentry.io/product/releases/setup/
---

# Set Up

Setting up your application to send Sentry releases data fully is a multi-step process, and is adaptable to your organization's needs.

If you're using one of our [release automation](https://docs.sentry.io/product/releases/setup/release-automation.md) options, it will automate steps 3.2 and 4 of this process. If you're managing your releases manually, then you should follow all of the steps below.

## [1. Configure Your SDK](https://docs.sentry.io/product/releases/setup.md#1-configure-your-sdk)

With your SDK configured to provide a release identifier and enable session tracking, you can monitor both [releases](https://docs.sentry.io/product/releases.md) and [release health](https://docs.sentry.io/product/releases/health.md). Check out the documentation for your specific platform to [configure the SDK](https://docs.sentry.io/platform-redirect.md?next=/configuration/releases/).

You must have the environment [configured in your SDK](https://docs.sentry.io/platform-redirect.md?next=/configuration/environments/) to use this feature.

### [Release Health](https://docs.sentry.io/product/releases/setup.md#release-health)

Release health is supported for the following SDKs:

* [Android](https://docs.sentry.io/platforms/android/configuration/releases.md#release-health)
* [Flutter](https://docs.sentry.io/platforms/dart/guides/flutter/configuration/releases.md#release-health)
* [iOS](https://docs.sentry.io/platforms/apple/configuration/releases.md#release-health)
* [JavaScript (browser)](https://docs.sentry.io/platforms/javascript/configuration/releases.md#release-health)
* [JavaScript (node)](https://docs.sentry.io/platforms/javascript/guides/node/configuration/releases.md#release-health)
* [Electron](https://docs.sentry.io/platforms/javascript/guides/electron/configuration/releases.md#release-health)
* [Native (C/C++)](https://docs.sentry.io/platforms/native/configuration/releases.md#release-health)
* [PHP](https://docs.sentry.io/platforms/php/configuration/releases.md)
* [Python](https://docs.sentry.io/platforms/python/configuration/releases.md#release-health)
* [React Native](https://docs.sentry.io/platforms/react-native/configuration/releases.md#release-health)
* [Rust](https://docs.sentry.io/platforms/rust/configuration/releases.md#release-health)
* [.NET](https://docs.sentry.io/platforms/dotnet/configuration/releases.md#release-health)
* [Unity](https://docs.sentry.io/platforms/unity/configuration/releases.md#release-health)

## [2. Upload Source Maps or Other Debug Files](https://docs.sentry.io/product/releases/setup.md#2-upload-source-maps-or-other-debug-files)

In cases where your code is processed — bundled, minified, transpiled, compiled, or otherwise obfuscated by tools like webpack, Terser, or the C++ compiler — source maps (or other debug files) are necessary for Sentry to display the source code in your stack traces in its original untransformed form. Setting up source maps is also necessary before [suspect commits](https://docs.sentry.io/product/releases/setup.md#3-associate-commits) can be enabled. Check out our SDK documentation to find source map or other debug file set up instructions for your specific platform if it's not in the list below:

* [Android](https://docs.sentry.io/platforms/android/configuration/using-ndk.md#symbolicate-stack-traces)
* [Flutter](https://docs.sentry.io/platforms/dart/guides/flutter/upload-debug.md)
* [iOS](https://docs.sentry.io/platforms/apple/guides/ios/dsym.md)
* [JavaScript](https://docs.sentry.io/platforms/javascript/sourcemaps.md)
* [Node.js](https://docs.sentry.io/platforms/javascript/guides/node/sourcemaps.md)

## [3. Associate Commits](https://docs.sentry.io/product/releases/setup.md#3-associate-commits)

[Associating commits](https://docs.sentry.io/product/releases/associate-commits.md) to a release allows you to more easily pinpoint which changes may be responsible for a given issue. To set them up:

1. [Install a repository integration](https://docs.sentry.io/organization/integrations/source-code-mgmt.md) so Sentry can access your commit history. (You can also upload commit data manually through our API if you don't want to use an integration.)
2. Configure your release management script to [associate commits with each release](https://docs.sentry.io/product/releases/associate-commits.md). If you're using one of our [release automation](https://docs.sentry.io/product/releases/setup/release-automation.md) options, this will be done for you.

Learn more about the benefits of tracking commit in [Associate Commits](https://docs.sentry.io/product/releases/associate-commits.md).

## [4. Notify Sentry](https://docs.sentry.io/product/releases/setup.md#4-notify-sentry)

If you're not using one of our [release automation](https://docs.sentry.io/product/releases/setup/release-automation.md) options, let Sentry know you’ve deployed your release by sending an additional request after creating a release:

```bash
sentry-cli releases --org ORGANIZATION_SLUG deploys VERSION new -e ENVIRONMENT
```

Make sure you have a [token](https://docs.sentry.io/cli/configuration.md) properly configured.

Typically, a release = a deployment, but if you have several environments in which you want to deploy a release, this step also allows you to create those deployments individually.

You can also use our [API](https://docs.sentry.io/api/releases/create-a-deploy.md) to create a deploy.

When you notify Sentry that you've deployed a release to a new environment, we can automatically send an email to Sentry users who have committed to the release being deployed.

If [finalizing the release](https://docs.sentry.io/cli/releases.md#finalizing-releases) isn't already included as part of your release automation process, make sure to do that. For more information, check out our [CLI documentation](https://docs.sentry.io/cli/releases.md).

## Pages in this section

- [Automatic Release Management](https://docs.sentry.io/product/releases/setup/release-automation.md)
