Repository navigation
Plugin SDK 1.1: offline bundles, provenance and reviewed updates - #27
Merged
Merged
Conversation
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.
Plugin authors and host operators can now distribute reviewed dependencies and update an installed plugin with explicit provenance, permission and settings review. The 1.1 release adds deterministic offline bundles and CycloneDX 1.6 SBOMs, operator-owned Ed25519 signing/verification, digest-bound approval and active-job version retention, durable update journals, and developer-triggered upstream candidates.
The working installed example executes a real bundled dependency, switches versions while an old command finishes, rolls back under a new approval, and reads the persisted state. Existing unsigned archives and the stable 1.0 API remain compatible. New entry points are Node-only; SDK runtime dependencies remain zero.
Validation: local
npm run checkpasses 495 tests, declaration consumers, 96 generated schemas, six generated projects and the independent packed example. Ten new runtime fixtures validate against their schemas; the generated SBOM validates against the official CycloneDX 1.6 schema. Tests include process termination/restart, uncertain journal acknowledgement, conflicts, cancellation, expired/revoked keys and bounded upstream fetches. Windows/Linux × Node22/24 CI and the existing benchmark guards run on this PR.Limits: trusted host ports enforce execution authority; signatures do not grant execution or prove code safety. Activation/rollback does not undo external effects. Security audit and vulnerability validation remain deferred at the owner's request; this release records functional acceptance only.