sentry-release-management

Manage Sentry releases and associate commits.Use when creating releases, tracking commits,or managing release artifacts.Trigger with phrases like "sentry release", "sentry commits","manage sentry versions", "sentry release workflow".

⭐878stars🔀101forks📁View on GitHub🕐Updated Jan 4, 2026⬇️1downloads

When & Why to Use This Skill

The Sentry Release Management skill streamlines the software deployment lifecycle by automating the creation, tracking, and finalization of Sentry releases. It integrates seamlessly with Sentry CLI and Git to associate commits with specific versions and manage source map uploads, ensuring precise error tracking and improved debugging efficiency for development teams.

Use Cases

  • Automated Deployment Workflows: Automatically create and finalize Sentry releases during the CI/CD process using Git SHAs or semantic versioning to maintain a consistent release history.
  • Enhanced Error Debugging: Link specific code commits to releases to identify exactly which changes introduced new bugs, enabling faster root cause analysis.
  • Source Map Integration: Automate the uploading of source maps to Sentry, allowing developers to view de-obfuscated stack traces from production environments directly in their error reports.
  • Release Artifact Management: Efficiently manage, list, and delete release versions and associated artifacts to keep the Sentry project organized and within storage limits.
namesentry-release-management
description|
allowed-toolsRead, Write, Edit, Bash(sentry-cli:*), Bash(git:*), Grep
version1.0.0
licenseMIT
authorJeremy Longshore <jeremy@intentsolutions.io>

Sentry Release Management

Prerequisites

  • Sentry CLI installed (npm install -g @sentry/cli)
  • SENTRY_AUTH_TOKEN environment variable set
  • SENTRY_ORG and SENTRY_PROJECT configured
  • Source maps available in build output

Instructions

  1. Create release using git SHA, semantic version, or package.json version
  2. Associate commits with sentry-cli releases set-commits --auto
  3. Upload source maps from build directory with URL prefix if needed
  4. Finalize release to mark it complete
  5. Configure SDK release option to match CLI release version
  6. Set up Webpack DefinePlugin or environment variable for build-time injection
  7. Use release management API to list, view, or delete releases
  8. Connect GitHub/GitLab integration for automatic commit linking
  9. Create release script to automate the full workflow
  10. Implement source map cleanup for old releases to manage storage

Output

  • Release created with version identifier
  • Commits associated with release
  • Source maps uploaded
  • Release finalized and ready

Error Handling

See {baseDir}/references/errors.md for comprehensive error handling.

Examples

See {baseDir}/references/examples.md for detailed examples.

Resources