Skip to content

Commit

Permalink
This branch was auto-updated!
Browse files Browse the repository at this point in the history
  • Loading branch information
github-actions[bot] authored Dec 18, 2023
2 parents 830ae22 + d229620 commit b5b63db
Showing 1 changed file with 5 additions and 1 deletion.
6 changes: 5 additions & 1 deletion website/docs/reference/commands/deps.md
Original file line number Diff line number Diff line change
Expand Up @@ -62,7 +62,11 @@ Update your versions in packages.yml, then run dbt deps

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`.
When you update the package spec and run `dbt deps` again, the `package-lock.yml` and `packages.yml` files update accordingly.

There are two flags related to `package-lock.yml`:
- `dbt deps --lock` — creates or updates the `package-lock.yml` file but does not install the packages.
- `dbt deps --upgrade` — creates or updates the `package-lock.yml` file with the most recent dependencies from `packages.yml`. Also install the packages unless the `--lock` flag is also passed.

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.

Expand Down

0 comments on commit b5b63db

Please sign in to comment.