Maybe? Move dbt-date and dbt-expectations dependencies here about dbt_fivetran_utils HOT 2 CLOSED

Another major con I see with this approach is that for every minor release of dbt-date or expectations we would also need to create a minor update to fivetran_utils. This means that 0.4.x would need to become 0.5.x after the dbt-date/expectations update. 😱 This would mean we would then need to update every source package to point to a new version of fivetran_utils. Unfortunately, this would explode the LOE from updating the dependency in one package, to needing to update nearly all the packages.

We discussed in standup yesterday that the best solution would be to ideally automate this update process. Primarily focusing on the cascading nature where the breaking change in the source will need to be breaking in the downstream dependent packages. In order to do this, we will need to apply this update manually but make note of the parts that may be automated so we can then streamline this effort when it happens in the future.

from dbt_fivetran_utils.

Closing out this feature request as previously discussed it would likely not be a great idea to include another dependency within this project.

from dbt_fivetran_utils.