chore: regenerate dbt models from newly published schemas - #26
Merged
Conversation
datnguye
force-pushed
the
schema-watch/regen
branch
from
August 10, 2026 08:34
cb2ec4f to
22070ab
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
2 participants
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.
Automated by
schema-watch.codegen dbt --discoverfound a change inthe versions published at schemas.getdbt.com and regenerated the models.
The 100%-coverage suite passed on the regenerated output. Review the
version map / new model modules before merging — a brand-new schema
version may want a fixture in
tests/conftest.pyand a real-artifactround-trip in
tests/artifact_parser/dbt/test_roundtrip.py.