06:42 <Confusion> Are there any known bugs in dependency resolution, where a gem is not upgraded to the most recent version available? I have a situation where I have gems named e.g. my-gem.1.3.20160606.121314, so major.minor.timestamp. I have a Gemfile dependency gem 'my-gem', '~> 1.3'. A new version is made available on our internal gemserver. When I run bundle update, it updates to an *older* version (version 1.3.20160415.something)..

06:43 <Radar> Confusion: is another gem depending on that older version?

06:43 <Radar> Confusion: i.e. check your Gemfile.lock for occurrences of that gem.

06:43 <Confusion> No, this is the only dependency in the Gemfile

06:43 <Confusion> (I've removed the rest for purposes of this test)

06:43 <Radar> Confusion: And is the gem only occurring once in the Gemfile.lock?

06:44 <Confusion> Checked: yes

06:45 <Confusion> So the new version is named 1.3.20160705.something. If I change the dependency to gem 'my-gem', '~> 1.3.20160701', it does update to the correct version

06:45 <Confusion> If I remove the .20160701 again, it 'updates' to the older version

06:47 <Radar> I don't know how that's happening then, sorry.

07:03 <Confusion> (I'm on a train that just went through a tunnel, so I may have missed something, sorry; did my explanation of how changing the dependency specification in the Gemfile influence matters come through?)

07:03 <Radar> yes

07:05 <Confusion> OK, I think I'll just file an issue then