bump-cluster-ui

Creates two pull requests bumping the cluster-ui package version after a release branch cut.

32.4k|4.1k|Updated Feb 6, 2014
One-click install
npx skills add https://github.com/cockroachdb/cockroach --skill bump-cluster-ui
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: bump-cluster-ui
Source: https://github.com/cockroachdb/cockroach/tree/main/.claude/skills/bump-cluster-ui
Command: npx skills add https://github.com/cockroachdb/cockroach --skill bump-cluster-ui

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

After every CockroachDB release branch cut, the cluster-ui npm package version must be updated in two places: the prerelease suffix must be dropped on the release branch, and the minor version must be incremented on master. Doing this manually is repetitive and error-prone, so this Skill automates both version bumps as ready-to-merge pull requests.

Core Features & Use Cases

  • Dual PR Automation: Creates one PR targeting the release branch (e.g., 26.2.0-prerelease.0 → 26.2.0) and one targeting master (e.g., 26.2.0-prerelease.0 → 26.3.0-prerelease.0).
  • Validation & Safety Checks: Verifies the release branch exists on origin and that the current version in package.json matches the expected prerelease pattern before making changes.
  • Convention-Compliant Commits: Follows historical commit message conventions, including optional Jira epic references and "Release note: None" trailers.
  • Use Case: After the release-26.2 branch is cut, run this Skill with version 26.2 and epic REL-4280 to automatically produce both version-bump PRs against cockroachdb/cockroach via your fork.

Quick Start

Ask the assistant to bump the cluster-ui version for release 26.2 with Jira epic REL-4280, and confirm the two planned pull requests when prompted.

Frequently Asked Questions about bump-cluster-ui

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

FAQPage Schema
How do I bump the cluster-ui version after a CockroachDB release branch cut?

Provide the release version (e.g., 26.2) and optionally a Jira epic. The Skill creates two PRs: one dropping the prerelease suffix on the release branch and one incrementing the minor version on master.

What file does the cluster-ui version bump change?

It edits the "version" field in pkg/ui/workspaces/cluster-ui/package.json. On the release branch it becomes {version}.0, and on master it becomes {next_version}.0-prerelease.0.

Why does the version bump push to a fork instead of cockroachdb/cockroach?

The cockroachdb/cockroach repository restricts direct branch creation, so branches are pushed to your personal fork remote. PRs are then opened with the fork branch as head and the upstream repo as base.

What happens if the release branch does not exist?

The Skill fetches origin/release-{version} first and stops with an error if the branch is missing. It also warns you if the current package.json version does not match the expected prerelease pattern.

What tools are required to run the cluster-ui version bump?

You need git with a configured fork remote and the GitHub CLI (gh) authenticated. If gh pr create fails, check your authentication with gh auth status.