Repository navigation
fix(cli): let the CLI install beside runtime-pinned databricks-sdk - #425
Merged
Merged
Conversation
The [cli] extra required databricks-sdk>=0.70.0, so it could not resolve in repos that pin the SDK to match their Databricks runtime — a bundle repo pinning 0.57.* had to run the CLI as an ephemeral overlay instead of a dev dependency. The CLI only uses Config(), Config.host, and Config.authenticate, which long predate 0.70. Lower the floor to 0.20.0: the oldest version verified end to end (isolated smoke test, the full CLI unit suite, and a live warehouse plan). The CI minimum-pin smoke invocation moves with it, so the floor stays exercised on every build.
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.
What
Lowers the
[cli]extra'sdatabricks-sdkfloor from>=0.70.0to>=0.20.0(and the dev-group floor with it), and moves the CI minimum-pin smoke invocation to==0.20.0so the declared floor stays exercised on every build.Why
The CLI is designed to run inside consumer repos, and consumer repos that deploy Databricks bundles pin
databricks-sdkto match their cluster runtime. A real adopter pinningdatabricks-sdk==0.57.*could not co-resolvedelta-engine[cli]at all — the CLI had to run as an ephemeraluv run --withoverlay instead of a normal dev dependency.The floor never reflected an API need: the CLI's entire SDK surface is
Config(),Config.host, andConfig.authenticate, all stable long before 0.70. The 0.70 value (and the>=0.120.0before it) was "current at time of writing".Evidence for 0.20.0
tests/distribution/cli_smoke_test.py) passes at 0.20.0, 0.30.0, 0.44.1, and 0.57.0.tests/clisuite (101 tests) passes with 0.20.0 installed.planagainst a real Unity Catalog workspace over a SQL warehouse — unified auth, connection, catalog read — succeeds with 0.20.0.uv.lockstill resolves the dev environment to the latest SDK (0.136.0), so the ceiling keeps being tested by the live suite while the smoke test guards the floor.🤖 Generated with Claude Code