Skip to content

ci(release): start stable releases from a pushed tag - #1115

Draft
e54-bot wants to merge 3 commits into
mainfrom
ci/agent-owned-release-tag
Draft

e54-bot wants to merge 3 commits into
mainfrom
ci/agent-owned-release-tag

Conversation

@e54-bot

@e54-bot e54-bot commented Nov 18, 2026 •

Copy link
Copy Markdown
Collaborator

Summary

Stable releases start from a pushed vX.Y.Z tag, the same for a maintainer and for an agent: git tag vX.Y.Z && git push origin vX.Y.Z. Whoever completes a requirement decides whether to release. There is no Release PR, release-please, CHANGELOG.md, version commit, or scheduled release job.

  • The checked-in version is the placeholder 0.1.0. Each job that builds runs scripts/stamp-version.py with the tag version. The stamped files are not committed.
  • The inline CI polling script is replaced by a pinned lewagon/wait-on-check-action on CI result.
  • The GitHub Release is created once with the complete artifact set. A draft left by a failed run is deleted by hand (documented).
  • docs/release.md and AGENTS.md describe the procedure and the bump rules.

Verification

  • actionlint passes. scripts/test-stamp-version.py passes and runs in CI.
  • Stamping 1.2.3 and building with --locked gives wright 1.2.3. The update, diagnostics_schema, and cli tests pass with the placeholder.
  • Homebrew and install.sh distribution tests pass locally on a rebuilt binary.

Not verified

No real release has run on this topology. The first tag after merge is the production validation. The wait-on-check action has not run in this workflow yet.

Remove release-please, the Release PR, and the committed version bump. The release agent decides when to release and pushes the vX.Y.Z tag; release.yml stamps the tag version into the checkout before it builds, and requires the tagged commit to be on the default branch.

The checked-in version is the placeholder 0.1.0.
Replace a draft left by an interrupted run instead of refusing; use python on the Windows leg; write LF newlines when stamping; drop release-please wording from lint docs and AGENTS.md; state the full bump rules.
Replace the inline CI polling script with a pinned wait-on-check action, drop the default-branch guard and the draft-retry logic, and describe the release as a pushed tag, the same for a maintainer and an agent.
@e54-bot e54-bot changed the title ci(release): start stable releases from an agent-pushed tag ci(release): start stable releases from a pushed tag Nov 18, 2026

This branch has not been deployed

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

Labels

None yet

Projects

Development

Successfully merging this pull request may close these issues.

2 participants