Releases: databricks/databricks-vscode
Releases · databricks/databricks-vscode
Release list
Release: v2.14.1 (#2140)
Release: v2.14.1
packages/databricks-vscode
(2026-08-21)
- Narrate live progress during Python environment setup (#2139) (f606d0a)
- Pre-check the host CLI before starting the SSH tunnel (#2127) (5af58f2)
- Show an info toast on a successful Python environment setup that had warnings (#2138) (2acdc44)
- Avoid duplicate profile section creation in
.databrickscfgduring OAuth setup (#2133) (6e1c472)
Release: v2.14.0 (#2137)
Release: v2.14.0
packages/databricks-vscode
(2026-08-20)
- Introduce frictionless Python environment setup that makes local Python setup for Databricks development just work. Because the extension already knows the compute you are targeting — a cluster's DBR version or a serverless environment version — it uses that single input to automatically build a local
.venvwhose Python version and package set exactly match the runtime, eliminating the classic "works locally, breaks on Databricks" mismatch. This release delivers the fully automated uv path: one click in VS Code (or thedatabricks environments setup-localCLI command) resolves the target, fetches runtime-pinned dependency artifacts, installs the correct Python, and provisions a matched environment withdatabricks-connectready to go (#2124) (315f77d) - Add explicit per-row Copy actions to the configuration view (#2115) (fe1e4aa)
- Update Databricks CLI to v1.13.0 (#2136, #2109) (43af52d) — see the CLI release notes for changes
Release: v2.13.1 (#2106)
Release: v2.13.1
packages/databricks-vscode
(2026-08-12)
- Build terminal commands for the shell that runs them, fixing "Create a new Databricks project" and other terminal actions on Windows with cmd.exe (#2092) (ebcf7c9) — reported in #1822
- Fix "Show Bundle Logs", "Show Logs" and "Show Error Logs" doing nothing on hosts that scope the log channel id, such as Cursor (#2093) (a1c7e84)
Release: v2.13.0 (#2089)
Release: v2.13.0
packages/databricks-vscode
(2026-08-06)
Release: v2.12.4 (#2065)
Release: v2.12.4
packages/databricks-vscode
(2026-07-30)
- Fix job run status not updating when the CLI returns a modern job-run URL (#2018) (d8f06d7)
- Update Databricks CLI to v1.9.0 (#2035) (9e6dc8d) — see the CLI release notes for changes since v1.7.0
Release: v2.12.3 (#2012)
Release: v2.12.3
packages/databricks-vscode
(2026-07-14)
- Always pass
--hoston databricks-cli login so custom workspace hosts are not redirected to the public login page (#2009) (d2f0518) — fixes the OAuth sign-in regression reported in #2011 - Update Databricks CLI to v1.7.0 (#1999) (f2e56f2) — see the CLI release notes for changes since v1.2.0; notably the direct deployment engine is now GA and the default for new deployments
Release: v2.12.2 (#1990)
Release: v2.12.1 (#1948)
Release: v2.12.1
packages/databricks-vscode
(2026-07-02)
- [telemetry] Detect Python package manager(s) at project setup (#1918) (133c453), closes #1918
- Correctly resolve relative includes in
databricks.ymlfrom parent folders (#1870) (06a3abc), closes #1870 #1818 #1731 - Rename schema name, databricks-asset-bundles.json to declarative-automatation-bundles.json (#1885) (a91942c), closes #1885
Release: v2.12.0 (#1928)
Release: v2.12.0
packages/databricks-vscode
(2026-06-24)
- Add create file support to WSFS explorer (#1922) (430a4d8), closes #1922
- Bound databricks-cli login timeout to fix indefinite WSL hang (#1921) (a56cb82), closes #1921 #1917
- Fix Databricks Connect run/debug interpreter split-brain (#1912) (2bebf16), closes #1912 #1905
- Fix Volume "Open in Databricks" routing to volume URL (#1925) (630e267), closes #1925
Release: v2.11.1 (#1916)
Release: v2.11.1
packages/databricks-vscode
(2026-06-18)
- fix: use correct target folder for createFolder/uploadFile in Workspace fs (#1913) (be427e9), closes #1913
- Drop the “or greater” addition on the line where extension suggests to activate a Python environment (13452fb), closes #1915
- Gate WSFS and docs panels on extension activation (#1909) (308f687), closes #1909
- Pass DATABRICKS_CLI_PATH and resolve the platform-specific CLI binary (#1910) (6fcb630), closes #1910 #1903