chore(main): release 2.2.0

[tkhwang]

🤖 I have created a release beep boop

2.2.0 (2026-06-17)

Features

• ui: redesign companion app layout and summary (24f4d51)
• ui: redesign companion app layout and summary (cae49ca)

---

This PR was generated with Release Please. See documentation.

[coderabbitai]

Warning

Review limit reached

@tkhwang, we couldn't start this review because you've reached your PR review rate limit.

More reviews will be available in 40 minutes and 30 seconds. Learn how PR review limits work.

Your organization has used up its prepaid credits, and credit purchases are no longer available. Enable the review add-on in the billing tab to keep reviews running — you're only billed for reviews past your plan's rate limits ($0.25/file).

⌛ How to resolve this issue?

After more reviews become available, a review can be triggered using the @coderabbitai review command as a PR comment. Alternatively, push new commits to this PR.

To avoid repeated limits, reduce automatic review volume by pausing incremental auto-reviews earlier, using label-based review opt-in, excluding WIP or generated PR titles, or requesting reviews manually when the PR is ready. If your team needs uninterrupted high-volume reviews, an organization admin can enable usage-based credits.

🚦 How do rate limits work?

CodeRabbit enforces per-developer PR review limits for each organization. Most developers receive the normal plan refill rate.

For paid Pro and Pro+ PR reviews, CodeRabbit uses adaptive limits for sustained high-volume activity. When a developer's recent PR review activity reaches the 95th percentile or higher among CodeRabbit users, the refill rate gradually slows as usage increases. The highest same-day bursts are limited more strictly.

Please see our Fair Usage Limits Policy for further information.

ℹ️ Review info

⚙️ Run configuration

Configuration used: defaults

Review profile: CHILL

Plan: Pro

Run ID: 80759f29-96a8-42ea-b6cc-f7638c2e2196

📥 Commits

Reviewing files that changed from the base of the PR and between 24f4d51 and aed9827.

📒 Files selected for processing (4)

• .release-please-manifest.json
• CHANGELOG.md
• apps/workbranch-cli/bin/workbranch
• bin/workbranch

✨ Finishing Touches

🧪 Generate unit tests (beta)

• Create PR with unit tests
• Commit unit tests in branch release-please--branches--main--components--workbranch

---

Thanks for using CodeRabbit! It's free for OSS, and your support helps us grow. If you like it, consider giving us a shout-out.

❤️ Share

• X
• Mastodon
• Reddit
• LinkedIn

_{Comment @coderabbitai help to get the list of available commands and usage tips.}

[chatgpt-codex-connector]

💡 Codex Review

Here are some automated review suggestions for this pull request.

Reviewed commit: aed9827715

ℹ️ About Codex in GitHub

Codex has been enabled to automatically review pull requests in this repo. Reviews are triggered when you

• Open a pull request for review
• Mark a draft as ready
• Comment "@codex review".

If Codex has suggestions, it will comment; otherwise it will react with 👍.

When you sign up for Codex through ChatGPT, Codex can also answer questions or update the PR, like "@codex address that feedback".

[chatgpt-codex-connector]

Release the companion package instead of the CLI

This manifest bump publishes a root v2.2.0 release even though the entries included in this release are companion UI changes, while apps/workbranch-companion remains at 2.0.0. I checked the release workflows: .github/workflows/companion-release.yml:20 only builds tags starting with workbranch-companion-v, and .github/workflows/homebrew-bump.yml:15 treats non-companion tags as CLI formula releases, so merging this release PR will update the CLI/Homebrew formula and skip packaging the companion UI update that the changelog advertises.

Useful? React with 👍 / 👎.