# Sentry Releases

> Manage Sentry releases, source maps and debug symbols with sentry-cli.

- Skill: `felinics/sentry-releases` (Agent Skill, multi-file: 2 files)
- Install (CLI): `npx skillmds@latest add felinics/sentry-releases`
- Raw SKILL.md: https://api.skillmd.com/api/skills/felinics/sentry-releases/raw
- Safety review: pending
- Works with: Claude Code, Claude.ai, OpenAI Codex
- Category: Coding & Dev Tools
- Author: felinics (https://skillmd.com/u/felinics)
- Updated: 2026-09-17
- Page: https://skillmd.com/skills/felinics/sentry-releases

---


# Sentry Releases

## Separate investigation and publishing
Use the bundled read-only Sentry Skill and `sentry` for issue investigation. Use `sentry-cli` for release artifacts. Verify the intended organization and project and check `sentry-cli info` before publishing; configure credentials locally.

## Release artifacts
Inspect the project's existing Sentry build integration. Upload source maps with the matching build artifacts and release identifiers. Use `sentry-cli sourcemaps --help` and `sentry-cli releases --help` for the installed version's exact commands. Upload debug symbols only for the matching binary build.

## Verify
Check upload results and ensure the release identifier matches the deployed application. A successful upload alone does not prove a production stack trace resolves: report that distinction. Do not change live release state without the user's publishing request.

Reference: https://docs.sentry.io/cli/