Skip to content

v0.1.0

Choose a tag to compare

@3leapsdave 3leapsdave released this 08 Nov 21:28
Immutable release. Only release title and notes can be modified.
v0.1.0
43a9c80

yamlprims v0.1.0

First code and package release of yamlprims: the spec-v1.4 YAML 1.2.2 Core Schema data layer in two independent Profile B implementations — safe Rust (yamlprims) and pure Go (github.com/3leaps/yamlprims/yaml) — together with the TypeScript WebAssembly binding (@3leaps/yamlprims), the Python abi3 binding (yamlprims), and the yamlprims CLI.

What it ships

  • Rust crate (yamlprims on crates.io, MSRV 1.88.0): #![forbid(unsafe_code)] library providing load, load_with, load_bytes, load_all, load_all_with, load_all_bytes, typed serde::Deserialize (from_str, from_str_with, from_slice, from_slice_with, from_node), canonical yamlprims-value/1 wire encoding (encode, encode_error), and plain JSON projection (encode_plain).
  • Go module (github.com/3leaps/yamlprims, package yaml, Go 1.21+): Pure-Go twin (CGO_ENABLED=0, standard library only, zero cgo) locked to the same spec-v1.4 value, resource-budget, error, and yamlprims-value/1 wire contract.
  • TypeScript / JavaScript package (@3leaps/yamlprims on npm): Zero-import wasm32-unknown-unknown WebAssembly module embedded in an ES module with zero runtime dependencies, linked with a 128 MiB (2048-page) linear-memory ceiling, pre-copy reservation validation, status-2 OutputLimitExceeded fallback, and 16 MiB high-water instance recycling.
  • Python package (yamlprims on PyPI): Prebuilt cp310-abi3 wheels (#![forbid(unsafe_code)] in crate via PyO3/maturin, GIL detached during native loads with catch_unwind panic containment) for CPython 3.10+ on Linux x86_64/aarch64 (manylinux2014, glibc 2.17+), macOS arm64, and Windows x86_64/arm64, plus source distribution (yamlprims-0.1.0.tar.gz).
  • Prebuilt yamlprims CLI (check, dump, dump --plain): Packaged archives for x86_64-unknown-linux-gnu, aarch64-unknown-linux-gnu, aarch64-apple-darwin, x86_64-pc-windows-msvc, and aarch64-pc-windows-msvc.

Core semantics & resource bounds

  • Strict YAML 1.2.2 Core Schema: Exact 128-bit integers (i128::MIN..=u128::MAX), IEEE 754 f64 floats, arbitrary mapping keys (Value::key_eq / KeyEq), retained non-core tags (UnknownTags::Preserve by default or UnknownTags::Reject), and strict flow/block indentation (ADR-0003). YAML 1.1 boolean words (yes, no, on, off, y, n) resolve as plain strings.
  • Explicit duplicate-key, NaN-key, and merge policies: Duplicate mapping keys are rejected (ErrorKind::DuplicateKey with RelatedRole::FirstDefinition), NaN keys are rejected (ErrorKind::InvalidKey), and << merge directives default to MergeKeys::Reject with explicit MergeKeys::Apply or MergeKeys::AsKey (ADR-0001).
  • Finite pre-materialization resource budgets (Limits): 12 validated resource limits (max_input_bytes, max_depth, max_nodes, max_expanded_nodes, max_alias_events, max_owned_bytes, max_scalar_bytes, max_key_bytes, max_mapping_entries, max_documents, max_output_bytes, max_warnings), including combined source collection depth, bytes-only anchor-cache registration, capacity-before-copy merge admission, and output-byte preflight (SecDR-0001).

Conformance & differential parity

  • Pinned structcorpus qualification (conformance/pins/pin-c8b7421.json): Both the Rust conformance driver (yamlprims-conformance-driver) and the pure-Go conformance driver (cmd/structcorpus-driver) qualify all 19 profile rows of structcorpus commit c8b7421b9e2473a9a7f37d04e3acfd5f552a2f99 across spec-v1.0 through spec-v1.4 (61,360 corpus cases / 90,982 expectations, plus 41 synthetic revision 1.4 boundary probes).
  • Four-language byte-for-byte parity: make crosscheck, make ts-check, and make python-check verify byte-for-byte agreement across Rust, Go, TypeScript, and Python on all 154 in-repo conformance vectors (conformance/vectors/cases.jsonl, SHA-256 f227a1205a9fbd97d0b13f2a9ef9cd01b3f2c747d35a83f781b1e3c77a0609f6) and on structcorpus --crosscheck-jsonl when present.

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.0 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.