Hi there! Upgradvisor has identified that one of your repository’s dependencies has a newer version available, and we recommend you upgrade.
Your code currently pins filetype 1.0.9 when filetype 1.2.0 is available. The attached graph shows the dependency path of your repository relative to filetype. Your code is shown in green (each node is a method), and your code calling filetype is shown in orange. Changes between version 1.0.9 and 1.2.0 are shown as starred.
From the attached graph and manual tracing conducted by the team, between the two versions of filetype, the only major change is utils.get_bytes, in which it only adds an hasattr method to check if the parameter obj exists a read parameter. This change does not affect lbry-sdk, as it neither have nor use the read parameter. Thus, we determine that it is a safe upgrade.
Upgradvisor is a research project from Columbia University’s RCS lab. Our goal is to provide meaningful information for developers (like you) on how to upgrade their software dependencies. If you have any questions or feedback please reach out to the Upgradvisor team at yaniv.david@columbia.edu.
Hi there! Upgradvisor has identified that one of your repository’s dependencies has a newer version available, and we recommend you upgrade.
Your code currently pins
filetype 1.0.9
when filetype1.2.0
is available. The attached graph shows the dependency path of your repository relative tofiletype
. Your code is shown in green (each node is a method), and your code callingfiletype
is shown in orange. Changes between version1.0.9
and1.2.0
are shown as starred.From the attached graph and manual tracing conducted by the team, between the two versions of
filetype
, the only major change isutils.get_bytes
, in which it only adds anhasattr
method to check if the parameterobj
exists aread
parameter. This change does not affectlbry-sdk
, as it neither have nor use theread
parameter. Thus, we determine that it is a safe upgrade.Upgradvisor is a research project from Columbia University’s RCS lab. Our goal is to provide meaningful information for developers (like you) on how to upgrade their software dependencies. If you have any questions or feedback please reach out to the Upgradvisor team at yaniv.david@columbia.edu.