Skip to content

Tag-based release pinning for ALL first-party reusable workflows + org-wide compliance enforcement #684

Closed
6 of 6 issues completed

Description

@github-actions

Extend the channel-tag release-pinning standard already adopted by dev-lead (@dev-lead/stable) and pr-review (@pr-review/stable) to every first-party reusable workflow in this repo, and make tag-pinning a CI-enforced standard rather than per-workflow bespoke tests.

Why

First-party reusables are pinned inconsistently. ci-failure-analyst-reusable.yml is currently pinned to an off-main SHA (0ef7b6150516c4fa447700b4902e8ed406bcfb99 # main) in three places — .github/workflows/ci-failure-analyst.lock.yml, templates/ci-failure-analyst.yml, and docs/aw/ci-failure-analyst.md. The annotated # main is inaccurate: that commit lives only on the unmerged fix/action-sha-pinning branch, so consumers copying the template inherit an off-main pin. The pr-review agent flagged this on #520 (MEDIUM, needs-human).

Direction

Replace SHA-# main pins with channel/version tags backed by cut-release.sh-style cuts, generalize the tooling + standard so it is not bespoke per agent, and add a single CI compliance check that rejects SHA / # main pins on any first-party reusable while still permitting the sanctioned mutable channel tags (<name>/stable, <name>/vX.Y.Z).

Shape of the work

  • Phase 1 — interim stopgap repin off the broken off-main SHA; generalize cut-release.sh + the release standard (versioning.md, AGENTS.md) to cover non-agent reusables.
  • Phase 2 — cut ci-failure-analyst initial release + channel tags (admin), repin callers/templates/docs to the channel tag, and land the generalized compliance test in CI.
  • Phase 3 — cross-repo rollout: lift the all-reusables standard into petry-projects/.github and repin downstream consumers (admin / cross-repo).

Grounded in docs/initiatives/agentic-release-strategy.md (epic #495) and docs/release/versioning.md. This epic is created inert — activation is a human decision.


Planned from idea discussion #666 by the BMAD Scrum Master initiative-planner. Inert until a maintainer adds initiative:auto.

Activity

  1. don-petry commented on Jul 14, 2026

    @don-petry
    Collaborator

    Reconciled + activated (2026-07-13)

    Audited against work that shipped out-of-band via the #1159 ci-failure-analyst versioning effort:

    Genuine remaining work (activated for dev-lead): #686 (generalize cut-release.sh + the release standard to non-agent reusables), #687 (CI compliance test rejecting SHA/# main pins on first-party reusables — note: the missed lock.yml pin is proof this guard doesn't exist yet), #689 (the one lock.yml repin), #690 (cross-repo rollout into petry-projects/.github).

    Adding initiative:auto. — Claude Code

  2. added
    initiative:autoDriver may auto-release this epic's ready sub-issues to dev-lead
    on Jul 14, 2026
  3. don-petry commented on Aug 3, 2026

    @don-petry
    Collaborator

    Note — this epic predates #1184 (major-scoped channels)

    The body above describes the standard as @dev-lead/stable / @pr-review/stable. Since #1184, the canonical form is major-scoped: <name>/v<MAJOR>-<tier>. Please do not read the bare <name>/<tier> examples here as current guidance — they are the pre-#1184 spelling.

    Completing that migration is now scoped into #687 (ACs 7–13), which is the right home because #687 is the check that defines what a sanctioned pin is — and as originally written it would have enshrined the legacy form.

    Current state in this repo: 7 legacy pins vs 10 major-scoped, with dependency-audit, auto-rebase and ci-failure-analyst each pinned both ways by different callers. pr-review is the blocking case — 4 callers pin it and it has no major-scoped tags cut yet.

  4. don-petry commented on Sep 1, 2026

    @don-petry
    Collaborator

    All six sub-issues are now closed (#685, #686, #687, #688, #689, #690). #690 closed 2026-09-01 as superseded — see its closing comment: the standard is live in petry-projects/.github/standards/ci-standards.md, the compliance gate enforces it org-wide, and pinned-version-report shows 90/92 fleet pins compliant with both exceptions being the deliberate SC2 stable pin (now guarded by #1624). Epic complete.

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 issueinitiative:autoDriver may auto-release this epic's ready sub-issues to dev-lead

    Type

    No type

    Projects

    No projects

      Milestone

      No milestone

      Relationships

      None yet

      Development

      No branches or pull requests

      Issue actions