diff options
author | eileencodes <eileencodes@gmail.com> | 2018-04-10 16:37:17 -0400 |
---|---|---|
committer | eileencodes <eileencodes@gmail.com> | 2018-04-10 16:40:14 -0400 |
commit | 72f17d59e40c95d08edb893b898145a7bf68d1a2 (patch) | |
tree | c6dd5986636d119e92f16a74f505362302f4c1fc /actionpack | |
parent | 561aad0c186103232c094e38d4d3fe4ea4c083f3 (diff) | |
download | rails-72f17d59e40c95d08edb893b898145a7bf68d1a2.tar.gz rails-72f17d59e40c95d08edb893b898145a7bf68d1a2.tar.bz2 rails-72f17d59e40c95d08edb893b898145a7bf68d1a2.zip |
Remove upper bound on Capybara
There's no reason to block future versions of Capybara since we don't
_know_ they are going to break. How will we know if we have a
conservative option set? This change prevents us from blocking users who
want to upgrade in the future.
Diffstat (limited to 'actionpack')
-rw-r--r-- | actionpack/lib/action_dispatch/system_test_case.rb | 2 |
1 files changed, 1 insertions, 1 deletions
diff --git a/actionpack/lib/action_dispatch/system_test_case.rb b/actionpack/lib/action_dispatch/system_test_case.rb index d06ff0c804..c74c0ccced 100644 --- a/actionpack/lib/action_dispatch/system_test_case.rb +++ b/actionpack/lib/action_dispatch/system_test_case.rb @@ -1,6 +1,6 @@ # frozen_string_literal: true -gem "capybara", ">= 2.15", "< 4.0" +gem "capybara", ">= 2.15" require "capybara/dsl" require "capybara/minitest" |