Repository navigation
ci(release): tag, release and publish from CI - #12
Merged
Merged
Conversation
Merging a "chore(release): prepare vX.Y.Z" commit (or dispatching Release from main) now creates the tag, the GitHub Release from CHANGELOG, and dispatches an idempotent crates.io publish on the tag. Mirrors bashkit. Co-Authored-By: Claude Opus 5.5 (1M context) <noreply@anthropic.com> Claude-Session: https://claude.ai/code/session_01Y2vd61x8kbPtmDxze9Q4Gi
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.
Before: a release needed someone to push a
v*tag from a local clone, and crates.io publishing was a separate manual run. A re-run failed on crates that were already published. markkit 0.1.0 is on crates.io but has no tag and no GitHub Release.After: merging a
chore(release): prepare vX.Y.Zcommit to main, or running Release by hand from main, does the whole release in CI:vX.Y.Ztag.How: this follows bashkit's release.yml and publish.yml.
Cargo.toml, that the commit is on main, and that any existing tag points at the same commit.Cargo.toml. For each ofmarkkitandmarkkit-cli, it does a dry run and then a--no-verifyupload.specs/release-process.mdand the CHANGELOG are updated.After merge: I'll run Release by hand to create
v0.1.0and its GitHub Release. Publish will then skip both crates, because 0.1.0 is already on crates.io.🤖 Generated with Claude Code
https://claude.ai/code/session_01Y2vd61x8kbPtmDxze9Q4Gi
Generated by Claude Code