convert ~> versions to highest matching #989
Merged
Conversation
This file contains 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
|
+1 |
|
This will greatly help when rebar3 packages are used from elixir land. ❤️ |
|
Note that I still need to add support to |
tsloughter
added a commit
that referenced
this pull request
Jan 6, 2016
convert ~> versions to highest matching
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
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.
This patch makes the dependency handler treat a fuzzy match like
~> 1.0.0in the same way it handles a package with no version given (pick the highest) and when a package from hex contains the fuzzy match. Nothing else changes, simply what version is picked to be in the lock file is given more flexibility. This will also allow us to fully support hex publishing inrebar3_hex.