Skip to content

chore: bump vendored opencode to v1.18.10-amicode.10 - #367

Open
Rchari1 wants to merge 1 commit into
mainfrom
chore/bump-opencode-amicode-10
Open

chore: bump vendored opencode to v1.18.10-amicode.10#367
Rchari1 wants to merge 1 commit into
mainfrom
chore/bump-opencode-amicode-10

Conversation

@Rchari1

@Rchari1 Rchari1 commented Aug 13, 2026

Copy link
Copy Markdown
Member

Bumps packages/extension/opencode.lock.json to v1.18.10-amicode.10 (c936b6fd4bae20e28d202d36c2211284864f2e3b).

Source: harmoniqs/opencode#195 -> merged to local/amicode, tagged v1.18.10-amicode.10 via https://github.com/harmoniqs/opencode/actions/runs/31729070856

Why: prior .9 still bundled the monochrome currentColor placeholders for Slack/GitHub/Linear/Harmoniqs/Pasqal — they rendered as faint gray against text-text-base. .10 ships full-color brand SVGs (explicit fills, 18×18, no tint) and the ConnectionIcon full-bleed fix so reload will show proper logos.

darwin-arm64  a95741afac79d280ac033c100aa51863b6109647f4e0e8c8e2051e01f5b89b1a
linux-arm64   f0e7a355227402357e0b69725ece3dd076c71e8fbc03802255cee1bb3ff31df6
linux-x64     353d651215cdc7801bd66065a63ebef5f9cb35487b683b8a051123943989050e

After merge, reload window will be live (no manual vendor fetch needed).

Full-color brand icons for connections — previous b0fadd5
(slack/github/linear/harmoniqs/pasqal) were monochrome
currentColor placeholders that washed out against text-text-base.
Now explicit brand fills at 18px, ConnectionIcon renders at full
bleed so colors show.

Tag v1.18.10-amicode.10 (c936b6fd) — shas verified from
amicode-release 31729070856.
@coderabbitai

coderabbitai Bot commented Aug 13, 2026

Copy link
Copy Markdown

Warning

Review limit reached

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

Next review available in: 21 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: defaults

Review profile: CHILL

Plan: Pro Plus

Run ID: 24e6a479-32ee-4c73-ac3c-bb67d34273c4

📥 Commits

Reviewing files that changed from the base of the PR and between 8d080ee and e4391ee.

📒 Files selected for processing (1)
  • packages/extension/opencode.lock.json

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

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