-
Notifications
You must be signed in to change notification settings - Fork 995
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Options for retaining previous behavior of dbt deps
for v1.7+
#5659
Conversation
The latest updates on your projects. Learn more about Vercel for Git ↗︎
|
dbt deps
dbt deps
for v1.7+
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
lgtm and correlates to this too: https://docs.getdbt.com/reference/commands/deps#predictable-package-installs. i just made some small tweaks to break up the paragraphs so it was easy to read/scan.
@@ -68,6 +68,8 @@ The `package-lock.yml` file should be committed in Git initially, and then updat | |||
|
|||
The `package-lock.yml` file includes a `sha1_hash` of the `packages` config. This enables dbt to detect if the `packages` config has been updated, and to rerun dependency resolution. To only check for changes to the `packages` config and update the lock file accordingly without installing those packages, provide the `--lock` flag (that is, `dbt deps --lock`). | |||
|
|||
### Forcing upgrades |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
💥
Previews
What are you changing in this pull request and why?
Resolves #5140
Problem
The default behavior of
dbt deps
changed in v1.7+, which can be surprising to long-time users ofdbt deps
.Solution
Document this in both the migration guide for v1.7 and anywhere else it is applicable (like here and/or here).
Checklist