Ruben FiszelandClaude Opus 5 7b3c545ce3 fix: refuse a dbt:// subscription that is not a whole relation ...

`# on dbt://main/analytics` deployed and persisted a trigger row. Every producer
spells `<warehouse>/<schema>/<name>` — the manifest ingest derives it from
`relation_name`, a `// materialize` target is checked against it — so a partial
one is an edge nothing can ever wake, which is what the dbt-only refusal exists
to prevent.

The shape now has one definition (`is_full_relation_path`) that both halves of
the deploy ask, rather than a segment count spelled twice: a subscription and a
write that disagreed would refuse and accept the same string.

Also rewrites the canvas test's comment as a current constraint per AGENTS.md.

Co-Authored-By: Claude Opus 5 (1M context) <noreply@anthropic.com>

2026-09-05 04:34:19 +02:00

..

src

fix: refuse a dbt:// subscription that is not a whole relation

2026-09-05 04:34:19 +02:00

Cargo.toml

fix: keep native triggers attached when a runnable is renamed (#10432)

2026-07-31 23:44:25 +02:00