Plugin registry updates should go through PR → validate → auto-merge,
same flow as community plugins. Each plugin repo handles its own
registry PR via CI.
Co-Authored-By: Claude Opus 4.6 (1M context) <noreply@anthropic.com>
After publishing to npm, CI clones plugin-registry repo,
updates version in all built-in plugin entries, rebuilds
registry.json + README, and pushes. Requires REGISTRY_PAT secret.
Co-Authored-By: Claude Opus 4.6 (1M context) <noreply@anthropic.com>
SDK needs dist/index.d.ts from CLI tsc build. In CI, build:publish
runs after fresh install with no dist/. Now build-publish.ts auto-runs
tsc if dist/index.d.ts missing, and CI runs pnpm build first.
Co-Authored-By: Claude Opus 4.6 (1M context) <noreply@anthropic.com>
- SDK peerDependencies: @openacp/cli (not workspace name)
- build-publish.ts builds and prepares both packages
- GitHub Actions publishes both on tag push
- SDK version synced with CLI version
- Template string deps excluded from build verification
Co-Authored-By: Claude Opus 4.6 (1M context) <noreply@anthropic.com>