Skip to content

ci: use crates.io trusted publishing - #11

Merged
fasterthanlime merged 1 commit into
mainfrom
ci/trusted-publishing
Aug 19, 2026
Merged

fasterthanlime merged 1 commit into
mainfrom
ci/trusted-publishing

Conversation

@fasterthanlime

Copy link
Copy Markdown
Contributor

Post-#10 release packaged copypatch 0.2.0-rc.5 then died: empty CARGO_REGISTRY_TOKEN.

Official TP path (release-plz quickstart):

  • drop CARGO_REGISTRY_TOKEN entirely (even an empty secret blocks OIDC)
  • id-token: write on the release job
  • do not use rust-lang/crates-io-auth-action; release-plz does the exchange

release-pr does not need a crates.io token.

You still have to click this on crates.io for copypatch and weavy:

  • repository: bearcove/weavy
  • workflow: release-plz.yml
  • environment: none

Without those rows this PR merges green and the next release still cannot publish.

Empty CARGO_REGISTRY_TOKEN failed the post-#10 publish. Official
release-plz TP: drop the secret, set id-token: write on the release
job. release-plz exchanges the OIDC token itself.

crates.io still needs trusted-publisher rows for copypatch and weavy
(repo bearcove/weavy, workflow release-plz.yml, environment none).
@fasterthanlime
fasterthanlime added this pull request to the merge queue Aug 19, 2026
Merged via the queue into main with commit a4351cc Aug 19, 2026
6 checks passed
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.

2 participants