Skip to content

Prepare v0.2.0: version bump, release notes and rechecked README commands - #63

Merged
professor3333 merged 2 commits into
mainfrom
release/v0.2.0
Nov 15, 2026
Merged

professor3333 merged 2 commits into
mainfrom
release/v0.2.0

Conversation

@professor3333

@professor3333 professor3333 commented Nov 15, 2026 •

Copy link
Copy Markdown
Owner
  • Version 0.1.0 → 0.2.0 (pyproject.toml, __init__.py, uv.lock — one line each).
  • docs/release_notes/v0.2.0.md: preview release (gates not judgeable), same default CRF bundle as v0.1.0, changes since v0.1.0, measured dev/test results, limitations, deployment and rollback.
  • README: every listed command rerun against the project. Fixes: annotate gate needs --gold annotations/pilot/pilot-2.jsonl to reproduce docs/pilot_gate.md (verified byte-identical); annotate import comment notes it rewrites pilot-1.jsonl (labels identical, schema version updated); app run mentions --port. New v0.2.0 paragraph in the deployment section.

After merge: tag v0.2.0 → release.yml builds, smoke-tests and pushes the image; then the CRF bundle is attached, the release notes applied, and the local rollback drill v0.1.0 ↔ v0.2.0 run and recorded.

Also: test_onnx_export_and_int8_parity failed on one GitHub runner (INT8 typed F1 0.93 vs 1.0 on the tiny fixture; CPU-dependent INT8 kernels, the same failure that delayed v0.1.0). The test now checks that the INT8 path works (loads, every output passes the validator, smaller file, distinct digest) and still requires exact FP32 parity; INT8 accuracy is decided by the trained-model gate in reports/onnx-int8/.

…ands

v0.2.0 serves the same CRF bundle as v0.1.0 and ships the declared test evaluation, two-reference scoring, the ONNX/INT8 check, the prospective check, fresh-clone reproduction and the public demo. Every README command was rerun: the pilot-gate command now names pilot-2 (which reproduces docs/pilot_gate.md byte for byte), the import comment notes that re-importing rewrites pilot-1 with identical labels, and app run mentions --port.
…xture

Dynamic INT8 kernels differ between CPUs, so INT8 predictions of the tiny fixture model vary by runner; a GitHub runner moved spans to typed F1 0.93 against 1.0, failing the 0.05 allowance (the same failure delayed v0.1.0). INT8 accuracy is decided by the typed-F1 gate on a trained model (reports/onnx-int8/, where it fails for DeBERTa run 3). The test still requires exact FP32 parity, and now that every INT8 output loads and passes the validator, with a smaller file and a distinct weights digest.
@professor3333
professor3333 merged commit 1c2d0cc into main Nov 15, 2026
2 checks passed
@professor3333
professor3333 deleted the release/v0.2.0 branch November 15, 2026 03:39
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant