## Changes

- Remove `SkipEngineEnvVar` field from `ProcessOptions` in `process.go`
- In `migrate.go`, clear `DATABRICKS_BUNDLE_ENGINE` in the context via
`env.Set(ctx, engine.EnvVar, "")` before calling `ProcessBundleRet`,
achieving the same effect

## Why
Simplify env var handling for
#4749

## Test plan
Existing tests.

🤖 Generated with [Claude Code](https://claude.com/claude-code)

---------

Co-authored-by: Claude Sonnet 4.6 <[email protected]>

## Changes

- Remove `SkipEngineEnvVar` field from `ProcessOptions` in `process.go`
- In `migrate.go`, clear `DATABRICKS_BUNDLE_ENGINE` in the context via
`env.Set(ctx, engine.EnvVar, "")` before calling `ProcessBundleRet`,
achieving the same effect

## Why
Simplify env var handling for
#4749

## Test plan
Existing tests.

🤖 Generated with [Claude Code](https://claude.com/claude-code)

---------

Co-authored-by: Claude Sonnet 4.6 <[email protected]>

…4749)

## Summary

Add a new `engine` field at the bundle/target level that allows users to
configure the deployment engine (`"terraform"` or `"direct"`) in their
bundle config.

### Behavior
- New bundles (no existing state): uses the configured engine, or
defaults to `terraform`
- Existing bundles (state present): if the configured engine doesn't
match state, a **warning** is issued pointing to the config source, and
the existing state's engine is used. Note, this is different from
current behaviour, where databricks CLI refuses to proceed with
config/state mismatch.
- Priority: state > `DATABRICKS_BUNDLE_ENGINE` env var > `bundle.engine`
config > default

### Example
```yaml
bundle:
  name: my-bundle
  engine: direct

targets:
  production:
    bundle:
      engine: terraform
```

## Test plan
Unit tests and acceptance tests.

🤖 Generated with [Claude Code](https://claude.com/claude-code)

---------

Co-authored-by: Claude Opus 4.6 <[email protected]>

## Release v0.295.0

### Notable Changes

* Databricks Asset Bundles have been renamed to Declarative Automation Bundles (DABs). This is a non-breaking change; no code or configuration modifications are required. See the [FAQ](https://docs.databricks.com/aws/en/dev-tools/bundles/faqs#why-was-databricks-asset-bundles-renamed-to-declarative-automation-bundles).
* Add `bundle.engine` config setting to select the deployment engine (`terraform` or [`direct`](https://docs.databricks.com/aws/en/dev-tools/bundles/direct)). The `bundle.engine` setting takes precedence over the `DATABRICKS_BUNDLE_ENGINE` environment variable. When the configured engine doesn't match existing deployment state, a warning is issued and the existing engine is used ([#4749](#4749), [#4782](#4782))

### CLI
* Add `databricks auth switch` command for setting the default profile ([#4651](#4651))
* Add positional argument support to `auth logout` ([#4744](#4744))
* Strip trailing slash from host in `auth login`, `auth token`, and `configure` commands ([#4633](#4633))

### Bundles
* Standardize `personal_schemas` enum across bundle templates ([#4401](#4401))
* engine/direct: Fix permanent drift on experiment name field ([#4627](#4627))
* engine/direct: Fix permissions state path to match input config schema ([#4703](#4703))
* Add default project name and success message to default-scala template ([#4661](#4661))
* Skip enum validation for unresolved variable references ([#4752](#4752))
* engine/direct: Support references to/from grants ([#4774](#4774))