Repository navigation
chore: bump SQL kernel to 1.2.0 - #991
Merged
Merged
Conversation
vuanhphung
had a problem deploying
to
azure-prod
October 19, 2026 21:15 — with 
GitHub Actions
Failure
GitHub Actions
Failure
Signed-off-by: Vu Anh Phung <vu.phung@databricks.com>
vuanhphung
force-pushed
the
chore/bump-kernel-1.2.0
branch
from
October 20, 2026 03:33
5e3cfb2 to
3bc0a7d
Compare
vuanhphung
added
integration-test
![peco-review-bot[bot]](https://avatars.githubusercontent.com/in/3801177?s=60&v=4){kind=small}
There was a problem hiding this comment.
Verdict: 1 Low
Looks good — a clean, mechanical dependency bump. Floor raised to ^1.2.0, KERNEL_REV advanced to a valid 40-char SHA, and the lockfile kernel block (incl. the pyarrow>=23.0.1,<24 pin) and content-hash are consistent. One low-severity note: no CHANGELOG entry for the kernel bump, which breaks from the repo's established pattern.
Other findings
- 🔵 Low — The
# Unreleasedsection has no entry for this kernel bump, but every prior kernel version change is recorded in the changelog (4.6.0: "Upgrade Databricks SQL Kernel to 1.1.0"; 4.5.0: "Upgrade Databricks SQL Kernel to 1.0.0"). This PR raises the user-visible dependency floor from^1.1.0to^1.2.0, which is a consumer-facing change for anyone installing the[kernel]extra. Consider adding an Unreleased line (e.g. "Upgrade Databricks SQL Kernel to 1.2.0") to keep the changelog consistent with the established convention.
|
Integration tests triggered. View workflow runs. Result posts back here as the "Python Integration Tests" check. |
1 similar comment
|
Integration tests triggered. View workflow runs. Result posts back here as the "Python Integration Tests" check. |
This branch was successfully deployed
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
1 participant
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.
Raise the optional kernel dependency floor to
^1.2.0and advanceKERNEL_REVto thev1.2.0commit (39ba84f5ab55c2b0bc874fd58a6f9215ee27cb23). Refresh the kernel artifacts and hashes inpoetry.lockwithout changing other dependencies.Validation:
poetry check --lock; 1,263 unit tests passed (4 skipped), plus 2 separate real-kernel routing tests passed with the published 1.2.0 wheel.