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

439 lines
10 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
Override the github git source instead of changing manually all entries
2016-09-13 20:19:09 -04:00
remote: https://github.com/QueueClassic/queue_classic.git
Allow the use of listen's 3.1.x branch. When the initial evented monitor feature was written, the latest version of listen was the 3.0.x series. Since then the listen project has moved on to the 3.1.x series. This patch allows the use of the new versions.
2016-10-03 07:28:17 -04:00
revision: 51d56ca6fa2fdf1eeffdffd702ae1cc0940b5156
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)
Allow the use of listen's 3.1.x branch. When the initial evented monitor feature was written, the latest version of listen was the 3.0.x series. Since then the listen project has moved on to the 3.1.x series. This patch allows the use of the new versions.
2016-10-03 07:28:17 -04:00
pg (>= 0.17, < 0.20)
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
Test thor master
2017-07-07 15:16:39 -04:00
GIT
remote: https://github.com/erikhuda/thor.git
revision: df5ba2b653a28087b3617d6c082b00866b0c0d6c
specs:
thor (0.19.4)
Use a branch of websocket-client-simple, to work around read/close race
2016-10-05 21:11:18 -04:00
GIT
remote: https://github.com/matthewd/websocket-client-simple.git
revision: e161305f1a466b9398d86df3b1731b03362da91b
branch: close-race
specs:
websocket-client-simple (0.3.0)
event_emitter
websocket
Start Rails 5.2 development
2017-03-21 19:41:39 -04:00
GIT
remote: https://github.com/rails/arel.git
Use bulk INSERT to insert fixtures Improves the performance from O(n) to O(1). Previously it would require 50 queries to insert 50 fixtures. Now it takes only one query. Disabled on sqlite which doesn't support multiple inserts.
2017-06-18 11:14:52 -04:00
revision: 67a51c62f4e19390cd8eb408596ca48bb0806362
Start Rails 5.2 development
2017-03-21 19:41:39 -04:00
specs:
arel (8.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
PATH
remote: .
specs:
Start Rails 5.2 development
2017-03-21 19:41:39 -04:00
actioncable (5.2.0.alpha)
actionpack (= 5.2.0.alpha)
Upgrade to nio4r 2.0.0 nio4r 2.0.0 primarily includes new features and bugfixes, with few breaking changes. The primary reason for bumping the major version is dropping support for all Ruby versions prior to 2.2.2, so as to match Rails 5. Full release announcement here: https://groups.google.com/forum/#!topic/socketry/ZDIUj1ufiJ8
2016-12-28 22:45:39 -05:00
nio4r (~> 2.0)
Initial stab at adding Action Cable to rails/master
2015-12-14 10:38:37 -05:00
websocket-driver (~> 0.6.1)
Start Rails 5.2 development
2017-03-21 19:41:39 -04:00
actionmailer (5.2.0.alpha)
actionpack (= 5.2.0.alpha)
actionview (= 5.2.0.alpha)
activejob (= 5.2.0.alpha)
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)
Fix Gemfile.lock by updating rails-dom-testing - Followup of https://github.com/rails/rails/pull/24946.
2016-05-10 01:13:56 -04:00
rails-dom-testing (~> 2.0)
Start Rails 5.2 development
2017-03-21 19:41:39 -04:00
actionpack (5.2.0.alpha)
actionview (= 5.2.0.alpha)
activesupport (= 5.2.0.alpha)
Do not allow rack pre releases
2016-06-30 14:10:22 -04:00
rack (~> 2.0)
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)
Fix Gemfile.lock by updating rails-dom-testing - Followup of https://github.com/rails/rails/pull/24946.
2016-05-10 01:13:56 -04:00
rails-dom-testing (~> 2.0)
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)
Start Rails 5.2 development
2017-03-21 19:41:39 -04:00
actionview (5.2.0.alpha)
activesupport (= 5.2.0.alpha)
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)
Change ActionView ERB Handler from Erubis to Erubi Erubi offers the following advantages for Rails: * Works with ruby's --enable-frozen-string-literal option * Has 88% smaller memory footprint * Does no freedom patching (Erubis adds a method to Kernel) * Has simpler internals (1 file, <150 lines of code) * Has an open development model (Erubis doesn't have a public source control repository or bug tracker) * Is not dead (Erubis hasn't been updated since 2011) Erubi is a simplified fork of Erubis that contains just the parts that are generally needed (which includes the parts that Rails uses). The only intentional difference in behavior is that it does not include support for <%=== tags for debug output. That could be added to the ActionView ERB handler if it is desired. The Erubis template handler remains in a deprecated state so that code that accesses it directly does not break. It can be removed after Rails 5.1.
2017-01-20 18:02:34 -05:00
erubi (~> 1.4)
Fix Gemfile.lock by updating rails-dom-testing - Followup of https://github.com/rails/rails/pull/24946.
2016-05-10 01:13:56 -04:00
rails-dom-testing (~> 2.0)
bundle update some gems * puma 3.7.0: to let kill("TERM") properly terminate the process in railties test (3.6.2 doesnot on my machine) * amq-protocol 2.1.0: to reduce warnings in AJ tests * rails-html-sanitizer: missing change in a previous commit that updated Gemfile
2017-01-28 15:36:15 -05:00
rails-html-sanitizer (~> 1.0, >= 1.0.3)
Start Rails 5.2 development
2017-03-21 19:41:39 -04:00
activejob (5.2.0.alpha)
activesupport (= 5.2.0.alpha)
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)
Start Rails 5.2 development
2017-03-21 19:41:39 -04:00
activemodel (5.2.0.alpha)
activesupport (= 5.2.0.alpha)
activerecord (5.2.0.alpha)
activemodel (= 5.2.0.alpha)
activesupport (= 5.2.0.alpha)
Remove deprecated support to passing a column to #quote
2016-12-29 02:20:50 -05:00
arel (~> 8.0)
Start Rails 5.2 development
2017-03-21 19:41:39 -04:00
activesupport (5.2.0.alpha)
Fix template resolver cache concurrency: "can't add a new key into hash during iteration" Resolved by https://github.com/ruby-concurrency/concurrent-ruby/pull/529 Fixes #24627.
2016-05-02 18:04:59 -04:00
concurrent-ruby (~> 1.0, >= 1.0.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
i18n (~> 0.7)
minitest (~> 5.1)
tzinfo (~> 1.1)
Start Rails 5.2 development
2017-03-21 19:41:39 -04:00
rails (5.2.0.alpha)
actioncable (= 5.2.0.alpha)
actionmailer (= 5.2.0.alpha)
actionpack (= 5.2.0.alpha)
actionview (= 5.2.0.alpha)
activejob (= 5.2.0.alpha)
activemodel (= 5.2.0.alpha)
activerecord (= 5.2.0.alpha)
activesupport (= 5.2.0.alpha)
Commit gemfile.lock
2017-07-04 14:54:26 -04:00
bundler (>= 1.3.0)
Start Rails 5.2 development
2017-03-21 19:41:39 -04:00
railties (= 5.2.0.alpha)
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)
Start Rails 5.2 development
2017-03-21 19:41:39 -04:00
railties (5.2.0.alpha)
actionpack (= 5.2.0.alpha)
activesupport (= 5.2.0.alpha)
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:
Allow capybara minor releases Capybara 2.14.0 was released. Loosen the tight constraint in the generated Gemfile, so that Rails applications can take advantage of the new version
2017-05-05 11:23:59 -04:00
addressable (2.5.1)
Bump Blade and its Sauce Labs plugin to fix tunnel shutdown and related error https://travis-ci.org/rails/rails/jobs/165766716#L506
2016-11-20 17:08:31 -05:00
public_suffix (~> 2.0, >= 2.0.2)
bundle update some gems * puma 3.7.0: to let kill("TERM") properly terminate the process in railties test (3.6.2 doesnot on my machine) * amq-protocol 2.1.0: to reduce warnings in AJ tests * rails-html-sanitizer: missing change in a previous commit that updated Gemfile
2017-01-28 15:36:15 -05:00
amq-protocol (2.1.0)
Add rubocop to Gemfile
2016-11-27 22:12:33 -05:00
ast (2.3.0)
Allow the use of listen's 3.1.x branch. When the initial evented monitor feature was written, the latest version of listen was the 3.0.x series. Since then the listen project has moved on to the 3.1.x series. This patch allows the use of the new versions.
2016-10-03 07:28:17 -04:00
backburner (1.3.1)
Update Gemfile.lock
2015-08-09 23:30:03 -04:00
beaneater (~> 1.0)
Allow the use of listen's 3.1.x branch. When the initial evented monitor feature was written, the latest version of listen was the 3.0.x series. Since then the listen project has moved on to the 3.1.x series. This patch allows the use of the new versions.
2016-10-03 07:28:17 -04:00
concurrent-ruby (~> 1.0.1)
Update Gemfile.lock
2015-08-09 23:30:03 -04:00
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)
Override the github git source instead of changing manually all entries
2016-09-13 20:19:09 -04:00
benchmark-ips (2.7.2)
bundle update
2016-12-26 07:46:01 -05:00
blade (0.7.0)
Add accidentally removed dependency in Gemfile.lock Follow up to ca0b6d0d416776655ed7516ac18f126fbde5315a.
2016-08-03 18:55:47 -04:00
activesupport (>= 3.0.0)
Bump Blade and its Sauce Labs plugin to fix tunnel shutdown and related error https://travis-ci.org/rails/rails/jobs/165766716#L506
2016-11-20 17:08:31 -05:00
blade-qunit_adapter (~> 2.0.1)
Add accidentally removed dependency in Gemfile.lock Follow up to ca0b6d0d416776655ed7516ac18f126fbde5315a.
2016-08-03 18:55:47 -04:00
coffee-script
coffee-script-source
curses (~> 1.0.0)
eventmachine
faye
sprockets (>= 3.0)
thin (>= 1.6.0)
thor (~> 0.19.1)
useragent (~> 0.16.7)
Bump Blade and its Sauce Labs plugin to fix tunnel shutdown and related error https://travis-ci.org/rails/rails/jobs/165766716#L506
2016-11-20 17:08:31 -05:00
blade-qunit_adapter (2.0.1)
bundle update
2016-12-26 07:46:01 -05:00
blade-sauce_labs_plugin (0.6.2)
Add accidentally removed dependency in Gemfile.lock Follow up to ca0b6d0d416776655ed7516ac18f126fbde5315a.
2016-08-03 18:55:47 -04:00
childprocess
faraday
selenium-webdriver
Update builder gem to avoid deprecations of 2.4
2017-01-13 13:50:25 -05:00
builder (3.2.3)
bundle update
2016-12-26 07:46:01 -05:00
bunny (2.6.2)
Bundle update to fix tests locally
2016-01-28 14:57:08 -05:00
amq-protocol (>= 2.0.1)
Allow the use of listen's 3.1.x branch. When the initial evented monitor feature was written, the latest version of listen was the 3.0.x series. Since then the listen project has moved on to the 3.1.x series. This patch allows the use of the new versions.
2016-10-03 07:28:17 -04:00
byebug (9.0.6)
Bundle capybara 2.14.1 that includes fix for Ruby warnings Ref: https://github.com/teamcapybara/capybara/pull/1868
2017-06-07 22:14:54 -04:00
capybara (2.14.1)
Add tests for system testing * Adds test case test * Adds driver adapter test * Adds tests for capybara seleium driver (testing the settings not actually opening the browser to test capybara w/ selenium because that would so so so slow) * Adds tests for rack test driver * Adds tests for generators
2016-08-27 16:48:24 -04:00
addressable
mime-types (>= 1.16)
nokogiri (>= 1.3.3)
rack (>= 1.0.0)
rack-test (>= 0.5.4)
xpath (~> 2.0)
Add accidentally removed dependency in Gemfile.lock Follow up to ca0b6d0d416776655ed7516ac18f126fbde5315a.
2016-08-03 18:55:47 -04:00
childprocess (0.5.9)
ffi (~> 1.0, >= 1.0.11)
Point to released coffee-rails
2016-06-30 13:35:25 -04:00
coffee-rails (4.2.1)
coffee-script (>= 2.2.0)
railties (>= 4.0.0, < 5.2.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
Bump coffee-script-source to fix bug Coffee script 1.12.1 was released and contained a bug where coffee script was undefined. 1.12.1 was yanked and 1.12.2 was released. This bumps coffee-script-source so that CI Railties tests pass. See: https://github.com/jashkenas/coffeescript/issues/4403
2016-12-16 10:43:44 -05:00
coffee-script-source (1.12.2)
Bump the bundled GlobalID version.
2017-04-16 11:40:00 -04:00
concurrent-ruby (1.0.5)
bundle update
2016-12-26 07:46:01 -05:00
connection_pool (2.2.1)
Override the github git source instead of changing manually all entries
2016-09-13 20:19:09 -04:00
cookiejar (0.3.3)
Add accidentally removed dependency in Gemfile.lock Follow up to ca0b6d0d416776655ed7516ac18f126fbde5315a.
2016-08-03 18:55:47 -04:00
curses (1.0.2)
Override the github git source instead of changing manually all entries
2016-09-13 20:19:09 -04:00
daemons (1.2.4)
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)
Bump `delayed_job_active_record` gem
2017-05-28 08:33:03 -04:00
delayed_job (4.1.3)
activesupport (>= 3.0, < 5.2)
delayed_job_active_record (4.1.2)
activerecord (>= 3.0, < 5.2)
delayed_job and delayed_job_active_record gems with AR5 support are available
2017-01-28 19:05:06 -05:00
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)
Override the github git source instead of changing manually all entries
2016-09-13 20:19:09 -04:00
em-http-request (1.1.5)
Remove Blade gem dependency Apps that depend on Action Cable don't need Blade for app development, so we can remove the gem dependency. We do need Blade for Action Cable dev, so we bundle it in the Gemfile. Signed-off-by: Jeremy Daer <jeremydaer@gmail.com>
2016-05-21 14:15:58 -04:00
addressable (>= 2.3.4)
Override the github git source instead of changing manually all entries
2016-09-13 20:19:09 -04:00
cookiejar (!= 0.3.1)
Remove Blade gem dependency Apps that depend on Action Cable don't need Blade for app development, so we can remove the gem dependency. We do need Blade for Action Cable dev, so we bundle it in the Gemfile. Signed-off-by: Jeremy Daer <jeremydaer@gmail.com>
2016-05-21 14:15:58 -04:00
em-socksify (>= 0.3)
eventmachine (>= 1.0.3)
http_parser.rb (>= 0.6.0)
em-socksify (0.3.1)
eventmachine (>= 1.0.0.beta.4)
Start Rails 5.2 development
2017-03-21 19:41:39 -04:00
erubi (1.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)
Use websocket-client-simple instead of Faye as a websockets client Mostly, this is just to avoid EventMachine. But there's also an argument to be made that we're better off using a different protocol library for our test suite than the one we use to implement the server.
2016-10-01 20:39:18 -04:00
event_emitter (0.2.5)
Bump Blade and its Sauce Labs plugin to fix tunnel shutdown and related error https://travis-ci.org/rails/rails/jobs/165766716#L506
2016-11-20 17:08:31 -05:00
eventmachine (1.2.1)
eventmachine (1.2.1-x64-mingw32)
eventmachine (1.2.1-x86-mingw32)
Update Blade and its Sauce Labs plugin for EventMachine 1.2 compatibility
2016-06-04 18:54:34 -04:00
execjs (2.7.0)
Fix all rubocop violations
2017-01-17 22:10:14 -05:00
faraday (0.11.0)
Add accidentally removed dependency in Gemfile.lock Follow up to ca0b6d0d416776655ed7516ac18f126fbde5315a.
2016-08-03 18:55:47 -04:00
multipart-post (>= 1.2, < 3)
Bump Blade and its Sauce Labs plugin to fix tunnel shutdown and related error https://travis-ci.org/rails/rails/jobs/165766716#L506
2016-11-20 17:08:31 -05:00
faye (1.2.3)
Remove Blade gem dependency Apps that depend on Action Cable don't need Blade for app development, so we can remove the gem dependency. We do need Blade for Action Cable dev, so we bundle it in the Gemfile. Signed-off-by: Jeremy Daer <jeremydaer@gmail.com>
2016-05-21 14:15:58 -04:00
cookiejar (>= 0.3.0)
em-http-request (>= 0.3.0)
eventmachine (>= 0.12.0)
faye-websocket (>= 0.9.1)
multi_json (>= 1.0.0)
rack (>= 1.0.0)
websocket-driver (>= 0.5.1)
Bump Blade and its Sauce Labs plugin to fix tunnel shutdown and related error https://travis-ci.org/rails/rails/jobs/165766716#L506
2016-11-20 17:08:31 -05:00
faye-websocket (0.10.5)
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)
Fix all rubocop violations
2017-01-17 22:10:14 -05:00
ffi (1.9.17)
Fix rubocop violations
2017-02-09 21:13:41 -05:00
ffi (1.9.17-x64-mingw32)
ffi (1.9.17-x86-mingw32)
Bump the bundled GlobalID version.
2017-04-16 11:40:00 -04:00
globalid (0.4.0)
activesupport (>= 4.2.0)
Bundle update to fix tests locally
2016-01-28 14:57:08 -05:00
hiredis (0.6.1)
Remove Blade gem dependency Apps that depend on Action Cable don't need Blade for app development, so we can remove the gem dependency. We do need Blade for Action Cable dev, so we bundle it in the Gemfile. Signed-off-by: Jeremy Daer <jeremydaer@gmail.com>
2016-05-21 14:15:58 -04:00
http_parser.rb (0.6.0)
Preparing for 5.1.0.beta1 release
2017-02-23 14:53:12 -05:00
i18n (0.8.1)
Fix all rubocop violations
2017-01-17 22:10:14 -05:00
jquery-rails (4.2.2)
Upgrade all gems to make sure Rails works with rack 2.0.0.rc1
2016-05-06 17:16:28 -04:00
rails-dom-testing (>= 1, < 3)
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
railties (>= 4.2.0)
thor (>= 0.14, < 2.0)
Fix all rubocop violations
2017-01-17 22:10:14 -05:00
json (2.0.3)
Fix rake guides:generate:kindle error
2016-12-18 10:13:50 -05:00
kindlerb (1.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
mustache
nokogiri
Install libxml-ruby gem so full XMLMini test suite can be run
2016-11-19 10:46:28 -05:00
libxml-ruby (2.9.0)
Allow the use of listen's 3.1.x branch. When the initial evented monitor feature was written, the latest version of listen was the 3.0.x series. Since then the listen project has moved on to the 3.1.x series. This patch allows the use of the new versions.
2016-10-03 07:28:17 -04:00
listen (3.1.5)
Override the github git source instead of changing manually all entries
2016-09-13 20:19:09 -04:00
rb-fsevent (~> 0.9, >= 0.9.4)
rb-inotify (~> 0.9, >= 0.9.7)
Allow the use of listen's 3.1.x branch. When the initial evented monitor feature was written, the latest version of listen was the 3.0.x series. Since then the listen project has moved on to the 3.1.x series. This patch allows the use of the new versions.
2016-10-03 07:28:17 -04:00
ruby_dep (~> 1.2)
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)
bundle mail 2.6.5 that includes fix for ::Fixnum warning
2017-05-19 04:50:25 -04:00
mail (2.6.5)
Prep Rails 5 beta 4
2016-04-27 16:47:22 -04:00
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)
Override the github git source instead of changing manually all entries
2016-09-13 20:19:09 -04:00
mime-types (3.1)
Prep Rails 5 beta 4
2016-04-27 16:47:22 -04:00
mime-types-data (~> 3.2015)
Override the github git source instead of changing manually all entries
2016-09-13 20:19:09 -04:00
mime-types-data (3.2016.0521)
Let's test nokogiri 1.8 against edge Rails, and vice versa
2017-06-06 04:32:49 -04:00
mini_portile2 (2.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
minitest (5.3.3)
Revert "bundle u mocha" This reverts commit 66e5b9d3f47cd52143be0e6a216ade34bb52b9cc. We're seeing some test failures in AR postgresql tests
2017-01-15 10:16:41 -05:00
mocha (0.14.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
metaclass (~> 0.0.1)
mono_logger (1.1.0)
Lock Faye version to avoid bug with its Promise polyfill, use mainline blade-sauce_labs_plugin gem
2016-05-31 10:44:09 -04:00
multi_json (1.12.1)
Add accidentally removed dependency in Gemfile.lock Follow up to ca0b6d0d416776655ed7516ac18f126fbde5315a.
2016-08-03 18:55:47 -04:00
multipart-post (2.0.0)
Upgrade all gems to make sure Rails works with rack 2.0.0.rc1
2016-05-06 17:16:28 -04:00
mustache (1.0.3)
Use mysql2 0.4.6 to suport MySQL 8.0.1 Follow up #28733 and brianmario/mysql2#840
2017-05-04 09:29:22 -04:00
mysql2 (0.4.6)
mysql2 (0.4.6-x64-mingw32)
mysql2 (0.4.6-x86-mingw32)
Upgrade to nio4r 2.0.0 nio4r 2.0.0 primarily includes new features and bugfixes, with few breaking changes. The primary reason for bumping the major version is dropping support for all Ruby versions prior to 2.2.2, so as to match Rails 5. Full release announcement here: https://groups.google.com/forum/#!topic/socketry/ZDIUj1ufiJ8
2016-12-28 22:45:39 -05:00
nio4r (2.0.0)
Let's test nokogiri 1.8 against edge Rails, and vice versa
2017-06-06 04:32:49 -04:00
nokogiri (1.8.0)
mini_portile2 (~> 2.2.0)
nokogiri (1.8.0-x64-mingw32)
mini_portile2 (~> 2.2.0)
nokogiri (1.8.0-x86-mingw32)
mini_portile2 (~> 2.2.0)
Bump rubocop and dependent gem versions
2017-05-24 02:20:00 -04:00
parallel (1.11.2)
Fix rubocop violations
2017-02-09 21:13:41 -05:00
parser (2.4.0.0)
Add rubocop to Gemfile
2016-11-27 22:12:33 -05:00
ast (~> 2.2)
Allow the use of listen's 3.1.x branch. When the initial evented monitor feature was written, the latest version of listen was the 3.0.x series. Since then the listen project has moved on to the 3.1.x series. This patch allows the use of the new versions.
2016-10-03 07:28:17 -04:00
pg (0.19.0)
pg (0.19.0-x64-mingw32)
pg (0.19.0-x86-mingw32)
Add rubocop to Gemfile
2016-11-27 22:12:33 -05:00
powerpack (0.1.1)
bundle update
2016-12-26 07:46:01 -05:00
psych (2.2.2)
Fix all rubocop violations
2017-01-17 22:10:14 -05:00
public_suffix (2.0.5)
bundle update some gems * puma 3.7.0: to let kill("TERM") properly terminate the process in railties test (3.6.2 doesnot on my machine) * amq-protocol 2.1.0: to reduce warnings in AJ tests * rails-html-sanitizer: missing change in a previous commit that updated Gemfile
2017-01-28 15:36:15 -05:00
puma (3.7.0)
Start Rails 5.1 development :tada:
2016-05-10 00:07:09 -04:00
qu (0.2.0)
multi_json
qu-redis (0.2.0)
qu (= 0.2.0)
redis-namespace
simple_uuid
Override the github git source instead of changing manually all entries
2016-09-13 20:19:09 -04:00
que (0.12.0)
Use sprockets 3 in the Rails 5 release
2015-12-16 13:30:58 -05:00
racc (1.4.14)
Bump rack version
2017-05-15 18:25:56 -04:00
rack (2.0.3)
Upgrade all gems to make sure Rails works with rack 2.0.0.rc1
2016-05-06 17:16:28 -04:00
rack-cache (1.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
rack (>= 0.4)
bundle up sidekiq to the one with safer integration with Rails 5 see: https://github.com/mperham/sidekiq/blob/master/5.0-Upgrade.md
2017-05-21 08:34:33 -04:00
rack-protection (2.0.0)
Override the github git source instead of changing manually all entries
2016-09-13 20:19:09 -04:00
rack
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-test (0.6.3)
rack (>= 1.0)
bundle update
2016-12-27 08:28:29 -05:00
rails-dom-testing (2.0.2)
Fix Gemfile.lock by updating rails-dom-testing - Followup of https://github.com/rails/rails/pull/24946.
2016-05-10 01:13:56 -04:00
activesupport (>= 4.2.0, < 6.0)
bundle update
2016-12-27 08:28:29 -05:00
nokogiri (~> 1.6)
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)
Bump rubocop and dependent gem versions
2017-05-24 02:20:00 -04:00
rainbow (2.2.2)
rake
bundle u rake to 12.0.0
2016-12-23 16:00:49 -05:00
rake (12.0.0)
bundle update
2016-12-26 07:46:01 -05:00
rb-fsevent (0.9.8)
Fixes FIXME: rb-inotify 0.99 has been released
2017-06-17 12:59:41 -04:00
rb-inotify (0.9.9)
ffi (~> 1.0)
Ask for a sane version of SDoc This will allow me to push a release, including bug fixes, without having to update Rails everytime.
2017-04-23 03:32:57 -04:00
rdoc (5.1.0)
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)
bundle up redis to the one that does not warn about ::Fixnum deprecation
2017-05-20 23:33:47 -04:00
redis (3.3.3)
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)
Use released resque
2017-02-10 01:31:41 -05:00
resque (1.27.0)
mono_logger (~> 1.0)
multi_json (~> 1.0)
redis-namespace (~> 1.3)
sinatra (>= 0.9.2)
vegas (~> 0.1.2)
Override the github git source instead of changing manually all entries
2016-09-13 20:19:09 -04:00
resque-scheduler (4.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
mono_logger (~> 1.0)
Override the github git source instead of changing manually all entries
2016-09-13 20:19:09 -04:00
redis (~> 3.3)
resque (~> 1.26)
Upgrade all gems to make sure Rails works with rack 2.0.0.rc1
2016-05-06 17:16:28 -04:00
rufus-scheduler (~> 3.2)
Bump RuboCop to 0.49.1
2017-05-29 17:16:56 -04:00
rubocop (0.49.1)
Bump rubocop and dependent gem versions
2017-05-24 02:20:00 -04:00
parallel (~> 1.10)
update rubocop to 0.47
2017-01-16 01:34:30 -05:00
parser (>= 2.3.3.1, < 3.0)
Add rubocop to Gemfile
2016-11-27 22:12:33 -05:00
powerpack (~> 0.1)
rainbow (>= 1.99.1, < 3.0)
ruby-progressbar (~> 1.7)
unicode-display_width (~> 1.0, >= 1.0.1)
ruby-progressbar (1.8.1)
bundle update
2016-12-26 07:46:01 -05:00
ruby_dep (1.5.0)
Add accidentally removed dependency in Gemfile.lock Follow up to ca0b6d0d416776655ed7516ac18f126fbde5315a.
2016-08-03 18:55:47 -04:00
rubyzip (1.2.0)
Fix all rubocop violations
2017-01-17 22:10:14 -05:00
rufus-scheduler (3.3.2)
bundle update
2016-12-26 07:46:01 -05:00
tzinfo
sass (3.4.23)
Override the github git source instead of changing manually all entries
2016-09-13 20:19:09 -04:00
sass-rails (5.0.6)
Use sass-rails in our test suite
2016-06-30 18:39:37 -04:00
railties (>= 4.0.0, < 6)
sass (~> 3.1)
sprockets (>= 2.8, < 4.0)
sprockets-rails (>= 2.0, < 4.0)
tilt (>= 1.1, < 3)
Ask for a sane version of SDoc This will allow me to push a release, including bug fixes, without having to update Rails everytime.
2017-04-23 03:32:57 -04:00
sdoc (1.0.0.rc2)
rdoc (~> 5.0)
Upgrade gems
2016-12-28 00:34:44 -05:00
selenium-webdriver (3.0.5)
Add accidentally removed dependency in Gemfile.lock Follow up to ca0b6d0d416776655ed7516ac18f126fbde5315a.
2016-08-03 18:55:47 -04:00
childprocess (~> 0.5)
rubyzip (~> 1.0)
websocket (~> 1.0)
Fix all rubocop violations
2017-01-17 22:10:14 -05:00
sequel (4.42.1)
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 up sidekiq to the one with safer integration with Rails 5 see: https://github.com/mperham/sidekiq/blob/master/5.0-Upgrade.md
2017-05-21 08:34:33 -04:00
sidekiq (5.0.0)
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)
bundle update
2016-12-26 07:46:01 -05:00
rack-protection (>= 1.5.0)
bundle up sidekiq to the one with safer integration with Rails 5 see: https://github.com/mperham/sidekiq/blob/master/5.0-Upgrade.md
2017-05-21 08:34:33 -04:00
redis (~> 3.3, >= 3.3.3)
Upgrade all gems to make sure Rails works with rack 2.0.0.rc1
2016-05-06 17:16:28 -04:00
sigdump (0.2.4)
Start Rails 5.1 development :tada:
2016-05-10 00:07:09 -04:00
simple_uuid (0.4.0)
point at rack master
2015-08-20 16:43:57 -04:00
sinatra (1.0)
rack (>= 1.0)
bundle update
2016-12-26 07:46:01 -05:00
sneakers (2.4.0)
bunny (~> 2.6)
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)
Bump concurrent-ruby and sprockets Bumped to Ruby 2.4 compatible versions
2016-12-19 21:22:39 -05:00
sprockets (3.7.1)
Use sprockets 3 in the Rails 5 release
2015-12-16 13:30:58 -05:00
concurrent-ruby (~> 1.0)
rack (> 1, < 3)
Restore action_cable.js UMD module support. Fixes #28366
2017-03-11 12:33:11 -05:00
sprockets-export (0.9.1)
Override the github git source instead of changing manually all entries
2016-09-13 20:19:09 -04:00
sprockets-rails (3.2.0)
Use release sprockets-rails
2015-12-17 15:22:58 -05:00
actionpack (>= 4.0)
activesupport (>= 4.0)
sprockets (>= 3.0.0)
bundle u sqlite3 this fixes sqlite3-1.3.12/lib/sqlite3/pragmas.rb:301: warning: method redefined; discarding old integrity_check
2017-01-05 03:38:19 -05:00
sqlite3 (1.3.13)
sqlite3 (1.3.13-x64-mingw32)
sqlite3 (1.3.13-x86-mingw32)
Allow the use of listen's 3.1.x branch. When the initial evented monitor feature was written, the latest version of listen was the 3.0.x series. Since then the listen project has moved on to the 3.1.x series. This patch allows the use of the new versions.
2016-10-03 07:28:17 -04:00
stackprof (0.2.10)
Upgrade all gems to make sure Rails works with rack 2.0.0.rc1
2016-05-06 17:16:28 -04:00
sucker_punch (2.0.2)
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
concurrent-ruby (~> 1.0.0)
Add accidentally removed dependency in Gemfile.lock Follow up to ca0b6d0d416776655ed7516ac18f126fbde5315a.
2016-08-03 18:55:47 -04:00
thin (1.7.0)
daemons (~> 1.0, >= 1.0.9)
eventmachine (~> 1.0, >= 1.0.4)
rack (>= 1, < 3)
Unlock sneakers adapter version
2015-04-26 03:44:18 -04:00
thread (0.1.7)
Bump the bundled GlobalID version.
2017-04-16 11:40:00 -04:00
thread_safe (0.3.6)
Use sass-rails in our test suite
2016-06-30 18:39:37 -04:00
tilt (2.0.5)
Override the github git source instead of changing manually all entries
2016-09-13 20:19:09 -04:00
turbolinks (5.0.1)
Update to Turbolinks 5.0.0 final
2016-06-30 13:18:52 -04:00
turbolinks-source (~> 5)
turbolinks-source (5.0.0)
Bump the bundled GlobalID version.
2017-04-16 11:40:00 -04:00
tzinfo (1.2.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
thread_safe (~> 0.1)
bundle update
2016-12-26 07:46:01 -05:00
tzinfo-data (1.2016.10)
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)
bundle update
2016-12-26 07:46:01 -05:00
uglifier (3.0.4)
Upgrade all gems to make sure Rails works with rack 2.0.0.rc1
2016-05-06 17:16:28 -04:00
execjs (>= 0.3.0, < 3)
Fix all style guides violations Closes #28382 Closes #28651
2017-04-19 20:02:03 -04:00
unicode-display_width (1.2.1)
Override the github git source instead of changing manually all entries
2016-09-13 20:19:09 -04:00
useragent (0.16.8)
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
vegas (0.1.11)
rack (>= 1.0.0)
bundle update
2016-12-26 07:46:01 -05:00
w3c_validators (1.3.1)
json (~> 2.0)
nokogiri (~> 1.6)
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)
Add accidentally removed dependency in Gemfile.lock Follow up to ca0b6d0d416776655ed7516ac18f126fbde5315a.
2016-08-03 18:55:47 -04:00
websocket (1.2.3)
Lock Faye version to avoid bug with its Promise polyfill, use mainline blade-sauce_labs_plugin gem
2016-05-31 10:44:09 -04:00
websocket-driver (0.6.4)
Initial stab at adding Action Cable to rails/master
2015-12-14 10:38:37 -05:00
websocket-extensions (>= 0.1.0)
websocket-extensions (0.1.2)
Bundle capybara 2.14.1 that includes fix for Ruby warnings Ref: https://github.com/teamcapybara/capybara/pull/1868
2017-06-07 22:14:54 -04:00
xpath (2.1.0)
Add tests for system testing * Adds test case test * Adds driver adapter test * Adds tests for capybara seleium driver (testing the settings not actually opening the browser to test capybara w/ selenium because that would so so so slow) * Adds tests for rack test driver * Adds tests for generators
2016-08-27 16:48:24 -04:00
nokogiri (~> 1.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
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)
Start Rails 5.2 development
2017-03-21 19:41:39 -04:00
arel!
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
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
Update Blade and its Sauce Labs plugin for EventMachine 1.2 compatibility
2016-06-04 18:54:34 -04:00
blade
blade-sauce_labs_plugin
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
Allow capybara minor releases Capybara 2.14.0 was released. Loosen the tight constraint in the generated Gemfile, so that Rails applications can take advantage of the new version
2017-05-05 11:23:59 -04:00
capybara (~> 2.13)
Point to released coffee-rails
2016-06-30 13:35:25 -04:00
coffee-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
dalli (>= 2.2.1)
delayed_job and delayed_job_active_record gems with AR5 support are available
2017-01-28 19:05:06 -05:00
delayed_job
delayed_job_active_record
Add tests for the ActionCable adapters
2016-01-24 05:43:40 -05:00
em-hiredis
Change ActionView ERB Handler from Erubis to Erubi Erubi offers the following advantages for Rails: * Works with ruby's --enable-frozen-string-literal option * Has 88% smaller memory footprint * Does no freedom patching (Erubis adds a method to Kernel) * Has simpler internals (1 file, <150 lines of code) * Has an open development model (Erubis doesn't have a public source control repository or bug tracker) * Is not dead (Erubis hasn't been updated since 2011) Erubi is a simplified fork of Erubis that contains just the parts that are generally needed (which includes the parts that Rails uses). The only intentional difference in behavior is that it does not include support for <%=== tags for debug output. That could be added to the ActionView ERB handler if it is desired. The Erubis template handler remains in a deprecated state so that code that accesses it directly does not break. It can be removed after Rails 5.1.
2017-01-20 18:02:34 -05:00
erubis (~> 2.7.0)
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
Make sure to bundle json 2.x on CI Without this, bundler tries to bundle json 1.8 on Ruby 2.4 in some cases https://travis-ci.org/rails/rails/jobs/175874852
2016-11-14 19:26:03 -05:00
json (>= 2.0.0)
Fix rake guides:generate:kindle error
2016-12-18 10:13:50 -05:00
kindlerb (~> 1.2.0)
Install libxml-ruby gem so full XMLMini test suite can be run
2016-11-19 10:46:28 -05:00
libxml-ruby
Allow the use of listen's 3.1.x branch. When the initial evented monitor feature was written, the latest version of listen was the 3.0.x series. Since then the listen project has moved on to the 3.1.x series. This patch allows the use of the new versions.
2016-10-03 07:28:17 -04:00
listen (>= 3.0.5, < 3.2)
Revert "I guess we're ready for the randomized tests now" This reverts commit 8c155c932f37fd2de5b530bc076ed60a03bc926c. Not really :cry:
2017-01-18 06:52:21 -05:00
minitest (< 5.3.4)
Revert "bundle u mocha" This reverts commit 66e5b9d3f47cd52143be0e6a216ade34bb52b9cc. We're seeing some test failures in AR postgresql tests
2017-01-15 10:16:41 -05:00
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.8 per security release today --> https://groups.google.com/forum/#!topic/ruby-security-ann/RCHyF5K9Lbc
2016-06-06 23:10:37 -04:00
nokogiri (>= 1.6.8)
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-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
Use released resque
2017-02-10 01:31:41 -05:00
resque
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
update rubocop to 0.47
2017-01-16 01:34:30 -05:00
rubocop (>= 0.47)
Use sass-rails in our test suite
2016-06-30 18:39:37 -04:00
sass-rails
Ask for a sane version of SDoc This will allow me to push a release, including bug fixes, without having to update Rails everytime.
2017-04-23 03:32:57 -04:00
sdoc (> 1.0.0.rc1, < 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
sequel
sidekiq
Unlock sneakers adapter version
2015-04-26 03:44:18 -04:00
sneakers
Restore action_cable.js UMD module support. Fixes #28366
2017-03-11 12:33:11 -05:00
sprockets-export
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
Test thor master
2017-07-07 15:16:39 -04:00
thor!
Update to Turbolinks 5.0.0 final
2016-06-30 13:18:52 -04:00
turbolinks (~> 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
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)
Use a branch of websocket-client-simple, to work around read/close race
2016-10-05 21:11:18 -04:00
websocket-client-simple!
Generate Bundler 1.10.1 lockfile
2015-05-29 01:40:29 -04:00
BUNDLED WITH
Let's test nokogiri 1.8 against edge Rails, and vice versa
2017-06-06 04:32:49 -04:00
1.15.1
Copy permalink