There's no actual problem being fixed here, but cocoapods got hit by a similar mistake with very bad consequences, see #1370.
(Our CI runs jazzy via bundler so uses the known-good gem versions rather than the latest versions of everything which is why it does not see the cocoapods issue.)
Per activesupport gem usage instructions.
There's no actual problem being fixed here, but cocoapods got hit by a similar mistake with very bad consequences, see #1370.
(Our CI runs jazzy via bundler so uses the known-good gem versions rather than the latest versions of everything which is why it does not see the cocoapods issue.)