Publish your extension

Publishing is release-driven: after a one-time registration, every GitHub Release you cut appears here automatically. No accounts, no tokens — your registry identity is your GitHub identity.

1. Set up releases (once per repo)

New extension? npx create-silo-extension scaffolds everything, including the publish workflow. Existing extension: add publish-extension-action — then publishing is just npm version patch && git push --follow-tags.

2. Register (once per extension)

Fill this in; it opens GitHub with the registration file pre-filled. A bot validates it and merges automatically — no waiting for a human. The id is derived as <github-owner>.<name>: that binding is checked, so nobody can publish under your name.

3. Done

After the bot merges, the registry ingests your latest release and your extension goes live at extensions.getsilo.dev/<id>. Publish from CI (the action above) and your listing gets the verified build badge — cryptographic proof the tarball was built from your repo.