release
/release
Publish a new Sentry JavaScript SDK release. Use when preparing a release, updating the changelog, or creating a release branch.
- Author
- getsentry ↗
- Repository
- sentry-javascript ↗
- Licence
- MIT
- Last repository change
- 25.10.2026
Assessment and security
- Files in this package
- 1
- Scripts
- 0
- HTML comments
- 0
- URLs in SKILL.md
- 1
No signals detected. Repository changed on 25.10.2026, without references to retired models or APIs.
MIT, open: use and modify while retaining author attribution.
What it does and when to use it
Publish a new Sentry JavaScript SDK release. Use when preparing a release, updating the changelog, or creating a release branch.
Arguments
/release [VERSION]
Original author description
Publish a new Sentry JavaScript SDK release. Use when preparing a release, updating the changelog, or creating a release branch.
How it works
- Steps
- First-time SDK releases
- Key commands
SKILL.md preview
--- name: release description: Publish a new Sentry JavaScript SDK release. Use when preparing a release, updating the changelog, or creating a release branch. argument-hint: [VERSION] --- # Release Process See `docs/publishing-a-release.md` for full details. ## Steps 1. Ensure you're on `develop` with latest changes. Stash any unsaved work with `git stash -u` if needed. 2. Run `pnpm run changelog` (use `pnpm run changelog | pbcopy` to copy output). 3. Decide on a version per [semver](https://semver.org). Check the top of `CHANGELOG.md` for the current version. 4. Create branch `prepare-release/VERSION` off `develop`. 5. Update `CHANGELOG.md` — add the new version entry with the changelog output. See the "Updating the Changelog" section in `docs/publishing-a-release.md` for formatting details. Do not remove existing entries. 6. Commit: `meta(changelog): Update changelog for VERSION` 7. Push the branch and remind the user to open a PR targeting `master`. 8. If you were on a different branch, checkout back and `git stash pop` if needed. ## First-time SDK releases Follow `docs/new-sdk-release-checklist.md`. If anything doesn't match the checklist, remind the user. ## Key commands - `pnpm run changelog` — generate changelog entries - `pnpm run lint` — verify code quality - `pnpm run test` — run test suite - `pnpm run build:dev` — verify build
Versions
| Repository | Score | Licence |
|---|---|---|
| This page · getsentry/sentry-javascript | 90 | MIT |
| josephfung/curia | 100 | MIT |
| max-sixty/worktrunk | 100 | MIT |
| gtapps/hermitd | 100 | MIT |
| gtapps/hermitd | 100 | MIT |
| anthony-chaudhary/fak | 100 | Apache-2.0 |
| tractorjuice/arc-kit | 100 | MIT |
| drvoss/everything-copilot-cli | 100 | MIT |
| sma1lboy/rove | 100 | MIT |
Database snapshot: 13.11.2026 · package version a2940cf7f9d4 (SHA-256 digest of the entire package)
Downloads in the last 30 days: 0 · ranking
Report a problem with this skill: harmful content, incorrect descriptions or an author’s removal request.
Similar skills
- 100ac-release
Release workflow: branch, changelog, PR, tag, GH release. Triggers on keywords: release, create release, publish release, tag release - 100release-notes
Generate release notes or changelog entries for completed changes. Use when asked to \"write release notes\", \"update the changelog\", \"document what changed\", \"create a release summary\", or when preparing a release. Follows Keep a Changelog format. - 100sentry-sdk-upgrade
Upgrade the Sentry JavaScript SDK across major versions. Use when asked to upgrade Sentry, migrate to a newer version, fix deprecated Sentry APIs, or resolve breaking changes after a Sentry version bump. - 100prepare-release
Prepare a new release by collecting commits, generating bilingual release notes, updating version files, and creating a release branch. Use when asked to prepare/create a release, bump version, or run `/prepare-release`. - 100changelog-generator
Generate changelogs from git commits. Use when user says "generate changelog", "update changelog", "what changed since last release", or before preparing a new release. - 100cmux-release
cmux release workflow, version bumping, changelog updates, pretag guard, release tags, and release asset expectations. Use when preparing or troubleshooting a cmux release.