refactor: rename @aictrl/plugin → @aictrl/plugin-sdk#66
Closed
byapparov wants to merge 1 commit into
Closed
Conversation
The npm package name @aictrl/plugin is used by a separate telemetry delivery vehicle with its own release cadence. Our monorepo's packages/plugin (plugin-author SDK: types, shell/tool helpers) collides on the name and can't be published from the CLI release workflow. Rename the monorepo package to @aictrl/plugin-sdk: - packages/plugin/package.json: name + reset version to 0.1.0 (first publish of the renamed package) - Root package.json + packages/cli/package.json: update workspace dep key - Source imports across packages/cli/src/ (8 files) - .opencode/tool/*.ts internal tooling imports - Config auto-install logic (packages/cli/src/config/config.ts) now writes @aictrl/plugin-sdk into user project package.json - Tests updated to match - Publish workflow step renamed - CONTRIBUTING.md and .opencode/agent/translator.md references updated User projects with existing @aictrl/plugin in their package.json will no longer auto-receive updates; the CLI will add @aictrl/plugin-sdk on next run. Documented path for plugin authors: depend on @aictrl/plugin-sdk. Co-Authored-By: Claude Opus 4.7 (1M context) <noreply@anthropic.com>
|
Now Step 2 — build concern manifests:S = 36 changed lines across bug hunter files, so N = 1. Total subagents = 3 (Security + Consistency + 1 Bug Hunter). Now extracting file patches for each manifest:Now dispatching all 3 subagents in parallel:[] |
Contributor
Author
|
Superseded by a proper inlining into the CLI package (no separate plugin-sdk npm package at all) — new PR incoming. |
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
1 participant
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
The npm package name `@aictrl/plugin` is taken by a separate telemetry-delivery vehicle with an independent release cadence. Our monorepo's `packages/plugin` (the plugin-author SDK — types and helpers for writing CLI plugins) has been publishing under the same name, which is how we ended up unable to release v0.3.3: the publish workflow tried to push `@aictrl/plugin@1.2.16` but npm already has `2.0.0` from the telemetry package.
Renaming the monorepo package to `@aictrl/plugin-sdk` frees the name and removes the collision.
Changes
User impact
Plugin authors currently depending on `@aictrl/plugin` (the SDK, not the telemetry one) should switch to `@aictrl/plugin-sdk`. User projects with existing `@aictrl/plugin` entries will keep working (the types are compatible between versions on their disk), but on next CLI run the CLI will add `@aictrl/plugin-sdk` to `package.json` — so both may briefly coexist until the old one is cleaned up manually.
Follow-up
Test plan
🤖 Generated with Claude Code