kotovalexarian-likes-github/rails--rails
1
0
Fork 0
mirror of https://github.com/rails/rails.git synced 2022-11-09 12:12:34 -05:00
Code Releases Activity
rails--rails/Gemfile.lock

333 lines
7.8 KiB
Text
Raw Normal View History

implement `provider_job_id` for `queue_classic`. The latest, currently unreleased, version of queue_classic is required for this to work. See https://github.com/QueueClassic/queue_classic/pull/262 for more details.
2015-08-13 03:56:06 -04:00
GIT
remote: git://github.com/QueueClassic/queue_classic.git
Bundle update to fix tests locally
2016-01-28 14:57:08 -05:00
revision: 2e3b624f3043849751b24a758d8c156337ead862
Add master branch to github gems to be able to use local clones
2015-09-01 07:44:32 -04:00
branch: master
implement `provider_job_id` for `queue_classic`. The latest, currently unreleased, version of queue_classic is required for this to work. See https://github.com/QueueClassic/queue_classic/pull/262 for more details.
2015-08-13 03:56:06 -04:00
specs:
Bundle update to fix tests locally
2016-01-28 14:57:08 -05:00
queue_classic (3.2.0.RC1)
implement `provider_job_id` for `queue_classic`. The latest, currently unreleased, version of queue_classic is required for this to work. See https://github.com/QueueClassic/queue_classic/pull/262 for more details.
2015-08-13 03:56:06 -04:00
pg (>= 0.17, < 0.19)
Track Gemfile.lock at the repository The main reason is to make bisect easier. In some points, we have a lot of git dependencies. Since we don't have the information of which commit we are referring to, bundler get the latest commit of the master branch of the dependency. This sometimes returns a version that is not compatible with Rails anymore, making the tests fail and the harder to identify the commit that introduced a bug. Also this will make sure that a contributor will always get a set of dependencies that are passing with our tests. In our CI server we delete the lock file to make sure we are always testing against the newest release of our dependencies.
2015-02-18 11:30:25 -05:00
GIT
remote: git://github.com/bkeepers/qu.git
revision: d098e2657c92e89a6413bebd9c033930759c061f
branch: master
specs:
qu (0.2.0)
qu-rails (0.2.0)
qu (= 0.2.0)
railties (>= 3.2, < 5)
qu-redis (0.2.0)
qu (= 0.2.0)
redis-namespace
run against edge sass to eliminate circular require warnings
2015-09-30 10:42:31 -04:00
GIT
remote: git://github.com/sass/sass.git
Bundle update to fix tests locally
2016-01-28 14:57:08 -05:00
revision: ac8e7aa8e99c425237c708f347f76495a2e18519
run against edge sass to eliminate circular require warnings
2015-09-30 10:42:31 -04:00
branch: stable
specs:
Bundle update to fix tests locally
2016-01-28 14:57:08 -05:00
sass (3.4.21)
run against edge sass to eliminate circular require warnings
2015-09-30 10:42:31 -04:00
Update turbolinks-rails for passing railties test Ref - https://github.com/turbolinks/turbolinks-rails/pull/3
2016-02-05 06:32:22 -05:00
GIT
remote: git://github.com/turbolinks/turbolinks-rails.git
Update to the latest Turbolinks gems
2016-02-23 18:56:19 -05:00
revision: 65884729016dbb4d032f12bb01b7e7c1ddeb68ac
Update turbolinks-rails for passing railties test Ref - https://github.com/turbolinks/turbolinks-rails/pull/3
2016-02-05 06:32:22 -05:00
specs:
Update to the latest Turbolinks gems
2016-02-23 18:56:19 -05:00
turbolinks (5.0.0.beta2)
Update turbolinks-rails for passing railties test Ref - https://github.com/turbolinks/turbolinks-rails/pull/3
2016-02-05 06:32:22 -05:00
turbolinks-source
Track Gemfile.lock at the repository The main reason is to make bisect easier. In some points, we have a lot of git dependencies. Since we don't have the information of which commit we are referring to, bundler get the latest commit of the master branch of the dependency. This sometimes returns a version that is not compatible with Rails anymore, making the tests fail and the harder to identify the commit that introduced a bug. Also this will make sure that a contributor will always get a set of dependencies that are passing with our tests. In our CI server we delete the lock file to make sure we are always testing against the newest release of our dependencies.
2015-02-18 11:30:25 -05:00
PATH
remote: .
specs:
Prep Rails 5 beta 4
2016-04-27 16:47:22 -04:00
actioncable (5.0.0.beta4)
actionpack (= 5.0.0.beta4)
Revert "Revert "Eliminate the EventMachine dependency""
2016-01-27 23:55:31 -05:00
nio4r (~> 1.2)
Initial stab at adding Action Cable to rails/master
2015-12-14 10:38:37 -05:00
websocket-driver (~> 0.6.1)
Prep Rails 5 beta 4
2016-04-27 16:47:22 -04:00
actionmailer (5.0.0.beta4)
actionpack (= 5.0.0.beta4)
actionview (= 5.0.0.beta4)
activejob (= 5.0.0.beta4)
Track Gemfile.lock at the repository The main reason is to make bisect easier. In some points, we have a lot of git dependencies. Since we don't have the information of which commit we are referring to, bundler get the latest commit of the master branch of the dependency. This sometimes returns a version that is not compatible with Rails anymore, making the tests fail and the harder to identify the commit that introduced a bug. Also this will make sure that a contributor will always get a set of dependencies that are passing with our tests. In our CI server we delete the lock file to make sure we are always testing against the newest release of our dependencies.
2015-02-18 11:30:25 -05:00
mail (~> 2.5, >= 2.5.4)
rails-dom-testing (~> 1.0, >= 1.0.5)
Prep Rails 5 beta 4
2016-04-27 16:47:22 -04:00
actionpack (5.0.0.beta4)
actionview (= 5.0.0.beta4)
activesupport (= 5.0.0.beta4)
point at rack master
2015-08-20 16:43:57 -04:00
rack (~> 2.x)
Bump rack-test to fix nil values being sent to `parse_nested_query` I found that nil values were being incorrectly sent to `parse_nested_query` in Rack. Originally it was thought that Rails was doing something incorrect but it was actually rack-test. This was fixed in brynary/rack-test@4a4b2c1 and is no longer an issue. This commit bumps rack-test in Rails so changes to Rack don't cause failures. See rack/rack#813 for more information.
2015-03-01 16:52:17 -05:00
rack-test (~> 0.6.3)
Track Gemfile.lock at the repository The main reason is to make bisect easier. In some points, we have a lot of git dependencies. Since we don't have the information of which commit we are referring to, bundler get the latest commit of the master branch of the dependency. This sometimes returns a version that is not compatible with Rails anymore, making the tests fail and the harder to identify the commit that introduced a bug. Also this will make sure that a contributor will always get a set of dependencies that are passing with our tests. In our CI server we delete the lock file to make sure we are always testing against the newest release of our dependencies.
2015-02-18 11:30:25 -05:00
rails-dom-testing (~> 1.0, >= 1.0.5)
Let strip_tags leave HTML escaping to Rails. Prevents double escaping errors, such as "&amp;" becoming "&amp;amp;".
2015-03-07 12:48:06 -05:00
rails-html-sanitizer (~> 1.0, >= 1.0.2)
Prep Rails 5 beta 4
2016-04-27 16:47:22 -04:00
actionview (5.0.0.beta4)
activesupport (= 5.0.0.beta4)
Track Gemfile.lock at the repository The main reason is to make bisect easier. In some points, we have a lot of git dependencies. Since we don't have the information of which commit we are referring to, bundler get the latest commit of the master branch of the dependency. This sometimes returns a version that is not compatible with Rails anymore, making the tests fail and the harder to identify the commit that introduced a bug. Also this will make sure that a contributor will always get a set of dependencies that are passing with our tests. In our CI server we delete the lock file to make sure we are always testing against the newest release of our dependencies.
2015-02-18 11:30:25 -05:00
builder (~> 3.1)
erubis (~> 2.7.0)
rails-dom-testing (~> 1.0, >= 1.0.5)
Let strip_tags leave HTML escaping to Rails. Prevents double escaping errors, such as "&amp;" becoming "&amp;amp;".
2015-03-07 12:48:06 -05:00
rails-html-sanitizer (~> 1.0, >= 1.0.2)
Prep Rails 5 beta 4
2016-04-27 16:47:22 -04:00
activejob (5.0.0.beta4)
activesupport (= 5.0.0.beta4)
Use released GlobalID now that it provides URI::GID::MissingModelIdError for Active Job
2015-12-17 19:20:19 -05:00
globalid (>= 0.3.6)
Prep Rails 5 beta 4
2016-04-27 16:47:22 -04:00
activemodel (5.0.0.beta4)
activesupport (= 5.0.0.beta4)
activerecord (5.0.0.beta4)
activemodel (= 5.0.0.beta4)
activesupport (= 5.0.0.beta4)
Use released arel
2015-12-17 15:11:29 -05:00
arel (~> 7.0)
Prep Rails 5 beta 4
2016-04-27 16:47:22 -04:00
activesupport (5.0.0.beta4)
Using released concurrent-ruby
2015-11-16 15:26:39 -05:00
concurrent-ruby (~> 1.0)
Track Gemfile.lock at the repository The main reason is to make bisect easier. In some points, we have a lot of git dependencies. Since we don't have the information of which commit we are referring to, bundler get the latest commit of the master branch of the dependency. This sometimes returns a version that is not compatible with Rails anymore, making the tests fail and the harder to identify the commit that introduced a bug. Also this will make sure that a contributor will always get a set of dependencies that are passing with our tests. In our CI server we delete the lock file to make sure we are always testing against the newest release of our dependencies.
2015-02-18 11:30:25 -05:00
i18n (~> 0.7)
minitest (~> 5.1)
tzinfo (~> 1.1)
Prep Rails 5 beta 4
2016-04-27 16:47:22 -04:00
rails (5.0.0.beta4)
actioncable (= 5.0.0.beta4)
actionmailer (= 5.0.0.beta4)
actionpack (= 5.0.0.beta4)
actionview (= 5.0.0.beta4)
activejob (= 5.0.0.beta4)
activemodel (= 5.0.0.beta4)
activerecord (= 5.0.0.beta4)
activesupport (= 5.0.0.beta4)
Track Gemfile.lock at the repository The main reason is to make bisect easier. In some points, we have a lot of git dependencies. Since we don't have the information of which commit we are referring to, bundler get the latest commit of the master branch of the dependency. This sometimes returns a version that is not compatible with Rails anymore, making the tests fail and the harder to identify the commit that introduced a bug. Also this will make sure that a contributor will always get a set of dependencies that are passing with our tests. In our CI server we delete the lock file to make sure we are always testing against the newest release of our dependencies.
2015-02-18 11:30:25 -05:00
bundler (>= 1.3.0, < 2.0)
Prep Rails 5 beta 4
2016-04-27 16:47:22 -04:00
railties (= 5.0.0.beta4)
Require sprockets-rails >= 2 Fixes https://github.com/rails/rails/commit/4d157ea8c15186c4903fa83f2dc51a5f78d13a37 Without any specification about the version of sprockets-rails, running a `bundle install` on a brand new app might result in sprockets 0.0.1 being installed. However, the minimum requirement is sprockets-rails 2 (see https://github.com/rails/rails/pull/17752/files)
2015-09-01 12:29:16 -04:00
sprockets-rails (>= 2.0.0)
Prep Rails 5 beta 4
2016-04-27 16:47:22 -04:00
railties (5.0.0.beta4)
actionpack (= 5.0.0.beta4)
activesupport (= 5.0.0.beta4)
method_source needs to be a hard dependency on railties
2015-03-05 09:58:17 -05:00
method_source
Track Gemfile.lock at the repository The main reason is to make bisect easier. In some points, we have a lot of git dependencies. Since we don't have the information of which commit we are referring to, bundler get the latest commit of the master branch of the dependency. This sometimes returns a version that is not compatible with Rails anymore, making the tests fail and the harder to identify the commit that introduced a bug. Also this will make sure that a contributor will always get a set of dependencies that are passing with our tests. In our CI server we delete the lock file to make sure we are always testing against the newest release of our dependencies.
2015-02-18 11:30:25 -05:00
rake (>= 0.8.7)
thor (>= 0.18.1, < 2.0)
GEM
remote: https://rubygems.org/
specs:
Bundle update to fix tests locally
2016-01-28 14:57:08 -05:00
amq-protocol (2.0.1)
Use released arel
2015-12-17 15:11:29 -05:00
arel (7.0.0)
Use sprockets 3 in the Rails 5 release
2015-12-16 13:30:58 -05:00
backburner (1.2.0)
Update Gemfile.lock
2015-08-09 23:30:03 -04:00
beaneater (~> 1.0)
dante (> 0.1.5)
Fix Gemfile.lock
2016-03-10 14:28:02 -05:00
bcrypt (3.1.11)
bcrypt (3.1.11-x64-mingw32)
bcrypt (3.1.11-x86-mingw32)
Update Gemfile.lock
2015-08-09 23:30:03 -04:00
beaneater (1.0.0)
benchmark-ips (2.3.0)
Track Gemfile.lock at the repository The main reason is to make bisect easier. In some points, we have a lot of git dependencies. Since we don't have the information of which commit we are referring to, bundler get the latest commit of the master branch of the dependency. This sometimes returns a version that is not compatible with Rails anymore, making the tests fail and the harder to identify the commit that introduced a bug. Also this will make sure that a contributor will always get a set of dependencies that are passing with our tests. In our CI server we delete the lock file to make sure we are always testing against the newest release of our dependencies.
2015-02-18 11:30:25 -05:00
builder (3.2.2)
Bundle update to fix tests locally
2016-01-28 14:57:08 -05:00
bunny (2.2.2)
amq-protocol (>= 2.0.1)
Use sprockets 3 in the Rails 5 release
2015-12-16 13:30:58 -05:00
byebug (8.2.1)
Bundle update to fix tests locally
2016-01-28 14:57:08 -05:00
coffee-rails (4.1.1)
Track Gemfile.lock at the repository The main reason is to make bisect easier. In some points, we have a lot of git dependencies. Since we don't have the information of which commit we are referring to, bundler get the latest commit of the master branch of the dependency. This sometimes returns a version that is not compatible with Rails anymore, making the tests fail and the harder to identify the commit that introduced a bug. Also this will make sure that a contributor will always get a set of dependencies that are passing with our tests. In our CI server we delete the lock file to make sure we are always testing against the newest release of our dependencies.
2015-02-18 11:30:25 -05:00
coffee-script (>= 2.2.0)
Bundle update to fix tests locally
2016-01-28 14:57:08 -05:00
railties (>= 4.0.0, < 5.1.x)
Update Gemfile.lock
2015-08-09 23:30:03 -04:00
coffee-script (2.4.1)
Track Gemfile.lock at the repository The main reason is to make bisect easier. In some points, we have a lot of git dependencies. Since we don't have the information of which commit we are referring to, bundler get the latest commit of the master branch of the dependency. This sometimes returns a version that is not compatible with Rails anymore, making the tests fail and the harder to identify the commit that introduced a bug. Also this will make sure that a contributor will always get a set of dependencies that are passing with our tests. In our CI server we delete the lock file to make sure we are always testing against the newest release of our dependencies.
2015-02-18 11:30:25 -05:00
coffee-script-source
execjs
Use sprockets 3 in the Rails 5 release
2015-12-16 13:30:58 -05:00
coffee-script-source (1.10.0)
Add test to make sure the sprockets cache is not shared per environment
2016-03-02 12:21:38 -05:00
concurrent-ruby (1.0.1)
Update Gemfile.lock
2015-08-09 23:30:03 -04:00
connection_pool (2.2.0)
Update dalli gem dalli 2.7.6 fixed deprecation warning caused by using `Rack::Session::Abstract::ID`. This commit suppress warnings on ActionPack tests. See: https://github.com/petergoldstein/dalli/commit/9874a7c3ad67eb1e31cafba0a51966db4f0c7e42
2016-02-13 22:56:16 -05:00
dalli (2.7.6)
Update Gemfile.lock
2015-08-09 23:30:03 -04:00
dante (0.2.0)
Upgrade all the gems
2015-10-20 13:58:57 -04:00
delayed_job (4.1.1)
Track Gemfile.lock at the repository The main reason is to make bisect easier. In some points, we have a lot of git dependencies. Since we don't have the information of which commit we are referring to, bundler get the latest commit of the master branch of the dependency. This sometimes returns a version that is not compatible with Rails anymore, making the tests fail and the harder to identify the commit that introduced a bug. Also this will make sure that a contributor will always get a set of dependencies that are passing with our tests. In our CI server we delete the lock file to make sure we are always testing against the newest release of our dependencies.
2015-02-18 11:30:25 -05:00
activesupport (>= 3.0, < 5.0)
Upgrade all the gems
2015-10-20 13:58:57 -04:00
delayed_job_active_record (4.1.0)
activerecord (>= 3.0, < 5)
delayed_job (>= 3.0, < 5)
Bundle update to fix tests locally
2016-01-28 14:57:08 -05:00
em-hiredis (0.3.1)
Add tests for the ActionCable adapters
2016-01-24 05:43:40 -05:00
eventmachine (~> 1.0)
Bundle update to fix tests locally
2016-01-28 14:57:08 -05:00
hiredis (~> 0.6.0)
Track Gemfile.lock at the repository The main reason is to make bisect easier. In some points, we have a lot of git dependencies. Since we don't have the information of which commit we are referring to, bundler get the latest commit of the master branch of the dependency. This sometimes returns a version that is not compatible with Rails anymore, making the tests fail and the harder to identify the commit that introduced a bug. Also this will make sure that a contributor will always get a set of dependencies that are passing with our tests. In our CI server we delete the lock file to make sure we are always testing against the newest release of our dependencies.
2015-02-18 11:30:25 -05:00
erubis (2.7.0)
Checked in changes to Gemfile.lock on latest master - Eventmachine version gets updated when `bundle` is run locally.
2016-01-17 08:56:10 -05:00
eventmachine (1.0.9.1)
point at rack master
2015-08-20 16:43:57 -04:00
execjs (2.6.0)
Support faye-websocket + EventMachine as an option
2016-03-01 19:50:19 -05:00
faye-websocket (0.10.3)
Add a couple of tests that connect with a WS client
2016-01-24 12:25:53 -05:00
eventmachine (>= 0.12.0)
websocket-driver (>= 0.5.1)
implements an evented file update checker [Puneet Agarwal] This is the implementation of the file update checker written by Puneet Agarwal for GSoC 2015 (except for the tiny version of the listen gem, which was 3.0.2 in the original patch). Puneet's branch became too out of sync with upstream. This is the final work in one single clean commit. Credit goes in the first line using a convention understood by the contrib app.
2015-10-12 14:41:14 -04:00
ffi (1.9.10)
ffi (1.9.10-x64-mingw32)
ffi (1.9.10-x86-mingw32)
Use released GlobalID now that it provides URI::GID::MissingModelIdError for Active Job
2015-12-17 19:20:19 -05:00
globalid (0.3.6)
activesupport (>= 4.1.0)
Bundle update to fix tests locally
2016-01-28 14:57:08 -05:00
hiredis (0.6.1)
Track Gemfile.lock at the repository The main reason is to make bisect easier. In some points, we have a lot of git dependencies. Since we don't have the information of which commit we are referring to, bundler get the latest commit of the master branch of the dependency. This sometimes returns a version that is not compatible with Rails anymore, making the tests fail and the harder to identify the commit that introduced a bug. Also this will make sure that a contributor will always get a set of dependencies that are passing with our tests. In our CI server we delete the lock file to make sure we are always testing against the newest release of our dependencies.
2015-02-18 11:30:25 -05:00
i18n (0.7.0)
Bundle update to fix tests locally
2016-01-28 14:57:08 -05:00
jquery-rails (4.1.0)
Install jquery-rails It will make sure that the generated application in the tests get the gem.
2015-12-18 01:12:50 -05:00
rails-dom-testing (~> 1.0)
railties (>= 4.2.0)
thor (>= 0.14, < 2.0)
Update Gemfile.lock
2015-08-09 23:30:03 -04:00
json (1.8.3)
Track Gemfile.lock at the repository The main reason is to make bisect easier. In some points, we have a lot of git dependencies. Since we don't have the information of which commit we are referring to, bundler get the latest commit of the master branch of the dependency. This sometimes returns a version that is not compatible with Rails anymore, making the tests fail and the harder to identify the commit that introduced a bug. Also this will make sure that a contributor will always get a set of dependencies that are passing with our tests. In our CI server we delete the lock file to make sure we are always testing against the newest release of our dependencies.
2015-02-18 11:30:25 -05:00
kindlerb (0.1.1)
mustache
nokogiri
Upgrade to listen 3.0.5, re-enable tests In listen 3.0.4 and below, the `#stop` method on the notification backends are a no-op, meaning that we are leaking them per test. This ended up triggering another bug in Ruby that causes our builds to fail randomly on CI. listen bug: https://github.com/guard/listen/issues/353 ruby bug: https://bugs.ruby-lang.org/issues/11744
2015-11-26 13:31:52 -05:00
listen (3.0.5)
implements an evented file update checker [Puneet Agarwal] This is the implementation of the file update checker written by Puneet Agarwal for GSoC 2015 (except for the tiny version of the listen gem, which was 3.0.2 in the original patch). Puneet's branch became too out of sync with upstream. This is the final work in one single clean commit. Credit goes in the first line using a convention understood by the contrib app.
2015-10-12 14:41:14 -04:00
rb-fsevent (>= 0.9.3)
rb-inotify (>= 0.9)
point at rack master
2015-08-20 16:43:57 -04:00
loofah (2.0.3)
Track Gemfile.lock at the repository The main reason is to make bisect easier. In some points, we have a lot of git dependencies. Since we don't have the information of which commit we are referring to, bundler get the latest commit of the master branch of the dependency. This sometimes returns a version that is not compatible with Rails anymore, making the tests fail and the harder to identify the commit that introduced a bug. Also this will make sure that a contributor will always get a set of dependencies that are passing with our tests. In our CI server we delete the lock file to make sure we are always testing against the newest release of our dependencies.
2015-02-18 11:30:25 -05:00
nokogiri (>= 1.5.9)
Prep Rails 5 beta 4
2016-04-27 16:47:22 -04:00
mail (2.6.4)
mime-types (>= 1.16, < 4)
Track Gemfile.lock at the repository The main reason is to make bisect easier. In some points, we have a lot of git dependencies. Since we don't have the information of which commit we are referring to, bundler get the latest commit of the master branch of the dependency. This sometimes returns a version that is not compatible with Rails anymore, making the tests fail and the harder to identify the commit that introduced a bug. Also this will make sure that a contributor will always get a set of dependencies that are passing with our tests. In our CI server we delete the lock file to make sure we are always testing against the newest release of our dependencies.
2015-02-18 11:30:25 -05:00
metaclass (0.0.4)
Add method_source to gemfile
2015-01-23 20:34:43 -05:00
method_source (0.8.2)
Prep Rails 5 beta 4
2016-04-27 16:47:22 -04:00
mime-types (3.0)
mime-types-data (~> 3.2015)
mime-types-data (3.2016.0221)
Update nokogiri to 1.6.7 This picks up https://github.com/sparklemotion/nokogiri/pull/1218 which allows nokogiri to compile on Xcode-only OS X systems.
2015-12-10 11:25:25 -05:00
mini_portile2 (2.0.0)
Track Gemfile.lock at the repository The main reason is to make bisect easier. In some points, we have a lot of git dependencies. Since we don't have the information of which commit we are referring to, bundler get the latest commit of the master branch of the dependency. This sometimes returns a version that is not compatible with Rails anymore, making the tests fail and the harder to identify the commit that introduced a bug. Also this will make sure that a contributor will always get a set of dependencies that are passing with our tests. In our CI server we delete the lock file to make sure we are always testing against the newest release of our dependencies.
2015-02-18 11:30:25 -05:00
minitest (5.3.3)
mocha (0.14.0)
metaclass (~> 0.0.1)
mono_logger (1.1.0)
Update Gemfile.lock
2015-08-09 23:30:03 -04:00
multi_json (1.11.2)
mustache (1.0.2)
Add prepared statements support for `Mysql2Adapter`
2016-02-17 09:18:07 -05:00
mysql2 (0.4.4)
mysql2 (0.4.4-x64-mingw32)
mysql2 (0.4.4-x86-mingw32)
Preparing for Rails 5.0.0.beta2
2016-02-01 16:27:38 -05:00
nio4r (1.2.1)
Bundle update to fix tests locally
2016-01-28 14:57:08 -05:00
nokogiri (1.6.7.2)
Update nokogiri to 1.6.7 This picks up https://github.com/sparklemotion/nokogiri/pull/1218 which allows nokogiri to compile on Xcode-only OS X systems.
2015-12-10 11:25:25 -05:00
mini_portile2 (~> 2.0.0.rc2)
Bundle update to fix tests locally
2016-01-28 14:57:08 -05:00
nokogiri (1.6.7.2-x64-mingw32)
Avoid conditionals in the Gemfile "conditionals in the gemfile creates conditional code in the Gemfile.lock. Since it is checked in the repository I think it is better to avoid it"
2015-12-16 12:33:09 -05:00
mini_portile2 (~> 2.0.0.rc2)
Bundle update to fix tests locally
2016-01-28 14:57:08 -05:00
nokogiri (1.6.7.2-x86-mingw32)
Avoid conditionals in the Gemfile "conditionals in the gemfile creates conditional code in the Gemfile.lock. Since it is checked in the repository I think it is better to avoid it"
2015-12-16 12:33:09 -05:00
mini_portile2 (~> 2.0.0.rc2)
Use sprockets 3 in the Rails 5 release
2015-12-16 13:30:58 -05:00
pg (0.18.4)
pg (0.18.4-x64-mingw32)
pg (0.18.4-x86-mingw32)
Bundle update to fix tests locally
2016-01-28 14:57:08 -05:00
psych (2.0.17)
puma (2.16.0)
Ruby 2.2.3 in windows need nokogiri 1.6.7.rc3 as it's the only version having correct pre-compiled so
2015-09-12 10:04:31 -04:00
que (0.11.2)
Use sprockets 3 in the Rails 5 release
2015-12-16 13:30:58 -05:00
racc (1.4.14)
Use released rack
2015-12-18 01:53:38 -05:00
rack (2.0.0.alpha)
json
Use sprockets 3 in the Rails 5 release
2015-12-16 13:30:58 -05:00
rack-cache (1.5.1)
Track Gemfile.lock at the repository The main reason is to make bisect easier. In some points, we have a lot of git dependencies. Since we don't have the information of which commit we are referring to, bundler get the latest commit of the master branch of the dependency. This sometimes returns a version that is not compatible with Rails anymore, making the tests fail and the harder to identify the commit that introduced a bug. Also this will make sure that a contributor will always get a set of dependencies that are passing with our tests. In our CI server we delete the lock file to make sure we are always testing against the newest release of our dependencies.
2015-02-18 11:30:25 -05:00
rack (>= 0.4)
rack-test (0.6.3)
rack (>= 1.0)
rails-deprecated_sanitizer (1.0.3)
activesupport (>= 4.2.0.alpha)
point at rack master
2015-08-20 16:43:57 -04:00
rails-dom-testing (1.0.7)
Track Gemfile.lock at the repository The main reason is to make bisect easier. In some points, we have a lot of git dependencies. Since we don't have the information of which commit we are referring to, bundler get the latest commit of the master branch of the dependency. This sometimes returns a version that is not compatible with Rails anymore, making the tests fail and the harder to identify the commit that introduced a bug. Also this will make sure that a contributor will always get a set of dependencies that are passing with our tests. In our CI server we delete the lock file to make sure we are always testing against the newest release of our dependencies.
2015-02-18 11:30:25 -05:00
activesupport (>= 4.2.0.beta, < 5.0)
nokogiri (~> 1.6.0)
rails-deprecated_sanitizer (>= 1.0.1)
Bundle update to fix tests locally
2016-01-28 14:57:08 -05:00
rails-html-sanitizer (1.0.3)
Use the released gem
2015-03-10 16:31:35 -04:00
loofah (~> 2.0)
Run latest precompiled JRuby on CI only against ActionPack Uses latest precompiled JRuby so that we don't spend time downloading versions Travis has not already compiled. http://rubies.travis-ci.org/ Uses latest jdk: oraclejdk8 per https://docs.travis-ci.com/user/build-environment-updates/2015-02-03/#Ruby-VM and https://docs.travis-ci.com/user/languages/ruby/#Supported-Ruby-Versions-and-RVM Follows on work in https://github.com/rails/rails/pull/23927 which was reverted https://github.com/rails/rails/commit/26fe5fa08d52384bcea09c4210e3b3baaf5e9b95 JRUBY_OPTS minimize GC, disable JIT, for max test speed - https://github.com/rails/rails/pull/16613 - https://github.com/rails/rails/pull/17088 Have Rails use JRuby-compatible Rake 11.1 - The Rake task was passing --verbose, an invalid option, to contemporary JRuby - https://github.com/ruby/rake/pull/120 - https://github.com/rails-api/active_model_serializers/pull/1585 - https://github.com/jruby/jruby/issues/3653#issuecomment-195883717 No advantage to directly mounting JRuby over installing from cache; both on S3 - https://github.com/rails/rails/pull/23499/commits/b2d5b336b5a812009444571b22eed90777cd9a8c - https://github.com/rails/rails/pull/23499/commits/f4fad041b2755d81e82ee3fc66d96f334b4653db
2016-02-05 12:31:18 -05:00
rake (11.1.1)
Bundle update to fix tests locally
2016-01-28 14:57:08 -05:00
rb-fsevent (0.9.7)
implements an evented file update checker [Puneet Agarwal] This is the implementation of the file update checker written by Puneet Agarwal for GSoC 2015 (except for the tiny version of the listen gem, which was 3.0.2 in the original patch). Puneet's branch became too out of sync with upstream. This is the final work in one single clean commit. Credit goes in the first line using a convention understood by the contrib app.
2015-10-12 14:41:14 -04:00
rb-inotify (0.9.5)
ffi (>= 0.5.0)
Bundle update to fix tests locally
2016-01-28 14:57:08 -05:00
rdoc (4.2.1)
redcarpet 3.2.2 has an XSS vulnerability see: http://www.openwall.com/lists/oss-security/2015/04/07/11
2015-04-09 05:20:53 -04:00
redcarpet (3.2.3)
Use sprockets 3 in the Rails 5 release
2015-12-16 13:30:58 -05:00
redis (3.2.2)
Update Gemfile.lock
2015-08-09 23:30:03 -04:00
redis-namespace (1.5.2)
Track Gemfile.lock at the repository The main reason is to make bisect easier. In some points, we have a lot of git dependencies. Since we don't have the information of which commit we are referring to, bundler get the latest commit of the master branch of the dependency. This sometimes returns a version that is not compatible with Rails anymore, making the tests fail and the harder to identify the commit that introduced a bug. Also this will make sure that a contributor will always get a set of dependencies that are passing with our tests. In our CI server we delete the lock file to make sure we are always testing against the newest release of our dependencies.
2015-02-18 11:30:25 -05:00
redis (~> 3.0, >= 3.0.4)
resque (1.25.2)
mono_logger (~> 1.0)
multi_json (~> 1.0)
redis-namespace (~> 1.3)
sinatra (>= 0.9.2)
vegas (~> 0.1.2)
resque-scheduler (4.0.0)
mono_logger (~> 1.0)
redis (~> 3.0)
resque (~> 1.25)
rufus-scheduler (~> 3.0)
Bundle update to fix tests locally
2016-01-28 14:57:08 -05:00
rufus-scheduler (3.2.0)
Track Gemfile.lock at the repository The main reason is to make bisect easier. In some points, we have a lot of git dependencies. Since we don't have the information of which commit we are referring to, bundler get the latest commit of the master branch of the dependency. This sometimes returns a version that is not compatible with Rails anymore, making the tests fail and the harder to identify the commit that introduced a bug. Also this will make sure that a contributor will always get a set of dependencies that are passing with our tests. In our CI server we delete the lock file to make sure we are always testing against the newest release of our dependencies.
2015-02-18 11:30:25 -05:00
sdoc (0.4.1)
json (~> 1.7, >= 1.7.7)
rdoc (~> 4.0)
Bundle update to fix tests locally
2016-01-28 14:57:08 -05:00
sequel (4.30.0)
Upgrade all the gems
2015-10-20 13:58:57 -04:00
serverengine (1.5.11)
Track Gemfile.lock at the repository The main reason is to make bisect easier. In some points, we have a lot of git dependencies. Since we don't have the information of which commit we are referring to, bundler get the latest commit of the master branch of the dependency. This sometimes returns a version that is not compatible with Rails anymore, making the tests fail and the harder to identify the commit that introduced a bug. Also this will make sure that a contributor will always get a set of dependencies that are passing with our tests. In our CI server we delete the lock file to make sure we are always testing against the newest release of our dependencies.
2015-02-18 11:30:25 -05:00
sigdump (~> 0.2.2)
Bundle update to fix tests locally
2016-01-28 14:57:08 -05:00
sidekiq (4.0.2)
Use sprockets 3 in the Rails 5 release
2015-12-16 13:30:58 -05:00
concurrent-ruby (~> 1.0)
Update Gemfile.lock
2015-08-09 23:30:03 -04:00
connection_pool (~> 2.2, >= 2.2.0)
redis (~> 3.2, >= 3.2.1)
sigdump (0.2.3)
point at rack master
2015-08-20 16:43:57 -04:00
sinatra (1.0)
rack (>= 1.0)
Upgrade all the gems
2015-10-20 13:58:57 -04:00
sneakers (2.3.5)
Ruby 2.2.3 in windows need nokogiri 1.6.7.rc3 as it's the only version having correct pre-compiled so
2015-09-12 10:04:31 -04:00
bunny (~> 2.2.0)
Upgrade all the gems
2015-10-20 13:58:57 -04:00
serverengine (~> 1.5.11)
Track Gemfile.lock at the repository The main reason is to make bisect easier. In some points, we have a lot of git dependencies. Since we don't have the information of which commit we are referring to, bundler get the latest commit of the master branch of the dependency. This sometimes returns a version that is not compatible with Rails anymore, making the tests fail and the harder to identify the commit that introduced a bug. Also this will make sure that a contributor will always get a set of dependencies that are passing with our tests. In our CI server we delete the lock file to make sure we are always testing against the newest release of our dependencies.
2015-02-18 11:30:25 -05:00
thor
Unlock sneakers adapter version
2015-04-26 03:44:18 -04:00
thread (~> 0.1.7)
Use sprockets 3 in the Rails 5 release
2015-12-16 13:30:58 -05:00
sprockets (3.5.2)
concurrent-ruby (~> 1.0)
rack (> 1, < 3)
Add test to make sure the sprockets cache is not shared per environment
2016-03-02 12:21:38 -05:00
sprockets-rails (3.0.4)
Use release sprockets-rails
2015-12-17 15:22:58 -05:00
actionpack (>= 4.0)
activesupport (>= 4.0)
sprockets (>= 3.0.0)
Upgrade all the gems
2015-10-20 13:58:57 -04:00
sqlite3 (1.3.11)
Avoid conditionals in the Gemfile "conditionals in the gemfile creates conditional code in the Gemfile.lock. Since it is checked in the repository I think it is better to avoid it"
2015-12-16 12:33:09 -05:00
sqlite3 (1.3.11-x64-mingw32)
sqlite3 (1.3.11-x86-mingw32)
Bundle update to fix tests locally
2016-01-28 14:57:08 -05:00
stackprof (0.2.8)
Update ActiveJob adapter for sucker_punch 2.0 This PR includes two changes for 2.0.0: - Breaking API change around `async.perform` --> `perform_async` - New addition of `perform_in`, which now allows end users of the adapter to use the `enqueued_at` public API method.
2016-01-27 11:29:18 -05:00
sucker_punch (2.0.0)
concurrent-ruby (~> 1.0.0)
Track Gemfile.lock at the repository The main reason is to make bisect easier. In some points, we have a lot of git dependencies. Since we don't have the information of which commit we are referring to, bundler get the latest commit of the master branch of the dependency. This sometimes returns a version that is not compatible with Rails anymore, making the tests fail and the harder to identify the commit that introduced a bug. Also this will make sure that a contributor will always get a set of dependencies that are passing with our tests. In our CI server we delete the lock file to make sure we are always testing against the newest release of our dependencies.
2015-02-18 11:30:25 -05:00
thor (0.19.1)
Unlock sneakers adapter version
2015-04-26 03:44:18 -04:00
thread (0.1.7)
Use latest sprockets-rails on internal dev
2015-04-26 11:42:13 -04:00
thread_safe (0.3.5)
Update to the latest Turbolinks gems
2016-02-23 18:56:19 -05:00
turbolinks-source (5.0.0.beta2)
Track Gemfile.lock at the repository The main reason is to make bisect easier. In some points, we have a lot of git dependencies. Since we don't have the information of which commit we are referring to, bundler get the latest commit of the master branch of the dependency. This sometimes returns a version that is not compatible with Rails anymore, making the tests fail and the harder to identify the commit that introduced a bug. Also this will make sure that a contributor will always get a set of dependencies that are passing with our tests. In our CI server we delete the lock file to make sure we are always testing against the newest release of our dependencies.
2015-02-18 11:30:25 -05:00
tzinfo (1.2.2)
thread_safe (~> 0.1)
Upgrade all the gems
2015-10-20 13:58:57 -04:00
tzinfo-data (1.2015.7)
Ruby 2.2.3 in windows need nokogiri 1.6.7.rc3 as it's the only version having correct pre-compiled so
2015-09-12 10:04:31 -04:00
tzinfo (>= 1.0.0)
uglifier (2.7.2)
Track Gemfile.lock at the repository The main reason is to make bisect easier. In some points, we have a lot of git dependencies. Since we don't have the information of which commit we are referring to, bundler get the latest commit of the master branch of the dependency. This sometimes returns a version that is not compatible with Rails anymore, making the tests fail and the harder to identify the commit that introduced a bug. Also this will make sure that a contributor will always get a set of dependencies that are passing with our tests. In our CI server we delete the lock file to make sure we are always testing against the newest release of our dependencies.
2015-02-18 11:30:25 -05:00
execjs (>= 0.3.0)
json (>= 1.8.0)
vegas (0.1.11)
rack (>= 1.0.0)
w3c_validators (1.2)
json
nokogiri
Make file update checker tests more resilient on Windows Without the `wdm` gem, it appears that `listen` keeps an open handle to each of these files, causing them not to be removed when the tempdir tries to clean iteslf up, and then directory to fail to unlink. In addition to fixing that particular failure, we now construct OS agnostic paths, and capture exceptions if the directory fails to unlink so that minitest will report it rather than crash
2016-04-21 12:54:54 -04:00
wdm (0.1.1)
Initial stab at adding Action Cable to rails/master
2015-12-14 10:38:37 -05:00
websocket-driver (0.6.3)
websocket-extensions (>= 0.1.0)
websocket-extensions (0.1.2)
Track Gemfile.lock at the repository The main reason is to make bisect easier. In some points, we have a lot of git dependencies. Since we don't have the information of which commit we are referring to, bundler get the latest commit of the master branch of the dependency. This sometimes returns a version that is not compatible with Rails anymore, making the tests fail and the harder to identify the commit that introduced a bug. Also this will make sure that a contributor will always get a set of dependencies that are passing with our tests. In our CI server we delete the lock file to make sure we are always testing against the newest release of our dependencies.
2015-02-18 11:30:25 -05:00
PLATFORMS
ruby
Gemfile: temporay pin "bcrypt" version and run "bundle update bcrypt" on Linux Related: #19617, #19187, #19533, #19689, #19675. This is POC (Proof Of Concept) which bundler does not remove mingw lines. https://github.com/rails/rails/pull/19617#issuecomment-90293795
2015-04-06 19:35:02 -04:00
x64-mingw32
x86-mingw32
Track Gemfile.lock at the repository The main reason is to make bisect easier. In some points, we have a lot of git dependencies. Since we don't have the information of which commit we are referring to, bundler get the latest commit of the master branch of the dependency. This sometimes returns a version that is not compatible with Rails anymore, making the tests fail and the harder to identify the commit that introduced a bug. Also this will make sure that a contributor will always get a set of dependencies that are passing with our tests. In our CI server we delete the lock file to make sure we are always testing against the newest release of our dependencies.
2015-02-18 11:30:25 -05:00
DEPENDENCIES
activerecord-jdbcmysql-adapter (>= 1.3.0)
activerecord-jdbcpostgresql-adapter (>= 1.3.0)
activerecord-jdbcsqlite3-adapter (>= 1.3.0)
backburner
Fix Gemfile.lock
2016-03-10 14:28:02 -05:00
bcrypt (~> 3.1.11)
Track Gemfile.lock at the repository The main reason is to make bisect easier. In some points, we have a lot of git dependencies. Since we don't have the information of which commit we are referring to, bundler get the latest commit of the master branch of the dependency. This sometimes returns a version that is not compatible with Rails anymore, making the tests fail and the harder to identify the commit that introduced a bug. Also this will make sure that a contributor will always get a set of dependencies that are passing with our tests. In our CI server we delete the lock file to make sure we are always testing against the newest release of our dependencies.
2015-02-18 11:30:25 -05:00
benchmark-ips
Uncomment byebug in framework Gemfile History: 1. `debugger` was there until d2ed433b where it was commented out, and I couldn't figure out why 2. Since then we inherited that when switching to `byebug` in 93559da4 Reasons: 1. It's nice to have a debugger when working on framework bugs 2. It's an uncommented dependency in app Gemfiles since Rails 4.2 (see fbe38c9e)
2015-04-24 01:24:50 -04:00
byebug
Track Gemfile.lock at the repository The main reason is to make bisect easier. In some points, we have a lot of git dependencies. Since we don't have the information of which commit we are referring to, bundler get the latest commit of the master branch of the dependency. This sometimes returns a version that is not compatible with Rails anymore, making the tests fail and the harder to identify the commit that introduced a bug. Also this will make sure that a contributor will always get a set of dependencies that are passing with our tests. In our CI server we delete the lock file to make sure we are always testing against the newest release of our dependencies.
2015-02-18 11:30:25 -05:00
coffee-rails (~> 4.1.0)
dalli (>= 2.2.1)
delayed_job
Fixed ActiveJob integration tests
2015-03-05 16:41:14 -05:00
delayed_job_active_record
Add tests for the ActionCable adapters
2016-01-24 05:43:40 -05:00
em-hiredis
Add a couple of tests that connect with a WS client
2016-01-24 12:25:53 -05:00
faye-websocket
Switch the default redis adapter to a single-stream model This new adapter does get a little more intimate with the redis-rb gem's implementation than I would like, but it's the least bad of the approaches I've come up with.
2016-01-31 10:00:00 -05:00
hiredis
Install jquery-rails It will make sure that the generated application in the tests get the gem.
2015-12-18 01:12:50 -05:00
jquery-rails
Track Gemfile.lock at the repository The main reason is to make bisect easier. In some points, we have a lot of git dependencies. Since we don't have the information of which commit we are referring to, bundler get the latest commit of the master branch of the dependency. This sometimes returns a version that is not compatible with Rails anymore, making the tests fail and the harder to identify the commit that introduced a bug. Also this will make sure that a contributor will always get a set of dependencies that are passing with our tests. In our CI server we delete the lock file to make sure we are always testing against the newest release of our dependencies.
2015-02-18 11:30:25 -05:00
kindlerb (= 0.1.1)
Upgrade to listen 3.0.5, re-enable tests In listen 3.0.4 and below, the `#stop` method on the notification backends are a no-op, meaning that we are leaking them per test. This ended up triggering another bug in Ruby that causes our builds to fail randomly on CI. listen bug: https://github.com/guard/listen/issues/353 ruby bug: https://bugs.ruby-lang.org/issues/11744
2015-11-26 13:31:52 -05:00
listen (~> 3.0.5)
Track Gemfile.lock at the repository The main reason is to make bisect easier. In some points, we have a lot of git dependencies. Since we don't have the information of which commit we are referring to, bundler get the latest commit of the master branch of the dependency. This sometimes returns a version that is not compatible with Rails anymore, making the tests fail and the harder to identify the commit that introduced a bug. Also this will make sure that a contributor will always get a set of dependencies that are passing with our tests. In our CI server we delete the lock file to make sure we are always testing against the newest release of our dependencies.
2015-02-18 11:30:25 -05:00
minitest (< 5.3.4)
mocha (~> 0.14)
Add prepared statements support for `Mysql2Adapter`
2016-02-17 09:18:07 -05:00
mysql2 (>= 0.4.4)
Require Nokogiri >= 1.6.7.1 Many CVEs released: https://groups.google.com/forum/#!topic/ruby-security-ann/aSbgDiwb24s
2015-12-17 17:35:25 -05:00
nokogiri (>= 1.6.7.1)
Track Gemfile.lock at the repository The main reason is to make bisect easier. In some points, we have a lot of git dependencies. Since we don't have the information of which commit we are referring to, bundler get the latest commit of the master branch of the dependency. This sometimes returns a version that is not compatible with Rails anymore, making the tests fail and the harder to identify the commit that introduced a bug. Also this will make sure that a contributor will always get a set of dependencies that are passing with our tests. In our CI server we delete the lock file to make sure we are always testing against the newest release of our dependencies.
2015-02-18 11:30:25 -05:00
pg (>= 0.18.0)
psych (~> 2.0)
Initial stab at adding Action Cable to rails/master
2015-12-14 10:38:37 -05:00
puma
Track Gemfile.lock at the repository The main reason is to make bisect easier. In some points, we have a lot of git dependencies. Since we don't have the information of which commit we are referring to, bundler get the latest commit of the master branch of the dependency. This sometimes returns a version that is not compatible with Rails anymore, making the tests fail and the harder to identify the commit that introduced a bug. Also this will make sure that a contributor will always get a set of dependencies that are passing with our tests. In our CI server we delete the lock file to make sure we are always testing against the newest release of our dependencies.
2015-02-18 11:30:25 -05:00
qu-rails!
qu-redis
que
implement `provider_job_id` for `queue_classic`. The latest, currently unreleased, version of queue_classic is required for this to work. See https://github.com/QueueClassic/queue_classic/pull/262 for more details.
2015-08-13 03:56:06 -04:00
queue_classic!
Track Gemfile.lock at the repository The main reason is to make bisect easier. In some points, we have a lot of git dependencies. Since we don't have the information of which commit we are referring to, bundler get the latest commit of the master branch of the dependency. This sometimes returns a version that is not compatible with Rails anymore, making the tests fail and the harder to identify the commit that introduced a bug. Also this will make sure that a contributor will always get a set of dependencies that are passing with our tests. In our CI server we delete the lock file to make sure we are always testing against the newest release of our dependencies.
2015-02-18 11:30:25 -05:00
racc (>= 1.4.6)
rack-cache (~> 1.2)
rails!
Update Gemfile.lock 'rake' gem is bundled to '>= 11.1' by 30279704646fff33e64c71ee3c4de34bf75232c4 (#23499), but it seems the commit did not fully include Gemfile.lock's.
2016-03-30 12:12:20 -04:00
rake (>= 11.1)
redcarpet 3.2.2 has an XSS vulnerability see: http://www.openwall.com/lists/oss-security/2015/04/07/11
2015-04-09 05:20:53 -04:00
redcarpet (~> 3.2.3)
Add tests for the ActionCable adapters
2016-01-24 05:43:40 -05:00
redis
Fix Gemfile.lock - Resque version was locked to < 1.26 in 92f869a0c85268 but Gemfile.lock was not updated.
2016-03-11 21:52:15 -05:00
resque (< 1.26)
Track Gemfile.lock at the repository The main reason is to make bisect easier. In some points, we have a lot of git dependencies. Since we don't have the information of which commit we are referring to, bundler get the latest commit of the master branch of the dependency. This sometimes returns a version that is not compatible with Rails anymore, making the tests fail and the harder to identify the commit that introduced a bug. Also this will make sure that a contributor will always get a set of dependencies that are passing with our tests. In our CI server we delete the lock file to make sure we are always testing against the newest release of our dependencies.
2015-02-18 11:30:25 -05:00
resque-scheduler
run against edge sass to eliminate circular require warnings
2015-09-30 10:42:31 -04:00
sass!
Track Gemfile.lock at the repository The main reason is to make bisect easier. In some points, we have a lot of git dependencies. Since we don't have the information of which commit we are referring to, bundler get the latest commit of the master branch of the dependency. This sometimes returns a version that is not compatible with Rails anymore, making the tests fail and the harder to identify the commit that introduced a bug. Also this will make sure that a contributor will always get a set of dependencies that are passing with our tests. In our CI server we delete the lock file to make sure we are always testing against the newest release of our dependencies.
2015-02-18 11:30:25 -05:00
sdoc (~> 0.4.0)
sequel
sidekiq
Unlock sneakers adapter version
2015-04-26 03:44:18 -04:00
sneakers
Track Gemfile.lock at the repository The main reason is to make bisect easier. In some points, we have a lot of git dependencies. Since we don't have the information of which commit we are referring to, bundler get the latest commit of the master branch of the dependency. This sometimes returns a version that is not compatible with Rails anymore, making the tests fail and the harder to identify the commit that introduced a bug. Also this will make sure that a contributor will always get a set of dependencies that are passing with our tests. In our CI server we delete the lock file to make sure we are always testing against the newest release of our dependencies.
2015-02-18 11:30:25 -05:00
sqlite3 (~> 1.3.6)
stackprof
Update ActiveJob adapter for sucker_punch 2.0 This PR includes two changes for 2.0.0: - Breaking API change around `async.perform` --> `perform_async` - New addition of `perform_in`, which now allows end users of the adapter to use the `enqueued_at` public API method.
2016-01-27 11:29:18 -05:00
sucker_punch
Update turbolinks-rails for passing railties test Ref - https://github.com/turbolinks/turbolinks-rails/pull/3
2016-02-05 06:32:22 -05:00
turbolinks!
Ruby 2.2.3 in windows need nokogiri 1.6.7.rc3 as it's the only version having correct pre-compiled so
2015-09-12 10:04:31 -04:00
tzinfo-data
Track Gemfile.lock at the repository The main reason is to make bisect easier. In some points, we have a lot of git dependencies. Since we don't have the information of which commit we are referring to, bundler get the latest commit of the master branch of the dependency. This sometimes returns a version that is not compatible with Rails anymore, making the tests fail and the harder to identify the commit that introduced a bug. Also this will make sure that a contributor will always get a set of dependencies that are passing with our tests. In our CI server we delete the lock file to make sure we are always testing against the newest release of our dependencies.
2015-02-18 11:30:25 -05:00
uglifier (>= 1.3.0)
w3c_validators
Make file update checker tests more resilient on Windows Without the `wdm` gem, it appears that `listen` keeps an open handle to each of these files, causing them not to be removed when the tempdir tries to clean iteslf up, and then directory to fail to unlink. In addition to fixing that particular failure, we now construct OS agnostic paths, and capture exceptions if the directory fails to unlink so that minitest will report it rather than crash
2016-04-21 12:54:54 -04:00
wdm (>= 0.1.0)
Generate Bundler 1.10.1 lockfile
2015-05-29 01:40:29 -04:00
BUNDLED WITH
Add mysql back to the Gemfile I didn't mean to commit that!
2015-12-16 15:59:00 -05:00
1.11.2
Copy permalink