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
Hi, certstream locked the version constraint of Faker as Faker==0.9.1, which leads to a troubling scenario that its direct downstream project [doccano, orcamentos] has to lock Faker.
Could you please loosen the version constraint of Faker?
Benefit of this is that users using both of [doccano, orcamentos] and Faker can upgrade their third party libraries in a timely manner to reduce technical debts.
Solution
The dependency trees of your project and affected downstream projects are shown as follows.
Taking the version constraints of upstream and downstream projects into comprehensive consideration, you can
Loosen Faker==0.9.1 to be Faker>=0.9.1.
Loosen Faker==0.9.1 to be Faker==*.
Try to add an upper bound for Faker’ version constraint, according to your compatibility.
@klen Please let me know your choice. I can submit a PR to fix this issue.
Thanks for your attention.
Best,
Neolith
The text was updated successfully, but these errors were encountered:
Hi, certstream locked the version constraint of Faker as Faker==0.9.1, which leads to a troubling scenario that its direct downstream project [doccano, orcamentos] has to lock Faker.
Could you please loosen the version constraint of Faker?
Benefit of this is that users using both of [doccano, orcamentos] and Faker can upgrade their third party libraries in a timely manner to reduce technical debts.
Solution
The dependency trees of your project and affected downstream projects are shown as follows.
Taking the version constraints of upstream and downstream projects into comprehensive consideration, you can
@klen Please let me know your choice. I can submit a PR to fix this issue.
Thanks for your attention.
Best,
Neolith
The text was updated successfully, but these errors were encountered: