Dependency incompatibility

[anismikou]

Hi,

I've been trying to adapt the CLI to our needs with multi cloud platform that connects to both Databricks and BigQuery and uses dbt, however this pyproject :

python = "^3.12"
dbt-core = "~1.9"
dbt-bigquery = "~1.9"
dbt-databricks = "~1.9"
datacontract-cli = { version="~0.10", extras = ["databricks", "dbt"] }
elementary-data = "^0.16.0"

Creates a big chunk of incompatibilities :

Resolving dependencies... (70.2s)

    Because datacontract-cli[databricks,dbt] (0.10.15) depends on pydantic (>=2.8.2,<2.10.0)
 and datacontract-cli[databricks,dbt] (0.10.14) depends on pydantic (>=2.8.2,<2.10.0), datacontract-cli[databricks,dbt] (0.10.14 || 0.10.15) requires pydantic (>=2.8.2,<2.10.0).
(1) So, because datacontract-cli[databricks,dbt] (0.10.16) depends on pydantic (>=2.8.2,<2.11.0), datacontract-cli[databricks,dbt] (0.10.14 || 0.10.15 || 0.10.16) requires pydantic (>=2.8.2,<2.11.0).

    Because datacontract-cli[databricks,dbt] (0.10.15) depends on databricks-sdk (>=0.32.0,<0.39.0)
 and datacontract-cli[databricks,dbt] (0.10.14) depends on databricks-sdk (>=0.32.0,<0.36.0), datacontract-cli[databricks,dbt] (0.10.14 || 0.10.15) requires databricks-sdk (>=0.32.0,<0.39.0).
    And because datacontract-cli[databricks,dbt] (0.10.16) depends on databricks-sdk (>=0.32.0,<0.39.0)
 and datacontract-cli[databricks,dbt] (0.10.13) depends on databricks-sql-connector (>=3.1.2,<3.5.0), datacontract-cli[databricks,dbt] (0.10.13 || 0.10.14 || 0.10.15 || 0.10.16) requires databricks-sdk (>=0.32.0,<0.39.0) or databricks-sql-connector (>=3.1.2,<3.5.0).
    And because datacontract-cli[databricks,dbt] (0.10.12) depends on databricks-sql-connector (>=3.1.2,<3.4.0)
 and datacontract-cli[databricks,dbt] (0.10.11) depends on databricks-sql-connector (>=3.1.2,<3.4.0), datacontract-cli[databricks,dbt] (0.10.11 || 0.10.12 || 0.10.13 || 0.10.14 || 0.10.15 || 0.10.16) requires databricks-sdk (>=0.32.0,<0.39.0) or databricks-sql-connector (>=3.1.2,<3.5.0).
    And because datacontract-cli[databricks,dbt] (0.10.10) depends on databricks-sql-connector (>=3.1.2,<3.3.0)
 and dbt-databricks (1.9.1) depends on databricks-sdk (0.17.0), if datacontract-cli[databricks,dbt] (0.10.10 || 0.10.11 || 0.10.12 || 0.10.13 || 0.10.14 || 0.10.15 || 0.10.16) and dbt-databricks (1.9.1) then databricks-sql-connector (>=3.1.2,<3.5.0).
    And because dbt-databricks (1.9.1) depends on databricks-sql-connector (>=3.5.0,<4.0.0)
 and datacontract-cli[databricks,dbt] (0.10.9) depends on pydantic (>=2.5.3,<2.8.0), if dbt-databricks (1.9.1) and datacontract-cli[databricks,dbt] (0.10.9 || 0.10.10 || 0.10.11 || 0.10.12 || 0.10.13 || 0.10.14 || 0.10.15 || 0.10.16) then pydantic (>=2.5.3,<2.8.0).
    And because datacontract-cli[databricks,dbt] (0.10.8) depends on pydantic (>=2.5.3,<2.8.0)
 and datacontract-cli[databricks,dbt] (0.10.7) depends on pydantic (>=2.5.3,<2.8.0), if dbt-databricks (1.9.1) and datacontract-cli[databricks,dbt] (0.10.7 || 0.10.8 || 0.10.9 || 0.10.10 || 0.10.11 || 0.10.12 || 0.10.13 || 0.10.14 || 0.10.15 || 0.10.16) then pydantic (>=2.5.3,<2.8.0).
    And because datacontract-cli[databricks,dbt] (0.10.6) depends on pydantic (>=2.5.3,<2.8.0)
 and datacontract-cli[databricks,dbt] (0.10.5) depends on pydantic (>=2.5.3,<2.8.0), if dbt-databricks (1.9.1) and datacontract-cli[databricks,dbt] (0.10.5 || 0.10.6 || 0.10.7 || 0.10.8 || 0.10.9 || 0.10.10 || 0.10.11 || 0.10.12 || 0.10.13 || 0.10.14 || 0.10.15 || 0.10.16) then pydantic (>=2.5.3,<2.8.0).
    Because no versions of dbt-databricks match >1.9,<1.9.1 || >1.9.1,<1.9.2 || >1.9.2,<1.10
 and dbt-databricks (1.9.0) depends on pydantic (>=1.10.0,<2), dbt-databricks (>=1.9,<1.9.1 || >1.9.1,<1.9.2 || >1.9.2,<1.10) requires pydantic (>=1.10.0,<2).
    Thus, if datacontract-cli[databricks,dbt] (0.10.5 || 0.10.6 || 0.10.7 || 0.10.8 || 0.10.9 || 0.10.10 || 0.10.11 || 0.10.12 || 0.10.13 || 0.10.14 || 0.10.15 || 0.10.16) and dbt-databricks (>=1.9,<1.9.2 || >1.9.2,<1.10) then pydantic (>=1.10.0,<2 || >=2.5.3,<2.8.0).
    And because datacontract-cli[databricks,dbt] (0.10.14 || 0.10.15 || 0.10.16) requires pydantic (>=2.8.2,<2.11.0) (1), datacontract-cli[databricks,dbt] (0.10.14 || 0.10.15 || 0.10.16) is incompatible with dbt-databricks (>=1.9,<1.9.2 || >1.9.2,<1.10)
    And because datacontract-cli[databricks,dbt] (0.10.4) depends on opentelemetry-exporter-otlp-proto-http (>=1.16.0,<1.17.0)
 and datacontract-cli[databricks,dbt] (0.10.3) depends on opentelemetry-exporter-otlp-proto-http (>=1.16.0,<1.17.0), if dbt-databricks (>=1.9,<1.9.2 || >1.9.2,<1.10) and datacontract-cli[databricks,dbt] (0.10.3 || 0.10.4 || 0.10.14 || 0.10.15 || 0.10.16) then opentelemetry-exporter-otlp-proto-http (>=1.16.0,<1.17.0).
    And because datacontract-cli[databricks,dbt] (0.10.2) depends on opentelemetry-exporter-otlp-proto-http (>=1.16.0,<1.17.0)
 and datacontract-cli[databricks,dbt] (0.10.1) depends on opentelemetry-exporter-otlp-proto-http (>=1.16.0,<1.17.0), if dbt-databricks (>=1.9,<1.9.2 || >1.9.2,<1.10) and datacontract-cli[databricks,dbt] (0.10.1 || 0.10.2 || 0.10.3 || 0.10.4 || 0.10.14 || 0.10.15 || 0.10.16) then opentelemetry-exporter-otlp-proto-http (>=1.16.0,<1.17.0).
(2) Because no versions of datacontract-cli match >0.10,<0.10.1 || >0.10.1,<0.10.2 || >0.10.2,<0.10.3 || >0.10.3,<0.10.4 || >0.10.4,<0.10.5 || >0.10.5,<0.10.6 || >0.10.6,<0.10.7 || >0.10.7,<0.10.8 || >0.10.8,<0.10.9 || >0.10.9,<0.10.10 || >0.10.10,<0.10.11 || >0.10.11,<0.10.12 || >0.10.12,<0.10.13 || >0.10.13,<0.10.14 || >0.10.14,<0.10.15 || >0.10.15,<0.10.16 || >0.10.16,<0.10.18 || >0.10.18,<0.11
 and datacontract-cli[databricks,dbt] (0.10.0) depends on opentelemetry-exporter-otlp-proto-http (>=1.16.0,<1.17.0), datacontract-cli[databricks,dbt] (>=0.10,<0.10.1 || >0.10.1,<0.10.2 || >0.10.2,<0.10.3 || >0.10.3,<0.10.4 || >0.10.4,<0.10.5 || >0.10.5,<0.10.6 || >0.10.6,<0.10.7 || >0.10.7,<0.10.8 || >0.10.8,<0.10.9 || >0.10.9,<0.10.10 || >0.10.10,<0.10.11 || >0.10.11,<0.10.12 || >0.10.12,<0.10.13 || >0.10.13,<0.10.14 || >0.10.14,<0.10.15 || >0.10.15,<0.10.16 || >0.10.16,<0.10.18 || >0.10.18,<0.11) requires opentelemetry-exporter-otlp-proto-http (>=1.16.0,<1.17.0).
    Thus, if dbt-databricks (>=1.9,<1.9.2 || >1.9.2,<1.10) and datacontract-cli[databricks,dbt] (>=0.10,<0.10.5 || >0.10.5,<0.10.6 || >0.10.6,<0.10.7 || >0.10.7,<0.10.8 || >0.10.8,<0.10.9 || >0.10.9,<0.10.10 || >0.10.10,<0.10.11 || >0.10.11,<0.10.12 || >0.10.12,<0.10.13 || >0.10.13,<0.10.18 || >0.10.18,<0.11) then opentelemetry-exporter-otlp-proto-http (>=1.16.0,<1.17.0).
    And because datacontract-cli[databricks,dbt] (0.10.13) depends on databricks-sql-connector (>=3.1.2,<3.5.0)
 and datacontract-cli[databricks,dbt] (0.10.12) depends on databricks-sql-connector (>=3.1.2,<3.4.0), if dbt-databricks (>=1.9,<1.9.2 || >1.9.2,<1.10) and datacontract-cli[databricks,dbt] (>=0.10,<0.10.5 || >0.10.5,<0.10.6 || >0.10.6,<0.10.7 || >0.10.7,<0.10.8 || >0.10.8,<0.10.9 || >0.10.9,<0.10.10 || >0.10.10,<0.10.11 || >0.10.11,<0.10.18 || >0.10.18,<0.11) then opentelemetry-exporter-otlp-proto-http (>=1.16.0,<1.17.0) or databricks-sql-connector (>=3.1.2,<3.5.0).
(3) So, because datacontract-cli[databricks,dbt] (0.10.11) depends on databricks-sql-connector (>=3.1.2,<3.4.0)
 and datacontract-cli[databricks,dbt] (0.10.10) depends on databricks-sql-connector (>=3.1.2,<3.3.0), if dbt-databricks (>=1.9,<1.9.2 || >1.9.2,<1.10) and datacontract-cli[databricks,dbt] (>=0.10,<0.10.5 || >0.10.5,<0.10.6 || >0.10.6,<0.10.7 || >0.10.7,<0.10.8 || >0.10.8,<0.10.9 || >0.10.9,<0.10.18 || >0.10.18,<0.11) then opentelemetry-exporter-otlp-proto-http (>=1.16.0,<1.17.0) or databricks-sql-connector (>=3.1.2,<3.5.0).

    Because datacontract-cli[databricks,dbt] (0.10.9) depends on databricks-sql-connector (>=3.1.2,<3.3.0)
 and datacontract-cli[databricks,dbt] (0.10.8) depends on databricks-sql-connector (>=3.1.2,<3.2.0), datacontract-cli[databricks,dbt] (0.10.8 || 0.10.9) requires databricks-sql-connector (>=3.1.2,<3.3.0).
    And because datacontract-cli[databricks,dbt] (0.10.7) depends on databricks-sql-connector (>=3.1.2,<3.2.0), datacontract-cli[databricks,dbt] (0.10.7 || 0.10.8 || 0.10.9) requires databricks-sql-connector (>=3.1.2,<3.3.0).
    And because datacontract-cli[databricks,dbt] (0.10.6) depends on databricks-sql-connector (>=3.1.2,<3.2.0)
 and datacontract-cli[databricks,dbt] (0.10.5) depends on databricks-sql-connector (>=3.1.2,<3.2.0), datacontract-cli[databricks,dbt] (0.10.5 || 0.10.6 || 0.10.7 || 0.10.8 || 0.10.9) requires databricks-sql-connector (>=3.1.2,<3.3.0).
(4) So, because if dbt-databricks (>=1.9,<1.9.2 || >1.9.2,<1.10) and datacontract-cli[databricks,dbt] (>=0.10,<0.10.5 || >0.10.5,<0.10.6 || >0.10.6,<0.10.7 || >0.10.7,<0.10.8 || >0.10.8,<0.10.9 || >0.10.9,<0.10.18 || >0.10.18,<0.11) then opentelemetry-exporter-otlp-proto-http (>=1.16.0,<1.17.0) or databricks-sql-connector (>=3.1.2,<3.5.0) (3), if dbt-databricks (>=1.9,<1.9.2 || >1.9.2,<1.10) and datacontract-cli[databricks,dbt] (>=0.10,<0.10.18 || >0.10.18,<0.11) then opentelemetry-exporter-otlp-proto-http (>=1.16.0,<1.17.0) or databricks-sql-connector (>=3.1.2,<3.5.0)

    Because no versions of dbt-databricks match >1.9,<1.9.1 || >1.9.1,<1.9.2 || >1.9.2,<1.10
 and dbt-databricks (1.9.1) depends on databricks-sql-connector (>=3.5.0,<4.0.0), dbt-databricks (>1.9,<1.9.2 || >1.9.2,<1.10) requires databricks-sql-connector (>=3.5.0,<4.0.0).
    And because dbt-databricks (1.9.0) depends on databricks-sql-connector (>=3.5.0,<4.0.0), dbt-databricks (>=1.9,<1.9.2 || >1.9.2,<1.10) requires databricks-sql-connector (>=3.5.0,<4.0.0).
(5) So, because if dbt-databricks (>=1.9,<1.9.2 || >1.9.2,<1.10) and datacontract-cli[databricks,dbt] (>=0.10,<0.10.18 || >0.10.18,<0.11) then opentelemetry-exporter-otlp-proto-http (>=1.16.0,<1.17.0) or databricks-sql-connector (>=3.1.2,<3.5.0) (4), if dbt-databricks (>=1.9,<1.9.2 || >1.9.2,<1.10) and datacontract-cli[databricks,dbt] (>=0.10,<0.10.18 || >0.10.18,<0.11) then opentelemetry-exporter-otlp-proto-http (>=1.16.0,<1.17.0)

    Because datacontract-cli[databricks,dbt] (0.10.15) depends on databricks-sdk (>=0.32.0,<0.39.0)
 and datacontract-cli[databricks,dbt] (0.10.14) depends on databricks-sdk (>=0.32.0,<0.36.0), datacontract-cli[databricks,dbt] (0.10.14 || 0.10.15) requires databricks-sdk (>=0.32.0,<0.39.0).
    And because datacontract-cli[databricks,dbt] (0.10.13) depends on databricks-sdk (>=0.32.0,<0.33.0), datacontract-cli[databricks,dbt] (0.10.13 || 0.10.14 || 0.10.15) requires databricks-sdk (>=0.32.0,<0.39.0).
    And because datacontract-cli[databricks,dbt] (0.10.12) depends on databricks-sql-connector (>=3.1.2,<3.4.0)
 and datacontract-cli[databricks,dbt] (0.10.11) depends on databricks-sql-connector (>=3.1.2,<3.4.0), datacontract-cli[databricks,dbt] (0.10.11 || 0.10.12 || 0.10.13 || 0.10.14 || 0.10.15) requires databricks-sdk (>=0.32.0,<0.39.0) or databricks-sql-connector (>=3.1.2,<3.4.0).
    And because datacontract-cli[databricks,dbt] (0.10.10) depends on databricks-sql-connector (>=3.1.2,<3.3.0)
 and datacontract-cli[databricks,dbt] (0.10.9) depends on databricks-sql-connector (>=3.1.2,<3.3.0), datacontract-cli[databricks,dbt] (0.10.9 || 0.10.10 || 0.10.11 || 0.10.12 || 0.10.13 || 0.10.14 || 0.10.15) requires databricks-sdk (>=0.32.0,<0.39.0) or databricks-sql-connector (>=3.1.2,<3.4.0).
    And because datacontract-cli[databricks,dbt] (0.10.8) depends on databricks-sql-connector (>=3.1.2,<3.2.0)
 and datacontract-cli[databricks,dbt] (0.10.7) depends on databricks-sql-connector (>=3.1.2,<3.2.0), datacontract-cli[databricks,dbt] (0.10.7 || 0.10.8 || 0.10.9 || 0.10.10 || 0.10.11 || 0.10.12 || 0.10.13 || 0.10.14 || 0.10.15) requires databricks-sdk (>=0.32.0,<0.39.0) or databricks-sql-connector (>=3.1.2,<3.4.0).
    And because datacontract-cli[databricks,dbt] (0.10.6) depends on databricks-sql-connector (>=3.1.2,<3.2.0)
 and datacontract-cli[databricks,dbt] (0.10.5) depends on databricks-sql-connector (>=3.1.2,<3.2.0), datacontract-cli[databricks,dbt] (0.10.5 || 0.10.6 || 0.10.7 || 0.10.8 || 0.10.9 || 0.10.10 || 0.10.11 || 0.10.12 || 0.10.13 || 0.10.14 || 0.10.15) requires databricks-sdk (>=0.32.0,<0.39.0) or databricks-sql-connector (>=3.1.2,<3.4.0).
    And because datacontract-cli[databricks,dbt] (0.10.4) depends on opentelemetry-exporter-otlp-proto-http (>=1.16.0,<1.17.0)
 and datacontract-cli[databricks,dbt] (0.10.3) depends on opentelemetry-exporter-otlp-proto-http (>=1.16.0,<1.17.0), datacontract-cli[databricks,dbt] (0.10.3 || 0.10.4 || 0.10.5 || 0.10.6 || 0.10.7 || 0.10.8 || 0.10.9 || 0.10.10 || 0.10.11 || 0.10.12 || 0.10.13 || 0.10.14 || 0.10.15) requires databricks-sdk (>=0.32.0,<0.39.0) or databricks-sql-connector (>=3.1.2,<3.4.0) or opentelemetry-exporter-otlp-proto-http (>=1.16.0,<1.17.0).
    And because datacontract-cli[databricks,dbt] (0.10.2) depends on opentelemetry-exporter-otlp-proto-http (>=1.16.0,<1.17.0)
 and datacontract-cli[databricks,dbt] (0.10.1) depends on opentelemetry-exporter-otlp-proto-http (>=1.16.0,<1.17.0), datacontract-cli[databricks,dbt] (0.10.1 || 0.10.2 || 0.10.3 || 0.10.4 || 0.10.5 || 0.10.6 || 0.10.7 || 0.10.8 || 0.10.9 || 0.10.10 || 0.10.11 || 0.10.12 || 0.10.13 || 0.10.14 || 0.10.15) requires databricks-sdk (>=0.32.0,<0.39.0) or databricks-sql-connector (>=3.1.2,<3.4.0) or opentelemetry-exporter-otlp-proto-http (>=1.16.0,<1.17.0).
    And because datacontract-cli[databricks,dbt] (>=0.10,<0.10.1 || >0.10.1,<0.10.2 || >0.10.2,<0.10.3 || >0.10.3,<0.10.4 || >0.10.4,<0.10.5 || >0.10.5,<0.10.6 || >0.10.6,<0.10.7 || >0.10.7,<0.10.8 || >0.10.8,<0.10.9 || >0.10.9,<0.10.10 || >0.10.10,<0.10.11 || >0.10.11,<0.10.12 || >0.10.12,<0.10.13 || >0.10.13,<0.10.14 || >0.10.14,<0.10.15 || >0.10.15,<0.10.16 || >0.10.16,<0.10.18 || >0.10.18,<0.11) requires opentelemetry-exporter-otlp-proto-http (>=1.16.0,<1.17.0) (2), datacontract-cli[databricks,dbt] (>=0.10,<0.10.16 || >0.10.16,<0.10.18 || >0.10.18,<0.11) requires databricks-sdk (>=0.32.0,<0.39.0) or databricks-sql-connector (>=3.1.2,<3.4.0) or opentelemetry-exporter-otlp-proto-http (>=1.16.0,<1.17.0).
    And because datacontract-cli[databricks,dbt] (0.10.16) depends on databricks-sdk (>=0.32.0,<0.39.0), datacontract-cli[databricks,dbt] (>=0.10,<0.10.18 || >0.10.18,<0.11) requires databricks-sdk (>=0.32.0,<0.39.0) or databricks-sql-connector (>=3.1.2,<3.4.0) or opentelemetry-exporter-otlp-proto-http (>=1.16.0,<1.17.0).
    And because dbt-databricks (1.9.2) depends on both databricks-sdk (0.17.0) and databricks-sql-connector (>=3.5.0,<4.0.0), if datacontract-cli[databricks,dbt] (>=0.10,<0.10.18 || >0.10.18,<0.11) and dbt-databricks (1.9.2) then opentelemetry-exporter-otlp-proto-http (>=1.16.0,<1.17.0).
(6) So, because if dbt-databricks (>=1.9,<1.9.2 || >1.9.2,<1.10) and datacontract-cli[databricks,dbt] (>=0.10,<0.10.18 || >0.10.18,<0.11) then opentelemetry-exporter-otlp-proto-http (>=1.16.0,<1.17.0) (5), if datacontract-cli[databricks,dbt] (>=0.10,<0.10.18 || >0.10.18,<0.11) and dbt-databricks (>=1.9,<1.10) then opentelemetry-exporter-otlp-proto-http (>=1.16.0,<1.17.0)

    Because no versions of soda-core-duckdb match >3.3.20,<3.3.21 || >3.3.21,<3.3.22 || >3.3.22,<3.4.0
 and soda-core-duckdb (3.3.21) depends on duckdb (1.0.0), soda-core-duckdb (>3.3.20,<3.3.22 || >3.3.22,<3.4.0) requires duckdb (1.0.0).
    And because soda-core-duckdb (3.3.22) depends on duckdb (1.0.0), soda-core-duckdb (>3.3.20,<3.4.0) requires duckdb (1.0.0).
    And because datacontract-cli[databricks,dbt] (0.10.18) depends on both duckdb (1.1.2) and soda-core-duckdb (>=3.3.20,<3.4.0), datacontract-cli[databricks,dbt] (0.10.18) requires soda-core-duckdb (3.3.20).
    And because if datacontract-cli[databricks,dbt] (>=0.10,<0.10.18 || >0.10.18,<0.11) and dbt-databricks (>=1.9,<1.10) then opentelemetry-exporter-otlp-proto-http (>=1.16.0,<1.17.0) (6), if dbt-databricks (>=1.9,<1.10) and datacontract-cli[databricks,dbt] (>=0.10,<0.11) then opentelemetry-exporter-otlp-proto-http (>=1.16.0,<1.17.0) or soda-core-duckdb (3.3.20)
    And because soda-core-duckdb (3.3.20) depends on soda-core (3.3.20), if dbt-databricks (>=1.9,<1.10) and datacontract-cli[databricks,dbt] (>=0.10,<0.11) then opentelemetry-exporter-otlp-proto-http (>=1.16.0,<1.17.0) or soda-core (3.3.20).
    And because soda-core (3.3.20) depends on opentelemetry-exporter-otlp-proto-http (>=1.16.0,<1.23.0)
 and no versions of opentelemetry-exporter-otlp-proto-http match >1.16.0,<1.17.0 || >1.17.0,<1.18.0 || >1.18.0,<1.19.0 || >1.19.0,<1.20.0 || >1.20.0,<1.21.0 || >1.21.0,<1.22.0 || >1.22.0,<1.23.0, if dbt-databricks (>=1.9,<1.10) and datacontract-cli[databricks,dbt] (>=0.10,<0.11) then opentelemetry-exporter-otlp-proto-http (1.16.0 || 1.17.0 || 1.18.0 || 1.19.0 || 1.20.0 || 1.21.0 || 1.22.0).
    And because opentelemetry-exporter-otlp-proto-http (1.16.0) depends on opentelemetry-proto (1.16.0)
 and opentelemetry-proto (1.16.0) depends on protobuf (>=3.19,<5.0), if dbt-databricks (>=1.9,<1.10) and datacontract-cli[databricks,dbt] (>=0.10,<0.11) then opentelemetry-exporter-otlp-proto-http (1.17.0 || 1.18.0 || 1.19.0 || 1.20.0 || 1.21.0 || 1.22.0) or protobuf (>=3.19,<5.0).
    And because opentelemetry-exporter-otlp-proto-http (1.17.0) depends on opentelemetry-proto (1.17.0)
 and opentelemetry-proto (1.17.0) depends on protobuf (>=3.19,<5.0), if dbt-databricks (>=1.9,<1.10) and datacontract-cli[databricks,dbt] (>=0.10,<0.11) then protobuf (>=3.19,<5.0) or opentelemetry-exporter-otlp-proto-http (1.18.0 || 1.19.0 || 1.20.0 || 1.21.0 || 1.22.0).
    And because opentelemetry-exporter-otlp-proto-http (1.18.0) depends on opentelemetry-proto (1.18.0)
 and opentelemetry-proto (1.18.0) depends on protobuf (>=3.19,<5.0), if dbt-databricks (>=1.9,<1.10) and datacontract-cli[databricks,dbt] (>=0.10,<0.11) then protobuf (>=3.19,<5.0) or opentelemetry-exporter-otlp-proto-http (1.19.0 || 1.20.0 || 1.21.0 || 1.22.0).
    And because opentelemetry-exporter-otlp-proto-http (1.19.0) depends on opentelemetry-proto (1.19.0)
 and opentelemetry-proto (1.19.0) depends on protobuf (>=3.19,<5.0), if dbt-databricks (>=1.9,<1.10) and datacontract-cli[databricks,dbt] (>=0.10,<0.11) then protobuf (>=3.19,<5.0) or opentelemetry-exporter-otlp-proto-http (1.20.0 || 1.21.0 || 1.22.0).
    And because opentelemetry-exporter-otlp-proto-http (1.20.0) depends on opentelemetry-proto (1.20.0)
 and opentelemetry-proto (1.20.0) depends on protobuf (>=3.19,<5.0), if dbt-databricks (>=1.9,<1.10) and datacontract-cli[databricks,dbt] (>=0.10,<0.11) then protobuf (>=3.19,<5.0) or opentelemetry-exporter-otlp-proto-http (1.21.0 || 1.22.0).
    And because opentelemetry-exporter-otlp-proto-http (1.21.0) depends on opentelemetry-proto (1.21.0)
 and opentelemetry-proto (1.21.0) depends on protobuf (>=3.19,<5.0), if dbt-databricks (>=1.9,<1.10) and datacontract-cli[databricks,dbt] (>=0.10,<0.11) then protobuf (>=3.19,<5.0) or opentelemetry-exporter-otlp-proto-http (1.22.0).
(7) So, because opentelemetry-exporter-otlp-proto-http (1.22.0) depends on opentelemetry-proto (1.22.0)
 and opentelemetry-proto (1.22.0) depends on protobuf (>=3.19,<5.0), if dbt-databricks (>=1.9,<1.10) and datacontract-cli[databricks,dbt] (>=0.10,<0.11) then protobuf (>=3.19,<5.0).

    Because no versions of dbt-core match >1.9,<1.9.1 || >1.9.1,<1.10
 and dbt-core (1.9.1) depends on protobuf (>=5.0,<6.0), dbt-core (>1.9,<1.10) requires protobuf (>=5.0,<6.0).
    And because dbt-core (1.9.0) depends on protobuf (>=5.0,<6.0), dbt-core (>=1.9,<1.10) requires protobuf (>=5.0,<6.0).
    And because if dbt-databricks (>=1.9,<1.10) and datacontract-cli[databricks,dbt] (>=0.10,<0.11) then protobuf (>=3.19,<5.0) (7), one of dbt-databricks (>=1.9,<1.10) or datacontract-cli[databricks,dbt] (>=0.10,<0.11) or dbt-core (>=1.9,<1.10) must be false
    And because dq-dbt-template depends on dbt-core (~1.9), dbt-databricks (>=1.9,<1.10) is incompatible with datacontract-cli[databricks,dbt] (>=0.10,<0.11).
    So, because dq-dbt-template depends on both dbt-databricks (~1.9) and datacontract-cli[databricks,dbt] (~0.10), version solving failed.

I havent combed through the message yet but is this something that is on your radar ?
It seems like an imcompatibility between the CLI and dbt-databricks based on a pydantic/protobof version ?

Maybe linked to : databricks/dbt-databricks#872 or #590 ?

[anismikou]

Apparently fixed with 0.10.20, i'll close the issue