Allow ruby version 4.0 in gemspec

[obrie]

This adds support for Ruby 4.0. Note this is currently broken for flatware-cucumber due to a change in Ruby that was fixed here: cucumber/cucumber-ruby-core#302

Opening this PR to start a discussion around how you want to move forward to address this. We could change the minimum version require for flatware-cucumber. I haven't spent time thinking through potential alternatives yet. Example of failure:

  1) Flatware::Cucumber.configure copies the arguments into each job
     Failure/Error: cli_config.parse! args + %w[--format Flatware::Cucumber::Formatter]
     
     Cucumber::Cli::YmlLoadError:
       cucumber.yml was found, but could not be parsed with ERB.  Please refer to cucumber's documentation on correct profile usage.
       #<ArgumentError: wrong number of arguments (given 3, expected 1)>
     # ./lib/flatware/cucumber.rb:38:in 'Flatware::Cucumber.configure'
     # ./spec/flatware/cucumber_spec.rb:7:in 'block (3 levels) in <top (required)>'
     # ------------------
     # --- Caused by: ---
     # ArgumentError:
     #   wrong number of arguments (given 3, expected 1)
     #   ./lib/flatware/cucumber.rb:38:in 'Flatware::Cucumber.configure'

  2) Flatware::Cucumber run with multiple scenarios in the same file calls the steps the correct number of times
     Failure/Error: puts event.inspect
     
     ArgumentError:
       wrong number of arguments (given 5, expected 2)
     # ./lib/flatware/cucumber/formatter.rb:53:in 'Kernel#inspect'
     # ./lib/flatware/cucumber/formatter.rb:53:in 'Flatware::Cucumber::Formatter#on_step_activated'
     # ./lib/flatware/cucumber.rb:44:in 'Flatware::Cucumber.run'
     # ./spec/flatware/cucumber_spec.rb:39:in 'block (5 levels) in <top (required)>'
     # ./spec/flatware/cucumber_spec.rb:38:in 'Dir.chdir'
     # ./spec/flatware/cucumber_spec.rb:38:in 'block (4 levels) in <top (required)>'

[obrie]

When running this on newer versions of cucumber, we get:

  1) Flatware::Cucumber run with multiple scenarios in the same file calls the steps the correct number of times
     Failure/Error: expect(Flatware).to have_received(:ran).with(3)
     
       Flatware received :ran with unexpected arguments
         expected: (3)
              got: (1) (1 time)
                   (2) (1 time)
     # ./spec/flatware/cucumber_spec.rb:47:in 'block (5 levels) in <top (required)>'
     # ./spec/flatware/cucumber_spec.rb:41:in 'Dir.chdir'
     # ./spec/flatware/cucumber_spec.rb:41:in 'block (4 levels) in <top (required)>'

I haven't quite figured that one out either.

[obrie]

@briandunn I think this is ready for review. At least, all specs are now passing :)

[briandunn]

@obrie I am so excited about this! There is a lot here I've been meaning to get to for a long time. Gonna review and merge soon. Thank you!

[briandunn]

Thank you so much!

[briandunn]

I am so happy you figured this out! Had me stuck. Also, I think we're gonna phase out cucumber support I don't think many are using it. (do you?)

[obrie]

Happy to help 😄

I've never used cucumber myself. I can't think of too many open-source projects I've seen that have used cucumber either. Based on the number of installs of flatware-cucumber, doesn't seem like there are that many folks who use both flatware and cucumber.

[mjankowski]

Thanks for merging this. Can confirm it works just fine on a WIP ruby 4.0 upgrade branch. Release soon?

Separately - we also dont need the cucumber support. Just using flatware as parallelizing wrapping around pretty vanilla rspec suite.

[mjankowski]

@briandunn anything we can do to assist in version release? Would a PR with the version update help? Anything more you want to fit in prior to that?

[briandunn]

Getting this when running rubocop locally: ``` ❯ be rubocop rubocop-rake extension supports plugin, specify `plugins: rubocop-rake` instead of `require: rubocop-rake` in /Users/brian/src/flatware/.rubocop.yml. For more information, see https://docs.rubocop.org/rubocop/plugin_migration_guide.html. Error: unrecognized cop or department Naming/PredicateMethod found in .rubocop.yml Did you mean `Naming/PredicateName`? ``` is there a mismatch between the bundle rubocop and the .rubocop.yml?

…

On Wed, Jan 21, 2026 at 11:36 AM Matt Jankowski ***@***.***> wrote: *mjankowski* left a comment (briandunn/flatware#113) <#113 (comment)> @briandunn <https://github.com/briandunn> anything we can do to assist in version release? Would a PR with the version update help? Anything more you want to fit in prior to that? — Reply to this email directly, view it on GitHub <#113 (comment)>, or unsubscribe <https://github.com/notifications/unsubscribe-auth/AAAWY7S5MWT23V3CCEOBZTD4H62J7AVCNFSM6AAAAACP4ENC2KVHI2DSMVQWIX3LMV43OSLTON2WKQ3PNVWWK3TUHMZTONZZHE3TQMJVGI> . You are receiving this because you were mentioned.Message ID: ***@***.***>

[mjankowski]

The Gemfile.lock is gitignored ... so I think there isnt really a specific bundle version?

That said, yes, I think that cop was renamed at some point, so it could be that you are running older rubocop and hitting that error? If you upgrade to latest rubocop (1.82.1) does that go away?

[briandunn]

yes thanks. I'll add a version constraint to the Gemfile.

…

On Thu, Jan 22, 2026 at 8:36 AM Matt Jankowski ***@***.***> wrote: *mjankowski* left a comment (briandunn/flatware#113) <#113 (comment)> The Gemfile.lock is gitignored ... so I think there isnt really a specific bundle version? That said, yes, I think that cop was renamed at some point, so it could be that you are running older rubocop and hitting that error? If you upgrade to latest rubocop (1.82.1) does that go away? — Reply to this email directly, view it on GitHub <#113 (comment)>, or unsubscribe <https://github.com/notifications/unsubscribe-auth/AAAWY7UKKTFQH2H5S5SYJXL4IDN7DAVCNFSM6AAAAACP4ENC2KVHI2DSMVQWIX3LMV43OSLTON2WKQ3PNVWWK3TUHMZTOOBUG4YTMMJVGA> . You are receiving this because you were mentioned.Message ID: ***@***.***>