Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Jump to bottom

Bump the pip group across 1 directory with 4 updates #61

Open
wants to merge 1 commit into
base: main
Choose a base branch
from
Open

Bump the pip group across 1 directory with 4 updates #61

wants to merge 1 commit into from

Conversation

dependabot[bot]
Copy link
Contributor

@dependabot dependabot bot commented on behalf of github Dec 23, 2024

Bumps the pip group with 4 updates in the / directory: dbt-oracle, dbt-core, sqlfluff and sqlfluff-templater-dbt.

Updates dbt-oracle from 1.8.3 to 1.8.4

Release notes

Sourced from dbt-oracle's releases.

v1.8.4

This release has the following bug fixes and updates

  • Fixes #158
  • Upgrades driver to 2.5.1
  • Dropped support for Python 3.8
  • Use timestamp(9) in dbt snapshots for dbt_valid_to column
Commits

Updates dbt-core from 1.8.8 to 1.9.1

Release notes

Sourced from dbt-core's releases.

dbt-core v1.9.1

dbt-core 1.9.1 - December 16, 2024

Fixes

  • update adapter version messages (#10230)
  • Fix debug log messages for microbatch batch execution information (#11111)
  • Fix running of extra "last" batch when there is only one batch (#11112)
  • Fix interpretation of PartialSuccess to result in non-zero exit code (#11114)
  • Warn about invalid usages of concurrent_batches config (#11122)

Contributors

dbt-core v1.9.0

dbt-core 1.9.0 - Dr. Susan La Flesche Picotte (December 09, 2024)

Breaking Changes

  • Fix changing the current working directory when using dpt deps, clean and init. (#8997)

Features

  • Parseable JSON and text output in quiet mode for dbt show and dbt compile (#9840)
  • serialize inferred primary key (#9824)
  • Add unit_test: selection method (#10053)
  • Maximally parallelize dbt clone in clone command" (#7914)
  • Add --host flag to dbt docs serve, defaulting to '127.0.0.1' (#10229)
  • Update data_test to accept arbitrary config options (#10197)
  • add pre_model and post_model hook calls to data and unit tests to be able to provide extra config options (#10198)
  • add --empty value to jinja context as flags.EMPTY (#10317)
  • Warning message for snapshot timestamp data types (#10234)
  • Support cumulative_type_params & sub-daily granularities in semantic manifest. (#10360)
  • Add time_granularity to metric spec. (#10376)
  • Support standard schema/database fields for snapshots (#10301)
  • Support ref and source in foreign key constraint expressions, bump dbt-common minimum to 1.6 (#8062)
  • Support new semantic layer time spine configs to enable sub-daily granularity. (#10475)
  • Add order_by and limit fields to saved queries. (#10531)
  • Add support for behavior flags (#10618)
  • Enable --resource-type and --exclude-resource-type CLI flags and environment variables for dbt test (#10656)
  • Allow configuring snapshot column names (#10185)
  • Add custom_granularities to YAML spec for time spines. (#9265)
  • Add basic functionality for creating microbatch incremental models (#9490, #10635, #10637, #10638, #10636, #10662, #10639)
  • Execute microbatch models in batches (#10700)
  • Create 'skip_nodes_if_on_run_start_fails' behavior change flag (#7387)
  • Allow snapshots to be defined in YAML. (#10246)
  • Write microbatch compiled/run targets to separate files, one per batch (#10714)
  • Track incremental_strategy as part of model_run tracking event (#10761)
  • Support required 'begin' config for microbatch models (#10701)
  • Parse-time validation of microbatch configs: require event_time, batch_size, lookback and validate input event_time (#10709)

... (truncated)

Changelog

Sourced from dbt-core's changelog.

dbt-core 1.9.1 - December 16, 2024

Fixes

  • update adapter version messages (#10230)
  • Fix debug log messages for microbatch batch execution information (#11111)
  • Fix running of extra "last" batch when there is only one batch (#11112)
  • Fix interpretation of PartialSuccess to result in non-zero exit code (#11114)
  • Warn about invalid usages of concurrent_batches config (#11122)

Contributors

dbt-core 1.9.0 - December 09, 2024

Breaking Changes

  • Fix changing the current working directory when using dpt deps, clean and init. (#8997)

Features

  • Parseable JSON and text output in quiet mode for dbt show and dbt compile (#9840)
  • serialize inferred primary key (#9824)
  • Add unit_test: selection method (#10053)
  • Maximally parallelize dbt clone in clone command" (#7914)
  • Add --host flag to dbt docs serve, defaulting to '127.0.0.1' (#10229)
  • Update data_test to accept arbitrary config options (#10197)
  • add pre_model and post_model hook calls to data and unit tests to be able to provide extra config options (#10198)
  • add --empty value to jinja context as flags.EMPTY (#10317)
  • Warning message for snapshot timestamp data types (#10234)
  • Support cumulative_type_params & sub-daily granularities in semantic manifest. (#10360)
  • Add time_granularity to metric spec. (#10376)
  • Support standard schema/database fields for snapshots (#10301)
  • Support ref and source in foreign key constraint expressions, bump dbt-common minimum to 1.6 (#8062)
  • Support new semantic layer time spine configs to enable sub-daily granularity. (#10475)
  • Add order_by and limit fields to saved queries. (#10531)
  • Add support for behavior flags (#10618)
  • Enable --resource-type and --exclude-resource-type CLI flags and environment variables for dbt test (#10656)
  • Allow configuring snapshot column names (#10185)
  • Add custom_granularities to YAML spec for time spines. (#9265)
  • Add basic functionality for creating microbatch incremental models (#9490, #10635, #10637, #10638, #10636, #10662, #10639)
  • Execute microbatch models in batches (#10700)
  • Create 'skip_nodes_if_on_run_start_fails' behavior change flag (#7387)
  • Allow snapshots to be defined in YAML. (#10246)
  • Write microbatch compiled/run targets to separate files, one per batch (#10714)
  • Track incremental_strategy as part of model_run tracking event (#10761)
  • Support required 'begin' config for microbatch models (#10701)
  • Parse-time validation of microbatch configs: require event_time, batch_size, lookback and validate input event_time (#10709)
  • Added the --inline-direct parameter to 'dbt show' (#10770)

... (truncated)

Commits
  • cffe8a3 Bumping version to 1.9.1 and generate changelog
  • 7fdd92f Warn if concurrent_batches config is set to True, but the available adapt...
  • dbd8ef3 update adapter version messages (#10919) (#11131)
  • ff50d1d fix MicrobatchExecutionDebug message (#11071) (#11120)
  • f7ab487 Fix microbatch model PartialSuccess status to result in non-zero exit code ...
  • 92a5548 Fix erroneous additional batch execution (#11113) (#11117)
  • df2dd6d [Automated] Merged prep-release/1.9.0_12240985734 into target 1.9.latest duri...
  • 26ed99e Bumping version to 1.9.0 and generate changelog
  • 9f5f002 Microbatch first last batch serial (#11072) (#11107)
  • 4e74e69 Implement partial parsing for singular data tests configs in yaml files (#111...
  • Additional commits viewable in compare view

Updates sqlfluff from 3.2.5 to 3.3.0

Release notes

Sourced from sqlfluff's releases.

[3.3.0] - 2024-12-10

Highlights

This release brings a few more significant changes. Especially given the introduction of several new rules, we highly recommend testing this release on your project before upgrading to make sure they are configured appropriately for your project style guide. As always, we have tried to make sure that the defaults for all new rules are both widely applicable, and fairly light touch. While all have been tested on some existing larger codebases which the maintainers have access to - do still report any bugs you might find on GitHub in the usual manner.

  • We've dropped the appdirs package as a dependency (as an abandoned project) and instead added platformdirs instead. Users should not notice any functionality changes beyond the different dependency.
  • TWO new dialects: Impala and StarRocks.
  • FIVE new rules:
    • AM08 (ambiguous.join_condition), which detects JOIN clauses without conditions (i.e. without an ON or USING clause). These are often typos and can result in significant row count increases if unintended.
    • CV12 (convention.join_condition), which is related to AM08 and detects cases where users have used a WHERE clause instead of a JOIN ... ON ... clause to do their join conditions. The join condition is a form of metadata and should communicate to the end user how the table should be joined. By mixing this information into the WHERE clause it makes the SQL harder to understand.
    • LT14 (layout.keyword_newline), which allows certain keywords to trigger line breaks in queries. Primarily this forces the main SELECT statement clauses like WHERE, GROUP BY etc. onto new lines. This rule has been designed to be highly configurable, but with sensible light-touch defaults. Check out the docs to adapt it to the conventions of your project.
    • ST10 (structure.constant_expression), some SQL users include redundant expressions in their code (e.g. WHERE tbl.col = tbl.col). These conditions always evaluate to a constant outcome (i.e. always evaluate as TRUE or FALSE) as so add no functionality or meaning to the query. This rule catches them.
    • ST11 (structure.unused_join), which detects unused joins in SQL statements, and is designed to catch tables that were once used, but where the column references have since been removed and now the table is unnecessary.

Beyond these changes, we've seen a whole host of dialect improvements to almost all of the supported dialects and several bugfixes which are combined into this release.

We also welcome TWELVE new contributors to the project in this release. Thanks to all of them for their hard work 🚀🏆🚀.

What’s Changed

... (truncated)

Changelog

Sourced from sqlfluff's changelog.

[3.3.0] - 2024-12-10

Highlights

This release brings a few more significant changes. Especially given the introduction of several new rules, we highly recommend testing this release on your project before upgrading to make sure they are configured appropriately for your project style guide. As always, we have tried to make sure that the defaults for all new rules are both widely applicable, and fairly light touch. While all have been tested on some existing larger codebases which the maintainers have access to - do still report any bugs you might find on GitHub in the usual manner.

  • We've dropped the appdirs package as a dependency (as an abandoned project) and instead added platformdirs instead. Users should not notice any functionality changes beyond the different dependency.
  • TWO new dialects: Impala and StarRocks.
  • FIVE new rules:
    • AM08 (ambiguous.join_condition), which detects JOIN clauses without conditions (i.e. without an ON or USING clause). These are often typos and can result in significant row count increases if unintended.
    • CV12 (convention.join_condition), which is related to AM08 and detects cases where users have used a WHERE clause instead of a JOIN ... ON ... clause to do their join conditions. The join condition is a form of metadata and should communicate to the end user how the table should be joined. By mixing this information into the WHERE clause it makes the SQL harder to understand.
    • LT14 (layout.keyword_newline), which allows certain keywords to trigger line breaks in queries. Primarily this forces the main SELECT statement clauses like WHERE, GROUP BY etc. onto new lines. This rule has been designed to be highly configurable, but with sensible light-touch defaults. Check out the docs to adapt it to the conventions of your project.
    • ST10 (structure.constant_expression), some SQL users include redundant expressions in their code (e.g. WHERE tbl.col = tbl.col). These conditions always evaluate to a constant outcome (i.e. always evaluate as TRUE or FALSE) as so add no functionality or meaning to the query. This rule catches them.
    • ST11 (structure.unused_join), which detects unused joins in SQL statements, and is designed to catch tables that were once used, but where the column references have since been removed and now the table is unnecessary.

Beyond these changes, we've seen a whole host of dialect improvements to almost all of the supported dialects and several bugfixes which are combined into this release.

We also welcome TWELVE new contributors to the project in this release. Thanks to all of them for their hard work 🚀🏆🚀.

What’s Changed

... (truncated)

Commits

Updates sqlfluff-templater-dbt from 3.2.5 to 3.3.0

Release notes

Sourced from sqlfluff-templater-dbt's releases.

[3.3.0] - 2024-12-10

Highlights

This release brings a few more significant changes. Especially given the introduction of several new rules, we highly recommend testing this release on your project before upgrading to make sure they are configured appropriately for your project style guide. As always, we have tried to make sure that the defaults for all new rules are both widely applicable, and fairly light touch. While all have been tested on some existing larger codebases which the maintainers have access to - do still report any bugs you might find on GitHub in the usual manner.

  • We've dropped the appdirs package as a dependency (as an abandoned project) and instead added platformdirs instead. Users should not notice any functionality changes beyond the different dependency.
  • TWO new dialects: Impala and StarRocks.
  • FIVE new rules:
    • AM08 (ambiguous.join_condition), which detects JOIN clauses without conditions (i.e. without an ON or USING clause). These are often typos and can result in significant row count increases if unintended.
    • CV12 (convention.join_condition), which is related to AM08 and detects cases where users have used a WHERE clause instead of a JOIN ... ON ... clause to do their join conditions. The join condition is a form of metadata and should communicate to the end user how the table should be joined. By mixing this information into the WHERE clause it makes the SQL harder to understand.
    • LT14 (layout.keyword_newline), which allows certain keywords to trigger line breaks in queries. Primarily this forces the main SELECT statement clauses like WHERE, GROUP BY etc. onto new lines. This rule has been designed to be highly configurable, but with sensible light-touch defaults. Check out the docs to adapt it to the conventions of your project.
    • ST10 (structure.constant_expression), some SQL users include redundant expressions in their code (e.g. WHERE tbl.col = tbl.col). These conditions always evaluate to a constant outcome (i.e. always evaluate as TRUE or FALSE) as so add no functionality or meaning to the query. This rule catches them.
    • ST11 (structure.unused_join), which detects unused joins in SQL statements, and is designed to catch tables that were once used, but where the column references have since been removed and now the table is unnecessary.

Beyond these changes, we've seen a whole host of dialect improvements to almost all of the supported dialects and several bugfixes which are combined into this release.

We also welcome TWELVE new contributors to the project in this release. Thanks to all of them for their hard work 🚀🏆🚀.

What’s Changed

... (truncated)

Changelog

Sourced from sqlfluff-templater-dbt's changelog.

[3.3.0] - 2024-12-10

Highlights

This release brings a few more significant changes. Especially given the introduction of several new rules, we highly recommend testing this release on your project before upgrading to make sure they are configured appropriately for your project style guide. As always, we have tried to make sure that the defaults for all new rules are both widely applicable, and fairly light touch. While all have been tested on some existing larger codebases which the maintainers have access to - do still report any bugs you might find on GitHub in the usual manner.

  • We've dropped the appdirs package as a dependency (as an abandoned project) and instead added platformdirs instead. Users should not notice any functionality changes beyond the different dependency.
  • TWO new dialects: Impala and StarRocks.
  • FIVE new rules:
    • AM08 (ambiguous.join_condition), which detects JOIN clauses without conditions (i.e. without an ON or USING clause). These are often typos and can result in significant row count increases if unintended.
    • CV12 (convention.join_condition), which is related to AM08 and detects cases where users have used a WHERE clause instead of a JOIN ... ON ... clause to do their join conditions. The join condition is a form of metadata and should communicate to the end user how the table should be joined. By mixing this information into the WHERE clause it makes the SQL harder to understand.
    • LT14 (layout.keyword_newline), which allows certain keywords to trigger line breaks in queries. Primarily this forces the main SELECT statement clauses like WHERE, GROUP BY etc. onto new lines. This rule has been designed to be highly configurable, but with sensible light-touch defaults. Check out the docs to adapt it to the conventions of your project.
    • ST10 (structure.constant_expression), some SQL users include redundant expressions in their code (e.g. WHERE tbl.col = tbl.col). These conditions always evaluate to a constant outcome (i.e. always evaluate as TRUE or FALSE) as so add no functionality or meaning to the query. This rule catches them.
    • ST11 (structure.unused_join), which detects unused joins in SQL statements, and is designed to catch tables that were once used, but where the column references have since been removed and now the table is unnecessary.

Beyond these changes, we've seen a whole host of dialect improvements to almost all of the supported dialects and several bugfixes which are combined into this release.

We also welcome TWELVE new contributors to the project in this release. Thanks to all of them for their hard work 🚀🏆🚀.

What’s Changed

... (truncated)

Commits

Dependabot will resolve any conflicts with this PR as long as you don't alter it yourself. You can also trigger a rebase manually by commenting @dependabot rebase.

Dependabot commands and options

You can trigger Dependabot actions by commenting on this PR:

  • @dependabot rebase will rebase this PR
  • @dependabot recreate will recreate this PR, overwriting any edits that have been made to it
  • @dependabot merge will merge this PR after your CI passes on it
  • @dependabot squash and merge will squash and merge this PR after your CI passes on it
  • @dependabot cancel merge will cancel a previously requested merge and block automerging
  • @dependabot reopen will reopen this PR if it is closed
  • @dependabot close will close this PR and stop Dependabot recreating it. You can achieve the same result by closing it manually
  • @dependabot show <dependency name> ignore conditions will show all of the ignore conditions of the specified dependency
  • @dependabot ignore <dependency name> major version will close this group update PR and stop Dependabot creating any more for the specific dependency's major version (unless you unignore this specific dependency's major version or upgrade to it yourself)
  • @dependabot ignore <dependency name> minor version will close this group update PR and stop Dependabot creating any more for the specific dependency's minor version (unless you unignore this specific dependency's minor version or upgrade to it yourself)
  • @dependabot ignore <dependency name> will close this group update PR and stop Dependabot creating any more for the specific dependency (unless you unignore this specific dependency or upgrade to it yourself)
  • @dependabot unignore <dependency name> will remove all of the ignore conditions of the specified dependency
  • @dependabot unignore <dependency name> <ignore condition> will remove the ignore condition of the specified dependency and ignore conditions

@dependabot
Bump the pip group across 1 directory with 4 updates
e565b62 
Bumps the pip group with 4 updates in the / directory: [dbt-oracle](https://github.com/oracle/dbt-oracle), [dbt-core](https://github.com/dbt-labs/dbt-core), [sqlfluff](https://github.com/sqlfluff/sqlfluff) and [sqlfluff-templater-dbt](https://github.com/sqlfluff/sqlfluff).


Updates `dbt-oracle` from 1.8.3 to 1.8.4
- [Release notes](https://github.com/oracle/dbt-oracle/releases)
- [Changelog](https://github.com/oracle/dbt-oracle/blob/main/HISTORY.md)
- [Commits](oracle/dbt-oracle@v1.8.3...v1.8.4)

Updates `dbt-core` from 1.8.8 to 1.9.1
- [Release notes](https://github.com/dbt-labs/dbt-core/releases)
- [Changelog](https://github.com/dbt-labs/dbt-core/blob/v1.9.1/CHANGELOG.md)
- [Commits](dbt-labs/dbt-core@v1.8.8...v1.9.1)

Updates `sqlfluff` from 3.2.5 to 3.3.0
- [Release notes](https://github.com/sqlfluff/sqlfluff/releases)
- [Changelog](https://github.com/sqlfluff/sqlfluff/blob/main/CHANGELOG.md)
- [Commits](sqlfluff/sqlfluff@3.2.5...3.3.0)

Updates `sqlfluff-templater-dbt` from 3.2.5 to 3.3.0
- [Release notes](https://github.com/sqlfluff/sqlfluff/releases)
- [Changelog](https://github.com/sqlfluff/sqlfluff/blob/main/CHANGELOG.md)
- [Commits](sqlfluff/sqlfluff@3.2.5...3.3.0)

---
updated-dependencies:
- dependency-name: dbt-oracle
  dependency-type: direct:production
  update-type: version-update:semver-patch
  dependency-group: pip
- dependency-name: dbt-core
  dependency-type: direct:production
  update-type: version-update:semver-minor
  dependency-group: pip
- dependency-name: sqlfluff
  dependency-type: direct:production
  update-type: version-update:semver-minor
  dependency-group: pip
- dependency-name: sqlfluff-templater-dbt
  dependency-type: direct:production
  update-type: version-update:semver-minor
  dependency-group: pip
...

Signed-off-by: dependabot[bot] <[email protected]>
@dependabot dependabot bot added dependencies Pull requests that update a dependency file python Pull requests that update Python code labels Dec 23, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Reviewers
No reviews
Assignees
No one assigned
Labels
dependencies Pull requests that update a dependency file python Pull requests that update Python code
Projects
None yet
Milestone
No milestone
Development

Successfully merging this pull request may close these issues.
0 participants