Skip to content

[Phase 2] Generalize cut-release.sh to release non-agent reusables #670

Closed as not planned

Description

@github-actions

Story

As a release engineer,
I want teach cut-release.sh and its tests to cut releases for ci-failure-analyst (and future non-agent reusables),
so that the same audited release primitive cuts tags for every first-party reusable, not just the two agents.

Acceptance Criteria

  1. scripts/cut-release.sh ci-failure-analyst 1.0.0 --channel stable --dry-run succeeds (the name is accepted by valid_agent).
  2. release_ref/channel_ref emit ci-failure-analyst/v1.0.0 and ci-failure-analyst/stable.
  3. tests/test_cut_release.bats covers the new name (valid + dry-run path) and still rejects an unknown name with a non-zero exit.
  4. docs/release/versioning.md "What is versioned" table gains a ci-failure-analyst row (reusable workflow + any scripts it carries — currently none beyond the reusable).

Tasks / Subtasks

Dev Notes

  • valid_agent() currently hardcodes pr-review | dev-lead (scripts/cut-release.sh). The pure helpers (valid_agent, validate_version, release_ref, channel_ref) are source-guarded so tests/test_cut_release.bats can source the file without running main — preserve that guard.
  • Do NOT change --dry-run/--push semantics or remove the immutable-tag overwrite refusal.
  • versioning.md currently scopes versioning to dev-lead/pr-review only; generalize the table and prose minimally without contradicting the agent-specific channel docs.
  • Testing standard: bats lives under tests/, run with bats tests/test_cut_release.bats; keep cases hermetic (use --dry-run, no real git push).

Project Structure Notes

Edits scripts/cut-release.sh, tests/test_cut_release.bats, docs/release/versioning.md. No new files.

References

  • scripts/cut-release.sh#valid_agent
  • tests/test_cut_release.bats
  • docs/release/versioning.md#what-is-versioned

Likely target surface

  • scripts/cut-release.sh
  • tests/test_cut_release.bats
  • docs/release/versioning.md

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

Activity

  1. added 18 commits that reference this issue on Aug 2, 2026
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

    initiativeEpic / initiative tracking issue

    Type

    No type

    Projects

    No projects

      Milestone

      No milestone

      Relationships

      None yet

      Development

      No branches or pull requests

      Issue actions