Skip to content

chore: validate plugin registrations against release-please config#70

Merged
yordis merged 1 commit into
mainfrom
yordis/ci-validate-plugins
May 27, 2026
Merged

chore: validate plugin registrations against release-please config#70
yordis merged 1 commit into
mainfrom
yordis/ci-validate-plugins

Conversation

@yordis

@yordis yordis commented May 27, 2026

Copy link
Copy Markdown
Member
  • Catch drift between plugin.json, marketplace.json, and release-please config/manifest before a release PR opens, so version bumps and new plugins never ship half-registered.

@cursor

cursor Bot commented May 27, 2026

Copy link
Copy Markdown

PR Summary

Low Risk
Adds validation-only tooling and CI; no runtime product or security behavior changes.

Overview
Adds automated checks so plugin folders stay aligned with marketplace and release-please metadata before releases.

A new scripts/validate-plugins.mjs walks each plugins/* directory and enforces plugin.json presence, directory/name match, semver versions, marketplace listing with ./plugins/<name> source, matching release-please-config.json package keys/components, and manifest versions equal to plugin.json. It also fails if marketplace, config, or manifest reference plugins that do not exist on disk.

A validate-plugins GitHub Actions workflow runs that script on PRs (path-filtered to plugin and registration files) and on pushes to main.

Reviewed by Cursor Bugbot for commit 184cdfb. Bugbot is set up for automated code reviews on this repo. Configure here.

@coderabbitai

coderabbitai Bot commented May 27, 2026

Copy link
Copy Markdown

Warning

Review limit reached

@yordis, we couldn't start this review because you've reached your PR review rate limit.

More reviews will be available in 9 minutes and 32 seconds. Learn how PR review limits work.

Your organization has run out of usage credits. Purchase more in the billing tab.

⌛ How to resolve this issue?

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.

We recommend that you space out your commits to avoid hitting the rate limit.

🚦 How do rate limits work?

CodeRabbit enforces hourly rate limits for each developer per organization.

Our paid plans include higher PR review limits than trial, open-source, and free plans. In all cases, reviews become available again over time. During sustained high-volume PR review activity, CodeRabbit may temporarily slow when the next review becomes available.

Please see our Fair Usage Limits Policy for further information.

ℹ️ Review info
⚙️ Run configuration

Configuration used: Organization UI

Review profile: CHILL

Plan: Pro

Run ID: a880b399-0f0b-4be6-999b-45ed70f2348b

📥 Commits

Reviewing files that changed from the base of the PR and between 5125fc9 and 184cdfb.

📒 Files selected for processing (2)
  • .github/workflows/validate-plugins.yml
  • scripts/validate-plugins.mjs
✨ Finishing Touches
🧪 Generate unit tests (beta)
  • Create PR with unit tests
  • Commit unit tests in branch yordis/ci-validate-plugins

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

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

Signed-off-by: Yordis Prieto <yordis.prieto@gmail.com>
@yordis yordis force-pushed the yordis/ci-validate-plugins branch from 27308ee to 184cdfb Compare May 27, 2026 07:21
@yordis yordis changed the title ci: validate plugin registrations against release-please config chore: validate plugin registrations against release-please config May 27, 2026
@yordis yordis merged commit b78248f into main May 27, 2026
6 checks passed
@yordis yordis deleted the yordis/ci-validate-plugins branch May 27, 2026 07:24
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