Clarify meta and tags don't trigger state:modified - #9715
Open
mirnawong1 wants to merge 3 commits into
Open
Conversation
|
The latest updates on your projects. Learn more about Vercel for GitHub.
|
mirnawong1
commented
Jul 29, 2026
mirnawong1
commented
Jul 29, 2026
mirnawong1
commented
Jul 29, 2026
mirnawong1
commented
Jul 29, 2026
mirnawong1
marked this pull request as ready for review
July 29, 2026 14:31
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Summary
metaandtags— including at the column level — do not triggerstate:modified, per confirmation from dbt-core maintainers (comment)metato the list of configs excluded fromstate:modified.configsin the state selection method docsdescription/persist_docsmetaandtagsresource-config pages pointing to this behaviorFixes #8798
🚀 Deployment available! Here are the direct links to the updated files: