ci: add tag-driven release workflow#1
Merged
Conversation
infinityplusone
force-pushed
the
ci/release-workflow
branch
from
0430f50 to
f74a844
Compare
Fires on push of a vX.Y.Z tag: - runs the test suite - publishes tango-webhooks then tango to crates.io - creates a GitHub Release with auto-generated notes Requires the CRATES_IO_TOKEN (aka CARGO_REGISTRY_TOKEN) repo secret with publish scope on crates.io. Co-Authored-By: Claude Opus 4.7 <noreply@anthropic.com>
infinityplusone
force-pushed
the
ci/release-workflow
branch
from
f74a844 to
3191f9f
Compare
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— fires on push ofvX.Y.Ztags.makegov-tango-webhooksthenmakegov-tangoto crates.io, and creates a GitHub Release with auto-generated notes.Setup checklist (do before merging)
makegov-tango+makegov-tango-webhooks.CARGO_REGISTRY_TOKENonmakegov/tango-rust.CRATES_IO_TOKEN— workflow here usesCARGO_REGISTRY_TOKENbecause cargo reads that env var directly.)Testing
v0.0.0-testtag (don't publish; delete on failure) and confirm the workflow triggers + reaches the publish step.v0.1.0.Notes
makegov-tango-webhooksfirst (leaf), thenmakegov-tango(depends on transport + serde, not on webhooks).makegov-*on crates.io but user code still imports asuse tango::.../use tango_webhooks::...via a[lib] nameshim — same pattern as theaws-sdk-*family.$MAKEGOV_BOT_SIGNATURE