dbt-core 1.12.4 adds OpenTelemetry trace ids to SQL

dbt-core 1.12.4 adds two Jinja functions, otel_trace_id() and otel_span_id(), that write OpenTelemetry trace and span ids into compiled model SQL, per dbt Labs' 1.12.4 release notes. A slow or failing query now carries the id of the dbt run that fired it. Tracking a bottleneck back to a specific model no longer means lining up timestamps across two separate logging systems.

Issue #15914 covers a bug where built-in generic tests were evicted from the test registry and left undefined at compile time. That happened after a project loaded a Fusion-generated manifest, and tests just stopped running with no error to explain the gap. For any team already running Fusion, a test suite that fails without an error is a bigger problem than one that's merely slow.

The release also validates that a resolved package install path stays inside the configured packages-install-path, closing a path traversal case. The three fixes arrive together in a single patch release, not a major version bump. Anyone running Fusion-generated manifests or relying on package installs to stay sandboxed should update regardless of whether they care about tracing.