Skip to content

feat(catalog): add bouncer as a github-source plugin - #22

Merged
chrispezza merged 1 commit into
mainfrom
feat/add-bouncer
Sep 23, 2026
Merged

chrispezza merged 1 commit into
mainfrom
feat/add-bouncer

Conversation

@chrispezza

Copy link
Copy Markdown
Contributor

What

Adds bouncer to .claude-plugin/marketplace.json with a github source (clownware/bouncer) and a row in the README's plugin table.

Why

Bouncer has been public since 2026-09-18 with its plugin manifest at v0.2.6, but it was only installable from its own single-plugin marketplace. The clownware.org marketplace page promises "one marketplace add, every plugin", and the site's plugin directory is generated from this manifest, so listing it here is what puts it on the site.

How

  • github source because the plugin's .claude-plugin/plugin.json sits at the repo root (no path to give git-subdir). validate.yml already accepts this type and requires repo.
  • No version in the entry: plugin.json owns it (MAINTAINING.md, version resolution order).
  • Description mirrors the plugin's own manifest and README so /plugin listings say the same thing as the repo.

Companion changes: clownware/bouncer#103 adds the LICENSE file the manifest already names; the clownware-website sync script learns to resolve github sources.

🤖 Generated with Claude Code

Bouncer lives in its own repository with its plugin manifest at the root,
so it is listed with a github source rather than git-subdir. Its version
stays in the plugin's own plugin.json per docs/MAINTAINING.md.

Co-Authored-By: Claude Fable 5.1 <noreply@anthropic.com>
@chrispezza
chrispezza merged commit 20a7abc into main Sep 23, 2026
2 checks passed
@chrispezza
chrispezza deleted the feat/add-bouncer branch September 23, 2026 18:01
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