chore(release): prepare v0.2.0 - #222
Merged
Merged
Conversation
- Bump steplock to 0.2.0: steplock init no longer writes a default checklist (breaking, so a minor bump before 1.0). - CHANGELOG: cut the Unreleased entries as 0.2.0 (2026-09-29). 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
steplockto 0.2.0.steplock initno longer writes a default checklist (feat(init)!: stop writing a default example-gate checklist #221). That is a breaking change, so this is a minor bump before 1.0.After merge, tag
v0.2.0on main. The Release workflow builds the binaries, creates the GitHub release, and publishes to crates.io.Test plan
cargo checkupdatesCargo.lockto 0.2.0cargo publish --locked --dry-runfor 0.2.0 succeeded on the PR headcargo test --locked(178 tests), clippy-D warnings,cargo fmt --check, and the tag version check withv0.2.0x86_64-apple-darwin(cargo build) andaarch64-unknown-linux-gnu(cargo zigbuild)release.ymlis unchanged since v0.1.0, and the v0.1.0 run succeeded end to end (crates.io has only 0.1.0)Kev review
Local Kev (
kev-latest). Each round added only verified facts:x86_64-apple-darwinbuild (wrongly called the only target PR CI skips)aarch64-unknown-linux-gnualso unbuiltaarch64-unknown-linux-gnubuilt withcargo zigbuild, so all five release targets are builtx86_64-apple-darwinbinary:--version, emptyinit,git pushapprovedVersion choice: 0.2.0 0.77, 0.1.1 0.19, 1.0.0 0.03.
Concerns probed in round 2 (each asked as "X is a reason to wait"): Release workflow not yet run for this tag 0.37, rewording the changelog entry 0.34, no human review 0.34, draft 0.30, breaking change 0.29. The top concern can only be checked after the tag is pushed.
The gate is reached at round 8 (0.804, gate 0.8), with the PR ready for review. The round 3 open question is answered: the owner asked to reach the gate instead of being asked.
🤖 Generated with Claude Code