Skip to content

Releases

v0.3.0

Choose a tag to compare

@3leapsdave 3leapsdave released this 18 Nov 19:26
Immutable release. Only release title and notes can be modified.
v0.3.0
42e12ca

yamlprims v0.3.0

Feature release of yamlprims implementing spec-v1.6: bounded byte-slice, reader, and writer ergonomics across Rust and Go, TypeScript parse / stringify plain-value helpers, Python single-pass native PyO3 safe_load / safe_load_all and buffered safe_dump / safe_dump_all, the YAML 1.1 to YAML 1.2.2 Core migration lint (lint_yaml11*, LintYAML11*, lintYaml11, and canonical yamlprims-lint/1), and the frozen yamlprims-cli command-line contract (migrating-from-libyaml.md).

What it ships

  • Bounded stream, byte-slice, and plain-host ergonomics (spec-v1.6 §9, §10.2, §11.2, §11.5):
    • Rust (yamlprims): load_reader, load_reader_with, load_all_reader, load_all_reader_with, from_slice, from_slice_with, from_reader, from_reader_with, to_writer, to_writer_with, emit_writer, emit_writer_with, emit_all_writer, and emit_all_writer_with. Readers read at most Limits::max_input_bytes + 1 bytes before raw-input admission; writers buffer the complete emitted payload under EmitLimits::max_output_bytes before calling writer.write_all, guaranteeing zero bytes written on any validation or limit refusal.
    • Go (github.com/3leaps/yamlprims/yaml): LoadBytesWith, LoadAllBytesWith, LoadReader, LoadReaderWith, LoadAllReader, LoadAllReaderWith, EmitWriter, EmitWriterWith, EmitAllWriter, EmitAllWriterWith, MarshalWriter, MarshalWriterWith, and typed Unmarshal, UnmarshalWith, UnmarshalReader, UnmarshalReaderWith, UnmarshalNode, and UnmarshalNodeWith (with math/big.Int support for full i128::MIN..=u128::MAX integers, default unknown-struct-field rejection, iterative finite pointer-chain unwrapping, and pointer-cycle rejection).
    • Python (yamlprims): Single-pass native PyO3 safe_load, safe_load_all, and buffered safe_dump, safe_dump_all accepting str, bytes, bytearray, memoryview, or .read() / .write() streams, enforcing pre-copy chunk byte caps (max_input_bytes) and materializing plain Python dict, list, str, int (up to 128-bit), float, bool, and None without a JSON round-trip.
    • TypeScript (@3leaps/yamlprims): parse, parseAll, stringify, and stringifyAll plain-value helpers (parse / parseAll return number for integers within ±(2^53 - 1) and raise a type error outside that range; stringify / stringifyAll also accept bigint inputs).
  • YAML 1.1 → YAML 1.2.2 Core migration lint (spec-v1.6 §10.3, §11.7):
    • Rust: LintCode (Yaml11Boolean, Yaml11Number, Yaml11Sexagesimal, Yaml11MergeKey), LintDiagnostic, LintResult, lint_yaml11, lint_yaml11_with, lint_yaml11_bytes, lint_yaml11_reader, lint_yaml11_reader_with, and encode_lint (yamlprims-lint/1).
    • Go: LintCode, LintDiagnostic, LintResult, LintYAML11, LintYAML11With, LintYAML11Bytes, LintYAML11Reader, LintYAML11ReaderWith, EncodeLint, and EncodeLintWith.
    • TypeScript: LintCode, LintDiagnostic, LintResult, lintYaml11, and encodeLint.
    • Python: LINT_CODES, LintDiagnostic, LintResult, lint_yaml11, and encode_lint.
    • Enforces Limits::max_warnings (1,000 default) truncation prior to diagnostic string formatting, fixed-buffer streaming field/message bounds (1,024 / 4,096 bytes), and pre-clone path/diagnostic max_owned_bytes admission with zero-clone error-path transfer on budget abort.
  • Frozen yamlprims-cli command-line contract (spec-v1.6 §10.4):
    • yamlprims [--merge=reject|apply|as_key] check [--lint-yaml11] [--format=text|json], yamlprims [--merge=...] dump [--plain|--ijson] [--max-output-bytes=N], yamlprims [--merge=...] emit [--from-wire|--from-plain] [--compat-quoting=yaml11-safe|core-only] [--max-output-bytes=N] (--max-output-bytes also applies to check --lint-yaml11 --format=json), --version, --help, - (stdin), --, whole-payload buffered stdout, and exit codes 0 / 1 / 2 as specified in spec-v1.6 §10.4.
  • Migration guide:

Conformance & differential parity

  • Pinned structcorpus load and emit round-trip qualification (conformance/pins/pin-b52fcd0.json): Both the Rust (crates/yamlprims/examples/structcorpus.rs) and pure-Go (cmd/structcorpus-driver) conformance drivers qualify all 20 profile rows of structcorpus commit b52fcd090d6879a0bd58ec5a5496c6a4de90504e (61,366 corpus cases / 90,988 expectations across spec-v1.0 through spec-v1.5, plus synthetic revision 1.4/1.5 boundary probes).
  • Four-language byte-for-byte parity (188 in-repo vectors): make crosscheck, make ts-check, and make python-check verify byte-for-byte agreement across Rust, Go, TypeScript, and Python on all 188 in-repo conformance vectors (conformance/vectors/cases.jsonl) covering yamlprims-value/1 wire output, decode_wire round-trip, plain JSON projection, deterministic emit_all output, encode_ijson projection, and yamlprims-lint/1 encode_lint output.

Verification

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

v0.2.2

Choose a tag to compare

@3leapsdave 3leapsdave released this 13 Nov 23:10
Immutable release. Only release title and notes can be modified.
v0.2.2
f9d1fd2

yamlprims v0.2.2

Patch release of yamlprims that hardens the release procedure. The library, CLI behaviour and the spec-v1.5 contract are unchanged.

What it ships

  • Explicit release commit: make release-tag refuses unless HEAD, fetched origin/main and YAMLPRIMS_RELEASE_COMMIT are the same commit, and the tag is signed on that commit rather than HEAD. make release-push-tag captures each verified annotated tag object, refuses one that names another commit or moved during verification, pushes that object by id, and requires the remote to hold exactly it. YAMLPRIMS_RELEASE_COMMIT was documented before but was not checked.
  • Per-release environment checks: make release-env-check names every per-release value (YAMLPRIMS_RELEASE_COMMIT, YAMLPRIMS_EXPECTED_*, YAMLPRIMS_RELEASE_ANCHOR_FILE, YAMLPRIMS_RELEASE_RUN_ID/_ATTEMPT, YAMLPRIMS_CRATE_RUN_ID) that belongs to another release. eval "$(make -s release-env-reset)" clears them. The release checklist starts with both.
  • Anchor-file binding after tagging: once YAMLPRIMS_RELEASE_ANCHOR_FILE names this tag's recorded anchor, release-verify-published-tag.sh binds to it (including when it writes an anchor), refuses an exported YAMLPRIMS_EXPECTED_* that disagrees, an anchor for another tag, and a configured anchor that is not a regular file. Recorded anchors for spec-vX.Y tags are accepted.
  • Clearer guard errors: the anchor, run-selection and crate-records guards print the values they compared and the likely cause.
  • npm validation lag: the OIDC publish step verifies npm with a 120 x 15 s poll budget by default, and the publish-npm job timeout is 45 minutes, so a successful publish no longer fails the job while npm validates the upload.
  • Prepush preflight: check-tooling.py --prepush fails at once, naming the python3-venv package, when the interpreter cannot create a venv. The make doctor yamllint floor is now 1.29.0, the Debian bookworm yamllint that the digest-pinned CI toolbox image installs (without a version pin).
  • Release checklist: adds make release-create-draft before signing, removes the section 4 crate dry run that ran before release-crates-fetch, lists the crate publish inputs, documents npm's validation delay, adds the post-publish Homebrew tap and Scoop bucket step, and lists YAMLPRIMS_YAML_BIN, YAMLPRIMS_DECERNOR_BIN and YAMLPRIMS_CARGO_TOKEN_FILE in the release environment.

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

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.

v0.2.0

Choose a tag to compare

@3leapsdave 3leapsdave released this 11 Nov 19:12
Immutable release. Only release title and notes can be modified.
v0.2.0
1b365fc

yamlprims v0.2.0

Feature release of yamlprims implementing the spec-v1.5 YAML 1.2.2 Core Schema data-layer writer, checked caller-tree constructors, stack-safe heap-worklist Node operations, symmetric decode_wire over yamlprims-value/1, and strict six-rule RFC 7493 I-JSON projection across Rust (yamlprims), pure Go (github.com/3leaps/yamlprims/yaml), TypeScript WebAssembly (@3leaps/yamlprims), Python PyO3/maturin (yamlprims), and the yamlprims CLI (ADR-0005).

What it ships

  • Deterministic YAML 1.2.2 Core Schema emitter (spec-v1.5 §10.2):
    • Rust (yamlprims): emit, emit_with, emit_all, emit_all_with, CompatQuoting (Yaml11Safe default, CoreOnly), EmitLimits, EmitOptions, and serde::Serialize support (impl serde::Serialize for Value/Node/Document/Mapping/Integer plus to_node, to_string, and to_string_with).
    • Go (github.com/3leaps/yamlprims/yaml): Emit, EmitWith, EmitAll, EmitAllWith, CompatQuoting (CompatQuotingYaml11Safe default, CompatQuotingCoreOnly), EmitLimits, EmitOptions, FromPlain, Marshal, and MarshalWith.
    • TypeScript (@3leaps/yamlprims): dump, dumpAll, fromPlain, defaultEmitLimits, and defaultEmitOptions over the zero-import wasm32-unknown-unknown module (emit_wire, load_ijson).
    • Python (yamlprims): dump, dump_all, from_plain, EmitLimits, and EmitOptions over the cp310-abi3 PyO3 module (GIL detached during native emission and wire decoding).
    • CLI (yamlprims): yamlprims emit (--from-wire, --from-plain, --compat-quoting=yaml11_safe|core_only, --merge=reject|apply|as_key, --max-output-bytes=N).
  • Strict RFC 7493 I-JSON projection (spec-v1.5 §11.6):
    • Rust: encode_ijson, load_ijson, load_ijson_with, load_ijson_bytes, and Options::ijson_default().
    • Go: EncodeIJSON, EncodeIJSONWith, LoadIJSON, LoadIJSONWith, LoadIJSONBytes, and DefaultIJSONOptions().
    • TypeScript & Python: loadIjson / load_ijson.
    • CLI: yamlprims dump --ijson.
    • Enforces the six RFC 7493 rules: single non-empty-stream document (ErrorKind::Type { expected: "single YAML document", found: "empty_stream" } on empty/comment-only streams, MultipleDocuments on >1), IEEE 754 safe integers in [-9_007_199_254_740_991, +9_007_199_254_740_991] (IntegerOutOfRange), finite binary64 floats with -0.0 emitted as 0 (FloatOutOfRange on NaN/±Infinity), String-only mapping keys (ErrorKind::Type { expected: "I-JSON string key", found: "non_string_key" }), mandatory UnknownTags::Reject (UnknownTag on any Tagged node), and rejection of all 66 Unicode noncharacters (U+FDD0..=U+FDEF and U+nFFFE/U+nFFFF across planes 0..=16) in keys and strings (ErrorKind::Type { expected: "RFC 7493 I-JSON string", found: "noncharacter" }).
  • Checked caller-tree construction, stack-safe Node operations, and symmetric decode_wire (spec-v1.5 §3, §6, §11.1):
    • Checked Document::new, Document::with_metadata, Tag::try_new, Tag::with_spelling, Tagged::new, and Node::into_value in Rust (plus aligned Go NewSimpleDocument, TryNewDocumentWithMetadata, TryNewTag, TryNewTagWithSpelling, TryNewTagged).
    • Iterative heap-worklist Drop, Clone, and PartialEq plus depth-bounded Debug (<= 255) for Node, Value, Mapping, Tagged, and Document, preventing call-stack overflow on deep caller-constructed trees on 2 MiB threads.
    • Symmetric Rust decode_wire(json: &str, opts: &Options) -> Result<WireEnvelope, Error> and aligned Go DecodeWire enforcing Limits before materialization.

Conformance & differential parity

  • Pinned structcorpus load and emit round-trip qualification (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 all 20 profile rows of structcorpus commit 6b1266e16676dc456328eb64c0eed028060845c3 across spec-v1.0 through spec-v1.4 (61,366 corpus cases / 90,988 expectations, including load -> emit_all_with -> load semantic identity across every positive value expectation in both drivers, plus 51 synthetic revision 1.4 boundary probes).
  • Four-language byte-for-byte parity (176 in-repo vectors): make crosscheck, make ts-check, and make python-check verify byte-for-byte agreement across Rust, Go, TypeScript, and Python on all 176 in-repo conformance vectors (conformance/vectors/cases.jsonl, SHA-256 91916121ab33318509739adce37e1e45804b20514c66339d1c1a97d028e690dc) covering yamlprims-value/1 wire output, decode_wire round-trip, plain JSON projection, deterministic emit_all output, and encode_ijson projection.

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

v0.1.1

Choose a tag to compare

@3leapsdave 3leapsdave released this 11 Nov 18:24
Immutable release. Only release title and notes can be modified.
v0.1.1
b51336f

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 structcorpus qualification (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 all 20 profile rows of structcorpus commit 6b1266e16676dc456328eb64c0eed028060845c3 across spec-v1.0 through spec-v1.4 (61,366 corpus cases / 90,988 expectations, including the 6 yamlprims-core-depth255 r1 native depth-ceiling expectations at S_254(0), S_255(0), S_256(0), alias-252, alias-253, and alias-254, plus 51 synthetic revision 1.4 boundary probes across both drivers in conformance/requalify.sh). Historical conformance/pins/pin-c8b7421.json and conformance/pins/pin-400ae34.json remain preserved for reproducible historical qualification.
  • Four-language byte-for-byte parity (160 in-repo vectors): make crosscheck, make ts-check, and make python-check verify byte-for-byte agreement across Rust (yamlprims), Go (github.com/3leaps/yamlprims/yaml), TypeScript (@3leaps/yamlprims), and Python (yamlprims) on all 160 in-repo conformance vectors (conformance/vectors/cases.jsonl, SHA-256 5579d41aed0aa65b34a8141638cfe0c33f94b0ac90f2e7297f7c6d261e4609e8), including the six 255-level depth-ceiling vectors under explicit Limits.
  • Python wire-parser stack safety at max_depth = 255: Converted the Python yamlprims-value/1 JSON parser (_WireJsonParser in bindings/python/python/yamlprims/__init__.py) to an explicit heap-stack state machine and unified _write_node, eliminating Python RecursionError when loading or round-tripping legal 255-deep containers under default CPython recursion limits.
  • Workspace hygiene: Added /dist/ to root .gitignore so 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.

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.