chore: remove the one-time crates.io bootstrap workflow - #25
Merged
Conversation
All six crates are published at 0.1.0 and each has a crates.io trusted publisher, so release.yml handles every release from here over OIDC. CARGO_REGISTRY_TOKEN is removed from the release environment; the token-based bootstrap has no purpose left. Co-Authored-By: Claude Opus 4.8 (1M context) <noreply@anthropic.com>
P4suta
enabled auto-merge (squash)
July 17, 2026 23:33
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.
All six crates are published at 0.1.0 with crates.io trusted publishers configured, and CARGO_REGISTRY_TOKEN is removed from the release environment. The token-based bootstrap workflow is no longer needed; release.yml publishes over OIDC from here.