release
Publish a new Sentry JavaScript SDK release. Use when preparing a release, updating the changelog, or creating a release branch.
Works with
--- name: release description: Publish a new Sentry JavaScript SDK release. Use when preparing a release, updating the changelog, or creating a release branch. license: MIT --- # 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 `yarn changelog` (use `yarn 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 - `yarn changelog` — generate changelog entries - `yarn lint` — verify code quality - `yarn test` — run test suite - `yarn build:dev` — verify build
More Writing & Documentation skills
paper-context-resolver
lllllllama/rigorpilot-skills
Rigor Paper Context helper for README-first deep learning repo reproduction. Use only when the README and repository files leave a narrow reproduction-critical gap and the task is to resolve a specific paper detail such as dataset split, preprocessing, evaluation protocol, checkpoint mapping, or runtime assumption from primary paper sources while recording conflicts. Do not use for general paper summary, repo scanning, environment setup, command execution, title-only paper lookup, or replacing README guidance by default.
repo-intake-and-plan
lllllllama/rigorpilot-skills
Rigor Intake helper for README-first deep learning repo reproduction. Use when the task is specifically to scan a repository, read the README and common project files, extract documented commands, classify inference, evaluation, and training candidates, and return the smallest trustworthy reproduction plan to the main orchestrator. Do not use for environment setup, asset download, command execution, final reporting, paper lookup, or end-to-end orchestration.
minimal-run-and-audit
lllllllama/rigorpilot-skills
Rigor Run skill for README-first deep learning repo reproduction. Use when the task is specifically to capture or normalize evidence from the selected smoke test or documented inference or evaluation command and write standardized `repro_outputs/` files, including patch notes when repository files changed. Do not use for training execution, initial repo intake, generic environment setup, paper lookup, target selection, hidden scientific-meaning changes, or end-to-end orchestration by itself.
