docs: document the new-crate token bootstrap for trusted publishing#266
Conversation
A brand-new crate cannot be created by OIDC trusted publishing — crates.io returns 403 "Trusted Publishing tokens do not support creating new crates", so the first version needs a one-time manual cargo publish with a token. This bit the v0.40.0 release when ts_netmon was added. Add an explicit new-crate checklist to RELEASING.md so the next new crate does the bootstrap up front. Signed-off-by: GeiserX <9169332+GeiserX@users.noreply.github.com>
|
Warning Review limit reached
More reviews will be available in 55 minutes and 34 seconds. Learn how PR review limits work. Your organization has used up its prepaid credits, and credit purchases are no longer available. Enable the review add-on in the billing tab to keep reviews running — you're only billed for reviews past your plan's rate limits ($0.25/file). ⌛ How to resolve this issue?After more reviews become available, a review can be triggered using the We recommend that you space out your commits to avoid hitting the rate limit. 🚦 How do rate limits work?CodeRabbit enforces hourly rate limits for each developer per organization. Our paid plans include higher PR review limits than trial, open-source, and free plans. In all cases, reviews become available again over time. During sustained high-volume PR review activity, CodeRabbit may temporarily slow when the next review becomes available. Please see our Fair Usage Limits Policy for further information. ℹ️ Review info⚙️ Run configurationConfiguration used: Path: .coderabbit.yaml Review profile: CHILL Plan: Pro Run ID: 📒 Files selected for processing (1)
✨ Finishing Touches🧪 Generate unit tests (beta)
Thanks for using CodeRabbit! It's free for OSS, and your support helps us grow. If you like it, consider giving us a shout-out. Comment |
1 participant
Why
The v0.40.0 publish failed at the newly-added
ts_netmoncrate with:crates.io's OIDC trusted publishing cannot create a brand-new crate — the first version of any new crate needs a one-time manual
cargo publishwith a real token, plus a trusted-publisher registration. The existing RELEASING.md said "all crates already exist, so no token bootstrap is needed", which is true until a new crate is added.What
Adds an "Adding a NEW
geiserx_*crate" subsection to RELEASING.md with the full checklist: workspace wiring, thescripts/publish-crates.shCRATESentry (leaf-first, before dependents) + count bump, and the one-time token bootstrap (cargo publish -p <crate>+setup-trusted-publishing.sh), plus how to resume a release that already published the rest of the workspace (gh workflow run Release --ref main,SKIP_PUBLISHED=1).Docs only.
Signed-off-by: Sergio sergio@geiser.cloud
Created using Claude Code (Opus 4.8)