Skip to content

feat(release): automate approved milestone publication - #470

Merged
ss-o merged 1 commit into
nextfrom
feature-468
Aug 31, 2026
Merged

feat(release): automate approved milestone publication#470
ss-o merged 1 commit into
nextfrom
feature-468

Conversation

@ss-o

@ss-o ss-o commented Aug 31, 2026

Copy link
Copy Markdown
Member

Description

Automate the approved Zi milestone release flow without automating tag creation:

  • call the organization semantic-version and release-notes preparation workflow after a promotion reaches main
  • require a maintainer-pushed signed annotated vX.Y.Z tag as publication authorization
  • reject malformed, lightweight, unverified, stale/off-main, target-mismatched, or insufficiently tested tags
  • publish generated GitHub release notes idempotently after verification

The reusable caller is pinned to the exact merged policy commit. No version file or release dependency is added. This becomes active when next is next promoted to main.

Related issues

Part of #468
Policy: z-shell/.github#583 and z-shell/.github#584

Type of change

  • feat - new feature (non-breaking)
  • ci - CI/workflow change

Validation

  • actionlint on both workflows
  • Ruby YAML parse with aliases enabled
  • zsh -n on the verifier and focused test
  • zsh -f tests/release-tag-verification.zsh
  • safe Trunk check on all four files
  • live read-only verification of signed tag v2.0.0 against its exact main commit and successful workflows
  • git diff --check

Checklist

  • Ordinary work targets next; only same-repository hotfixes target main
  • Commit messages follow Conventional Commits format
  • No prohibited Co-authored-by trailer is present
  • Contribution guidelines reviewed
  • Relevant tests pass
  • Release policy documentation was updated in feat(release): allow approval-gated Zi automation .github#584

Migration plan

Not required. This does not change Zi's public shell contract.

@ss-o
ss-o merged commit d01d99f into next Aug 31, 2026
8 checks passed
@ss-o
ss-o deleted the feature-468 branch August 31, 2026 15:46
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant