Repository navigation
chore: prepare v0.1.0 for release - #4
Merged
Merged
Conversation
Add the user-selected MIT license, version and package metadata, release notes, and a release-readiness checklist. Verify installed wheels in CI and link the public wiki. Keep runtime behavior unchanged; tagging and publication remain separate approval steps.
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
0.1.0and update the lockfile without changing dependency pins.Scope and safety
Verification
uv pip check.Next gate
Review and merge this preparation PR, verify post-merge CI, then explicitly approve the signed release tag and publication destination. Rebuild artifacts from the final approved release commit.