Publish M4 semantic contrast datasets and lineage - #8
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
1 participant
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.
Publish the reviewed M4 CPU semantic contrast and lineage APIs from development merge
f7a367d70d02c3927e4c4dd2f5bfc2b3f419505a.The exact allowlisted projection changes 13 files (5 added, 8 modified), covering the advanced APIs, source-bound dataset generation, fresh replay verification, lineage records, and the bounded contact/visibility and publication-close fixes. Internal implementation plans and acceptance artifacts are excluded.
Validation: the newly commit-bound snapshot has the same 160-file content manifest as the accepted M4 public snapshot (40 smoke tests passed; wheel and sdist built; installed NO_SELECTION semantic roundtrip passed). Full development CPU acceptance was 4215 passed / 56 skipped; independent source and final candidate reviews passed. Fresh Public CI must pass on this PR before merging.
Native execution is not performed, and this does not create a release tag or PyPI release.