Skip to content

ci(release): publish crates from a pushed tag - #638

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

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

Conversation

@e54-bot

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

Copy link
Copy Markdown
Contributor

Summary

crates.io publication moves from release-plz into the tag workflow. A release is a committed version and a pushed vX.Y.Z tag, the same for a maintainer and for an agent. There is no Release PR and no scheduled release job.

  • release-gate checks that the tag equals the workspace version and waits for the checks on the tagged commit with a pinned lewagon/wait-on-check-action.
  • publish-crates runs a cargo publish --workspace --locked --dry-run, then publishes in the protected release environment, before the binary build and the GitHub Release.
  • The version stays committed, unlike wright: cargo publishes the committed Cargo.toml, and Public API compatibility compares it with the latest published release.
  • release-plz.yml, release-plz.toml, and the CODEOWNERS entry are removed. docs/release.md describes the procedure.

Verification

  • actionlint passes. cargo publish --workspace --locked --dry-run passes for both crates.

Not verified

  • No real release has run on this topology. The wait-on-check action has not run in this workflow yet; its running-workflow-name exclusion of the gate job is untested.
  • Whether a rerun skips a crate version already on crates.io is undocumented by cargo and untested.

Remove release-plz and the Release PR. The release agent commits the version and pushes the vX.Y.Z tag. The tag workflow now checks that the tag matches the workspace version, that the commit is on the default branch, and that the required checks passed, then publishes both crates before it builds the binaries and creates the GitHub Release.
Treat a skipped required check as passing in the release gate, report check-runs API errors, run a cargo publish dry run before publication, and document environment approvals, tag credentials, and approved breaks.
Replace the inline check-run polling script with a pinned wait-on-check action and drop the default-branch guard. The release is a committed version and a pushed tag, the same for a maintainer and an agent.
@e54-bot e54-bot changed the title ci(release): publish crates from an agent-pushed tag ci(release): publish crates 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

None yet

Development

Successfully merging this pull request may close these issues.

2 participants