ci: mint crates.io token via OIDC auth action before publish#1
Merged
Conversation
cargo publish does not perform the Trusted Publishing OIDC exchange itself; add rust-lang/crates-io-auth-action (SHA-pinned v1.0.4) to mint a short-lived CARGO_REGISTRY_TOKEN consumed by cargo publish.
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
cargo publishdoes not perform the crates.io Trusted Publishing OIDC exchange itself.rust-lang/crates-io-auth-action(SHA-pinnedv1.0.4) ahead of publish to mint a short-livedCARGO_REGISTRY_TOKEN, consumed via env bycargo publish.Why a PR
Direct pushes to
mainare now blocked by the ruleset (3 requiredTestchecks). This change goes through CI like everything else.Test plan
Test (ubuntu-latest),Test (macos-latest),Test (windows-latest)publishjob authenticates via OIDC andcargo publishsucceeds