Repository navigation
Prepare the first public 0.2.0 release - #43
Merged
Merged
Conversation
wangjohn
marked this pull request as ready for review
October 9, 2026 04:45
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 the first public 0.2.0 release with the October 8 preparation date, twelve completed onboarding work packages and two explicitly deferred proposals: WP-1's z-score cap (#30) and WP-10's bundled generic contrast (#37). References/scores remain 8.1 and evaluations 2.1. The four-document diff changes no algorithms, dependencies, package version or workflow.
The release guide distinguishes new TestPyPI dispatches from immutable same-version reruns, requires source/archive/hash evidence and fresh index install/setup/version/demo/explicit-score verification, and keeps the README's verified GitHub fallback and next-version follow-up conditional on actual publication. The existing workflow checks tests before development-version mutation, guards tag/package-version agreement, builds once and validates those exact archives before upload.
Independent October 8 review refreshed stale preparation dates and rechecked both public project JSON endpoints: each returned HTTP 404. GitHub environments were read-only verified: TestPyPI allows only main; PyPI allows only v* tags and requires wangjohn review. Account-level publisher bindings, actual uploads, index installs and release tag remain maintainer gates; none were performed by this reviewer. Draft release notes remain unpublished.
Validation on head
8b06b0bec0fb6830eaac545534016ecc4dec9c41:make dist-check DIST="--syntax": passed; checked sdist/wheel contents, strict twine rendering, clean Python 3.11 wheel CLI/library/demo, syntax model setup/idempotence and parser-enabled build/demo. This is local wheel evidence, not an index install.Historical evidence is preserved: actual main
fbafabba5a9d0361469eb3c42698b1ac22fa67d9passed all eleven jobs in CI 37275647444, including full native Windows and regressions. Previous preparation headdcd39c262bcfec3ec561bb2f4bcc1b25d517f217passed all eleven in CI 37276896588. Earlier implementation reported full local source/sdist checks and scratch development-archive rehearsal; their disappeared temporary archives/logs were not independently reverified by this review.The maintainer owns final merge selection, publisher account setup, TestPyPI rehearsal, tag/PyPI approval/upload, archive hashes and fresh index verification, optional GitHub release, then README/index instructions and next-version follow-up. English/own-contrast and experimental paragraph research limits remain explicit.
Fresh verification reran packaging/report compatibility (147 passed, no skips), confirmed local setup/version/demo/explicit-score contracts, and independently verified current project endpoints remain 404. These source/local probes are not index-install evidence.