Hard bump the capybara version

[cupakromer]

If we still have a dependency on capybara, we should hard bump the version on 4.0. Additionally, reach out to the capybara team early on this process to better coordinate any changes that need to be made, and sync the releases between the two gems.

Related to: #1091, #1094

[cupakromer]

Just dropping this here as a reminder to future self / team.

[myronmarston]

👍

[pirj]

Rails depended on Capybara 2.15+ up until now (6-0-stable as of 04e08ee17).

There are bump commits in master to depend on 3.2.6+, but it's not released/tagged yet, presumably might happen in 6.1.

Capybara seems stable, 3.0 is around for three years already, and there are no plans for 4.0 as far as I can see.

With this in mind, wondering if we sh bump it to ~> 3.0 or rely on Rails to pick a version they need to use under the hood.

[JonRowe]

Whats the minimum version supported by our current matrix, should at least bump to that if you want to tackle @pirj?

[pirj]

capybara first appeared as ~> 2.7.0 in Rails 5.1.0.beta1, was bumped to ~> 2.13.0 in Rails 5.1.0.rc1, remained ~> 2.13.0 in 5.1.0 and is > 2.15 in 5-1-stable.

I intend to bump it to >= 2.13 from our current ~> 2.13 to allow for both 2 & 3, and a smoother transition between the two.

[JonRowe]

It would be better to do ~> 2.13, ~> 3.0 to exclude 4 until we're compatible (and we'll need to check we're 3.x compatible)