Closed bsrz closed 3 years ago
Same issue here. I could workaround this by specifying gem 'danger-swiftlint', '>=0.24.3'
in my Gemfile. But I suppose that the issue lies in Bundler gem itself as that's where the decision for the version is made (I assume). I guess there's something wrongly matching 3
to be higher than 24
by just looking at the first digit (2
).
Thanks for the issue! Yeah good thinking @Jeehut, seems to be the case. @bsarrazin which bundler version are you using? Seems really weird that this wouldn't be working ...
@ashfurrow my apologies for the delay. I am using bundler 2.1.4, which I think is the latest?
I was also seeing a conflict with a gem of mine. So I'm thinking maybe that was the source of conflict. Take a look https://rubygems.org/gems/sekrit/ I think you have far deeper Ruby knowledge than I do. Any feedback is appreciated!
Looks like tweaking the dependency versions and releasing 0.3.0 has fixed it. 🤞
Closing this since it's pretty old and seems to be fixed.
Problem
Running
$ bundle update
ends up in downgrading the library or downgrading danger itself if version is locked.Setup
Ruby version: 2.6.5 Using rbenv
Contents of
Gemfile
:Contents of
Gemfile.lock
(the relevant part):Running
bundle update
(the relevant part):Contents of
Gemfile.lock
after update (the relevant part):Forcing the version in the
Gemfile
usinggem 'danger-swiftlint', '~> 0.24'
results in downgrading danger itself: