Repository navigation
Add deployment plugins for canvases - #12
Merged
Merged
Conversation
nicosuave
marked this pull request as ready for review
September 7, 2026 20:02
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.
Allow deployments to install browser libraries and authenticated server functions through
canvas.plugins.ts. Browser packages share the Canvas React runtime; functions receive the verified caller and configured secret bindings through gallery, private standalone, and MCP transports. Public standalone views cannot invoke functions.Includes compiler types, JSON schema validation,
pluginCall, MCP discovery, documentation, and regression coverage. Targeted plugin, authentication, browser, build, and installed-package checks passed; the broad compiler rerun is deferred to CI after local timeouts under extreme machine load.