mirrors
/
rails
mirror of https://github.com/rails/rails
8
0
Fork 0
Code Issues Projects Releases Wiki Activity
rails/Gemfile.lock

579 lines
14 KiB
Plaintext
Raw Normal View History

Make Railties CI log for Ruby 2.6 accessible again Pending the next release of Thor which [fixes](https://github.com/erikhuda/thor/commit/006832ea32480618791f89bb7d9e67b22fc814b9) calls to `ERB.new`, Railties CI log for Ruby 2.6 is flooded with so many warnings it is too long for Travis to handle: ``` /home/travis/.rvm/gems/ruby-head/gems/thor-0.20.0/lib/thor/actions/file_manipulation.rb:120: warning: Passing safe_level with the 2nd argument of ERB.new is deprecated. Do not use it, and specify other arguments as keyword arguments. /home/travis/.rvm/gems/ruby-head/gems/thor-0.20.0/lib/thor/actions/file_manipulation.rb:120: warning: Passing trim_mode with the 3rd argument of ERB.new is deprecated. Use keyword argument like ERB.new(str, trim_mode: ...) instead. /home/travis/.rvm/gems/ruby-head/gems/thor-0.20.0/lib/thor/actions/file_manipulation.rb:120: warning: Passing eoutvar with the 4th argument of ERB.new is deprecated. Use keyword argument like ERB.new(str, eoutvar: ...) instead. The log length has exceeded the limit of 4 MB (this usually means that the test suite is raising the same exception over and over). The job has been terminated ``` https://travis-ci.org/rails/rails/jobs/372623604#L10000 https://api.travis-ci.org/v3/job/372623604/log.txt This patch forces installation of fixed Thor, and enables us to look at the the log.
2018-04-29 17:12:44 +08:00
GIT
remote: https://github.com/erikhuda/thor.git
revision: 006832ea32480618791f89bb7d9e67b22fc814b9
ref: 006832ea32480618791f89bb7d9e67b22fc814b9
specs:
thor (0.20.0)
Move back to @matthewd's close io fixed rb-inotify.
2017-07-20 01:43:12 +08:00
GIT
remote: https://github.com/matthewd/rb-inotify.git
revision: 856730aad4b285969e8dd621e44808a7c5af4242
branch: close-handling
specs:
rb-inotify (0.9.9)
ffi (~> 1.0)
Use a branch of websocket-client-simple, to work around read/close race
2016-10-06 09:11:18 +08: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
Use my fork instead of an thrid-party fork This will avoid the branch being deleted by mistake making all builds to fail.
2018-01-12 03:37:27 +08:00
GIT
remote: https://github.com/rafaelfranca/queue_classic.git
revision: dee64b361355d56700ad7aa3b151bf653a617526
branch: update-pg
specs:
queue_classic (3.2.0.RC1)
pg (>= 0.17, < 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-19 00:30:25 +08:00
PATH
remote: .
specs:
Start Rails 6.0 development!!! :tada::tada::tada:
2018-01-31 07:51:17 +08:00
actioncable (6.0.0.alpha)
actionpack (= 6.0.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-29 11:45:39 +08:00
nio4r (~> 2.0)
Update Gemfile.lock to reflect websocket-driver 0.7.0 Follow up to e1473e0cbfbd97eeea2bc6eefd73bec0d4863359
2018-01-19 06:50:50 +08:00
websocket-driver (>= 0.6.1)
Start Rails 6.0 development!!! :tada::tada::tada:
2018-01-31 07:51:17 +08:00
actionmailer (6.0.0.alpha)
actionpack (= 6.0.0.alpha)
actionview (= 6.0.0.alpha)
activejob (= 6.0.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-19 00:30:25 +08: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 13:13:56 +08:00
rails-dom-testing (~> 2.0)
Start Rails 6.0 development!!! :tada::tada::tada:
2018-01-31 07:51:17 +08:00
actionpack (6.0.0.alpha)
actionview (= 6.0.0.alpha)
activesupport (= 6.0.0.alpha)
Do not allow rack pre releases
2016-07-01 02:10:22 +08:00
rack (~> 2.0)
Update rack-test dependency constraint
2017-07-20 07:04:53 +08: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 13:13:56 +08: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-08 01:48:06 +08:00
rails-html-sanitizer (~> 1.0, >= 1.0.2)
Start Rails 6.0 development!!! :tada::tada::tada:
2018-01-31 07:51:17 +08:00
actionview (6.0.0.alpha)
activesupport (= 6.0.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-19 00:30:25 +08: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-21 07:02:34 +08:00
erubi (~> 1.4)
Fix Gemfile.lock by updating rails-dom-testing - Followup of https://github.com/rails/rails/pull/24946.
2016-05-10 13:13:56 +08: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-29 04:36:15 +08:00
rails-html-sanitizer (~> 1.0, >= 1.0.3)
Start Rails 6.0 development!!! :tada::tada::tada:
2018-01-31 07:51:17 +08:00
activejob (6.0.0.alpha)
activesupport (= 6.0.0.alpha)
Use released GlobalID now that it provides URI::GID::MissingModelIdError for Active Job
2015-12-18 08:20:19 +08:00
globalid (>= 0.3.6)
Start Rails 6.0 development!!! :tada::tada::tada:
2018-01-31 07:51:17 +08:00
activemodel (6.0.0.alpha)
activesupport (= 6.0.0.alpha)
activerecord (6.0.0.alpha)
activemodel (= 6.0.0.alpha)
activesupport (= 6.0.0.alpha)
activestorage (6.0.0.alpha)
actionpack (= 6.0.0.alpha)
activerecord (= 6.0.0.alpha)
Extract content types from blob data
2018-01-16 02:06:17 +08:00
marcel (~> 0.3.1)
Start Rails 6.0 development!!! :tada::tada::tada:
2018-01-31 07:51:17 +08:00
activesupport (6.0.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-03 06:04:59 +08:00
concurrent-ruby (~> 1.0, >= 1.0.2)
Don't force people to upgrade i18n gem
2018-02-15 00:55:36 +08:00
i18n (>= 0.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-19 00:30:25 +08:00
minitest (~> 5.1)
tzinfo (~> 1.1)
Start Rails 6.0 development!!! :tada::tada::tada:
2018-01-31 07:51:17 +08:00
rails (6.0.0.alpha)
actioncable (= 6.0.0.alpha)
actionmailer (= 6.0.0.alpha)
actionpack (= 6.0.0.alpha)
actionview (= 6.0.0.alpha)
activejob (= 6.0.0.alpha)
activemodel (= 6.0.0.alpha)
activerecord (= 6.0.0.alpha)
activestorage (= 6.0.0.alpha)
activesupport (= 6.0.0.alpha)
Commit gemfile.lock
2017-07-05 02:54:26 +08:00
bundler (>= 1.3.0)
Start Rails 6.0 development!!! :tada::tada::tada:
2018-01-31 07:51:17 +08:00
railties (= 6.0.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-02 00:29:16 +08:00
sprockets-rails (>= 2.0.0)
Start Rails 6.0 development!!! :tada::tada::tada:
2018-01-31 07:51:17 +08:00
railties (6.0.0.alpha)
actionpack (= 6.0.0.alpha)
activesupport (= 6.0.0.alpha)
method_source needs to be a hard dependency on railties
2015-03-05 22:58:17 +08: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-19 00:30:25 +08:00
rake (>= 0.8.7)
Bump minimum version of Thor to 0.19.0 Thor 0.18 is causing failures in all the generator tests.
2018-05-23 04:56:29 +08:00
thor (>= 0.19.0, < 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-19 00:30:25 +08:00
GEM
remote: https://rubygems.org/
specs:
Bundle update
2018-05-31 01:49:55 +08:00
activerecord-jdbc-adapter (51.1-java)
activerecord (~> 5.1.0)
activerecord-jdbcmysql-adapter (51.1-java)
activerecord-jdbc-adapter (= 51.1)
jdbc-mysql (~> 5.1.36)
activerecord-jdbcpostgresql-adapter (51.1-java)
activerecord-jdbc-adapter (= 51.1)
jdbc-postgres (>= 9.4, < 43)
activerecord-jdbcsqlite3-adapter (51.1-java)
activerecord-jdbc-adapter (= 51.1)
jdbc-sqlite3 (~> 3.8, < 3.30)
Use `credentials` instead of `keyfile` in GCS sevice The `keyfile` was renamed to `credentials` in `google-cloud-storage` 1.8.0. https://github.com/GoogleCloudPlatform/google-cloud-ruby/blob/master/google-cloud-storage/CHANGELOG.md#180--2017-11-14 Although `keyfile` can still be used, but it looks like deprecate. https://github.com/GoogleCloudPlatform/google-cloud-ruby/blob/ddf7b2a856d676316525eb581c1a4cc83ca6097b/google-cloud-storage/lib/google/cloud/storage.rb#L589...L590 Therefore, I think that should use `credentials` in newly generated applications. Ref: https://github.com/GoogleCloudPlatform/google-cloud-ruby/issues/1802
2017-11-29 12:08:33 +08:00
addressable (2.5.2)
public_suffix (>= 2.0.2, < 4.0)
Bundle update
2018-05-31 01:49:55 +08:00
amq-protocol (2.3.0)
archive-zip (0.11.0)
PhantomJS is abandoned, replace it with Selenium/Chrome headless
2017-10-20 00:01:52 +08:00
io-like (~> 0.3.0)
Update rubocop to the latest version Includes [Switch Layout/SpaceBeforeBlockBraces's empty braces default](https://github.com/bbatsov/rubocop/pull/5263) from [0.52.1](https://github.com/bbatsov/rubocop/blob/master/CHANGELOG.md#0521-2017-12-27). Before: 131 offenses detected. After: no offenses detected
2018-02-23 07:54:23 +08:00
ast (2.4.0)
Bundle update
2018-05-31 01:49:55 +08:00
aws-eventstream (1.0.0)
aws-partitions (1.88.0)
aws-sdk-core (3.21.2)
aws-eventstream (~> 1.0)
Use v3 of the AWS SDK
2017-09-10 11:22:10 +08:00
aws-partitions (~> 1.0)
Resolve gemspec typo
2017-08-01 04:55:55 +08:00
aws-sigv4 (~> 1.0)
jmespath (~> 1.0)
Bundle update
2018-05-31 01:49:55 +08:00
aws-sdk-kms (1.5.0)
Use v3 of the AWS SDK
2017-09-10 11:22:10 +08:00
aws-sdk-core (~> 3)
aws-sigv4 (~> 1.0)
Bundle update
2018-05-31 01:49:55 +08:00
aws-sdk-s3 (1.13.0)
aws-sdk-core (~> 3, >= 3.21.2)
Use v3 of the AWS SDK
2017-09-10 11:22:10 +08:00
aws-sdk-kms (~> 1)
aws-sigv4 (~> 1.0)
Bundle update
2018-05-31 01:49:55 +08:00
aws-sigv4 (1.0.2)
azure-core (0.1.14)
Depend on offical azure-core No need to depend on my fork anymore, they've just release fix officially.
2017-08-02 15:38:03 +08:00
faraday (~> 0.9)
faraday_middleware (~> 0.10)
Update azure-core to 0.1.11 to fix rails-dev-box rails-dev-box was failing to install gems with a filesystem permission error. The issue was introduced when azure-core was bumped from 0.1.9 to 0.1.10 in d2f493c. azure-core has fixed the build problem [1] and released a new version, 0.1.11 with the fix. This change is just to run `bundle update azure-core` to pick up that fix. [1]: https://github.com/Azure/azure-ruby-asm-core/commit/536c3fc21cc48c292959cc10a9e5551e165aa0ed
2017-08-24 12:53:02 +08:00
nokogiri (~> 1.6)
Bundle update
2018-05-31 01:49:55 +08:00
azure-storage (0.15.0.preview)
Resolve gemspec typo
2017-08-01 04:55:55 +08:00
azure-core (~> 0.1)
faraday (~> 0.9)
faraday_middleware (~> 0.10)
Bundle update
2018-05-31 01:49:55 +08:00
nokogiri (~> 1.6, >= 1.6.8)
Update rack-test dependency constraint
2017-07-20 07:04:53 +08:00
backburner (1.4.1)
Update Gemfile.lock
2015-08-10 11:30:03 +08: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 19:28:17 +08:00
concurrent-ruby (~> 1.0.1)
Update Gemfile.lock
2015-08-10 11:30:03 +08:00
dante (> 0.1.5)
Bundle update
2018-05-31 01:49:55 +08:00
bcrypt (3.1.12)
bcrypt (3.1.12-java)
bcrypt (3.1.12-x64-mingw32)
bcrypt (3.1.12-x86-mingw32)
Update Gemfile.lock
2015-08-10 11:30:03 +08:00
beaneater (1.0.0)
Override the github git source instead of changing manually all entries
2016-09-14 08:19:09 +08:00
benchmark-ips (2.7.2)
Bump `thor` and `blade` For test with latest thor.
2017-08-17 07:53:36 +08:00
blade (0.7.1)
Add accidentally removed dependency in Gemfile.lock Follow up to ca0b6d0d416776655ed7516ac18f126fbde5315a.
2016-08-04 06:55:47 +08: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-21 06:08:31 +08:00
blade-qunit_adapter (~> 2.0.1)
Add accidentally removed dependency in Gemfile.lock Follow up to ca0b6d0d416776655ed7516ac18f126fbde5315a.
2016-08-04 06:55:47 +08:00
coffee-script
coffee-script-source
curses (~> 1.0.0)
eventmachine
faye
sprockets (>= 3.0)
thin (>= 1.6.0)
Bump `thor` and `blade` For test with latest thor.
2017-08-17 07:53:36 +08:00
thor (>= 0.19.1)
Add accidentally removed dependency in Gemfile.lock Follow up to ca0b6d0d416776655ed7516ac18f126fbde5315a.
2016-08-04 06:55:47 +08:00
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-21 06:08:31 +08:00
blade-qunit_adapter (2.0.1)
Bundle update
2018-05-31 01:49:55 +08:00
blade-sauce_labs_plugin (0.7.3)
Add accidentally removed dependency in Gemfile.lock Follow up to ca0b6d0d416776655ed7516ac18f126fbde5315a.
2016-08-04 06:55:47 +08:00
childprocess
faraday
selenium-webdriver
Bundle update
2018-05-31 01:49:55 +08:00
bootsnap (1.3.0)
bundle lock --add-platform java "The dependency activerecord-jdbcsqlite3-adapter (>= 1.3.0) will be unused by any of the platforms Bundler is installing for. Bundler is installing for ruby, x64-mingw32, x86-mingw32 but the dependency is only for java. To add those platforms to the bundle, run `bundle lock --add-platform java`."
2017-10-20 19:34:43 +08:00
msgpack (~> 1.0)
Bundle update
2018-05-31 01:49:55 +08:00
bootsnap (1.3.0-java)
Upgrade capybara to 3.0.1 to make sure our tests are passing
2018-04-07 05:09:14 +08:00
msgpack (~> 1.0)
Update builder gem to avoid deprecations of 2.4
2017-01-14 02:50:25 +08:00
builder (3.2.3)
Bundle update
2018-05-31 01:49:55 +08:00
bunny (2.9.2)
amq-protocol (~> 2.3.0)
byebug (10.0.2)
capybara (3.1.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-28 04:48:24 +08:00
addressable
Test with released thor thor 0.20.0 was released so we can test with the released version.
2017-08-17 02:03:24 +08:00
mini_mime (>= 0.1.3)
Fix broken `ServerTest` with Capybara 3.0.0 It seems that it is no longer possible to specify the value held by `Capybara.server` as sever. Ref: https://github.com/teamcapybara/capybara/commit/ba7674086cbcd3b22d3614011815bc5d483e5960
2018-04-06 19:55:34 +08:00
nokogiri (~> 1.8)
rack (>= 1.6.0)
rack-test (>= 0.6.3)
xpath (~> 3.0)
Bundle update
2018-05-31 01:49:55 +08:00
childprocess (0.9.0)
Add accidentally removed dependency in Gemfile.lock Follow up to ca0b6d0d416776655ed7516ac18f126fbde5315a.
2016-08-04 06:55:47 +08:00
ffi (~> 1.0, >= 1.0.11)
Bundle update
2018-05-31 01:49:55 +08:00
chromedriver-helper (1.2.0)
archive-zip (~> 0.10)
nokogiri (~> 1.8)
Update rack-test dependency constraint
2017-07-20 07:04:53 +08:00
coffee-rails (4.2.2)
Point to released coffee-rails
2016-07-01 01:35:25 +08:00
coffee-script (>= 2.2.0)
Update rack-test dependency constraint
2017-07-20 07:04:53 +08:00
railties (>= 4.0.0)
Update Gemfile.lock
2015-08-10 11:30:03 +08: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-19 00:30:25 +08: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 23:43:44 +08:00
coffee-script-source (1.12.2)
Bump the bundled GlobalID version.
2017-04-16 23:40:00 +08:00
concurrent-ruby (1.0.5)
bundle lock --add-platform java "The dependency activerecord-jdbcsqlite3-adapter (>= 1.3.0) will be unused by any of the platforms Bundler is installing for. Bundler is installing for ruby, x64-mingw32, x86-mingw32 but the dependency is only for java. To add those platforms to the bundle, run `bundle lock --add-platform java`."
2017-10-20 19:34:43 +08:00
concurrent-ruby (1.0.5-java)
Bundle update
2018-05-31 01:49:55 +08:00
connection_pool (2.2.2)
Override the github git source instead of changing manually all entries
2016-09-14 08:19:09 +08:00
cookiejar (0.3.3)
Bundle update
2018-05-31 01:49:55 +08:00
crass (1.0.4)
Add accidentally removed dependency in Gemfile.lock Follow up to ca0b6d0d416776655ed7516ac18f126fbde5315a.
2016-08-04 06:55:47 +08:00
curses (1.0.2)
Bundle update
2018-05-31 01:49:55 +08:00
daemons (1.2.6)
Unlock dalli version The issue was fixed with https://github.com/petergoldstein/dalli/pull/679, and a new version containing that fix was released.
2018-04-11 15:52:10 +08:00
dalli (2.7.8)
Update Gemfile.lock
2015-08-10 11:30:03 +08:00
dante (0.2.0)
Use `credentials` instead of `keyfile` in GCS sevice The `keyfile` was renamed to `credentials` in `google-cloud-storage` 1.8.0. https://github.com/GoogleCloudPlatform/google-cloud-ruby/blob/master/google-cloud-storage/CHANGELOG.md#180--2017-11-14 Although `keyfile` can still be used, but it looks like deprecate. https://github.com/GoogleCloudPlatform/google-cloud-ruby/blob/ddf7b2a856d676316525eb581c1a4cc83ca6097b/google-cloud-storage/lib/google/cloud/storage.rb#L589...L590 Therefore, I think that should use `credentials` in newly generated applications. Ref: https://github.com/GoogleCloudPlatform/google-cloud-ruby/issues/1802
2017-11-29 12:08:33 +08:00
declarative (0.0.10)
Resolve gemspec typo
2017-08-01 04:55:55 +08:00
declarative-option (0.1.0)
Bundle update
2018-05-31 01:49:55 +08:00
delayed_job (4.1.5)
activesupport (>= 3.0, < 5.3)
delayed_job_active_record (4.1.3)
activerecord (>= 3.0, < 5.3)
delayed_job and delayed_job_active_record gems with AR5 support are available
2017-01-29 08:05:06 +08:00
delayed_job (>= 3.0, < 5)
Resolve gemspec typo
2017-08-01 04:55:55 +08:00
digest-crc (0.4.1)
Override the github git source instead of changing manually all entries
2016-09-14 08:19:09 +08: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-22 02:15:58 +08:00
addressable (>= 2.3.4)
Override the github git source instead of changing manually all entries
2016-09-14 08:19:09 +08: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-22 02:15:58 +08:00
em-socksify (>= 0.3)
eventmachine (>= 1.0.3)
http_parser.rb (>= 0.6.0)
Update em-socksify to the latest version Avoid warning: parentheses after method name is interpreted as an argument list, not a decomposed argument
2018-02-07 06:08:13 +08:00
em-socksify (0.3.2)
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-22 02:15:58 +08:00
eventmachine (>= 1.0.0.beta.4)
Bundle update
2018-05-31 01:49:55 +08:00
erubi (1.7.1)
Update et-orbi to latest version avoids `warning: assigned but unused variable - tu`.
2018-05-28 14:36:49 +08:00
et-orbi (1.1.2)
Update rack-test dependency constraint
2017-07-20 07:04:53 +08:00
tzinfo
Suppress deprecated warning in Action Cable
2017-07-25 14:53:02 +08:00
event_emitter (0.2.6)
Bundle update
2018-05-31 01:49:55 +08:00
eventmachine (1.2.7)
Update Blade and its Sauce Labs plugin for EventMachine 1.2 compatibility
2016-06-05 06:54:34 +08:00
execjs (2.7.0)
Bundle update
2018-05-31 01:49:55 +08:00
faraday (0.15.2)
Add accidentally removed dependency in Gemfile.lock Follow up to ca0b6d0d416776655ed7516ac18f126fbde5315a.
2016-08-04 06:55:47 +08:00
multipart-post (>= 1.2, < 3)
Test with released thor thor 0.20.0 was released so we can test with the released version.
2017-08-17 02:03:24 +08:00
faraday_middleware (0.12.2)
Resolve gemspec typo
2017-08-01 04:55:55 +08:00
faraday (>= 0.7.4, < 1.0)
Update rack-test dependency constraint
2017-07-20 07:04:53 +08:00
faye (1.2.4)
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-22 02:15:58 +08: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)
Update rack-test dependency constraint
2017-07-20 07:04:53 +08:00
faye-websocket (0.10.7)
Add a couple of tests that connect with a WS client
2016-01-25 01:25:53 +08:00
eventmachine (>= 0.12.0)
websocket-driver (>= 0.5.1)
Fix segmentation fault in EventedFileUpdateChecker resolves #32705
2018-04-25 02:54:52 +08:00
ffi (1.9.21)
ffi (1.9.21-java)
ffi (1.9.21-x64-mingw32)
ffi (1.9.21-x86-mingw32)
Update fugit to latest version [fugit 1.1.3](https://github.com/floraison/fugit/commit/03a3ee86f3cd5d929442dd25896b99acbd151947) fixes warnings that show up in ActiveJob tests. See [CI](https://travis-ci.org/rails/rails/jobs/394107740#L3764-L3778).
2018-06-21 18:05:42 +08:00
fugit (1.1.3)
Bundle update
2018-05-31 01:49:55 +08:00
et-orbi (~> 1.1, >= 1.1.1)
raabro (~> 1.1)
Preparing for 5.2.0.beta1 release
2017-11-28 02:01:15 +08:00
globalid (0.4.1)
Bump the bundled GlobalID version.
2017-04-16 23:40:00 +08:00
activesupport (>= 4.2.0)
Support streaming downloads from Google Cloud Storage
2018-05-02 11:20:56 +08:00
google-api-client (0.19.8)
Resolve gemspec typo
2017-08-01 04:55:55 +08:00
addressable (~> 2.5, >= 2.5.1)
Use `credentials` instead of `keyfile` in GCS sevice The `keyfile` was renamed to `credentials` in `google-cloud-storage` 1.8.0. https://github.com/GoogleCloudPlatform/google-cloud-ruby/blob/master/google-cloud-storage/CHANGELOG.md#180--2017-11-14 Although `keyfile` can still be used, but it looks like deprecate. https://github.com/GoogleCloudPlatform/google-cloud-ruby/blob/ddf7b2a856d676316525eb581c1a4cc83ca6097b/google-cloud-storage/lib/google/cloud/storage.rb#L589...L590 Therefore, I think that should use `credentials` in newly generated applications. Ref: https://github.com/GoogleCloudPlatform/google-cloud-ruby/issues/1802
2017-11-29 12:08:33 +08:00
googleauth (>= 0.5, < 0.7.0)
Resolve gemspec typo
2017-08-01 04:55:55 +08:00
httpclient (>= 2.8.1, < 3.0)
mime-types (~> 3.0)
representable (~> 3.0)
retriable (>= 2.0, < 4.0)
Support streaming downloads from Google Cloud Storage
2018-05-02 11:20:56 +08:00
google-cloud-core (1.2.0)
Resolve gemspec typo
2017-08-01 04:55:55 +08:00
google-cloud-env (~> 1.0)
google-cloud-env (1.0.1)
faraday (~> 0.11)
Bundle update
2018-05-31 01:49:55 +08:00
google-cloud-storage (1.12.0)
Resolve gemspec typo
2017-08-01 04:55:55 +08:00
digest-crc (~> 0.4)
Support streaming downloads from Google Cloud Storage
2018-05-02 11:20:56 +08:00
google-api-client (~> 0.19.0)
google-cloud-core (~> 1.2)
Use `credentials` instead of `keyfile` in GCS sevice The `keyfile` was renamed to `credentials` in `google-cloud-storage` 1.8.0. https://github.com/GoogleCloudPlatform/google-cloud-ruby/blob/master/google-cloud-storage/CHANGELOG.md#180--2017-11-14 Although `keyfile` can still be used, but it looks like deprecate. https://github.com/GoogleCloudPlatform/google-cloud-ruby/blob/ddf7b2a856d676316525eb581c1a4cc83ca6097b/google-cloud-storage/lib/google/cloud/storage.rb#L589...L590 Therefore, I think that should use `credentials` in newly generated applications. Ref: https://github.com/GoogleCloudPlatform/google-cloud-ruby/issues/1802
2017-11-29 12:08:33 +08:00
googleauth (~> 0.6.2)
googleauth (0.6.2)
Resolve gemspec typo
2017-08-01 04:55:55 +08:00
faraday (~> 0.12)
Use `credentials` instead of `keyfile` in GCS sevice The `keyfile` was renamed to `credentials` in `google-cloud-storage` 1.8.0. https://github.com/GoogleCloudPlatform/google-cloud-ruby/blob/master/google-cloud-storage/CHANGELOG.md#180--2017-11-14 Although `keyfile` can still be used, but it looks like deprecate. https://github.com/GoogleCloudPlatform/google-cloud-ruby/blob/ddf7b2a856d676316525eb581c1a4cc83ca6097b/google-cloud-storage/lib/google/cloud/storage.rb#L589...L590 Therefore, I think that should use `credentials` in newly generated applications. Ref: https://github.com/GoogleCloudPlatform/google-cloud-ruby/issues/1802
2017-11-29 12:08:33 +08:00
jwt (>= 1.4, < 3.0)
Resolve gemspec typo
2017-08-01 04:55:55 +08:00
logging (~> 2.0)
memoist (~> 0.12)
multi_json (~> 1.11)
os (~> 0.9)
signet (~> 0.7)
Bundle update to fix tests locally
2016-01-29 03:57:08 +08:00
hiredis (0.6.1)
bundle lock --add-platform java "The dependency activerecord-jdbcsqlite3-adapter (>= 1.3.0) will be unused by any of the platforms Bundler is installing for. Bundler is installing for ruby, x64-mingw32, x86-mingw32 but the dependency is only for java. To add those platforms to the bundle, run `bundle lock --add-platform java`."
2017-10-20 19:34:43 +08:00
hiredis (0.6.1-java)
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-22 02:15:58 +08:00
http_parser.rb (0.6.0)
Resolve gemspec typo
2017-08-01 04:55:55 +08:00
httpclient (2.8.3)
Bundle update
2018-05-31 01:49:55 +08:00
i18n (1.0.1)
Preparing for 5.2.0.beta1 release
2017-11-28 02:01:15 +08:00
concurrent-ruby (~> 1.0)
Use ImageProcessing gem for ActiveStorage variants ImageProcessing gem is a wrapper around MiniMagick and ruby-vips, and implements an interface for common image resizing and processing. This is the canonical image processing gem recommended in [Shrine], and that's where it developed from. The initial implementation was extracted from Refile, which also implements on-the-fly transformations. Some features that ImageProcessing gem adds on top of MiniMagick: * resizing macros - #resize_to_limit - #resize_to_fit - #resize_to_fill - #resize_and_pad * automatic orientation * automatic thumbnail sharpening * avoids the complex and inefficient MiniMagick::Image class * will use "magick" instead of "convert" on ImageMagick 7 However, the biggest feature of the ImageProcessing gem is that it has an alternative implementation that uses libvips. Libvips is an alternative to ImageMagick that can process images very rapidly (we've seen up 10x faster than ImageMagick). What's great is that the ImageProcessing gem provides the same interface for both implementations. The macros are named the same, and the libvips implementation does auto orientation and thumbnail sharpening as well; only the operations/options specific to ImageMagick/libvips differ. The integration provided by this PR should work for both implementations. The plan is to introduce the ImageProcessing backend in Rails 6.0 as the default backend and deprecate the MiniMagick backend, then in Rails 6.1 remove the MiniMagick backend.
2018-04-06 07:48:29 +08:00
image_processing (1.2.0)
mini_magick (~> 4.0)
ruby-vips (>= 2.0.10, < 3)
PhantomJS is abandoned, replace it with Selenium/Chrome headless
2017-10-20 00:01:52 +08:00
io-like (0.3.0)
Bundle update
2018-05-31 01:49:55 +08:00
jdbc-mysql (5.1.46)
jdbc-postgres (42.1.4)
jdbc-sqlite3 (3.20.1)
jmespath (1.4.0)
Update rack-test dependency constraint
2017-07-20 07:04:53 +08:00
json (2.1.0)
bundle lock --add-platform java "The dependency activerecord-jdbcsqlite3-adapter (>= 1.3.0) will be unused by any of the platforms Bundler is installing for. Bundler is installing for ruby, x64-mingw32, x86-mingw32 but the dependency is only for java. To add those platforms to the bundle, run `bundle lock --add-platform java`."
2017-10-20 19:34:43 +08:00
json (2.1.0-java)
Use `credentials` instead of `keyfile` in GCS sevice The `keyfile` was renamed to `credentials` in `google-cloud-storage` 1.8.0. https://github.com/GoogleCloudPlatform/google-cloud-ruby/blob/master/google-cloud-storage/CHANGELOG.md#180--2017-11-14 Although `keyfile` can still be used, but it looks like deprecate. https://github.com/GoogleCloudPlatform/google-cloud-ruby/blob/ddf7b2a856d676316525eb581c1a4cc83ca6097b/google-cloud-storage/lib/google/cloud/storage.rb#L589...L590 Therefore, I think that should use `credentials` in newly generated applications. Ref: https://github.com/GoogleCloudPlatform/google-cloud-ruby/issues/1802
2017-11-29 12:08:33 +08:00
jwt (2.1.0)
Fix rake guides:generate:kindle error
2016-12-18 23:13:50 +08: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-19 00:30:25 +08:00
mustache
nokogiri
Bundle update
2018-05-31 01:49:55 +08:00
libxml-ruby (3.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 19:28:17 +08:00
listen (3.1.5)
Override the github git source instead of changing manually all entries
2016-09-14 08:19:09 +08: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 19:28:17 +08:00
ruby_dep (~> 1.2)
Resolve gemspec typo
2017-08-01 04:55:55 +08:00
little-plugger (1.1.4)
logging (2.2.2)
little-plugger (~> 1.1)
multi_json (~> 1.10)
Bundle update
2018-05-31 01:49:55 +08:00
loofah (2.2.2)
Preparing for 5.2.0.beta1 release
2017-11-28 02:01:15 +08:00
crass (~> 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-19 00:30:25 +08:00
nokogiri (>= 1.5.9)
Fix tests on Mail 2.7 Reverts 4d96be1c27bd6faed957b197a461f18543acebf2 References #31026
2017-11-01 12:44:55 +08:00
mail (2.7.0)
mini_mime (>= 0.1.1)
Bundle update
2018-05-31 01:49:55 +08:00
marcel (0.3.2)
Extract content types from blob data
2018-01-16 02:06:17 +08:00
mimemagic (~> 0.3.2)
Resolve gemspec typo
2017-08-01 04:55:55 +08:00
memoist (0.16.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-19 00:30:25 +08:00
metaclass (0.0.4)
Preparing for 5.2.0.beta1 release
2017-11-28 02:01:15 +08:00
method_source (0.9.0)
Override the github git source instead of changing manually all entries
2016-09-14 08:19:09 +08:00
mime-types (3.1)
Prep Rails 5 beta 4
2016-04-28 04:47:22 +08:00
mime-types-data (~> 3.2015)
Override the github git source instead of changing manually all entries
2016-09-14 08:19:09 +08:00
mime-types-data (3.2016.0521)
Extract content types from blob data
2018-01-16 02:06:17 +08:00
mimemagic (0.3.2)
Resolve gemspec typo
2017-08-01 04:55:55 +08:00
mini_magick (4.8.0)
Fix broken `ServerTest` with Capybara 3.0.0 It seems that it is no longer possible to specify the value held by `Capybara.server` as sever. Ref: https://github.com/teamcapybara/capybara/commit/ba7674086cbcd3b22d3614011815bc5d483e5960
2018-04-06 19:55:34 +08:00
mini_mime (1.0.0)
Update nokogiri version on Gemfile
2017-12-15 02:06:53 +08:00
mini_portile2 (2.3.0)
Bump `minitest-server` In order to use `minitest_bisect` with Minitest 5.11.x, it needs to be updated. Ref: https://github.com/seattlerb/minitest-server/issues/2
2018-02-07 20:47:48 +08:00
minitest (5.11.3)
Add minitest-bisect as part of the gemfile
2016-07-12 14:06:25 +08:00
minitest-bisect (1.4.0)
minitest-server (~> 1.0)
path_expander (~> 1.0)
Bump `minitest-server` In order to use `minitest_bisect` with Minitest 5.11.x, it needs to be updated. Ref: https://github.com/seattlerb/minitest-server/issues/2
2018-02-07 20:47:48 +08:00
minitest-server (1.0.5)
Add minitest-bisect as part of the gemfile
2016-07-12 14:06:25 +08:00
minitest (~> 5.0)
Upgrade Mocha from v1.3.0 to v1.5.0 Mocha v1.5.0 is currently the latest release.
2018-04-07 19:26:27 +08:00
mocha (1.5.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-19 00:30:25 +08:00
metaclass (~> 0.0.1)
mono_logger (1.1.0)
Run `bundle update` on bootsnap 1.2.1 fixes a bug in `Kernel.require` and resolve a test failure. See https://github.com/Shopify/bootsnap/pull/143
2018-03-23 09:09:24 +08:00
msgpack (1.2.4)
msgpack (1.2.4-java)
msgpack (1.2.4-x64-mingw32)
msgpack (1.2.4-x86-mingw32)
Bundle update
2018-05-31 01:49:55 +08:00
multi_json (1.13.1)
Add accidentally removed dependency in Gemfile.lock Follow up to ca0b6d0d416776655ed7516ac18f126fbde5315a.
2016-08-04 06:55:47 +08:00
multipart-post (2.0.0)
Update rack-test dependency constraint
2017-07-20 07:04:53 +08:00
mustache (1.0.5)
Update to sinatra 2.0.1 Although not a direct dependency, it's pulled in by Resque for Active Job integration tests so we need to update because the rack-protection gem has a security vulnerability[1]. [1]: https://nvd.nist.gov/vuln/detail/CVE-2018-7212
2018-02-21 21:04:36 +08:00
mustermann (1.0.2)
Bundle update
2018-05-31 01:49:55 +08:00
mysql2 (0.5.1)
mysql2 (0.5.1-x64-mingw32)
mysql2 (0.5.1-x86-mingw32)
nio4r (2.3.1)
nio4r (2.3.1-java)
Update loofah to mitigate CVE-2018-8048 See flavorjones/loofah#144
2018-03-22 00:48:47 +08:00
nokogiri (1.8.2)
Update nokogiri version on Gemfile
2017-12-15 02:06:53 +08:00
mini_portile2 (~> 2.3.0)
Update loofah to mitigate CVE-2018-8048 See flavorjones/loofah#144
2018-03-22 00:48:47 +08:00
nokogiri (1.8.2-java)
nokogiri (1.8.2-x64-mingw32)
Update nokogiri version on Gemfile
2017-12-15 02:06:53 +08:00
mini_portile2 (~> 2.3.0)
Update loofah to mitigate CVE-2018-8048 See flavorjones/loofah#144
2018-03-22 00:48:47 +08:00
nokogiri (1.8.2-x86-mingw32)
Update nokogiri version on Gemfile
2017-12-15 02:06:53 +08:00
mini_portile2 (~> 2.3.0)
Resolve gemspec typo
2017-08-01 04:55:55 +08:00
os (0.9.6)
Update rubocop to the latest version Includes [Switch Layout/SpaceBeforeBlockBraces's empty braces default](https://github.com/bbatsov/rubocop/pull/5263) from [0.52.1](https://github.com/bbatsov/rubocop/blob/master/CHANGELOG.md#0521-2017-12-27). Before: 131 offenses detected. After: no offenses detected
2018-02-23 07:54:23 +08:00
parallel (1.12.1)
Rubocop 0.54 Fix `.rubocop.yml: Lint/EndAlignment has the wrong namespace - should be Layout` warning
2018-04-22 01:13:34 +08:00
parser (2.5.1.0)
Update rubocop to the latest version Includes [Switch Layout/SpaceBeforeBlockBraces's empty braces default](https://github.com/bbatsov/rubocop/pull/5263) from [0.52.1](https://github.com/bbatsov/rubocop/blob/master/CHANGELOG.md#0521-2017-12-27). Before: 131 offenses detected. After: no offenses detected
2018-02-23 07:54:23 +08:00
ast (~> 2.4.0)
Bundle update
2018-05-31 01:49:55 +08:00
path_expander (1.0.3)
PostgreSQL: Update Gemfile to pg-1.0.0 Queue_classic currently limits pg to "< 0.20". It is therefore not used for rails CI tests. There has been a bull request for a while (by a co-worker of mine), which fixes the incompatibilities and extends dependencies to pg-1.x. This patch add this pull request to the Gemfile as an interim solution, until it is merged.
2018-01-11 04:02:27 +08:00
pg (1.0.0)
pg (1.0.0-x64-mingw32)
pg (1.0.0-x86-mingw32)
Add rubocop to Gemfile
2016-11-28 11:12:33 +08:00
powerpack (0.1.1)
update psych gem to 3.2 stable release
2018-03-10 04:14:36 +08:00
psych (3.0.2)
Fix broken `ServerTest` with Capybara 3.0.0 It seems that it is no longer possible to specify the value held by `Capybara.server` as sever. Ref: https://github.com/teamcapybara/capybara/commit/ba7674086cbcd3b22d3614011815bc5d483e5960
2018-04-06 19:55:34 +08:00
public_suffix (3.0.2)
Bundle update
2018-05-31 01:49:55 +08:00
puma (3.11.4)
puma (3.11.4-java)
que (0.14.3)
PhantomJS is abandoned, replace it with Selenium/Chrome headless
2017-10-20 00:01:52 +08:00
qunit-selenium (0.0.4)
selenium-webdriver
thor
Update raabro to latest version [v 1.1.6](https://github.com/floraison/raabro/blob/master/CHANGELOG.md#raabro-116--released-2018-06-22) fixes a warning we see on [Rails CI](https://travis-ci.org/rails/rails/jobs/395177524#L3763).
2018-06-24 05:23:54 +08:00
raabro (1.1.6)
Use sprockets 3 in the Rails 5 release
2015-12-17 02:30:58 +08:00
racc (1.4.14)
Bundle update
2018-05-31 01:49:55 +08:00
rack (2.0.5)
rack-cache (1.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-19 00:30:25 +08:00
rack (>= 0.4)
Update to sinatra 2.0.1 Although not a direct dependency, it's pulled in by Resque for Active Job integration tests so we need to update because the rack-protection gem has a security vulnerability[1]. [1]: https://nvd.nist.gov/vuln/detail/CVE-2018-7212
2018-02-21 21:04:36 +08:00
rack-protection (2.0.1)
Override the github git source instead of changing manually all entries
2016-09-14 08:19:09 +08:00
rack
Bump rack-test to 1.0.0
2018-03-28 06:24:49 +08:00
rack-test (1.0.0)
Update rack-test dependency constraint
2017-07-20 07:04:53 +08:00
rack (>= 1.0, < 3)
rails-dom-testing (2.0.3)
activesupport (>= 4.2.0)
nokogiri (>= 1.6)
Bundle update
2018-05-31 01:49:55 +08:00
rails-html-sanitizer (1.0.4)
loofah (~> 2.2, >= 2.2.2)
Update rubocop to the latest version Includes [Switch Layout/SpaceBeforeBlockBraces's empty braces default](https://github.com/bbatsov/rubocop/pull/5263) from [0.52.1](https://github.com/bbatsov/rubocop/blob/master/CHANGELOG.md#0521-2017-12-27). Before: 131 offenses detected. After: no offenses detected
2018-02-23 07:54:23 +08:00
rainbow (3.0.0)
Bundle update
2018-05-31 01:49:55 +08:00
rake (12.3.1)
rb-fsevent (0.10.3)
rdoc (6.0.4)
redcarpet 3.2.2 has an XSS vulnerability see: http://www.openwall.com/lists/oss-security/2015/04/07/11
2015-04-09 17:20:53 +08:00
redcarpet (3.2.3)
redis-rb 4.0 support * Use `gem 'redis', '~> 4.0'` for new app Gemfiles * Loosen Action Cable redis-rb dep to `>= 3.3, < 5` * Bump redis-namespace for looser Redis version dep * Avoid using the underlying `redis.client` directly * Use `Redis.new` instead of `Redis.connect`
2017-09-29 12:54:00 +08:00
redis (4.0.1)
Use released `redis-namespace` instead of master version The `redis-namespace` 1.6.0 includes redis-rb 4.0 support.
2017-11-08 16:08:23 +08:00
redis-namespace (1.6.0)
redis (>= 3.0.4)
Resolve gemspec typo
2017-08-01 04:55:55 +08:00
representable (3.0.4)
declarative (< 0.1.0)
declarative-option (< 0.2.0)
uber (< 0.2.0)
Update rack-test dependency constraint
2017-07-20 07:04:53 +08:00
resque (1.27.4)
Use released resque
2017-02-10 14:31:41 +08:00
mono_logger (~> 1.0)
multi_json (~> 1.0)
redis-namespace (~> 1.3)
sinatra (>= 0.9.2)
vegas (~> 0.1.2)
Use released `resque-scheduler` instead of master version The v4.3.1 has already released that includes Redis 4.0 support. https://github.com/resque/resque-scheduler/blob/master/CHANGELOG.md#431---2017-11-20
2017-12-14 06:49:08 +08:00
resque-scheduler (4.3.1)
mono_logger (~> 1.0)
redis (>= 3.3, < 5)
resque (~> 1.26)
rufus-scheduler (~> 3.2)
Resolve gemspec typo
2017-08-01 04:55:55 +08:00
retriable (3.1.1)
Bundle update
2018-05-31 01:49:55 +08:00
rubocop (0.56.0)
Bump rubocop and dependent gem versions
2017-05-24 14:20:00 +08:00
parallel (~> 1.10)
Rubocop 0.54 Fix `.rubocop.yml: Lint/EndAlignment has the wrong namespace - should be Layout` warning
2018-04-22 01:13:34 +08:00
parser (>= 2.5)
Add rubocop to Gemfile
2016-11-28 11:12:33 +08:00
powerpack (~> 0.1)
Update rubocop to the latest version Includes [Switch Layout/SpaceBeforeBlockBraces's empty braces default](https://github.com/bbatsov/rubocop/pull/5263) from [0.52.1](https://github.com/bbatsov/rubocop/blob/master/CHANGELOG.md#0521-2017-12-27). Before: 131 offenses detected. After: no offenses detected
2018-02-23 07:54:23 +08:00
rainbow (>= 2.2.2, < 4.0)
Add rubocop to Gemfile
2016-11-28 11:12:33 +08:00
ruby-progressbar (~> 1.7)
unicode-display_width (~> 1.0, >= 1.0.1)
Bump RuboCop 0.50.0 RuboCop 0.50.0 was released. https://github.com/bbatsov/rubocop/releases/tag/v0.50.0 And `rubocop-0-50` channel is available in Code Climate. https://github.com/codeclimate/codeclimate-rubocop/issues/107#issuecomment-336234260 This commit will bump RuboCop to 0.50.0. There are no new offences in this change. ```console % bundle exec rubocop --version 0.50.0 % bundle exec rubocop Inspecting 2350 files (snip) 2350 files inspected, no offenses detected ```
2017-10-13 10:52:33 +08:00
ruby-progressbar (1.9.0)
Bundle update
2018-05-31 01:49:55 +08:00
ruby-vips (2.0.12)
Use ImageProcessing gem for ActiveStorage variants ImageProcessing gem is a wrapper around MiniMagick and ruby-vips, and implements an interface for common image resizing and processing. This is the canonical image processing gem recommended in [Shrine], and that's where it developed from. The initial implementation was extracted from Refile, which also implements on-the-fly transformations. Some features that ImageProcessing gem adds on top of MiniMagick: * resizing macros - #resize_to_limit - #resize_to_fit - #resize_to_fill - #resize_and_pad * automatic orientation * automatic thumbnail sharpening * avoids the complex and inefficient MiniMagick::Image class * will use "magick" instead of "convert" on ImageMagick 7 However, the biggest feature of the ImageProcessing gem is that it has an alternative implementation that uses libvips. Libvips is an alternative to ImageMagick that can process images very rapidly (we've seen up 10x faster than ImageMagick). What's great is that the ImageProcessing gem provides the same interface for both implementations. The macros are named the same, and the libvips implementation does auto orientation and thumbnail sharpening as well; only the operations/options specific to ImageMagick/libvips differ. The integration provided by this PR should work for both implementations. The plan is to introduce the ImageProcessing backend in Rails 6.0 as the default backend and deprecate the MiniMagick backend, then in Rails 6.1 remove the MiniMagick backend.
2018-04-06 07:48:29 +08:00
ffi (~> 1.9)
bundle update
2016-12-26 20:46:01 +08:00
ruby_dep (1.5.0)
Update rack-test dependency constraint
2017-07-20 07:04:53 +08:00
rubyzip (1.2.1)
Bundle update
2018-05-31 01:49:55 +08:00
rufus-scheduler (3.5.0)
fugit (~> 1.1, >= 1.1.1)
sass (3.5.6)
Fix warnings in railties tests This warning has been fixed in sass-rails. This change picks up the fix.
2017-07-24 18:55:08 +08:00
sass-listen (~> 4.0.0)
sass-listen (4.0.0)
rb-fsevent (~> 0.9, >= 0.9.4)
rb-inotify (~> 0.9, >= 0.9.7)
Use released sass-rails
2017-11-15 03:42:12 +08:00
sass-rails (5.0.7)
railties (>= 4.0.0, < 6)
sass (~> 3.1)
sprockets (>= 2.8, < 4.0)
sprockets-rails (>= 2.0, < 4.0)
tilt (>= 1.1, < 3)
Refer to a stable release of SDoc
2018-02-07 02:49:15 +08:00
sdoc (1.0.0)
rdoc (>= 5.0)
Bundle update
2018-05-31 01:49:55 +08:00
selenium-webdriver (3.12.0)
Add accidentally removed dependency in Gemfile.lock Follow up to ca0b6d0d416776655ed7516ac18f126fbde5315a.
2016-08-04 06:55:47 +08:00
childprocess (~> 0.5)
Bundle update
2018-05-31 01:49:55 +08:00
rubyzip (~> 1.2)
sequel (5.8.0)
serverengine (2.0.6)
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-19 00:30:25 +08:00
sigdump (~> 0.2.2)
Bundle update
2018-05-31 01:49:55 +08:00
sidekiq (5.1.3)
Use released `sidekiq` instead of master version The sidekiq 5.0.5 includes redis-rb 4.0 support. Ref: https://github.com/mperham/sidekiq/blob/90db3b84208cbb73a50d1a77a1dea97d3490ce70/Changes.md#505
2017-10-09 19:49:55 +08:00
concurrent-ruby (~> 1.0)
connection_pool (~> 2.2, >= 2.2.0)
rack-protection (>= 1.5.0)
Bundle update
2018-05-31 01:49:55 +08:00
redis (>= 3.3.5, < 5)
Upgrade all gems to make sure Rails works with rack 2.0.0.rc1
2016-05-07 05:16:28 +08:00
sigdump (0.2.4)
Use `credentials` instead of `keyfile` in GCS sevice The `keyfile` was renamed to `credentials` in `google-cloud-storage` 1.8.0. https://github.com/GoogleCloudPlatform/google-cloud-ruby/blob/master/google-cloud-storage/CHANGELOG.md#180--2017-11-14 Although `keyfile` can still be used, but it looks like deprecate. https://github.com/GoogleCloudPlatform/google-cloud-ruby/blob/ddf7b2a856d676316525eb581c1a4cc83ca6097b/google-cloud-storage/lib/google/cloud/storage.rb#L589...L590 Therefore, I think that should use `credentials` in newly generated applications. Ref: https://github.com/GoogleCloudPlatform/google-cloud-ruby/issues/1802
2017-11-29 12:08:33 +08:00
signet (0.8.1)
Resolve gemspec typo
2017-08-01 04:55:55 +08:00
addressable (~> 2.3)
faraday (~> 0.9)
Use `credentials` instead of `keyfile` in GCS sevice The `keyfile` was renamed to `credentials` in `google-cloud-storage` 1.8.0. https://github.com/GoogleCloudPlatform/google-cloud-ruby/blob/master/google-cloud-storage/CHANGELOG.md#180--2017-11-14 Although `keyfile` can still be used, but it looks like deprecate. https://github.com/GoogleCloudPlatform/google-cloud-ruby/blob/ddf7b2a856d676316525eb581c1a4cc83ca6097b/google-cloud-storage/lib/google/cloud/storage.rb#L589...L590 Therefore, I think that should use `credentials` in newly generated applications. Ref: https://github.com/GoogleCloudPlatform/google-cloud-ruby/issues/1802
2017-11-29 12:08:33 +08:00
jwt (>= 1.5, < 3.0)
Resolve gemspec typo
2017-08-01 04:55:55 +08:00
multi_json (~> 1.10)
Update to sinatra 2.0.1 Although not a direct dependency, it's pulled in by Resque for Active Job integration tests so we need to update because the rack-protection gem has a security vulnerability[1]. [1]: https://nvd.nist.gov/vuln/detail/CVE-2018-7212
2018-02-21 21:04:36 +08:00
sinatra (2.0.1)
Update rack-test dependency constraint
2017-07-20 07:04:53 +08:00
mustermann (~> 1.0)
rack (~> 2.0)
Update to sinatra 2.0.1 Although not a direct dependency, it's pulled in by Resque for Active Job integration tests so we need to update because the rack-protection gem has a security vulnerability[1]. [1]: https://nvd.nist.gov/vuln/detail/CVE-2018-7212
2018-02-21 21:04:36 +08:00
rack-protection (= 2.0.1)
Update rack-test dependency constraint
2017-07-20 07:04:53 +08:00
tilt (~> 2.0)
Bundle update
2018-05-31 01:49:55 +08:00
sneakers (2.7.0)
bunny (~> 2.9.2)
concurrent-ruby (~> 1.0)
serverengine (~> 2.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-19 00:30:25 +08:00
thor
Update sprockets to Security release for CVE-2018-3760 See: https://github.com/rails/sprockets/blob/v3.7.2/CHANGELOG.md https://github.com/rails/sprockets/commit/9c34fa05900b968d74f08ccf40917848a7be9441
2018-06-24 16:44:52 +08:00
sprockets (3.7.2)
Use sprockets 3 in the Rails 5 release
2015-12-17 02:30:58 +08:00
concurrent-ruby (~> 1.0)
rack (> 1, < 3)
Update rack-test dependency constraint
2017-07-20 07:04:53 +08:00
sprockets-export (1.0.0)
Bundle update
2018-05-31 01:49:55 +08:00
sprockets-rails (3.2.1)
Use release sprockets-rails
2015-12-18 04:22:58 +08: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 16:38:19 +08:00
sqlite3 (1.3.13)
sqlite3 (1.3.13-x64-mingw32)
sqlite3 (1.3.13-x86-mingw32)
Bundle update
2018-05-31 01:49:55 +08:00
stackprof (0.2.11)
sucker_punch (2.0.4)
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-28 00:29:18 +08:00
concurrent-ruby (~> 1.0.0)
Update rack-test dependency constraint
2017-07-20 07:04:53 +08:00
thin (1.7.2)
Add accidentally removed dependency in Gemfile.lock Follow up to ca0b6d0d416776655ed7516ac18f126fbde5315a.
2016-08-04 06:55:47 +08:00
daemons (~> 1.0, >= 1.0.9)
eventmachine (~> 1.0, >= 1.0.4)
rack (>= 1, < 3)
Bump the bundled GlobalID version.
2017-04-16 23:40:00 +08:00
thread_safe (0.3.6)
bundle lock --add-platform java "The dependency activerecord-jdbcsqlite3-adapter (>= 1.3.0) will be unused by any of the platforms Bundler is installing for. Bundler is installing for ruby, x64-mingw32, x86-mingw32 but the dependency is only for java. To add those platforms to the bundle, run `bundle lock --add-platform java`."
2017-10-20 19:34:43 +08:00
thread_safe (0.3.6-java)
Fix warnings in railties tests This warning has been fixed in sass-rails. This change picks up the fix.
2017-07-24 18:55:08 +08:00
tilt (2.0.8)
Fix turbolinks warning in railties test * Upgrade turbolinks from v5.0.1 to v5.1.0 * Fix warning in railties test lib/turbolinks/assertions.rb:17: warning: assigned but unused variable - visit_action
2018-04-09 04:05:13 +08:00
turbolinks (5.1.1)
turbolinks-source (~> 5.1)
turbolinks-source (5.1.0)
Update et-orbi to latest version avoids `warning: assigned but unused variable - tu`.
2018-05-28 14:36:49 +08:00
tzinfo (1.2.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-19 00:30:25 +08:00
thread_safe (~> 0.1)
Bundle update
2018-05-31 01:49:55 +08:00
tzinfo-data (1.2018.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 22:04:31 +08:00
tzinfo (>= 1.0.0)
Resolve gemspec typo
2017-08-01 04:55:55 +08:00
uber (0.1.0)
Bundle update
2018-05-31 01:49:55 +08:00
uglifier (4.1.10)
Upgrade all gems to make sure Rails works with rack 2.0.0.rc1
2016-05-07 05:16:28 +08:00
execjs (>= 0.3.0, < 3)
Bundle update
2018-05-31 01:49:55 +08:00
unicode-display_width (1.3.3)
useragent (0.16.10)
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-19 00:30:25 +08:00
vegas (0.1.11)
rack (>= 1.0.0)
Update rack-test dependency constraint
2017-07-20 07:04:53 +08:00
w3c_validators (1.3.3)
json (>= 1.8)
bundle update
2016-12-26 20:46:01 +08:00
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-22 00:54:54 +08:00
wdm (0.1.1)
Bundle update
2018-05-31 01:49:55 +08:00
websocket (1.2.8)
websocket-driver (0.7.0)
Initial stab at adding Action Cable to rails/master
2015-12-14 23:38:37 +08:00
websocket-extensions (>= 0.1.0)
Bundle update
2018-05-31 01:49:55 +08:00
websocket-driver (0.7.0-java)
Start Rails 6.0 development!!! :tada::tada::tada:
2018-01-31 07:51:17 +08:00
websocket-extensions (>= 0.1.0)
Bundle update
2018-05-31 01:49:55 +08:00
websocket-extensions (0.1.3)
xpath (3.1.0)
Fix broken `ServerTest` with Capybara 3.0.0 It seems that it is no longer possible to specify the value held by `Capybara.server` as sever. Ref: https://github.com/teamcapybara/capybara/commit/ba7674086cbcd3b22d3614011815bc5d483e5960
2018-04-06 19:55:34 +08:00
nokogiri (~> 1.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-19 00:30:25 +08:00
PLATFORMS
bundle lock --add-platform java "The dependency activerecord-jdbcsqlite3-adapter (>= 1.3.0) will be unused by any of the platforms Bundler is installing for. Bundler is installing for ruby, x64-mingw32, x86-mingw32 but the dependency is only for java. To add those platforms to the bundle, run `bundle lock --add-platform java`."
2017-10-20 19:34:43 +08:00
java
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-19 00:30:25 +08:00
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-07 07:35:02 +08: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-19 00:30:25 +08:00
DEPENDENCIES
activerecord-jdbcmysql-adapter (>= 1.3.0)
activerecord-jdbcpostgresql-adapter (>= 1.3.0)
activerecord-jdbcsqlite3-adapter (>= 1.3.0)
Use v3 of the AWS SDK
2017-09-10 11:22:10 +08:00
aws-sdk-s3
Resolve gemspec typo
2017-08-01 04:55:55 +08:00
azure-storage
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-19 00:30:25 +08:00
backburner
Fix Gemfile.lock
2016-03-11 03:28:02 +08: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-19 00:30:25 +08:00
benchmark-ips
Update Blade and its Sauce Labs plugin for EventMachine 1.2 compatibility
2016-06-05 06:54:34 +08:00
blade
blade-sauce_labs_plugin
Add bootsnap to default Gemfile: Bootsnap precomputes load path resolution and caches ruby ISeq and YAML parsing/compilation, reducing application boot time by approximately 50% on supported configurations.
2017-06-02 02:28:51 +08:00
bootsnap (>= 1.1.0)
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 13:24:50 +08:00
byebug
Remove upper bound on Capybara There's no reason to block future versions of Capybara since we don't _know_ they are going to break. How will we know if we have a conservative option set? This change prevents us from blocking users who want to upgrade in the future.
2018-04-11 04:37:17 +08:00
capybara (>= 2.15)
PhantomJS is abandoned, replace it with Selenium/Chrome headless
2017-10-20 00:01:52 +08:00
chromedriver-helper
Point to released coffee-rails
2016-07-01 01:35:25 +08:00
coffee-rails
Support for connection pooling on mem cache store
2017-12-13 08:11:47 +08:00
connection_pool
Unlock dalli version The issue was fixed with https://github.com/petergoldstein/dalli/pull/679, and a new version containing that fix was released.
2018-04-11 15:52:10 +08:00
dalli
Use released `delayed_job` instead of master version Ref: https://github.com/collectiveidea/delayed_job/blob/master/CHANGELOG.md#414---2017-12-29
2017-12-30 05:57:28 +08:00
delayed_job
delayed_job and delayed_job_active_record gems with AR5 support are available
2017-01-29 08:05:06 +08:00
delayed_job_active_record
Fix segmentation fault in EventedFileUpdateChecker resolves #32705
2018-04-25 02:54:52 +08:00
ffi (<= 1.9.21)
Support streaming downloads from Google Cloud Storage
2018-05-02 11:20:56 +08:00
google-cloud-storage (~> 1.11)
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 23:00:00 +08:00
hiredis
Use ImageProcessing gem for ActiveStorage variants ImageProcessing gem is a wrapper around MiniMagick and ruby-vips, and implements an interface for common image resizing and processing. This is the canonical image processing gem recommended in [Shrine], and that's where it developed from. The initial implementation was extracted from Refile, which also implements on-the-fly transformations. Some features that ImageProcessing gem adds on top of MiniMagick: * resizing macros - #resize_to_limit - #resize_to_fit - #resize_to_fill - #resize_and_pad * automatic orientation * automatic thumbnail sharpening * avoids the complex and inefficient MiniMagick::Image class * will use "magick" instead of "convert" on ImageMagick 7 However, the biggest feature of the ImageProcessing gem is that it has an alternative implementation that uses libvips. Libvips is an alternative to ImageMagick that can process images very rapidly (we've seen up 10x faster than ImageMagick). What's great is that the ImageProcessing gem provides the same interface for both implementations. The macros are named the same, and the libvips implementation does auto orientation and thumbnail sharpening as well; only the operations/options specific to ImageMagick/libvips differ. The integration provided by this PR should work for both implementations. The plan is to introduce the ImageProcessing backend in Rails 6.0 as the default backend and deprecate the MiniMagick backend, then in Rails 6.1 remove the MiniMagick backend.
2018-04-06 07:48:29 +08:00
image_processing (~> 1.2)
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-15 08:26:03 +08:00
json (>= 2.0.0)
Fix rake guides:generate:kindle error
2016-12-18 23:13:50 +08:00
kindlerb (~> 1.2.0)
Install libxml-ruby gem so full XMLMini test suite can be run
2016-11-19 23:46:28 +08: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 19:28:17 +08:00
listen (>= 3.0.5, < 3.2)
Add minitest-bisect as part of the gemfile
2016-07-12 14:06:25 +08:00
minitest-bisect
mocha 1.3.0
2017-09-25 08:12:58 +08:00
mocha
Bump mysql2 version Skip 0.4.8 and 0.4.9, which had [Compilation failures against MariaDB Connector/C 3.0.2](https://github.com/brianmario/mysql2/releases/tag/0.4.10).
2018-02-16 02:12:58 +08:00
mysql2 (>= 0.4.10)
Update nokogiri version on Gemfile
2017-12-15 02:06:53 +08:00
nokogiri (>= 1.8.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-19 00:30:25 +08:00
pg (>= 0.18.0)
update psych gem to 3.2 stable release
2018-03-10 04:14:36 +08:00
psych (~> 3.0)
Initial stab at adding Action Cable to rails/master
2015-12-14 23:38:37 +08: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-19 00:30:25 +08:00
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 15:56:06 +08:00
queue_classic!
PhantomJS is abandoned, replace it with Selenium/Chrome headless
2017-10-20 00:01:52 +08:00
qunit-selenium
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-19 00:30:25 +08: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-31 00:12:20 +08:00
rake (>= 11.1)
Move back to @matthewd's close io fixed rb-inotify.
2017-07-20 01:43:12 +08:00
rb-inotify!
redcarpet 3.2.2 has an XSS vulnerability see: http://www.openwall.com/lists/oss-security/2015/04/07/11
2015-04-09 17:20:53 +08:00
redcarpet (~> 3.2.3)
redis-rb 4.0 support * Use `gem 'redis', '~> 4.0'` for new app Gemfiles * Loosen Action Cable redis-rb dep to `>= 3.3, < 5` * Bump redis-namespace for looser Redis version dep * Avoid using the underlying `redis.client` directly * Use `Redis.new` instead of `Redis.connect`
2017-09-29 12:54:00 +08:00
redis (~> 4.0)
Use released `redis-namespace` instead of master version The `redis-namespace` 1.6.0 includes redis-rb 4.0 support.
2017-11-08 16:08:23 +08:00
redis-namespace
Use released resque
2017-02-10 14:31:41 +08:00
resque
Use released `resque-scheduler` instead of master version The v4.3.1 has already released that includes Redis 4.0 support. https://github.com/resque/resque-scheduler/blob/master/CHANGELOG.md#431---2017-11-20
2017-12-14 06:49:08 +08:00
resque-scheduler
update rubocop to 0.47
2017-01-16 14:34:30 +08:00
rubocop (>= 0.47)
Use released sass-rails
2017-11-15 03:42:12 +08:00
sass-rails
Refer to a stable release of SDoc
2018-02-07 02:49:15 +08:00
sdoc (~> 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-19 00:30:25 +08:00
sequel
Use released `sidekiq` instead of master version The sidekiq 5.0.5 includes redis-rb 4.0 support. Ref: https://github.com/mperham/sidekiq/blob/90db3b84208cbb73a50d1a77a1dea97d3490ce70/Changes.md#505
2017-10-09 19:49:55 +08:00
sidekiq
Unlock sneakers adapter version
2015-04-26 15:44:18 +08:00
sneakers
Restore action_cable.js UMD module support. Fixes #28366
2017-03-12 01:33:11 +08: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-19 00:30:25 +08: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-28 00:29:18 +08:00
sucker_punch
Make Railties CI log for Ruby 2.6 accessible again Pending the next release of Thor which [fixes](https://github.com/erikhuda/thor/commit/006832ea32480618791f89bb7d9e67b22fc814b9) calls to `ERB.new`, Railties CI log for Ruby 2.6 is flooded with so many warnings it is too long for Travis to handle: ``` /home/travis/.rvm/gems/ruby-head/gems/thor-0.20.0/lib/thor/actions/file_manipulation.rb:120: warning: Passing safe_level with the 2nd argument of ERB.new is deprecated. Do not use it, and specify other arguments as keyword arguments. /home/travis/.rvm/gems/ruby-head/gems/thor-0.20.0/lib/thor/actions/file_manipulation.rb:120: warning: Passing trim_mode with the 3rd argument of ERB.new is deprecated. Use keyword argument like ERB.new(str, trim_mode: ...) instead. /home/travis/.rvm/gems/ruby-head/gems/thor-0.20.0/lib/thor/actions/file_manipulation.rb:120: warning: Passing eoutvar with the 4th argument of ERB.new is deprecated. Use keyword argument like ERB.new(str, eoutvar: ...) instead. The log length has exceeded the limit of 4 MB (this usually means that the test suite is raising the same exception over and over). The job has been terminated ``` https://travis-ci.org/rails/rails/jobs/372623604#L10000 https://api.travis-ci.org/v3/job/372623604/log.txt This patch forces installation of fixed Thor, and enables us to look at the the log.
2018-04-29 17:12:44 +08:00
thor!
Update to Turbolinks 5.0.0 final
2016-07-01 01:18:52 +08: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 22:04:31 +08: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-19 00:30:25 +08: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-22 00:54:54 +08:00
wdm (>= 0.1.0)
Use a branch of websocket-client-simple, to work around read/close race
2016-10-06 09:11:18 +08:00
websocket-client-simple!
Generate Bundler 1.10.1 lockfile
2015-05-29 13:40:29 +08:00
BUNDLED WITH
Update fugit to latest version [fugit 1.1.3](https://github.com/floraison/fugit/commit/03a3ee86f3cd5d929442dd25896b99acbd151947) fixes warnings that show up in ActiveJob tests. See [CI](https://travis-ci.org/rails/rails/jobs/394107740#L3764-L3778).
2018-06-21 18:05:42 +08:00
1.16.2