ci: publish to crates.io by OIDC instead of a personal API token - #103
Merged
Conversation
The PyPI half of the release already authenticates as this repository; the crates.io half authenticated as whoever created `CARGO_REGISTRY_TOKEN`. That made one person a single point of failure independent of who owns the crate — the token outlives their involvement, or dies with their account, and no amount of adding owners changes it. `crates-io-auth-action` exchanges the run's OIDC identity for a token scoped to this crate and revokes it in its post step, so the credential exists only for the length of the job and there is no secret to rotate. The pairing now matches PyPI's on both sides of the release. Merging this before registering the Trusted Publisher on crates.io breaks the next release at the auth step, so register it first; the setup needs a crate that already has a published version, which is why this follows 0.2.0 rather than shipping with it. Co-Authored-By: Claude Opus 5 (1M context) <noreply@anthropic.com>
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.
The PyPI half of the release already authenticates as this repository; the crates.io half authenticated as whoever created
CARGO_REGISTRY_TOKEN. That made one person a single point of failure independent of who owns the crate — the token outlives their involvement, or dies with their account, and no amount of adding owners changes it.crates-io-auth-actionexchanges the run's OIDC identity for a token scoped to this crate and revokes it in its post step, so the credential exists only for the length of the job and there is no secret to rotate. The pairing now matches PyPI's on both sides of the release.Merging this before registering the Trusted Publisher on crates.io breaks the next release at the auth step, so register it first; the setup needs a crate that already has a published version, which is why this follows 0.2.0 rather than shipping with it.