Since this comes up often: IMO the rule of thumb for whether or not you should yank a gem release is: don't.
Two exceptions:
- The gem was pushed by an attacker who took over your account.
- Legal reasons (e.g. copyright, etc).
1/4
Having this sort of tool available in such a freeform language is so cool! I love the casual flexibility of Ruby and Just A Text Editor, but there are still those times that the grass looks pretty green in statically-typed IDE land.
Here's a great example of why our new referral gem is super neato. I wanted to see how to instantiate Webpacker's `Manifest`. git-grep produced a bunch of unhelpful matches (image 1), whereas referral found its one-and-only call site (image 2).
More here: github.com/testdouble/referr…
Excellent point! So far that information only made it into my #rubykaigi presentation 😅
I've just thrown the relevant slides up... even without my words, they probably answer some questions. I'll definitely add a proper explanation to docs ASAP, though.
speakerdeck.com/matthewd/rub…
I really, really appreciate people like @dwradcliffe who devote time to keeping the lights on while everyone else is relaxing and you should, too. 🙇🏼 x.com/rubygems_status/status…