Got ArgumentError with unknown keyword in Ruby 3.4.0-preview2

[PikachuEXE]

👓 What did you see?

✅ What did you expect to see?

No error

📦 Which tool/library version are you using?

ruby 3.4.0-preview2
cucumber-ruby 9.2.0

🔬 How could we reproduce it?

I run bundle exec cucumber but the following is easier:

• irb
• Hash.new(strict: false).freeze (simplified from https://github.com/cucumber/cucumber-ruby/blob/v9.2.0/lib/cucumber/multiline_argument/data_table.rb#L78)

Ruby 3.3:

Ruby 3.4:

📚 Any additional context?

Trying to fix CI for ruby-head for https://github.com/egonSchiele/contracts.ruby

Update 1: Rubocop added a cop for this: https://docs.rubocop.org/rubocop/cops_lint.html#linthashnewwithkeywordargumentsasdefault

[luke-hill]

This is fixed in main - It will be released in cucumber v10. For now if you stick to ruby 3.3 you should be fine

[ashmaroli]

Hello @luke-hill,
May I ask if you'd be willing to ship a v9.2.1 with just a468bc6 cherry-picked onto a branch spun-off from tag v9.2.0 to resolve this issue for everyone who wish to use cucumber with Ruby 3.4. (One particular use-case is introduction of Ruby 3.4 to existing CI matrix); Especially since v10.0.0 may involve major internal rewrites..?
If you're not willing to ship a patch release in the near future, I could use that reason to justify having my projects point to a temporary fork of cucumber/cucumber-ruby to unblock pull requests waiting on Ruby 3.4 support.
Thanks.

[tagliala]

9.2.1 with that commit, if it does not break, would be appreciated

Additionally, it is worth to mention that the comment in a468bc6

# Future versions [3.4.0+] of ruby will interpret these as keywords and break.

feels outdated, since 3.4.0+ is not future anymore and can be improved. Copilot suggests

# Ruby versions from 3.4.0 onwards interpret these as keywords and break.

[jagthedrummer]

Would be really nice to get a point release with this fix published. Having to wait for cucumber 10 in order to use ruby 3.4 doesn't seem like a great solution, and I'd imagine that lots of people are going to be looking to upgrade to ruby 3.4 in the next few days/weeks/months.

[jagthedrummer]

I opened #1773 to cherry-pick the ruby 3.4 fix into the 9.2 branch. Unfortunately tests are failing in the 9.2 release branch (an example run), so I'm not sure if this PR actually breaks anything for CI or not. It seems like the main branch in this repo is failing in the same way.

[tagliala]

FWIW, using cucumber for main allows ActiveAdmin specs to pass without any change: https://github.com/activeadmin/activeadmin/actions/runs/12602417643/job/35125445673

[luke-hill]

If I get to see some more rockets / +1s I will prioritise this.

Because (primarily my fault), we've got a mix of stuff in main it will need a bit of cherry-picking and branching. But I'm happy to prioritise it if I see more demand for it. For now (I think I posted this in another thread), I'm going to continue to work on the v10 rework