Prepare Claude plugin alpha.4 candidate - #23
Merged
Conversation
Align the portable Skill with the current bounded Compiler so agents can author only shapes the service can compile. Prepare immutable alpha.4 package bytes while leaving the public catalog on published alpha.3 until a separate promotion. Record the bounded public install evidence and require npm OIDC publication without a token fallback.
Checking only the public package version could admit different bytes under the pinned SemVer. Reconcile exact local and registry archives by inventory, file content, and modes before and after release approval while ignoring gzip framing.
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
1 participant
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.
Summary
@firstdraft.com/claude-code@0.1.0-alpha.4while deliberately leaving the public marketplace pinned to published alpha.3@firstdraft.com/cli@0.1.0-alpha.2registry package by inventory, content, and modes, and require npm trusted publishing for the plugin releaseRelease boundary
This prepares an unpromoted candidate only. Merging it does not publish a package, create a release tag, promote the public catalog, or deploy First Draft.
The candidate tarball SHA-256 is:
d662b86f33dd75c7a22e89e092c51497b0df9e14958a369d7ac96b85088ac3bdVerification
git diff --check