You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
When click==8.1.4 was released, our code quality workflows using mypy began failing. An issue has been created on the click repository.
Solution
The solution is to exclude, for the time being, click==8.1.4. Currently our click dependency is set to click>=7.0,<9.0, this should become on main click>=8.1.1,<8.1.4.
Backports
We need to backport this fix to 1.3.latest, 1.4.latest, and 1.5.latest. For the backports we should update the dependency from click>=7.0,<9.0 to click>=7.0,<8.1.4. The reason for the different specification in the backports is that we already support click 7.x in these earlier versions. Dropping support for click 7.x could be problematic if people are installing dbt-core alongside other dependencies which limit click to 7.x., then dropping support for click 7.x would represent a breaking change (and we shouldn't do this in a patch version).
The text was updated successfully, but these errors were encountered:
Problem
When
click==8.1.4
was released, our code quality workflows usingmypy
began failing. An issue has been created on the click repository.Solution
The solution is to exclude, for the time being,
click==8.1.4
. Currently our click dependency is set toclick>=7.0,<9.0
, this should become on mainclick>=8.1.1,<8.1.4
.Backports
We need to backport this fix to
1.3.latest
,1.4.latest
, and1.5.latest
. For the backports we should update the dependency fromclick>=7.0,<9.0
toclick>=7.0,<8.1.4
. The reason for the different specification in the backports is that we already supportclick 7.x
in these earlier versions. Dropping support forclick 7.x
could be problematic if people are installing dbt-core alongside other dependencies which limit click to7.x.
, then dropping support forclick 7.x
would represent a breaking change (and we shouldn't do this in a patch version).The text was updated successfully, but these errors were encountered: