Skip to content

feat: Run compatible legacy projects from one launcher - #1802

Merged
hatayama merged 2 commits into
feature/v2-cli-delegation-integrationfrom
feat/v2-cli-delegation
Jul 16, 2026
Merged

feat: Run compatible legacy projects from one launcher#1802
hatayama merged 2 commits into
feature/v2-cli-delegation-integrationfrom
feat/v2-cli-delegation

Conversation

@hatayama

@hatayama hatayama commented Jul 16, 2026

Copy link
Copy Markdown
Owner

Refs: V3 dispatcher to V2 CLI delegation — To-Do 5–8

Summary

  • Runs compatible legacy projects through the installed launcher without global CLI switching.
  • Stores each required legacy CLI version separately and forwards command arguments unchanged.

User Impact

  • Projects from both CLI generations can share one launcher.
  • Missing Node or installation failures retain actionable guidance.

Changes

  • Install the matching legacy package into a versioned cache through npm.
  • Resolve the package bin entrypoint and invoke it through Node.
  • Keep global management commands and launch handling in the dispatcher.

Verification

  • scripts/check-go-cli.sh (pass)

Review in cubic

Install each required CLI generation in an isolated cache and run its declared Node entrypoint so one launcher can serve both project generations.
@coderabbitai

coderabbitai Bot commented Jul 16, 2026

Copy link
Copy Markdown
Contributor

Warning

Review limit reached

@hatayama, you've reached your PR review limit, so we couldn't start this review.

Next review available in: 38 minutes

Enable usage-based reviews in Billing to review now. Otherwise, wait until the next included review is available.
You're only billed for reviews past your plan's rate limits ($0.25/file).

How can I continue?

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 reviews.

How do review limits work?

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

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, additional reviews become available more gradually as earlier reviews age out of the rolling window.

Please refer docs for additional details.

Review details
⚙️ Run configuration

Configuration used: Path: .coderabbit.yaml

Review profile: CHILL

Plan: Pro

Run ID: 90170a54-7b41-42fc-a350-3ed58732b8c4

📥 Commits

Reviewing files that changed from the base of the PR and between c6f0af7 and 83fa3e0.

📒 Files selected for processing (7)
  • cli/dispatcher/internal/dispatcher/dispatcher_v2_delegate.go
  • cli/dispatcher/internal/dispatcher/dispatcher_v2_delegate_test.go
  • cli/dispatcher/internal/dispatcher/dispatcher_v2_detect_test.go
  • cli/dispatcher/internal/dispatcher/dispatcher_v2_install.go
  • cli/dispatcher/internal/dispatcher/dispatcher_v2_install_test.go
  • cli/dispatcher/internal/dispatcher/dispatcher_v2_run.go
  • cli/dispatcher/internal/dispatcher/run_dispatcher.go
✨ Finishing Touches
🧪 Generate unit tests (beta)
  • Create PR with unit tests
  • Commit unit tests in branch feat/v2-cli-delegation

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

Comment @coderabbitai help to get the list of available commands.

Route installation diagnostics to stderr and cover project-scoped version and dispatcher command routing so setup can parse the delegated version reliably.
@hatayama
hatayama merged commit e0bc7f7 into feature/v2-cli-delegation-integration Jul 16, 2026
2 checks passed
@hatayama
hatayama deleted the feat/v2-cli-delegation branch July 16, 2026 05:11
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant