Skip to content

chore(provider-opencode-go): set initial version 0.1.0 - #805

Open
rohitg00 wants to merge 1 commit into
mainfrom
chore/provider-opencode-go-version
Open

chore(provider-opencode-go): set initial version 0.1.0#805
rohitg00 wants to merge 1 commit into
mainfrom
chore/provider-opencode-go-version

Conversation

@rohitg00

Copy link
Copy Markdown
Contributor

What

Set provider-opencode-go to 0.1.0 ahead of its first registry release.

Why

The worker merged with version = "1.0.0", but a fresh worker with no production use starts at 0.x. First Release Control cut targets 0.1.0-experimental@next, so the manifest baseline must sit below it.

The removed Cargo.toml comment claimed provider-opencode-go/v0.1.0v0.2.1 tags exist from a retired bundled Node provider; no such tags, releases, or registry versions exist, so nothing collides.

@rohitg00 rohitg00 added the no-ticket PR deliberately has no Linear ticket (bump/typo/CI-only) label Aug 14, 2026
@vercel

vercel Bot commented Aug 14, 2026

Copy link
Copy Markdown

The latest updates on your projects. Learn more about Vercel for GitHub.

Project Deployment Actions Updated (UTC)
workers Ready Ready Preview Aug 14, 2026 2:53pm
workers-tech-spec Ready Ready Preview Aug 14, 2026 2:53pm

Request Review

@coderabbitai

coderabbitai Bot commented Aug 14, 2026

Copy link
Copy Markdown

Warning

Review limit reached

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

Next review available in: 47 minutes

You've used all free OSS reviews for now. Wait for the free limit to reset to keep reviewing this public repository.

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: Organization UI

Review profile: CHILL

Plan: Pro Plus

Run ID: d675f508-7632-4352-82cf-eecf8adb4f03

📥 Commits

Reviewing files that changed from the base of the PR and between 3fcb69e and 1bb0098.

⛔ Files ignored due to path filters (1)
  • provider-opencode-go/Cargo.lock is excluded by !**/*.lock
📒 Files selected for processing (1)
  • provider-opencode-go/Cargo.toml

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

Copy link
Copy Markdown
Contributor

skill-check — worker

0 verified, 60 skipped (no docs/).

Layer Result
structure
vale
ai
render

Four for four. Nicely done.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

no-ticket PR deliberately has no Linear ticket (bump/typo/CI-only)

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant