Repository navigation
docs(maintenance): close the 0.3.0 release milestone - #36
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.
Close the 0.3.0 maintenance milestone in the plan and record the published tag, successful trusted-publication workflow, all 20 installation combinations, exact PyPI artifact hashes and fresh CPU-analysis installation verification.
Mark completed release/import/checkpoint/Torch work accurately instead of leaving it as a future release gate. Separate the remaining Python 3.13, GPU processing evaluation, dependency/security and model/WSI/GPU validation milestones. Keep broad typing/docs work deferred and retain the rule against unrelated baseline collection or CI expansion. Mention legacy token cleanup conditionally; no credentials or settings changed.
Only docs/maintenance-plan.md changes. Existing changed-file hooks and whitespace checks passed. No new tests, runtime changes, workflows or validation reports.