How do I install the Bump Conventions skill?

Run npx skillmds@latest add getsentry/bump-conventions in your terminal (requires Node.js), paste this page's agent-chat prompt into Claude, Cursor, or any MCP-connected agent, or download the SKILL.md file and copy it into your agent's skills directory.

Is Bump Conventions safe to use?

This skill has not completed SkillMD's automated safety review yet. Independent scanners report: SkillSpector: PASS, Skill Scanner: PASS. Capability flags: docs only. SkillMD never runs a skill's scripts for you; review the SKILL.md before installing.

Which AI agents work with Bump Conventions?

This skill is tagged as working with Claude Code, Claude.ai, OpenAI Codex. SKILL.md is an open format, so most agents that read a skills directory can load it too.

Is Bump Conventions free to use?

Yes. Installing skills from SkillMD is free, and the skill stays under its author's original license.

Who published Bump Conventions?

Sentry (@getsentry) published this skill. Their other Agent Skills are listed on their SkillMD profile.

Bump Conventions by getsentry — Agent Skill

Name: Bump Conventions
Rating: 4.2 (5 reviews)
Author: Sentry

Bump Conventions

Bump the @sentry/conventions dependency to a new version across every package in the monorepo. Use when upgrading, bumping, or aligning @sentry/conventions, or when a new @sentry/conventions release needs to be pulled into all workspaces.

Sentry Updated Sep 10, 2026 845 repo stars

File contents

Bump `@sentry/conventions`

Bump @sentry/conventions across every package.json at once, keeping the two pin styles consistent, then refresh yarn.lock.

1. Determine the target version

If the user gave a version, use it. Otherwise get the latest:

npm view @sentry/conventions version

2. Update every declared version

Find every package.json that declares @sentry/conventions (use the Grep tool so node_modules and build output are skipped automatically) and bump each to the new version. There are two pin styles, and each must keep its style:

packages/* declare a caret range in dependencies, e.g. "^0.15.1" → "^0.16.0"
dev-packages/* test suites declare an exact pin in devDependencies, e.g. "0.15.1" → "0.16.0"

Edit only the version string; leave the caret alone. If a file declares a version that matches neither the current caret nor the exact pin, list it and confirm with the user before touching it. Preserve each file's trailing newline.

3. Refresh the lockfile and build

yarn install
yarn dedupe-deps:fix
yarn build:dev

yarn install collapses the combined yarn.lock entry ("@sentry/conventions@<OLD>", "@sentry/conventions@^<OLD>":) onto the new version. Confirm no stale <OLD> resolution remains:

grep -n '@sentry/conventions@' yarn.lock

4. Check for breaking API changes

A conventions bump can rename or remove exported attribute constants. If yarn build:dev fails, inspect the type errors and update usages in src/ and test/. Heaviest consumers: packages/core, packages/opentelemetry, packages/aws-serverless.

Use LSP findReferences on the changed export to catch every call site. Do not paper over a rename with a cast.

After fixing, re-run yarn build:dev and confirm it passes before verifying, so the next step runs against fresh build output.

5. Final verification

yarn circularDepCheck
yarn fix
yarn test

Commit

Use the chore(deps): prefix the repo uses for dependency bumps:

chore(deps): Bump `@sentry/conventions` to <NEW>

---name: bump-conventionsdescription: Bump the @sentry/conventions dependency to a new version across every package in the monorepo. Use when upgrading, bumping, or aligning @sentry/conventions, or when a new @sentry/conventions release needs to be pulled into all workspaces.---# Bump `@sentry/conventions`Bump `@sentry/conventions` across every `package.json` at once, keeping the two pin styles consistent, then refresh `yarn.lock`.## 1. Determine the target versionIf the user gave a version, use it. Otherwise get the latest:```bashnpm view @sentry/conventions version```## 2. Update every declared versionFind every `package.json` that declares `@sentry/conventions` (use the Grep tool so `node_modules` and build output are skipped automatically) and bump each to the new version. There are two pin styles, and **each must keep its style**:- `packages/*` declare a caret range in `dependencies`, e.g. `"^0.15.1"` → `"^0.16.0"`- `dev-packages/*` test suites declare an exact pin in `devDependencies`, e.g. `"0.15.1"` → `"0.16.0"`Edit only the version string; leave the caret alone. If a file declares a version that matches neither the current caret nor the exact pin, list it and confirm with the user before touching it. Preserve each file's trailing newline.## 3. Refresh the lockfile and build```bashyarn installyarn dedupe-deps:fixyarn build:dev````yarn install` collapses the combined `yarn.lock` entry (`"@sentry/conventions@<OLD>", "@sentry/conventions@^<OLD>":`) onto the new version. Confirm no stale `<OLD>` resolution remains:```bashgrep -n '@sentry/conventions@' yarn.lock```## 4. Check for breaking API changesA `conventions` bump can rename or remove exported attribute constants. If `yarn build:dev` fails, inspect the type errors and update usages in `src/` **and** `test/`. Heaviest consumers: `packages/core`, `packages/opentelemetry`, `packages/aws-serverless`.Use LSP `findReferences` on the changed export to catch every call site. Do not paper over a rename with a cast.After fixing, re-run `yarn build:dev` and confirm it passes before verifying, so the next step runs against fresh build output.## 5. Final verification```bashyarn circularDepCheckyarn fixyarn test```## CommitUse the `chore(deps):` prefix the repo uses for dependency bumps:```chore(deps): Bump `@sentry/conventions` to <NEW>```

Frequently asked questions