Skip to content

Update factory_bot_rails.gemspec#479

Closed
JuanVqz wants to merge 1 commit into
thoughtbot:mainfrom
JuanVqz:patch-1
Closed

Update factory_bot_rails.gemspec#479
JuanVqz wants to merge 1 commit into
thoughtbot:mainfrom
JuanVqz:patch-1

Conversation

@JuanVqz
Copy link
Copy Markdown

@JuanVqz JuanVqz commented Jul 4, 2024

I am currently in the process of upgrading from Ruby 2.6 to Ruby 3.0. Initially, I didn't find any restrictions on updating my current factory_bot_rails version to the latest one. Unfortunately, this turned out to be incorrect. The latest version of factory_bot_rails requires factory_bot v6.4, which requires Ruby 3, causing my update to fail.

SyntaxError: /root/project/vendor/bundle/ruby/2.6.0/gems/factory_bot-6.4.5/lib/factory_bot/evaluator.rb:38: syntax error, unexpected ...
...method_missing(method_name, ...)

So, adding the required_ruby_version might help to prevent the misconception.

References:

I am currently in the process of upgrading from Ruby 2.6 to Ruby 3.0. Initially, I didn't find any restrictions on updating my current factory_bot_rails version to the latest one. Unfortunately, this turned out to be incorrect. The latest version of factory_bot_rails requires factory_bot v6.4, which in turn requires Ruby 3, causing my update to fail.

```
SyntaxError: /root/project/vendor/bundle/ruby/2.6.0/gems/factory_bot-6.4.5/lib/factory_bot/evaluator.rb:38: syntax error, unexpected ...
...method_missing(method_name, ...)
```

So, adding the `required_ruby_version` might help to prevent the misconception.

References:
  - thoughtbot/factory_bot#1614
  - thoughtbot/factory_bot@36bd065
  - https://github.com/thoughtbot/factory_bot/pull/1622/files
@neilvcarvalho
Copy link
Copy Markdown
Member

I see this was already introduced at #510 - I'm sorry that PR was merged instead of yours, even though yours was opened first.

@JuanVqz
Copy link
Copy Markdown
Author

JuanVqz commented Jan 31, 2025

I see this was already introduced at #510 - I'm sorry that PR was merged instead of yours, even though yours was opened first.

Thanks for merging the fix 👍

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants