Merge branch 'current' into revert-6668-revert-6666-jerco/update-comp…

…atible-release-track

website/docs/docs/core/docker-install.md

@@ -30,11 +30,23 @@ docker pull ghcr.io/dbt-labs/<db_adapter_name>:<version_tag>
 ### Running a dbt Docker image in a container
 
 The `ENTRYPOINT` for dbt Docker images is the command `dbt`. You can bind-mount your project to `/usr/app` and use dbt as normal:
+
+```
+docker run \
+--network=host \
+--mount type=bind,source=path/to/project,target=/usr/app \
+--mount type=bind,source=path/to/profiles.yml,target=/root/.dbt/profiles.yml \
+<dbt_image_name> \
+ls
+```
+
+Or 
+
 ```
 docker run \
 --network=host \
 --mount type=bind,source=path/to/project,target=/usr/app \
---mount type=bind,source=path/to/profiles.yml,target=/root/.dbt/ \
+--mount type=bind,source=path/to/profiles.yml.dbt,target=/root/.dbt/ \
 <dbt_image_name> \
 ls
 ```

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

@@ -20,6 +20,8 @@ Release notes are grouped by month for both multi-tenant and virtual private clo
 
 ## December 2024
 
+- **New**: The dbt Semantic Layer supports Sigma as a [partner integration](/docs/cloud-integrations/avail-sl-integrations), available in Preview. Refer to [Sigma](https://help.sigmacomputing.com/docs/configure-a-dbt-semantic-layer-integration) for more information.
+- **New**: The dbt Semantic Layer now supports Azure Single-tenant deployments. Refer to [Set up the dbt Semantic Layer](/docs/use-dbt-semantic-layer/setup-sl) for more information on how to get started.
 - **Fix**: Resolved intermittent issues in Single-tenant environments affecting Semantic Layer and query history.
 - **Fix**: [The dbt Semantic Layer](/docs/use-dbt-semantic-layer/dbt-sl) now respects the BigQuery [`execution_project` attribute](/docs/core/connect-data-platform/bigquery-setup#execution-project), including for exports.
 - **New**: [Model notifications](/docs/deploy/model-notifications) are now generally available in dbt Cloud. These notifications alert model owners through email about any issues encountered by models and tests as soon as they occur while running a job.

website/docs/docs/deploy/job-scheduler.md

@@ -11,9 +11,10 @@ The job scheduler is the backbone of running jobs in dbt Cloud, bringing power a
 The scheduler enables both cron-based and event-driven execution of dbt commands in the user’s data platform. Specifically, it handles:
 
 - Cron-based execution of dbt Cloud jobs that run on a predetermined cadence
-- Event-driven execution of dbt Cloud CI jobs triggered by pull requests to the dbt repo
+- Event-driven execution of dbt Cloud jobs that run based on the completion of another job ([trigger on job completion](/docs/deploy/deploy-jobs#trigger-on-job-completion))
+- Event-driven execution of dbt Cloud CI jobs triggered when a pull request is merged to the branch ([merge jobs](/docs/deploy/merge-jobs))
 - Event-driven execution of dbt Cloud jobs triggered by API
-- Event-driven execution of dbt Cloud jobs manually triggered by a user to "Run Now"
+- Event-driven execution of dbt Cloud jobs manually triggered by a user to **Run now**
 
 The scheduler handles various tasks including queuing jobs, creating temporary environments to run the dbt commands required for those jobs, providing logs for debugging and remediation, and storing dbt artifacts for direct consumption/ingestion by the Discovery API. 
 

website/docs/docs/deploy/model-notifications.md

@@ -36,17 +36,17 @@ version: 2
 
 groups:
   - name: finance
-    description: "Models related to the finance department"
     owner:
       # Email is required to receive model-level notifications, additional properties are also allowed.
       name: "Finance Team"
+      description: "Models related to the finance department"
       email: [email protected]
       favorite_food: donuts
 
   - name: marketing
-    description: "Models related to the marketing department"
     owner:
       name: "Marketing Team"
+      description: "Models related to the marketing department"
       email: [email protected]
       favorite_food: jaffles
 ```

website/docs/guides/redshift-qs.md

@@ -118,8 +118,7 @@ Now we are going to load our sample data into the S3 bucket that our Cloudformat
         id integer,
         user_id integer,
         order_date date,
-        status varchar(50),
-        _etl_loaded_at timestamp default current_timestamp
+        status varchar(50)
     );
 
     create table stripe.payment(
@@ -128,8 +127,7 @@ Now we are going to load our sample data into the S3 bucket that our Cloudformat
         paymentmethod varchar(50),
         status varchar(50),
         amount integer,
-        created date,
-        _batched_at timestamp default current_timestamp
+        created date
     );
     ```
 

website/snippets/_sl-partner-links.md

@@ -106,6 +106,21 @@ The following tools integrate with the dbt Semantic Layer:
     </a>
 </div>
 
+<div className="card-container">
+  <Card
+    title="Sigma (Preview)"
+    body="Connect Sigma to the dbt Semantic Layer to allow you to leverage your predefined dbt metrics in Sigma workbooks."
+    link="https://help.sigmacomputing.com/docs/configure-a-dbt-semantic-layer-integration"
+    icon="sigma"/>
+    <a href="https://help.sigmacomputing.com/docs/configure-a-dbt-semantic-layer-integration"
+    className="external-link"
+      target="_blank"
+      rel="noopener noreferrer">
+      <Icon name='fa-external-link' />
+    </a>
+</div>
+
+
 <div className="card-container">
   <Card
     title="Steep"

website/snippets/_v2-sl-prerequisites.md

@@ -1,5 +1,6 @@
-- Have a dbt Cloud Team or Enterprise account. Single-tenant accounts should contact their account representative for setup.
-- Ensure your production and development environments use [dbt version 1.6 or higher](/docs/dbt-versions/upgrade-dbt-version-in-cloud).
+- Have a dbt Cloud Team or Enterprise account.
+   - Available on all [tenant configurations](/docs/cloud/about-cloud/tenancy). Single-tenant accounts should contact your account representative for setup.
+- Ensure your production and development environments are on a [supported dbt version](/docs/dbt-versions/upgrade-dbt-version-in-cloud).
 - Use Snowflake, BigQuery, Databricks, or Redshift.
 -  Create a successful run in the environment where you configure the Semantic Layer. 
    - **Note:** Semantic Layer supports querying in Deployment environments; development querying is coming soon.

website/snippets/cloud-feature-parity.md

@@ -9,7 +9,7 @@ The following table outlines which dbt Cloud features are supported on the diffe
 | dbt Copilot                   | ✅               | ✅                     | ✅                  | ✅                  |
 | dbt Explorer                  | ✅               | ✅                     | ✅                  | ✅                  |
 | dbt Mesh                      | ✅               | ✅                     | ✅                  | ✅                  |
-| dbt Semantic Layer            | ✅               | ✅ (Upon request)      | ✅                  | ❌                  |
+| dbt Semantic Layer            | ✅               | ✅ (Upon request)      | ✅                  | ✅                  |
 | Discovery API                 | ✅               | ✅                     | ✅                  | ✅                  |  
 | IP restrictions               | ✅               | ✅                     | ✅                  | ✅                  |
 | Job scheduler                 | ✅               | ✅                     | ✅                  | ✅                  |