chore(deps): revert databricks-sql-connector to 4.2.6 (4.2.7 yanked)#1498
Merged
Conversation
The 4.2.7 release was yanked upstream. Revert the uv.lock pin to 4.2.6 and tighten the ceiling to <4.2.7 (keeping the patch-level pinning from #1497). Net effect for the unreleased 1.12.1: connector stays at 4.2.6 with a strict patch-level ceiling.
Coverage report
This PR does not seem to contain any modification to coverable code. |
jprakash-db
approved these changes
Jun 4, 2026
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
2 participants
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Summary
The
databricks-sql-connector4.2.7 release was yanked upstream shortly after #1497 bumped to it. This reverts to 4.2.6 while keeping the strict patch-level pinning.uv.lockpin reverted 4.2.7 → 4.2.6.databricks-sql-connector[pyarrow]ceiling<4.2.8→<4.2.7— stays patch-level, so the max admitted version is 4.2.6 and any future bump remains intentional.>=4.1.1) unchanged.Net effect for the unreleased 1.12.1: connector stays at 4.2.6 with a strict patch-level ceiling. The CHANGELOG entry from #1497 is collapsed accordingly (the 4.2.7 round-trip never shipped in a tagged release).
Verification
uv lockresolves to 4.2.6 under the<4.2.7constraint.pre-commit run --files uv.lock CHANGELOG.md pyproject.tomlpasses (uv-lockconsistency check green).