Merge branch 'current' into content/adapter-maintain-behavior-flags

website/docs/docs/build/dimensions.md

@@ -124,7 +124,7 @@ mf query --metrics users_created,users_deleted --group-by metric_time__year --or
 
 You can set `is_partition` for time to define specific time spans. Additionally, use the `type_params` section to set `time_granularity` to adjust aggregation details (hourly, daily, weekly, and so on).
 
-<Tabs>
+<Tabs queryString="dimension">
 
 <TabItem value="is_partition" label="is_partition">
 

website/docs/reference/commands/retry.md

@@ -10,6 +10,8 @@ Retry works with the following commands:
 
 - [`build`](/reference/commands/build)
 - [`compile`](/reference/commands/compile)
+- [`clone`](/reference/commands/clone)
+- [`docs generate`](/reference/commands/cmd-docs#dbt-docs-generate)
 - [`seed`](/reference/commands/seed)
 - [`snapshot`](/reference/commands/build)
 - [`test`](/reference/commands/test)

website/docs/reference/global-configs/behavior-changes.md

@@ -41,7 +41,12 @@ By contrast, behavior change migrations happen slowly, over the course of months
 
 These flags _must_ be set in the `flags` dictionary in `dbt_project.yml`. They configure behaviors closely tied to project code, which means they should be defined in version control and modified through pull or merge requests, with the same testing and peer review.
 
-The following example displays the current flags and their current default values in the latest dbt Cloud and dbt Core versions. To opt out of a specific behavior change, set the values of the flag to `False` in `dbt_project.yml`. You'll continue to see warnings for legacy behaviors that you have opted out of explicitly until you either resolve them (switch the flag to `True`) or choose to silence the warnings using the `warn_error_options.silence` flag.
+The following example displays the current flags and their current default values in the latest dbt Cloud and dbt Core versions. To opt out of a specific behavior change, set the values of the flag to `False` in `dbt_project.yml`. You will continue to see warnings for legacy behaviors you’ve opted out of, until you either:
+
+- Resolve the issue (by switching the flag to `True`)
+- Silence the warnings using the `warn_error_options.silence` flag
+
+Here's an example of the available behavior change flags with their default values:
 
 <File name='dbt_project.yml'>
 
@@ -50,6 +55,7 @@ flags:
   require_explicit_package_overrides_for_builtin_materializations: False
   require_model_names_without_spaces: False
   source_freshness_run_project_hooks: False
+  restrict_direct_pg_catalog_access: False
 ```
 
 </File>
@@ -61,7 +67,7 @@ When we use dbt Cloud in the following table, we're referring to accounts that h
 | require_explicit_package_overrides_for_builtin_materializations | 2024.04.141      | 2024.06.192         | 1.6.14, 1.7.14  | 1.8.0             |
 | require_resource_names_without_spaces                           | 2024.05.146      | TBD*                | 1.8.0           | 1.9.0             |
 | source_freshness_run_project_hooks                              | 2024.03.61       | TBD*                | 1.8.0           | 1.9.0             |
-| [Redshift] restrict_direct_pg_catalog_access                    | 2024.09.242      | TBD*                | dbt-redshift v1.9.0           | 1.9.0             |
+| [Redshift] [restrict_direct_pg_catalog_access](#redshift-restrict_direct_pg_catalog_access)    | 2024.09.242      | TBD*                | dbt-redshift v1.9.0           | 1.9.0             |
 
 When the dbt Cloud Maturity is "TBD," it means we have not yet determined the exact date when these flags' default values will change. Affected users will see deprecation warnings in the meantime, and they will receive emails providing advance warning ahead of the maturity date. In the meantime, if you are seeing a deprecation warning, you can either:
 - Migrate your project to support the new behavior, and then set the flag to `True` to stop seeing the warnings.

website/docs/reference/global-configs/usage-stats.md

@@ -25,6 +25,6 @@ For full transparency, you can see all the event definitions in [`tracking.py`](
     send_anonymous_usage_stats: False
   ```
 
-  dbt Core users can also use the` DO_NOT_TRACK` environment variable to enable or disable sending anonymous data. For more information, see [Environment variables](/docs/build/environment-variables).
+  dbt Core users can also use the `DO_NOT_TRACK` environment variable to enable or disable sending anonymous data. For more information, see [Environment variables](/docs/build/environment-variables).
 
   `DO_NOT_TRACK=1` is the same as `DBT_SEND_ANONYMOUS_USAGE_STATS=False`