Merge branch 'current' into joey-Blog-CTA-to-Coalesce-2024

website/docs/docs/dbt-versions/core-upgrade/01-upgrading-to-v1.8.md

@@ -60,21 +60,30 @@ dbt test --select "test_type:data"           # run all data tests
 
 Unit tests are defined in YML files in your `models/` directory and are currently only supported on SQL models. To distinguish between the two, the `tests:` config has been renamed to `data_tests:`. Both are currently supported for backward compatibility.
 
-### The `--empty` flag
+#### New `data_tests:` syntax
 
-The [`run`](/reference/commands/run#the-`--empty`-flag) and [`build`](/reference/commands/build#the---empty-flag) commands now support the `--empty` flag for building schema-only dry runs. The `--empty` flag limits the refs and sources to zero rows. dbt will still execute the model SQL against the target data warehouse but will avoid expensive reads of input data. This validates dependencies and ensures your models will build properly.
+The `tests:` syntax is changing to reflect the addition of unit tests. Start migrating your [data test](/docs/build/data-tests#new-test-syntax) YML to use `data_tests:` after you upgrade to v1.8 to prevent issues in the future.
+
+```yml
+
+models:
+  - name: orders
+    columns:
+      - name: order_id
+        data_tests:
+          - unique
+          - not_null
 
-### Additional attributes in run_results.json
 
-The run_results.json now includes three attributes related to the `applied` state that complement `unique_id`:
+```
 
-- `compiled`: Boolean entry of the node compilation status (`False` after parsing, but `True` after compiling).
-- `compiled_code`: Rendered string of the code that was compiled (empty after parsing, but full string after compiling).
-- `relation_name`: The fully-qualified name of the object that was (or will be) created/updated within the database.
+### The `--empty` flag
 
+The [`run`](/reference/commands/run#the-`--empty`-flag) and [`build`](/reference/commands/build#the---empty-flag) commands now support the `--empty` flag for building schema-only dry runs. The `--empty` flag limits the refs and sources to zero rows. dbt will still execute the model SQL against the target data warehouse but will avoid expensive reads of input data. This validates dependencies and ensures your models will build properly.
 
 ## Quick hits
 
 - [Global config flags](/reference/global-configs/about-global-configs) are deprecated from the [`profiles.yml`](/docs/core/connect-data-platform/profiles.yml) file and should be moved to the [`dbt_project.yml`](/reference/dbt_project.yml).
 - A new subcategory of flags has been created for [legacy behaviors](/reference/global-configs/legacy-behaviors).
 - The [`--indirect_selection`](/reference/global-configs/indirect-selection) flag used with `dbt test` or `dbt build` configures which tests to run for the nodes you specify.
+

website/docs/docs/dbt-versions/core-upgrade/02-upgrading-to-v1.7.md

@@ -60,6 +60,15 @@ dbt Core v1.5 introduced model governance which we're continuing to refine.  v1.
 - **[Type aliasing for model contracts](/reference/resource-configs/contract):** dbt will use each adapter's built-in type aliasing for user-provided data types—meaning you can now write `string` always, and dbt will translate to `text` on Postgres/Redshift. This is "on" by default, but you can opt-out.
 - **[Raise warning for numeric types](/reference/resource-configs/contract):** Because of issues when putting `numeric` in model contracts without considering that default values such as `numeric(38,0)` might round decimals accordingly. dbt will now warn you if it finds a numeric type without specified precision/scale.
 
+### Additional attributes in run_results.json
+
+The run_results.json now includes three attributes related to the `applied` state that complement `unique_id`:
+
+- `compiled`: Boolean entry of the node compilation status (`False` after parsing, but `True` after compiling).
+- `compiled_code`: Rendered string of the code that was compiled (empty after parsing, but full string after compiling).
+- `relation_name`: The fully-qualified name of the object that was (or will be) created/updated within the database.
+
+
 ### Quick hits
 
 With these quick hits, you can now:

website/docs/reference/artifacts/run-results-json.md

@@ -42,7 +42,7 @@ import RowsAffected from '/snippets/_run-result.md';
 
 <!-- this partial comes from https://github.com/dbt-labs/docs.getdbt.com/tree/current/website/snippets/_run-result-->
 
-<VersionBlock firstVersion="1.8">
+<VersionBlock firstVersion="1.7">
 
 The run_results.json includes three attributes related to the `applied` state that complement `unique_id`: