Merge branch 'current' into add-meta-tag

.github/CODEOWNERS

@@ -4,14 +4,14 @@
 *      @dbt-labs/product-docs
 
 # Adapter & Package Development Docs
-/website/docs/docs/supported-data-platforms.md                @dbt-labs/product-docs @dataders
-/website/docs/reference/warehouse-setups                      @dbt-labs/product-docs @dataders
+/website/docs/docs/supported-data-platforms.md                @dbt-labs/product-docs @amychen1776 
+/website/docs/reference/warehouse-setups                      @dbt-labs/product-docs @amychen1776 
 # `resource-configs` contains more than just warehouse setups
-/website/docs/reference/resource-configs/*-configs.md           @dbt-labs/product-docs @dataders
-/website/docs/guides/advanced/adapter-development              @dbt-labs/product-docs @dataders @dbeatty10
+/website/docs/reference/resource-configs/*-configs.md           @dbt-labs/product-docs @amychen1776 
+/website/docs/guides/advanced/adapter-development              @dbt-labs/product-docs @amychen1776
 
-/website/docs/guides/building-packages                          @dbt-labs/product-docs @amychen1776 @dataders @dbeatty10
-/website/docs/guides/creating-new-materializations              @dbt-labs/product-docs @dataders @dbeatty10
+/website/docs/guides/building-packages                          @dbt-labs/product-docs @amychen1776
+/website/docs/guides/creating-new-materializations              @dbt-labs/product-docs
 
 # Require approval from the Multicell team when making
 # changes to the public facing migration documentation.

.github/workflows/vale.yml

@@ -29,11 +29,11 @@ jobs:
           python-version: '3.x'
 
       - name: Install Vale
-        run: pip install vale==2.27.0  # Install a stable version of Vale
+        run: pip install vale==3.9.1.0  # Install a stable version of Vale
 
       - name: Get changed files
         id: changed-files
-        uses: tj-actions/changed-files@v34
+        uses: tj-actions/changed-files@v45
         with:
           files: |
             website/**/*.md
@@ -63,10 +63,9 @@ jobs:
         uses: errata-ai/vale-action@reviewdog
         with:
           token: ${{ secrets.GITHUB_TOKEN }}
-          reporter: github-check
+          reporter: github-pr-review
           files: ${{ steps.changed-files.outputs.all_changed_and_modified_files }}
           separator: ' '
-          version: '2.27.0'
 
 #      - name: Post summary comment
 #        if: ${{ steps.changed-files.outputs.any_changed == 'true' }}

styles/Vocab/EN/accept.txt → styles/config/vocabularies/EN/accept.txt

@@ -65,3 +65,5 @@ N/A
 pseudocolumn
 yml
 values=
+dbt v\\d+\\.\\d+
+v\\d+\\.\\d+

styles/custom/Typos.yml

@@ -37,3 +37,5 @@ tokens:
   - '\w+/\w+|\w+-\w+|n/a'
   - 'n/a' 
   - 'N/A'
+  - 'dbt v\\d+\\.\\d+'
+  - 'v\\d+\\.\\d+ '

website/blog/2022-04-14-add-ci-cd-to-bitbucket.md

@@ -197,7 +197,7 @@ Reading the file over, you can see that we:
 
 In summary, anytime anything is pushed to main, we’ll ensure our production database reflects the dbt transformation, and we’ve saved the resulting artifacts to defer to.
 
-> ❓ **What are artifacts and why should I defer to them?** dbt artifacts are metadata of the last run - what models and tests were defined, which ones ran successfully, and which failed. If a future dbt run is set to ***defer*** to this metadata, it means that it can select models and tests to run based on their state, including and especially their difference from the reference metadata. See [Artifacts](https://docs.getdbt.com/reference/artifacts/dbt-artifacts), [Selection methods: “state”](https://docs.getdbt.com/reference/node-selection/methods#the-state-method), and [Caveats to state comparison](https://docs.getdbt.com/reference/node-selection/state-comparison-caveats) for details.
+> ❓ **What are artifacts and why should I defer to them?** dbt artifacts are metadata of the last run - what models and tests were defined, which ones ran successfully, and which failed. If a future dbt run is set to ***defer*** to this metadata, it means that it can select models and tests to run based on their state, including and especially their difference from the reference metadata. See [Artifacts](https://docs.getdbt.com/reference/artifacts/dbt-artifacts), [Selection methods: “state”](https://docs.getdbt.com/reference/node-selection/methods#state), and [Caveats to state comparison](https://docs.getdbt.com/reference/node-selection/state-comparison-caveats) for details.
 
 ### Slim Continuous Integration: Retrieve the artifacts and do a state-based run
 

website/dbt-versions.js

@@ -20,6 +20,7 @@ exports.versions = [
   },
   {
     version: "1.9",
+    customDisplay: "1.9 (Compatible)",
     EOLDate: "2025-12-08",
   },
   {

website/docs/best-practices/how-we-style/5-how-we-style-our-yaml.md

@@ -7,6 +7,7 @@ id: 5-how-we-style-our-yaml
 
 - 2️⃣ Indents should be two spaces
 - ➡️ List items should be indented
+- 🔠 List items with a single entry can be a string. For example, `'select': 'other_user'`, but it's best practice to provide the argument as an explicit list. For example, `'select': ['other_user']`
 - 🆕 Use a new line to separate list items that are dictionaries where appropriate
 - 📏 Lines of YAML should be no longer than 80 characters.
 - 🛠️ Use the [dbt JSON schema](https://github.com/dbt-labs/dbt-jsonschema) with any compatible IDE and a YAML formatter (we recommend [Prettier](https://prettier.io/)) to validate your YAML files and format them automatically.