To quote my comment on the commit that introduced the "bug":
Was this intentionally released as a non-breaking change, and thus a "not-a-major" version bump?
Using the ... operator, as noted in the git commit comment, is Ruby 3.0+ only. For Rails apps this isn't a huge deal, as they only deal with one version of Ruby at a time. For other libraries that depend on factory_bot this is awful (e.g. https://github.com/pboling/activerecord-transactionable/actions/runs/8169704061/job/22334293843). In that link the latest (broken) gem is installing fine on Ruby 2.5.
I know there is a fair bit of disagreement over how SemVer is interpreted... and this is not serving the community very well.
Description
To quote my comment on the commit that introduced the "bug":
Reproduction Steps
Using a Ruby < 3.0, for example, Ruby 2.5:
Then set it up and use it. 💥
Expected behavior
If the gem sits it fits.
Actual behavior
The gem blew up:
System configuration
factory_bot version: 6.4.5 rails version: N/A ruby version: 2.5.9