Skip to content
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

Add notification when newer dbt versions are available #35

Open
ehmartens opened this issue Apr 21, 2022 · 3 comments
Open

Add notification when newer dbt versions are available #35

ehmartens opened this issue Apr 21, 2022 · 3 comments

Comments

@ehmartens
Copy link

Overview

I'm interested in adding a feature that would notify dbtenv users if a new version of dbt-core or the adapter they are using is available that fits within their project's versions requirements.

More info

I’ve noticed that if I have a version of the required dbt adapter installed that meets the version requirements in dbt_project.yml, I’ll never be prompted to see if there is a newer version of dbt or a dbt adapter that also meets those version requirements.

An example:

dbt_project.yml has:

require-dbt-version: [">=1.0.0", "<2.0.0"]

I have dbt-snowflake v1.0.0 installed. This meets the version requirement and therefore I run with dbt-snowflake==1.0.0

A new version of the adapter is released, with some bug fixes: version 1.0.1

Until I intentionally install dbt-snowflake==1.0.1, I won't ever upgrade (and may potentially not know that an upgrade is available)

The desired functionality would print some message when dbt runs indicating that there is a new version of dbt-snowflake that meets my version requirements. This would allow me to choose whether or not to upgrade the version I'm using.

@jaypeedevlin
Copy link
Contributor

How do you feel about when the adapter version remains the same and dbt-core is patched? Should we show a warning then? I've been thinking a lot about how we handle versions in a post 1.0 world and I don't want to derail your suggestion, but i have thoughts I'll share elsewhere hopefully soon!

@NiallRees
Copy link
Contributor

Both would be great @ehmartens @jaypeedevlin!

@ehmartens
Copy link
Author

@jaypeedevlin I see the benefit of both! I'm not sure if they should be the same PR or not, but I'm down to add both. Could definitely use some guidance. Also very interested in your thoughts on life > 1.0 :)

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

3 participants