Repository navigation
Closed
Labels
dev-lead:hands-offExclude from dev-lead agent automationExclude from dev-lead agent automationinitiativeEpic / initiative tracking issueEpic / initiative tracking issueinitiative:holdInitiative driver must not release this issue (human hold)Initiative driver must not release this issue (human hold)
Description
Story
As a OrganizationAdmin,
I want cut the immutable ci-failure-analyst/v0.1.0 release tag, move ci-failure-analyst/stable onto it, and extend the release-channel-tags ruleset to protect ci-failure-analyst/**,
so that callers can pin to a sanctioned, protected channel tag the same way they pin dev-lead/pr-review.
Acceptance Criteria
- An immutable
ci-failure-analyst/v0.1.0annotated tag exists on origin, pointing at an on-main commit that containsci-failure-analyst-reusable.yml. - A moving
ci-failure-analyst/stablechannel tag exists on origin, pointing at the same commit as the release tag. - Both tags were produced via
scripts/cut-release.sh ci-failure-analyst 0.1.0 --channel stable --push(through the generalized tooling, not ad-hocgit tag). - The
release-channel-tagsrepository ruleset target is extended to includeci-failure-analyst/**(restricting update/deletion, bypass limited to OrganizationAdmin + the automation Integration app), mirroring the existingpr-review/**/dev-lead/**protection. - The commit SHA the tags point at is recorded in the issue/PR for audit.
Tasks / Subtasks
- Cut the release + channel tags through cut-release.sh. (AC: test issue from agent #1, Go-live improvements for PR review agent #2, Add @claude delegation, auto-merge, and rebase handling #3)
- Dry-run first:
cut-release.sh ci-failure-analyst 0.1.0 --channel stable --dry-run. - Then
--pushto publish (requires push rights the agent token does not have — admin action).
- Dry-run first:
- Extend the release-channel-tags ruleset to cover ci-failure-analyst/**. (AC: Optimize review: small-PR and incremental fast paths #4)
- Update the ruleset target patterns; keep bypass scoped to OrganizationAdmin + Integration app, consistent with AGENTS.md.
- Record the tagged commit SHA for the audit trail. (AC: feat: add Copilot engine support via REVIEW_ENGINE toggle #5)
Dev Notes
- HANDS-OFF: pushing tags and editing the repository ruleset require privileges the dev-lead GITHUB_TOKEN does not have — per AGENTS.md the agents (running as GITHUB_TOKEN) cannot create/move release-channel tags; only an OrganizationAdmin or the promotion automation can. This is a human/admin runbook item, not auto-released to dev-lead.
- Depends on story id 2:
cut-release.sh valid_agentmust acceptci-failure-analystfirst, otherwise the cut fails with 'unknown agent'. - Version choice: start at v0.1.0 (initial, pre-1.0) unless humans prefer v1.0.0 to signal production-ready — see open_questions. cut-release.sh enforces strict MAJOR.MINOR.PATCH and refuses to overwrite an existing immutable release tag.
- The repo currently has the ruleset only for
pr-review/**anddev-lead/**(AGENTS.md). Until ci-failure-analyst/** is added, the channel tag is unprotected — do both in this story. - No application code changes; this is tag + settings only. Repinning callers to the new tag is the separate story id 5.
Project Structure Notes
No file changes in-repo beyond an optional audit note; the artifacts are git tags + a repository ruleset (GitHub settings), consistent with how pr-review/dev-lead tags are managed.
References
- scripts/cut-release.sh (usage)
- AGENTS.md (Release channel tags; ruleset targets pr-review/, dev-lead/)
- docs/release/versioning.md (Tag scheme)
- docs/release/runbook.md
Likely target surface
git tags: ci-failure-analyst/v0.1.0, ci-failure-analyst/stablerepository ruleset: release-channel-tags
Story prepared by the BMAD Scrum Master (Bob) for epic #684. Status: ready-for-dev.
Metadata
Metadata
Assignees
Labels
dev-lead:hands-offExclude from dev-lead agent automationExclude from dev-lead agent automationinitiativeEpic / initiative tracking issueEpic / initiative tracking issueinitiative:holdInitiative driver must not release this issue (human hold)Initiative driver must not release this issue (human hold)
Activity
don-petry commentedon Jul 14, 2026
Completed via the #1159 versioning work (out-of-band). The ci-failure-analyst release + channel tags now exist on the remote:
ci-failure-analyst/{next,ring0,ring1,stable},v1.0.0, and the major-scopedv1-{next,ring0,ring1,stable}channels (cut aftercut-release.shlearned about ci-failure-analyst in PR #1165). The release-channel ruleset already covers these via its genericrefs/tags/**pattern, so no separate extension was needed. Closing as completed. — Claude Code