Add release workflow with crates.io Trusted Publishing - #60
Closed
dogenkigen wants to merge 1 commit into
Closed
dogenkigen wants to merge 1 commit into
dogenkigen wants to merge 1 commit into
Conversation
Publishes the crate when a v* tag is pushed, after verifying the tag matches the Cargo.toml version and running the full CI suite. Auth uses OIDC via rust-lang/crates-io-auth-action, so no API token is stored. Also bumps actions/checkout to v4 in the existing CI workflow. Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
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.
Summary
.github/workflows/release.yml, which publishesdoc-assertto crates.io when av*tag is pushed.Cargo.toml.rust-lang/crates-io-auth-action), so no long-lived API token is stored in the repo.releaseGitHub environment so it can be gated with protection rules.actions/checkoutfrom v3 to v4 in the existing CI workflow.Required one-time setup (before the first tagged release)
doc-assert→ Settings → Trusted Publishing → add GitHub publisher: ownerDocAssert, repodoc-assert, workflowrelease.yml, environmentrelease.release; restrict deployment to tags matchingv*(optionally require reviewer approval).Releasing
Bump
versioninCargo.toml, merge tomain, then:🤖 Generated with Claude Code