Here's an example PR from a few days ago where someone contributed an improvement to the type definitions Sorbet maintains for the standard library: https://gi

Here's an example PR from a few days ago where someone contributed an improvement to the type definitions Sorbet maintains for the standard library: https://github.com/sorbet/sorbet/pull/5024 https://github.com/sorbet/sorbet/pull/5024 By adding those type definitions, any downstream projects using Sorbet that happened to use those definitions incorrectly will start to see new type errors. Here's another example: https://sorbet.run/#%23%20typed%3A%20true%0Aextend%20T%3A%3ASig%0A%0Asig%20%7Bparams%28x%3A%20%7Bkey1%3A%20Integer%7D%29.void%7D%0Adef%20foo%28x%29%0A%20%20x%5B%3Akey2%5D%20%23%20no%20error!%0Aend https://sorbet.run/#%23%20typed%3A%20true%0Aextend%20T%3A%3A... This example shows a bug in how Sorbet handles shape types, that we definitely want to fix in the future but haven't had the time to yet. When we fix that, any project using shape types incorrectly will suddenly have new type errors.