The dbt-materialize
adapter should always match major and minor releases of dbt-core
(i.e. if dbt-core
v1.2.x is released, we should also bump dbt-materialize
to v1.2.x). For patch releases, version numbers might differ and we should follow our own release cadence (i.e. if dbt-core
v1.1.1 is released and dbt-materialize
is on v1.1.5, that's legit).
The following line in setup.py
guarantees that the adapter always installs the latest patch version of dbt-postgres
and dbt-core
:
install_requires=["dbt-postgres~=1.1.0"],
See the dbt documentation for more details on versioning.
Run the dbt-materialize
test suite via mzcompose
to bring up all the dependencies and match how it is run in CI:
./mzcompose --dev run default