@searls could you also resolve it by another shim version that sets the required_ruby_version < 3.0 ?

@searls Yeah as much as I agree with the philosophy of not yanking, it seems like the best option in this situation.

@searls As stated in the [SEMVER spec](https://semver.org/#spec-item-4):

> Major version zero (0.y.z) is for initial development. Anything MAY change at any time. The public API SHOULD NOT be considered stable.

IMO this looks like a license to go ahead and yank it :P