version release date history wrong for "humanize" gem

[Jeremy Weathers]

I noticed that https://rubygems.org/gems/humanize suggests that the gem is abandoned with an update 2.5 years ago, rather than the actual last release of 1.8.0 about 2 weeks ago. I'm not sure if this data problem is confined to this one gem or if it affects many - it's certainly not a universal problem.

[David Radcliffe]

Looks like the date is hardcoded in the gemspec: https://github.com/radar/humanize/blob/baeb72d3db2c274b3609d978cde2027b2c9c9f15/humanize.gemspec#L12

We've discussed this before here: https://github.com/rubygems/rubygems.org/issues/1171

---
David Radcliffe

On Thu, Aug 30, 2018 at 9:47 AM Jeremy Weathers <jer...@codekindly.com> wrote:

I noticed that https://rubygems.org/gems/humanize suggests that the gem is abandoned with an update 2.5 years ago, rather than the actual last release of 1.8.0 about 2 weeks ago. I'm not sure if this data problem is confined to this one gem or if it affects many - it's certainly not a universal problem.

--
You received this message because you are subscribed to the Google Groups "rubygems.org" group.
To unsubscribe from this group and stop receiving emails from it, send an email to rubygems-org...@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

[Ryan Bigg]

Hi! I'm the owner of this gem and can definitely fix this problem now. https://github.com/radar/humanize/commit/4713f9d5977b0afb69b58a3c20a51a8e64dd46bb 

Releasing 1.8.1 with this fix :)