Prepare plugin 0.1.0 release candidate - #24
Merged
Conversation
Distinguish artifact compilation from retained GitHub publication so agents can report safe phases and retries without guessing at causes. Bind the alpha.5 plugin candidate to the API 0.2 and CLI alpha.3 contract, and test singleton recovery and release-window boundaries.
Use ordinary versions so compatibility lines, not prerelease labels, carry the breaking-change policy. Keep next as a separate approval-gated channel, pin the published CLI, and guard OIDC publication and release ordering.
Separate checkout tooling identity from the installable release and rehearse registry, protected-tag, and catalog ordering before an immutable tag is created. Reconcile only coherent exact identities after publication so catalog promotion and later CI remain viable.
Compare a consumed candidate compatibility document with its immutable protected-tag blob so the recorded tarball digest cannot drift after release. Pin the exact release-order invocations and rejection paths that enforce this boundary.
raghubetina
changed the title
raghubetina
marked this pull request as ready for review
August 7, 2026 21: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
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
0.1.0with the pre-1.0 minor-breaking/patch-compatible policy and no compatibility aliases0.1.0main revision and API-contract0.2.xcompatibility linenextas an approval-gated channel independent of SemVer and leavelatestand the public marketplace catalog unchangedVerification
d37d8b6775a0b97ce10bd651485bd308fed1dda2gh skill publish --dry-runCandidate identity
0.1.002fad6cd2207f3d2ab7598f0aa67825520ebc5b807294e0c241774ee3ac6a89d8506cad9c9e4e6739f39d95a4e2cfb84b5e0ca63bd05ddec06400c7f27d0b8355d2d8de815c8d90761171bc42ef10f3e3635f4ed4614fa257d3c921b305acdabRelease boundary
This remains a draft source-integration PR. The public catalog still serves plugin alpha.3, npm
latestis not moved, and this PR does not authorize or perform a plugin publication, release tag, catalog promotion, service deployment, API-contract activation, or staging mutation. Service API 0.2 activation and plugin 0.1.0 publication/promotion remain an explicitly approved and announced maintenance-window sequence.