Skip to content

Document watcher mode dbt 1.5+ requirement #2700

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Merged
tatiana merged 9 commits into from
May 28, 2026
+20 −0
Merged

Document watcher mode dbt 1.5+ requirement #2700

Changes from all commits
Commits
Show all changes
9 commits
Select commit Hold shift + click to select a range
339c6bc
Document dbt 1.8+ requirement for watcher execution mode
tatiana May 19, 2026
61c81e4
Snapshot watcher-tested requirements for dbt 1.8/1.9/1.10 on AF 3.2
tatiana May 19, 2026
d486c06
Drop editable astronomer_cosmos pin from reference snapshots
tatiana May 19, 2026
aab5c4f
Apply suggestion from @tatiana
tatiana May 27, 2026
5948e90
Correct dbt 1.5+ floor explanation in watcher docs
tatiana May 27, 2026
f80bccf
Update requirements/requirements-airflow-3.2-dbt-1.8.txt
tatiana May 27, 2026
f7cdbdc
Update requirements/requirements-airflow-3.2-dbt-1.9.txt
tatiana May 27, 2026
e79acc1
Update requirements/requirements-airflow-3.2-dbt-1.10.txt
tatiana May 27, 2026
1405700
Drop dbt 1.8 / 1.9 / 1.10 requirements reference snapshots
tatiana May 27, 2026
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
20 changes: 20 additions & 0 deletions docs/guides/run_dbt/airflow-worker/watcher-execution-mode.rst
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -354,6 +354,26 @@ which increases overall task throughput. By default, the sensor now runs in defe
Known limitations
~~~~~~~~~~~~~~~~~

Minimum supported dbt version
+++++++++++++++++++++++++++++

``ExecutionMode.WATCHER`` requires **dbt-core 1.5 or newer**. The watcher
relies on ``--log-format json`` to consume structured per-model events from
dbt, with the flag placed after the dbt subcommand (e.g.
``dbt build --log-format json …``). dbt-core 1.5 introduced finer-grained
Comment thread
tatiana marked this conversation as resolved.
log CLI parameters (see the
`dbt-core 1.5.0 changelog <https://github.com/dbt-labs/dbt-core/blob/v1.5.0/CHANGELOG.md#dbt-core-150---april-27-2023>`_,
"Implemented new log cli parameters for finer-grained control", tracked in
`dbt-core#6639 <https://github.com/dbt-labs/dbt-core/issues/6639>`_) and
accepts ``--log-format`` in that position; older dbt releases predate this
change and are not validated by Cosmos's watcher tests.

dbt versions older than 1.5 have all reached end of life and are no longer
supported by dbt Labs; see the
`dbt Core versions <https://docs.getdbt.com/docs/dbt-versions/core>`_ page
for current dbt-Labs-supported releases. If you must run an older dbt
Comment thread
tatiana marked this conversation as resolved.
release with Cosmos, use ``ExecutionMode.LOCAL`` instead.

Producer task implementation
++++++++++++++++++++++++++++

Expand Down