Repository navigation
ci: install recoverable trusted release workflow - #24
Merged
Merged
Conversation
Publish tagged commits from `main` to crates.io with Trusted Publishing, then create GitHub Releases from validated changelog entries. Test the tagged source with locked dependencies before publishing. Make partial releases safe to retry by verifying existing crate contents and GitHub Release metadata before skipping them. Reject conflicts and yanked versions, and document the environment and tag protection setup.
QuadnucYard
force-pushed
the
codex/release-recovery
branch
from
October 11, 2026 09:18
1415b8d to
5d31bf1
Compare
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.
The repository currently has no automatic release workflow on main. Install the tag-triggered workflow and the prepared 0.4.0 metadata so a protected maintainer tag validates and tests the package, publishes through crates.io Trusted Publishing, and creates a GitHub Release from the changelog.
Make partial-release retries safe: verify the existing crate's registry checksum, clean commit, manifests, and source before skipping publication; verify an existing GitHub Release's tag, title, notes, and prerelease status before accepting it. Conflicting or yanked artifacts stop the run. The release guide documents the exact publisher settings and recovery behavior.
Validation: 23 release-script tests pass, Cargo package build verification passes with
cargo publish --dry-run --locked --all-features --registry crates-io, and the live registry lookup confirms 0.4.0 still needs publishing. No crate or release tag has been published.