-
-
Notifications
You must be signed in to change notification settings - Fork 328
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
cucumber-rails
incompatible with latest cucumber-ruby
#538
Comments
Because we don't permit it yet. |
So let’s keep this open as a reminder to make cucumber-rails compatible with cucumber-ruby 8. |
cucumber-rails
incomaptible with latest cucumber-ruby
cucumber-rails
incompatible with latest cucumber-ruby
Here we go: #541. Needs a release now. |
I would like to set up #546 as part of delivering this. |
Just checked out cucumber-rails@main in one of our projects and bumped Cucumber to v8. It's working smoothly out of the box! I just need a release version now 🤣 |
Cheers. I'll get on it soon. We've just been fixing up a bunch of stuff with the pipelines e.t.c. so there will be quite a lot of non-package related fixes. |
@luke-hill is there any chance this will be released soon? |
Sorry I have been swamped in other stuff and been a bit fluey. I'll get on this soon. |
No worries, hope you’re feeling better now |
👓 What did you see?
When updating to latest
cucumber-ruby
I couldn't jump to version 8 without dropping to much older version ofcucumber-rails
.✅ What did you expect to see?
I expected to see both
cucumber-ruby
andcucumber-rails
be updated to newest published versions.📦 Which tool/library version are you using?
Rails 7.0.3
Ruby 2.7.6
🔬 How could we reproduce it?
Steps to reproduce the behavior:
gem cucumber
to Gemfilebundle install
cucumber-rails
installed and not version 2.xThe text was updated successfully, but these errors were encountered: