Update humanize requirement #121
Open
Conversation
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
1 participant
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
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
humanize==1.0.0when humanize4.3.0is available. The attached graph shows the dependency path of your repository relative tohumanize. Your code is shown in green (each node is a method), and your code callinghumanizeis shown in orange. Changes between version1.0.0and4.3.0are shown as starred.From the attached graph and manual tracing conducted by the team, between the two versions of
humanize, the only major change resides intime.naturaltime, in which it only adds two additional parameters to the function and a string concatenation that are irrelevant tobashhub-client. We have tested the potential upgrade usingbashhub-client's test suite and the upgrade won’t break any tests. Thus, we determine that it is a safe upgrade. (Please note that the down-stream changes are refactorings-only.)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 [email protected].