Repository navigation
Conversation
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.
This branch has not been deployed
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Summary
crates.io publication moves from release-plz into the tag workflow. A release is a committed version and a pushed
vX.Y.Ztag, the same for a maintainer and for an agent. There is no Release PR and no scheduled release job.release-gatechecks that the tag equals the workspace version and waits for the checks on the tagged commit with a pinnedlewagon/wait-on-check-action.publish-cratesruns acargo publish --workspace --locked --dry-run, then publishes in the protectedreleaseenvironment, before the binary build and the GitHub Release.wright: cargo publishes the committedCargo.toml, andPublic API compatibilitycompares it with the latest published release.release-plz.yml,release-plz.toml, and the CODEOWNERS entry are removed.docs/release.mddescribes the procedure.Verification
actionlintpasses.cargo publish --workspace --locked --dry-runpasses for both crates.Not verified
running-workflow-nameexclusion of the gate job is untested.