release-v2.12.3·Release: v2.12.3 (#2012)
Summary
Fixed OAuth sign-in regression that was incorrectly redirecting users with custom workspace hosts to the public login page. Updated Databricks CLI to v1.7.0, which makes the direct deployment engine generally available and sets it as the default for new deployments.
Summary generated by brickster.ai. For the full changelog and any code/binary attachments, follow the GitHub link above.
More from databricks/databricks-vscode
Release: v2.20.0 (#2232)
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.
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.
Release: v2.18.0 (#2201)
The Python setup success panel now displays which preset configuration was selected. The bundled Databricks CLI is updated to v1.17.0, enabling SSH sessions to survive transient disconnects for more reliable connections.
Release: v2.17.2 (#2191)
The bundled Databricks CLI was updated to v1.16.1, fixing an SSH transfer regression for transfers larger than 1 MiB. No other user-facing changes are included in this release.
Release: v2.17.1 (rollback to v2.16.0)
v2.17.1 rolls back to v2.16.0 to fix an SSH connectivity regression introduced in v2.17.0. The v2.17.0 improvements will return in a future release once the underlying issue is resolved.
Release: v2.17.0 (#2187)
The Python environment setup now includes a preset picker for Full, DB Connect, or Python-only configurations with improved error recovery and actionable error messages for common issues. Script uploads now preserve stdout on failure, and the Databricks CLI was updated to v1.16.0.