15:47 <odigity> I just ran `bundle outdated` and it reported nothing, even though there's a new version of the sequel gem. How can I troubleshoot this?

15:49 <jhass> maybe you got something that locks on an old version as a dependency? looking at the Gemfile.lock could help

15:53 <odigity> jhass, nope, I checked. I'm the only one using sequel, no other gem is depending on it.

15:54 <jhass> latest bundler? if so try to produce a minimal testcase and open an issue

15:54 <odigity> 1.10.6

15:55 <odigity> which is latest

16:05 <odigity> I figured it out. Apparently having BUNDLE_FROZEN: '1' in your ~/.bundle/config file will also prevent the outdated command from contacting rubygems and looking for new versions.

20:06 <indirect> odigity: having a frozen bundle means that no gem version can change. it means you probably ran `install —deployment` at some point

20:06 <indirect> if you’re on a dev machine, you need to run `install —no-deployment`

20:09 <odigity> indirect, I'm aware that FROZEN prevents bundle from using a Gemfile newer than Gemfile.lock, and I know how it happened (it's part of the design of the official ruby docker container). The surprise was that it would prevent the 'outdated' command from working.

20:09 <odigity> outdated doesn't install or in any way modify anything. it could be allowed to run. but it doesn't.