release 3.2
Release notes, drafted
Four notes cover everything user-visible in 3.2. Rewrite any draft in place; decide the proposed replacement, deletion, and addition in the margin; then sign off on the wording that should ship.
CLI
Adds --dry-run to every mutating command. Running without it is unchanged, so existing scripts keep working.
API
The v1 header is deprecated, not gone.
Deprecates the v1 auth header. It keeps working until the next major, and the server now sets a Sunset header on every v1 response.
Console
The run list grew a status column, so a failure now reads off the list instead
of costing a click each. It is the release's
Run status now shows on the run list itself. Filtering by it lands in 3.3.
Operations
The minute figure is from staging (1.1M rows) on a warm cache — rounded rather than promised. If operators will book a window around it, the note should give a range instead.
Plan a brief deployment window for this migration; staging took 45–75 seconds on 1.1 million rows.
Run the schema migration before deploying. It is online and takes about a minute on a million rows.
Left out on purpose
The dependency bumps and the flaky-test fixes stay in the changelog only — nothing a user would change behavior over. If one of them deserves a note after all, say so in a comment and a draft for it arrives in the next version.
Bumps the PDF renderer to 4.1. Output is unchanged on our corpus; the bump is for the upstream security fix.