Merge remote-tracking branch 'upstream/current' into current

website/docs/docs/build/semantic-models.md

@@ -123,14 +123,18 @@ semantic_models:
     config:
       enabled: true | false
       group: some_group
+      meta:
+        some_key: some_value
 ```
 
 Semantic model config in `dbt_project.yml`:
 ```yml
-semantic_models:
+semantic-models:
   my_project_name:
     +enabled: true | false
     +group: some_group
+    +meta:
+      some_key: some_value
 ```
 
 </VersionBlock>

website/docs/docs/cloud/cloud-cli-installation.md

@@ -193,13 +193,13 @@ We recommend using virtual environments (venv) to namespace `cloud-cli`.
 2. Make sure you're in your virtual environment and run the following command to install the dbt Cloud CLI:
 
   ```bash
-  pip3 install dbt
+  pip install dbt --no-cache-dir
   ```
 
-3. (Optional) To revert back to dbt Core, first uninstall both the dbt Cloud CLI and dbt Core. Then reinstall dbt Core.
+3. (Optional) To revert to dbt Core, first uninstall both the dbt Cloud CLI and dbt Core. Then reinstall dbt Core.
 
   ```bash
-  pip3 uninstall dbt-core dbt
+  pip uninstall dbt-core dbt
   pip install dbt-adapter_name --force-reinstall
   ```
 

website/docs/docs/deploy/ci-jobs.md

@@ -15,7 +15,7 @@ dbt Labs recommends that you create your CI job in a dedicated dbt Cloud [deploy
 - You have a dbt Cloud account.
 - For the [Concurrent CI checks](/docs/deploy/continuous-integration#concurrent-ci-checks) and [Smart cancellation of stale builds](/docs/deploy/continuous-integration#smart-cancellation) features, your dbt Cloud account must be on the [Team or Enterprise plan](https://www.getdbt.com/pricing/).
 - You must be connected using dbt Cloud’s native Git integration with [GitHub](/docs/cloud/git/connect-github), [GitLab](/docs/cloud/git/connect-gitlab), or [Azure DevOps](/docs/cloud/git/connect-azure-devops).
-    - If you’re using GitLab, you must use a paid or self-hosted account which includes support for GitLab webhooks.
+    - With GitLab, you need a paid or self-hosted account which includes support for GitLab webhooks and [project access tokens](https://docs.gitlab.com/ee/user/project/settings/project_access_tokens.html). With GitLab Free, merge requests will invoke CI jobs but CI status updates (success or failure of the job) will not be reported back to GitLab. 
     - If you previously configured your dbt project by providing a generic git URL that clones using SSH, you must reconfigure the project to connect through dbt Cloud's native integration.
 
 

website/docs/guides/microsoft-fabric-qs.md

@@ -20,7 +20,7 @@ In this quickstart guide, you'll learn how to use dbt Cloud with Microsoft Fabri
 
 :::tip Public preview
 
-A public preview of dbt Cloud support for Microsoft Fabric in now available! 
+A public preview of Microsoft Fabric in dbt Cloud is now available! 
 
 :::
 

website/docs/reference/commands/deps.md

@@ -60,28 +60,28 @@ Update your versions in packages.yml, then run dbt deps
 
 <VersionBlock firstVersion="1.7">
 
-dbt generates the `package-lock.yml` file in the _project_root_ where `packages.yml` is recorded, which contains all the resolved packages, the first time you run `dbt deps`. Each subsequent run records the packages installed in this file. If the subsequent `dbt deps` runs contain no updated packages in `depenedencies.yml` or `packages.yml`, dbt-core installs from `package-lock.yml`. 
+dbt generates the `package-lock.yml` file in the _project_root_ where `packages.yml` is recorded, which contains all the resolved packages, the first time you run `dbt deps`. Each subsequent run records the packages installed in this file. If the subsequent `dbt deps` runs contain no updated packages in `dependencies.yml` or `packages.yml`, dbt-core installs from `package-lock.yml`. 
 
 When you update the package spec and run `dbt deps` again, the package-lock and package files update accordingly. You can run `dbt deps --lock` to update the `package-lock.yml` with the most recent dependencies from `packages`.
 
-The `--add` flag allows you to add a package to the `packages.yml` with configurable `--version` and `--source` information. The `--dry-run` flag, when set to `False`(default), recompiles the `package-lock.yml` file after a new package is added to the `packages.yml` file. Set the flag to `True` for the changes to not persist. 
+The `--add-package` flag allows you to add a package to the `packages.yml` with configurable `--version` and `--source` information. The `--dry-run` flag, when set to `False`(default), recompiles the `package-lock.yml` file after a new package is added to the `packages.yml` file. Set the flag to `True` for the changes to not persist. 
 
-Examples of the `--add` flag:
+Examples of the `--add-package` flag:
 ```shell
 # add package from hub (--source arg defaults to "hub")
-dbt deps add --package dbt-labs/dbt_utils --version 1.0.0
+dbt deps --add-package dbt-labs/dbt_utils@1.0.0
 
-# add package from hub with semantic version
-dbt deps add --package dbt-labs/snowplow --version ">=0.7.0,<0.8.0"
+# add package from hub with semantic version range
+dbt deps --add-package dbt-labs/snowplow@">=0.7.0,<0.8.0"
 
 # add package from git
-dbt deps add --package https://github.com/fivetran/dbt_amplitude --version v0.3.0 --source git 
+dbt deps --add-package https://github.com/fivetran/dbt_amplitude@v0.3.0 --source git
 
-# add package from local (--version not required for local)
-dbt deps add --package /opt/dbt/redshift --source local
+# add package from local
+dbt deps --add-package /opt/dbt/redshift --source local
 
-# add package to packages.yml WITHOUT updating package-lock.yml
-dbt deps add --package dbt-labs/dbt_utils --version 1.0.0 --dry-run True
+# add package to packages.yml and package-lock.yml WITHOUT actually installing dependencies
+dbt deps --add-package dbt-labs/dbt_utils@1.0.0 --dry-run
 
 ```
-</VersionBlock>
+</VersionBlock>