release 3.2

Release notes, drafted

Four notes cover everything user-visible in 3.2. Each is a draft you own: double-click one (or its ✎) and rewrite it until it reads right — the exact wording reaches me, and the next version of this page carries it. The framing lines are mine, and one of them is a rewrite I'm proposing: accept or reject it in the margin, or select it and comment if it needs discussing first. When the set reads well, sign off; if a note shouldn't ship at all, say so in a comment.

CLI

Adds --dry-run to every mutating command. Running without it is unchanged, so existing scripts keep working.
✎

API

Kept deliberately dry — the Sunset header does the announcing, and the migration guide carries the detail.

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 only visual change.

before: the run list, before and after the status columnbefore
after: the run list, before and after the status columnafter
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) — rounded rather than promised.

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.

Run the schema migration before deploying. It is online and takes about a minute on a million rows.
✎
✓ Accept✗ Reject

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.