Skip to content

chore: mark plugins that migrated to OpenCode V2 - #564

Open
github-actions[bot] wants to merge 1 commit into
mainfrom
bot/health-compat
Open

github-actions[bot] wants to merge 1 commit into
mainfrom
bot/health-compat

Conversation

@github-actions

@github-actions github-actions Bot commented Oct 18, 2026 •

Copy link
Copy Markdown
Contributor

The nightly health check now detects OpenCode V2 support in these V1-only or unverified plugins, so they no longer face the V1 sunset.

  • data/plugins/aegis-devops.yaml (Aegis-DevOps): v1 → v2 (source (1 files): Plugin.define)
  • data/plugins/antigravity-auth.yaml (Antigravity Auth): v1 → v2 (package.json: @opencode/client, @opencode/plugin, @opencode-ai/plugin@^0.15.30; dual V1/V2 support)
  • data/plugins/beads-plugin.yaml (Beads Plugin): v1 → v2 (package.json: @opencode/plugin)
  • data/plugins/brhp.yaml (BRHP): v1 → v2 (package.json: @opencode/plugin, @opencode/theme)
  • data/plugins/cache-stats.yaml (cache-stats): v1 → v2 (package.json: @opencode/theme; plugins/cache-stats/package.json: @opencode/client, @opencode/plugin)
  • data/plugins/cli-subagent-output.yaml (Subagent Reporter): v1 → v2 (package.json: @opencode/plugin)
  • data/plugins/envsitter-guard.yaml (Envsitter Guard): v1 → v2 (package.json: @opencode/plugin, @opencode-ai/plugin@^1.19.3; dual V1/V2 support)
  • data/plugins/handoff.yaml (Handoff): v1 → v2 (package.json: @opencode/plugin)
  • data/plugins/keep-going.yaml (keep-going): v1 → v2 (source (12 files): V2 plugin object (id + setup))
  • data/plugins/kibi-opencode.yaml (kibi-opencode): v1 → v2 (npm kibi-opencode@3.1.4: @opencode-ai/plugin@^1.19.5; packages/opencode/package.json: @opencode-ai/plugin@^1.19.5; source: V2 plugin object (id + setup), @opencode-ai/plugin (with Plugin.define); dual V1/V2 support)
  • data/plugins/oh-my-openagent.yaml (Oh My OpenAgent): v1 → v2 (package.json: @opencode/plugin, @opencode-ai/plugin@1.18.31, @opencode-ai/sdk@1.18.31; dual V1/V2 support)
  • data/plugins/opencode-agents-sidebar.yaml (Opencode Agents Sidebar): v1 → v2 (package.json: @opencode/plugin, @opencode/theme)
  • data/plugins/opencode-ntfy.sh.yaml (OpenCode ntfy.sh): v1 → v2 (package.json: @opencode/plugin)
  • data/plugins/opencode-short-term-memory.yaml (opencode-short-term-memory): v1 → v2 (package.json: @opencode/plugin, @opencode-ai/plugin@1.14.25, @opencode-ai/sdk@1.14.25; dual V1/V2 support)
  • data/plugins/opencode-snip.yaml (opencode-snip): v1 → v2 (package.json: @opencode/plugin)
  • data/plugins/opencode-telemetry.yaml (Opencode Telemetry): v1 → v2 (package.json: @opencode/plugin, @opencode-ai/plugin@^1.14.28, @opencode-ai/plugin@*; dual V1/V2 support)
  • data/plugins/opencode-usage-monitor.yaml (Opencode Usage Monitor): v1 → v2 (package.json: @opencode/plugin, @opencode/theme)
  • data/plugins/toon-config.yaml (toon-config): v1 → v2 (package.json: @opencode/ai, @opencode/plugin)

@github-actions github-actions Bot added the health Catalog link-rot and maintenance tracking label Oct 18, 2026
@sourcery-ai

sourcery-ai Bot commented Oct 18, 2026 •

Copy link
Copy Markdown
Reviewer's guide (collapsed on small PRs)

Reviewer's Guide

The PR updates plugin catalog metadata so the nightly health check recognizes BRHP and opencode-snip as migrated to OpenCode V2, removing them from the V1 sunset path.

File-Level Changes

Change Details Files
Mark two plugins as compatible with OpenCode V2.
  • Update BRHP compatibility metadata from v1 to v2.
  • Update opencode-snip compatibility metadata from v1 to v2.
data/plugins/brhp.yaml
data/plugins/opencode-snip.yaml

Possibly linked issues

  • #714: The PR updates two plugin entries to compat: v2, directly showing the V2 support the issue asks to encourage.

Tips and commands

Interacting with Sourcery

  • Trigger a new review: Comment @sourcery-ai review on the pull request.
  • Continue discussions: Reply directly to Sourcery's review comments.
  • Generate a GitHub issue from a review comment: Ask Sourcery to create an
    issue from a review comment by replying to it. You can also reply to a
    review comment with @sourcery-ai issue to create an issue from it.
  • Generate a pull request title: Write @sourcery-ai anywhere in the pull
    request title to generate a title at any time. You can also comment
    @sourcery-ai title on the pull request to (re-)generate the title at any time.
  • Generate a pull request summary: Write @sourcery-ai summary anywhere in
    the pull request body to generate a PR summary at any time exactly where you
    want it. You can also comment @sourcery-ai summary on the pull request to
    (re-)generate the summary at any time.
  • Generate reviewer's guide: Comment @sourcery-ai guide on the pull
    request to (re-)generate the reviewer's guide at any time.
  • Resolve all Sourcery comments: Comment @sourcery-ai resolve on the
    pull request to resolve all Sourcery comments. Useful if you've already
    addressed all the comments and don't want to see them anymore.
  • Dismiss all Sourcery reviews: Comment @sourcery-ai dismiss on the pull
    request to dismiss all existing Sourcery reviews. Especially useful if you
    want to start fresh with a new review - don't forget to comment
    @sourcery-ai review to trigger a new review!

Customizing Your Experience

Access your dashboard to:

  • Enable or disable review features such as the Sourcery-generated pull request
    summary, the reviewer's guide, and others.
  • Change the review language.
  • Add, remove or edit custom review instructions.
  • Adjust other review settings.

Getting Help

@coderabbitai

coderabbitai Bot commented Oct 18, 2026 •

Copy link
Copy Markdown

Important

Review skipped

Bot user detected.

To trigger a single review, invoke the @coderabbitai review command.

Run configuration
  • Source mode: Auto
  • Repository: Unavailable
  • Branch: Unavailable
  • File: No configuration file from this repository applied
  • Commit: Unavailable
  • Layers: defaults
  • Review profile: CHILL
  • Plan: Advanced
  • Run ID: 213cb2ae-0ebf-4563-82a7-266311fad463

You can disable this status message by setting the reviews.review_status to false in the CodeRabbit configuration file.

Use the checkbox below for a quick retry:

  • Trigger review
  • Autofix · Keep fixing CodeRabbit findings and required CI, and resolving merge conflicts

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

CodeRabbit Verify

  • Run CodeRabbit Verify to test the changes in this pull request.

sourcery-ai[bot]
sourcery-ai Bot previously approved these changes Oct 18, 2026

@sourcery-ai sourcery-ai Bot left a comment

Copy link
Copy Markdown

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Hey - I've reviewed your changes and they look great!

Sourcery assessment

Approved.


Sourcery is free for open source - if you like our reviews please consider sharing them ✨

@github-actions
github-actions Bot force-pushed the bot/health-compat branch 7 times, most recently from b8121aa to 25198a4 Compare October 25, 2026 09:53
@github-actions
github-actions Bot force-pushed the bot/health-compat branch 4 times, most recently from fe6a8f4 to c210c07 Compare October 29, 2026 11:35
@sourcery-ai
sourcery-ai Bot dismissed their stale review October 29, 2026 11:35

Sourcery withdrew this approval because it has stopped reviewing this pull request.

@sourcery-ai

sourcery-ai Bot commented Oct 29, 2026

Copy link
Copy Markdown

Sourcery has withdrawn its approval of this pull request. It auto-reviews a pull request 5 times, and this push is past that limit, so the approval no longer reflects code Sourcery has read.

Comment @sourcery-ai review to get a fresh review, which can approve again.

Re-reviews, rate limits and approvals

@github-actions
github-actions Bot force-pushed the bot/health-compat branch 4 times, most recently from 9f7a6b2 to 69b1902 Compare November 2, 2026 13:36
@sonarqubecloud

sonarqubecloud Bot commented Nov 3, 2026

Copy link
Copy Markdown

This branch has not been deployed

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

Labels

health Catalog link-rot and maintenance tracking

Projects

None yet

Development

Successfully merging this pull request may close these issues.

0 participants