ci(publish): 'publish' branch trigger + idempotent OIDC release#15
Merged
Conversation
…prx-czni) Release flow: bump version on main, fast-forward main into the `publish` branch, push — CI publishes via Trusted Publishing (OIDC, keyless). Adds `branches: [publish]` alongside the existing v* tag + workflow_dispatch triggers. Idempotency guard: the job checks `npm view <name>@<version>` and SKIPS the publish when that version already exists, so re-pushing `publish` without a version bump is a clean no-op rather than a 'version already exists' red build. Co-Authored-By: Claude Opus 4.8 (1M context) <noreply@anthropic.com>
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.
prx-czni. Adds a dedicated
publishbranch as a release trigger (alongsidev*tags + manual dispatch), publishing via npm Trusted Publishing (OIDC — keyless, no token, no 2FA).Release flow: bump version on
main→ fast-forwardmainintopublish→ push → CI publishes whatever version is in package.json.Idempotency (the key bit): the job checks
npm view <name>@<version>and skips the publish if that version already exists — so re-pushingpublishwithout a version bump is a clean no-op, never a 'version already exists' red build.After merge I'll create the
publishbranch and push it to validate the trigger + idempotency end-to-end (it'll no-op since 0.2.0 is already live). The actual OIDC publish path validates on the next version bump.🤖 Generated with Claude Code