release-v2.20.0·Release: v2.20.0 (#2232)
Summary
The extension now requires VS Code 1.104 or later and immediately refreshes the Bundle Variables view when overrides are saved or reset. Upgraded Databricks CLI integration migrates bundle deployment state to the direct engine and errors if a configured workspace ID does not match the connected workspace.
Summary from the captured archive. Follow the original source for full context.
More from databricks/databricks-vscode
Release: v2.23.0 (#2277)
The extension now has a databricks.notebooks.configureJupyterCellMarkers setting to stop it writing Jupyter cell-marker settings to workspace settings, and claude and codex are available in SSH tunnel connections with Unity Gateway preconfigured. The bundled Databricks CLI moves to v1.23.0, which restores legacy-import uploads for bundle deploys (so notebooks are no longer uploaded as plain files) and adds workspace.sync_mode, replacing the deprecated presets.source_linked_deployment and experimental.immutable_folder.
Release: v2.22.0 (#2272)
Release v2.22.0 stops bundle sub-project discovery from blocking the extension host and has VS Code handle proxies and certificates for Databricks SDK calls. It also fixes uv workspace member environment selection and constraint conflicts, and exposes the bundle Configuration view and Bundle Resource Explorer in Remote SSH mode.
Release: v2.21.0 (#2248)
Databricks Asset Bundles now exclusively deploy using the direct engine, removing the Terraform deployment engine and its bundled binary. This release also restores default TLS certificate verification for SDK calls and sorts folders alphabetically in the Workspace File System view.
Release: v2.19.0 (#2215)
Users can now configure a custom Databricks CLI path and utilize HTTP proxies or corporate CA certificates with the SDK and bundled CLI. The update also resolves a potential ReDoS vulnerability during email redaction on large inputs.