rielflow-version-bump

name

rielflow-version-bump

description

Use when bumping rielflow workspace package versions without publishing a release. Applies to requests such as bump to a requested version, version bump only, prepare version metadata, or updating rielflow package.json and bun.lock versions. Stops before tags, GitHub releases, archive builds, Homebrew tap updates, npm publishing, commits, or pushes unless the user explicitly asks for those actions.

Rielflow Version Bump

Scope

Use this skill for source metadata changes only:

• root package.json
• every packages/*/package.json
• bun.lock workspace version entries generated by bun install

Do not start the release workflow, create tags, upload GitHub release assets, render the Homebrew formula, publish npm packages, or push commits unless the user explicitly asks for those separate actions. If the user asks for a full release, complete this bump first, then use rielflow-release.

Workflow

1. Inspect the current state:

   git status --branch --short
   bun --print 'JSON.parse(await Bun.file("package.json").text()).version'
   bun --print 'JSON.parse(await Bun.file("packages/rielflow/package.json").text()).version'
   

2. Check for unrelated dirty files. Work with existing user changes; do not revert them. For a bump-only request, keep the final diff limited to version metadata.

3. Update only version fields in package.json and packages/*/package.json. Prefer structured JSON edits or a small targeted script over broad repository text replacement.

4. Run bun install from the repository root so bun.lock reflects the package manifests.

5. Verify the version consistency:

   rg '"version": "<version>"' package.json packages/*/package.json bun.lock
   rg '<previous-version>' package.json packages/*/package.json bun.lock
   git diff --stat
   git diff -- package.json packages/*/package.json bun.lock
   

   The previous-version search should return no matches in the targeted version metadata paths unless a dependency or changelog intentionally still mentions it.

6. For bump-only work, do not mix unrelated test fixes into the bump. If a check exposes an unrelated failure, report it separately and leave the bump diff clean unless the user asks to fix it.

Verification

For a metadata-only bump, minimum verification is:

bun install
rg '"version": "<version>"' package.json packages/*/package.json bun.lock
git diff --stat

Run task ci when the bump is part of a release or when the user asks for full validation. If task ci fails on an unrelated existing test issue, do not turn a bump-only request into a broader code change without user approval.

Commit Boundary

When the user asks to commit the bump, use the repository commit policy and stage only the version files unless the user requested additional changes. Keep the version bump commit separate from release assets and Homebrew tap commits.