Upgrade SQL kernel native packages to 1.0.0 - #516
Merged
Conversation
vuanhphung
had a problem deploying
to
azure-prod
September 1, 2026 02:56 — with 
GitHub Actions
Failure
GitHub Actions
Failure
vuanhphung
had a problem deploying
to
azure-prod
September 1, 2026 02:56 — with
GitHub Actions
Failure
GitHub Actions
Failure
vuanhphung
had a problem deploying
to
azure-prod
September 1, 2026 02:56 — with
GitHub Actions
Failure
GitHub Actions
Failure
vuanhphung
had a problem deploying
to
azure-prod
September 1, 2026 02:56 — with
GitHub Actions
Failure
GitHub Actions
Failure
|
Thanks for your contribution! To satisfy the DCO policy in our contributing guide every commit message must include a sign-off message. One or more of your commits is missing this message. You can reword previous commit messages with an interactive rebase ( |
vuanhphung
force-pushed
the
vu-phung/upgrade-sql-kernel-1.0.0
branch
from
September 1, 2026 02:57
669d23b to
ed14fa3
Compare
vuanhphung
had a problem deploying
to
azure-prod
September 1, 2026 02:57 — with
GitHub Actions
Failure
GitHub Actions
Failure
vuanhphung
had a problem deploying
to
azure-prod
September 1, 2026 02:57 — with
GitHub Actions
Failure
GitHub Actions
Failure
vuanhphung
had a problem deploying
to
azure-prod
September 1, 2026 02:57 — with
GitHub Actions
Failure
GitHub Actions
Failure
vuanhphung
had a problem deploying
to
azure-prod
September 1, 2026 02:57 — with
GitHub Actions
Failure
GitHub Actions
Failure
![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 High
Mechanical version bump of the kernel native packages 0.2.0 → 1.0.0 across index.js version guards, package.json, and the lockfile — the code changes are consistent and correct. One high concern: the lockfile resolved URLs now point at the internal npm-proxy.cloud.databricks.com host rather than the public npm registry, which will break npm ci for external consumers/CI.
Signed-off-by: Vu Anh Phung <vu.phung@databricks.com>
vuanhphung
force-pushed
the
vu-phung/upgrade-sql-kernel-1.0.0
branch
from
September 1, 2026 03:03
ed14fa3 to
7b7dad4
Compare
sreekanth-db
approved these changes
Sep 1, 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.
Upgrade all platform-specific
databricks-sql-kernelpackages from0.2.0to1.0.0and refresh their lockfile metadata throughnpm-proxy.cloud.databricks.com.This also updates the napi-rs router version guard and release documentation.
Validation:
npm run build; 329 kernel tests against the installed 1.0.0 binary; 1,290 full unit tests; Prettier andgit diff --check.This PR was created with GitHub MCP.