Prepare LabCraft-Eval v0.1.2 integrity release - #17
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.
What changed
v0.1.2v0.1.2as a metadata-only Hugging Face release while preserving the frozenv0.1.1scored snapshotWhy
The public
mainbranch predates the current scorer, provenance, and model-identity fixes. This PR promotes the verified integrity branch and makes the repository suitable for a reader-facing public release without rewriting the frozen historical result artifacts.Validation
uv lock --checkuv sync --frozen --extra dev --extra analysis --extra providersuv run --frozen python scripts/model_matrix.py validateuv run --frozen ruff check .uv run --frozen pytest -q(486 passed)labcraft 0.1.2)git diff --checkLocal Docker validation was not available because the desktop Docker daemon was not running; the PR CI Docker job is the authoritative check.
CodeQL visibility note
CodeQL completed extraction and analysis of 84/84 Python files and 2/2 workflow files, but SARIF upload is unavailable while this repository is private. After merge, the repository will be made public and the
mainCodeQL push run must pass before tagging or announcing v0.1.2.