What causes PackageVersionConstraintConflict?

Two packages both depend on dbt-utils but specify non-overlapping version ranges. A package specifies a require-dbt-version constraint that excludes the current dbt version. Upgrading one package to a newer version introduced a transitive dependency conflict with another installed package. packages.yml pins a package to an old version that is incompatible with the current dbt major version

How do I fix PackageVersionConstraintConflict?

Step 1: Read the dbt deps error output — it names the conflicting packages and their version constraints.. Step 2: Check each conflicting package's changelog for its dbt version and dependency requirements.. Step 3: Update all conflicting packages to versions with overlapping dependency ranges.. Step 4: If the conflict is between a package and the dbt version, upgrade dbt or pin the package to an older compatible version.. Step 5: Run 'dbt deps' after changes and confirm no conflicts remain before committing.

Medium severityconfiguration

Power BI Refresh Error:
PackageVersionConstraintConflict

What does this error mean?

The 'dbt deps' command failed because two or more packages in packages.yml require incompatible versions of the same dependency, or a package requires a dbt version range that does not match the installed dbt version.

Common causes

1Two packages both depend on dbt-utils but specify non-overlapping version ranges
2A package specifies a require-dbt-version constraint that excludes the current dbt version
3Upgrading one package to a newer version introduced a transitive dependency conflict with another installed package
4packages.yml pins a package to an old version that is incompatible with the current dbt major version

How to fix it

1Step 1: Read the dbt deps error output — it names the conflicting packages and their version constraints.
2Step 2: Check each conflicting package's changelog for its dbt version and dependency requirements.
3Step 3: Update all conflicting packages to versions with overlapping dependency ranges.
4Step 4: If the conflict is between a package and the dbt version, upgrade dbt or pin the package to an older compatible version.
5Step 5: Run 'dbt deps' after changes and confirm no conflicts remain before committing.

Frequently asked questions

How do I see the full dependency tree for my dbt packages?

After running dbt deps successfully, check the package-lock.yml file generated in the project root. It lists the resolved version of every package and sub-dependency. If dbt deps fails, the error output describes the conflicting constraints.

Is there a way to override a transitive package dependency version?

Yes. Add the conflicting transitive dependency explicitly to your packages.yml with a version range that satisfies all direct dependencies. This overrides the auto-resolved version and can resolve many constraint conflicts.