Skip to content

docs: mark language support roadmap complete#418

Merged
OBenner merged 1 commit into
developfrom
docs/roadmap-complete
Jul 12, 2026
Merged

docs: mark language support roadmap complete#418
OBenner merged 1 commit into
developfrom
docs/roadmap-complete

Conversation

@OBenner

@OBenner OBenner commented Jul 12, 2026

Copy link
Copy Markdown
Owner

Summary

Status update for docs/LANGUAGE_SUPPORT_ROADMAP.md: all five phases are complete.

Phase PRs
1 — Detection fixes + test discovery parity #387, #388
2 — Security scanners (native runners + osv-scanner + rules tables) #390, #394
3 — Framework detection for compiled ecosystems #395
4 — Targeted tests + compiler-cache warm-up #402, #412
5 — CLI E2E harness (run_cli_session) #415

Native GUI / mobile / embedded verification remain explicitly out of scope per the phase 5 section.

🤖 Generated with Claude Code

All five phases landed: #387, #388 (phase 1), #390, #394 (phase 2),
#395 (phase 3), #402, #412 (phase 4), #415 (phase 5, CLI slice).

Co-Authored-By: Claude Fable 5 <noreply@anthropic.com>
Signed-off-by: Oleg Miagkov <mrobenner@gmail.com>
@coderabbitai

coderabbitai Bot commented Jul 12, 2026

Copy link
Copy Markdown
Contributor

Warning

Review limit reached

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

Next review available in: 57 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: ASSERTIVE

Plan: Pro

Run ID: 5b5ba2d2-46a4-4a12-a159-7aba53488bb9

📥 Commits

Reviewing files that changed from the base of the PR and between d055374 and 6f2bf4e.

📒 Files selected for processing (1)
  • docs/LANGUAGE_SUPPORT_ROADMAP.md
✨ Finishing Touches
🧪 Generate unit tests (beta)
  • Create PR with unit tests
  • Commit unit tests in branch docs/roadmap-complete

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.

@github-actions github-actions Bot added documentation Improvements or additions to documentation size/S labels Jul 12, 2026
@sonarqubecloud

Copy link
Copy Markdown

@OBenner OBenner merged commit 49d908b into develop Jul 12, 2026
4 checks passed
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

documentation Improvements or additions to documentation size/S

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant