Release v1.16.0
CLI
aitools installnow registers the official Claude marketplace if it is missing before installing the Databricks Claude plugin. (#6485)databricks aitools install --output jsonnow reports anerror_categoryfor a failed or skipped install (per agent, and at the top level for a failure with no per-agent entry), giving coding agents and CI a stable classification of why an install did not complete. (#6482)databricks aitools installhonors--output json, emitting a structured{scope, agents[...]}document that reports each agent's delivery and install status so coding agents and CI can consume the result without scraping the text output. JSON mode requires--scopeand--agentsso the command runs without interactive prompts. (#6481)databricks bundle syncnow prints sync progress (Action: PUT,Uploaded ...) by default, matchingdatabricks sync. Previously it was silent unless--outputwas passed. Use--output jsonfor machine-readable output. (#6568)- Support major-only DBR runtime versions such as
19.x-scala2.13in the cluster picker used bydatabricks auth login --configure-clusteranddatabricks labs. (#6574) - Deprecated the
databricks environments setup-local --constraints-onlyflag in favour of the orthogonal--no-dbconnect; the flag still works as a hidden alias but is hidden from--helpand prints a one-line deprecation notice, and will be removed in a later release. (#6470) - Add orthogonal
--no-constraintsand--no-dbconnectflags todatabricks environments setup-local:--no-constraintsskips writing the remote Python-version and dependency pins, and--no-dbconnectskips the databricks-connect dependency. (#6464) databricks environments setup-localnow reports a distinctE_PROVISION_CONFLICTerror code in--output jsonwhen the project's dependencies conflict with the pins written for the target environment, making the requirements unsatisfiable (the same conflict surfaced as aW_USER_CONSTRAINT_CONFLICTwarning); it is reported after the project files are written, without attempting the doomed provisioning, while other provisioning failures continue to reportE_PROVISION. (#6479)databricks ssh connectandssh setupnow verify the tunnel's SSH host key against the key the workspace published for the connection, recorded in~/.databricks/ssh-tunnel-known-hosts/<name>instead of~/.ssh/known_hosts. Reconnecting with a name used before no longer fails withHost key verification failedwhen the compute behind that name changed, and no longer needs a manualssh-keygen -R; host blocks written by an earlierdatabricks ssh setuppick this up once you re-run it. (#6557)- Stop
databricks ssh connect --idefrom adding a duplicate entry to the IDE's Remote Explorer on every connect: the remote authority is now the SSH host alias alone, instead of embedding the per-instance remote OS user. (#6550) - Add
--max-clientsand--server-timeoutflags todatabricks ssh setup, and--server-timeouttodatabricks ssh connect. Both are fixed when the SSH tunnel server job is submitted, sossh setupnow serializes them into the generatedProxyCommandinstead of falling back to the built-in defaults. (#6547) ssh connectsessions no longer end when the tunnel's websocket connection is lost. The CLI reattaches to the running session and replays the bytes that were missed, so the shell and everything running in it stay intact, and a transient failure to open a replacement connection for the periodic auth refresh is retried rather than ending the session. Reattaching requires an SSH server started by a CLI that supports it; against an older server the connection behaves as before. (#6558)
Bundles
- Added PyDABs (Python) support for secrets:
Resources.add_secretand thesecret_mutatordecorator. (#6553) - Fix job and pipeline environment dependencies with a
*version wildcard (e.g.numpy==2.5.*) being treated as local file paths. (#6555) - Add the
postgres_snapshot_schedulesbundle resource for managing a Lakebase Postgres branch's automatic-snapshot schedule (direct deployment engine only). (#6449)