Skip to content

chore(deps): allow packaging 26.x - #1777

Merged
sd-db merged 2 commits into
mainfrom
sd-db/allow-packaging-26
Nov 17, 2026
Merged

sd-db merged 2 commits into
mainfrom
sd-db/allow-packaging-26

Conversation

@sd-db

@sd-db sd-db commented Nov 17, 2026

Copy link
Copy Markdown
Collaborator

Description

Raises the packaging upper bound from <26.0 to <27.0, so dbt-databricks can be installed alongside packaging 26.x. uv.lock moves to packaging 26.3.

packaging became a direct dependency in #1474 with the usual next-major cap. 26.0 was already out at the time, so the cap excluded the current major for no reason. The adapter only uses packaging.version (parse and Version), which works the same on 26.x. No other dependency in the lock caps it, and the min-deps floor (packaging==21.0) is unchanged.

Unit tests pass with packaging 26.3 installed (1,729 passed, 4 skipped).

Checklist

  • I have run this code in development and it appears to resolve the stated issue
  • This PR includes tests, or tests are not required/relevant for this PR
  • I have updated the CHANGELOG.md and added information about my change to the "dbt-databricks next" section.
  • [Optional] I have run the dbt-databricks-pr-ready project skill for this PR and addressed its merge-readiness feedback

This pull request and its description were written by Isaac.

Raise the packaging upper bound from <26.0 to <27.0 and refresh uv.lock to packaging 26.3. The adapter only uses packaging.version, which is unchanged across 26.x.

Co-authored-by: Isaac <no-reply@databricks.com>
Co-authored-by: Isaac <no-reply@databricks.com>
@github-actions

Copy link
Copy Markdown

Coverage report

This PR does not seem to contain any modification to coverable code.

@sd-db
sd-db merged commit d49164b into main Nov 17, 2026
15 of 16 checks passed
@sd-db
sd-db deleted the sd-db/allow-packaging-26 branch November 17, 2026 15:59
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants