Bump Cluster Ui

Fetch remote branches and confirm origin/release-{version} exists:

git fetch origin release-{version} --no-tags

If the branch does not exist, report the error and stop.

Step 3: Read Current State

Read pkg/ui/workspaces/cluster-ui/package.json on both branches to verify the current version matches the expected {major}.{minor}.0-prerelease.0 pattern:

git show origin/release-{version}:pkg/ui/workspaces/cluster-ui/package.json
git show origin/master:pkg/ui/workspaces/cluster-ui/package.json

If the version does not match expectations, warn the user and ask whether to proceed.

Step 4: Confirm with User

Show the user a summary of the two planned changes:

Release branch PR (targeting release-{version}):
  package.json version: {version}.0-prerelease.0 → {version}.0

Master PR (targeting master):
  package.json version: {version}.0-prerelease.0 → {next_version}.0-prerelease.0

Where {next_version} increments the minor: e.g., 26.2 → 26.3.

Get explicit confirmation before proceeding.

Step 5: Identify Fork Remote

The cockroachdb/cockroach repo restricts branch creation, so branches must be pushed to the user's personal fork. Identify the fork remote:

git remote -v

Look for a remote pointing to the user's fork (e.g., fork → kyle-a-wong/cockroach). If no fork remote is found, ask the user which remote to use.

Use {fork} below to refer to the identified fork remote name, and {fork_owner} for the GitHub username (e.g., kyle-a-wong).

Step 6: Create Release Branch PR

git checkout -b bump-cluster-ui-{version} origin/release-{version}

Edit pkg/ui/workspaces/cluster-ui/package.json: change the "version" field from "{version}.0-prerelease.0" to "{version}.0".

Commit with message: