0.18.0 compatibility #26
Conversation
| @@ -1,3 +1,3 @@ | |||
| packages: | |||
| - package: fishtown-analytics/dbt_utils | |||
| version: [">=0.4.0", "<0.6.0"] | |||
There was a problem hiding this comment.
I guess this would work with earlier versions, but would return deprecation warnings. I'd prefer to be tightly scoped here instead
There was a problem hiding this comment.
Agreed! If we're upgrading a package to use functionality only available in dbt >= 0.18.0 (dispatch), I think we should also scope it to require utils >= 0.6.0.
If a package does not require net-new functionality, though (stitch_utils, segment, logging, redshift), I don't know that we need to raise the lower bounds + cut a minor version?
| @@ -1,3 +1,3 @@ | |||
| packages: | |||
| - package: fishtown-analytics/dbt_utils | |||
| version: [">=0.4.0", "<0.6.0"] | |||
There was a problem hiding this comment.
Agreed! If we're upgrading a package to use functionality only available in dbt >= 0.18.0 (dispatch), I think we should also scope it to require utils >= 0.6.0.
If a package does not require net-new functionality, though (stitch_utils, segment, logging, redshift), I don't know that we need to raise the lower bounds + cut a minor version?
Description & motivation
0.18.0 release
Checklist