Releases: dbt-labs/dbt-utils
Release list
dbt-utils 0.6.4
dbt-utils v0.6.4
This is a patch release with no breaking changes.
Instead we made lots of teeny, tiny, under-the-hood improvements, mostly to help out adapter maintainers and ourselves as utils maintainers :)
Fixes
- Fix
insert_by_periodto supportdbt v0.19.0, with backwards compatibility for earlier versions (#319, #320)
Under the hood
- Speed up CI via threads, workflows (#315, #316)
- Fix
equalitytest when used with ephemeral models + explicit column set (#321) - Fix
get_query_results_as_dictintegration test with consistent ordering (#322) - All macros are now properly dispatched, making it possible for non-core adapters to implement a shim package for dbt-utils (#312) Thanks @chaerinlee1 and @swanderz
- Small, non-breaking changes to accommodate TSQL (can't group by column number references, no real TRUE/FALSE values, aggregation CTEs need named columns) (#310) Thanks @swanderz
- Make
get_relations_by_patternandget_relations_by_prefixmore powerful by returningrelation.type(#323)
dbt-utils 0.6.3
This is a patch release with no substantive changes.
Quality of life
- Bump
require-dbt-version: [">=0.18.0", "<0.20.0"]. This package will support dbt v0.19.0 without any breaking changes. - Documentation updates (readme + issue/PR templates)
dbt-utils 0.6.2
Another day, another bugfix release. Happens to the best of us!
This release fixes a regression that was introduced in 0.6.0.
Fixes
- Fix the logic in
get_tables_by_pattern_sqlto ensure non-default arguments are respected (#279)
dbt-utils v0.6.1
dbt-utils v0.6.0
dbt-utils v0.6.0
Thanks to our contributors @tayloramurphy and @JoshuaHuntley
Breaking changes
- 🚨 dbt v0.18.0 or greater is required for this release. If you are not ready to upgrade, consider using a previous release of this package
- 🚨 The
get_tables_by_prefix,union_tablesandget_tables_by_patternmacros have been removed
Migration instructions
Migration instructions can be found in the Changelog
Features
- Switch usage of
adapter_macrotoadapter.dispatch, and definedbt_utils_dispatch_list,
enabling users of community-supported database plugins to add or override macro implementations
specific to their database (#267) - Use
add_ephemeral_prefixinstead of hard-coding a string literal, to support
database adapters that use different prefixes (#267) - Implement a quote_columns argument in the unique_combination_of_columns schema test (#270 @JoshuaHuntley)
Quality of life
dbt-utils 0.5.1
This is a bug fix release
Quality of life
- Improve release process, and fix tests (#251)
- Make deprecation warnings more useful (#258 @tayloramurphy 🙌 )
dbt-utils 0.5.0
New functionality has been included in this release!
Features
- Throw a nice error when trying to use a macro that requires the information schema on an ephemeral model (#243) (🚨 may cause previously silent errors to no longer be silent)
- Add
unique_whereandnot_null_whererelationship tests (#250 @MartinGuindon) - Add
distinctargument to thepivotmacro (#248 @DylanBaker) - Add
get_relations_by_patternmacro (#220 @JDW818)
Fixes
- Fix incorrect test behavior for the
unpivotmacro (#249 @avishalom)
Quality of life
- Replace BigQuery
__TABLES_SUMMARY__withINFORMATION_SCHEMA(#247 @preston-hf)
dbt-utils v0.4.1
0.4.0
🚨 This release contains a breaking change
This package now requires dbt >=0.17.0
Features
- v0.17.0 compatibility (#235 @DylanBaker) (🚨 breaking change)
Fixes
Under the hood
- Use python v3.6.3 for integration tests (#233)
- Add GitHub templates (#217 #222)
- Update star macro to use
adapter.quote(#205 @bjgbeelen) - Simplify running the integration tests (#211 @bjgbeelen)
- Update test scripts to ensure existing profiles are not removed (#231)
🙏 Thank you to all our contributors!
0.3.0
🚨 This release contains a breaking change
This package now requires dbt >=0.15.1
Fixes
- The
surrogate_keymacro now takes a list instead multiple arguments (#197 @DylanBaker).
-- before
{{ dbt_utils.surrogate_key('field_a', 'field_b') }}
-- after
{{ dbt_utils.surrogate_key(['field_a', 'field_b']) }}Support for multiple arguments will be removed in a future release.
- Documentation improvements (#201 @CaptainEli , #203 @avishalom)
- Whitespace cleanups (#196 / #199 @Limess)
🙏 Thank you to all our contributors!