chore(deps): bump databricks-sql-connector to 4.2.7 and restore patch-level ceiling#1497
Merged
Merged
Conversation
Refresh the uv.lock pin for databricks-sql-connector from 4.2.6 to 4.2.7 (within the existing >=4.1.1, <4.3.0 ceiling; pyproject.toml unchanged). Release: https://github.com/databricks/databricks-sql-python/releases/tag/v4.2.7
#1474 widened the databricks-sql-connector ceiling from a patch-level pin (<4.1.6) to a minor-level pin (<4.3.0), which silently admits any 4.2.x patch. Restore the strict patch-level ceiling (<4.2.8) so future patch releases require an intentional bump.
sd-db
changed the title
Coverage report
This PR does not seem to contain any modification to coverable code. |
jprakash-db
approved these changes
Jun 4, 2026
Collaborator
Author
|
/integration-test |
|
Integration tests dispatched for PR #1497 by @sd-db. Track progress in the Actions tab. |
|
Integration results for PR #1497 — UC cluster ✅ success · SQL warehouse ✅ success · All-purpose cluster ✅ success · Shard coverage ✅ success |
sd-db
added a commit
that referenced
this pull request
Jun 5, 2026
…1498) ## Summary The `databricks-sql-connector` **4.2.7** release was **yanked upstream** shortly after [#1497](#1497) bumped to it. This reverts to **4.2.6** while keeping the strict patch-level pinning. - **Lock**: `uv.lock` pin reverted 4.2.7 → 4.2.6. - **Ceiling**: `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. - Floor (`>=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 lock` resolves to 4.2.6 under the `<4.2.7` constraint. - `pre-commit run --files uv.lock CHANGELOG.md pyproject.toml` passes (`uv-lock` consistency check green).
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
Bumps
databricks-sql-connectorto 4.2.7 and restores a strict, patch-level ceiling.uv.lockpin refreshed 4.2.6 → 4.2.7 (upstream release: https://github.com/databricks/databricks-sql-python/releases/tag/v4.2.7). No transitive churn.databricks-sql-connector[pyarrow]ceiling tightened<4.3.0→<4.2.8. #1474 had widened it from a patch-level pin (<4.1.6) to a minor-level pin (<4.3.0), which silently admits any future 4.2.x patch. Reverting to a patch-level ceiling keeps connector upgrades intentional — even patch releases now require an explicit bump.>=4.1.1) unchanged.Verification
uv lockresolves to 4.2.7 within the new<4.2.8constraint.pre-commit run --files uv.lock CHANGELOG.md pyproject.tomlpasses (uv-lockconsistency check green).