Repository navigation
chore: release v0.0.2 - #17
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.
Summary
Prepare the patch release containing the changes merged since v0.0.1, including Linux CLI support.
After merging, tag the bump commit as
v0.0.2to trigger release packaging and the tested Homebrew formula update.Evidence
0.0.1.After:
cargo update --workspacesynchronized both files;cargo run --locked -- --versionprintsgbat 0.0.2.cargo fmt --check,cargo clippy --all-targets --locked -- -D warnings, andcargo test --lockedpassed locally on Linux (27 tests).Merge Danger
Door: two-way
The version commit is reversible before the release tag is pushed.
Blast Radius: packaging
Only the package version changes. Publishing the tag triggers the existing macOS archive and Homebrew release workflow.