Skip to content
Skills Library
Programming · Automation

release

/release

Publish a new Sentry JavaScript SDK release. Use when preparing a release, updating the changelog, or creating a release branch.

Licence
MIT
Last repository change
25.10.2026

Assessment and security

90/ 100Class: good
Format25 / 25
Frontmatter with name and description, valid name, description up to 1,024 characters, name matching the folder.
Discoverability25 / 25
Description explains when to use the skill, has a reasonable length and uses third person.
Content25 / 35
At least 150 words and at most 500 lines, headings, step lists, examples or code.
Hygiene15 / 15
No placeholders such as TODO, no Windows paths, with a licence.
Riskno signals detected in the scan
Files in this package
1
Scripts
0
HTML comments
0
URLs in SKILL.md
1
Deprecation

No signals detected. Repository changed on 25.10.2026, without references to retired models or APIs.

Licence

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

  1. Steps
  2. First-time SDK releases
  3. Key commands
Original SKILL.md headings · 27 lines, 179 words
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

RepositoryScoreLicence
This page · getsentry/sentry-javascript90MIT
josephfung/curia100MIT
max-sixty/worktrunk100MIT
gtapps/hermitd100MIT
gtapps/hermitd100MIT
anthony-chaudhary/fak100Apache-2.0
tractorjuice/arc-kit100MIT
drvoss/everything-copilot-cli100MIT
sma1lboy/rove100MIT

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.

Feedback and reports

Your message goes to Bartosz Sokoliński. An email address is needed only for a reply. See the privacy policy.