Fix: ensure root package is treated top-level in dbt#5290
Merged
georgesittas merged 1 commit intomainfrom Sep 3, 2025
Merged
Conversation
izeigerman
approved these changes
Sep 3, 2025
1c59608 to
ecfbb29
Compare
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.
The added test demonstrates what this PR aims to support. Basically:
macrosdirectory indbt_project.ymlthat lives withindbt_packages/The above works in dbt, but SQLMesh didn't support it until now because an assumption was made that each package could only see the contents defined within it, not outside of it. So, the package in the 2nd bullet above would fail to see the aforementioned macro and fail at render time, since the symbol wasn't present in
jinja_env.globals.