aboutsummaryrefslogtreecommitdiffstats
path: root/Gemfile
diff options
context:
space:
mode:
authoreileencodes <eileencodes@gmail.com>2018-04-10 16:37:17 -0400
committereileencodes <eileencodes@gmail.com>2018-04-10 16:40:14 -0400
commit72f17d59e40c95d08edb893b898145a7bf68d1a2 (patch)
treec6dd5986636d119e92f16a74f505362302f4c1fc /Gemfile
parent561aad0c186103232c094e38d4d3fe4ea4c083f3 (diff)
downloadrails-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 'Gemfile')
-rw-r--r--Gemfile2
1 files changed, 1 insertions, 1 deletions
diff --git a/Gemfile b/Gemfile
index 6ae11c1fb2..e350e31bd2 100644
--- a/Gemfile
+++ b/Gemfile
@@ -11,7 +11,7 @@ gem "rake", ">= 11.1"
gem "mocha"
-gem "capybara", ">= 2.15", "< 4.0"
+gem "capybara", ">= 2.15"
gem "rack-cache", "~> 1.2"
gem "coffee-rails"