Sentry Release Management

Overview

Manage the full Sentry release lifecycle: create versioned releases, associate commits for suspect commit detection, upload source maps for readable stack traces, and monitor release health with crash-free rates and adoption metrics. Every production deploy should create a Sentry release so errors are grouped by version and regressions are caught immediately.

Prerequisites

• Sentry CLI installed: npm install -g @sentry/cli (v2.x) or use npx @sentry/cli
• Auth token with project:releases and org:read scopes from sentry.io/settings/auth-tokens/
• Environment variables set: SENTRY_AUTH_TOKEN, SENTRY_ORG, SENTRY_PROJECT
• Source maps generated by your build (e.g., tsc --sourceMap, Vite build.sourcemap: true)
• GitHub/GitLab integration installed in Sentry for automatic commit association (Settings > Integrations)

Instructions

Step 1 — Create a Release and Associate Commits

Choose a release naming convention. Sentry accepts any string, but two patterns dominate production usage: