feat: widen dbt-core compatibility range #5211
Merged
Conversation
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
![github-advanced-security[bot]](https://avatars.githubusercontent.com/in/57789?s=60&v=4){kind=small}
eakmanrq
force-pushed
the
eakmanrq/widen_dbt_core_compat_range
branch
25 times, most recently
from
f588c44 to
c0c7b25
Compare
erindru
approved these changes
Aug 26, 2025
eakmanrq
force-pushed
the
eakmanrq/widen_dbt_core_compat_range
branch
from
c0c7b25 to
50cb8c7
Compare
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Widens the core compatibility range by addresses a few gaps where we weren't currently compatible and then adding CI checks to run fast tests and load dbt-sushi across the latest bugfix release of each dbt version.
One key part of this change is making sure that any fast dbt test we have doesn't require a sushi context or more generally DuckDB adapter information. This is because the DuckDB dbt-adapter for old dbt releases changed how catalogs are determined that affects these tests. Therefore we currently just run this slow tests on later versions. In tests where we needed some adapter to do things like loading with the Manifest, I used a Postgres connection instead since that is stable across the dbt releases.