You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
{{ message }}
This repository was archived by the owner on Dec 4, 2024. It is now read-only.
This package has a dependency on dbt_utils that restricts its version to <0.9.0. dbt_utils recently released compatibility release v0.9.x in preparation for their v1.0.0 release. It would be nice to be able to test against that release in preparation for the 1.0 release. Slack announcement
Describe alternatives you've considered
A clear and concise description of any alternative solutions or features you've considered.
I suppose it's not mission critical to be compatible with v0.9.x, but there are some breaking changes in v1.0 (they moved certain macros into dbt-core) that it would be nice to prepare for.
Additional context
Is this feature database-specific? Which database(s) is/are relevant? Please include any other relevant context here.
Who will this benefit?
What kind of use case will this feature be useful for? Please be specific and provide examples, this will help us prioritize properly.
dbt_utils is one of the most popular dbt packages. It seems compatibly with that package is more or less a necessity.
Are you interested in contributing this feature?
Perhaps. I just don't have the time at the moment.
The text was updated successfully, but these errors were encountered:
Describe the feature
This package has a dependency on dbt_utils that restricts its version to <0.9.0. dbt_utils recently released compatibility release v0.9.x in preparation for their v1.0.0 release. It would be nice to be able to test against that release in preparation for the 1.0 release. Slack announcement
Describe alternatives you've considered
A clear and concise description of any alternative solutions or features you've considered.
I suppose it's not mission critical to be compatible with v0.9.x, but there are some breaking changes in v1.0 (they moved certain macros into dbt-core) that it would be nice to prepare for.
Additional context
Is this feature database-specific? Which database(s) is/are relevant? Please include any other relevant context here.
Who will this benefit?
What kind of use case will this feature be useful for? Please be specific and provide examples, this will help us prioritize properly.
dbt_utils is one of the most popular dbt packages. It seems compatibly with that package is more or less a necessity.
Are you interested in contributing this feature?
Perhaps. I just don't have the time at the moment.
The text was updated successfully, but these errors were encountered: