Open thesamesam opened 1 year ago
Hi @thesamesam.
Wow, I had totally forgotten about this whole thing. Looks like I need to fault it back into working memory again.
I am able to commit to the hamstergem
repo, but the gem owner, who is the only person who can release new gem versions, has not been active on this project for a long time so we haven't been able to release new versions. If he ever decides to come back and release a new version, that will be appreciated.
In the meantime, I have a maintained fork here: https://github.com/immutable-ruby/immutable-ruby
If the same problem exists on that fork, I will fix it immediately and release a new version.
Looks like the problem was already fixed in immutable-ruby
.
Hi,
Would it be possible for a new release to be made containing the fixes for https://github.com/hamstergem/hamster/issues/251 / https://github.com/hamstergem/hamster/pull/252? This would make it a lot easier in distributions carrying hamster who want to support newer Ruby versions.
Thanks in any case.