This repository was archived by the owner on Jan 20, 2026. It is now read-only.
Merged
Conversation
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 subscribe to this conversation on GitHub.
Already have an account?
Sign in.
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.
PR Overview
Package version introduced in this PR:
v0.5.0
This PR addresses the following Issue/Feature(s):
Summary of changes:
Updates freshness to align with the new config framework introduced in dbt Core v1.9. Documents how users on older versions of dbt Core will/can interface with freshness
Submission Checklist
older versions of dbt do not run freshness tests, but there's no error message
Testing Instructions: Confirm the change addresses the issue(s)
freshness tests are running on dbt 1.9.5+
Focus Areas: Complex logic or queries that need extra attention
Changelog