Repository navigation
ci(release): tag-driven release with attested binaries and crates.io trusted publishing (LAB-5117) - #4
Merged
Conversation
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.
Adds
.github/workflows/release.ymland an install section in the README.A version tag (
v0.1.0,v0.2.0-rc.1) runs four jobs, all on GitHub-hosted runners:vplus the crate version, the tagged commit must be onmain, andcargo package --lockedmust build.x86_64andaarch64Linux and a binary for Apple silicon. Each job runs the test suite on its own target before it builds. These jobs hold onlycontents: read, so dependency build scripts never see a signing or publishing token.ckbinary inside it withactions/attest(the actionattest-build-provenancenow wraps), then creates the GitHub Release. A tag with a-makes a pre-release.releaseenvironment) and runscargo publish. It runs last because a crates.io version can never be republished.No installer script ships. The README documents
cargo install --locked cachekit-cliand the pinned verify command, and says why--owner cachekit-ioalone is not enough.Before the first tag, the crate must exist on crates.io with this workflow registered as its trusted publisher, and the repository must be public, because artifact attestations need a public repository on this plan.
Closes LAB-5117