Daniel Huss

Thank you @deivid-rodriguez! To your point: > I'm probably missing context but to me this seems like the wrong place to fix this problem. [...] I feel RubyGems is doing...

As a fun aside, I was curious why the `rubygems.org` repo didn't have similar problems with reporting dates on gem versions. [This check](https://github.com/rubygems/rubygems.org/blob/34907a6b36a81c276c9cc8a53a7534170f401308/app/models/version.rb#L189), from the early days of migrating gems...

I appreciate the feedback and discussion here! Thanks for taking the time 😄 > 1. Add a comment to [rubygems.org's `rely_on_built_at?`] I popped up a brief PR on that side...

Great catch! This is an ongoing issue that's further upstream from us. Check out [RubyGems #6859](https://github.com/rubygems/rubygems/pull/6859) for some detail!

I agree that Bundler should be our first stop for validating a `Gemfile`! When we discussed, other options came up first. Namely, using `bundler outdated`, or other gems like [libyear-bundler](https://github.com/jaredbeck/libyear-bundler)....