Publish and review an add-on

NextGuide Publisher is the supported browser workflow for content-only v1 add-ons. It authenticates through the NextGuide Publisher GitHub App—no personal access token is needed for the web workflow.

Before you submit

1. Create a public repository using the official add-on template.
2. Set the manifest's id, repository, version, author, and icon.
3. Commit and push the files to your repository's default branch.
4. Sign in through the NextGuide Publisher GitHub App and select the repository in its publisher portal.
5. Run validation and fix every reported issue before submitting for review.

{
  "id": "acme.hello-world",
  "version": "0.1.0",
  "repository": "https://github.com/acme/hello-world"
}

How publishing works

The GitHub App checks repository access and source files, creates or reuses a matching immutable GitHub Release archive, then submits its pinned commit and SHA-256 for independent registry review. A moderator checks the release before approval.

A release is not published to the trusted catalog merely because it exists on GitHub.

What if submission fails after creating a Release?

Return to the publisher after correcting the problem. The publisher can reuse an existing asset only if its hash and size match; do not overwrite a published artifact or bump the version to retry an identical upload.

After approval

The approved release appears in the signed add-on catalog. Developers can track their own submissions through the publisher portal.

Updates require a higher SemVer version and new review. Publishers can withdraw their own add-on; the owner can revoke releases from the private admin review dashboard. Withdrawal removes releases from the active catalog but does not erase audit history or uninstall existing sites' copies.

Account Mode's end-user marketplace installer is not implemented yet. The publishing portal is for developers, not the in-site add-on installer.

See Updates & removal for the full lifecycle.