dbt-databricks must be <1.10.2

[arbiv]

null

Summary by CodeRabbit

• Chores
  • Updated the way dbt package versions are installed in the GitHub Actions workflow, including a temporary upper version limit for the databricks_catalog warehouse type to address a known issue.
  • Applied a temporary version restriction on the dbt-databricks dependency to maintain compatibility until the related issue is resolved.

[coderabbitai]

Walkthrough

The change updates the dbt package version specifiers in the GitHub Actions workflow and the pyproject.toml for the dbt-databricks dependency. It adds an explicit upper version bound <1.10.2 as a temporary workaround for a known issue, switching all version constraints from <= to the compatible release operator ~=.

Changes

File(s)	Change Summary
.github/workflows/test-warehouse.yml	Updated dbt package install commands to use ~= instead of <=; added upper bound <1.10.2 for databricks_catalog with a comment referencing a related issue.
pyproject.toml	Restricted dbt-databricks version upper bound to <1.10.2 with a comment about the temporary workaround for a known issue.

Poem

In the garden of code, a version grows,
With tildes and bounds, the workflow flows.
Databricks catalog gets a cap for now,
Awaiting a fix, we hop and bow.
🐇✨

---

📜 Recent review details

Configuration used: CodeRabbit UI
Review profile: CHILL
Plan: Pro

📥 Commits

Reviewing files that changed from the base of the PR and between 4b3d76c and b1c16b2.

📒 Files selected for processing (2)

• .github/workflows/test-warehouse.yml (1 hunks)
• pyproject.toml (1 hunks)

✅ Files skipped from review due to trivial changes (2)

• pyproject.toml
• .github/workflows/test-warehouse.yml

⏰ Context from checks skipped due to timeout of 90000ms (2)

• GitHub Check: code-quality
• GitHub Check: test / test

---

🪧 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.
  • Explain this complex logic.
  • 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 explain this code block.
  • @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 explain its main purpose.
  • @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.

Support

Need help? Create a ticket on our support page for assistance with any issues or questions.

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.
• @coderabbitai generate sequence diagram to generate a sequence diagram of the changes in this PR.
• @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.

[github-actions]

👋 @arbiv
Thank you for raising your pull request.
Please make sure to add tests and document all user-facing changes.
You can do this by editing the docs files in this pull request.

[coderabbitai]

Actionable comments posted: 0

🧹 Nitpick comments (1)

.github/workflows/test-warehouse.yml (1)

125-125: Clarify the TODO comment’s removal criteria
The workaround note is helpful, but add specific conditions or a target milestone/issue resolution date to ensure the TODO doesn’t linger indefinitely.

📜 Review details

Configuration used: CodeRabbit UI
Review profile: CHILL
Plan: Pro

📥 Commits

Reviewing files that changed from the base of the PR and between 0c442e1 and 4b3d76c.

📒 Files selected for processing (1)

• .github/workflows/test-warehouse.yml (1 hunks)

⏰ Context from checks skipped due to timeout of 90000ms (13)

• GitHub Check: test (1.8.0, databricks_catalog) / test
• GitHub Check: test (1.8.0, athena) / test
• GitHub Check: test (1.8.0, bigquery) / test
• GitHub Check: test (athena) / test
• GitHub Check: test (redshift) / test
• GitHub Check: test (snowflake) / test
• GitHub Check: test (databricks_catalog) / test
• GitHub Check: test (bigquery) / test
• GitHub Check: test (1.8.0, snowflake) / test
• GitHub Check: test (postgres) / test
• GitHub Check: test (1.8.0, redshift) / test
• GitHub Check: test (1.8.0, postgres) / test
• GitHub Check: code-quality

🔇 Additional comments (1)

.github/workflows/test-warehouse.yml (1)

126-126: Verify the combined pip version specifier
Ensure that dbt-databricks<1.10.2,~=… enforces the intended range under PEP 440 semantics.

You can simulate resolution without modifying the repo:

#!/bin/bash
# Verify pip resolves to the highest patch <1.10.2
pip download "dbt-databricks<1.10.2,~=1.10.1" --no-deps -d /tmp