Release: v2.12.4

[github-actions]

Release: v2.12.4

Patch release. Curated to the user-visible changes; internal/CI-only commits
(test(e2e), chore(deps)) and the inert python-setup feat series
(disabled-by-default feature flag, not yet wired) are excluded from the
changelog.

packages/databricks-vscode

• Fix job run status not updating when the CLI returns a modern job-run URL (fix(bundle): match modern CLI run URL in JobRunStatus.parseId #2018)
• Update Databricks CLI to v1.9.0 (Update Databricks CLI to v1.9.0 #2035) — see the CLI release notes for changes since v1.7.0

packages/databricks-vscode-types

No user-facing changes.

---

Tracking: DECO-27846

[github-actions]

If integration tests don't run automatically, an authorized user can run them manually by following the instructions below:

Trigger:
go/deco-tests-run/vscode

Inputs:

• PR number: 2065
• Commit SHA: 96527aea2919ed438a6daa04225d1c1996c7c670

Checks will be approved automatically on success.

[rugpanov]

🧪 e2e tests triggered — vscode-isolated-pr run #30546972484

Note: this is a private execution in databricks-eng/eng-dev-ecosystem. Only EMU (corporate) accounts on VPN can open it — the org has an IP allow list, so personal/public accounts (or off-VPN) get HTTP 403.

Judging by the known-flaky baseline (unity_catalog system.access, Windows terraform init, WebDriver races), not the run-level conclusion.

[rugpanov]

e2e assessment — run #30546972484

Only 1 of ~38 matrix jobs failed (linux bundle_sub_folder), and it failed in CI setup, not a test: the azure/login action couldn't fetch its federated OIDC token (Failed to fetch federated token from GitHub … give write permissions to id-token). The shard never reached its specs.

• ✅ Not a product regression, not a spec flake — CI plumbing (OIDC token federation), unrelated to v2.12.4.
• ⚠️ This is the CI workflow's secret-fetch azure/login, not the extension's Azure CLI auth code path — different thing.
• This PR only edits CHANGELOG.md; the shipped code (fix(bundle): match modern CLI run URL in JobRunStatus.parseId #2018, CLI v1.9.0) already landed on main via its own PRs.

Re-ran the failed job to clear the infra flake. Proceeding on the known-flaky judgment.