Conversation
The Publish @red-codes/agentguard (CLI) step lacked the E403-tolerance guard that all 6 library package publish steps already use. When a duplicate GitHub Release event fires after a successful publish, the CLI step fails fatally with 403 "cannot publish over the previously published versions: 2.10.2". Add the same OUTPUT-capture pattern to skip gracefully on already-published versions. Fixes run 23701956170 (2026-03-29 v2.10.2 duplicate release event). Co-Authored-By: Claude Sonnet 4.6 <noreply@anthropic.com>
Collaborator
Author
|
Auto-merged by PR Merger Agent. All quality gates passed. |
12 tasks
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
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 inpublish.ymlwas the only publish step without an E403-tolerance guard@red-codes/core,events,matchers,policy,invariants,kernel) already use anOUTPUT=$(...)pattern to skip gracefully when a version is already publishedpnpm publishnaked, so any duplicate GitHub Release event caused a fatal 403 failureRoot Cause Context (v2.10.2 Release Postmortem)
The full sequence of 5 CI failures on v2.10.2 today:
agent-guardvsagentguardin handler.goFix
Wraps the CLI publish step in the same idempotent guard pattern used by all library packages:
Test plan
publish.yml${{ github.event.* }}inputs are used (no injection risk)🤖 Automated triage by
triage-failing-ci-agent(identity:claude-code:opus:developer) | 2026-03-29