fix(seeds): resolve seed file paths from the package root by fornwall · Pull Request #16129 · dbt-labs/dbt

fornwall · 2026-08-29T22:32:53Z

The same path handling existed in four places: resolve_seed_path() and has_same_content() joined the package root with the package-relative path correctly, while adapter.get_seed_file_path() and the BigQuery seed macro each derived it incorrectly. All four now go through a new DbtSeed::resolve_file_path() function.

Only DuckDB and BigQuery exposed the bug. Other adapters insert rows from agate_table, which has already been read from the resolved path; DuckDB and BigQuery instead pass the CSV path to the engine from Jinja:

BigQuery: the macro built its path from a non-existing model['project_root'], so the expression collapsed to the bare project-relative original_file_path. The driver resolved that against the process working directory -> seeds loaded when dbt ran from the project root, and missed otherwise.
DuckDB: get_seed_file_path joined the package root with original_file_path, which already carries dbt_packages/<pkg>. The prefix was repeated, and the COPY failed for every seed in an installed package.

Resolver-built seeds store their package root separately from their package-relative path. Use that pair consistently instead of rebuilding file locations from project-relative original_file_path. This fixes DuckDB dependency seeds, which duplicated the package prefix, and BigQuery seeds run outside the project root, which previously used a cwd-relative path. It also removes the now-unused in_dir fallback. Cover shared path resolution, adapter serialization, and BigQuery macro forwarding separately. Signed-off-by: Fredrik Fornwall <fredrik@fornwall.net>

fornwall requested a review from a team as a code owner August 29, 2026 22:32

cla-bot Bot added the cla:yes label Aug 29, 2026

github-actions Bot added the community label Aug 29, 2026