Just got this error too after an update from 2.4.1 to 2.4.2.
Is this really the correct way to break the syntax in minor updates? I mean, going from 2.4 to 2.5 I might expect some syntax changes, but 2.4.1 to 2.4.2 should not break the syntax IMO (even if the behavior was not intended in the first place), even thought ruby does not follow semver.
At least an entry should be added to the changelog and/or caveats section.