Update dbt-core requirement from <1.9,>=1.8 to >=1.8,<1.10

[dependabot]

Updates the requirements on dbt-core to permit the latest version.

Release notes

Sourced from dbt-core's releases.

dbt-core v1.9.0

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)
• Enable specification of dbt_valid_to for current records (#10187)
• Enable retry support for microbatch models (#10715, #10729)
• Use unrendered database and schema source properties during state:modified, behind state_modified_compare_more_unrendered_values behavoiur flag (#9573)
• Ensure microbatch models respect full_refresh model config (#10785)
• Adds validations for custom_granularities to ensure unique naming. (#9265)
• Enable use of multi-column unique key in snapshots (#9992)
• Change gating of microbatch feature to be behind project flag / behavior flag (#10798)
• Ensure --event-time-start is before --event-time-end (#10786)
• Ensure microbatch models use same current_time value (#10819)
• Emit warning when microbatch model has no input with event_time config (#10926)
• Emit debug logging event whenever artifacts are written (#10937)
• Support --empty for snapshots (#10372)
• Add new hard_deletes="new_record" mode for snapshots. (#10235)

... (truncated)

Changelog

Sourced from dbt-core's changelog.

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)
• Enable specification of dbt_valid_to for current records (#10187)
• Enable retry support for microbatch models (#10715, #10729)
• Use unrendered database and schema source properties during state:modified, behind state_modified_compare_more_unrendered_values behavoiur flag (#9573)
• Ensure microbatch models respect full_refresh model config (#10785)
• Adds validations for custom_granularities to ensure unique naming. (#9265)
• Enable use of multi-column unique key in snapshots (#9992)
• Change gating of microbatch feature to be behind project flag / behavior flag (#10798)
• Ensure --event-time-start is before --event-time-end (#10786)
• Ensure microbatch models use same current_time value (#10819)
• Emit warning when microbatch model has no input with event_time config (#10926)
• Emit debug logging event whenever artifacts are written (#10937)
• Support --empty for snapshots (#10372)
• Add new hard_deletes="new_record" mode for snapshots. (#10235)
• Allow microbatch batches to run in parallel (#10853, #10855)

... (truncated)

Commits

• 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...
• 34f92a8 Access DEBUG flag through get_flags() (#11069) (#11096)
• a4b3085 [Automated] Merged prep-release/1.9.0rc2_12121325802 into target 1.9.latest d...
• 333d600 Bumping version to 1.9.0rc2 and generate changelog
• 61b6cb3 [Tidy first] move microbatch compilation to .compile method (#11063) (#11065)
• 6a36444 Add batch context object to microbatch jinja context (#11031) (#11064)
• 65f05e0 Rename internal batch_info variable to previous_batch_results (#11056) (#...
• aceae51 [Automated] Merged prep-release/1.9.0rc1_12015575655 into target 1.9.latest d...
• Additional commits viewable in compare view

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 this major version will close this PR and stop Dependabot creating any more for this major version (unless you reopen the PR or upgrade to it yourself)
• @dependabot ignore this minor version will close this PR and stop Dependabot creating any more for this minor version (unless you reopen the PR or upgrade to it yourself)
• @dependabot ignore this dependency will close this PR and stop Dependabot creating any more for this dependency (unless you reopen the PR or upgrade to it yourself)

[coderabbitai]

Important

Review skipped

Bot user detected.

To trigger a single review, invoke the @coderabbitai review command.

You can disable this status message by setting the reviews.review_status to false in the CodeRabbit configuration file.

---

🪧 Tips

Chat

There are 3 ways to chat with CodeRabbit:

• Review comments: Directly reply to a review comment made by CodeRabbit. Example:
  • I pushed a fix in commit <commit_id>, please review it.
  • Generate unit testing code for this file.
  • Open a follow-up GitHub issue for this discussion.
• Files and specific lines of code (under the "Files changed" tab): Tag @coderabbitai in a new review comment at the desired location with your query. Examples:
  • @coderabbitai generate unit testing code for this file.
  • @coderabbitai modularize this function.
• PR comments: Tag @coderabbitai in a new PR comment to ask questions about the PR branch. For the best results, please provide a very specific query, as very limited context is provided in this mode. Examples:
  • @coderabbitai gather interesting stats about this repository and render them as a table. Additionally, render a pie chart showing the language distribution in the codebase.
  • @coderabbitai read src/utils.ts and generate unit testing code.
  • @coderabbitai read the files in the src/scheduler package and generate a class diagram using mermaid and a README in the markdown format.
  • @coderabbitai help me debug CodeRabbit configuration file.

Note: Be mindful of the bot's finite context window. It's strongly recommended to break down tasks such as reading entire modules into smaller chunks. For a focused discussion, use review comments to chat about specific files and their changes, instead of using the PR comments.

CodeRabbit Commands (Invoked using PR comments)

• @coderabbitai pause to pause the reviews on a PR.
• @coderabbitai resume to resume the paused reviews.
• @coderabbitai review to trigger an incremental review. This is useful when automatic reviews are disabled for the repository.
• @coderabbitai full review to do a full review from scratch and review all the files again.
• @coderabbitai summary to regenerate the summary of the PR.
• @coderabbitai generate docstrings to generate docstrings for this PR. (Experiment)
• @coderabbitai resolve resolve all the CodeRabbit review comments.
• @coderabbitai configuration to show the current CodeRabbit configuration for the repository.
• @coderabbitai help to get help.

Other keywords and placeholders

• Add @coderabbitai ignore anywhere in the PR description to prevent this PR from being reviewed.
• Add @coderabbitai summary to generate the high-level summary at a specific location in the PR description.
• Add @coderabbitai anywhere in the PR title to generate the title automatically.

CodeRabbit Configuration File (.coderabbit.yaml)

• You can programmatically configure CodeRabbit by adding a .coderabbit.yaml file to the root of your repository.
• Please see the configuration documentation for more information.
• If your editor has YAML language server enabled, you can add the path at the top of this file to enable auto-completion and validation: # yaml-language-server: $schema=https://coderabbit.ai/integrations/schema.v2.json

Documentation and Community

• Visit our Documentation for detailed information on how to use CodeRabbit.
• Join our Discord Community to get help, request features, and share feedback.
• Follow us on X/Twitter for updates and announcements.