Repository navigation
v0.11.0: numeric correctness and clean consumer validation #342
Description
0.11 addresses two reproduced numeric failures: unsafe Python integers silently round, and Arrow float16 values decode as storage bits.
Tracking:
- fix(codec): reject unsafe Python integers before JSON encoding #331
- fix(codec): decode Arrow float16 values for NumPy and Torch #332
- test(ci): generate and execute wrappers in a clean consumer project #333
- chore(release): integrate and validate the 0.11 numeric correctness release #334
The integer policy for this release is explicit rejection outside the JavaScript safe range. Exact bigint transport remains a separate design in #337.
Release acceptance:
- Each child issue meets its acceptance criteria.
- Numeric menagerie rows reflect corrected values or explicit rejection.
- Generated wrappers pass the clean consumer gate.
- Full checks pass on the integrated release commit, including required CI and resolved CodeRabbit threads.
- Migration notes and published-package verification are complete.
Start the bounded architecture prototypes in #345 before deciding implementation order and the release split. Preserve the numeric acceptance criteria here; prototype completion alone does not close the defects. Historical #260 tracks the already-shipped 0.9 work and is not a duplicate of this release.
Activity
bbopen commentedon Sep 20, 2026
The 0.11 release is complete. The numeric corrections, clean consumer gate, release integration, and migration guidance meet their child criteria. Menagerie expectations now require unsafe integer rejection and successful numeric float16 conversion. The complete candidate passed required CI and independent review; publication and fresh registry installation are verified below.
Verified release evidence:
0861ebeand mergef6f811dhave identical trees.The architecture decision records the accepted scope and prototype limits.
Closing with the implemented and verified 0.11 release outcome.