When there is a conflict because of an activated gem we shouldn't blindly try and backtrack to parent of current gem (which is conflicting). If there are no other versions of parent available, it will lead to dead end. In which case try backtracking to gem that originally activated the conflicting gem.
…ANGELOG entry [ci skip]
User can additionally specifiy require: true in gem dependency. It behaves same as not specifying any argument.
That can be reused across several places in bundler and hence extracted that code which is responsible for properly detecting current ruby version.