MetricSign
EN|NLRequest Access
Medium severityconfiguration

Power BI Refresh Error:
PackageVersionMismatch

What does this error mean?

dbt detected a conflict between the installed package versions and the version constraints declared in packages.yml. This can also surface as a conflict between a package's required dbt version range and the dbt version installed in the environment. The run fails at project load time before any models execute.

Common causes

  • 1Two packages both depend on a third package but declare incompatible version ranges — dbt cannot satisfy both constraints simultaneously
  • 2The installed version of dbt-core is outside the range required by a package listed in packages.yml
  • 3packages.yml pins a specific package version that has been unpublished from the dbt Hub registry
  • 4A dbt Cloud environment was upgraded to a newer dbt version but the packages.yml still pins packages that are incompatible with the new version
  • 5`dbt deps` was not re-run after changing packages.yml, leaving the installed packages out of sync with the declared constraints

How to fix it

  1. 1Run `dbt deps` to reinstall all packages according to the current packages.yml constraints — this resolves many stale installation issues.
  2. 2Check the error output for the specific package and version constraint that conflicts.
  3. 3Review the release notes of the conflicting package to find the version compatible with your current dbt version.
  4. 4If two packages conflict with each other, open the respective GitHub repos to check whether a fix exists or whether you need to pin specific versions.
  5. 5In dbt Cloud, verify the environment's dbt version under Account Settings → Environments and align packages.yml to that version.

Frequently asked questions

How do I find which packages are conflicting?

The `dbt deps` output lists the resolution attempt and names the conflicting packages and their version constraints. Run `dbt deps` locally with the `--debug` flag for full detail.

Can I pin package versions to avoid future conflicts?

Yes — use `version: '1.2.3'` in packages.yml instead of a range. This prevents automatic upgrades but protects against surprise conflicts. Test version upgrades in a development environment before updating the production pin.

Other configuration errors