Skip to content

v0.2.1

Choose a tag to compare

@3leapsdave 3leapsdave released this 13 Nov 13:42
Immutable release. Only release title and notes can be modified.
v0.2.1
5fe5226

yamlprims v0.2.1

Patch release of yamlprims: a CLI version flag, conformance binding of the structcorpus revision 5 (spec-v1.5) policy profiles, release tooling that reads and writes workflow YAML with the published yamlprims CLI instead of PyYAML, and release-ceremony fixes. The library API and the spec-v1.5 contract are unchanged.

What it ships

  • CLI --version / -V: yamlprims --version (or -V), as the only argument, prints yamlprims 0.2.1 to stdout and exits 0; combined with any other argument it is a usage error (exit 2).
  • structcorpus revision 5 profiles (conformance/pins/pin-b52fcd0.json): The Rust (crates/yamlprims/examples/structcorpus.rs) and Go (cmd/structcorpus-driver) conformance drivers bind yamlprims-core, yamlprims-core-stream, yamlprims-core-merge-apply and yamlprims-core-merge-as-key r5 (spec-v1.5, the revision 4 source-loader policy fields) and qualify structcorpus commit b52fcd090d6879a0bd58ec5a5496c6a4de90504e (61,366 corpus cases / 90,988 expectations, 20 result rows). The corpus carries no r5 cases; synthetic driver controls in conformance/scripts/structcorpus_probes_v14.py exercise each r5 binding (62 controls per driver).
  • Release tooling without PyYAML: The workflow digest and permission checkers read workflows with yamlprims dump --plain (YAML 1.2 Core, duplicate keys refused) and write their mutation controls with yamlprims emit --from-plain, through scripts/yaml_json.py. They run the published v0.2.0 CLI, never the working tree's build, and only if its SHA-256 matches the per-platform digest in config/yamlprims-cli.txt; CI installs it with scripts/ci-install-yamlprims.sh. Maintainers set YAMLPRIMS_YAML_BIN.
  • Release-ceremony fixes: scripts/release-decernor.sh resolves the same when sourced from zsh; make release-verify-remote-tag prints the YAMLPRIMS_EXPECTED_TAG_OBJECT / YAMLPRIMS_EXPECTED_COMMIT exports for make release-record-anchor; scripts/release-verify-registries.py validates YAMLPRIMS_REGISTRY_POLL_ATTEMPTS / YAMLPRIMS_REGISTRY_POLL_SLEEP and explains a final npm 404 during npm's post-upload validation.
  • Documentation: The README describes memory-safe YAML reading and writing per language and the YAML to I-JSON to RFC 8785 JCS path with canonprims.

Verification

The yamlprims CLI parses, emits, and projects YAML; it verifies no cryptographic signatures and embeds no keys. To verify this release, verify the annotated OpenPGP-signed v0.2.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.