bump-conventions

Bump the @sentry/conventions dependency version across every package in the monorepo.

8.7k|1.8k|Updated Feb 1, 2012
One-click install
npx skills add https://github.com/getsentry/sentry-javascript --skill bump-conventions
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: bump-conventions
Source: https://github.com/getsentry/sentry-javascript/tree/main/.agents/skills/bump-conventions
Command: npx skills add https://github.com/getsentry/sentry-javascript --skill bump-conventions

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Upgrading a shared dependency like @sentry/conventions across a large monorepo is error-prone: packages use different pin styles, the yarn.lock entry must be collapsed, and renamed exports can silently break builds. This Skill automates the entire bump workflow so nothing is missed.

Core Features & Use Cases

  • Consistent version updates: Finds every package.json declaring @sentry/conventions and bumps it while preserving each file's pin style (caret ranges in packages/, exact pins in dev-packages/).
  • Lockfile refresh and verification: Runs yarn install and dedupe, then confirms no stale version resolution remains in yarn.lock.
  • Breaking change detection: Uses build errors and LSP findReferences to locate and fix renamed or removed exported constants across src/ and test/ directories.
  • Use Case: A new @sentry/conventions 0.16.0 release is published and you need every workspace in the sentry-javascript monorepo updated, built, and tested with a proper chore(deps) commit.

Quick Start

Ask the AI to bump @sentry/conventions to version 0.16.0 across all packages in the monorepo and verify the build and tests pass.

Frequently Asked Questions about bump-conventions

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I bump a dependency version across all packages in a monorepo?

Find every package.json declaring the dependency, update each version while preserving its pin style, then run yarn install to collapse the lockfile entry. Verify no stale version remains in yarn.lock and rebuild to catch breaking changes.

How do I update @sentry/conventions in the sentry-javascript repo?

Use this Skill with an optional version argument, defaulting to the latest npm release. It updates all package.json declarations, refreshes yarn.lock, fixes any renamed exports, and runs the full verification suite.

What happens if a dependency bump breaks the build?

A conventions bump can rename or remove exported attribute constants, causing type errors. Use LSP findReferences on the changed export to find every call site in src/ and test/, update usages, and re-run yarn build:dev until it passes.

Why does yarn.lock still show the old dependency version after upgrading?

The lockfile combines multiple version ranges into one entry, so a partial update leaves stale resolutions. Run yarn install and yarn dedupe-deps:fix, then grep yarn.lock for the old version to confirm it is gone.

Should caret ranges and exact pins be handled differently when bumping dependencies?

Yes. Packages declaring caret ranges like ^0.15.1 must keep the caret, while test suites with exact pins like 0.15.1 stay exact. Edit only the version string and never change the pin style.