Updates and removal
Publisher updates, Account Mode version pinning and verified rollback for content add-ons.
Updates and removal
Publisher workflow
Every new add-on version requires its own independently reviewed immutable GitHub Release, committed source provenance and signed registry approval.
- Increase
versioninnextguide-addon.json. - Commit and push the changed files to the source repository.
- Open the NextGuide Publisher GitHub App and select the repository.
- Validate and submit the new version for independent review.
- Wait for the signed registry to contain the approved release.
Do not overwrite existing GitHub Release assets to make a silent change. Create a new version instead.
Account Mode installation lifecycle
The owner-facing Add-ons page can install, enable/disable, update, roll back and uninstall content-only v1 releases when the site's NextGuide package satisfies their declared compatibility range.
| Action | What happens |
|---|---|
| Install | Recheck signed registry, verify exact remote archive and place content in private storage, initially disabled |
| Enable | Recheck latest signed approval and local integrity before marking content enabled |
| Disable | Mark content disabled without deleting settings |
| Update | Recheck the newer reviewed version, then atomically advance the pinned version |
| Rollback | Verify an already stored, still-approved version and restore it in a disabled state |
| Uninstall | Remove the installed record; preserve private add-on settings and historical blobs for recovery |
Owner authentication and same-origin checks apply to every mutation. A concurrent change requires refreshing the page rather than overwriting another update. A revoked or stale release cannot be reactivated or rolled back.
Current milestone boundaries
Enabled, reviewed v1 Markdown content can be opened at the site's dedicated /docs/addons/<publisher.addon>/ route (or /addons/<id>/ when the docs base is root). Fresh Account Mode installations now include enabled and still-approved Markdown pages in their public docs sidebar and search index. Pages are excluded when disabled, revoked, corrupted or no longer covered by a fresh signed registry. Already-installed sites need an explicit generated-file refresh to receive the updated navigation adapter; authored MDX must not be overwritten. Executable add-ons, privileged permissions, secrets, React components and automatic background update checks remain future milestones. Legacy v1 content is never compiled as untrusted MDX.
For details see Account Mode marketplace and runtime API.