Repository navigation
chore(crates): use OIDC to publish crates - #13543
Conversation
There was a problem hiding this comment.
Pull request overview
Updates the crates release reusable workflow to publish to crates.io using GitHub OIDC (tokenless auth) instead of a long-lived CARGO_REGISTRY_TOKEN secret, aligning crate publishing with modern provenance-oriented release practices.
Changes:
- Adds
rust-lang/crates-io-auth-actionto mint a crates.io token via OIDC. - Switches
crate-publishto use the OIDC-minted token (steps.auth.outputs.token) instead ofsecrets.CARGO_REGISTRY_TOKEN.
💡 Add Copilot custom instructions for smarter, more guided reviews. Learn how to get started.
Merging this PR will degrade performance by 1.79%
Performance Changes
Comparing Footnotes
|
Rsdoctor Bundle Diff AnalysisFound 5 projects in monorepo, 0 projects with changes. 📊 Quick Summary
Generated by Rsdoctor GitHub Action |
📦 Binary Size-limit
🎉 Size decreased by 11.09KB from 49.06MB to 49.05MB (⬇️0.02%) |
Deploying rspack with
|
| Latest commit: |
8c6c3ef
|
| Status: | ✅ Deploy successful! |
| Preview URL: | https://b26c2c49.rspack-v2.pages.dev |
| Branch Preview URL: | https://chore-crate-oicd-pub.rspack-v2.pages.dev |
…k into chore/crate_oicd_pub
chore(backport): use OIDC to publish crates (#13543)
Summary
use OIDC publish for safety reason
Related links
Checklist