Merge pull request #468 from dbt-labs/repo-sync

REPO SYNC - Public to Private

website/docs/docs/build/unit-tests.md

@@ -11,7 +11,7 @@ keywords:
 
 Support for unit testing dbt models is available to dbt Cloud customers who have chosen to ["Keep on latest version"](/docs/dbt-versions/upgrade-dbt-version-in-cloud#keep-on-latest-version). This feature is currently available in beta, and supports all dbt-Labs-maintained adapters, with more adapter availability rolling out through March.
 
-For dbt Core, unit tests will be available in v1.8, planned for spring 2024. The v1.8.0-b1 release of `dbt-core` & dbt Labs-maintained adapters is available as of February 29.
+For dbt Core, the v1.8.0-b1 release of `dbt-core` and dbt Labs-maintained adapters are available now.
 
 :::
 

website/docs/docs/core/connect-data-platform/sqlite-setup.md

@@ -85,7 +85,7 @@ your_profile_name:
 
   - SQLite does not allow views in one schema (i.e. database file) to reference objects in another schema. You'll get this error from SQLite: "view [someview] cannot reference objects in database [somedatabase]". You must set `materialized='table'` in models that reference other schemas.
 
-- Materializations are simplified: they drop and re-create the model, instead of doing the backup-and-swap-in new model that the other dbt database adapters support. This choice was made because SQLite doesn't support `DROP ... CASCADE` or `ALTER VIEW` or provide information about relation dependencies in something information_schema-like. These limitations make it really difficult to make the backup-and-swap-in functionality work properly. Given how SQLite aggressively [locks](https://sqlite.org/lockingv3.html the database anyway, it's probably not worth the effort.
+- Materializations are simplified: they drop and re-create the model, instead of doing the backup-and-swap-in new model that the other dbt database adapters support. This choice was made because SQLite doesn't support `DROP ... CASCADE` or `ALTER VIEW` or provide information about relation dependencies in something information_schema-like. These limitations make it really difficult to make the backup-and-swap-in functionality work properly. Given how SQLite aggressively [locks](https://sqlite.org/lockingv3.html) the database anyway, it's probably not worth the effort.
 
 ## SQLite Extensions
 

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

@@ -10,7 +10,6 @@ displayed_sidebar: "docs"
 - Changelog (coming soon)
 - [dbt Core CLI Installation guide](/docs/core/installation-overview)
 - [Cloud upgrade guide](/docs/dbt-versions/upgrade-dbt-version-in-cloud)
-- Release schedule (coming soon)
 
 ## What to know before upgrading
 

website/docs/docs/supported-data-platforms.md

@@ -30,8 +30,8 @@ There are two types of adapters available today:
 1. Does it work?
 2. Does anyone "own" the code, or is anyone liable for ensuring it works?
 3. Do bugs get fixed quickly?
-4. Does it stay up-to-date with new Core features?
+4. Does it stay up-to-date with new dbt Core features?
 5. Is the usage substantial enough to self-sustain?
-pendency on this library?
+6. Do other known projects depend on this library?
 
-</details>
+</details>

website/docs/guides/custom-cicd-pipelines.md

@@ -261,8 +261,8 @@ jobs:
       DBT_JOB_BRANCH: ${{ github.ref_name }}
 
     steps:
-      - uses: "actions/checkout@v3"
-      - uses: "actions/setup-python@v4"
+      - uses: "actions/checkout@v4"
+      - uses: "actions/setup-python@v5"
         with:
           python-version: "3.9"
       - name: Run dbt Cloud job

website/docs/reference/dbt-jinja-functions/builtins.md

@@ -31,7 +31,7 @@ From dbt v1.5 and higher, use the following macro to extract user-provided argum
 ```
 {% macro ref() %}
 -- extract user-provided positional and keyword arguments
-  {% set version = kwargs.get('version') %}
+  {% set version = kwargs.get('version') or kwargs.get('v') %}
   {% set packagename = none %}
   {%- if (varargs | length) == 1 -%}
     {% set modelname = varargs[0] %}

website/snippets/_adapters-trusted.md

@@ -11,6 +11,17 @@
   padding: 0rem 0.75rem; display:inline-block'>dbt Core</div>"
     icon="alloydb"/>
 
+<Card
+    title="Apache Spark"
+    body="<ul><li><a href='/docs/cloud/connect-data-platform/connect-apache-spark'>Set up in dbt Cloud </a> <br /></li><li><a href='/docs/core/connect-data-platform/spark-setup'>Install with dbt Core </a> </li></ul> <br /> <a href=https://badge.fury.io/py/dbt-spark><img src=https://badge.fury.io/py/dbt-spark.svg/></a><br /><br /><div style='background: #E5E7EB;
+  border-radius: 1.5rem;
+  color:#262A38;
+  padding: 0rem 0.75rem; display:inline-block'>dbt Cloud</div> <div style='  background: #E5E7EB;
+  border-radius: 1.5rem;
+  color:#262A38;
+  padding: 0rem 0.75rem; display:inline-block'>dbt Core</div>"
+    icon="apache-spark"/>
+
  <Card
     title="Athena"
     body="<ul><li><a href='/docs/core/connect-data-platform/athena-setup'>Install with dbt Core </a> </li> </ul><br /><br /><a href=https://badge.fury.io/py/dbt-athena-community><img src=https://badge.fury.io/py/dbt-athena-community.svg/></a><br /><br /><div style='background: #E5E7EB;
@@ -103,7 +114,7 @@
   border-radius: 1.5rem;
   color:#262A38;
   padding: 0rem 0.75rem; display:inline-block'>dbt Core</div>"
-    icon="redshift"/>
+    icon="postgres"/>
 
 <Card
     title="Redshift"
@@ -127,17 +138,6 @@
   padding: 0rem 0.75rem; display:inline-block'>dbt Core</div>"
     icon="snowflake"/>
 
-<Card
-    title="Spark"
-    body="<ul><li><a href='/docs/cloud/connect-data-platform/connect-apache-spark'>Set up in dbt Cloud </a> <br /></li><li><a href='/docs/core/connect-data-platform/spark-setup'>Install with dbt Core </a> </li></ul> <br /> <a href=https://badge.fury.io/py/dbt-spark><img src=https://badge.fury.io/py/dbt-spark.svg/></a><br /><br /><div style='background: #E5E7EB;
-  border-radius: 1.5rem;
-  color:#262A38;
-  padding: 0rem 0.75rem; display:inline-block'>dbt Cloud</div> <div style='  background: #E5E7EB;
-  border-radius: 1.5rem;
-  color:#262A38;
-  padding: 0rem 0.75rem; display:inline-block'>dbt Core</div>"
-    icon="databricks"/>
-
 <Card
     title="Starburst/Trino"
     body="<ul><li><a href='/docs/cloud/connect-data-platform/connect-starburst-trino'>Set up in dbt Cloud </a> <br /></li><li><a href='/docs/core/connect-data-platform/trino-setup'>Install with dbt Core  </a> </li></ul> <br /> <a href=https://badge.fury.io/py/dbt-trino><img src=https://badge.fury.io/py/dbt-trino.svg/></a><br /><br /><div style='background: #E5E7EB;

website/snippets/core-versions-table.md

@@ -1,7 +1,8 @@
 ### Latest releases
 
-|                      dbt Core                        | Initial release |      Support level and end date      |
-|:----------------------------------------------------:|:---------------:|:-------------------------------------:|
+|                      dbt Core                                 | Initial release |      Support level and end date      |
+|:-------------------------------------------------------------:|:---------------:|:-------------------------------------:|
+| [**v1.8**](/docs/dbt-versions/core-upgrade/upgrading-to-v1.8) | April 2024    | Beta                              |
 | [**v1.7**](/docs/dbt-versions/core-upgrade/upgrading-to-v1.7) | Nov 2, 2023   | <b>Active &mdash; Nov 1, 2024</b> | 
 | [**v1.6**](/docs/dbt-versions/core-upgrade/upgrading-to-v1.6) | Jul 31, 2023  | Critical &mdash; Jul 30, 2024 |  
 | [**v1.5**](/docs/dbt-versions/core-upgrade/upgrading-to-v1.5) | Apr 27, 2023  | Critical &mdash; Apr 27, 2024 |

website/snippets/quickstarts/change-way-model-materialized.md

@@ -19,8 +19,8 @@ By default, everything gets created as a view. You can override that at the dire
       models:
         jaffle_shop:
           +materialized: table
-        example:
-          +materialized: view
+          example:
+            +materialized: view
       ```
 
       </File>