dep: rubygems >= 3.2.0 for Platform#match_gem?

[flavorjones]

Closes #286

[henrikbjorn]

@flavorjones This kind of sucks for those that aren't quite able to upgrade the rubygems platform. This means that even though tailwind has new releases, we won't get the update through this gem.

why not bump the minor version with this? Or even a new Major, since it is a BC break?

[flavorjones]

@henrikbjorn That might have been a good idea, but I can't go back in time and fix it now. I'd suggest pinning your app to 2.0.30 if you can't upgrade rubygems.

Out of curiosity, can you share more about your situation and why you're not able to upgrade? Rubygems 3.2.0 is over three years old at this point I think should be shipped in all versions of Ruby that are not EOL.

[henrikbjorn]

@henrikbjorn That might have been a good idea, but I can't go back in time and fix it now. I'd suggest pinning your app to 2.0.30 if you can't upgrade rubygems.

Out of curiosity, can you share more about your situation and why you're not able to upgrade? Rubygems 3.2.0 is over three years old at this point I think should be shipped in all versions of Ruby that are not EOL.

Can't be specific.

But I think some might have old infrastructures, or stuck with gems that haven't been updated in a while etc.

How about doing a point release for 2.0.x that checks for 'respond_to?` or something?

[flavorjones]

There are two known workarounds:

• upgrade rubygems
• pin this gem to 2.0.30

Because there are ways around this issue, and because this issue affects so few people, writing and testing a third workaround and making a release feels like a relatively low priority for me, at least without additional information.