Skip to content

[Phase 2] Cut ci-failure-analyst initial release + channel tags and extend the release-channel ruleset #688

Closed

Description

@github-actions

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

  1. An immutable ci-failure-analyst/v0.1.0 annotated tag exists on origin, pointing at an on-main commit that contains ci-failure-analyst-reusable.yml.
  2. A moving ci-failure-analyst/stable channel tag exists on origin, pointing at the same commit as the release tag.
  3. Both tags were produced via scripts/cut-release.sh ci-failure-analyst 0.1.0 --channel stable --push (through the generalized tooling, not ad-hoc git tag).
  4. The release-channel-tags repository ruleset target is extended to include ci-failure-analyst/** (restricting update/deletion, bypass limited to OrganizationAdmin + the automation Integration app), mirroring the existing pr-review/** / dev-lead/** protection.
  5. The commit SHA the tags point at is recorded in the issue/PR for audit.

Tasks / Subtasks

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_agent must accept ci-failure-analyst first, 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/** and dev-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/stable
  • repository ruleset: release-channel-tags

Story prepared by the BMAD Scrum Master (Bob) for epic #684. Status: ready-for-dev.

Activity

  1. added
    initiativeEpic / initiative tracking issue
    initiative:holdInitiative driver must not release this issue (human hold)
    dev-lead:hands-offExclude from dev-lead agent automation
    on Jun 14, 2026
  2. don-petry commented on Jul 14, 2026

    @don-petry
    Collaborator

    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-scoped v1-{next,ring0,ring1,stable} channels (cut after cut-release.sh learned about ci-failure-analyst in PR #1165). The release-channel ruleset already covers these via its generic refs/tags/** pattern, so no separate extension was needed. Closing as completed. — Claude Code

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Metadata

Metadata

Assignees

No one assigned

    Labels

    dev-lead:hands-offExclude from dev-lead agent automationinitiativeEpic / initiative tracking issueinitiative:holdInitiative driver must not release this issue (human hold)

    Type

    No type

    Projects

    No projects

      Milestone

      No milestone

      Relationships

      None yet

      Development

      No branches or pull requests

      Issue actions