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

613 lines
15 KiB
Text
Raw Normal View History

Switch queue_classic back to origin repository It has been moved to the a fork as part of https://github.com/rails/rails/pull/31671 . That was since to that time a required PR was not yet merged. Now the queue_classic master branch is compatible to recent pg versions, so that there's no need to keep using a fork.
2019-01-25 14:01:47 -05:00
GIT
remote: https://github.com/QueueClassic/queue_classic.git
Bundle update
2019-10-10 00:48:16 -04:00
revision: 4260d8963ddef91bdb9ae390d93e811521b83350
Switch queue_classic back to origin repository It has been moved to the a fork as part of https://github.com/rails/rails/pull/31671 . That was since to that time a required PR was not yet merged. Now the queue_classic master branch is compatible to recent pg versions, so that there's no need to keep using a fork.
2019-01-25 14:01:47 -05:00
specs:
Bundle update
2019-10-10 00:48:16 -04:00
queue_classic (4.0.0.pre.alpha1)
Switch queue_classic back to origin repository It has been moved to the a fork as part of https://github.com/rails/rails/pull/31671 . That was since to that time a required PR was not yet merged. Now the queue_classic master branch is compatible to recent pg versions, so that there's no need to keep using a fork.
2019-01-25 14:01:47 -05:00
pg (>= 0.17, < 2.0)
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
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 6.1 development
2019-04-24 15:57:14 -04:00
actioncable (6.1.0.alpha)
actionpack (= 6.1.0.alpha)
Update Gemfile.lock with newly added `activesupport` dependencies Reference: 3b23c644971fc5805505748e78c3230d25ef7618
2019-10-01 22:24:44 -04:00
activesupport (= 6.1.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)
Update Gemfile.lock to reflect websocket-driver 0.7.0 Follow up to e1473e0cbfbd97eeea2bc6eefd73bec0d4863359
2018-01-18 17:50:50 -05:00
websocket-driver (>= 0.6.1)
Start Rails 6.1 development
2019-04-24 15:57:14 -04:00
actionmailbox (6.1.0.alpha)
actionpack (= 6.1.0.alpha)
activejob (= 6.1.0.alpha)
activerecord (= 6.1.0.alpha)
activestorage (= 6.1.0.alpha)
activesupport (= 6.1.0.alpha)
Import Action Mailbox
2018-12-24 15:16:22 -05:00
mail (>= 2.7.1)
Start Rails 6.1 development
2019-04-24 15:57:14 -04:00
actionmailer (6.1.0.alpha)
actionpack (= 6.1.0.alpha)
actionview (= 6.1.0.alpha)
activejob (= 6.1.0.alpha)
Update Gemfile.lock with newly added `activesupport` dependencies Reference: 3b23c644971fc5805505748e78c3230d25ef7618
2019-10-01 22:24:44 -04:00
activesupport (= 6.1.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 6.1 development
2019-04-24 15:57:14 -04:00
actionpack (6.1.0.alpha)
actionview (= 6.1.0.alpha)
activesupport (= 6.1.0.alpha)
Do not allow rack pre releases
2016-06-30 14:10:22 -04:00
rack (~> 2.0)
Update rack-test dependency constraint
2017-07-19 19:04:53 -04: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)
Rails HTML sanitizer gemfile lock changes on bundle install.
2019-08-09 11:40:59 -04:00
rails-html-sanitizer (~> 1.0, >= 1.2.0)
Start Rails 6.1 development
2019-04-24 15:57:14 -04:00
actiontext (6.1.0.alpha)
actionpack (= 6.1.0.alpha)
activerecord (= 6.1.0.alpha)
activestorage (= 6.1.0.alpha)
activesupport (= 6.1.0.alpha)
Import Action Text
2019-01-04 19:43:11 -05:00
nokogiri (>= 1.8.5)
Start Rails 6.1 development
2019-04-24 15:57:14 -04:00
actionview (6.1.0.alpha)
activesupport (= 6.1.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)
Require and support rails-html-sanitzer 1.2.0 Rails now requires 1.2.0 because it relies on the safe_list_sanitizer API exclusively. Also raise `sanitizer_vendor` API from the dead for rails-deprecated_sanitizer. Fixes https://github.com/rails/rails-deprecated_sanitizer/pull/6
2019-08-08 18:07:45 -04:00
rails-html-sanitizer (~> 1.1, >= 1.2.0)
Start Rails 6.1 development
2019-04-24 15:57:14 -04:00
activejob (6.1.0.alpha)
activesupport (= 6.1.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 6.1 development
2019-04-24 15:57:14 -04:00
activemodel (6.1.0.alpha)
activesupport (= 6.1.0.alpha)
activerecord (6.1.0.alpha)
activemodel (= 6.1.0.alpha)
activesupport (= 6.1.0.alpha)
activestorage (6.1.0.alpha)
actionpack (= 6.1.0.alpha)
activejob (= 6.1.0.alpha)
activerecord (= 6.1.0.alpha)
Update Gemfile.lock with newly added `activesupport` dependencies Reference: 3b23c644971fc5805505748e78c3230d25ef7618
2019-10-01 22:24:44 -04:00
activesupport (= 6.1.0.alpha)
Extract content types from blob data
2018-01-15 13:06:17 -05:00
marcel (~> 0.3.1)
Start Rails 6.1 development
2019-04-24 15:57:14 -04:00
activesupport (6.1.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)
Don't force people to upgrade i18n gem
2018-02-14 11:55:36 -05: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-18 11:30:25 -05:00
minitest (~> 5.1)
tzinfo (~> 1.1)
bump Zeitwerk to 2.2
2019-10-09 15:28:35 -04:00
zeitwerk (~> 2.2)
Start Rails 6.1 development
2019-04-24 15:57:14 -04:00
rails (6.1.0.alpha)
actioncable (= 6.1.0.alpha)
actionmailbox (= 6.1.0.alpha)
actionmailer (= 6.1.0.alpha)
actionpack (= 6.1.0.alpha)
actiontext (= 6.1.0.alpha)
actionview (= 6.1.0.alpha)
activejob (= 6.1.0.alpha)
activemodel (= 6.1.0.alpha)
activerecord (= 6.1.0.alpha)
activestorage (= 6.1.0.alpha)
activesupport (= 6.1.0.alpha)
Commit gemfile.lock
2017-07-04 14:54:26 -04:00
bundler (>= 1.3.0)
Start Rails 6.1 development
2019-04-24 15:57:14 -04:00
railties (= 6.1.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 6.1 development
2019-04-24 15:57:14 -04:00
railties (6.1.0.alpha)
actionpack (= 6.1.0.alpha)
activesupport (= 6.1.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)
Abort early if generator command fails (#34420) * No need to go through ruby * Abort early if a generator command fails * Reuse `rails_command` method * Bump thor minimum dependency to 0.20.3 * Add some minimal docs * Add a changelog entry * Restore original logging
2018-12-07 01:01:32 -05:00
thor (>= 0.20.3, < 2.0)
Track Gemfile.lock at the repository The main reason is to make bisect easier. In some points, we have a lot of git dependencies. Since we don't have the information of which commit we are referring to, bundler get the latest commit of the master branch of the dependency. This sometimes returns a version that is not compatible with Rails anymore, making the tests fail and the harder to identify the commit that introduced a bug. Also this will make sure that a contributor will always get a set of dependencies that are passing with our tests. In our CI server we delete the lock file to make sure we are always testing against the newest release of our dependencies.
2015-02-18 11:30:25 -05:00
GEM
remote: https://rubygems.org/
specs:
Bundle update
2019-10-10 00:48:16 -04:00
activerecord-jdbc-adapter (52.3-java)
Upgrade all the gems
2018-09-05 17:41:31 -04:00
activerecord (~> 5.2.0)
Bundle update
2019-10-10 00:48:16 -04:00
activerecord-jdbcmysql-adapter (52.3-java)
activerecord-jdbc-adapter (= 52.3)
jdbc-mysql (~> 5.1.36, < 9)
activerecord-jdbcpostgresql-adapter (52.3-java)
activerecord-jdbc-adapter (= 52.3)
Bundle update
2018-05-30 13:49:55 -04:00
jdbc-postgres (>= 9.4, < 43)
Bundle update
2019-10-10 00:48:16 -04:00
activerecord-jdbcsqlite3-adapter (52.3-java)
activerecord-jdbc-adapter (= 52.3)
Bundle update
2018-05-30 13:49:55 -04:00
jdbc-sqlite3 (~> 3.8, < 3.30)
Bundle update
2019-10-10 00:48:16 -04:00
addressable (2.7.0)
public_suffix (>= 2.0.2, < 5.0)
Bundle update
2018-05-30 13:49:55 -04:00
amq-protocol (2.3.0)
Output junit format test report
2019-03-24 13:59:28 -04:00
ansi (1.5.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-22 18:54:23 -05:00
ast (2.4.0)
Bundle update
2019-10-10 00:48:16 -04:00
aws-eventstream (1.0.3)
aws-partitions (1.221.0)
aws-sdk-core (3.68.1)
aws-eventstream (~> 1.0, >= 1.0.2)
Use v3 of the AWS SDK
2017-09-09 23:22:10 -04:00
aws-partitions (~> 1.0)
Bundle update
2019-10-10 00:48:16 -04:00
aws-sigv4 (~> 1.1)
Resolve gemspec typo
2017-07-31 16:55:55 -04:00
jmespath (~> 1.0)
Bundle update
2019-10-10 00:48:16 -04:00
aws-sdk-kms (1.24.0)
aws-sdk-core (~> 3, >= 3.61.1)
aws-sigv4 (~> 1.1)
aws-sdk-s3 (1.48.0)
aws-sdk-core (~> 3, >= 3.61.1)
Use v3 of the AWS SDK
2017-09-09 23:22:10 -04:00
aws-sdk-kms (~> 1)
Bundle update
2019-10-10 00:48:16 -04:00
aws-sigv4 (~> 1.1)
aws-sdk-sns (1.19.0)
aws-sdk-core (~> 3, >= 3.61.1)
aws-sigv4 (~> 1.1)
aws-sigv4 (1.1.0)
aws-eventstream (~> 1.0, >= 1.0.2)
Update azure-storage gem to latest version
2019-08-06 12:25:39 -04:00
azure-core (0.1.15)
Depend on offical azure-core No need to depend on my fork anymore, they've just release fix officially.
2017-08-02 03:38:03 -04: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 00:53:02 -04:00
nokogiri (~> 1.6)
Update azure-storage gem to latest version
2019-08-06 12:25:39 -04:00
azure-storage-blob (1.1.0)
azure-core (~> 0.1.13)
azure-storage-common (~> 1.0)
nokogiri (~> 1.6, >= 1.6.8)
azure-storage-common (1.1.0)
azure-core (~> 0.1.13)
Bundle update
2018-05-30 13:49:55 -04:00
nokogiri (~> 1.6, >= 1.6.8)
Update backburner to the latest version version 1.5.0 includes to warning fixes that show on tests: https://github.com/nesquena/backburner/commit/cd9670146bca4df83ae2aacb95b3e6d1c1c1eee8 https://github.com/nesquena/backburner/commit/4dfa22bda1685ca1afa9f7d474df471ca6364e69
2018-09-28 06:40:24 -04:00
backburner (1.5.0)
Update Gemfile.lock
2015-08-09 23:30:03 -04:00
beaneater (~> 1.0)
Update backburner to the latest version version 1.5.0 includes to warning fixes that show on tests: https://github.com/nesquena/backburner/commit/cd9670146bca4df83ae2aacb95b3e6d1c1c1eee8 https://github.com/nesquena/backburner/commit/4dfa22bda1685ca1afa9f7d474df471ca6364e69
2018-09-28 06:40:24 -04:00
concurrent-ruby (~> 1.0, >= 1.0.1)
Update Gemfile.lock
2015-08-09 23:30:03 -04:00
dante (> 0.1.5)
Bundle update
2019-10-10 00:48:16 -04:00
bcrypt (3.1.13)
bcrypt (3.1.13-java)
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)
Bump `thor` and `blade` For test with latest thor.
2017-08-16 19:53:36 -04:00
blade (0.7.1)
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)
Bump `thor` and `blade` For test with latest thor.
2017-08-16 19:53:36 -04:00
thor (>= 0.19.1)
Add accidentally removed dependency in Gemfile.lock Follow up to ca0b6d0d416776655ed7516ac18f126fbde5315a.
2016-08-03 18:55:47 -04: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-20 17:08:31 -05:00
blade-qunit_adapter (2.0.1)
Bundle update
2018-05-30 13:49:55 -04:00
blade-sauce_labs_plugin (0.7.3)
Add accidentally removed dependency in Gemfile.lock Follow up to ca0b6d0d416776655ed7516ac18f126fbde5315a.
2016-08-03 18:55:47 -04:00
childprocess
faraday
selenium-webdriver
Bundle update
2019-10-10 00:48:16 -04:00
bootsnap (1.4.5)
Upgrade capybara to 3.0.1 to make sure our tests are passing
2018-04-06 17:09:14 -04:00
msgpack (~> 1.0)
Bundle update
2019-10-10 00:48:16 -04:00
bootsnap (1.4.5-java)
includes bootsnap 1.4.2-java in Gemfile.lock Was just pushed.
2019-03-26 16:32:01 -04:00
msgpack (~> 1.0)
Update builder gem to avoid deprecations of 2.4
2017-01-13 13:50:25 -05:00
builder (3.2.3)
Bundle update
2019-10-10 00:48:16 -04:00
bunny (2.14.3)
Update Sneakers to the latest version Sneakers 2.11.0 has a more recent Bunny dependency which squashes some Ruby 2.6 warnings tickled by ActiveJob tests.
2019-01-29 17:39:43 -05:00
amq-protocol (~> 2.3, >= 2.3.0)
Bundle update
2019-10-10 00:48:16 -04:00
byebug (11.0.1)
capybara (3.29.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
addressable
Test with released thor thor 0.20.0 was released so we can test with the released version.
2017-08-16 14:03:24 -04: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 07:55:34 -04:00
nokogiri (~> 1.8)
rack (>= 1.6.0)
rack-test (>= 0.6.3)
Stop setting a default Capybara app host It's intended not to be set if Capybara starts the app server itself. Base Rails-generated URLs off of Capybara.current_session.server_url instead.
2019-07-24 22:19:21 -04:00
regexp_parser (~> 1.5)
bundle update
2018-11-09 17:21:08 -05:00
xpath (~> 3.2)
Bundle update
2019-10-10 00:48:16 -04:00
childprocess (3.0.0)
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)
Support Rails with sass-rails 6
2019-08-16 16:13:24 -04:00
concurrent-ruby (1.1.5)
Bundle update
2018-05-30 13:49:55 -04:00
connection_pool (2.2.2)
Override the github git source instead of changing manually all entries
2016-09-13 20:19:09 -04:00
cookiejar (0.3.3)
Extract ActionMailbox::PostfixRelayer
2018-11-25 14:30:05 -05:00
crack (0.4.3)
safe_yaml (~> 1.0.0)
Bundle update
2018-05-30 13:49:55 -04:00
crass (1.0.4)
Add accidentally removed dependency in Gemfile.lock Follow up to ca0b6d0d416776655ed7516ac18f126fbde5315a.
2016-08-03 18:55:47 -04:00
curses (1.0.2)
Bundle update
2019-10-10 00:48:16 -04:00
daemons (1.3.1)
dalli (2.7.10)
Update Gemfile.lock
2015-08-09 23:30:03 -04: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-28 23:08:33 -05:00
declarative (0.0.10)
Resolve gemspec typo
2017-07-31 16:55:55 -04:00
declarative-option (0.1.0)
Bundle update
2019-10-10 00:48:16 -04:00
delayed_job (4.1.8)
activesupport (>= 3.0, < 6.1)
delayed_job_active_record (4.1.4)
activerecord (>= 3.0, < 6.1)
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)
Resolve gemspec typo
2017-07-31 16:55:55 -04:00
digest-crc (0.4.1)
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)
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-06 17:08:13 -05: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-21 14:15:58 -04:00
eventmachine (>= 1.0.0.beta.4)
Bundle update
2019-10-10 00:48:16 -04:00
erubi (1.9.0)
et-orbi (1.2.2)
Update rack-test dependency constraint
2017-07-19 19:04:53 -04:00
tzinfo
Suppress deprecated warning in Action Cable
2017-07-25 02:53:02 -04:00
event_emitter (0.2.6)
Bundle update
2018-05-30 13:49:55 -04:00
eventmachine (1.2.7)
Update Blade and its Sauce Labs plugin for EventMachine 1.2 compatibility
2016-06-04 18:54:34 -04:00
execjs (2.7.0)
Bundle update
2019-10-10 00:48:16 -04:00
faraday (0.17.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)
Update azure-storage gem to latest version
2019-08-06 12:25:39 -04:00
faraday_middleware (0.13.1)
Resolve gemspec typo
2017-07-31 16:55:55 -04:00
faraday (>= 0.7.4, < 1.0)
Update rack-test dependency constraint
2017-07-19 19:04:53 -04: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-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)
Bundle update
2019-10-10 00:48:16 -04:00
faye-websocket (0.10.9)
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)
Unlock `selenium-webdriver` version `selenium-webdriver` is deprecateing various features for improvement in 4.0. I want to test with the latest version to check if Rails uses deprecated features or not.
2019-06-06 00:29:02 -04:00
ffi (1.11.1)
ffi (1.11.1-java)
ffi (1.11.1-x64-mingw32)
ffi (1.11.1-x86-mingw32)
Bundle update
2019-10-10 00:48:16 -04:00
fugit (1.3.3)
bundle update resque-scheduler to latest version Resque 2.0 includes grammar fixes for warnings tickled by our tests. Updating resque-scheduler also requires and updates resque to version 2.0. ``` $ ruby -v ruby 2.6.2p47 (2019-03-13 revision 67232) [x86_64-linux] ```
2019-05-08 08:58:20 -04:00
et-orbi (~> 1.1, >= 1.1.8)
Bundle update
2018-05-30 13:49:55 -04:00
raabro (~> 1.1)
Preparing for 6.0.0.beta2 release
2019-02-25 17:45:04 -05:00
globalid (0.4.2)
Bump the bundled GlobalID version.
2017-04-16 11:40:00 -04:00
activesupport (>= 4.2.0)
Bundle update
2019-10-10 00:48:16 -04:00
google-api-client (0.32.1)
Resolve gemspec typo
2017-07-31 16:55:55 -04:00
addressable (~> 2.5, >= 2.5.1)
Bundle update
2019-10-10 00:48:16 -04:00
googleauth (>= 0.5, < 0.10.0)
Resolve gemspec typo
2017-07-31 16:55:55 -04:00
httpclient (>= 2.8.1, < 3.0)
Bundle update
2019-10-10 00:48:16 -04:00
mini_mime (~> 1.0)
Resolve gemspec typo
2017-07-31 16:55:55 -04:00
representable (~> 3.0)
retriable (>= 2.0, < 4.0)
bundle update
2018-11-09 17:21:08 -05:00
signet (~> 0.10)
Bundle update
2019-10-10 00:48:16 -04:00
google-cloud-core (1.3.1)
Resolve gemspec typo
2017-07-31 16:55:55 -04:00
google-cloud-env (~> 1.0)
Bundle update
2019-10-10 00:48:16 -04:00
google-cloud-env (1.2.1)
Resolve gemspec typo
2017-07-31 16:55:55 -04:00
faraday (~> 0.11)
Bundle update
2019-10-10 00:48:16 -04:00
google-cloud-storage (1.21.1)
addressable (~> 2.5)
Resolve gemspec typo
2017-07-31 16:55:55 -04:00
digest-crc (~> 0.4)
Bundle update
2019-10-10 00:48:16 -04:00
google-api-client (~> 0.26)
Support streaming downloads from Google Cloud Storage
2018-05-01 23:20:56 -04:00
google-cloud-core (~> 1.2)
Bundle update
2019-10-10 00:48:16 -04:00
googleauth (>= 0.6.2, < 0.10.0)
mini_mime (~> 1.0)
googleauth (0.9.0)
Resolve gemspec typo
2017-07-31 16:55:55 -04: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-28 23:08:33 -05:00
jwt (>= 1.4, < 3.0)
bundle update
2018-11-09 17:21:08 -05:00
memoist (~> 0.16)
Resolve gemspec typo
2017-07-31 16:55:55 -04:00
multi_json (~> 1.11)
Upgrade all the gems
2018-09-05 17:41:31 -04:00
os (>= 0.9, < 2.0)
Resolve gemspec typo
2017-07-31 16:55:55 -04:00
signet (~> 0.7)
Bundle update
2019-10-10 00:48:16 -04:00
hashdiff (1.0.0)
bundle update
2018-11-09 17:21:08 -05:00
hiredis (0.6.3)
hiredis (0.6.3-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-21 14:15:58 -04:00
http_parser.rb (0.6.0)
Resolve gemspec typo
2017-07-31 16:55:55 -04:00
httpclient (2.8.3)
Update i18n to the latest version ``` /home/u/.rbenv/versions/2.7.0-dev/lib/ruby/gems/2.7.0/gems/i18n-1.6.0/lib/i18n/backend/base.rb:146: warning: The last argument is used as the keyword parameter /home/u/.rbenv/versions/2.7.0-dev/lib/ruby/gems/2.7.0/gems/i18n-1.6.0/lib/i18n/backend/base.rb:84: warning: The last argument is used as the keyword parameter /home/u/.rbenv/versions/2.7.0-dev/lib/ruby/gems/2.7.0/gems/i18n-1.6.0/lib/i18n.rb:179: warning: for `t' defined here /home/u/.rbenv/versions/2.7.0-dev/lib/ruby/gems/2.7.0/gems/i18n-1.6.0/lib/i18n.rb:179: warning: for `translate' defined here /home/u/.rbenv/versions/2.7.0-dev/lib/ruby/gems/2.7.0/gems/i18n-1.6.0/lib/i18n.rb:205: warning: The last argument is used as the keyword parameter ``` Was fixed by ruby-i18n/i18n@2920107fbfbf8778e5e197b7439d24c8a3720762 .
2019-10-07 16:52:51 -04:00
i18n (1.7.0)
Preparing for 5.2.0.beta1 release
2017-11-27 13:01:15 -05:00
concurrent-ruby (~> 1.0)
Bundle update
2019-10-10 00:48:16 -04:00
image_processing (1.9.3)
mini_magick (>= 4.9.5, < 5)
bundle update
2018-11-09 17:21:08 -05:00
ruby-vips (>= 2.0.13, < 3)
Bump RuboCop to 0.74.0 ### Summary RuboCop 0.74.0 has been released. https://github.com/rubocop-hq/rubocop/releases/tag/v0.74.0 And rubocop-0-74 channel is available in Code Climate. https://github.com/codeclimate/codeclimate/releases/tag/v0.85.5 This PR specifies the same RuboCop Performance (1.3.0) and RuboCop Rails (2.0.0) versions as Code Climate's Gemfile.lock. https://github.com/codeclimate/codeclimate-rubocop/blob/channel/rubocop-0-74/Gemfile.lock#L51-L55 Also, the `EnforcedStyle` of `Layout/IndentationConsistency` has been renamed from `EnforcedStyle: rails` to `EnforcedStyle: indented_internal_methods` - https://github.com/rubocop-hq/rubocop/pull/7113 - https://github.com/rubocop-hq/rubocop/pull/7163 And this commit disables `Layout/SpaceAroundOperators` that was changed from RuboCop 0.74 by rubocop-hq/rubocop#7211. cf. https://github.com/rails/rails/pull/36943#issuecomment-521659529
2019-08-15 08:56:18 -04:00
jaro_winkler (1.5.3)
jaro_winkler (1.5.3-java)
Bundle update
2019-10-10 00:48:16 -04:00
jdbc-mysql (5.1.47)
jdbc-postgres (42.2.6)
jdbc-sqlite3 (3.28.0)
Bundle update
2018-05-30 13:49:55 -04:00
jmespath (1.4.0)
Update json to the latest version ``` /home/u/.rbenv/versions/2.7.0-dev/lib/ruby/gems/2.7.0/gems/json-2.1.0/lib/json/common.rb:156: warning: The last argument is nil, treating as empty keywords /home/u/.rbenv/versions/2.7.0-dev/lib/ruby/gems/2.7.0/gems/json-2.1.0/lib/json/common.rb:156: warning: The last argument is used as the keyword parameter ``` Was fixed in 2.2.0.
2019-10-07 18:40:45 -04:00
json (2.2.0)
json (2.2.0-java)
Bundle update
2019-10-10 00:48:16 -04:00
jwt (2.2.1)
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
Bundle update
2018-05-30 13:49:55 -04: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 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)
Bundle update
2019-10-10 00:48:16 -04:00
loofah (2.3.0)
Preparing for 5.2.0.beta1 release
2017-11-27 13:01:15 -05: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-18 11:30:25 -05:00
nokogiri (>= 1.5.9)
Bump mail to `2.7.1`
2018-10-13 19:33:40 -04:00
mail (2.7.1)
Fix tests on Mail 2.7 Reverts 4d96be1c27bd6faed957b197a461f18543acebf2 References #31026
2017-11-01 00:44:55 -04:00
mini_mime (>= 0.1.1)
Bump marcel for significant gem size reduction
2018-09-14 23:49:07 -04:00
marcel (0.3.3)
Extract content types from blob data
2018-01-15 13:06:17 -05:00
mimemagic (~> 0.3.2)
Resolve gemspec typo
2017-07-31 16:55:55 -04:00
memoist (0.16.0)
Abort early if generator command fails (#34420) * No need to go through ruby * Abort early if a generator command fails * Reuse `rails_command` method * Bump thor minimum dependency to 0.20.3 * Add some minimal docs * Add a changelog entry * Restore original logging
2018-12-07 01:01:32 -05:00
method_source (0.9.2)
Import Action Mailbox
2018-12-24 15:16:22 -05:00
mimemagic (0.3.3)
Update mini_magick to the latest version Squashes 7 warnings tickled by ActiveStorage test task. Before: ``` ~/code/rails/activestorage$ bundle exec rake test 2>&1 | grep mini_magick /home/u/.rbenv/versions/2.7.0-dev/lib/ruby/gems/2.7.0/gems/mini_magick-4.9.2/lib/mini_magick/configuration.rb:122: warning: method redefined; discarding old processor /home/u/.rbenv/versions/2.7.0-dev/lib/ruby/gems/2.7.0/gems/mini_magick-4.9.2/lib/mini_magick/configuration.rb:128: warning: method redefined; discarding old processor= /home/u/.rbenv/versions/2.7.0-dev/lib/ruby/gems/2.7.0/gems/mini_magick-4.9.2/lib/mini_magick/configuration.rb:138: warning: method redefined; discarding old cli /home/u/.rbenv/versions/2.7.0-dev/lib/ruby/gems/2.7.0/gems/mini_magick-4.9.2/lib/mini_magick/configuration.rb:139: warning: instance variable @cli not initialized /home/u/.rbenv/versions/2.7.0-dev/lib/ruby/gems/2.7.0/gems/mini_magick-4.9.2/lib/mini_magick/configuration.rb:143: warning: method redefined; discarding old cli= /home/u/.rbenv/versions/2.7.0-dev/lib/ruby/gems/2.7.0/gems/mini_magick-4.9.2/lib/mini_magick/configuration.rb:153: warning: method redefined; discarding old cli_path /home/u/.rbenv/versions/2.7.0-dev/lib/ruby/gems/2.7.0/gems/mini_magick-4.9.2/lib/mini_magick/configuration.rb:154: warning: instance variable @cli_path not initialized /home/u/.rbenv/versions/2.7.0-dev/lib/ruby/gems/2.7.0/gems/mini_magick-4.9.2/lib/mini_magick/configuration.rb:154: warning: instance variable @processor_path not initialized /home/u/.rbenv/versions/2.7.0-dev/lib/ruby/gems/2.7.0/gems/mini_magick-4.9.2/lib/mini_magick/configuration.rb:157: warning: method redefined; discarding old debug= ``` After: ``` ~/code/rails/activestorage$ bundle exec rake test 2>&1 | grep mini_magick /home/u/.rbenv/versions/2.7.0-dev/lib/ruby/gems/2.7.0/gems/mini_magick-4.9.5/lib/mini_magick/configuration.rb:142: warning: method redefined; discarding old cli /home/u/.rbenv/versions/2.7.0-dev/lib/ruby/gems/2.7.0/gems/mini_magick-4.9.5/lib/mini_magick/configuration.rb:157: warning: method redefined; discarding old cli= ```
2019-08-16 01:33:22 -04:00
mini_magick (4.9.5)
Bundle update
2019-10-10 00:48:16 -04:00
mini_mime (1.0.2)
Bump Nokogiri for sparklemotion/nokogiri@bf41ba0
2018-12-31 20:33:26 -05:00
mini_portile2 (2.4.0)
Address to the warning "DEPRECATED: global use of assertion methods" This addresses to the warning "DEPRECATED: global use of assertion methods" which is introduced in minitest v5.12.0. https://github.com/seattlerb/minitest/commit/e6bc4485730403faff6966c1671cf5de72b2d233 https://buildkite.com/rails/rails/builds/64121#880aecf2-849f-4603-95f1-228784c7d3f4/1003-1010
2019-10-04 04:16:33 -04:00
minitest (5.12.2)
Bundle update
2019-10-10 00:48:16 -04:00
minitest-bisect (1.5.1)
Add minitest-bisect as part of the gemfile
2016-07-12 02:06:25 -04:00
minitest-server (~> 1.0)
Bundle update
2019-10-10 00:48:16 -04:00
path_expander (~> 1.1)
minitest-reporters (1.4.0)
Output junit format test report
2019-03-24 13:59:28 -04:00
ansi
builder
minitest (>= 5.0)
ruby-progressbar
Add test retries for railties
2018-10-10 18:33:09 -04:00
minitest-retry (0.1.9)
minitest (>= 5.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 07:47:48 -05:00
minitest-server (1.0.5)
Add minitest-bisect as part of the gemfile
2016-07-12 02:06:25 -04:00
minitest (~> 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-18 11:30:25 -05:00
mono_logger (1.1.0)
Bundle update
2019-10-10 00:48:16 -04:00
msgpack (1.3.1)
msgpack (1.3.1-java)
msgpack (1.3.1-x64-mingw32)
msgpack (1.3.1-x86-mingw32)
Update multi_json to the latest version Avoid `warning: tried to create a Proc object without giving a block` in Ruby head. Fixed in intridea/multi_json@26a94ab8c78a394cc237e2ea292c1de4f6ed30d7 .
2019-10-15 04:22:20 -04:00
multi_json (1.14.1)
Bundle update
2019-10-10 00:48:16 -04:00
multipart-post (2.1.1)
bundle update
2018-11-09 17:21:08 -05:00
mustache (1.1.0)
Upgrade all the gems
2018-09-05 17:41:31 -04:00
mustermann (1.0.3)
mysql2 (0.5.2)
Address to the warning "DEPRECATED: global use of assertion methods" This addresses to the warning "DEPRECATED: global use of assertion methods" which is introduced in minitest v5.12.0. https://github.com/seattlerb/minitest/commit/e6bc4485730403faff6966c1671cf5de72b2d233 https://buildkite.com/rails/rails/builds/64121#880aecf2-849f-4603-95f1-228784c7d3f4/1003-1010
2019-10-04 04:16:33 -04:00
mysql2 (0.5.2-x64-mingw32)
mysql2 (0.5.2-x86-mingw32)
Bundle update
2019-10-10 00:48:16 -04:00
nio4r (2.5.2)
nio4r (2.5.2-java)
Support Rails with sass-rails 6
2019-08-16 16:13:24 -04:00
nokogiri (1.10.4)
Bump Nokogiri for sparklemotion/nokogiri@bf41ba0
2018-12-31 20:33:26 -05:00
mini_portile2 (~> 2.4.0)
Support Rails with sass-rails 6
2019-08-16 16:13:24 -04:00
nokogiri (1.10.4-java)
nokogiri (1.10.4-x64-mingw32)
Bump Nokogiri for sparklemotion/nokogiri@bf41ba0
2018-12-31 20:33:26 -05:00
mini_portile2 (~> 2.4.0)
Support Rails with sass-rails 6
2019-08-16 16:13:24 -04:00
nokogiri (1.10.4-x86-mingw32)
Bump Nokogiri for sparklemotion/nokogiri@bf41ba0
2018-12-31 20:33:26 -05:00
mini_portile2 (~> 2.4.0)
Bundle update
2019-10-10 00:48:16 -04:00
os (1.0.1)
parallel (1.18.0)
parser (2.6.5.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-22 18:54:23 -05:00
ast (~> 2.4.0)
Bundle update
2019-10-10 00:48:16 -04:00
path_expander (1.1.0)
pg (1.1.4)
pg (1.1.4-x64-mingw32)
pg (1.1.4-x86-mingw32)
Bump RuboCop to 0.66.0 ### Summary RuboCop 0.66.0 has been released. https://github.com/rubocop-hq/rubocop/releases/tag/v0.66.0 And rubocop-0-66 channel is available in Code Climate. https://github.com/codeclimate/codeclimate/releases/tag/v0.84.0 RuboCop 0.66.0 fixed the false negative to indentation for modifier. And this PR applied the auto-correction fixed by it. https://github.com/rubocop-hq/rubocop/pull/6792 In addtion, this PR is also updating the following 4 gems that RuboCop depends on. - Update Psych gem ... https://github.com/rubocop-hq/rubocop/pull/6766 - Update Parser gem to 2.6.2.0 that supports Ruby 2.5.5 and 2.6.2 ... https://github.com/whitequark/parser/blob/v2.6.2.0/CHANGELOG.md#changelog - Remove powerpack gem ... https://github.com/rubocop-hq/rubocop/pull/6806 - Update unicode-display_width gem ... https://github.com/rubocop-hq/rubocop/pull/6813
2019-03-26 01:03:21 -04:00
psych (3.1.0)
Bundle update
2019-10-10 00:48:16 -04:00
public_suffix (4.0.1)
puma (4.2.1)
Update puma to the latest version Currently: `lib/ruby/gems/2.6.0/gems/puma-3.12.1/lib/puma/minissl.rb:5: warning: mismatched indentations at 'rescue' with 'begin' at 3`
2019-08-18 07:21:39 -04:00
nio4r (~> 2.0)
Bundle update
2019-10-10 00:48:16 -04:00
puma (4.2.1-java)
Update puma to the latest version Currently: `lib/ruby/gems/2.6.0/gems/puma-3.12.1/lib/puma/minissl.rb:5: warning: mismatched indentations at 'rescue' with 'begin' at 3`
2019-08-18 07:21:39 -04:00
nio4r (~> 2.0)
Bundle update
2018-05-30 13:49:55 -04:00
que (0.14.3)
PhantomJS is abandoned, replace it with Selenium/Chrome headless
2017-10-19 12:01:52 -04: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-23 17:23:54 -04:00
raabro (1.1.6)
Update racc to latest version racc 1.4.15 includes fixes for compiling with Ruby 2.7 since [ruby/ruby@3d1c86a](https://github.com/ruby/ruby/commit/3d1c86a). Before: ``` ruby -v ruby 2.7.0dev (2019-03-07 trunk 67189) [x86_64-linux] bundle install ... Fetching racc 1.4.14 Installing racc 1.4.14 with native extensions Gem::Ext::BuildError: ERROR: Failed to build gem native extension. current directory: /home/u/.rbenv/versions/2.7.0-dev/lib/ruby/gems/2.7.0/gems/racc-1.4.14/ext/racc /home/u/.rbenv/versions/2.7.0-dev/bin/ruby -I /home/u/.rbenv/versions/2.7.0-dev/lib/ruby/2.7.0 -r ./siteconf20190307-14242-16jzp6c.rb extconf.rb checking for rb_ary_subseq()... yes creating Makefile current directory: /home/u/.rbenv/versions/2.7.0-dev/lib/ruby/gems/2.7.0/gems/racc-1.4.14/ext/racc make "DESTDIR=" clean current directory: /home/u/.rbenv/versions/2.7.0-dev/lib/ruby/gems/2.7.0/gems/racc-1.4.14/ext/racc make "DESTDIR=" make: *** No rule to make target '/home/u/.rbenv/versions/2.7.0-dev/include/ruby-2.7.0/defines.h', needed by 'cparse.o'. Stop. make failed, exit code 2 Gem files will remain installed in /home/u/.rbenv/versions/2.7.0-dev/lib/ruby/gems/2.7.0/gems/racc-1.4.14 for inspection. Results logged to /home/u/.rbenv/versions/2.7.0-dev/lib/ruby/gems/2.7.0/extensions/x86_64-linux/2.7.0-static/racc-1.4.14/gem_make.out An error occurred while installing racc (1.4.14), and Bundler cannot continue. Make sure that `gem install racc -v '1.4.14' --source 'https://rubygems.org/'` succeeds before bundling. In Gemfile: racc ```
2019-03-07 06:29:26 -05:00
racc (1.4.15)
bundle update resque-scheduler to latest version Resque 2.0 includes grammar fixes for warnings tickled by our tests. Updating resque-scheduler also requires and updates resque to version 2.0. ``` $ ruby -v ruby 2.6.2p47 (2019-03-13 revision 67232) [x86_64-linux] ```
2019-05-08 08:58:20 -04:00
rack (2.0.7)
Bundle update
2019-10-10 00:48:16 -04:00
rack-cache (1.9.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
rack (>= 0.4)
Bundle update
2019-10-10 00:48:16 -04:00
rack-protection (2.0.7)
Override the github git source instead of changing manually all entries
2016-09-13 20:19:09 -04:00
rack
Make Webpacker the default JavaScript compiler for Rails 6 (#33079) * Use Webpacker by default on new apps * Stop including coffee-rails by default * Drop using a js_compressor by default * Drop extra test for coffeescript inclusion by default * Stick with skip_javascript to signify skipping webpack * Don't install a JS runtime by default any more * app/javascript will be the new default directory for JS * Make it clear that this is just for configuring the default Webpack framework setup now * Start using the Webpack tag in the default layout * Irrelevant test * jQuery is long gone * Stop having asset pipeline compile default application.js * Add rails-ujs by default to the Webpack setup * Add Active Storage JavaScript to application.js pack by default * Consistent quoting * Add Turbolinks to default pack * Add Action Cable to default pack Need some work on how to set the global consumer that channels will work with. @javan? * Require all channels by default and use a separate consumer stub * Channel generator now targets Webpack style * Update task docs to match new generator style * Use uniform import style * Drop the JS assets generator It was barely helpful as it was. It’s no longer helpful in a Webpacked world. Sayonara! * Add app/javascript to the stats directories * Simpler import style Which match the other imports. * Address test failures from dropping JS compilation (and compression) * webpacker-default: Modify `AssetsGeneratorTest` Before: ``` $ bin/test test/generators/assets_generator_test.rb Run options: --seed 46201 F Failure: AssetsGeneratorTest#test_assets [/Users/ttanimichi/ghq/github.com/ttanimichi/rails/railties/test/generators/assets_generator_test.rb:12]: Expected file "app/assets/javascripts/posts.js" to exist, but does not bin/test /Users/ttanimichi/ghq/github.com/ttanimichi/rails/railties/test/generators/assets_generator_test.rb:10 . Finished in 0.031343s, 63.8101 runs/s, 95.7152 assertions/s. 2 runs, 3 assertions, 1 failures, 0 errors, 0 skips ``` After: ``` $ bin/test test/generators/assets_generator_test.rb Run options: --seed 43571 .. Finished in 0.030370s, 65.8545 runs/s, 65.8545 assertions/s. 2 runs, 2 assertions, 0 failures, 0 errors, 0 skips ``` * webpacker-default: Modify `ChannelGeneratorTest` Before: ``` $ bin/test test/generators/channel_generator_test.rb Run options: --seed 8986 .F Failure: ChannelGeneratorTest#test_channel_with_multiple_actions_is_created [/Users/ttanimichi/ghq/github.com/ttanimichi/rails/railties/test/generators/channel_generator_test.rb:43]: Expected file "app/assets/javascripts/channels/chat.js" to exist, but does not bin/test /Users/ttanimichi/ghq/github.com/ttanimichi/rails/railties/test/generators/channel_generator_test.rb:34 .F Failure: ChannelGeneratorTest#test_channel_is_created [/Users/ttanimichi/ghq/github.com/ttanimichi/rails/railties/test/generators/channel_generator_test.rb:29]: Expected file "app/assets/javascripts/channels/chat.js" to exist, but does not bin/test /Users/ttanimichi/ghq/github.com/ttanimichi/rails/railties/test/generators/channel_generator_test.rb:22 E Error: ChannelGeneratorTest#test_cable_js_is_created_if_not_present_already: Errno::ENOENT: No such file or directory @ apply2files - /Users/ttanimichi/ghq/github.com/ttanimichi/rails/railties/test/fixtures/tmp/app/assets/javascripts/cable.js bin/test /Users/ttanimichi/ghq/github.com/ttanimichi/rails/railties/test/generators/channel_generator_test.rb:60 F Failure: ChannelGeneratorTest#test_channel_suffix_is_not_duplicated [/Users/ttanimichi/ghq/github.com/ttanimichi/rails/railties/test/generators/channel_generator_test.rb:87]: Expected file "app/assets/javascripts/channels/chat.js" to exist, but does not bin/test /Users/ttanimichi/ghq/github.com/ttanimichi/rails/railties/test/generators/channel_generator_test.rb:80 F Failure: ChannelGeneratorTest#test_channel_on_revoke [/Users/ttanimichi/ghq/github.com/ttanimichi/rails/railties/test/generators/channel_generator_test.rb:77]: Expected file "app/assets/javascripts/cable.js" to exist, but does not bin/test /Users/ttanimichi/ghq/github.com/ttanimichi/rails/railties/test/generators/channel_generator_test.rb:68 Finished in 0.064384s, 108.7227 runs/s, 481.4861 assertions/s. 7 runs, 31 assertions, 4 failures, 1 errors, 0 skips ``` After: ``` $ bin/test test/generators/channel_generator_test.rb Run options: --seed 44857 ....... Finished in 0.060243s, 116.1961 runs/s, 697.1764 assertions/s. 7 runs, 42 assertions, 0 failures, 0 errors, 0 skips ``` * Fix shared generator tests. * webpacker-default: Modify `ControllerGeneratorTest` The JS assets generator was dropped. ref. https://github.com/rails/rails/commit/46215b179483d3e4d264555f5a4952f43eb8142a * Revert "Simpler import style". It's currently failing with an error of "TypeError: undefined is not an object (evaluating '__WEBPACK_IMPORTED_MODULE_2_activestorage___default.a.start')". Waiting for @javan to have a look. This reverts commit 5d3ebb71059f635d3756cbda4ab9752027e09256. * require webpacker in test app * Add webpacker without making the build hang/timeout. (#33640) * use yarn workspaces to allow for installing unreleased packages and only generate js/bootsnap when required * no longer need to have webpacker in env templates as webpacker moved this config to yml file * Fix rubocop violation * Got the test passing for the running scaffold * update expected lines of code * update middleware tests to account for webpacker * disable js in plugins be default to get the tests passing (#34009) * clear codeclimate report issues * Anything newer than currently released is good * Use Webpacker development version during development of Rails * Edge should get development webpacker as well * Add changelog entry for Webpacker change
2018-10-01 01:31:21 -04:00
rack-proxy (0.6.5)
rack
Upgrade all the gems
2018-09-05 17:41:31 -04:00
rack-test (1.1.0)
Update rack-test dependency constraint
2017-07-19 19:04:53 -04:00
rack (>= 1.0, < 3)
rails-dom-testing (2.0.3)
activesupport (>= 4.2.0)
nokogiri (>= 1.6)
Bundle update
2019-10-10 00:48:16 -04:00
rails-html-sanitizer (1.3.0)
loofah (~> 2.3)
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-22 18:54:23 -05:00
rainbow (3.0.0)
Bundle update
2019-10-10 00:48:16 -04:00
rake (13.0.0)
Bundle update
2018-05-30 13:49:55 -04:00
rb-fsevent (0.10.3)
Switch to released rb-inotify 0.10.0 It contains guard/rb-inotify#79, which is what we were waiting for.
2018-12-30 09:05:30 -05:00
rb-inotify (0.10.0)
ffi (~> 1.0)
Bundle update
2019-10-10 00:48:16 -04:00
rdoc (6.2.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 update
2019-10-10 00:48:16 -04:00
redis (4.1.3)
Use released `redis-namespace` instead of master version The `redis-namespace` 1.6.0 includes redis-rb 4.0 support.
2017-11-08 03:08:23 -05:00
redis-namespace (1.6.0)
redis (>= 3.0.4)
Stop setting a default Capybara app host It's intended not to be set if Capybara starts the app server itself. Base Rails-generated URLs off of Capybara.current_session.server_url instead.
2019-07-24 22:19:21 -04:00
regexp_parser (1.6.0)
Resolve gemspec typo
2017-07-31 16:55:55 -04:00
representable (3.0.4)
declarative (< 0.1.0)
declarative-option (< 0.2.0)
uber (< 0.2.0)
bundle update resque-scheduler to latest version Resque 2.0 includes grammar fixes for warnings tickled by our tests. Updating resque-scheduler also requires and updates resque to version 2.0. ``` $ ruby -v ruby 2.6.2p47 (2019-03-13 revision 67232) [x86_64-linux] ```
2019-05-08 08:58:20 -04:00
resque (2.0.0)
Use released resque
2017-02-10 01:31:41 -05:00
mono_logger (~> 1.0)
multi_json (~> 1.0)
bundle update resque-scheduler to latest version Resque 2.0 includes grammar fixes for warnings tickled by our tests. Updating resque-scheduler also requires and updates resque to version 2.0. ``` $ ruby -v ruby 2.6.2p47 (2019-03-13 revision 67232) [x86_64-linux] ```
2019-05-08 08:58:20 -04:00
redis-namespace (~> 1.6)
Use released resque
2017-02-10 01:31:41 -05:00
sinatra (>= 0.9.2)
vegas (~> 0.1.2)
bundle update resque-scheduler to latest version Resque 2.0 includes grammar fixes for warnings tickled by our tests. Updating resque-scheduler also requires and updates resque to version 2.0. ``` $ ruby -v ruby 2.6.2p47 (2019-03-13 revision 67232) [x86_64-linux] ```
2019-05-08 08:58:20 -04:00
resque-scheduler (4.4.0)
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-13 17:49:08 -05:00
mono_logger (~> 1.0)
bundle update resque-scheduler to latest version Resque 2.0 includes grammar fixes for warnings tickled by our tests. Updating resque-scheduler also requires and updates resque to version 2.0. ``` $ ruby -v ruby 2.6.2p47 (2019-03-13 revision 67232) [x86_64-linux] ```
2019-05-08 08:58:20 -04:00
redis (>= 3.3)
resque (>= 1.26)
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-13 17:49:08 -05:00
rufus-scheduler (~> 3.2)
Upgrade all the gems
2018-09-05 17:41:31 -04:00
retriable (3.1.2)
Bundle update
2019-10-10 00:48:16 -04:00
rubocop (0.75.0)
Bump RuboCop to 0.58.2 ## Summary RuboCop 0.58.2 was released. https://github.com/rubocop-hq/rubocop/releases/tag/v0.58.2 And rubocop-0-58 channel is available in Code Climate. https://github.com/codeclimate/codeclimate/releases/tag/v0.76.0 https://github.com/codeclimate/codeclimate/commit/38f21f0 In addition, the following changes are made in this PR. - Replace Custom cops with Rails cops - Add jaro_winkler gem to Gemfile.lock ### Replace Custom cops with Rails cops These are compatible replacements. - Replace `CustomCops/AssertNot` cop with `Rails/AssertNot` cop. - Replace `CustomCops/RefuteNot` cop with `Rails/RefuteMethods` cop. With this replacement, it was decided to use cop of RuboCop itself. It removes the code related to CustomCops accordingly. ### Add jaro_winkler gem to Gemfile.lock Since RuboCop 0.57.0 depends on jaro_winkler gem, it has been added to Gemfile.lock.
2018-07-02 23:11:28 -04:00
jaro_winkler (~> 1.5.1)
Bump rubocop and dependent gem versions
2017-05-24 02:20:00 -04:00
parallel (~> 1.10)
Bump rubocop to 0.71
2019-06-06 01:38:19 -04:00
parser (>= 2.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-22 18:54:23 -05:00
rainbow (>= 2.2.2, < 4.0)
Add rubocop to Gemfile
2016-11-27 22:12:33 -05:00
ruby-progressbar (~> 1.7)
Bump rubocop to 0.71
2019-06-06 01:38:19 -04:00
unicode-display_width (>= 1.4.0, < 1.7)
Bundle update
2019-10-10 00:48:16 -04:00
rubocop-performance (1.5.0)
rubocop (>= 0.71.0)
rubocop-rails (2.3.2)
rack (>= 1.1)
rubocop (>= 0.72.0)
Bump rubocop to 0.71
2019-06-06 01:38:19 -04:00
ruby-progressbar (1.10.1)
Bundle update
2019-10-10 00:48:16 -04:00
ruby-vips (2.0.15)
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-05 19:48:29 -04:00
ffi (~> 1.9)
bundle update
2016-12-26 07:46:01 -05:00
ruby_dep (1.5.0)
Bundle update
2019-10-10 00:48:16 -04:00
rubyzip (2.0.0)
bundle update resque-scheduler to latest version Resque 2.0 includes grammar fixes for warnings tickled by our tests. Updating resque-scheduler also requires and updates resque to version 2.0. ``` $ ruby -v ruby 2.6.2p47 (2019-03-13 revision 67232) [x86_64-linux] ```
2019-05-08 08:58:20 -04:00
rufus-scheduler (3.6.0)
fugit (~> 1.1, >= 1.1.6)
Bundle update
2019-10-10 00:48:16 -04:00
safe_yaml (1.0.5)
Support Rails with sass-rails 6
2019-08-16 16:13:24 -04:00
sass-rails (6.0.0)
sassc-rails (~> 2.1, >= 2.1.1)
Update sassc to the latest version ``` /home/u/.rbenv/versions/2.7.0-dev/lib/ruby/gems/2.7.0/gems/ffi-1.11.1/lib/ffi/library.rb:275: warning: method redefined; discarding old _context_get_included_files /home/u/.rbenv/versions/2.7.0-dev/lib/ruby/gems/2.7.0/gems/ffi-1.11.1/lib/ffi/library.rb:275: warning: method redefined; discarding old list_get_length /home/u/.rbenv/versions/2.7.0-dev/lib/ruby/gems/2.7.0/gems/ffi-1.11.1/lib/ffi/library.rb:275: warning: method redefined; discarding old list_get_value /home/u/.rbenv/versions/2.7.0-dev/lib/ruby/gems/2.7.0/gems/ffi-1.11.1/lib/ffi/library.rb:275: warning: method redefined; discarding old _make_data_context /home/u/.rbenv/versions/2.7.0-dev/lib/ruby/gems/2.7.0/gems/ffi-1.11.1/lib/ffi/library.rb:275: warning: method redefined; discarding old version ``` Were fixed in sassc 2.2.1.
2019-10-08 03:58:32 -04:00
sassc (2.2.1)
ffi (~> 1.9)
sassc (2.2.1-x64-mingw32)
ffi (~> 1.9)
sassc (2.2.1-x86-mingw32)
Support Rails with sass-rails 6
2019-08-16 16:13:24 -04:00
ffi (~> 1.9)
sassc-rails (2.1.2)
railties (>= 4.0.0)
sassc (>= 2.0)
sprockets (> 3.0)
sprockets-rails
tilt
Refer to a stable release of SDoc
2018-02-06 13:49:15 -05:00
sdoc (1.0.0)
rdoc (>= 5.0)
Bundle update
2019-10-10 00:48:16 -04:00
selenium-webdriver (3.142.6)
childprocess (>= 0.5, < 4.0)
rubyzip (>= 1.2.2)
sequel (5.25.0)
Upgrade all the gems
2018-09-05 17:41:31 -04:00
serverengine (2.0.7)
Track Gemfile.lock at the repository The main reason is to make bisect easier. In some points, we have a lot of git dependencies. Since we don't have the information of which commit we are referring to, bundler get the latest commit of the master branch of the dependency. This sometimes returns a version that is not compatible with Rails anymore, making the tests fail and the harder to identify the commit that introduced a bug. Also this will make sure that a contributor will always get a set of dependencies that are passing with our tests. In our CI server we delete the lock file to make sure we are always testing against the newest release of our dependencies.
2015-02-18 11:30:25 -05:00
sigdump (~> 0.2.2)
Bundle update
2019-10-10 00:48:16 -04:00
sidekiq (6.0.1)
Fix Active Job Sidekiq integration tests The `Sidekiq::Logging` module was removed in Sidekiq 6.0 in favour of `Sidekiq.logger=`. https://github.com/mperham/sidekiq/wiki/Logging#api-changes > The old Sidekiq::Logging class was removed in Sidekiq 6.0. You should > not be accessing any Sidekiq internal classes to use the logger. Use > `logger` directly in your Worker or use `Sidekiq.logger` elsewhere.
2019-09-01 17:31:21 -04:00
connection_pool (>= 2.2.2)
rack (>= 2.0.0)
rack-protection (>= 2.0.0)
redis (>= 4.1.0)
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)
bundle update
2018-11-09 17:21:08 -05:00
signet (0.11.0)
Resolve gemspec typo
2017-07-31 16:55:55 -04: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-28 23:08:33 -05:00
jwt (>= 1.5, < 3.0)
Resolve gemspec typo
2017-07-31 16:55:55 -04:00
multi_json (~> 1.10)
Bundle update
2019-10-10 00:48:16 -04:00
sinatra (2.0.7)
Update rack-test dependency constraint
2017-07-19 19:04:53 -04:00
mustermann (~> 1.0)
rack (~> 2.0)
Bundle update
2019-10-10 00:48:16 -04:00
rack-protection (= 2.0.7)
Update rack-test dependency constraint
2017-07-19 19:04:53 -04:00
tilt (~> 2.0)
Update Sneakers to the latest version Sneakers 2.11.0 has a more recent Bunny dependency which squashes some Ruby 2.6 warnings tickled by ActiveJob tests.
2019-01-29 17:39:43 -05:00
sneakers (2.11.0)
bunny (~> 2.12)
Bundle update
2018-05-30 13:49:55 -04:00
concurrent-ruby (~> 1.0)
Update Sneakers to the latest version Sneakers 2.11.0 has a more recent Bunny dependency which squashes some Ruby 2.6 warnings tickled by ActiveJob tests.
2019-01-29 17:39:43 -05:00
rake
Bundle update
2018-05-30 13:49:55 -04:00
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-18 11:30:25 -05:00
thor
Bundle update
2019-10-10 00:48:16 -04:00
sprockets (4.0.0)
Use sprockets 3 in the Rails 5 release
2015-12-16 13:30:58 -05:00
concurrent-ruby (~> 1.0)
rack (> 1, < 3)
Update rack-test dependency constraint
2017-07-19 19:04:53 -04:00
sprockets-export (1.0.0)
Bundle update
2018-05-30 13:49:55 -04:00
sprockets-rails (3.2.1)
Use release sprockets-rails
2015-12-17 15:22:58 -05:00
actionpack (>= 4.0)
activesupport (>= 4.0)
sprockets (>= 3.0.0)
Bundle update
2019-10-10 00:48:16 -04:00
sqlite3 (1.4.1)
stackprof (0.2.13)
sucker_punch (2.1.2)
Upgrade all the gems
2018-09-05 17:41:31 -04:00
concurrent-ruby (~> 1.0)
Update rack-test dependency constraint
2017-07-19 19:04:53 -04:00
thin (1.7.2)
Add accidentally removed dependency in Gemfile.lock Follow up to ca0b6d0d416776655ed7516ac18f126fbde5315a.
2016-08-03 18:55:47 -04:00
daemons (~> 1.0, >= 1.0.9)
eventmachine (~> 1.0, >= 1.0.4)
rack (>= 1, < 3)
Make sure we are using a working version of thor locally
2018-11-09 22:00:58 -05:00
thor (0.20.3)
Bump the bundled GlobalID version.
2017-04-16 11:40:00 -04: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 07:34:43 -04:00
thread_safe (0.3.6-java)
Bundle update
2019-10-10 00:48:16 -04:00
tilt (2.0.10)
turbolinks (5.2.1)
Upgrade all the gems
2018-09-05 17:41:31 -04:00
turbolinks-source (~> 5.2)
turbolinks-source (5.2.0)
Update et-orbi to latest version avoids `warning: assigned but unused variable - tu`.
2018-05-28 02:36:49 -04: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-18 11:30:25 -05:00
thread_safe (~> 0.1)
Bundle update
2019-10-10 00:48:16 -04:00
tzinfo-data (1.2019.3)
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)
Resolve gemspec typo
2017-07-31 16:55:55 -04:00
uber (0.1.0)
Bundle update
2019-10-10 00:48:16 -04:00
uglifier (4.2.0)
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)
Bump rubocop to 0.71
2019-06-06 01:38:19 -04:00
unicode-display_width (1.6.0)
Bundle update
2018-05-30 13:49:55 -04:00
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-18 11:30:25 -05:00
vegas (0.1.11)
rack (>= 1.0.0)
Upgrade all the gems
2018-09-05 17:41:31 -04:00
w3c_validators (1.3.4)
Update rack-test dependency constraint
2017-07-19 19:04:53 -04:00
json (>= 1.8)
bundle update
2016-12-26 07:46:01 -05: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-21 12:54:54 -04:00
wdm (0.1.1)
Bundle update
2019-10-10 00:48:16 -04:00
webdrivers (4.1.3)
Use webdrivers instead of chromedriver-helper for AV UJS tests
2019-03-24 17:05:30 -04:00
nokogiri (~> 1.6)
Bundle update
2019-10-10 00:48:16 -04:00
rubyzip (>= 1.3.0)
selenium-webdriver (>= 3.0, < 4.0)
webmock (3.7.6)
Extract ActionMailbox::PostfixRelayer
2018-11-25 14:30:05 -05:00
addressable (>= 2.3.6)
crack (>= 0.3.2)
Bundle update
2019-10-10 00:48:16 -04:00
hashdiff (>= 0.4.0, < 2.0.0)
webpacker (4.0.7)
Use released webpacker
2019-01-17 17:21:09 -05:00
activesupport (>= 4.2)
rack-proxy (>= 0.6.1)
railties (>= 4.2)
Bundle update
2018-05-30 13:49:55 -04:00
websocket (1.2.8)
Bundle update
2019-10-10 00:48:16 -04:00
websocket-driver (0.7.1)
Initial stab at adding Action Cable to rails/master
2015-12-14 10:38:37 -05:00
websocket-extensions (>= 0.1.0)
Bundle update
2019-10-10 00:48:16 -04:00
websocket-driver (0.7.1-java)
Rename methods and update docs This is a minor update to the named methods for the following: - s/desired_capabilities/capabilities - s/driver_options/capabilities Since they are all the same thing we should keep the name the same throughout the feature. Updated docs to match / be a little bit clearer Also updated the Gemfile for selenium-webdriver.
2019-01-29 09:01:58 -05:00
websocket-extensions (>= 0.1.0)
Bundle update
2019-10-10 00:48:16 -04:00
websocket-extensions (0.1.4)
bundle update
2018-11-09 17:21:08 -05:00
xpath (3.2.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 07:55:34 -04:00
nokogiri (~> 1.8)
bump Zeitwerk to 2.2
2019-10-09 15:28:35 -04:00
zeitwerk (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
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 07:34:43 -04: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-18 11:30:25 -05: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-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)
Use v3 of the AWS SDK
2017-09-09 23:22:10 -04:00
aws-sdk-s3
Accept inbound emails from a variety of ingresses
2018-10-06 22:02:08 -04:00
aws-sdk-sns
Update azure-storage gem to latest version
2019-08-06 12:25:39 -04:00
azure-storage-blob
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
Bump bootsnap to a version with disables iseq_cache for Ruby 2.5 - Refs https://github.com/Shopify/bootsnap/pull/257
2019-04-26 03:25:28 -04:00
bootsnap (>= 1.4.4)
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
Stop setting a default Capybara app host It's intended not to be set if Capybara starts the app server itself. Base Rails-generated URLs off of Capybara.current_session.server_url instead.
2019-07-24 22:19:21 -04:00
capybara (>= 3.26)
Support for connection pooling on mem cache store
2017-12-12 19:11:47 -05: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 03:52:10 -04: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-29 16:57:28 -05:00
delayed_job
delayed_job and delayed_job_active_record gems with AR5 support are available
2017-01-28 19:05:06 -05:00
delayed_job_active_record
Support streaming downloads from Google Cloud Storage
2018-05-01 23:20:56 -04: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 10:00:00 -05: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-05 19:48:29 -04: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-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)
Add minitest-bisect as part of the gemfile
2016-07-12 02:06:25 -04:00
minitest-bisect
Output junit format test report
2019-03-24 13:59:28 -04:00
minitest-reporters
Add test retries for railties
2018-10-10 18:33:09 -04:00
minitest-retry
Required mysql2 gem 0.5.0 This follows up #36692, `Mysql2::Error::TimeoutError` is introduced from mysql2 gem 0.5.0. https://github.com/brianmario/mysql2/pull/911
2019-09-12 22:12:41 -04:00
mysql2 (~> 0.5)
Update nokogiri version on Gemfile
2017-12-14 13:06:53 -05:00
nokogiri (>= 1.8.1)
Unlock pg verson Get a warning about `async_exec`, but it seems that build has passed through the fix of https://bitbucket.org/ged/ruby-pg/commits/be48d118eeedbf6b6a1f0aa14749ab97fc22065c.
2018-09-15 03:07:03 -04:00
pg (>= 0.18.0)
update psych gem to 3.2 stable release
2018-03-09 15:14:36 -05:00
psych (~> 3.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
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!
PhantomJS is abandoned, replace it with Selenium/Chrome headless
2017-10-19 12:01:52 -04: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-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)
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 00:54:00 -04: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 03:08:23 -05:00
redis-namespace
Use released resque
2017-02-10 01:31:41 -05: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-13 17:49:08 -05:00
resque-scheduler
update rubocop to 0.47
2017-01-16 01:34:30 -05:00
rubocop (>= 0.47)
Bump RuboCop to 0.67.2 Performance cops will be extracted from RuboCop to RuboCop Performance when next RuboCop 0.68 will be released. https://github.com/rubocop-hq/rubocop/issues/5977 RuboCop 0.67 is its transition period. Since rails/rails repository uses Performance cops, This PR added rubocop-performance gem to Gemfile. And this PR fixes some offenses using the following auto-correct. ```console % bundle exec rubocop -a Offenses: activerecord/test/cases/connection_adapters/connection_handlers_multi_db_test.rb:212:26: C: [Corrected] Layout/SpaceAroundOperators: Operator = > should be surrounded by a single space. "primary" => { adapter: "sqlite3", database: "db/primary.sqlite3" } ^^ activerecord/test/cases/connection_adapters/connection_handlers_multi_db_test.rb:239:26: C: [Corrected] Layout/SpaceAroundOperators: Operator => should be surrounded by a single space. "primary" => { adapter: "sqlite3", database: "db/primary.sqlite3" } ^^ actionview/test/template/resolver_shared_tests.rb:1:1: C: [Corrected] Style/FrozenStringLiteralComment: Missing magic comment # frozen_string_literal: true. module ResolverSharedTests ^ actionview/test/template/resolver_shared_tests.rb:10:33: C: [Corrected] Layout/SpaceAroundEqualsInParameterDefault: Surrounding space missing in default value assignment. def with_file(filename, source="File at #{filename}") ^ actionview/test/template/resolver_shared_tests.rb:106:5: C: [Corrected] Rails/RefuteMethods: Prefer assert_not_same over refute_same. refute_same a, b ^^^^^^^^^^^ 2760 files inspected, 5 offenses detected, 5 offenses corrected ```
2019-04-16 04:05:50 -04:00
rubocop-performance
Bump rubocop to 0.71
2019-06-06 01:38:19 -04:00
rubocop-rails
Use released sass-rails
2017-11-14 14:42:12 -05:00
sass-rails
Refer to a stable release of SDoc
2018-02-06 13:49:15 -05:00
sdoc (~> 1.0)
Bump minimum selenium-webdriver version Since #36424, we need an newer version in order to pass.
2019-07-04 19:17:39 -04:00
selenium-webdriver (>= 3.141.592)
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
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 07:49:55 -04:00
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
Use `execute_batch2` rather than `execute_batch` to fix performance regression for fixture loading d8d6bd5 makes fixture loading to bulk statements by using `execute_batch` for sqlite3 adapter. But `execute_batch` is slower and it caused the performance regression for fixture loading. In sqlite3 1.4.0, it have new batch method `execute_batch2`. I've confirmed `execute_batch2` is extremely faster than `execute_batch`. So I think it is worth to upgrade sqlite3 to 1.4.0 to use that method. Before: ``` % ARCONN=sqlite3 bundle exec ruby -w -Itest test/cases/associations/eager_test.rb -n test_eager_loading_too_may_ids Using sqlite3 Run options: -n test_eager_loading_too_may_ids --seed 35790 # Running: . Finished in 202.437406s, 0.0049 runs/s, 0.0049 assertions/s. 1 runs, 1 assertions, 0 failures, 0 errors, 0 skips ARCONN=sqlite3 bundle exec ruby -w -Itest -n test_eager_loading_too_may_ids 142.57s user 60.83s system 98% cpu 3:27.08 total ``` After: ``` % ARCONN=sqlite3 bundle exec ruby -w -Itest test/cases/associations/eager_test.rb -n test_eager_loading_too_may_ids Using sqlite3 Run options: -n test_eager_loading_too_may_ids --seed 16649 # Running: . Finished in 8.471032s, 0.1180 runs/s, 0.1180 assertions/s. 1 runs, 1 assertions, 0 failures, 0 errors, 0 skips ARCONN=sqlite3 bundle exec ruby -w -Itest -n test_eager_loading_too_may_ids 10.71s user 1.36s system 95% cpu 12.672 total ```
2019-04-03 14:19:08 -04:00
sqlite3 (~> 1.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
stackprof
Update ActiveJob adapter for sucker_punch 2.0 This PR includes two changes for 2.0.0: - Breaking API change around `async.perform` --> `perform_async` - New addition of `perform_in`, which now allows end users of the adapter to use the `enqueued_at` public API method.
2016-01-27 11:29:18 -05:00
sucker_punch
Update 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 webdrivers instead of chromedriver-helper for AV UJS tests
2019-03-24 17:05:30 -04:00
webdrivers
Extract ActionMailbox::PostfixRelayer
2018-11-25 14:30:05 -05:00
webmock
Don't lock the webpacker gem by its patch version
2019-03-08 18:59:36 -05:00
webpacker (~> 4.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
Zeitwerk integration
2019-02-11 15:44:25 -05:00
1.17.3
Copy permalink