Repository navigation
Prepare v0.2.0 release with companion packages - #20
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
2 participants
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.
Bump all software packages to 0.2.0 and derive companion archive metadata from Cargo.toml. Run companion validation and packaging in the release workflow alongside existing statistical model/CLI checks. Include release notes that explicitly retain experimental, non-qualified neural status and exclude neural weights. Local root and companion formatting, Clippy with warnings denied, Rust tests and all 15 Python tests passed. Independent review cleared exact head 4e32414; all 13 CI checks passed. Closes #19.