sentry-ci-integration

# Sentry CI Integration ## Overview Sentry releases connect errors to the code that caused them. Automating release creation in CI/CD ensures every deploy has commit association (suspect commits), source maps for readable stack traces, and deployment tracking across environments. This skill covers `sentry-cli` commands, the official GitHub Action, build tool plugins (`@sentry/webpack-plugin`, `@sentry/vite-plugin`, `@sentry/esbuild-plugin`), and multi-platform CI configurations. ## Prerequisites - Sentry account with a project at [sentry.io](https://sentry.io) - `SENTRY_AUTH_TOKEN` — generate at sentry.io/settings/auth-tokens/ with scopes `project:releases` and `org:read` - `SENTRY_ORG` and `SENTRY_PROJECT` environment variables matching your organization and project slugs - Source maps generated during your build step (`devtool: 'source-map'` in webpack, `build.sourcemap: true` in Vite) - Git integration installed in Sentry (sentry.io/settings/integrations/ — GitHub, GitLab, or Bitbucket) for commit association - `sentry-cli` available via `npm install -g @sentry/cli`, `npx @sentry/cli`, or the `getsentry/sentry-cli` Docker image ## Instructions ### Step 1 — Configure Environment Variables and Auth Token Set up the three required environment variables in your CI platform. Every `sentry-cli` command reads these automatically. ```bash # GitHub Actions — add as repository secrets: # Settings > Secrets and variables > Actions > New repository secret SENTRY_AUTH_TOKEN=s...