Skip to content

[Phase 1] Define versioning scheme + cut first immutable release tags (pr-review, dev-lead, scripts) #496

Closed

Description

@don-petry

Parent: #495 · Phase 1 · Work type: Spike · Targets SC1.

Define a per-agent semantic versioning scheme (e.g. pr-review/vX.Y.Z, dev-lead/vX.Y.Z) covering the reusable workflows and the scripts they depend on (engine.sh, review-one-pr.sh, etc.). Cut the first immutable release tag from current known-good main, then create the moving stable channel tag pointing at it.

Why two kinds of tag: immutable vX.Y.Z are the audit/rollback targets; the floating stable is what callers pin to (moved centrally on promotion — see §5.1). GitHub forbids expressions in uses: refs, so a moving tag — not a Variable — is how we get "one knob, no caller edits."

Done when: versioning convention documented; first vX.Y.Z + stable tags exist; tag↔commit mapping recorded.

Ref: docs/initiatives/agentic-release-strategy.md §5.1, §7 Phase 1.

Activity

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