We currently don't support version requirements like ~> 1.0 or ~> 2.0. The issue being the or. We have no support for or or and. This causes transitive Elixir dependencies to often fail because they can't be resolved.

Handling the constraint once parsed I think should be to just pick the largest. So in the case of ~> 1.0 or ~> 2.0 it will be converted to ~> 2.0.