ci(release): use crates.io trusted publishing (no secret) - #18
Merged
Conversation
Replace the long-lived CARGO_REGISTRY_TOKEN secret with rust-lang/crates-io-auth-action + id-token: write. Publishing no longer needs a GitHub Actions secret once a Trusted Publisher is configured on crates.io for beyondoss/slipstream / release.yml. Co-authored-by: Jared Lunde <jared.lunde@gmail.com>
jaredLunde
marked this pull request as ready for review
August 16, 2026 00:58
|
Bugbot is not enabled for your account, so this pull request was not reviewed. Enable Bugbot in the Cursor dashboard to get automatic reviews on future PRs. |
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
2 participants
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.
You’re right — with Trusted Publishing you don’t need a long-lived
CARGO_REGISTRY_TOKENsecret. The failed0.7.3publish used the old secret-based path and got403 authentication failed.Change
Switch Release’s publish job to OIDC:
permissions: id-token: write(+contents: read)rust-lang/crates-io-auth-action@v1→ short-lived tokencargo publishuses that token (notsecrets.CARGO_REGISTRY_TOKEN)One-time crates.io setup (you)
Before this works, add a Trusted Publisher on the crate (owner UI):
beyondossslipstreamrelease.ymlhttps://crates.io/crates/beyond-slipstream/settings/new-trusted-publisher
After merge
mainis still at0.7.3while crates.io is0.7.2, so the Release workflow on this merge should publish0.7.3automatically once the trusted publisher is configured.