digitalocean/droplet_kit

Faraday dependency is overly specific

coderanger opened this issue · 0 comments

The gem dependency on faraday is ~> 0.9.1. This only allows 0.9.1 and 0.9.2. Faraday 0.10 was released last November and it is currently up to 0.12. Was this an intentional lock? Usually ~> should only have two version components if you're using it in a SemVer style. If what you want is >=0.9.1 && <1.0 you can do that with '~> 0.9', '>= 0.9.1' or something similar. This is causing dependency conflicts in some Chef ecosystem tools as we try to upgrade Faraday to more recent versions.