ci: add manual public-npm release workflow (OIDC trusted publishing) - #5
Merged
Conversation
Promotes a chosen tag to public reply-cli via workflow_dispatch. Rebuilds from the tag, publishes with provenance (OIDC, no token). Flips the GitHub Release to full/latest; gated by the npm-public environment. Co-Authored-By: Claude Opus 4.8 (1M context) <noreply@anthropic.com>
vigubikReply
enabled auto-merge
July 23, 2026 20:24
vigubikReply
disabled auto-merge
July 23, 2026 20:24
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.
Adds
.github/workflows/publish-public.yml— a manual promotion of a tested tag to public npm (reply-cli).v0.3.0).NPM_TOKEN; publishes with provenance.reply-cli, publishes, then flips that tag's GitHub Release to full/latest.npm-publicenvironment (required reviewers:@reply-team/release-mergers, restricted tomain).The workflow filename (
publish-public.yml) and environment (npm-public) are fixed by the npm trusted-publisher config and must not change.Internal auto-release is unaffected (this is
ci:, no version bump).Ref: REPLY-51236