Merge branch 'current' into mirnawong1-patch-21

website/docs/docs/collaborate/govern/model-versions.md

@@ -393,6 +393,32 @@ dbt.exceptions.AmbiguousAliasError: Compilation Error
 We opted to use `generate_alias_name` for this functionality so that the logic remains accessible to end users, and could be reimplemented with custom logic.
 :::
 
+### Run a model with multiple versions
+
+To run a model with multiple versions, you can use the [`--select` flag](/reference/node-selection/syntax). For example:
+
+- Run all versions of `dim_customers`:
+
+  ```bash
+  dbt run --select dim_customers # Run all versions of the model
+  ```
+- Run only version 2 of `dim_customers`:
+
+  You can use either of the following commands (both achieve the same result):
+
+  ```bash
+    dbt run --select dim_customers.v2 # Run a specific version of the model
+    dbt run --select dim_customers_v2 # Alternative syntax for the specific version
+  ```
+
+- Run the latest version of `dim_customers` using the `--select` flag shorthand:
+
+  ```bash
+  dbt run -s dim_customers version:latest # Run the latest version of the model
+  ```
+
+These commands provide flexibility in managing and executing different versions of a dbt model.
+
 ### Optimizing model versions
 
 How you define each model version is completely up to you. While it's easy to start by copy-pasting from one model's SQL definition into another, you should think about _what actually is changing_ from one version to another.

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

@@ -6,9 +6,9 @@ meta:
   authors: 'Vertica (Former authors: Matthew Carter, Andy Regan, Andrew Hedengren)'
   github_repo: 'vertica/dbt-vertica'
   pypi_package: 'dbt-vertica'
-  min_core_version: 'v1.4.0 and newer'
+  min_core_version: 'v1.6.0 and newer'
   cloud_support: 'Not Supported'
-  min_supported_version: 'Vertica 12.0.0'
+  min_supported_version: 'Vertica 23.4.0'
   slack_channel_name: 'n/a'
   slack_channel_link: 'https://www.getdbt.com/community/'
   platform_name: 'Vertica'

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

@@ -41,6 +41,3 @@ The following are **Trusted adapters** ✓ you can connect to in dbt Core:
 import AdaptersTrusted from '/snippets/_adapters-trusted.md';
 
 <AdaptersTrusted />
-
-<br/> * Install these adapters using dbt Core as they're not currently supported in dbt Cloud. <br />
-

website/docs/docs/trusted-adapters.md

@@ -25,12 +25,12 @@ Refer to the [Build, test, document, and promote adapters](/guides/adapter-creat
 
 ### Trusted vs Verified
 
-The Verification program exists to highlight adapters that meets both of the following criteria:
+The Verification program exists to highlight adapters that meet both of the following criteria:
 
 - the guidelines given in the Trusted program,
 - formal agreements required for integration with dbt Cloud
 
-For more information on the Verified Adapter program, reach out the [dbt Labs partnerships team](mailto:[email protected])
+For more information on the Verified Adapter program, reach out to the [dbt Labs partnerships team](mailto:[email protected])
 
 ### Trusted adapters
 

website/docs/reference/resource-properties/latest_version.md

@@ -25,6 +25,8 @@ The latest version of this model. The "latest" version is relevant for:
 
 This value can be a string or a numeric (integer or float) value. It must be one of the [version identifiers](/reference/resource-properties/versions#v) specified in this model's list of `versions`.
 
+To run the latest version of a model, you can use the [`--select` flag](/reference/node-selection/syntax). Refer to [Model versions](/docs/collaborate/govern/model-versions#run-a-model-with-multiple-versions) for more information and syntax.
+
 ## Default
 
 If not specified for a versioned model, `latest_version` defaults to the largest [version identifier](/reference/resource-properties/versions#v): numerically greatest (if all version identifiers are numeric), otherwise the alphabetically last (if they are strings).

website/docs/reference/resource-properties/versions.md

@@ -43,6 +43,9 @@ The value of the version identifier is used to order versions of a model relativ
 
 In general, we recommend that you use a simple "major versioning" scheme for your models: `1`, `2`, `3`, and so on, where each version reflects a breaking change from previous versions. You are able to use other versioning schemes. dbt will sort your version identifiers alphabetically if the values are not all numeric. You should **not** include the letter `v` in the version identifier, as dbt will do that for you.
 
+To run a model with multiple versions, you can use the [`--select` flag](/reference/node-selection/syntax). Refer to [Model versions](/docs/collaborate/govern/model-versions#run-a-model-with-multiple-version) for more information and syntax.
+
+
 ### `defined_in`
 
 The name of the model file (excluding the file extension, e.g. `.sql` or `.py`) where the model version is defined.

website/snippets/_adapters-trusted.md

@@ -1,18 +1,23 @@
 <div className="grid--4-col">
 
 <Card
-    title="Athena*"
+    title="Athena"
     body="<a href='/docs/core/connect-data-platform/athena-setup'><img src='/img/icons/dbt-bit.svg' width='7%'/>Install with dbt Core </a> <br /><br /><a href=https://badge.fury.io/py/dbt-athena-community><img src=https://badge.fury.io/py/dbt-athena-community.svg/></a>"
     icon="athena"/>
 
 <Card
-    title="Materialize*"
+    title="Glue"
+    body="<a href='/docs/core/connect-data-platform/glue-setup'><img src='/img/icons/dbt-bit.svg' width='7%'/>Install with dbt Core </a> <br /><br /><a href=https://badge.fury.io/py/dbt-glue><img src=https://badge.fury.io/py/dbt-glue.svg/></a>"
+    icon="glue"/>
+
+<Card
+    title="Materialize"
     body="<a href='/docs/core/connect-data-platform/materialize-setup'><img src='/img/icons/dbt-bit.svg' width='7%'/>Install with dbt Core </a> <br /><br /><a 
     href=https://badge.fury.io/py/dbt-materialize><img src=https://badge.fury.io/py/dbt-materialize.svg/></a>"
     icon="materialize"/>
 
 <Card
-    title="Oracle Autonomous Database*"
+    title="Oracle Autonomous Database"
     body="<a href='/docs/core/connect-data-platform/oracle-setup'><img src='/img/icons/dbt-bit.svg' width='7%'/>Install with dbt Core </a> <br /><br /><a 
     href=https://badge.fury.io/py/dbt-oracle><img src=https://badge.fury.io/py/dbt-oracle.svg/></a>"
     icon="oracle"/>

website/snippets/_adapters-verified.md

@@ -15,7 +15,7 @@
     icon="databricks"/>
 
 <Card
-    title="Dremio*"
+    title="Dremio"
     body="<a href='/docs/core/connect-data-platform/dremio-setup'><img src='/img/icons/dbt-bit.svg' width='7%'/>Install with dbt Core  </a> <br /><br /> <a href=https://badge.fury.io/py/dbt-dremio><img src=https://badge.fury.io/py/dbt-dremio.svg/><br />"
     icon="dremio"/>
 
@@ -49,11 +49,11 @@
     body="<a href='/guides/microsoft-fabric?step=1'><img src='/img/icons/dbt-bit.svg' width='7%'/>Set up in dbt Cloud </a> <br /><a href='/docs/core/connect-data-platform/fabric-setup'><img src='/img/icons/dbt-bit.svg' width='7%'/>Install with dbt Core  </a> <br /><br /> <a href=https://badge.fury.io/py/dbt-fabric><img src=https://badge.fury.io/py/dbt-fabric.svg/></a>"
     icon="fabric"/>
 <Card
-    title="Azure Synapse*"
+    title="Azure Synapse"
     body="<a href='/docs/core/connect-data-platform/azuresynapse-setup'><img src='/img/icons/dbt-bit.svg' width='7%'/>Install with dbt Core  </a> <br /><br /> <a href=https://badge.fury.io/py/dbt-synapse><img src=https://badge.fury.io/py/dbt-synapse.svg/><br /> 🚧 Verification in progress"
     icon="rocket"/>
 <Card
-    title="Teradata*"
+    title="Teradata"
     body="<a href='/docs/core/connect-data-platform/teradata-setup'><img src='/img/icons/dbt-bit.svg' width='7%'/>Install with dbt Core  </a> <br /><br /> <a href=https://badge.fury.io/py/dbt-teradata><img src=https://badge.fury.io/py/dbt-teradata.svg/><br />"
     icon="teradata"/>