Repository navigation
feat(account): secure Markdown add-on install, update and rollback in Studio - #111
Merged
Merged
Conversation
Preserve completed private journal and reviewed archive transport milestones.
…nd signed downloads
… freshness renewal
This was referenced Nov 8, 2026
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
NextGuide Add-ons — Account Mode v1 lifecycle
Wires the previously merged signed catalog, DNS-pinned GitHub artifact downloader, and private installation journal into actual owner-authenticated Account Mode UI.
Install,Enable/Disable,Update,Rollback,Uninstall, native shadcn/Base UI confirmation dialog and status feedback.Boundaries
Only content-only Markdown v1 is supported; no third-party JavaScript is launched. The site does not yet mount installed Markdown into public docs. Releases targeting
>=1.0.0correctly remain incompatible with the current alpha package. Executable v2 packages, secrets, account jobs, React widgets, public rendering and approval of privilege changes remain separate security milestones. No private ngapi code or npm release changes.