ci: publish the initial Playproof npm release - #230
Closed
drewstone wants to merge 1 commit into
Closed
Conversation
Contributor
Author
|
Closing: Playproof is released from its own repository (tangle-network/playproof) via that repo's tag-triggered publish workflow. agent-sdk must not act as a credential relay for another package. No changes from this PR are needed. |
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
Adds the one-shot, idempotent npm publisher for
@tangle-network/playproof@0.1.0in the repository that already owns the organization’s npm release credential.After merge, the workflow checks out the immutable public
v0.1.0tag, verifies package identity, performs a frozen pnpm 11 install, compiles Python workers, runs the full package/export gates, packs exactly one tarball, publishes only if the version is absent, and installs/imports all 12 public entrypoints in a clean consumer.This PR will not merge until
tangle-network/playproofhas a verified zero-parentmainroot and matchingv0.1.0tag. The temporary publisher workflow will be deleted after registry verification.