Yqr

v0.3.0 Breaking

This release includes 1 breaking change for platform teams planning a safe upgrade.

Published 16d CLI & Terminal

View tool

✓ No known CVEs patched

Read the diff → Tool health → What is this tool? →

✓ No known CVEs patched in this version

Topics

cli jq parser rust yaml yq

Affected surfaces

breaking_upgrade

ReleasePort's take

Light signal

editorial:auto 11d

The release introduces a new --preserve / -p flag for byte/comment‑preserving reads and changes the behavior of --engine to no longer imply preservation.

Why it matters: Breaking change: --engine now selects only the backend parser, removing its implicit preservation effect; operators must add --preserve where needed.

Summary

AI summary

Decoupled byte/comment preservation into a new --preserve flag, breaking previous implicit behavior.

Changes in this release

Type	Severity	Summary	CVE
Breaking	High	Changes --engine to select backend parser only; no longer implies preservation Changes --engine to select backend parser only; no longer implies preservation Source: llm_adapter@2026-07-15 Confidence: high	—
Feature	Low	Adds --preserve / -p flag for byte/comment‑preserving reads Adds --preserve / -p flag for byte/comment‑preserving reads Source: llm_adapter@2026-07-15 Confidence: high	—
Feature	Low	Adds runnable demo showcase under docs/content/demo/ with yqr-demo.sh and sample YAML files Adds runnable demo showcase under docs/content/demo/ with yqr-demo.sh and sample YAML files Source: llm_adapter@2026-07-15 Confidence: high	—

Full changelog

Byte/comment preservation becomes its own flag, decoupled from backend
selection.

Added

--preserve / -p flag for byte/comment-preserving reads. It turns on
fidelity mode with the default backend, so yqr -p '.' file.yaml reproduces
the input byte-for-byte — comments, quoting, indentation, and line endings
survive.
A runnable demo showcase under docs/content/demo/ (yqr-demo.sh plus sample
deploy.yaml / config.yaml inputs) walking through navigation, iteration,
pipes, raw output, and preserve mode.

Changed

--engine now selects the backend parser only and no longer implies
preservation. It picks which library performs a --preserve read (default
noyalib); whether to preserve is --preserve's job. Without --preserve,
--engine has no observable effect.

Breaking

--engine noyalib '.' no longer preserves bytes on its own — use
--preserve (optionally with --engine noyalib to name the backend
explicitly). This decouples backend choice from fidelity mode.