Update release base versions for supported packages, keep matching version fields in sync, and verify generated versions. The workflow covers committing and pushing the changes, with guidance for release steps after merging.
Bump the base version of one or more packages (riptide-native, cli, linear-cli, rpi-cli, rpi-plugin) on a PR - updates every synced file, verifies, commits, pushes. Use when cutting a release or asked to bump versions.
Run score Not tested
See how to installReview the instructions the agent will receive before you install.
Versions are bases (ci-scripts/derive-version.ts): releases derive base + commits since base changed on every channel (dev/beta/prod); at the bump-merge SHA the derived version is exactly the new base. Bump only to cut a release or force a minor/major — never in regular PRs.
Default: minor+1, patch 0 (0.134.x → 0.135.0) — always above every shipped derived build. Never hand-pick a patch (can land below a shipped dev build); major only if asked.
Set the identical version in every file listed. Leave Cargo.lock/bun.lock alone.
| package | files |
|---|---|
| riptide-native | apps/riptide-native/tauri.conf.json "version" · apps/riptide-native/package.json "version" · apps/riptide-native/Cargo.toml version = |
| cli | apps/cli/package.json "version" |
| linear-cli | apps/linear-cli/package.json "version" |
| rpi-cli | apps/rpi-cli/package.json "version" |
| rpi-plugin | apps/riptide-rpi-claude-plugin/.claude-plugin/plugin.json "version" · marketplace.json (same dir) top-level "version" and plugins[0].version |
Plugin patch versions derive per release like everything else (ci-scripts/stamp-plugin-versions.ts) — plugin content ships without bumps; bump a plugin base only for minor/major intent.
Commit first (derivation errors on uncommitted edits), verify while the bump commit is HEAD, then push to the PR branch and note the intent in the PR description ("cuts 0.135.0"):
# shallow-clone error? git fetch --unshallow
INPUT_RELEASE_TYPE=dev bun run ci-scripts/generate-version.ts # riptide → release_version=<new base>
INPUT_RELEASE_TYPE=prod bun run ci-scripts/generate-version.ts # riptide → release_version=<new base>
VERSION_FILE=apps/cli/package.json COUNT_PATHS=apps/cli bun run ci-scripts/derive-package-version.ts # each CLI → <new base>
Any other output = files out of sync or bump commit isn't HEAD. Fix before pushing.
Releases build in HumanLayer's private release repo, which checks out this repo. Maintainers pin both dispatches there to the merge commit — they ship the identical version no matter when they run (every channel derives the same version at the same SHA):
SHA=$(gh pr view <PR> --json mergeCommit -q .mergeCommit.oid)
gh workflow run release-riptide-beta.yml --repo <release repo> -f public_ref=$SHA
gh workflow run release-riptide-prod.yml --repo <release repo> -f public_ref=$SHA
Useful inputs on both: notes, urgency, skip_cask_update, skip_signing, dry_run.
npm CLIs publish automatically after a merge to main — nothing to dispatch.
No reviews yet. Tell others what you thought.
No login needed. Share how it worked for you, ask a question, or note where it did not run.
No comments yet. Be the first to write one.
Automate website navigation, form entry, and clicks through a browser command line tool. Extract page text, capture screenshots, and compare page states to check interactions or test web app behavior across screen sizes.
Rewrite dense or ambiguous English into short, direct sentences using principles from ASD-STE100, a standard for clear technical English. It preserves facts and conditions, identifies writing issues, and shows the original and revised text side by side.
Inspect GitHub pull requests, read review conversations, and investigate failed automated checks with dedicated scripts. Get consolidated status reports, unresolved discussion threads, and failing job or step logs, with full logs saved for further inspection.
Compare function call structures across Git commits, branches, or working files to support code review. Display call trees and trace paths from an entry function to a target function, with support for 22 languages.
Automate browser tasks from the terminal using the chrome-devtools-mcp CLI. Inspect page elements, click and fill forms, navigate tabs, capture screenshots, and investigate network requests, console messages, performance, and memory through shell commands.
Review the changes made during a session and organize them into focused Git commits. The skill groups related files, writes messages explaining why changes were made, and stages specific files while excluding unrelated material.