chore: add trusted-publisher crates.io release job#3
Merged
Conversation
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.
What changed
Adds a separate crates.io publish job to the tag-driven release workflow while keeping the existing WASM GitHub release flow intact.
Why
We want crates.io publishing to follow the
unfmttrusted-publisher pattern instead of using a long-lived registry token.Impact
Tag releases will still verify, build, and upload WASM assets, then run a dedicated crates.io publish job authenticated through GitHub OIDC and
rust-lang/crates-io-auth-action.Validation
cargo publish --dry-run --locked --allow-dirtysuccessfully