v0.186.1

0.186.1 (2026-10-29)

Quoted columns in snapshots, microbatch cursors and merges

Following 0.186.0's support for quoted mixed-case columns, the remaining configuration checks now match them too:

• Snapshot keys, check columns and generated-column clashes, microbatch cursor columns, and merge immutable or excluded columns compare names the same way as contracts and incremental checks, so a quoted column such as "listingId" is found.
• On Snowflake, an unquoted configured name that only matches a case-sensitive column, such as unique_key ['listingId'] for a column created as "listingId", is now rejected with a message showing what to write ('"listingId"'). Previously it failed with a misleading "missing required columns" or "cursor not produced" error. Configurations that worked in 0.186.0 are unaffected; plain incremental merge and delete_insert keep accepting unquoted names.
• The Snowflake adapter page has a new "Case-sensitive column names" section.

Internal

• Result and cost reporting moved behind the native boundary (#1272); no behaviour change.

Full change: #1273