chore: bump dbt-core upper bound to <1.11.12 (#1505)

## Summary

- Bump `dbt-core` upper bound from `<1.11.9` to `<1.11.12` to include
dbt-core 1.11.9, 1.11.10, and 1.11.11.
- `uv.lock` pin moves `1.11.8` → `1.11.11` (`uv lock --upgrade-package
dbt-core`; no transitive churn).
- `requirements.lowest-direct.txt` is unchanged — the floor stays at
`1.11.2`, so the lowest-direct resolution is unaffected (verified via
`scripts/regenerate_min_deps_lock.sh`, no drift).

## Test plan

- [x] `hatch run pre-commit run --all-files` passes (incl. `uv-lock
--check`)
- [x] CI passes
- [x] `/integration-test`

Author: sd-db

CHANGELOG.md

@@ -26,6 +26,7 @@
 - Tighten the `databricks-sql-connector` ceiling to patch level (`<4.3.0` → `<4.2.7`) so patch upgrades require an intentional bump; the locked version stays at 4.2.6. ([#1497](https://github.com/databricks/dbt-databricks/pull/1497), [#1498](https://github.com/databricks/dbt-databricks/pull/1498))
 - Stabilize the `TestChangingSchema*` Python-model functional tests under min-deps (dbt-core 1.11.2), where a sibling class's source schema.yml could leak into their parse and fail with `EnvVarMissingError`. ([#1488](https://github.com/databricks/dbt-databricks/pull/1488))
 - **BREAKING:** users who relied on column-level constraints (NOT NULL, primary key, foreign key, check) being applied under `use_materialization_v2: true` without `contract.enforced: true` must now set `contract.enforced: true` explicitly on the model.
+- Bump upper bound of dbt-core to `<1.11.12` to include dbt-core 1.11.9, 1.11.10, and 1.11.11 ([#1505](https://github.com/databricks/dbt-databricks/pull/1505))
 
 ## dbt-databricks 1.12.0 (May 18, 2026)
 

pyproject.toml

@@ -27,7 +27,7 @@ dependencies = [
     "databricks-sql-connector[pyarrow]>=4.1.1, <4.2.7",
     "dbt-adapters>=1.22.0, <1.23.0",
     "dbt-common>=1.37.0, <1.38.0",
-    "dbt-core>=1.11.2, <1.11.9",
+    "dbt-core>=1.11.2, <1.11.12",
     "dbt-spark>=1.10.0, <1.11.0",
     "keyring>=23.13.0, <25.6.0",
     "packaging>=21.0, <26.0",