ci: add automated crates.io publishing to release workflow#706
Merged
Conversation
Add publish-crates job with OIDC trusted publishing via rust-lang/crates-io-auth-action and katyo/publish-crates. Runs after build-binaries, before create-release. Includes tag-to-manifest version verification and 15s inter-crate delay for workspace dependency resolution on the registry.
bug-ops
force-pushed
the
ci/crates-io-publish
branch
from
22df91d to
5936816
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
1 participant
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
publish-cratesjob to release workflow triggered onv*tagsrust-lang/crates-io-auth-action(no manual API token)katyo/publish-crateshandles workspace topological ordering with 15s inter-crate delaybuild-binaries->publish-crates->create-releaseSetup required
Configure trusted publishers on crates.io for each workspace crate:
bug-ops/zephrelease.ymlreleaseCreate a
releaseenvironment in GitHub repo settings (Settings > Environments).Test plan