Learn how to fix dbt 1.10 deprecation warnings for meta
and tags
properties, and migrate your project automatically with MetaMove.
meta
and tags
should be structured in your YAML files. Instead of manually updating potentially hundreds of files, you can use MetaMove - a CLI tool specifically designed to automate this migration.
meta
and tags
.
The key change affects how you define meta
and tags
properties across your dbt project:
Before (dbt < 1.10):
meta
configtransformed
directory:
.yml
and .yaml
files, so wildcards work safely:
meta
and tags
at any nesting level, including inside columns
config
sectionsmeta
and tags
, be aware of other properties moving to configs:
freshness
(for sources)docs
group
access
config
block following the same pattern as meta
and tags
.
--warn-error
flags that promote warnings to errors, you may need to adjust your configuration during migration:
config
blocks, MetaMove will merge the new properties. However, if you encounter conflicts:
-o
flag to organize transformed files by directorymeta
and tags
structure is essential for maintaining a robust, future-proof dbt project. MetaMove makes this migration straightforward by automating the tedious work while preserving your careful formatting and comments.
The goal is to enable you to work with more safety, feedback, and confidence going forward. By moving meta
and tags
under config
blocks, dbt can provide better validation and prevent the subtle issues that arise from misspelled properties or unintended conflicts.
Start your migration today: