Release v0.5.0 - #4
Merged
Merged
Conversation
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
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.
Release v0.5.0
This PR prepares the v0.5.0 release.
What's included
commitor revert— undo commits produced bycommitor commit(hard reset for unpushed,git revertfor pushed).commitor scan --diff-range <RANGE>— analyze a fixed git range instead of the working tree, plus--markdownfor PR comments.commitor scan --context "<title/description>"— forward a PR's stated intent to the model.commitor commit— offers to push the new branch, auto-detecting the upstream.commitor commitruns at~/.commitor/history/<repo-id>.jsonl../action) that runscommitor scan --diff-rangeon PRs and posts an updatable Markdown comment.commitor commitgains interactive branch selection, base-branch tracking, and an offline mode.--diff-rangescans now always consult the backend (the local heuristic is advisory only at PR scale), so unrelated changes in a large diff are no longer missed.publish.yml) is now idempotent — re-running a release no longer fails on an already-published crates.io / npm version.Checklist
After merging, create the tag on the merge commit:
Note: the previous
v0.5.0tag was a phantom (pointed at code still versioned 0.4.0). Delete it before re-tagging this release: