denis256 notes and projects

dbt-core v1.11.12 was published on July 1, 2026, with a focused fix for false deprecation warnings around state model configs. The key change is that the release adds the ModelState schema to the bundled jsonschemas, so valid keys such as pre_clone, lag_tolerance, and require_fresh_data_from stop looking deprecated to dbt users and operators.

The full release notes and downloads are on the GitHub release page.

State model configs stop looking deprecated

The main fix in dbt-core v1.11.12 is small, but it targets a noisy failure mode. dbt had been emitting spurious deprecation warnings for state model configs. The release notes call out pre_clone, lag_tolerance, and require_fresh_data_from as examples of affected config keys.

The cause was not that these config keys suddenly became invalid. The fix adds the ModelState schema to the bundled jsonschemas. With that schema present, dbt can validate these state model config values without treating them as deprecated surface area.

For teams that scan dbt output in CI, this kind of warning noise is more than cosmetic. Deprecation warnings tend to feed alert rules, upgrade reports, pull request checks, and human review queues. A warning that fires on valid configuration makes it harder to spot the warning that actually matters.

Cleaner output for state aware projects

This release is most relevant to projects that already use state model configs. If a project uses keys like pre_clone, lag_tolerance, or require_fresh_data_from, v1.11.12 should make command output cleaner without requiring a config rename.

That does not mean every dbt project will see a visible change. If the project never used these config keys, this release is likely just routine patch uptake. The release notes describe one fix, so there is no broad behavior change to assume.

The useful detail is the direction of the fix. It updates the schema bundle that dbt ships, rather than asking users to edit working model config. That is the right shape for this bug. The user config was not the problem. The validation metadata was incomplete.

What operators should check

After upgrading to v1.11.12, look at the warning section of normal dbt runs. Pipelines that previously reported deprecation warnings for state model configs should stop reporting those specific messages.

It is also worth checking any local logic that counts warnings. Some teams fail CI on new deprecation warnings, while others store dbt warnings as build metadata. If those systems were carrying allow lists for the affected state config warnings, the allow lists may become unnecessary after this patch.

There is no migration step in the release notes. There is also no prerelease flag on this GitHub release. Treat it as a regular patch release whose value is mainly lower noise in validation and build logs.

Narrow release, narrow risk

dbt-core v1.11.12 is not a feature release. It is a patch for one reported issue, linked as #13016 in the notes. That makes the release easy to reason about: if the spurious state config warnings affected your project, this is directly relevant. If not, it is still a normal patch level update, but there is not much new surface to learn.

The contributor section credits @tauhid621 for the fix through the same issue link. Beyond that, the notes do not list extra changes, dependency updates, or migration work. Keep the upgrade review proportional to that scope.

Where to get it

• Release page: dbt-core v1.11.12
• Repository: dbt-labs/dbt-core
• Tag: v1.11.12