-
-
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
Update aruba requirement from ~> 1.0 to ~> 2.1 #544
Conversation
4d6b07b
to
f931e83
Compare
f931e83
to
6156dcc
Compare
Right, so there is a version requirement that's too steep for the older Railses:
|
Yip. It's going to take some time to get all of these things in. I'm going to try tackle them in a specific order. aruba and rubocop-rspec last, rubocop/performance first. |
cae2333
to
abc94e5
Compare
Updates the requirements on [aruba](https://github.com/cucumber/aruba) to permit the latest version. - [Release notes](https://github.com/cucumber/aruba/releases) - [Changelog](https://github.com/cucumber/aruba/blob/main/CHANGELOG.md) - [Commits](cucumber/aruba@v1.0.0...v2.1.0) --- updated-dependencies: - dependency-name: aruba dependency-type: direct:development ... Signed-off-by: dependabot[bot] <[email protected]>
abc94e5
to
4637048
Compare
This will need a bit of thought. Leave it with me for a few days |
@luke-hill you might consider changing the aruba requirement to: s.add_development_dependency('aruba', '>= 1.0', '< 3') It's a test-only requirement, so it would be easy to just make the test suite compatible with both versions of aruba. It looks to me like the only difference is that the tests are using a file without the step of creating the file, and that can be fixed in 1 as well so it no longer gives a warning there. Running the tests with aruba 2 in at least the supported combinations would help diagnose and fix the warnings the suite generates now with aruba 1. This would be a much better solution than dropping supported Rails versions. However, I wasn't able to easily track down why cucumber is restricted to versions < 4 on Rails 5.0 (in this repo only), as the PR that added that restriction didn't come with an explanation of why. I checked the shared dependencies and they all should work. What happens when you try to run cucumber 4 with rails 5.0? Or is the cucumber dependency restriction in the rails gemfiles just a way to test against different cucumber versions that cucumber-rails supports? |
I did a better version of this fix in #552. |
OK, I won't notify you again about this release, but will get in touch when a new version is available. If you'd rather skip all updates until the next major or minor version, let me know by commenting If you change your mind, just re-open this PR and I'll resolve any conflicts on it. |
Updates the requirements on aruba to permit the latest version.
Changelog
Sourced from aruba's changelog.
... (truncated)
Commits
e6edc69
Prepare version 2.1.0 for releaseba54535
Merge pull request #870 from cucumber/dependabot/bundler/cucumber-gte-4.0-and...aef6d5d
Test with cucumber 8 in CI64897ff
Add appraisal for Cucumber 8726109c
Update cucumber requirement from >= 4.0, < 8.0 to >= 4.0, < 9.0d5bd6e3
Merge pull request #869 from cucumber/fix-new-rubocop-offenses3920ad8
Autocorrect Lint/NonDeterministicRequireOrder16e44ee
Autocorrect Style/EnvHomefa023da
Ensure use of RuboCop version supporting TargetRubyVersion 2.54936a34
Prepare version 2.0.1 for releaseDependabot will resolve any conflicts with this PR as long as you don't alter it yourself. You can also trigger a rebase manually by commenting
@dependabot rebase
.Dependabot commands and options
You can trigger Dependabot actions by commenting on this PR:
@dependabot rebase
will rebase this PR@dependabot recreate
will recreate this PR, overwriting any edits that have been made to it@dependabot merge
will merge this PR after your CI passes on it@dependabot squash and merge
will squash and merge this PR after your CI passes on it@dependabot cancel merge
will cancel a previously requested merge and block automerging@dependabot reopen
will reopen this PR if it is closed@dependabot close
will close this PR and stop Dependabot recreating it. You can achieve the same result by closing it manually@dependabot ignore this major version
will close this PR and stop Dependabot creating any more for this major version (unless you reopen the PR or upgrade to it yourself)@dependabot ignore this minor version
will close this PR and stop Dependabot creating any more for this minor version (unless you reopen the PR or upgrade to it yourself)@dependabot ignore this dependency
will close this PR and stop Dependabot creating any more for this dependency (unless you reopen the PR or upgrade to it yourself)