Yeah, see, I'm not going to jump in and fix this on the spot with that kind of tone - it's just opening Pandora's Box. You don't have to be nice or whatever, but you can't word it like that. This issue could've easily been titled "Can't cache package installs due to outdated version".
Nobody is paid to work on this, and the people who have worked on it in the past have lives they're living. Shit happens, people get busy, or their use cases move on, etc. It's a free and open source library that, surprisingly, has found widespread use for over a decade in the face of an actively hostile API set.
There have been multiple calls to enable other people to step up and provide stewardship/maintenance/etc. If things aren't happening, it's because those calls haven't been answered. Opening an issue with an exasperated title like yours will do nothing to move it along.
tl;dr: If I find time later this week I'll bump it myself. Don't disrespect the people who have poured work into the project (and I'm speaking about other contributors more than myself here). GitHub and open source culture provide an illusion that free work is owed when that simply isn't the case. on Release a new version already!
34 minutes ago