Use the latest Sorbet version and regenerate Tapioca RBIs

[issyl0]

• Have you followed the guidelines in our Contributing document?
• Have you checked to ensure there aren't other open Pull Requests for the same change?
• Have you added an explanation of what your changes do and why you'd like us to include them?
• Have you written new tests for your changes? Here's an example.
• Have you successfully run brew style with your changes locally?
• Have you successfully run brew tests with your changes locally?

---

• The Sorbet version was originally pinned in 1a6467e because we found that newer versions surfaced over 100 new typing errors in Tapioca's autogenerated RBI files. If we remove and entirely regenerate (using Ruby 2.6.3, not Ruby 2.7), as opposed to resync the Tapioca RBIs, these errors go away.
• Current errors status report, using Ruby 2.6.3 and Sorbet 0.5.5866:
  • bundle exec srb tc: 13 errors.
  • bundle exec srb tc --typed-override=sorbet/files.yaml: 18 errors.
  • None of the errors are in RBI files. 🎉

(cc @vidusheeamoli, @mistydemeo)

---

I have a question about the Ruby version mismatch: should Library/Homebrew have a .ruby-version file so that rbenv can use the correct Ruby version automatically rather than defaulting to the global one?

[vidusheeamoli]

Tested this as well. Works well for me!

[MikeMcQuaid]

I have a question about the Ruby version mismatch: should Library/Homebrew have a .ruby-version file so that rbenv can use the correct Ruby version automatically rather than defaulting to the global one?

It could do but would probably make more sense to put it in the repository root.

[MikeMcQuaid]

Let's prioritise ASAP getting a CI job step that tests something that will fail if a newer version of sorbet goes 💥