dbt fixes DAG dependency loss for overloaded UDFs, cuts parse-time memory usage
The UDF dependency fix matters for correctness of DAG-based orchestration: silently dropped dependencies on overloaded UDFs could cause dbt to run or refresh models out of order without any visible error, corrupting downstream state in ways that are hard to detect. The parse-time memory/lazy-view change is an internal efficiency improvement for large projects but the source gives no benchmark numbers, so its practical impact on parse times at scale can't be quantified from this text alone.
What changed
dbt-core 1.12.0-rc3 fixes a bug where ref/source/function dependencies declared inside an overloaded UDF's overload body were dropped from the DAG when the overload SQL file got absorbed into the root function node; those dependencies are now carried onto the root node instead. Separately, dbt reduced parse-time memory and macro-generation overhead by virtualizing macros and switching flat_graph/WritableManifest to lazy, no-copy views.
Why it matters
The UDF dependency fix matters for correctness of DAG-based orchestration: silently dropped dependencies on overloaded UDFs could cause dbt to run or refresh models out of order without any visible error, corrupting downstream state in ways that are hard to detect. The parse-time memory/lazy-view change is an internal efficiency improvement for large projects but the source gives no benchmark numbers, so its practical impact on parse times at scale can't be quantified from this text alone.