This release adds 3 notable features for engineering teams evaluating rollout.
Published 18d
CLI & Terminal
✓ No known CVEs patched
✓ No known CVEs patched in this version
Topics
cli
jq
parser
rust
yaml
yq
Summary
AI summaryAdded runtime‑selectable fidelity engines for byte‑preserving YAML reads.
Full changelog
Added
- Fidelity engines for byte-preserving reads, selectable at runtime with the
new--engineflag. With--engine noyalibor--engine rust-yaml,
untouched nodes are emitted as their original source bytes — comments,
quoting, indentation, and line endings survive, and the identity filter
reproduces the input byte-for-byte. - Both fidelity backends now ship in the default build, so
--engine noyalib
and--engine rust-yamlare switchable in one binary without recompiling.
Build with--no-default-featuresfor a minimal binary that carries neither
backend (the standard re-serializing pipeline still works;--enginethen
reports the backend as unavailable). - A backend-agnostic fidelity round-trip harness (
tests/fidelity.rs) that
checks theparse -> emit == inputproperty across backends, one case per
formatting dimension (comments, blank lines, indent, quote/block/flow style,
CRLF, BOM, multi-doc, anchors, numbers, key order). - A shared real-world corpus (
tests/corpus/) driving both the validation
suite and the Criterion benchmarks from one case table (Kubernetes, GitHub
Actions, Docker Compose, Helm, application config). - Kubernetes usage guide in the documentation.
Changed
- An unknown
--enginevalue is now diagnosed before any input is read, so a
typo is reported immediately instead of after consuming stdin or the file.
Weekly OSS security release digest.
The CVE patches and breaking changes that affected production tools this week. One email, every Sunday.
No spam, unsubscribe anytime.
Share this release
About Yqr
All releases →Beta — feedback welcome: [email protected]