Skip to content

ci: fix release-plz with crates.io trusted publishing#24

Merged
jdidion merged 1 commit into
mainfrom
ci/release-plz-trusted-publishing
Jul 5, 2026
Merged

ci: fix release-plz with crates.io trusted publishing#24
jdidion merged 1 commit into
mainfrom
ci/release-plz-trusted-publishing

Conversation

@jdidion

@jdidion jdidion commented Jul 5, 2026

Copy link
Copy Markdown
Owner

The 'Manage Release PRs and Publish Crates' workflow failed at checkout ('token not supplied') because no token secrets were configured. This switches crates.io auth to trusted publishing (OIDC): adds id-token: write, drops the CARGO_REGISTRY_TOKEN env var, and moves to the renamed release-plz/action.

Requires two one-time setup steps (documented separately): a RELEASE_PLZ_TOKEN GitHub PAT secret for the GitHub-side release PRs/tags, and a crates.io trusted-publisher registration for the beekeeper crate.

Co-Authored-By: Claude Opus 4.8 (1M context) noreply@anthropic.com

Switch the release workflow to crates.io trusted publishing (OIDC):
add id-token: write and drop the CARGO_REGISTRY_TOKEN env var, so no
long-lived crates.io token is stored. Also move to the renamed
release-plz/action. RELEASE_PLZ_TOKEN (GitHub PAT) is still required
for the GitHub-side release PRs/tags. Fixes the workflow, which failed
at checkout because no token secret was configured.

Co-Authored-By: Claude Opus 4.8 (1M context) <noreply@anthropic.com>
@jdidion jdidion merged commit 5af05ad into main Jul 5, 2026
28 checks passed
@jdidion jdidion deleted the ci/release-plz-trusted-publishing branch July 5, 2026 13:01
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant