-
Notifications
You must be signed in to change notification settings - Fork 17
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Update behavior deprecation flags to be behavior change flags #193
Conversation
Thank you for your pull request! We could not find a changelog entry for this change. For details on how to document a change, see the contributing guide. |
Codecov ReportAttention: Patch coverage is
Additional details and impacted files@@ Coverage Diff @@
## main #193 +/- ##
==========================================
+ Coverage 65.16% 65.18% +0.01%
==========================================
Files 52 52
Lines 3333 3323 -10
==========================================
- Hits 2172 2166 -6
+ Misses 1161 1157 -4
Flags with carried forward coverage won't be shown. Click here to find out more. ☔ View full report in Codecov by Sentry. |
Description
Behavior changes are not always behavior deprecation changes. However, a lot of the verbiage and messaging around behavior flags suggested they only support deprecating changes. This PR updates this verbiage to allow for more types of behavior changes, e.g. changing how we do something (
pg_catalog
usage indbt-redshift
) or allowing users to opt-in to new features that will be fully supported in dbt as the data platform matures the feature (Iceberg usage indbt-snowflake
).I'm adding
Skip Changelog
as the intent is already captured in a previous changelog; it would be duplicative.Checklist
changie new
to create a changelog entry