Repository navigation
Prepare Akiki 0.2.2 - #9
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.
Prepare Akiki 0.2.2 from the reviewed
mainbranch. Update the package version, runtime version, version assertion, release manifest, and model card. The model identity, weight checksums, and engine and training source pins are preserved.Release notes:
nativedirectory. Uselibrary_pathor the engine-specific environment variables for a separately built library.akiki-trainingcompanion. The public wrapper supports authorized local installations. Thetrainingextra supplies runtime dependencies only.Validation: 456 tests passed offline with both existing local native engines required. Eleven checks were skipped because ONNX Runtime or an explicit real-model path was unavailable. Ruff and formatting checks passed. The packaging tests built and verified distributions with the 0.2.2 metadata. The version is not yet present on PyPI.
After merge, wait for the full builds and private training checks on
main. Publish a GitHub release taggedv0.2.2at that tested commit to start Trusted Publishing.