Publish the crate with trusted publishing instead of a stored token - #2530
Merged
Conversation
The crate now has a crates.io publisher policy naming this workflow, so the job can exchange its OIDC token for a short-lived key and the stored CARGO_REGISTRY_TOKEN can be deleted. Matches how release-nuget authenticates. The policy names release.yml specifically: renaming or moving this file breaks publishing until the policy is updated to match. Co-Authored-By: Claude Fable 5 <noreply@anthropic.com>
Contributor
DoltLite performance vs PR base
blobpk details
compositepk details
int details
textpk details
vc details
All relative performance gates passed. |
Contributor
DoltLite source coverage
Merged 200 pooled raw profiles from the distributed Linux correctness jobs. Per-file coverage (98 files)
|
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 crates.io publisher policy is now configured on the crate (GitHub,
dolthub/doltlite, workflowrelease.yml, owner ID 42156961 — matching the verified org ID), sorelease-cratesno longer needs a stored credential.Changes: adds
permissions: id-token: write, drops the token pre-flight check, and insertsrust-lang/crates-io-auth-action@v1to exchange the job's OIDC token for a short-lived publishing key. Same authentication shape asrelease-nuget.Sequencing
release-cratesis green and the version lands on crates.io.CARGO_REGISTRY_TOKENsecret. Worth doing promptly: that token has change-owners scope, not just publish.Note
The policy names
release.ymlexplicitly, so renaming or relocating this workflow file breaks publishing until the policy is updated. That's recorded in the job comment for whoever touches it next.🤖 Generated with Claude Code