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>
- Updated the Telegram notification workflow to trigger on branch pushes instead of tags.
- Improved commit notification formatting to include the number of new commits and a direct link to the diff.
- Streamlined the pull request notification process with enhanced message formatting and author links.
- Replaced the previous notification method with a direct API call to Telegram for better control and customization.
- Updated Telegram notification messages to include clickable links for authors and PR creators, improving accessibility and navigation.
- Adjusted formatting for triggered events to provide a consistent user experience.
- Updated the telegram-notify workflow to include the repository name in notifications for better context.
- Enhanced commit messages formatting to display author names and commit counts more clearly.
- Improved pull request notifications by including the status and branch details, making it easier to track changes.
- Refined release notifications to highlight the author and provide clearer links to release notes.
- Adjusted CI failure notifications to include the short commit SHA for easier identification of issues.
- Enhanced the telegram-notify workflow by consolidating notification steps and utilizing curl for sending messages, improving reliability and flexibility.
- Introduced environment variables for Telegram bot configuration, streamlining the notification process for push events, pull requests, releases, and CI failures.
- Removed redundant steps and optimized message formatting for better clarity in notifications.
- Modified the workflow configuration to trigger on all branches instead of ignoring tags, ensuring notifications are sent for all relevant branch activities.
- Changed the Telegram action version from v1 to master in multiple notification steps within the workflow file to ensure the latest features and fixes are utilized.
- Modified deep link construction in action-detect.ts and adapter.ts to include threadId, allowing navigation to specific messages within forum topics.
- Updated buildDeepLink function in permissions.ts to accept threadId as a parameter for improved link accuracy.
- Enhanced comments for clarity on deep link structure and usage.