Repository navigation
v0.1.1
yamlprims v0.1.1
Patch release of yamlprims binding the yamlprims-core-depth255 r1 native parser ceiling conformance profile at structcorpus commit 6b1266e16676dc456328eb64c0eed028060845c3, adding the six 255-level sequence and alias-expansion ceiling vectors to the four-language differential suite, and hardening workspace release hygiene.
Conformance & differential parity
- Pinned
structcorpusqualification (conformance/pins/pin-6b1266e.json): Both the Rust conformance driver (crates/yamlprims/examples/structcorpus.rs) and the pure-Go conformance driver (cmd/structcorpus-driver) qualify all20profile rows ofstructcorpuscommit6b1266e16676dc456328eb64c0eed028060845c3acrossspec-v1.0throughspec-v1.4(61,366corpus cases /90,988expectations, including the6yamlprims-core-depth255r1 native depth-ceiling expectations atS_254(0),S_255(0),S_256(0),alias-252,alias-253, andalias-254, plus51synthetic revision 1.4 boundary probes across both drivers inconformance/requalify.sh). Historicalconformance/pins/pin-c8b7421.jsonandconformance/pins/pin-400ae34.jsonremain preserved for reproducible historical qualification. - Four-language byte-for-byte parity (
160in-repo vectors):make crosscheck,make ts-check, andmake python-checkverify byte-for-byte agreement across Rust (yamlprims), Go (github.com/3leaps/yamlprims/yaml), TypeScript (@3leaps/yamlprims), and Python (yamlprims) on all160in-repo conformance vectors (conformance/vectors/cases.jsonl, SHA-2565579d41aed0aa65b34a8141638cfe0c33f94b0ac90f2e7297f7c6d261e4609e8), including the six 255-level depth-ceiling vectors under explicitLimits. - Python wire-parser stack safety at
max_depth = 255: Converted the Pythonyamlprims-value/1JSON parser (_WireJsonParserinbindings/python/python/yamlprims/__init__.py) to an explicit heap-stack state machine and unified_write_node, eliminating PythonRecursionErrorwhen loading or round-tripping legal 255-deep containers under default CPython recursion limits. - Workspace hygiene: Added
/dist/to root.gitignoreso staged release artifact directories never appear as untracked paths in working checkouts.
Verification
The yamlprims CLI parses and projects YAML; it verifies no cryptographic signatures and embeds no keys. To verify this release, verify the annotated OpenPGP-signed v0.1.1 tag and the dual-signed checksum manifests (SHA256SUMS and SHA512SUMS, signed with both Minisign and the OpenPGP release signing subkey) against the public pins committed in the tagged tree (docs/security/ and keys/expected-fingerprints.txt); see docs/security/README.md and RELEASE_CHECKLIST.md.