fix(ci): add E403 guard to CLI publish step — idempotent on re-runs#1330
Merged
fix(ci): add E403 guard to CLI publish step — idempotent on re-runs#1330
Conversation
Closes #1329 The `Publish @red-codes/agentguard (CLI)` step was the only publish step in the workflow without "already published" handling. When the release workflow is triggered multiple times (e.g. draft→publish or manual re-run), subsequent runs fail with E403 rather than gracefully skipping. All library package steps already use this pattern; apply it to the CLI step for consistency. Co-Authored-By: Claude Sonnet 4.6 <noreply@anthropic.com>
Collaborator
Author
|
Auto-merged by PR Merger Agent. All quality gates passed. |
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
Publish @red-codes/agentguard (CLI)step was the only publish step without E403/"already published" handlingnpm error 403instead of gracefully skippingRoot cause
publish.ymlline 144 (before this fix) ran a barepnpm publishwith no error guard. All other publish steps already wrap the command to treatE403: already publishedas a warning, not a failure.Evidence
v2.10.2 release (2026-03-29) triggered 4 workflow runs. Run 3 succeeded; run 4 failed with
E403: cannot publish over previously published versions: 2.10.2. Tracked in #1329.Test plan
aguardwrapper step exactly::notice::and skip)Closes #1329
🤖 Generated with Claude Code