Merge branch 'current' into emdash

website/docs/docs/dbt-versions/release-notes.md

@@ -20,6 +20,31 @@ Release notes are grouped by month for both multi-tenant and virtual private clo
 
 ## October 2024
 
+<Expandable alt_header="Coalesce 2024 announcements">
+
+  Documentation for new features and functionality announced at Coalesce 2024:
+
+  - Iceberg table support for [Snowflake](https://docs.getdbt.com/reference/resource-configs/snowflake-configs#iceberg-table-format)
+  - [Athena](https://docs.getdbt.com/reference/resource-configs/athena-configs) and [Teradata](https://docs.getdbt.com/reference/resource-configs/teradata-configs) adapter support in dbt Cloud
+  - dbt Cloud now hosted on [Azure](https://docs.getdbt.com/docs/cloud/about-cloud/access-regions-ip-addresses)
+  - Get comfortable with [Versionless dbt Cloud](https://docs.getdbt.com/docs/dbt-versions/versionless-cloud)
+  - Scalable [microbatch incremental models](https://docs.getdbt.com/docs/build/incremental-microbatch)
+  - Advanced CI [features](https://docs.getdbt.com/docs/deploy/advanced-ci)
+  - [Linting with CI jobs](https://docs.getdbt.com/docs/deploy/continuous-integration#sql-linting)
+  - dbt Assist is now [dbt Copilot](https://docs.getdbt.com/docs/cloud/dbt-copilot)
+  - Developer blog on [Snowflake Feature Store and dbt: A bridge between data pipelines and ML](https://docs.getdbt.com/blog/snowflake-feature-store)
+  - New [Quickstart for dbt Cloud CLI](https://docs.getdbt.com/guides/dbt-cloud-cli?step=1)
+  - [Auto-exposures with Tableau](https://docs.getdbt.com/docs/collaborate/auto-exposures)
+  - Semantic Layer integration with [Excel desktop and M365](https://docs.getdbt.com/docs/cloud-integrations/semantic-layer/excel)
+  - [Data health tiles](https://docs.getdbt.com/docs/collaborate/data-tile)
+  - [Semantic Layer and Cloud IDE integration](https://docs.getdbt.com/docs/build/metricflow-commands#metricflow-commands)
+  - Query history in [Explorer](https://docs.getdbt.com/docs/collaborate/model-query-history#view-query-history-in-explorer)
+  - Semantic Layer Metricflow improvements, including [improved granularity and custom calendar](https://docs.getdbt.com/docs/build/metricflow-time-spine#custom-calendar) 
+  - [Python SDK](https://docs.getdbt.com/docs/dbt-cloud-apis/sl-python) is now generally available 
+
+</Expandable>
+
+
 - **New**: The [dbt Semantic Layer Python software development kit](/docs/dbt-cloud-apis/sl-python) is now [generally available](/docs/dbt-versions/product-lifecycles). It provides users with easy access to the dbt Semantic Layer with Python and enables developers to interact with the dbt Semantic Layer APIs to query metrics/dimensions in downstream tools.
 - **Enhancement**: You can now add a description to a singular data test in dbt Cloud Versionless. Use the [`description` property](/reference/resource-properties/description) to document [singular data tests](/docs/build/data-tests#singular-data-tests). You can also use [docs block](/docs/build/documentation#using-docs-blocks) to capture your test description. The enhancement will be included in upcoming dbt Core 1.9 release.
 - **New**: Introducing the [microbatch incremental model strategy](/docs/build/incremental-microbatch) (beta), available in dbt Cloud Versionless and will soon be supported in dbt Core 1.9. The microbatch strategy allows for efficient, batch-based processing of large time-series datasets for improved performance and resiliency, especially when you're working with data that changes over time (like new records being added daily). To enable this feature in dbt Cloud, set the `DBT_EXPERIMENTAL_MICROBATCH` environment variable to `true` in your project.

website/docs/reference/node-selection/defer.md

@@ -71,8 +71,6 @@ group by 1
 
 I want to test my changes. Nothing exists in my development schema, `dev_alice`.
 
-### test
-
 </File>
 
 <Tabs
@@ -139,6 +137,8 @@ Because `model_a` is unselected, dbt will check to see if `dev_alice.model_a` ex
 </TabItem>
 </Tabs>
 
+### test
+
 I also have a `relationships` test that establishes referential integrity between `model_a` and `model_b`:
 
 <File name='models/resources.yml'>