Summary

Coordinated release bundling the 16-PR cascade merged 2026-04-22 / 23 since the last release (engine-v1.13.0 / dagster-v1.9.0 / vscode-v1.6.3).

• Engine 1.13.0 → 1.14.0 (20 Cargo.toml bumps + CHANGELOG finalize; rocky-bigquery stays on its own 0.1.0 track).
• dagster-rocky 1.9.0 → 1.10.0 (pyproject.toml + CHANGELOG).
• rocky vscode 1.6.3 → 1.6.4 (package.json + CHANGELOG).

Headlines

Engine 1.14.0 (12 PRs)

• Arc 7 wave 2 wave-2 complete — cached DESCRIBE end-to-end. rocky run taps batch_describe_schema results into a persisted SCHEMA_CACHE; rocky compile / rocky lsp now typecheck leaf models against real warehouse types without a live round-trip. New rocky discover --with-schemas / rocky state clear-schema-cache / --cache-ttl surface. (feat(engine/rocky-core): schema cache infra (Arc 7 wave 2 wave-2 PR 1a) #223, feat(engine): wire Arc 7 wave 2 wave-2 schema cache into typecheck callsites (PR 1b) #228, feat(engine): rocky run schema-cache write tap (Arc 7 wave 2 wave-2 PR 2) #230, feat(engine/rocky-cli): add rocky discover --with-schemas (PR 3) #231, feat(engine/rocky-cli): rocky state clear-schema-cache + --cache-ttl (Arc 7 PR 4) #232)
• Arc 2 wave 3 complete — bytes_scanned / bytes_written on MaterializationOutput, so rocky cost produces real $ on BigQuery + Databricks. Snowflake deferred by design (cost is duration × DBU). (feat(engine/rocky-bigquery): plumb totalBytesBilled into bytes_scanned #219, docs(engine/rocky-snowflake): document why bytes_scanned is deferred #220, feat(engine/rocky-databricks): override execute_statement_with_stats with total_byte_count #221, docs(engine): clarify bytes_scanned holds billing-relevant bytes, not scan volume #222)
• Unity Catalog workspace-binding reconcile (feat(engine/rocky-databricks): reconcile Unity Catalog workspace bindings alongside grants #226) — behaviour change worth flagging for consumers: reconciler removes hand-added bindings not in rocky.toml.
• Fivetran connector metadata (feat(engine/rocky-fivetran): surface connector config metadata via SourceOutput.metadata #225) via adapter-namespaced SourceOutput.metadata.
• Internal: compute_backoff lifted into rocky_core::retry (refactor(engine/rocky-core): dedup compute_backoff across adapter crates #217).

Dagster 1.10.0 (4 PRs)

• FR-001 RockyComponent Pipes execution mode + FR-006 strict rocky doctor on startup (feat(integrations/dagster): wave 1 — Pipes execution mode + strict doctor on startup #224).
• FR-003 RockyResource.state_health() accessor (feat(integrations/dagster): add RockyResource.state_health() accessor #227) + sub-second probe follow-up via doctor(check="state_rw") forwarding (feat(integrations/dagster): thread --check through doctor() #229).
• RockyResource.cost() wiring + fixture (feat(integrations/dagster): add RockyResource.cost() method + fixture #218).

VS Code 1.6.4

• Regenerated TS bindings for engine 1.14.0 type additions (ClearSchemaCacheOutput, DiscoverOutput.schemas_cached, SourceOutput.metadata, MaterializationOutput.bytes_scanned/bytes_written). No extension feature changes.

Known follow-up (not in this PR)

• state_path CLI-vs-LSP unification. CLI default .rocky-state.redb in CWD vs LSP models_dir.join(".rocky-state.redb") diverge. Until unified, LSP inlay-hints don't observe what rocky run writes to the cache. Needs a migration story for existing user state files — separate PR.

Test plan

• cargo build -p rocky-cli + cargo build -p rocky (binary reports rocky 1.14.0) — clean
• cargo fmt --all --check — clean
• uv run pytest tests/ in integrations/dagster — 374/374 green
• npm run compile in editors/vscode — clean at v1.6.4
• just codegen — no drift (bindings already in sync from each merged PR)
• No 1.13.0 version refs left under engine/ (aside from Cargo.lock which got regenerated, and unrelated fixture data files which carry old engine-version strings until just regen-fixtures is run)
• CI (engine-ci, codegen-drift) green on this PR before merge

Release-day flow after merge

1. Merge this PR to main.
2. From the merged commit: git tag -a engine-v1.14.0 -m "Release engine-v1.14.0" && git push origin engine-v1.14.0 — triggers engine-release.yml (5-target matrix, ~15-25 min).
3. git tag -a dagster-v1.10.0 -m "Release dagster-v1.10.0" && git push origin dagster-v1.10.0 — triggers dagster-release.yml (wheel → PyPI via OIDC).
4. git tag -a vscode-v1.6.4 -m "Release vscode-v1.6.4" && git push origin vscode-v1.6.4 — triggers vscode-release.yml (VSIX → Marketplace via VSCE_PAT).