Impact Score: 5/10
dbt Core: dbt-core v1.12.4
Source available — automated, not human-reviewed
Component: dbt-core · Channel: stable. Automated analysis, not a compatibility certification. How this works.
Analysis updated: 2026-11-01.
⚡ Executive Summary (TL;DR)
dbt Core v1.12.4. Source highlight: dbt-core 1.12.4 - September 08, 2026
Who Does This Impact? (Role-Based Analysis)
💻 Software Engineers & Devs
Check the source notes against the package and APIs you use before upgrading.
📊 Product & Engineering Leads
Use the documented changes to assess relevance to your product; release frequency alone is not a quality measure.
⚙️ DevOps & Security
Verify the target version, runtime requirements and rollback procedure in the official documentation.
✨ New Features & Capabilities (1)
- Add otel_trace_id() and otel_span_id() Jinja functions to correlate query comments and model SQL with OpenTelemetry trace/span ids (#)
🔧 Bug Fixes & Patches (4)
- Re-parse the built-in generic tests (test_not_null, test_unique, test_accepted_values, test_relationships) after loading a Fusion-generated manifest, so they are not permanently evicted and left undefined at test-compile time (#15914)
- Write target/manifest.json from the corrected in-memory manifest after loading a Fusion-generated manifest, so the on-disk artifact reflects the rediscovered adapter macros actually used for compilation instead of Fusion's raw bundled macros (#)
- Capture and re-emit fusion parser subprocess output through dbt-core's event system instead of letting it pass through to raw stdout/stderr, re-leveling each line by its json-compat severity when available (#15672)
- Validate that a resolved package installation path stays within the configured packages-install-path (#N/A)
📄 View Raw Release Notes (Original Developer Log)
## dbt-core 1.12.4 - September 08, 2026
### Features
- Add otel_trace_id() and otel_span_id() Jinja functions to correlate query comments and model SQL with OpenTelemetry trace/span ids ([#](https://github.com/dbt-labs/dbt-core/issues/))
### Fixes
- Re-parse the built-in generic tests (test_not_null, test_unique, test_accepted_values, test_relationships) after loading a Fusion-generated manifest, so they are not permanently evicted and left undefined at test-compile time ([#15914](https://github.com/dbt-labs/dbt-core/issues/15914))
- Write target/manifest.json from the corrected in-memory manifest after loading a Fusion-generated manifest, so the on-disk artifact reflects the rediscovered adapter macros actually used for compilation instead of Fusion's raw bundled macros ([#](https://github.com/dbt-labs/dbt-core/issues/))
- Capture and re-emit fusion parser subprocess output through dbt-core's event system instead of letting it pass through to raw stdout/stderr, re-leveling each line by its json-compat severity when available ([#15672](https://github.com/dbt-labs/dbt-core/issues/15672))
- Validate that a resolved package installation path stays within the configured packages-install-path ([#N/A](https://github.com/dbt-labs/dbt-core/issues/N/A))
### Under the Hood
- sync JSON schemas from dbt-fusion ([#N/A](https://github.com/dbt-labs/dbt-core/issues/N/A))
### Contributors
- [@aiguofer](https://github.com/aiguofer) ([#15914](https://github.com/dbt-labs/dbt-core/issues/15914), [#](https://github.com/dbt-labs/dbt-core/issues/), [#15672](https://github.com/dbt-labs/dbt-core/issues/15672))
- [@ash2shukla](https://github.com/ash2shukla) ([#N/A](https://github.com/dbt-labs/dbt-core/issues/N/A))
- [@b-per](https://github.com/b-per) ([#](https://github.com/dbt-labs/dbt-core/issues/))
- [@fa-assistant](https://github.com/fa-assistant) ([#N/A](https://github.com/dbt-labs/dbt-core/issues/N/A))