Skip to content

Release 0.3.0 - #100

Merged
JacobStephens2 merged 1 commit into
mainfrom
release-0.3.0
Sep 27, 2026
Merged

JacobStephens2 merged 1 commit into
mainfrom
release-0.3.0

Conversation

@JacobStephens2

Copy link
Copy Markdown
Owner

Summary

Bumps thirdshift to 0.3.0 so the Merge run ships.

 Cargo.toml
-version = "0.2.0"
+version = "0.3.0"

0.3.0 ships the changes merged since v0.2.0. The headline is the Merge run (thirdshift merge <Issue URL>): #89 (define Merge run, Self-merge and Foreign commit), #96 (tracer bullet), #97 (a failed Self-merge goes back round the Repair loop; policy refusals leave the PR ready), #98 (post-merge steps: delete the Issue branch, close the issue), #99 (review Foreign commits with a Repair). Also #95 (Repair and base-move budgets raised to 5) and the site work in #72–#87.

Evidence

  • Before: installed 0.2.0 rejects the command: thirdshift merge <url> prints thirdshift: not a GitHub issue URL: merge, and thirdshift help has no merge line.
    After: on this branch, thirdshift version prints thirdshift 0.3.0 and thirdshift help lists thirdshift merge <Issue URL>. CI on main at 8b5f908 is green (run 36324291060).

Merge Danger

Door: two-way

The merge only changes a version number. Pushing the v0.3.0 tag afterward is one-way: it publishes to crates.io, and a crates.io version can't be re-published.

Blast Radius: release metadata

🤖 Generated with Claude Code

Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
@JacobStephens2
JacobStephens2 merged commit ee5096b into main Sep 27, 2026
13 checks passed
@JacobStephens2
JacobStephens2 deleted the release-0.3.0 branch September 27, 2026 14:38
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant