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

613 lines
15 KiB
Plaintext
Raw Normal View History

Use mysql2 from git to fix warnings with Ruby 2.7 Closes #40272.
2020-09-23 03:40:47 +08:00
GIT
remote: https://github.com/brianmario/mysql2.git
Update development gems
2021-06-09 07:27:47 +08:00
revision: 7f4e844fccf6afa888d0bd108d4707a2a7784484
Use mysql2 from git to fix warnings with Ruby 2.7 Closes #40272.
2020-09-23 03:40:47 +08:00
specs:
mysql2 (0.5.3)
Use queue_classic branch which works on psql 14 This fixes the failing CI for ActiveJob. This uses my fork, we can switch back when the following PR is merged: https://github.com/QueueClassic/queue_classic/pull/334
2021-10-05 04:51:47 +08:00
GIT
remote: https://github.com/jhawthorn/queue_classic.git
revision: dbfee9bda71020b8f11ae8d9b85932462b7fbee0
branch: fix-connection-pg-14
specs:
queue_classic (4.0.0.pre.alpha1)
pg (>= 0.17, < 2.0)
Use a branch of websocket-client-simple, to work around read/close race
2016-10-06 09:11:18 +08:00
GIT
remote: https://github.com/matthewd/websocket-client-simple.git
revision: e161305f1a466b9398d86df3b1731b03362da91b
branch: close-race
specs:
websocket-client-simple (0.3.0)
event_emitter
websocket
Track Gemfile.lock at the repository The main reason is to make bisect easier. In some points, we have a lot of git dependencies. Since we don't have the information of which commit we are referring to, bundler get the latest commit of the master branch of the dependency. This sometimes returns a version that is not compatible with Rails anymore, making the tests fail and the harder to identify the commit that introduced a bug. Also this will make sure that a contributor will always get a set of dependencies that are passing with our tests. In our CI server we delete the lock file to make sure we are always testing against the newest release of our dependencies.
2015-02-19 00:30:25 +08:00
PATH
remote: .
specs:
Start Rails 7.1 development
2021-12-07 23:52:30 +08:00
actioncable (7.1.0.alpha)
actionpack (= 7.1.0.alpha)
activesupport (= 7.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-29 11:45:39 +08:00
nio4r (~> 2.0)
Update Gemfile.lock to reflect websocket-driver 0.7.0 Follow up to e1473e0cbfbd97eeea2bc6eefd73bec0d4863359
2018-01-19 06:50:50 +08:00
websocket-driver (>= 0.6.1)
Start Rails 7.1 development
2021-12-07 23:52:30 +08:00
actionmailbox (7.1.0.alpha)
actionpack (= 7.1.0.alpha)
activejob (= 7.1.0.alpha)
activerecord (= 7.1.0.alpha)
activestorage (= 7.1.0.alpha)
activesupport (= 7.1.0.alpha)
Import Action Mailbox
2018-12-25 04:16:22 +08:00
mail (>= 2.7.1)
Start Rails 7.1 development
2021-12-07 23:52:30 +08:00
actionmailer (7.1.0.alpha)
actionpack (= 7.1.0.alpha)
actionview (= 7.1.0.alpha)
activejob (= 7.1.0.alpha)
activesupport (= 7.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-19 00:30:25 +08:00
mail (~> 2.5, >= 2.5.4)
Fix Gemfile.lock by updating rails-dom-testing - Followup of https://github.com/rails/rails/pull/24946.
2016-05-10 13:13:56 +08:00
rails-dom-testing (~> 2.0)
Start Rails 7.1 development
2021-12-07 23:52:30 +08:00
actionpack (7.1.0.alpha)
actionview (= 7.1.0.alpha)
activesupport (= 7.1.0.alpha)
Bump rack to remove ssl? override Rack 2.2+ already understands "wss" as being "ssl", so bumping the requirement lets us remove this override and call to super.
2021-05-25 09:36:35 +08:00
rack (~> 2.0, >= 2.2.0)
Update rack-test dependency constraint
2017-07-20 07:04:53 +08:00
rack-test (>= 0.6.3)
Fix Gemfile.lock by updating rails-dom-testing - Followup of https://github.com/rails/rails/pull/24946.
2016-05-10 13:13:56 +08:00
rails-dom-testing (~> 2.0)
Rails HTML sanitizer gemfile lock changes on bundle install.
2019-08-09 23:40:59 +08:00
rails-html-sanitizer (~> 1.0, >= 1.2.0)
Start Rails 7.1 development
2021-12-07 23:52:30 +08:00
actiontext (7.1.0.alpha)
actionpack (= 7.1.0.alpha)
activerecord (= 7.1.0.alpha)
activestorage (= 7.1.0.alpha)
activesupport (= 7.1.0.alpha)
Use `ActiveRecord::FixtureSet.signed_global_id` defined by the globalid gem Also make explicit that actiontext depends on the globalid gem.
2021-11-25 06:33:45 +08:00
globalid (>= 0.6.0)
Import Action Text
2019-01-05 08:43:11 +08:00
nokogiri (>= 1.8.5)
Start Rails 7.1 development
2021-12-07 23:52:30 +08:00
actionview (7.1.0.alpha)
activesupport (= 7.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-19 00:30:25 +08:00
builder (~> 3.1)
Change ActionView ERB Handler from Erubis to Erubi Erubi offers the following advantages for Rails: * Works with ruby's --enable-frozen-string-literal option * Has 88% smaller memory footprint * Does no freedom patching (Erubis adds a method to Kernel) * Has simpler internals (1 file, <150 lines of code) * Has an open development model (Erubis doesn't have a public source control repository or bug tracker) * Is not dead (Erubis hasn't been updated since 2011) Erubi is a simplified fork of Erubis that contains just the parts that are generally needed (which includes the parts that Rails uses). The only intentional difference in behavior is that it does not include support for <%=== tags for debug output. That could be added to the ActionView ERB handler if it is desired. The Erubis template handler remains in a deprecated state so that code that accesses it directly does not break. It can be removed after Rails 5.1.
2017-01-21 07:02:34 +08:00
erubi (~> 1.4)
Fix Gemfile.lock by updating rails-dom-testing - Followup of https://github.com/rails/rails/pull/24946.
2016-05-10 13:13:56 +08:00
rails-dom-testing (~> 2.0)
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-09 06:07:45 +08:00
rails-html-sanitizer (~> 1.1, >= 1.2.0)
Start Rails 7.1 development
2021-12-07 23:52:30 +08:00
activejob (7.1.0.alpha)
activesupport (= 7.1.0.alpha)
Use released GlobalID now that it provides URI::GID::MissingModelIdError for Active Job
2015-12-18 08:20:19 +08:00
globalid (>= 0.3.6)
Start Rails 7.1 development
2021-12-07 23:52:30 +08:00
activemodel (7.1.0.alpha)
activesupport (= 7.1.0.alpha)
activerecord (7.1.0.alpha)
activemodel (= 7.1.0.alpha)
activesupport (= 7.1.0.alpha)
activestorage (7.1.0.alpha)
actionpack (= 7.1.0.alpha)
activejob (= 7.1.0.alpha)
activerecord (= 7.1.0.alpha)
activesupport (= 7.1.0.alpha)
Allow Marcel to be released following semver
2021-09-21 05:19:28 +08:00
marcel (~> 1.0)
Active Storage: upgrade to mini_mime 1.1.0 Fix validating uppercase variant formats. Closes #41796.
2021-04-05 10:44:02 +08:00
mini_mime (>= 1.1.0)
Start Rails 7.1 development
2021-12-07 23:52:30 +08:00
activesupport (7.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-03 06:04:59 +08:00
concurrent-ruby (~> 1.0, >= 1.0.2)
Add I18n to eager_load_namespaces
2019-11-22 03:59:22 +08:00
i18n (>= 1.6, < 2)
Fix minitest version constraints in Gemfile.lock Followup to e803ab6e80e2fc0b772e2135ce85111cdce23e2f. The dependencies of each entry are alphasorted, and minitest-server's version constraint is still pessimistic.
2020-06-01 18:59:27 +08:00
minitest (>= 5.1)
Update to TZInfo v2.0.0 Co-authored-by: Jared Beck <jared@jaredbeck.com> Co-authored-by: Jonathan Hefner <jonathan@hefner.pro>
2017-12-29 20:47:10 +08:00
tzinfo (~> 2.0)
Start Rails 7.1 development
2021-12-07 23:52:30 +08:00
rails (7.1.0.alpha)
actioncable (= 7.1.0.alpha)
actionmailbox (= 7.1.0.alpha)
actionmailer (= 7.1.0.alpha)
actionpack (= 7.1.0.alpha)
actiontext (= 7.1.0.alpha)
actionview (= 7.1.0.alpha)
activejob (= 7.1.0.alpha)
activemodel (= 7.1.0.alpha)
activerecord (= 7.1.0.alpha)
activestorage (= 7.1.0.alpha)
activesupport (= 7.1.0.alpha)
Update Gemfile.lock
2020-08-18 17:14:00 +08:00
bundler (>= 1.15.0)
Start Rails 7.1 development
2021-12-07 23:52:30 +08:00
railties (= 7.1.0.alpha)
railties (7.1.0.alpha)
actionpack (= 7.1.0.alpha)
activesupport (= 7.1.0.alpha)
method_source needs to be a hard dependency on railties
2015-03-05 22:58:17 +08:00
method_source
Fix the development container to set the right permissions to bundler
2021-10-13 06:16:38 +08:00
rake (>= 12.2)
Leverage new :env option for Thor::Actions#run Follow-up to #34980. Also, refactor tests to be less brittle.
2019-12-16 02:58:07 +08:00
thor (~> 1.0)
Relax dependency on Zeitwerk 2.5
2021-10-22 02:30:36 +08:00
zeitwerk (~> 2.5)
Track Gemfile.lock at the repository The main reason is to make bisect easier. In some points, we have a lot of git dependencies. Since we don't have the information of which commit we are referring to, bundler get the latest commit of the master branch of the dependency. This sometimes returns a version that is not compatible with Rails anymore, making the tests fail and the harder to identify the commit that introduced a bug. Also this will make sure that a contributor will always get a set of dependencies that are passing with our tests. In our CI server we delete the lock file to make sure we are always testing against the newest release of our dependencies.
2015-02-19 00:30:25 +08:00
GEM
remote: https://rubygems.org/
specs:
Upgrade capybara to work with Ruby 3.1 and earlier
2021-12-09 05:44:11 +08:00
addressable (2.8.0)
Bundle update
2019-10-10 12:48:16 +08:00
public_suffix (>= 2.0.2, < 5.0)
Upgrade all the gems
2020-11-04 14:39:41 +08:00
amq-protocol (2.3.2)
Upgrade the development Gemfile.lock
2021-04-14 02:18:28 +08:00
ast (2.4.2)
aws-eventstream (1.1.1)
Upgrade development gems
2021-06-18 04:26:38 +08:00
aws-partitions (1.469.0)
aws-sdk-core (3.114.3)
Upgrade all the gems
2020-11-04 14:39:41 +08:00
aws-eventstream (~> 1, >= 1.0.2)
Fix test with new capybara
2019-12-28 02:30:45 +08:00
aws-partitions (~> 1, >= 1.239.0)
Bundle update
2019-10-10 12:48:16 +08:00
aws-sigv4 (~> 1.1)
Resolve gemspec typo
2017-08-01 04:55:55 +08:00
jmespath (~> 1.0)
Upgrade development gems
2021-06-18 04:26:38 +08:00
aws-sdk-kms (1.44.0)
Upgrade the development Gemfile.lock
2021-04-14 02:18:28 +08:00
aws-sdk-core (~> 3, >= 3.112.0)
Bundle update
2019-10-10 12:48:16 +08:00
aws-sigv4 (~> 1.1)
Upgrade development gems
2021-06-18 04:26:38 +08:00
aws-sdk-s3 (1.96.1)
Upgrade the development Gemfile.lock
2021-04-14 02:18:28 +08:00
aws-sdk-core (~> 3, >= 3.112.0)
Use v3 of the AWS SDK
2017-09-10 11:22:10 +08:00
aws-sdk-kms (~> 1)
Bundle update
2019-10-10 12:48:16 +08:00
aws-sigv4 (~> 1.1)
Update development gems
2021-06-09 07:27:47 +08:00
aws-sdk-sns (1.41.0)
Upgrade the development Gemfile.lock
2021-04-14 02:18:28 +08:00
aws-sdk-core (~> 3, >= 3.112.0)
Bundle update
2019-10-10 12:48:16 +08:00
aws-sigv4 (~> 1.1)
Upgrade the development Gemfile.lock
2021-04-14 02:18:28 +08:00
aws-sigv4 (1.2.3)
Upgrade all the gems
2020-11-04 14:39:41 +08:00
aws-eventstream (~> 1, >= 1.0.2)
Upgrade all the gems to make sure we are testing with the latest versions locally
2021-01-22 05:22:41 +08:00
azure-storage-blob (2.0.1)
Unlock `azure-storage-blob` version to use version 2.0 `azure-storage-blob` 2.0.0 has been released. https://rubygems.org/gems/azure-storage-blob/versions/2.0.0 According to this commit and changelog, `azure-storage-blob` 1.1.0 did not support Ruby 2.6 and higher. As of right now, Rails master branch should support Ruby 2.5.0, 2.6.0 and 2.7.0 then it should be appropriate to unlock `azure-storage-blob` version. https://github.com/Azure/azure-storage-ruby/commit/252e3f06a5cf2e2583302bfefa95d8b25818a44f This commit addresses this following error: ```ruby % cd activestorage % bundle exec rake test Traceback (most recent call last): 14: from /Users/yahonda/.rbenv/versions/2.6.5/lib/ruby/gems/2.6.0/gems/rake-13.0.1/lib/rake/rake_test_loader.rb:5:in `<main>' 13: from /Users/yahonda/.rbenv/versions/2.6.5/lib/ruby/gems/2.6.0/gems/rake-13.0.1/lib/rake/rake_test_loader.rb:5:in `select' 12: from /Users/yahonda/.rbenv/versions/2.6.5/lib/ruby/gems/2.6.0/gems/rake-13.0.1/lib/rake/rake_test_loader.rb:17:in `block in <main>' 11: from /Users/yahonda/.rbenv/versions/2.6.5/lib/ruby/gems/2.6.0/gems/zeitwerk-2.3.0/lib/zeitwerk/kernel.rb:23:in `require' 10: from /Users/yahonda/.rbenv/versions/2.6.5/lib/ruby/gems/2.6.0/gems/zeitwerk-2.3.0/lib/zeitwerk/kernel.rb:23:in `require' 9: from /Users/yahonda/src/github.com/rails/rails/activestorage/test/service/azure_storage_service_test.rb:7:in `<top (required)>' 8: from /Users/yahonda/src/github.com/rails/rails/activestorage/test/service/azure_storage_service_test.rb:8:in `<class:AzureStorageServiceTest>' 7: from /Users/yahonda/src/github.com/rails/rails/activestorage/lib/active_storage/service.rb:51:in `configure' 6: from /Users/yahonda/src/github.com/rails/rails/activestorage/lib/active_storage/service/configurator.rb:8:in `build' 5: from /Users/yahonda/src/github.com/rails/rails/activestorage/lib/active_storage/service/configurator.rb:17:in `build' 4: from /Users/yahonda/src/github.com/rails/rails/activestorage/lib/active_storage/service/configurator.rb:30:in `resolve' 3: from /Users/yahonda/.rbenv/versions/2.6.5/lib/ruby/gems/2.6.0/gems/zeitwerk-2.3.0/lib/zeitwerk/kernel.rb:23:in `require' 2: from /Users/yahonda/.rbenv/versions/2.6.5/lib/ruby/gems/2.6.0/gems/zeitwerk-2.3.0/lib/zeitwerk/kernel.rb:23:in `require' 1: from /Users/yahonda/src/github.com/rails/rails/activestorage/lib/active_storage/service/azure_storage_service.rb:3:in `<top (required)>' /Users/yahonda/.rbenv/versions/2.6.5/lib/ruby/gems/2.6.0/gems/bundler-2.1.4/lib/bundler/rubygems_integration.rb:346:in `block (2 levels) in replace_gem': can't activate azure-storage-blob (~> 1.1), already activated azure-storage-blob-2.0.0. Make sure all dependencies are added to Gemfile. (Gem::LoadError) 11: from /Users/yahonda/.rbenv/versions/2.6.5/lib/ruby/gems/2.6.0/gems/rake-13.0.1/lib/rake/rake_test_loader.rb:5:in `<main>' 10: from /Users/yahonda/.rbenv/versions/2.6.5/lib/ruby/gems/2.6.0/gems/rake-13.0.1/lib/rake/rake_test_loader.rb:5:in `select' 9: from /Users/yahonda/.rbenv/versions/2.6.5/lib/ruby/gems/2.6.0/gems/rake-13.0.1/lib/rake/rake_test_loader.rb:17:in `block in <main>' 8: from /Users/yahonda/.rbenv/versions/2.6.5/lib/ruby/gems/2.6.0/gems/zeitwerk-2.3.0/lib/zeitwerk/kernel.rb:23:in `require' 7: from /Users/yahonda/.rbenv/versions/2.6.5/lib/ruby/gems/2.6.0/gems/zeitwerk-2.3.0/lib/zeitwerk/kernel.rb:23:in `require' 6: from /Users/yahonda/src/github.com/rails/rails/activestorage/test/service/azure_storage_service_test.rb:7:in `<top (required)>' 5: from /Users/yahonda/src/github.com/rails/rails/activestorage/test/service/azure_storage_service_test.rb:8:in `<class:AzureStorageServiceTest>' 4: from /Users/yahonda/src/github.com/rails/rails/activestorage/lib/active_storage/service.rb:51:in `configure' 3: from /Users/yahonda/src/github.com/rails/rails/activestorage/lib/active_storage/service/configurator.rb:8:in `build' 2: from /Users/yahonda/src/github.com/rails/rails/activestorage/lib/active_storage/service/configurator.rb:17:in `build' 1: from /Users/yahonda/src/github.com/rails/rails/activestorage/lib/active_storage/service/configurator.rb:29:in `resolve' /Users/yahonda/src/github.com/rails/rails/activestorage/lib/active_storage/service/configurator.rb:33:in `rescue in resolve': Missing service adapter for "AzureStorage" (RuntimeError) rake aborted! ``` * Update Gemfile.lock to bump azure-storage-blob version ``` % bundle update --conservative faraday azure-storage-blob google-cloud-storage` ``` - How to find gem name to update by setting `gem "azure-storage-blob", "= 2.0.0"` temporarily ```ruby % git diff diff --git a/Gemfile b/Gemfile index 5fdaceab2f..6be7dccf4b 100644 --- a/Gemfile +++ b/Gemfile @@ -84,7 +84,7 @@ end group :storage do gem "aws-sdk-s3", require: false gem "google-cloud-storage", "~> 1.11", require: false - gem "azure-storage-blob", require: false + gem "azure-storage-blob", "= 2.0.0", require: false # Use 2.0.0 temporarily to find which gems need bump gem "image_processing", "~> 1.2" end % bundle install Fetching gem metadata from https://rubygems.org/......... Fetching gem metadata from https://rubygems.org/. Resolving dependencies..... Bundler could not find compatible versions for gem "faraday": In snapshot (Gemfile.lock): faraday (= 0.17.1) In Gemfile: azure-storage-blob (= 2.0.0) was resolved to 2.0.0, which depends on azure-storage-common (~> 2.0) was resolved to 2.0.1, which depends on faraday (~> 1.0) google-cloud-storage (~> 1.11) was resolved to 1.25.0, which depends on googleauth (~> 0.9) was resolved to 0.10.0, which depends on faraday (~> 0.12) Running `bundle update` will rebuild your snapshot from scratch, using only the gems in your Gemfile, which may resolve the conflict. % git checkout -f Gemfile % bundle update --conservative faraday azure-storage-blob google-cloud-storage ```
2020-03-16 18:38:22 +08:00
azure-storage-common (~> 2.0)
Upgrade all the gems to make sure we are testing with the latest versions locally
2021-01-22 05:22:41 +08:00
nokogiri (~> 1.11.0.rc2)
azure-storage-common (2.0.2)
Unlock `azure-storage-blob` version to use version 2.0 `azure-storage-blob` 2.0.0 has been released. https://rubygems.org/gems/azure-storage-blob/versions/2.0.0 According to this commit and changelog, `azure-storage-blob` 1.1.0 did not support Ruby 2.6 and higher. As of right now, Rails master branch should support Ruby 2.5.0, 2.6.0 and 2.7.0 then it should be appropriate to unlock `azure-storage-blob` version. https://github.com/Azure/azure-storage-ruby/commit/252e3f06a5cf2e2583302bfefa95d8b25818a44f This commit addresses this following error: ```ruby % cd activestorage % bundle exec rake test Traceback (most recent call last): 14: from /Users/yahonda/.rbenv/versions/2.6.5/lib/ruby/gems/2.6.0/gems/rake-13.0.1/lib/rake/rake_test_loader.rb:5:in `<main>' 13: from /Users/yahonda/.rbenv/versions/2.6.5/lib/ruby/gems/2.6.0/gems/rake-13.0.1/lib/rake/rake_test_loader.rb:5:in `select' 12: from /Users/yahonda/.rbenv/versions/2.6.5/lib/ruby/gems/2.6.0/gems/rake-13.0.1/lib/rake/rake_test_loader.rb:17:in `block in <main>' 11: from /Users/yahonda/.rbenv/versions/2.6.5/lib/ruby/gems/2.6.0/gems/zeitwerk-2.3.0/lib/zeitwerk/kernel.rb:23:in `require' 10: from /Users/yahonda/.rbenv/versions/2.6.5/lib/ruby/gems/2.6.0/gems/zeitwerk-2.3.0/lib/zeitwerk/kernel.rb:23:in `require' 9: from /Users/yahonda/src/github.com/rails/rails/activestorage/test/service/azure_storage_service_test.rb:7:in `<top (required)>' 8: from /Users/yahonda/src/github.com/rails/rails/activestorage/test/service/azure_storage_service_test.rb:8:in `<class:AzureStorageServiceTest>' 7: from /Users/yahonda/src/github.com/rails/rails/activestorage/lib/active_storage/service.rb:51:in `configure' 6: from /Users/yahonda/src/github.com/rails/rails/activestorage/lib/active_storage/service/configurator.rb:8:in `build' 5: from /Users/yahonda/src/github.com/rails/rails/activestorage/lib/active_storage/service/configurator.rb:17:in `build' 4: from /Users/yahonda/src/github.com/rails/rails/activestorage/lib/active_storage/service/configurator.rb:30:in `resolve' 3: from /Users/yahonda/.rbenv/versions/2.6.5/lib/ruby/gems/2.6.0/gems/zeitwerk-2.3.0/lib/zeitwerk/kernel.rb:23:in `require' 2: from /Users/yahonda/.rbenv/versions/2.6.5/lib/ruby/gems/2.6.0/gems/zeitwerk-2.3.0/lib/zeitwerk/kernel.rb:23:in `require' 1: from /Users/yahonda/src/github.com/rails/rails/activestorage/lib/active_storage/service/azure_storage_service.rb:3:in `<top (required)>' /Users/yahonda/.rbenv/versions/2.6.5/lib/ruby/gems/2.6.0/gems/bundler-2.1.4/lib/bundler/rubygems_integration.rb:346:in `block (2 levels) in replace_gem': can't activate azure-storage-blob (~> 1.1), already activated azure-storage-blob-2.0.0. Make sure all dependencies are added to Gemfile. (Gem::LoadError) 11: from /Users/yahonda/.rbenv/versions/2.6.5/lib/ruby/gems/2.6.0/gems/rake-13.0.1/lib/rake/rake_test_loader.rb:5:in `<main>' 10: from /Users/yahonda/.rbenv/versions/2.6.5/lib/ruby/gems/2.6.0/gems/rake-13.0.1/lib/rake/rake_test_loader.rb:5:in `select' 9: from /Users/yahonda/.rbenv/versions/2.6.5/lib/ruby/gems/2.6.0/gems/rake-13.0.1/lib/rake/rake_test_loader.rb:17:in `block in <main>' 8: from /Users/yahonda/.rbenv/versions/2.6.5/lib/ruby/gems/2.6.0/gems/zeitwerk-2.3.0/lib/zeitwerk/kernel.rb:23:in `require' 7: from /Users/yahonda/.rbenv/versions/2.6.5/lib/ruby/gems/2.6.0/gems/zeitwerk-2.3.0/lib/zeitwerk/kernel.rb:23:in `require' 6: from /Users/yahonda/src/github.com/rails/rails/activestorage/test/service/azure_storage_service_test.rb:7:in `<top (required)>' 5: from /Users/yahonda/src/github.com/rails/rails/activestorage/test/service/azure_storage_service_test.rb:8:in `<class:AzureStorageServiceTest>' 4: from /Users/yahonda/src/github.com/rails/rails/activestorage/lib/active_storage/service.rb:51:in `configure' 3: from /Users/yahonda/src/github.com/rails/rails/activestorage/lib/active_storage/service/configurator.rb:8:in `build' 2: from /Users/yahonda/src/github.com/rails/rails/activestorage/lib/active_storage/service/configurator.rb:17:in `build' 1: from /Users/yahonda/src/github.com/rails/rails/activestorage/lib/active_storage/service/configurator.rb:29:in `resolve' /Users/yahonda/src/github.com/rails/rails/activestorage/lib/active_storage/service/configurator.rb:33:in `rescue in resolve': Missing service adapter for "AzureStorage" (RuntimeError) rake aborted! ``` * Update Gemfile.lock to bump azure-storage-blob version ``` % bundle update --conservative faraday azure-storage-blob google-cloud-storage` ``` - How to find gem name to update by setting `gem "azure-storage-blob", "= 2.0.0"` temporarily ```ruby % git diff diff --git a/Gemfile b/Gemfile index 5fdaceab2f..6be7dccf4b 100644 --- a/Gemfile +++ b/Gemfile @@ -84,7 +84,7 @@ end group :storage do gem "aws-sdk-s3", require: false gem "google-cloud-storage", "~> 1.11", require: false - gem "azure-storage-blob", require: false + gem "azure-storage-blob", "= 2.0.0", require: false # Use 2.0.0 temporarily to find which gems need bump gem "image_processing", "~> 1.2" end % bundle install Fetching gem metadata from https://rubygems.org/......... Fetching gem metadata from https://rubygems.org/. Resolving dependencies..... Bundler could not find compatible versions for gem "faraday": In snapshot (Gemfile.lock): faraday (= 0.17.1) In Gemfile: azure-storage-blob (= 2.0.0) was resolved to 2.0.0, which depends on azure-storage-common (~> 2.0) was resolved to 2.0.1, which depends on faraday (~> 1.0) google-cloud-storage (~> 1.11) was resolved to 1.25.0, which depends on googleauth (~> 0.9) was resolved to 0.10.0, which depends on faraday (~> 0.12) Running `bundle update` will rebuild your snapshot from scratch, using only the gems in your Gemfile, which may resolve the conflict. % git checkout -f Gemfile % bundle update --conservative faraday azure-storage-blob google-cloud-storage ```
2020-03-16 18:38:22 +08:00
faraday (~> 1.0)
faraday_middleware (~> 1.0.0.rc1)
Upgrade all the gems to make sure we are testing with the latest versions locally
2021-01-22 05:22:41 +08:00
net-http-persistent (~> 4.0)
nokogiri (~> 1.11.0.rc2)
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 18:40:24 +08:00
backburner (1.5.0)
Update Gemfile.lock
2015-08-10 11:30:03 +08: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 18:40:24 +08:00
concurrent-ruby (~> 1.0, >= 1.0.1)
Update Gemfile.lock
2015-08-10 11:30:03 +08:00
dante (> 0.1.5)
Upgrade all the gems
2020-11-04 14:39:41 +08:00
bcrypt (3.1.16)
Update development gems
2021-06-09 07:27:47 +08:00
beaneater (1.1.1)
Revert "Lock benchmark-ips version "< 2.9.0"" This reverts commit b63e1477eaccfa6416db4f09bb82880ecb0797d1.
2021-05-25 05:11:38 +08:00
benchmark-ips (2.9.1)
Upgrade the development Gemfile.lock
2021-04-14 02:18:28 +08:00
blade (0.7.2)
Add accidentally removed dependency in Gemfile.lock Follow up to ca0b6d0d416776655ed7516ac18f126fbde5315a.
2016-08-04 06:55:47 +08:00
activesupport (>= 3.0.0)
Upgrade the development Gemfile.lock
2021-04-14 02:18:28 +08:00
blade-qunit_adapter (>= 2.0.1)
Add accidentally removed dependency in Gemfile.lock Follow up to ca0b6d0d416776655ed7516ac18f126fbde5315a.
2016-08-04 06:55:47 +08:00
coffee-script
coffee-script-source
Upgrade the development Gemfile.lock
2021-04-14 02:18:28 +08:00
curses (>= 1.4.0)
Add accidentally removed dependency in Gemfile.lock Follow up to ca0b6d0d416776655ed7516ac18f126fbde5315a.
2016-08-04 06:55:47 +08:00
eventmachine
faye
sprockets (>= 3.0)
thin (>= 1.6.0)
Bump `thor` and `blade` For test with latest thor.
2017-08-17 07:53:36 +08:00
thor (>= 0.19.1)
Upgrade the development Gemfile.lock
2021-04-14 02:18:28 +08:00
useragent (>= 0.16.7)
Bump Blade and its Sauce Labs plugin to fix tunnel shutdown and related error https://travis-ci.org/rails/rails/jobs/165766716#L506
2016-11-21 06:08:31 +08:00
blade-qunit_adapter (2.0.1)
Update development gems
2021-06-09 07:27:47 +08:00
bootsnap (1.7.5)
Start Rails 6.2 development :tada:
2020-12-03 07:37:26 +08:00
msgpack (~> 1.0)
Fix test with new capybara
2019-12-28 02:30:45 +08:00
builder (3.2.4)
Update development gems
2021-06-09 07:27:47 +08:00
bunny (2.18.0)
Upgrade all the gems
2020-11-04 14:39:41 +08:00
amq-protocol (~> 2.3, >= 2.3.1)
Update development gems
2021-06-09 07:27:47 +08:00
sorted_set (~> 1, >= 1.0.2)
Upgrade capybara to work with Ruby 3.1 and earlier
2021-12-09 05:44:11 +08:00
capybara (3.36.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-28 04:48:24 +08:00
addressable
Upgrade capybara to work with Ruby 3.1 and earlier
2021-12-09 05:44:11 +08:00
matrix
Test with released thor thor 0.20.0 was released so we can test with the released version.
2017-08-17 02:03:24 +08:00
mini_mime (>= 0.1.3)
Fix broken `ServerTest` with Capybara 3.0.0 It seems that it is no longer possible to specify the value held by `Capybara.server` as sever. Ref: https://github.com/teamcapybara/capybara/commit/ba7674086cbcd3b22d3614011815bc5d483e5960
2018-04-06 19:55:34 +08:00
nokogiri (~> 1.8)
rack (>= 1.6.0)
rack-test (>= 0.6.3)
Upgrade the development Gemfile.lock
2021-04-14 02:18:28 +08:00
regexp_parser (>= 1.5, < 3.0)
bundle update
2018-11-10 06:21:08 +08:00
xpath (~> 3.2)
Upgrade development gems
2021-06-18 04:26:38 +08:00
childprocess (4.1.0)
Update Gemfile.lock
2015-08-10 11:30:03 +08:00
coffee-script (2.4.1)
Track Gemfile.lock at the repository The main reason is to make bisect easier. In some points, we have a lot of git dependencies. Since we don't have the information of which commit we are referring to, bundler get the latest commit of the master branch of the dependency. This sometimes returns a version that is not compatible with Rails anymore, making the tests fail and the harder to identify the commit that introduced a bug. Also this will make sure that a contributor will always get a set of dependencies that are passing with our tests. In our CI server we delete the lock file to make sure we are always testing against the newest release of our dependencies.
2015-02-19 00:30:25 +08:00
coffee-script-source
execjs
Bump coffee-script-source to fix bug Coffee script 1.12.1 was released and contained a bug where coffee script was undefined. 1.12.1 was yanked and 1.12.2 was released. This bumps coffee-script-source so that CI Railties tests pass. See: https://github.com/jashkenas/coffeescript/issues/4403
2016-12-16 23:43:44 +08:00
coffee-script-source (1.12.2)
Update development gems
2021-06-09 07:27:47 +08:00
concurrent-ruby (1.1.9)
connection_pool (2.2.5)
Override the github git source instead of changing manually all entries
2016-09-14 08:19:09 +08:00
cookiejar (0.3.3)
Upgrade all the gems to make sure we are testing with the latest versions locally
2021-01-22 05:22:41 +08:00
crack (0.4.5)
rexml
Update sprockets-rails to fix tests on Ruby master Without this, railties/test/application/rake_test.rb fails with: ActionView::Template::Error: wrong number of arguments (given 2, expected 1)
2020-10-04 05:43:39 +08:00
crass (1.0.6)
Make Sprockets more optional, offer Propshaft as alternative (#43261) * Make Sprockets more optional, offer Propshaft as alternative * Whups, local reference * No longer used * Spacing * Need explicit sprockets-rails inclusion now * Manually require the sprockets railtie * Don't need these changes right now * Kick off another build * Fix tests * DRY up test * Require railtie when using sprockets * Introduce option to skip asset pipeline * No longer relevant * Always have to return * Gone * Add helper for skip_sprockets? * Fix guard statement * Use latest gems * Include propshaft * fix tests for #43261 (#43277) * help fix tests for #43261 skip_sprockets? should not be called on options :skip_sprockets is no longer a value in the option hash, so skip_sprockets? should not be called on it move --asset-pipeline to shared generator skip_sprockets? is defined on app_base, and used in the plugin generator to determine whether to add the engine's assets to the dummy sprockets manifest, so I believe it makes sense to include in both generators Because of this change, I also changed the shared test back to testing against non-sprockets add skip_sprockets to Gemfile template vars Mocking skip_sprockets? in app_base generator fix more generator tests * use skip_sprockets? everywhere * Use latest propshaft * Update `AssetUrlHelper` docs to list both asset pipeline gems (#43328) * Update to latest Propshaft * Bump Propshaft again * Ask for latest * Use latest propshaft Co-authored-by: Hartley McGuire <skipkayhil@gmail.com> Co-authored-by: Richard Macklin <1863540+rmacklin@users.noreply.github.com>
2021-10-09 23:03:05 +08:00
cssbundling-rails (0.2.2)
railties (>= 6.0.0)
Upgrade development gems
2021-06-18 04:26:38 +08:00
curses (1.4.2)
Update development gems
2021-06-09 07:27:47 +08:00
daemons (1.4.0)
Bump dalli from 2.7.11 to 3.0.1 in Gemfile.lock
2021-10-14 18:12:11 +08:00
dalli (3.0.1)
Update Gemfile.lock
2015-08-10 11:30:03 +08:00
dante (0.2.0)
Use debug 1.1+ for the debugger + log quieting
2021-09-20 21:18:30 +08:00
debug (1.1.0)
Depend on ruby/debug, replacing Byebug ruby/debug is a new debugger that is going to ship with CRuby. It makes sense for Rails to switch to this one because that is where the language is heading, and because Byebug is not fully compatible with Zeitwerk. See https://github.com/deivid-rodriguez/byebug/issues/564 While ruby/debug has not been heavily tested with Zeitwerk, casual usage seems to suggest it works without issues, including explicit namespaces, which is where Byebug and Zeitwerk conflict. Byebug is terrific, thanks a lot for all these years. :heart:
2021-09-08 23:35:41 +08:00
irb
reline (>= 0.2.7)
Update w3c_validtors for Ruby 3 compatibility (#40227) * Update w3c_validtors for Ruby 3 compatibility * Update google-api-client for Ruby 3 compatibility
2020-09-21 13:19:59 +08:00
declarative (0.0.20)
Upgrade all the gems to make sure we are testing with the latest versions locally
2021-01-22 05:22:41 +08:00
delayed_job (4.1.9)
activesupport (>= 3.0, < 6.2)
Upgrade the development Gemfile.lock
2021-04-14 02:18:28 +08:00
delayed_job_active_record (4.1.6)
Upgrade all the gems to make sure we are testing with the latest versions locally
2021-01-22 05:22:41 +08:00
activerecord (>= 3.0, < 6.2)
delayed_job and delayed_job_active_record gems with AR5 support are available
2017-01-29 08:05:06 +08:00
delayed_job (>= 3.0, < 5)
Upgrade all the gems to make sure we are testing with the latest versions locally
2021-01-22 05:22:41 +08:00
digest-crc (0.6.3)
rake (>= 12.0.0, < 14.0.0)
Upgrade all the gems
2020-11-04 14:39:41 +08:00
em-http-request (1.1.7)
Remove Blade gem dependency Apps that depend on Action Cable don't need Blade for app development, so we can remove the gem dependency. We do need Blade for Action Cable dev, so we bundle it in the Gemfile. Signed-off-by: Jeremy Daer <jeremydaer@gmail.com>
2016-05-22 02:15:58 +08:00
addressable (>= 2.3.4)
Override the github git source instead of changing manually all entries
2016-09-14 08:19:09 +08:00
cookiejar (!= 0.3.1)
Remove Blade gem dependency Apps that depend on Action Cable don't need Blade for app development, so we can remove the gem dependency. We do need Blade for Action Cable dev, so we bundle it in the Gemfile. Signed-off-by: Jeremy Daer <jeremydaer@gmail.com>
2016-05-22 02:15:58 +08:00
em-socksify (>= 0.3)
eventmachine (>= 1.0.3)
http_parser.rb (>= 0.6.0)
Update em-socksify to the latest version Avoid warning: parentheses after method name is interpreted as an argument list, not a decomposed argument
2018-02-07 06:08:13 +08:00
em-socksify (0.3.2)
Remove Blade gem dependency Apps that depend on Action Cable don't need Blade for app development, so we can remove the gem dependency. We do need Blade for Action Cable dev, so we bundle it in the Gemfile. Signed-off-by: Jeremy Daer <jeremydaer@gmail.com>
2016-05-22 02:15:58 +08:00
eventmachine (>= 1.0.0.beta.4)
CI against erubi 1.10.0
2020-11-14 13:31:58 +08:00
erubi (1.10.0)
Upgrade all the gems
2020-11-04 14:39:41 +08:00
et-orbi (1.2.4)
Update rack-test dependency constraint
2017-07-20 07:04:53 +08:00
tzinfo
Suppress deprecated warning in Action Cable
2017-07-25 14:53:02 +08:00
event_emitter (0.2.6)
Bundle update
2018-05-31 01:49:55 +08:00
eventmachine (1.2.7)
Update development gems
2021-06-09 07:27:47 +08:00
execjs (2.8.1)
faraday (1.4.2)
faraday-em_http (~> 1.0)
faraday-em_synchrony (~> 1.0)
faraday-excon (~> 1.1)
Upgrade all the gems to make sure we are testing with the latest versions locally
2021-01-22 05:22:41 +08:00
faraday-net_http (~> 1.0)
Update development gems
2021-06-09 07:27:47 +08:00
faraday-net_http_persistent (~> 1.1)
Add accidentally removed dependency in Gemfile.lock Follow up to ca0b6d0d416776655ed7516ac18f126fbde5315a.
2016-08-04 06:55:47 +08:00
multipart-post (>= 1.2, < 3)
Update development gems
2021-06-09 07:27:47 +08:00
ruby2_keywords (>= 0.0.4)
faraday-em_http (1.0.0)
faraday-em_synchrony (1.0.0)
faraday-excon (1.1.0)
Upgrade all the gems to make sure we are testing with the latest versions locally
2021-01-22 05:22:41 +08:00
faraday-net_http (1.0.1)
Update development gems
2021-06-09 07:27:47 +08:00
faraday-net_http_persistent (1.1.0)
Upgrade all the gems
2020-11-04 14:39:41 +08:00
faraday_middleware (1.0.0)
Unlock `azure-storage-blob` version to use version 2.0 `azure-storage-blob` 2.0.0 has been released. https://rubygems.org/gems/azure-storage-blob/versions/2.0.0 According to this commit and changelog, `azure-storage-blob` 1.1.0 did not support Ruby 2.6 and higher. As of right now, Rails master branch should support Ruby 2.5.0, 2.6.0 and 2.7.0 then it should be appropriate to unlock `azure-storage-blob` version. https://github.com/Azure/azure-storage-ruby/commit/252e3f06a5cf2e2583302bfefa95d8b25818a44f This commit addresses this following error: ```ruby % cd activestorage % bundle exec rake test Traceback (most recent call last): 14: from /Users/yahonda/.rbenv/versions/2.6.5/lib/ruby/gems/2.6.0/gems/rake-13.0.1/lib/rake/rake_test_loader.rb:5:in `<main>' 13: from /Users/yahonda/.rbenv/versions/2.6.5/lib/ruby/gems/2.6.0/gems/rake-13.0.1/lib/rake/rake_test_loader.rb:5:in `select' 12: from /Users/yahonda/.rbenv/versions/2.6.5/lib/ruby/gems/2.6.0/gems/rake-13.0.1/lib/rake/rake_test_loader.rb:17:in `block in <main>' 11: from /Users/yahonda/.rbenv/versions/2.6.5/lib/ruby/gems/2.6.0/gems/zeitwerk-2.3.0/lib/zeitwerk/kernel.rb:23:in `require' 10: from /Users/yahonda/.rbenv/versions/2.6.5/lib/ruby/gems/2.6.0/gems/zeitwerk-2.3.0/lib/zeitwerk/kernel.rb:23:in `require' 9: from /Users/yahonda/src/github.com/rails/rails/activestorage/test/service/azure_storage_service_test.rb:7:in `<top (required)>' 8: from /Users/yahonda/src/github.com/rails/rails/activestorage/test/service/azure_storage_service_test.rb:8:in `<class:AzureStorageServiceTest>' 7: from /Users/yahonda/src/github.com/rails/rails/activestorage/lib/active_storage/service.rb:51:in `configure' 6: from /Users/yahonda/src/github.com/rails/rails/activestorage/lib/active_storage/service/configurator.rb:8:in `build' 5: from /Users/yahonda/src/github.com/rails/rails/activestorage/lib/active_storage/service/configurator.rb:17:in `build' 4: from /Users/yahonda/src/github.com/rails/rails/activestorage/lib/active_storage/service/configurator.rb:30:in `resolve' 3: from /Users/yahonda/.rbenv/versions/2.6.5/lib/ruby/gems/2.6.0/gems/zeitwerk-2.3.0/lib/zeitwerk/kernel.rb:23:in `require' 2: from /Users/yahonda/.rbenv/versions/2.6.5/lib/ruby/gems/2.6.0/gems/zeitwerk-2.3.0/lib/zeitwerk/kernel.rb:23:in `require' 1: from /Users/yahonda/src/github.com/rails/rails/activestorage/lib/active_storage/service/azure_storage_service.rb:3:in `<top (required)>' /Users/yahonda/.rbenv/versions/2.6.5/lib/ruby/gems/2.6.0/gems/bundler-2.1.4/lib/bundler/rubygems_integration.rb:346:in `block (2 levels) in replace_gem': can't activate azure-storage-blob (~> 1.1), already activated azure-storage-blob-2.0.0. Make sure all dependencies are added to Gemfile. (Gem::LoadError) 11: from /Users/yahonda/.rbenv/versions/2.6.5/lib/ruby/gems/2.6.0/gems/rake-13.0.1/lib/rake/rake_test_loader.rb:5:in `<main>' 10: from /Users/yahonda/.rbenv/versions/2.6.5/lib/ruby/gems/2.6.0/gems/rake-13.0.1/lib/rake/rake_test_loader.rb:5:in `select' 9: from /Users/yahonda/.rbenv/versions/2.6.5/lib/ruby/gems/2.6.0/gems/rake-13.0.1/lib/rake/rake_test_loader.rb:17:in `block in <main>' 8: from /Users/yahonda/.rbenv/versions/2.6.5/lib/ruby/gems/2.6.0/gems/zeitwerk-2.3.0/lib/zeitwerk/kernel.rb:23:in `require' 7: from /Users/yahonda/.rbenv/versions/2.6.5/lib/ruby/gems/2.6.0/gems/zeitwerk-2.3.0/lib/zeitwerk/kernel.rb:23:in `require' 6: from /Users/yahonda/src/github.com/rails/rails/activestorage/test/service/azure_storage_service_test.rb:7:in `<top (required)>' 5: from /Users/yahonda/src/github.com/rails/rails/activestorage/test/service/azure_storage_service_test.rb:8:in `<class:AzureStorageServiceTest>' 4: from /Users/yahonda/src/github.com/rails/rails/activestorage/lib/active_storage/service.rb:51:in `configure' 3: from /Users/yahonda/src/github.com/rails/rails/activestorage/lib/active_storage/service/configurator.rb:8:in `build' 2: from /Users/yahonda/src/github.com/rails/rails/activestorage/lib/active_storage/service/configurator.rb:17:in `build' 1: from /Users/yahonda/src/github.com/rails/rails/activestorage/lib/active_storage/service/configurator.rb:29:in `resolve' /Users/yahonda/src/github.com/rails/rails/activestorage/lib/active_storage/service/configurator.rb:33:in `rescue in resolve': Missing service adapter for "AzureStorage" (RuntimeError) rake aborted! ``` * Update Gemfile.lock to bump azure-storage-blob version ``` % bundle update --conservative faraday azure-storage-blob google-cloud-storage` ``` - How to find gem name to update by setting `gem "azure-storage-blob", "= 2.0.0"` temporarily ```ruby % git diff diff --git a/Gemfile b/Gemfile index 5fdaceab2f..6be7dccf4b 100644 --- a/Gemfile +++ b/Gemfile @@ -84,7 +84,7 @@ end group :storage do gem "aws-sdk-s3", require: false gem "google-cloud-storage", "~> 1.11", require: false - gem "azure-storage-blob", require: false + gem "azure-storage-blob", "= 2.0.0", require: false # Use 2.0.0 temporarily to find which gems need bump gem "image_processing", "~> 1.2" end % bundle install Fetching gem metadata from https://rubygems.org/......... Fetching gem metadata from https://rubygems.org/. Resolving dependencies..... Bundler could not find compatible versions for gem "faraday": In snapshot (Gemfile.lock): faraday (= 0.17.1) In Gemfile: azure-storage-blob (= 2.0.0) was resolved to 2.0.0, which depends on azure-storage-common (~> 2.0) was resolved to 2.0.1, which depends on faraday (~> 1.0) google-cloud-storage (~> 1.11) was resolved to 1.25.0, which depends on googleauth (~> 0.9) was resolved to 0.10.0, which depends on faraday (~> 0.12) Running `bundle update` will rebuild your snapshot from scratch, using only the gems in your Gemfile, which may resolve the conflict. % git checkout -f Gemfile % bundle update --conservative faraday azure-storage-blob google-cloud-storage ```
2020-03-16 18:38:22 +08:00
faraday (~> 1.0)
Upgrade all the gems
2020-11-04 14:39:41 +08:00
faye (1.4.0)
Remove Blade gem dependency Apps that depend on Action Cable don't need Blade for app development, so we can remove the gem dependency. We do need Blade for Action Cable dev, so we bundle it in the Gemfile. Signed-off-by: Jeremy Daer <jeremydaer@gmail.com>
2016-05-22 02:15:58 +08:00
cookiejar (>= 0.3.0)
Upgrade all the gems
2020-11-04 14:39:41 +08:00
em-http-request (>= 1.1.6)
Remove Blade gem dependency Apps that depend on Action Cable don't need Blade for app development, so we can remove the gem dependency. We do need Blade for Action Cable dev, so we bundle it in the Gemfile. Signed-off-by: Jeremy Daer <jeremydaer@gmail.com>
2016-05-22 02:15:58 +08:00
eventmachine (>= 0.12.0)
Upgrade all the gems
2020-11-04 14:39:41 +08:00
faye-websocket (>= 0.11.0)
Remove Blade gem dependency Apps that depend on Action Cable don't need Blade for app development, so we can remove the gem dependency. We do need Blade for Action Cable dev, so we bundle it in the Gemfile. Signed-off-by: Jeremy Daer <jeremydaer@gmail.com>
2016-05-22 02:15:58 +08:00
multi_json (>= 1.0.0)
rack (>= 1.0.0)
websocket-driver (>= 0.5.1)
Update development gems
2021-06-09 07:27:47 +08:00
faye-websocket (0.11.1)
Add a couple of tests that connect with a WS client
2016-01-25 01:25:53 +08:00
eventmachine (>= 0.12.0)
websocket-driver (>= 0.5.1)
Upgrade development gems
2021-06-18 04:26:38 +08:00
ffi (1.15.3)
Update development gems
2021-06-09 07:27:47 +08:00
fugit (1.5.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 20:58:20 +08:00
et-orbi (~> 1.1, >= 1.1.8)
Upgrade all the gems
2020-11-04 14:39:41 +08:00
raabro (~> 1.4)
Start Rails 7.1 development
2021-12-07 23:52:30 +08:00
globalid (1.0.0)
Update globalid to 0.5.1 for ruby-head compatibility https://github.com/ruby/uri/pull/26 was recently pulled in ruby-head, and it breaks globalid < 0.5.
2021-07-28 05:23:13 +08:00
activesupport (>= 5.0)
Upgrade the development Gemfile.lock
2021-04-14 02:18:28 +08:00
google-apis-core (0.3.0)
Resolve gemspec typo
2017-08-01 04:55:55 +08:00
addressable (~> 2.5, >= 2.5.1)
Upgrade all the gems to make sure we are testing with the latest versions locally
2021-01-22 05:22:41 +08:00
googleauth (~> 0.14)
Resolve gemspec typo
2017-08-01 04:55:55 +08:00
httpclient (>= 2.8.1, < 3.0)
Bundle update
2019-10-10 12:48:16 +08:00
mini_mime (~> 1.0)
Resolve gemspec typo
2017-08-01 04:55:55 +08:00
representable (~> 3.0)
retriable (>= 2.0, < 4.0)
Update w3c_validtors for Ruby 3 compatibility (#40227) * Update w3c_validtors for Ruby 3 compatibility * Update google-api-client for Ruby 3 compatibility
2020-09-21 13:19:59 +08:00
rexml
Upgrade all the gems to make sure we are testing with the latest versions locally
2021-01-22 05:22:41 +08:00
signet (~> 0.14)
Upgrade the development Gemfile.lock
2021-04-14 02:18:28 +08:00
webrick
Update development gems
2021-06-09 07:27:47 +08:00
google-apis-iamcredentials_v1 (0.4.0)
Upgrade all the gems to make sure we are testing with the latest versions locally
2021-01-22 05:22:41 +08:00
google-apis-core (~> 0.1)
Update development gems
2021-06-09 07:27:47 +08:00
google-apis-storage_v1 (0.4.0)
Upgrade all the gems to make sure we are testing with the latest versions locally
2021-01-22 05:22:41 +08:00
google-apis-core (~> 0.1)
Upgrade the development Gemfile.lock
2021-04-14 02:18:28 +08:00
google-cloud-core (1.6.0)
Resolve gemspec typo
2017-08-01 04:55:55 +08:00
google-cloud-env (~> 1.0)
Unlock `azure-storage-blob` version to use version 2.0 `azure-storage-blob` 2.0.0 has been released. https://rubygems.org/gems/azure-storage-blob/versions/2.0.0 According to this commit and changelog, `azure-storage-blob` 1.1.0 did not support Ruby 2.6 and higher. As of right now, Rails master branch should support Ruby 2.5.0, 2.6.0 and 2.7.0 then it should be appropriate to unlock `azure-storage-blob` version. https://github.com/Azure/azure-storage-ruby/commit/252e3f06a5cf2e2583302bfefa95d8b25818a44f This commit addresses this following error: ```ruby % cd activestorage % bundle exec rake test Traceback (most recent call last): 14: from /Users/yahonda/.rbenv/versions/2.6.5/lib/ruby/gems/2.6.0/gems/rake-13.0.1/lib/rake/rake_test_loader.rb:5:in `<main>' 13: from /Users/yahonda/.rbenv/versions/2.6.5/lib/ruby/gems/2.6.0/gems/rake-13.0.1/lib/rake/rake_test_loader.rb:5:in `select' 12: from /Users/yahonda/.rbenv/versions/2.6.5/lib/ruby/gems/2.6.0/gems/rake-13.0.1/lib/rake/rake_test_loader.rb:17:in `block in <main>' 11: from /Users/yahonda/.rbenv/versions/2.6.5/lib/ruby/gems/2.6.0/gems/zeitwerk-2.3.0/lib/zeitwerk/kernel.rb:23:in `require' 10: from /Users/yahonda/.rbenv/versions/2.6.5/lib/ruby/gems/2.6.0/gems/zeitwerk-2.3.0/lib/zeitwerk/kernel.rb:23:in `require' 9: from /Users/yahonda/src/github.com/rails/rails/activestorage/test/service/azure_storage_service_test.rb:7:in `<top (required)>' 8: from /Users/yahonda/src/github.com/rails/rails/activestorage/test/service/azure_storage_service_test.rb:8:in `<class:AzureStorageServiceTest>' 7: from /Users/yahonda/src/github.com/rails/rails/activestorage/lib/active_storage/service.rb:51:in `configure' 6: from /Users/yahonda/src/github.com/rails/rails/activestorage/lib/active_storage/service/configurator.rb:8:in `build' 5: from /Users/yahonda/src/github.com/rails/rails/activestorage/lib/active_storage/service/configurator.rb:17:in `build' 4: from /Users/yahonda/src/github.com/rails/rails/activestorage/lib/active_storage/service/configurator.rb:30:in `resolve' 3: from /Users/yahonda/.rbenv/versions/2.6.5/lib/ruby/gems/2.6.0/gems/zeitwerk-2.3.0/lib/zeitwerk/kernel.rb:23:in `require' 2: from /Users/yahonda/.rbenv/versions/2.6.5/lib/ruby/gems/2.6.0/gems/zeitwerk-2.3.0/lib/zeitwerk/kernel.rb:23:in `require' 1: from /Users/yahonda/src/github.com/rails/rails/activestorage/lib/active_storage/service/azure_storage_service.rb:3:in `<top (required)>' /Users/yahonda/.rbenv/versions/2.6.5/lib/ruby/gems/2.6.0/gems/bundler-2.1.4/lib/bundler/rubygems_integration.rb:346:in `block (2 levels) in replace_gem': can't activate azure-storage-blob (~> 1.1), already activated azure-storage-blob-2.0.0. Make sure all dependencies are added to Gemfile. (Gem::LoadError) 11: from /Users/yahonda/.rbenv/versions/2.6.5/lib/ruby/gems/2.6.0/gems/rake-13.0.1/lib/rake/rake_test_loader.rb:5:in `<main>' 10: from /Users/yahonda/.rbenv/versions/2.6.5/lib/ruby/gems/2.6.0/gems/rake-13.0.1/lib/rake/rake_test_loader.rb:5:in `select' 9: from /Users/yahonda/.rbenv/versions/2.6.5/lib/ruby/gems/2.6.0/gems/rake-13.0.1/lib/rake/rake_test_loader.rb:17:in `block in <main>' 8: from /Users/yahonda/.rbenv/versions/2.6.5/lib/ruby/gems/2.6.0/gems/zeitwerk-2.3.0/lib/zeitwerk/kernel.rb:23:in `require' 7: from /Users/yahonda/.rbenv/versions/2.6.5/lib/ruby/gems/2.6.0/gems/zeitwerk-2.3.0/lib/zeitwerk/kernel.rb:23:in `require' 6: from /Users/yahonda/src/github.com/rails/rails/activestorage/test/service/azure_storage_service_test.rb:7:in `<top (required)>' 5: from /Users/yahonda/src/github.com/rails/rails/activestorage/test/service/azure_storage_service_test.rb:8:in `<class:AzureStorageServiceTest>' 4: from /Users/yahonda/src/github.com/rails/rails/activestorage/lib/active_storage/service.rb:51:in `configure' 3: from /Users/yahonda/src/github.com/rails/rails/activestorage/lib/active_storage/service/configurator.rb:8:in `build' 2: from /Users/yahonda/src/github.com/rails/rails/activestorage/lib/active_storage/service/configurator.rb:17:in `build' 1: from /Users/yahonda/src/github.com/rails/rails/activestorage/lib/active_storage/service/configurator.rb:29:in `resolve' /Users/yahonda/src/github.com/rails/rails/activestorage/lib/active_storage/service/configurator.rb:33:in `rescue in resolve': Missing service adapter for "AzureStorage" (RuntimeError) rake aborted! ``` * Update Gemfile.lock to bump azure-storage-blob version ``` % bundle update --conservative faraday azure-storage-blob google-cloud-storage` ``` - How to find gem name to update by setting `gem "azure-storage-blob", "= 2.0.0"` temporarily ```ruby % git diff diff --git a/Gemfile b/Gemfile index 5fdaceab2f..6be7dccf4b 100644 --- a/Gemfile +++ b/Gemfile @@ -84,7 +84,7 @@ end group :storage do gem "aws-sdk-s3", require: false gem "google-cloud-storage", "~> 1.11", require: false - gem "azure-storage-blob", require: false + gem "azure-storage-blob", "= 2.0.0", require: false # Use 2.0.0 temporarily to find which gems need bump gem "image_processing", "~> 1.2" end % bundle install Fetching gem metadata from https://rubygems.org/......... Fetching gem metadata from https://rubygems.org/. Resolving dependencies..... Bundler could not find compatible versions for gem "faraday": In snapshot (Gemfile.lock): faraday (= 0.17.1) In Gemfile: azure-storage-blob (= 2.0.0) was resolved to 2.0.0, which depends on azure-storage-common (~> 2.0) was resolved to 2.0.1, which depends on faraday (~> 1.0) google-cloud-storage (~> 1.11) was resolved to 1.25.0, which depends on googleauth (~> 0.9) was resolved to 0.10.0, which depends on faraday (~> 0.12) Running `bundle update` will rebuild your snapshot from scratch, using only the gems in your Gemfile, which may resolve the conflict. % git checkout -f Gemfile % bundle update --conservative faraday azure-storage-blob google-cloud-storage ```
2020-03-16 18:38:22 +08:00
google-cloud-errors (~> 1.0)
Upgrade the development Gemfile.lock
2021-04-14 02:18:28 +08:00
google-cloud-env (1.5.0)
Unlock `azure-storage-blob` version to use version 2.0 `azure-storage-blob` 2.0.0 has been released. https://rubygems.org/gems/azure-storage-blob/versions/2.0.0 According to this commit and changelog, `azure-storage-blob` 1.1.0 did not support Ruby 2.6 and higher. As of right now, Rails master branch should support Ruby 2.5.0, 2.6.0 and 2.7.0 then it should be appropriate to unlock `azure-storage-blob` version. https://github.com/Azure/azure-storage-ruby/commit/252e3f06a5cf2e2583302bfefa95d8b25818a44f This commit addresses this following error: ```ruby % cd activestorage % bundle exec rake test Traceback (most recent call last): 14: from /Users/yahonda/.rbenv/versions/2.6.5/lib/ruby/gems/2.6.0/gems/rake-13.0.1/lib/rake/rake_test_loader.rb:5:in `<main>' 13: from /Users/yahonda/.rbenv/versions/2.6.5/lib/ruby/gems/2.6.0/gems/rake-13.0.1/lib/rake/rake_test_loader.rb:5:in `select' 12: from /Users/yahonda/.rbenv/versions/2.6.5/lib/ruby/gems/2.6.0/gems/rake-13.0.1/lib/rake/rake_test_loader.rb:17:in `block in <main>' 11: from /Users/yahonda/.rbenv/versions/2.6.5/lib/ruby/gems/2.6.0/gems/zeitwerk-2.3.0/lib/zeitwerk/kernel.rb:23:in `require' 10: from /Users/yahonda/.rbenv/versions/2.6.5/lib/ruby/gems/2.6.0/gems/zeitwerk-2.3.0/lib/zeitwerk/kernel.rb:23:in `require' 9: from /Users/yahonda/src/github.com/rails/rails/activestorage/test/service/azure_storage_service_test.rb:7:in `<top (required)>' 8: from /Users/yahonda/src/github.com/rails/rails/activestorage/test/service/azure_storage_service_test.rb:8:in `<class:AzureStorageServiceTest>' 7: from /Users/yahonda/src/github.com/rails/rails/activestorage/lib/active_storage/service.rb:51:in `configure' 6: from /Users/yahonda/src/github.com/rails/rails/activestorage/lib/active_storage/service/configurator.rb:8:in `build' 5: from /Users/yahonda/src/github.com/rails/rails/activestorage/lib/active_storage/service/configurator.rb:17:in `build' 4: from /Users/yahonda/src/github.com/rails/rails/activestorage/lib/active_storage/service/configurator.rb:30:in `resolve' 3: from /Users/yahonda/.rbenv/versions/2.6.5/lib/ruby/gems/2.6.0/gems/zeitwerk-2.3.0/lib/zeitwerk/kernel.rb:23:in `require' 2: from /Users/yahonda/.rbenv/versions/2.6.5/lib/ruby/gems/2.6.0/gems/zeitwerk-2.3.0/lib/zeitwerk/kernel.rb:23:in `require' 1: from /Users/yahonda/src/github.com/rails/rails/activestorage/lib/active_storage/service/azure_storage_service.rb:3:in `<top (required)>' /Users/yahonda/.rbenv/versions/2.6.5/lib/ruby/gems/2.6.0/gems/bundler-2.1.4/lib/bundler/rubygems_integration.rb:346:in `block (2 levels) in replace_gem': can't activate azure-storage-blob (~> 1.1), already activated azure-storage-blob-2.0.0. Make sure all dependencies are added to Gemfile. (Gem::LoadError) 11: from /Users/yahonda/.rbenv/versions/2.6.5/lib/ruby/gems/2.6.0/gems/rake-13.0.1/lib/rake/rake_test_loader.rb:5:in `<main>' 10: from /Users/yahonda/.rbenv/versions/2.6.5/lib/ruby/gems/2.6.0/gems/rake-13.0.1/lib/rake/rake_test_loader.rb:5:in `select' 9: from /Users/yahonda/.rbenv/versions/2.6.5/lib/ruby/gems/2.6.0/gems/rake-13.0.1/lib/rake/rake_test_loader.rb:17:in `block in <main>' 8: from /Users/yahonda/.rbenv/versions/2.6.5/lib/ruby/gems/2.6.0/gems/zeitwerk-2.3.0/lib/zeitwerk/kernel.rb:23:in `require' 7: from /Users/yahonda/.rbenv/versions/2.6.5/lib/ruby/gems/2.6.0/gems/zeitwerk-2.3.0/lib/zeitwerk/kernel.rb:23:in `require' 6: from /Users/yahonda/src/github.com/rails/rails/activestorage/test/service/azure_storage_service_test.rb:7:in `<top (required)>' 5: from /Users/yahonda/src/github.com/rails/rails/activestorage/test/service/azure_storage_service_test.rb:8:in `<class:AzureStorageServiceTest>' 4: from /Users/yahonda/src/github.com/rails/rails/activestorage/lib/active_storage/service.rb:51:in `configure' 3: from /Users/yahonda/src/github.com/rails/rails/activestorage/lib/active_storage/service/configurator.rb:8:in `build' 2: from /Users/yahonda/src/github.com/rails/rails/activestorage/lib/active_storage/service/configurator.rb:17:in `build' 1: from /Users/yahonda/src/github.com/rails/rails/activestorage/lib/active_storage/service/configurator.rb:29:in `resolve' /Users/yahonda/src/github.com/rails/rails/activestorage/lib/active_storage/service/configurator.rb:33:in `rescue in resolve': Missing service adapter for "AzureStorage" (RuntimeError) rake aborted! ``` * Update Gemfile.lock to bump azure-storage-blob version ``` % bundle update --conservative faraday azure-storage-blob google-cloud-storage` ``` - How to find gem name to update by setting `gem "azure-storage-blob", "= 2.0.0"` temporarily ```ruby % git diff diff --git a/Gemfile b/Gemfile index 5fdaceab2f..6be7dccf4b 100644 --- a/Gemfile +++ b/Gemfile @@ -84,7 +84,7 @@ end group :storage do gem "aws-sdk-s3", require: false gem "google-cloud-storage", "~> 1.11", require: false - gem "azure-storage-blob", require: false + gem "azure-storage-blob", "= 2.0.0", require: false # Use 2.0.0 temporarily to find which gems need bump gem "image_processing", "~> 1.2" end % bundle install Fetching gem metadata from https://rubygems.org/......... Fetching gem metadata from https://rubygems.org/. Resolving dependencies..... Bundler could not find compatible versions for gem "faraday": In snapshot (Gemfile.lock): faraday (= 0.17.1) In Gemfile: azure-storage-blob (= 2.0.0) was resolved to 2.0.0, which depends on azure-storage-common (~> 2.0) was resolved to 2.0.1, which depends on faraday (~> 1.0) google-cloud-storage (~> 1.11) was resolved to 1.25.0, which depends on googleauth (~> 0.9) was resolved to 0.10.0, which depends on faraday (~> 0.12) Running `bundle update` will rebuild your snapshot from scratch, using only the gems in your Gemfile, which may resolve the conflict. % git checkout -f Gemfile % bundle update --conservative faraday azure-storage-blob google-cloud-storage ```
2020-03-16 18:38:22 +08:00
faraday (>= 0.17.3, < 2.0)
Upgrade the development Gemfile.lock
2021-04-14 02:18:28 +08:00
google-cloud-errors (1.1.0)
Update development gems
2021-06-09 07:27:47 +08:00
google-cloud-storage (1.31.1)
Bundle update
2019-10-10 12:48:16 +08:00
addressable (~> 2.5)
Resolve gemspec typo
2017-08-01 04:55:55 +08:00
digest-crc (~> 0.4)
Upgrade all the gems to make sure we are testing with the latest versions locally
2021-01-22 05:22:41 +08:00
google-apis-iamcredentials_v1 (~> 0.1)
google-apis-storage_v1 (~> 0.1)
Support streaming downloads from Google Cloud Storage
2018-05-02 11:20:56 +08:00
google-cloud-core (~> 1.2)
Fix test with new capybara
2019-12-28 02:30:45 +08:00
googleauth (~> 0.9)
Bundle update
2019-10-10 12:48:16 +08:00
mini_mime (~> 1.0)
Update development gems
2021-06-09 07:27:47 +08:00
googleauth (0.16.2)
Unlock `azure-storage-blob` version to use version 2.0 `azure-storage-blob` 2.0.0 has been released. https://rubygems.org/gems/azure-storage-blob/versions/2.0.0 According to this commit and changelog, `azure-storage-blob` 1.1.0 did not support Ruby 2.6 and higher. As of right now, Rails master branch should support Ruby 2.5.0, 2.6.0 and 2.7.0 then it should be appropriate to unlock `azure-storage-blob` version. https://github.com/Azure/azure-storage-ruby/commit/252e3f06a5cf2e2583302bfefa95d8b25818a44f This commit addresses this following error: ```ruby % cd activestorage % bundle exec rake test Traceback (most recent call last): 14: from /Users/yahonda/.rbenv/versions/2.6.5/lib/ruby/gems/2.6.0/gems/rake-13.0.1/lib/rake/rake_test_loader.rb:5:in `<main>' 13: from /Users/yahonda/.rbenv/versions/2.6.5/lib/ruby/gems/2.6.0/gems/rake-13.0.1/lib/rake/rake_test_loader.rb:5:in `select' 12: from /Users/yahonda/.rbenv/versions/2.6.5/lib/ruby/gems/2.6.0/gems/rake-13.0.1/lib/rake/rake_test_loader.rb:17:in `block in <main>' 11: from /Users/yahonda/.rbenv/versions/2.6.5/lib/ruby/gems/2.6.0/gems/zeitwerk-2.3.0/lib/zeitwerk/kernel.rb:23:in `require' 10: from /Users/yahonda/.rbenv/versions/2.6.5/lib/ruby/gems/2.6.0/gems/zeitwerk-2.3.0/lib/zeitwerk/kernel.rb:23:in `require' 9: from /Users/yahonda/src/github.com/rails/rails/activestorage/test/service/azure_storage_service_test.rb:7:in `<top (required)>' 8: from /Users/yahonda/src/github.com/rails/rails/activestorage/test/service/azure_storage_service_test.rb:8:in `<class:AzureStorageServiceTest>' 7: from /Users/yahonda/src/github.com/rails/rails/activestorage/lib/active_storage/service.rb:51:in `configure' 6: from /Users/yahonda/src/github.com/rails/rails/activestorage/lib/active_storage/service/configurator.rb:8:in `build' 5: from /Users/yahonda/src/github.com/rails/rails/activestorage/lib/active_storage/service/configurator.rb:17:in `build' 4: from /Users/yahonda/src/github.com/rails/rails/activestorage/lib/active_storage/service/configurator.rb:30:in `resolve' 3: from /Users/yahonda/.rbenv/versions/2.6.5/lib/ruby/gems/2.6.0/gems/zeitwerk-2.3.0/lib/zeitwerk/kernel.rb:23:in `require' 2: from /Users/yahonda/.rbenv/versions/2.6.5/lib/ruby/gems/2.6.0/gems/zeitwerk-2.3.0/lib/zeitwerk/kernel.rb:23:in `require' 1: from /Users/yahonda/src/github.com/rails/rails/activestorage/lib/active_storage/service/azure_storage_service.rb:3:in `<top (required)>' /Users/yahonda/.rbenv/versions/2.6.5/lib/ruby/gems/2.6.0/gems/bundler-2.1.4/lib/bundler/rubygems_integration.rb:346:in `block (2 levels) in replace_gem': can't activate azure-storage-blob (~> 1.1), already activated azure-storage-blob-2.0.0. Make sure all dependencies are added to Gemfile. (Gem::LoadError) 11: from /Users/yahonda/.rbenv/versions/2.6.5/lib/ruby/gems/2.6.0/gems/rake-13.0.1/lib/rake/rake_test_loader.rb:5:in `<main>' 10: from /Users/yahonda/.rbenv/versions/2.6.5/lib/ruby/gems/2.6.0/gems/rake-13.0.1/lib/rake/rake_test_loader.rb:5:in `select' 9: from /Users/yahonda/.rbenv/versions/2.6.5/lib/ruby/gems/2.6.0/gems/rake-13.0.1/lib/rake/rake_test_loader.rb:17:in `block in <main>' 8: from /Users/yahonda/.rbenv/versions/2.6.5/lib/ruby/gems/2.6.0/gems/zeitwerk-2.3.0/lib/zeitwerk/kernel.rb:23:in `require' 7: from /Users/yahonda/.rbenv/versions/2.6.5/lib/ruby/gems/2.6.0/gems/zeitwerk-2.3.0/lib/zeitwerk/kernel.rb:23:in `require' 6: from /Users/yahonda/src/github.com/rails/rails/activestorage/test/service/azure_storage_service_test.rb:7:in `<top (required)>' 5: from /Users/yahonda/src/github.com/rails/rails/activestorage/test/service/azure_storage_service_test.rb:8:in `<class:AzureStorageServiceTest>' 4: from /Users/yahonda/src/github.com/rails/rails/activestorage/lib/active_storage/service.rb:51:in `configure' 3: from /Users/yahonda/src/github.com/rails/rails/activestorage/lib/active_storage/service/configurator.rb:8:in `build' 2: from /Users/yahonda/src/github.com/rails/rails/activestorage/lib/active_storage/service/configurator.rb:17:in `build' 1: from /Users/yahonda/src/github.com/rails/rails/activestorage/lib/active_storage/service/configurator.rb:29:in `resolve' /Users/yahonda/src/github.com/rails/rails/activestorage/lib/active_storage/service/configurator.rb:33:in `rescue in resolve': Missing service adapter for "AzureStorage" (RuntimeError) rake aborted! ``` * Update Gemfile.lock to bump azure-storage-blob version ``` % bundle update --conservative faraday azure-storage-blob google-cloud-storage` ``` - How to find gem name to update by setting `gem "azure-storage-blob", "= 2.0.0"` temporarily ```ruby % git diff diff --git a/Gemfile b/Gemfile index 5fdaceab2f..6be7dccf4b 100644 --- a/Gemfile +++ b/Gemfile @@ -84,7 +84,7 @@ end group :storage do gem "aws-sdk-s3", require: false gem "google-cloud-storage", "~> 1.11", require: false - gem "azure-storage-blob", require: false + gem "azure-storage-blob", "= 2.0.0", require: false # Use 2.0.0 temporarily to find which gems need bump gem "image_processing", "~> 1.2" end % bundle install Fetching gem metadata from https://rubygems.org/......... Fetching gem metadata from https://rubygems.org/. Resolving dependencies..... Bundler could not find compatible versions for gem "faraday": In snapshot (Gemfile.lock): faraday (= 0.17.1) In Gemfile: azure-storage-blob (= 2.0.0) was resolved to 2.0.0, which depends on azure-storage-common (~> 2.0) was resolved to 2.0.1, which depends on faraday (~> 1.0) google-cloud-storage (~> 1.11) was resolved to 1.25.0, which depends on googleauth (~> 0.9) was resolved to 0.10.0, which depends on faraday (~> 0.12) Running `bundle update` will rebuild your snapshot from scratch, using only the gems in your Gemfile, which may resolve the conflict. % git checkout -f Gemfile % bundle update --conservative faraday azure-storage-blob google-cloud-storage ```
2020-03-16 18:38:22 +08:00
faraday (>= 0.17.3, < 2.0)
Use `credentials` instead of `keyfile` in GCS sevice The `keyfile` was renamed to `credentials` in `google-cloud-storage` 1.8.0. https://github.com/GoogleCloudPlatform/google-cloud-ruby/blob/master/google-cloud-storage/CHANGELOG.md#180--2017-11-14 Although `keyfile` can still be used, but it looks like deprecate. https://github.com/GoogleCloudPlatform/google-cloud-ruby/blob/ddf7b2a856d676316525eb581c1a4cc83ca6097b/google-cloud-storage/lib/google/cloud/storage.rb#L589...L590 Therefore, I think that should use `credentials` in newly generated applications. Ref: https://github.com/GoogleCloudPlatform/google-cloud-ruby/issues/1802
2017-11-29 12:08:33 +08:00
jwt (>= 1.4, < 3.0)
bundle update
2018-11-10 06:21:08 +08:00
memoist (~> 0.16)
Resolve gemspec typo
2017-08-01 04:55:55 +08:00
multi_json (~> 1.11)
Upgrade all the gems
2018-09-06 05:41:31 +08:00
os (>= 0.9, < 2.0)
Update w3c_validtors for Ruby 3 compatibility (#40227) * Update w3c_validtors for Ruby 3 compatibility * Update google-api-client for Ruby 3 compatibility
2020-09-21 13:19:59 +08:00
signet (~> 0.14)
Upgrade all the gems
2020-11-04 14:39:41 +08:00
hashdiff (1.0.1)
bundle update
2018-11-10 06:21:08 +08:00
hiredis (0.6.3)
Remove Blade gem dependency Apps that depend on Action Cable don't need Blade for app development, so we can remove the gem dependency. We do need Blade for Action Cable dev, so we bundle it in the Gemfile. Signed-off-by: Jeremy Daer <jeremydaer@gmail.com>
2016-05-22 02:15:58 +08:00
http_parser.rb (0.6.0)
Resolve gemspec typo
2017-08-01 04:55:55 +08:00
httpclient (2.8.3)
Use `ActiveRecord::FixtureSet.signed_global_id` defined by the globalid gem Also make explicit that actiontext depends on the globalid gem.
2021-11-25 06:33:45 +08:00
i18n (1.8.11)
Preparing for 5.2.0.beta1 release
2017-11-28 02:01:15 +08:00
concurrent-ruby (~> 1.0)
Upgrade all the gems to make sure we are testing with the latest versions locally
2021-01-22 05:22:41 +08:00
image_processing (1.12.1)
Bundle update
2019-10-10 12:48:16 +08:00
mini_magick (>= 4.9.5, < 5)
Bump image_processing gem version since it fixes ruby 2.7 warnings
2020-01-08 04:40:28 +08:00
ruby-vips (>= 2.0.17, < 3)
Make Sprockets more optional, offer Propshaft as alternative (#43261) * Make Sprockets more optional, offer Propshaft as alternative * Whups, local reference * No longer used * Spacing * Need explicit sprockets-rails inclusion now * Manually require the sprockets railtie * Don't need these changes right now * Kick off another build * Fix tests * DRY up test * Require railtie when using sprockets * Introduce option to skip asset pipeline * No longer relevant * Always have to return * Gone * Add helper for skip_sprockets? * Fix guard statement * Use latest gems * Include propshaft * fix tests for #43261 (#43277) * help fix tests for #43261 skip_sprockets? should not be called on options :skip_sprockets is no longer a value in the option hash, so skip_sprockets? should not be called on it move --asset-pipeline to shared generator skip_sprockets? is defined on app_base, and used in the plugin generator to determine whether to add the engine's assets to the dummy sprockets manifest, so I believe it makes sense to include in both generators Because of this change, I also changed the shared test back to testing against non-sprockets add skip_sprockets to Gemfile template vars Mocking skip_sprockets? in app_base generator fix more generator tests * use skip_sprockets? everywhere * Use latest propshaft * Update `AssetUrlHelper` docs to list both asset pipeline gems (#43328) * Update to latest Propshaft * Bump Propshaft again * Ask for latest * Use latest propshaft Co-authored-by: Hartley McGuire <skipkayhil@gmail.com> Co-authored-by: Richard Macklin <1863540+rmacklin@users.noreply.github.com>
2021-10-09 23:03:05 +08:00
importmap-rails (0.7.3)
Replace webpack with importmapped Hotwire as default js (#42999) * Turbolinks is being replaced with Hotwire * Make --webpack opt-in * Don't use specific webpacker installers any more in preparation for next Webpacker * Update railties/lib/rails/app_updater.rb Co-authored-by: Alex Ghiculescu <alex@tanda.co> * Trailing whitespace * Convert to Turbo data attribute for tracking * Default is no webpack, no hotwire * Swap out turbolinks references for hotwire * Drop explicit return * Only generate package.json if using webpack * Only create package.json in webpack mode * Only create app/javascript in webpack mode * Generate correct style/js links based on js mode * Fix tests from changed output format Not sure why these are showing up in this PR, though. * Rubocopping * Stick with webpack for the test app for now * Adjust tests * Replace minitest-reporters with minitest-ci (#43016) minitest-reporters is used to create junit xml reports on CI. But when it loads before rails minitest plugin makes `Rails::TestUnitReporter` not being added as a reporter. minitest-ci is now only loaded at ci and does not interferes with rails minitest plugins. And keeps junit reports workings * Too heavy handed to actually run bundle Just like we don't auto-migrate * Pin js frameworks in importmap Instead of having importmap preconfigure it. * Match updated app/javascript path * No need for the explaining comment * Fixes test cases for replace webpack with importmapped Hotwire as default js (#42999) * Fix rubocop issues * Fix more railities test cases * Fix plugin generator railties shared test cases * Fix Action Text install generator asset pipeline spec * They're modules, not files * Let dev use the latest release as well So we don't have to replace unexisting dev releases with latest release * Make Webpack responsible for generating all the JS files it needs Webpacker 6 has already moved from app/javascript to app/packs. * Don't add rails/ujs by default any longer All the ajax/form functionality has been superseded by Turbo. The rest lives in a weird inbetween land we need to address through other means. * Use new importmap location * Switch to using turbo-rails and stimulus-rails directly The hotwire-rails gem does not offer enough value for its indirection * Use latest Webpacker * Prevent version resolution requests from getting swallowed * Use ESM syntax for imports * Move management of yarn, package.json, etc to Webpacker 6 * Update for Webpacker 6 * Move bin/setup addition to Webpacker as well * Remove dead tests * Bump to Webpacker 6.0.0.rc.2 * No longer relevant given the new default is no webpacker * Rely on Webpacker 6 * No longer relevant * No longer relevant * Make cable channel generator work for both webpacker and importmap setups * Fix tests * For tests testing importmap way * Use Webpacker 6 dummy * RuboCopping * One more bump to fix webpack-dev-server * Another bump. Hopefully the last one! * Also enough to not want turbo tracking on * Fix tests * Latest * Fix tests * Fix more tests * Fix tests Co-authored-by: Alex Ghiculescu <alex@tanda.co> Co-authored-by: André Luis Leal Cardoso Junior <andrehjr@gmail.com> Co-authored-by: Abhay Nikam <nikam.abhay1@gmail.com> Co-authored-by: Guillermo Iguaran <guilleiguaran@gmail.com>
2021-08-26 16:39:36 +08:00
rails (>= 6.0.0)
Depend on ruby/debug, replacing Byebug ruby/debug is a new debugger that is going to ship with CRuby. It makes sense for Rails to switch to this one because that is where the language is heading, and because Byebug is not fully compatible with Zeitwerk. See https://github.com/deivid-rodriguez/byebug/issues/564 While ruby/debug has not been heavily tested with Zeitwerk, casual usage seems to suggest it works without issues, including explicit namespaces, which is where Byebug and Zeitwerk conflict. Byebug is terrific, thanks a lot for all these years. :heart:
2021-09-08 23:35:41 +08:00
io-console (0.5.9)
irb (1.3.7)
reline (>= 0.2.7)
Bundle update
2018-05-31 01:49:55 +08:00
jmespath (1.4.0)
Make Sprockets more optional, offer Propshaft as alternative (#43261) * Make Sprockets more optional, offer Propshaft as alternative * Whups, local reference * No longer used * Spacing * Need explicit sprockets-rails inclusion now * Manually require the sprockets railtie * Don't need these changes right now * Kick off another build * Fix tests * DRY up test * Require railtie when using sprockets * Introduce option to skip asset pipeline * No longer relevant * Always have to return * Gone * Add helper for skip_sprockets? * Fix guard statement * Use latest gems * Include propshaft * fix tests for #43261 (#43277) * help fix tests for #43261 skip_sprockets? should not be called on options :skip_sprockets is no longer a value in the option hash, so skip_sprockets? should not be called on it move --asset-pipeline to shared generator skip_sprockets? is defined on app_base, and used in the plugin generator to determine whether to add the engine's assets to the dummy sprockets manifest, so I believe it makes sense to include in both generators Because of this change, I also changed the shared test back to testing against non-sprockets add skip_sprockets to Gemfile template vars Mocking skip_sprockets? in app_base generator fix more generator tests * use skip_sprockets? everywhere * Use latest propshaft * Update `AssetUrlHelper` docs to list both asset pipeline gems (#43328) * Update to latest Propshaft * Bump Propshaft again * Ask for latest * Use latest propshaft Co-authored-by: Hartley McGuire <skipkayhil@gmail.com> Co-authored-by: Richard Macklin <1863540+rmacklin@users.noreply.github.com>
2021-10-09 23:03:05 +08:00
jsbundling-rails (0.1.7)
railties (>= 6.0.0)
Upgrade all the gems to make sure we are testing with the latest versions locally
2021-01-22 05:22:41 +08:00
json (2.5.1)
Update development gems
2021-06-09 07:27:47 +08:00
jwt (2.2.3)
Fix rake guides:generate:kindle error
2016-12-18 23:13:50 +08:00
kindlerb (1.2.0)
Track Gemfile.lock at the repository The main reason is to make bisect easier. In some points, we have a lot of git dependencies. Since we don't have the information of which commit we are referring to, bundler get the latest commit of the master branch of the dependency. This sometimes returns a version that is not compatible with Rails anymore, making the tests fail and the harder to identify the commit that introduced a bug. Also this will make sure that a contributor will always get a set of dependencies that are passing with our tests. In our CI server we delete the lock file to make sure we are always testing against the newest release of our dependencies.
2015-02-19 00:30:25 +08:00
mustache
nokogiri
Upgrade all the gems to make sure we are testing with the latest versions locally
2021-01-22 05:22:41 +08:00
libxml-ruby (3.2.1)
Stop trying to configure listen by default on compatible platforms (#42985) * Stop trying to configure listen by default on compatible platforms Modern computers with SSDs don't see much/any benefit from having an evented file update watcher. Remove complexity by taking this spinning-drive concession out. * Actually need listen for testing the opt-in * Test no longer relevant
2021-08-11 21:18:43 +08:00
listen (3.6.0)
Update listen gem to v3.3 Version 3.3 fixes memory leaks that occur when stopping individual listeners (see guard/listen#476).
2020-11-10 23:52:20 +08:00
rb-fsevent (~> 0.10, >= 0.10.3)
rb-inotify (~> 0.9, >= 0.9.10)
Preparing for 7.0.0.alpha1 release
2021-09-16 05:55:08 +08:00
loofah (2.12.0)
Preparing for 5.2.0.beta1 release
2017-11-28 02:01:15 +08:00
crass (~> 1.0.2)
Track Gemfile.lock at the repository The main reason is to make bisect easier. In some points, we have a lot of git dependencies. Since we don't have the information of which commit we are referring to, bundler get the latest commit of the master branch of the dependency. This sometimes returns a version that is not compatible with Rails anymore, making the tests fail and the harder to identify the commit that introduced a bug. Also this will make sure that a contributor will always get a set of dependencies that are passing with our tests. In our CI server we delete the lock file to make sure we are always testing against the newest release of our dependencies.
2015-02-19 00:30:25 +08:00
nokogiri (>= 1.5.9)
Bump mail to `2.7.1`
2018-10-14 07:33:40 +08:00
mail (2.7.1)
Fix tests on Mail 2.7 Reverts 4d96be1c27bd6faed957b197a461f18543acebf2 References #31026
2017-11-01 12:44:55 +08:00
mini_mime (>= 0.1.1)
Use `ActiveRecord::FixtureSet.signed_global_id` defined by the globalid gem Also make explicit that actiontext depends on the globalid gem.
2021-11-25 06:33:45 +08:00
marcel (1.0.2)
Upgrade capybara to work with Ruby 3.1 and earlier
2021-12-09 05:44:11 +08:00
matrix (0.4.2)
Fix test with new capybara
2019-12-28 02:30:45 +08:00
memoist (0.16.2)
Preparing for 6.1.0.rc1 release
2020-11-03 05:12:47 +08:00
method_source (1.0.0)
Upgrade all the gems to make sure we are testing with the latest versions locally
2021-01-22 05:22:41 +08:00
mini_magick (4.11.0)
Use `ActiveRecord::FixtureSet.signed_global_id` defined by the globalid gem Also make explicit that actiontext depends on the globalid gem.
2021-11-25 06:33:45 +08:00
mini_mime (1.1.2)
Upgrade development gems
2021-06-18 04:26:38 +08:00
mini_portile2 (2.5.3)
Upgrade the development Gemfile.lock
2021-04-14 02:18:28 +08:00
minitest (5.14.4)
Bundle update
2019-10-10 12:48:16 +08:00
minitest-bisect (1.5.1)
Add minitest-bisect as part of the gemfile
2016-07-12 14:06:25 +08:00
minitest-server (~> 1.0)
Bundle update
2019-10-10 12:48:16 +08:00
path_expander (~> 1.1)
Replace webpack with importmapped Hotwire as default js (#42999) * Turbolinks is being replaced with Hotwire * Make --webpack opt-in * Don't use specific webpacker installers any more in preparation for next Webpacker * Update railties/lib/rails/app_updater.rb Co-authored-by: Alex Ghiculescu <alex@tanda.co> * Trailing whitespace * Convert to Turbo data attribute for tracking * Default is no webpack, no hotwire * Swap out turbolinks references for hotwire * Drop explicit return * Only generate package.json if using webpack * Only create package.json in webpack mode * Only create app/javascript in webpack mode * Generate correct style/js links based on js mode * Fix tests from changed output format Not sure why these are showing up in this PR, though. * Rubocopping * Stick with webpack for the test app for now * Adjust tests * Replace minitest-reporters with minitest-ci (#43016) minitest-reporters is used to create junit xml reports on CI. But when it loads before rails minitest plugin makes `Rails::TestUnitReporter` not being added as a reporter. minitest-ci is now only loaded at ci and does not interferes with rails minitest plugins. And keeps junit reports workings * Too heavy handed to actually run bundle Just like we don't auto-migrate * Pin js frameworks in importmap Instead of having importmap preconfigure it. * Match updated app/javascript path * No need for the explaining comment * Fixes test cases for replace webpack with importmapped Hotwire as default js (#42999) * Fix rubocop issues * Fix more railities test cases * Fix plugin generator railties shared test cases * Fix Action Text install generator asset pipeline spec * They're modules, not files * Let dev use the latest release as well So we don't have to replace unexisting dev releases with latest release * Make Webpack responsible for generating all the JS files it needs Webpacker 6 has already moved from app/javascript to app/packs. * Don't add rails/ujs by default any longer All the ajax/form functionality has been superseded by Turbo. The rest lives in a weird inbetween land we need to address through other means. * Use new importmap location * Switch to using turbo-rails and stimulus-rails directly The hotwire-rails gem does not offer enough value for its indirection * Use latest Webpacker * Prevent version resolution requests from getting swallowed * Use ESM syntax for imports * Move management of yarn, package.json, etc to Webpacker 6 * Update for Webpacker 6 * Move bin/setup addition to Webpacker as well * Remove dead tests * Bump to Webpacker 6.0.0.rc.2 * No longer relevant given the new default is no webpacker * Rely on Webpacker 6 * No longer relevant * No longer relevant * Make cable channel generator work for both webpacker and importmap setups * Fix tests * For tests testing importmap way * Use Webpacker 6 dummy * RuboCopping * One more bump to fix webpack-dev-server * Another bump. Hopefully the last one! * Also enough to not want turbo tracking on * Fix tests * Latest * Fix tests * Fix more tests * Fix tests Co-authored-by: Alex Ghiculescu <alex@tanda.co> Co-authored-by: André Luis Leal Cardoso Junior <andrehjr@gmail.com> Co-authored-by: Abhay Nikam <nikam.abhay1@gmail.com> Co-authored-by: Guillermo Iguaran <guilleiguaran@gmail.com>
2021-08-26 16:39:36 +08:00
minitest-ci (3.4.0)
minitest (>= 5.0.6)
Update development gems
2021-06-09 07:27:47 +08:00
minitest-retry (0.2.2)
Add test retries for railties
2018-10-11 06:33:09 +08:00
minitest (>= 5.0)
Fix test with new capybara
2019-12-28 02:30:45 +08:00
minitest-server (1.0.6)
Fix minitest version constraints in Gemfile.lock Followup to e803ab6e80e2fc0b772e2135ce85111cdce23e2f. The dependencies of each entry are alphasorted, and minitest-server's version constraint is still pessimistic.
2020-06-01 18:59:27 +08:00
minitest (~> 5.0)
Upgrade the development Gemfile.lock
2021-04-14 02:18:28 +08:00
mono_logger (1.1.1)
msgpack (1.4.2)
Update w3c_validtors for Ruby 3 compatibility (#40227) * Update w3c_validtors for Ruby 3 compatibility * Update google-api-client for Ruby 3 compatibility
2020-09-21 13:19:59 +08:00
multi_json (1.15.0)
Bundle update
2019-10-10 12:48:16 +08:00
multipart-post (2.1.1)
Fix test with new capybara
2019-12-28 02:30:45 +08:00
mustache (1.1.1)
Upgrade all the gems
2020-11-04 14:39:41 +08:00
mustermann (1.1.1)
ruby2_keywords (~> 0.0.1)
Upgrade all the gems to make sure we are testing with the latest versions locally
2021-01-22 05:22:41 +08:00
net-http-persistent (4.0.1)
connection_pool (~> 2.2)
Use `ActiveRecord::FixtureSet.signed_global_id` defined by the globalid gem Also make explicit that actiontext depends on the globalid gem.
2021-11-25 06:33:45 +08:00
nio4r (2.5.8)
Upgrade development gems
2021-06-18 04:26:38 +08:00
nokogiri (1.11.7)
mini_portile2 (~> 2.5.0)
racc (~> 1.4)
Update development gems
2021-06-09 07:27:47 +08:00
nokogiri (1.11.7-x86_64-darwin)
Upgrade all the gems to make sure we are testing with the latest versions locally
2021-01-22 05:22:41 +08:00
racc (~> 1.4)
Update development gems
2021-06-09 07:27:47 +08:00
nokogiri (1.11.7-x86_64-linux)
Upgrade all the gems to make sure we are testing with the latest versions locally
2021-01-22 05:22:41 +08:00
racc (~> 1.4)
Update w3c_validtors for Ruby 3 compatibility (#40227) * Update w3c_validtors for Ruby 3 compatibility * Update google-api-client for Ruby 3 compatibility
2020-09-21 13:19:59 +08:00
os (1.1.1)
Upgrade all the gems to make sure we are testing with the latest versions locally
2021-01-22 05:22:41 +08:00
parallel (1.20.1)
Enforce standardizing nodoc comments by rubocop Follow up to 18707ab1, b87d8e51. rubocop 1.19.0 includes https://github.com/rubocop/rubocop/pull/9964.
2021-08-12 19:01:37 +08:00
parser (3.0.2.0)
Update RuboCop to v0.90 Signed-off-by: Utkarsh Gupta <utkarsh@debian.org>
2020-09-06 09:07:04 +08:00
ast (~> 2.4.1)
Bundle update
2019-10-10 12:48:16 +08:00
path_expander (1.1.0)
Updates pg gem version
2020-03-30 18:05:56 +08:00
pg (1.2.3)
Make Sprockets more optional, offer Propshaft as alternative (#43261) * Make Sprockets more optional, offer Propshaft as alternative * Whups, local reference * No longer used * Spacing * Need explicit sprockets-rails inclusion now * Manually require the sprockets railtie * Don't need these changes right now * Kick off another build * Fix tests * DRY up test * Require railtie when using sprockets * Introduce option to skip asset pipeline * No longer relevant * Always have to return * Gone * Add helper for skip_sprockets? * Fix guard statement * Use latest gems * Include propshaft * fix tests for #43261 (#43277) * help fix tests for #43261 skip_sprockets? should not be called on options :skip_sprockets is no longer a value in the option hash, so skip_sprockets? should not be called on it move --asset-pipeline to shared generator skip_sprockets? is defined on app_base, and used in the plugin generator to determine whether to add the engine's assets to the dummy sprockets manifest, so I believe it makes sense to include in both generators Because of this change, I also changed the shared test back to testing against non-sprockets add skip_sprockets to Gemfile template vars Mocking skip_sprockets? in app_base generator fix more generator tests * use skip_sprockets? everywhere * Use latest propshaft * Update `AssetUrlHelper` docs to list both asset pipeline gems (#43328) * Update to latest Propshaft * Bump Propshaft again * Ask for latest * Use latest propshaft Co-authored-by: Hartley McGuire <skipkayhil@gmail.com> Co-authored-by: Richard Macklin <1863540+rmacklin@users.noreply.github.com>
2021-10-09 23:03:05 +08:00
propshaft (0.1.7)
rails (>= 7.0.0.alpha2)
Update development gems
2021-06-09 07:27:47 +08:00
psych (3.3.2)
Update w3c_validtors for Ruby 3 compatibility (#40227) * Update w3c_validtors for Ruby 3 compatibility * Update google-api-client for Ruby 3 compatibility
2020-09-21 13:19:59 +08:00
public_suffix (4.0.6)
Update development gems
2021-06-09 07:27:47 +08:00
puma (5.3.2)
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 19:21:39 +08:00
nio4r (~> 2.0)
Bundle update
2018-05-31 01:49:55 +08:00
que (0.14.3)
Upgrade all the gems
2020-11-04 14:39:41 +08:00
raabro (1.4.0)
Depend on Zeitwerk 2.5
2021-10-20 20:21:24 +08:00
racc (1.6.0)
Update sidekiq to fix warnings in Active Job tests `Redis#exists(key)` will return an Integer in redis-rb 4.3, if you want to keep the old behavior, use `exists?` instead. To opt-in to the new behavior now you can set Redis.exists_returns_integer = true. (/Users/eugene/.rbenv/versions/2.7.2/lib/ruby/gems/2.7.0/gems/sidekiq-6.0.4/lib/sidekiq/launcher.rb:134:in `block (2 levels) in ❤')
2020-10-04 05:27:05 +08:00
rack (2.2.3)
Upgrade all the gems
2020-11-04 14:39:41 +08:00
rack-cache (1.12.1)
Track Gemfile.lock at the repository The main reason is to make bisect easier. In some points, we have a lot of git dependencies. Since we don't have the information of which commit we are referring to, bundler get the latest commit of the master branch of the dependency. This sometimes returns a version that is not compatible with Rails anymore, making the tests fail and the harder to identify the commit that introduced a bug. Also this will make sure that a contributor will always get a set of dependencies that are passing with our tests. In our CI server we delete the lock file to make sure we are always testing against the newest release of our dependencies.
2015-02-19 00:30:25 +08:00
rack (>= 0.4)
Upgrade all the gems
2020-11-04 14:39:41 +08:00
rack-protection (2.1.0)
Override the github git source instead of changing manually all entries
2016-09-14 08:19:09 +08:00
rack
Upgrade all the gems
2018-09-06 05:41:31 +08:00
rack-test (1.1.0)
Update rack-test dependency constraint
2017-07-20 07:04:53 +08:00
rack (>= 1.0, < 3)
rails-dom-testing (2.0.3)
activesupport (>= 4.2.0)
nokogiri (>= 1.6)
Preparing for 7.0.0.alpha1 release
2021-09-16 05:55:08 +08:00
rails-html-sanitizer (1.4.2)
Bundle update
2019-10-10 12:48:16 +08:00
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-23 07:54:23 +08:00
rainbow (3.0.0)
Depend on Zeitwerk 2.5.0.beta6
2021-10-14 17:12:20 +08:00
rake (13.0.6)
Update development gems
2021-06-09 07:27:47 +08:00
rb-fsevent (0.11.0)
Fix test with new capybara
2019-12-28 02:30:45 +08:00
rb-inotify (0.10.1)
Switch to released rb-inotify 0.10.0 It contains guard/rb-inotify#79, which is what we were waiting for.
2018-12-30 22:05:30 +08:00
ffi (~> 1.0)
Update development gems
2021-06-09 07:27:47 +08:00
rbtree (0.4.4)
Upgrade sdoc to 2.2.0 Sdoc 2.2.0 has improved accessibility and bug fixes. Changelog: * #161 Add 'skip to content' link and improve shortcut keys * #170 Fix link hovers in headings * #169 Fix clearing search results * #167 Update Merge script to work with sdoc v2 * #160 Remove outline from reset stylesheet * #159 Remove TAB override in panel * #157 Move to GitHub action for tests * #155 Fix Ctrl+C copying Jan Schär
2021-05-21 16:06:22 +08:00
rdoc (6.3.1)
redcarpet 3.2.2 has an XSS vulnerability see: http://www.openwall.com/lists/oss-security/2015/04/07/11
2015-04-09 17:20:53 +08:00
redcarpet (3.2.3)
Upgrade development gems
2021-06-18 04:26:38 +08:00
redis (4.3.1)
Use released redis-namespace instead of master branch https://rubygems.org/gems/redis-namespace/versions/1.8.1
2021-02-22 17:48:02 +08:00
redis-namespace (1.8.1)
redis (>= 3.0.4)
Upgrade capybara to work with Ruby 3.1 and earlier
2021-12-09 05:44:11 +08:00
regexp_parser (2.2.0)
Depend on ruby/debug, replacing Byebug ruby/debug is a new debugger that is going to ship with CRuby. It makes sense for Rails to switch to this one because that is where the language is heading, and because Byebug is not fully compatible with Zeitwerk. See https://github.com/deivid-rodriguez/byebug/issues/564 While ruby/debug has not been heavily tested with Zeitwerk, casual usage seems to suggest it works without issues, including explicit namespaces, which is where Byebug and Zeitwerk conflict. Byebug is terrific, thanks a lot for all these years. :heart:
2021-09-08 23:35:41 +08:00
reline (0.2.7)
io-console (~> 0.5)
Upgrade the development Gemfile.lock
2021-04-14 02:18:28 +08:00
representable (3.1.1)
Resolve gemspec typo
2017-08-01 04:55:55 +08:00
declarative (< 0.1.0)
Upgrade the development Gemfile.lock
2021-04-14 02:18:28 +08:00
trailblazer-option (>= 0.1.1, < 0.2.0)
Resolve gemspec typo
2017-08-01 04:55:55 +08:00
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 20:58:20 +08:00
resque (2.0.0)
Use released resque
2017-02-10 14:31:41 +08: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 20:58:20 +08:00
redis-namespace (~> 1.6)
Use released resque
2017-02-10 14:31:41 +08: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 20:58:20 +08: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-14 06:49:08 +08: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 20:58:20 +08: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-14 06:49:08 +08:00
rufus-scheduler (~> 3.2)
Upgrade all the gems
2018-09-06 05:41:31 +08:00
retriable (3.1.2)
Upgrade the development Gemfile.lock
2021-04-14 02:18:28 +08:00
rexml (3.2.5)
Upgrade all the gems to make sure we are testing with the latest versions locally
2021-01-22 05:22:41 +08:00
rouge (3.26.0)
Enforce standardizing nodoc comments by rubocop Follow up to 18707ab1, b87d8e51. rubocop 1.19.0 includes https://github.com/rubocop/rubocop/pull/9964.
2021-08-12 19:01:37 +08:00
rubocop (1.19.0)
Bump rubocop and dependent gem versions
2017-05-24 14:20:00 +08:00
parallel (~> 1.10)
Upgrade all the gems to make sure we are testing with the latest versions locally
2021-01-22 05:22:41 +08:00
parser (>= 3.0.0.0)
Update rubocop to the latest version Includes [Switch Layout/SpaceBeforeBlockBraces's empty braces default](https://github.com/bbatsov/rubocop/pull/5263) from [0.52.1](https://github.com/bbatsov/rubocop/blob/master/CHANGELOG.md#0521-2017-12-27). Before: 131 offenses detected. After: no offenses detected
2018-02-23 07:54:23 +08:00
rainbow (>= 2.2.2, < 4.0)
Upgrade all the gems to make sure we are testing with the latest versions locally
2021-01-22 05:22:41 +08:00
regexp_parser (>= 1.8, < 3.0)
bumping rubocop to 0.80
2020-02-20 23:08:20 +08:00
rexml
Enforce standardizing nodoc comments by rubocop Follow up to 18707ab1, b87d8e51. rubocop 1.19.0 includes https://github.com/rubocop/rubocop/pull/9964.
2021-08-12 19:01:37 +08:00
rubocop-ast (>= 1.9.1, < 2.0)
Add rubocop to Gemfile
2016-11-28 11:12:33 +08:00
ruby-progressbar (~> 1.7)
Upgrade all the gems to make sure we are testing with the latest versions locally
2021-01-22 05:22:41 +08:00
unicode-display_width (>= 1.4.0, < 3.0)
Enforce standardizing nodoc comments by rubocop Follow up to 18707ab1, b87d8e51. rubocop 1.19.0 includes https://github.com/rubocop/rubocop/pull/9964.
2021-08-12 19:01:37 +08:00
rubocop-ast (1.9.1)
Update development gems
2021-06-09 07:27:47 +08:00
parser (>= 3.0.1.1)
Tweak unreachable assertion tests in the block of `assert_raises` I found an unexpected use of assertion in the block of `assert_raise` when I implemented https://github.com/rubocop/rubocop-minitest/pull/137. It is expected to be asserted after an exception is raised in `assert_raise` block, but in actually it is not asserted after an exception is raised. Therefore, this PR removes or updates assertions that have not been asserted after an exception has raised. This PR will add `rubocop-minitest` and enable `Minitest/UnreachableAssertion` cop to able similar auto-detection, but will remove `rubocop-minitest` from this PR if you don't like it.
2021-06-24 18:46:21 +08:00
rubocop-minitest (0.15.0)
rubocop (>= 0.90, < 2.0)
Re-enable `Layout/SpaceAroundOperators` cop We prefer space around operators, but `Layout/SpaceAroundOperators` cop was temporarily disabled in #36943 since that cop changed to check alignment strictly somehow. In RuboCop 1.0.0, that is fixed by https://github.com/rubocop-hq/rubocop/pull/8906. Related https://github.com/rails/rails/pull/38034#discussion_r359845661, https://github.com/rails/rails/pull/39770#discussion_r448829561.
2020-10-22 15:12:38 +08:00
rubocop-packaging (0.5.1)
rubocop (>= 0.89, < 2.0)
Enforce standardizing nodoc comments by rubocop Follow up to 18707ab1, b87d8e51. rubocop 1.19.0 includes https://github.com/rubocop/rubocop/pull/9964.
2021-08-12 19:01:37 +08:00
rubocop-performance (1.11.4)
Enable `Performance/MapCompact` cop Follow up to #42053.
2021-04-23 15:31:19 +08:00
rubocop (>= 1.7.0, < 2.0)
Re-enable `Layout/SpaceAroundOperators` cop We prefer space around operators, but `Layout/SpaceAroundOperators` cop was temporarily disabled in #36943 since that cop changed to check alignment strictly somehow. In RuboCop 1.0.0, that is fixed by https://github.com/rubocop-hq/rubocop/pull/8906. Related https://github.com/rails/rails/pull/38034#discussion_r359845661, https://github.com/rails/rails/pull/39770#discussion_r448829561.
2020-10-22 15:12:38 +08:00
rubocop-ast (>= 0.4.0)
Enforce standardizing nodoc comments by rubocop Follow up to 18707ab1, b87d8e51. rubocop 1.19.0 includes https://github.com/rubocop/rubocop/pull/9964.
2021-08-12 19:01:37 +08:00
rubocop-rails (2.11.3)
Re-enable `Layout/SpaceAroundOperators` cop We prefer space around operators, but `Layout/SpaceAroundOperators` cop was temporarily disabled in #36943 since that cop changed to check alignment strictly somehow. In RuboCop 1.0.0, that is fixed by https://github.com/rubocop-hq/rubocop/pull/8906. Related https://github.com/rails/rails/pull/38034#discussion_r359845661, https://github.com/rails/rails/pull/39770#discussion_r448829561.
2020-10-22 15:12:38 +08:00
activesupport (>= 4.2.0)
Bundle update
2019-10-10 12:48:16 +08:00
rack (>= 1.1)
Update development gems
2021-06-09 07:27:47 +08:00
rubocop (>= 1.7.0, < 2.0)
Upgrade all the gems to make sure we are testing with the latest versions locally
2021-01-22 05:22:41 +08:00
ruby-progressbar (1.11.0)
Update development gems
2021-06-09 07:27:47 +08:00
ruby-vips (2.1.2)
Upgrade the development Gemfile.lock
2021-04-14 02:18:28 +08:00
ffi (~> 1.12)
Upgrade all the gems to make sure we are testing with the latest versions locally
2021-01-22 05:22:41 +08:00
ruby2_keywords (0.0.4)
Rails 7.0 requires selenium-webdriver >= 4.0.0 New Rails 7.0 generator produces a Gemfile with "selenium-webdriver", ">= 4.0.0" to support Ruby 3.0 (#43270), and latest webdrivers 5.0.0 requires selenium-webdriver ~ 4.0. https://rubygems.org/gems/webdrivers/versions/5.0.0 It is time to drop selenium-webdriver 3.x support for Rails 7.0.
2021-10-20 21:31:26 +08:00
rubyzip (2.3.2)
Upgrade all the gems to make sure we are testing with the latest versions locally
2021-01-22 05:22:41 +08:00
rufus-scheduler (3.7.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 20:58:20 +08:00
fugit (~> 1.1, >= 1.1.6)
Upgrade sdoc to 2.2.0 Sdoc 2.2.0 has improved accessibility and bug fixes. Changelog: * #161 Add 'skip to content' link and improve shortcut keys * #170 Fix link hovers in headings * #169 Fix clearing search results * #167 Update Merge script to work with sdoc v2 * #160 Remove outline from reset stylesheet * #159 Remove TAB override in panel * #157 Move to GitHub action for tests * #155 Fix Ctrl+C copying Jan Schär
2021-05-21 16:06:22 +08:00
sdoc (2.2.0)
Use official sdoc gem instead of fork [skip ci]
2020-11-03 03:57:41 +08:00
rdoc (>= 5.0)
Rails 7.0 requires selenium-webdriver >= 4.0.0 New Rails 7.0 generator produces a Gemfile with "selenium-webdriver", ">= 4.0.0" to support Ruby 3.0 (#43270), and latest webdrivers 5.0.0 requires selenium-webdriver ~ 4.0. https://rubygems.org/gems/webdrivers/versions/5.0.0 It is time to drop selenium-webdriver 3.x support for Rails 7.0.
2021-10-20 21:31:26 +08:00
selenium-webdriver (4.0.3)
Support selenium-webdriver 4 * Use public API to add argument to the selenium driver. While `args` is also public API it doesn't know how to handle if no argument is being set yet in Selenium 4. * Fix assertions to match return on Selenium 4
2020-12-29 09:11:25 +08:00
childprocess (>= 0.5, < 5.0)
Rails 7.0 requires selenium-webdriver >= 4.0.0 New Rails 7.0 generator produces a Gemfile with "selenium-webdriver", ">= 4.0.0" to support Ruby 3.0 (#43270), and latest webdrivers 5.0.0 requires selenium-webdriver ~ 4.0. https://rubygems.org/gems/webdrivers/versions/5.0.0 It is time to drop selenium-webdriver 3.x support for Rails 7.0.
2021-10-20 21:31:26 +08:00
rexml (~> 3.2, >= 3.2.5)
Bundle update
2019-10-10 12:48:16 +08:00
rubyzip (>= 1.2.2)
Update development gems
2021-06-09 07:27:47 +08:00
sequel (5.45.0)
Upgrade all the gems
2018-09-06 05:41:31 +08: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-19 00:30:25 +08:00
sigdump (~> 0.2.2)
Update development gems
2021-06-09 07:27:47 +08:00
set (1.0.1)
Upgrade the development Gemfile.lock
2021-04-14 02:18:28 +08:00
sidekiq (6.2.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-02 05:31:21 +08:00
connection_pool (>= 2.2.2)
Update sidekiq to fix warnings in Active Job tests `Redis#exists(key)` will return an Integer in redis-rb 4.3, if you want to keep the old behavior, use `exists?` instead. To opt-in to the new behavior now you can set Redis.exists_returns_integer = true. (/Users/eugene/.rbenv/versions/2.7.2/lib/ruby/gems/2.7.0/gems/sidekiq-6.0.4/lib/sidekiq/launcher.rb:134:in `block (2 levels) in ❤')
2020-10-04 05:27:05 +08:00
rack (~> 2.0)
redis (>= 4.2.0)
Upgrade all gems to make sure Rails works with rack 2.0.0.rc1
2016-05-07 05:16:28 +08:00
sigdump (0.2.4)
Upgrade the development Gemfile.lock
2021-04-14 02:18:28 +08:00
signet (0.15.0)
Resolve gemspec typo
2017-08-01 04:55:55 +08:00
addressable (~> 2.3)
Unlock `azure-storage-blob` version to use version 2.0 `azure-storage-blob` 2.0.0 has been released. https://rubygems.org/gems/azure-storage-blob/versions/2.0.0 According to this commit and changelog, `azure-storage-blob` 1.1.0 did not support Ruby 2.6 and higher. As of right now, Rails master branch should support Ruby 2.5.0, 2.6.0 and 2.7.0 then it should be appropriate to unlock `azure-storage-blob` version. https://github.com/Azure/azure-storage-ruby/commit/252e3f06a5cf2e2583302bfefa95d8b25818a44f This commit addresses this following error: ```ruby % cd activestorage % bundle exec rake test Traceback (most recent call last): 14: from /Users/yahonda/.rbenv/versions/2.6.5/lib/ruby/gems/2.6.0/gems/rake-13.0.1/lib/rake/rake_test_loader.rb:5:in `<main>' 13: from /Users/yahonda/.rbenv/versions/2.6.5/lib/ruby/gems/2.6.0/gems/rake-13.0.1/lib/rake/rake_test_loader.rb:5:in `select' 12: from /Users/yahonda/.rbenv/versions/2.6.5/lib/ruby/gems/2.6.0/gems/rake-13.0.1/lib/rake/rake_test_loader.rb:17:in `block in <main>' 11: from /Users/yahonda/.rbenv/versions/2.6.5/lib/ruby/gems/2.6.0/gems/zeitwerk-2.3.0/lib/zeitwerk/kernel.rb:23:in `require' 10: from /Users/yahonda/.rbenv/versions/2.6.5/lib/ruby/gems/2.6.0/gems/zeitwerk-2.3.0/lib/zeitwerk/kernel.rb:23:in `require' 9: from /Users/yahonda/src/github.com/rails/rails/activestorage/test/service/azure_storage_service_test.rb:7:in `<top (required)>' 8: from /Users/yahonda/src/github.com/rails/rails/activestorage/test/service/azure_storage_service_test.rb:8:in `<class:AzureStorageServiceTest>' 7: from /Users/yahonda/src/github.com/rails/rails/activestorage/lib/active_storage/service.rb:51:in `configure' 6: from /Users/yahonda/src/github.com/rails/rails/activestorage/lib/active_storage/service/configurator.rb:8:in `build' 5: from /Users/yahonda/src/github.com/rails/rails/activestorage/lib/active_storage/service/configurator.rb:17:in `build' 4: from /Users/yahonda/src/github.com/rails/rails/activestorage/lib/active_storage/service/configurator.rb:30:in `resolve' 3: from /Users/yahonda/.rbenv/versions/2.6.5/lib/ruby/gems/2.6.0/gems/zeitwerk-2.3.0/lib/zeitwerk/kernel.rb:23:in `require' 2: from /Users/yahonda/.rbenv/versions/2.6.5/lib/ruby/gems/2.6.0/gems/zeitwerk-2.3.0/lib/zeitwerk/kernel.rb:23:in `require' 1: from /Users/yahonda/src/github.com/rails/rails/activestorage/lib/active_storage/service/azure_storage_service.rb:3:in `<top (required)>' /Users/yahonda/.rbenv/versions/2.6.5/lib/ruby/gems/2.6.0/gems/bundler-2.1.4/lib/bundler/rubygems_integration.rb:346:in `block (2 levels) in replace_gem': can't activate azure-storage-blob (~> 1.1), already activated azure-storage-blob-2.0.0. Make sure all dependencies are added to Gemfile. (Gem::LoadError) 11: from /Users/yahonda/.rbenv/versions/2.6.5/lib/ruby/gems/2.6.0/gems/rake-13.0.1/lib/rake/rake_test_loader.rb:5:in `<main>' 10: from /Users/yahonda/.rbenv/versions/2.6.5/lib/ruby/gems/2.6.0/gems/rake-13.0.1/lib/rake/rake_test_loader.rb:5:in `select' 9: from /Users/yahonda/.rbenv/versions/2.6.5/lib/ruby/gems/2.6.0/gems/rake-13.0.1/lib/rake/rake_test_loader.rb:17:in `block in <main>' 8: from /Users/yahonda/.rbenv/versions/2.6.5/lib/ruby/gems/2.6.0/gems/zeitwerk-2.3.0/lib/zeitwerk/kernel.rb:23:in `require' 7: from /Users/yahonda/.rbenv/versions/2.6.5/lib/ruby/gems/2.6.0/gems/zeitwerk-2.3.0/lib/zeitwerk/kernel.rb:23:in `require' 6: from /Users/yahonda/src/github.com/rails/rails/activestorage/test/service/azure_storage_service_test.rb:7:in `<top (required)>' 5: from /Users/yahonda/src/github.com/rails/rails/activestorage/test/service/azure_storage_service_test.rb:8:in `<class:AzureStorageServiceTest>' 4: from /Users/yahonda/src/github.com/rails/rails/activestorage/lib/active_storage/service.rb:51:in `configure' 3: from /Users/yahonda/src/github.com/rails/rails/activestorage/lib/active_storage/service/configurator.rb:8:in `build' 2: from /Users/yahonda/src/github.com/rails/rails/activestorage/lib/active_storage/service/configurator.rb:17:in `build' 1: from /Users/yahonda/src/github.com/rails/rails/activestorage/lib/active_storage/service/configurator.rb:29:in `resolve' /Users/yahonda/src/github.com/rails/rails/activestorage/lib/active_storage/service/configurator.rb:33:in `rescue in resolve': Missing service adapter for "AzureStorage" (RuntimeError) rake aborted! ``` * Update Gemfile.lock to bump azure-storage-blob version ``` % bundle update --conservative faraday azure-storage-blob google-cloud-storage` ``` - How to find gem name to update by setting `gem "azure-storage-blob", "= 2.0.0"` temporarily ```ruby % git diff diff --git a/Gemfile b/Gemfile index 5fdaceab2f..6be7dccf4b 100644 --- a/Gemfile +++ b/Gemfile @@ -84,7 +84,7 @@ end group :storage do gem "aws-sdk-s3", require: false gem "google-cloud-storage", "~> 1.11", require: false - gem "azure-storage-blob", require: false + gem "azure-storage-blob", "= 2.0.0", require: false # Use 2.0.0 temporarily to find which gems need bump gem "image_processing", "~> 1.2" end % bundle install Fetching gem metadata from https://rubygems.org/......... Fetching gem metadata from https://rubygems.org/. Resolving dependencies..... Bundler could not find compatible versions for gem "faraday": In snapshot (Gemfile.lock): faraday (= 0.17.1) In Gemfile: azure-storage-blob (= 2.0.0) was resolved to 2.0.0, which depends on azure-storage-common (~> 2.0) was resolved to 2.0.1, which depends on faraday (~> 1.0) google-cloud-storage (~> 1.11) was resolved to 1.25.0, which depends on googleauth (~> 0.9) was resolved to 0.10.0, which depends on faraday (~> 0.12) Running `bundle update` will rebuild your snapshot from scratch, using only the gems in your Gemfile, which may resolve the conflict. % git checkout -f Gemfile % bundle update --conservative faraday azure-storage-blob google-cloud-storage ```
2020-03-16 18:38:22 +08:00
faraday (>= 0.17.3, < 2.0)
Use `credentials` instead of `keyfile` in GCS sevice The `keyfile` was renamed to `credentials` in `google-cloud-storage` 1.8.0. https://github.com/GoogleCloudPlatform/google-cloud-ruby/blob/master/google-cloud-storage/CHANGELOG.md#180--2017-11-14 Although `keyfile` can still be used, but it looks like deprecate. https://github.com/GoogleCloudPlatform/google-cloud-ruby/blob/ddf7b2a856d676316525eb581c1a4cc83ca6097b/google-cloud-storage/lib/google/cloud/storage.rb#L589...L590 Therefore, I think that should use `credentials` in newly generated applications. Ref: https://github.com/GoogleCloudPlatform/google-cloud-ruby/issues/1802
2017-11-29 12:08:33 +08:00
jwt (>= 1.5, < 3.0)
Resolve gemspec typo
2017-08-01 04:55:55 +08:00
multi_json (~> 1.10)
Upgrade all the gems
2020-11-04 14:39:41 +08:00
sinatra (2.1.0)
Update rack-test dependency constraint
2017-07-20 07:04:53 +08:00
mustermann (~> 1.0)
Upgrade all the gems
2020-11-04 14:39:41 +08:00
rack (~> 2.2)
rack-protection (= 2.1.0)
Update rack-test dependency constraint
2017-07-20 07:04:53 +08: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-30 06:39:43 +08:00
sneakers (2.11.0)
bunny (~> 2.12)
Bundle update
2018-05-31 01:49:55 +08: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-30 06:39:43 +08:00
rake
Bundle update
2018-05-31 01:49:55 +08: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-19 00:30:25 +08:00
thor
Update development gems
2021-06-09 07:27:47 +08:00
sorted_set (1.0.3)
rbtree
set (~> 1.0)
Update sprockets-rails to fix tests on Ruby master Without this, railties/test/application/rake_test.rb fails with: ActionView::Template::Error: wrong number of arguments (given 2, expected 1)
2020-10-04 05:43:39 +08:00
sprockets (4.0.2)
Use sprockets 3 in the Rails 5 release
2015-12-17 02:30:58 +08:00
concurrent-ruby (~> 1.0)
rack (> 1, < 3)
Update rack-test dependency constraint
2017-07-20 07:04:53 +08:00
sprockets-export (1.0.0)
Update sprockets-rails to fix tests on Ruby master Without this, railties/test/application/rake_test.rb fails with: ActionView::Template::Error: wrong number of arguments (given 2, expected 1)
2020-10-04 05:43:39 +08:00
sprockets-rails (3.2.2)
Use release sprockets-rails
2015-12-18 04:22:58 +08:00
actionpack (>= 4.0)
activesupport (>= 4.0)
sprockets (>= 3.0.0)
Update sqlite3 to avoid Ruby 2.7 warnings
2019-12-19 17:27:02 +08:00
sqlite3 (1.4.2)
Update development gems
2021-06-09 07:27:47 +08:00
stackprof (0.2.17)
Make Sprockets more optional, offer Propshaft as alternative (#43261) * Make Sprockets more optional, offer Propshaft as alternative * Whups, local reference * No longer used * Spacing * Need explicit sprockets-rails inclusion now * Manually require the sprockets railtie * Don't need these changes right now * Kick off another build * Fix tests * DRY up test * Require railtie when using sprockets * Introduce option to skip asset pipeline * No longer relevant * Always have to return * Gone * Add helper for skip_sprockets? * Fix guard statement * Use latest gems * Include propshaft * fix tests for #43261 (#43277) * help fix tests for #43261 skip_sprockets? should not be called on options :skip_sprockets is no longer a value in the option hash, so skip_sprockets? should not be called on it move --asset-pipeline to shared generator skip_sprockets? is defined on app_base, and used in the plugin generator to determine whether to add the engine's assets to the dummy sprockets manifest, so I believe it makes sense to include in both generators Because of this change, I also changed the shared test back to testing against non-sprockets add skip_sprockets to Gemfile template vars Mocking skip_sprockets? in app_base generator fix more generator tests * use skip_sprockets? everywhere * Use latest propshaft * Update `AssetUrlHelper` docs to list both asset pipeline gems (#43328) * Update to latest Propshaft * Bump Propshaft again * Ask for latest * Use latest propshaft Co-authored-by: Hartley McGuire <skipkayhil@gmail.com> Co-authored-by: Richard Macklin <1863540+rmacklin@users.noreply.github.com>
2021-10-09 23:03:05 +08:00
stimulus-rails (0.5.4)
Replace webpack with importmapped Hotwire as default js (#42999) * Turbolinks is being replaced with Hotwire * Make --webpack opt-in * Don't use specific webpacker installers any more in preparation for next Webpacker * Update railties/lib/rails/app_updater.rb Co-authored-by: Alex Ghiculescu <alex@tanda.co> * Trailing whitespace * Convert to Turbo data attribute for tracking * Default is no webpack, no hotwire * Swap out turbolinks references for hotwire * Drop explicit return * Only generate package.json if using webpack * Only create package.json in webpack mode * Only create app/javascript in webpack mode * Generate correct style/js links based on js mode * Fix tests from changed output format Not sure why these are showing up in this PR, though. * Rubocopping * Stick with webpack for the test app for now * Adjust tests * Replace minitest-reporters with minitest-ci (#43016) minitest-reporters is used to create junit xml reports on CI. But when it loads before rails minitest plugin makes `Rails::TestUnitReporter` not being added as a reporter. minitest-ci is now only loaded at ci and does not interferes with rails minitest plugins. And keeps junit reports workings * Too heavy handed to actually run bundle Just like we don't auto-migrate * Pin js frameworks in importmap Instead of having importmap preconfigure it. * Match updated app/javascript path * No need for the explaining comment * Fixes test cases for replace webpack with importmapped Hotwire as default js (#42999) * Fix rubocop issues * Fix more railities test cases * Fix plugin generator railties shared test cases * Fix Action Text install generator asset pipeline spec * They're modules, not files * Let dev use the latest release as well So we don't have to replace unexisting dev releases with latest release * Make Webpack responsible for generating all the JS files it needs Webpacker 6 has already moved from app/javascript to app/packs. * Don't add rails/ujs by default any longer All the ajax/form functionality has been superseded by Turbo. The rest lives in a weird inbetween land we need to address through other means. * Use new importmap location * Switch to using turbo-rails and stimulus-rails directly The hotwire-rails gem does not offer enough value for its indirection * Use latest Webpacker * Prevent version resolution requests from getting swallowed * Use ESM syntax for imports * Move management of yarn, package.json, etc to Webpacker 6 * Update for Webpacker 6 * Move bin/setup addition to Webpacker as well * Remove dead tests * Bump to Webpacker 6.0.0.rc.2 * No longer relevant given the new default is no webpacker * Rely on Webpacker 6 * No longer relevant * No longer relevant * Make cable channel generator work for both webpacker and importmap setups * Fix tests * For tests testing importmap way * Use Webpacker 6 dummy * RuboCopping * One more bump to fix webpack-dev-server * Another bump. Hopefully the last one! * Also enough to not want turbo tracking on * Fix tests * Latest * Fix tests * Fix more tests * Fix tests Co-authored-by: Alex Ghiculescu <alex@tanda.co> Co-authored-by: André Luis Leal Cardoso Junior <andrehjr@gmail.com> Co-authored-by: Abhay Nikam <nikam.abhay1@gmail.com> Co-authored-by: Guillermo Iguaran <guilleiguaran@gmail.com>
2021-08-26 16:39:36 +08:00
rails (>= 6.0.0)
Upgrade the development Gemfile.lock
2021-04-14 02:18:28 +08:00
sucker_punch (3.0.1)
Upgrade all the gems
2018-09-06 05:41:31 +08:00
concurrent-ruby (~> 1.0)
Add --css app generator option (#43177) * Add --css to preconfigure a CSS bundler/processor * Simpler conditional * Add CSS gems * Test CSS options
2021-09-07 23:48:13 +08:00
tailwindcss-rails (0.4.3)
rails (>= 6.0.0)
Replace uglifier with terser in dummy applications Terser is more up to date with modern javascript features, and the uglifier gem repository recommends using it for minifying ES6+. Followup for 955041b
2021-06-28 12:48:56 +08:00
terser (1.1.4)
execjs (>= 0.3.0, < 3)
Update development gems
2021-06-09 07:27:47 +08:00
thin (1.8.1)
Add accidentally removed dependency in Gemfile.lock Follow up to ca0b6d0d416776655ed7516ac18f126fbde5315a.
2016-08-04 06:55:47 +08:00
daemons (~> 1.0, >= 1.0.9)
eventmachine (~> 1.0, >= 1.0.4)
rack (>= 1, < 3)
Upgrade all the gems to make sure we are testing with the latest versions locally
2021-01-22 05:22:41 +08:00
thor (1.1.0)
Bundle update
2019-10-10 12:48:16 +08:00
tilt (2.0.10)
Upgrade the development Gemfile.lock
2021-04-14 02:18:28 +08:00
trailblazer-option (0.1.1)
Make Sprockets more optional, offer Propshaft as alternative (#43261) * Make Sprockets more optional, offer Propshaft as alternative * Whups, local reference * No longer used * Spacing * Need explicit sprockets-rails inclusion now * Manually require the sprockets railtie * Don't need these changes right now * Kick off another build * Fix tests * DRY up test * Require railtie when using sprockets * Introduce option to skip asset pipeline * No longer relevant * Always have to return * Gone * Add helper for skip_sprockets? * Fix guard statement * Use latest gems * Include propshaft * fix tests for #43261 (#43277) * help fix tests for #43261 skip_sprockets? should not be called on options :skip_sprockets is no longer a value in the option hash, so skip_sprockets? should not be called on it move --asset-pipeline to shared generator skip_sprockets? is defined on app_base, and used in the plugin generator to determine whether to add the engine's assets to the dummy sprockets manifest, so I believe it makes sense to include in both generators Because of this change, I also changed the shared test back to testing against non-sprockets add skip_sprockets to Gemfile template vars Mocking skip_sprockets? in app_base generator fix more generator tests * use skip_sprockets? everywhere * Use latest propshaft * Update `AssetUrlHelper` docs to list both asset pipeline gems (#43328) * Update to latest Propshaft * Bump Propshaft again * Ask for latest * Use latest propshaft Co-authored-by: Hartley McGuire <skipkayhil@gmail.com> Co-authored-by: Richard Macklin <1863540+rmacklin@users.noreply.github.com>
2021-10-09 23:03:05 +08:00
turbo-rails (0.7.14)
Replace webpack with importmapped Hotwire as default js (#42999) * Turbolinks is being replaced with Hotwire * Make --webpack opt-in * Don't use specific webpacker installers any more in preparation for next Webpacker * Update railties/lib/rails/app_updater.rb Co-authored-by: Alex Ghiculescu <alex@tanda.co> * Trailing whitespace * Convert to Turbo data attribute for tracking * Default is no webpack, no hotwire * Swap out turbolinks references for hotwire * Drop explicit return * Only generate package.json if using webpack * Only create package.json in webpack mode * Only create app/javascript in webpack mode * Generate correct style/js links based on js mode * Fix tests from changed output format Not sure why these are showing up in this PR, though. * Rubocopping * Stick with webpack for the test app for now * Adjust tests * Replace minitest-reporters with minitest-ci (#43016) minitest-reporters is used to create junit xml reports on CI. But when it loads before rails minitest plugin makes `Rails::TestUnitReporter` not being added as a reporter. minitest-ci is now only loaded at ci and does not interferes with rails minitest plugins. And keeps junit reports workings * Too heavy handed to actually run bundle Just like we don't auto-migrate * Pin js frameworks in importmap Instead of having importmap preconfigure it. * Match updated app/javascript path * No need for the explaining comment * Fixes test cases for replace webpack with importmapped Hotwire as default js (#42999) * Fix rubocop issues * Fix more railities test cases * Fix plugin generator railties shared test cases * Fix Action Text install generator asset pipeline spec * They're modules, not files * Let dev use the latest release as well So we don't have to replace unexisting dev releases with latest release * Make Webpack responsible for generating all the JS files it needs Webpacker 6 has already moved from app/javascript to app/packs. * Don't add rails/ujs by default any longer All the ajax/form functionality has been superseded by Turbo. The rest lives in a weird inbetween land we need to address through other means. * Use new importmap location * Switch to using turbo-rails and stimulus-rails directly The hotwire-rails gem does not offer enough value for its indirection * Use latest Webpacker * Prevent version resolution requests from getting swallowed * Use ESM syntax for imports * Move management of yarn, package.json, etc to Webpacker 6 * Update for Webpacker 6 * Move bin/setup addition to Webpacker as well * Remove dead tests * Bump to Webpacker 6.0.0.rc.2 * No longer relevant given the new default is no webpacker * Rely on Webpacker 6 * No longer relevant * No longer relevant * Make cable channel generator work for both webpacker and importmap setups * Fix tests * For tests testing importmap way * Use Webpacker 6 dummy * RuboCopping * One more bump to fix webpack-dev-server * Another bump. Hopefully the last one! * Also enough to not want turbo tracking on * Fix tests * Latest * Fix tests * Fix more tests * Fix tests Co-authored-by: Alex Ghiculescu <alex@tanda.co> Co-authored-by: André Luis Leal Cardoso Junior <andrehjr@gmail.com> Co-authored-by: Abhay Nikam <nikam.abhay1@gmail.com> Co-authored-by: Guillermo Iguaran <guilleiguaran@gmail.com>
2021-08-26 16:39:36 +08:00
rails (>= 6.0.0)
Upgrade all the gems to make sure we are testing with the latest versions locally
2021-01-22 05:22:41 +08:00
tzinfo (2.0.4)
Update to TZInfo v2.0.0 Co-authored-by: Jared Beck <jared@jaredbeck.com> Co-authored-by: Jonathan Hefner <jonathan@hefner.pro>
2017-12-29 20:47:10 +08:00
concurrent-ruby (~> 1.0)
Resolve gemspec typo
2017-08-01 04:55:55 +08:00
uber (0.1.0)
Upgrade all the gems to make sure we are testing with the latest versions locally
2021-01-22 05:22:41 +08:00
unicode-display_width (2.0.0)
Bundle update
2018-05-31 01:49:55 +08: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-19 00:30:25 +08:00
vegas (0.1.11)
rack (>= 1.0.0)
Update w3c_validtors for Ruby 3 compatibility (#40227) * Update w3c_validtors for Ruby 3 compatibility * Update google-api-client for Ruby 3 compatibility
2020-09-21 13:19:59 +08:00
w3c_validators (1.3.6)
Update rack-test dependency constraint
2017-07-20 07:04:53 +08:00
json (>= 1.8)
bundle update
2016-12-26 20:46:01 +08:00
nokogiri (~> 1.6)
Update w3c_validtors for Ruby 3 compatibility (#40227) * Update w3c_validtors for Ruby 3 compatibility * Update google-api-client for Ruby 3 compatibility
2020-09-21 13:19:59 +08:00
rexml (~> 3.2)
Rails 7.0 requires selenium-webdriver >= 4.0.0 New Rails 7.0 generator produces a Gemfile with "selenium-webdriver", ">= 4.0.0" to support Ruby 3.0 (#43270), and latest webdrivers 5.0.0 requires selenium-webdriver ~ 4.0. https://rubygems.org/gems/webdrivers/versions/5.0.0 It is time to drop selenium-webdriver 3.x support for Rails 7.0.
2021-10-20 21:31:26 +08:00
webdrivers (5.0.0)
Use webdrivers instead of chromedriver-helper for AV UJS tests
2019-03-25 05:05:30 +08:00
nokogiri (~> 1.6)
Bundle update
2019-10-10 12:48:16 +08:00
rubyzip (>= 1.3.0)
Rails 7.0 requires selenium-webdriver >= 4.0.0 New Rails 7.0 generator produces a Gemfile with "selenium-webdriver", ">= 4.0.0" to support Ruby 3.0 (#43270), and latest webdrivers 5.0.0 requires selenium-webdriver ~ 4.0. https://rubygems.org/gems/webdrivers/versions/5.0.0 It is time to drop selenium-webdriver 3.x support for Rails 7.0.
2021-10-20 21:31:26 +08:00
selenium-webdriver (~> 4.0)
Update development gems
2021-06-09 07:27:47 +08:00
webmock (3.13.0)
Extract ActionMailbox::PostfixRelayer
2018-11-26 03:30:05 +08:00
addressable (>= 2.3.6)
crack (>= 0.3.2)
Bundle update
2019-10-10 12:48:16 +08:00
hashdiff (>= 0.4.0, < 2.0.0)
Ruby 3 does not have webrick by default Railties CI against Ruby 3.0.0-dev has been failing since https://buildkite.com/rails/rails/builds/73338#51165eef-b631-4f9c-8e98-fc210e71e6d1 This pull request addresses the following error. ```ruby $ ruby -v ruby 3.0.0dev (2020-12-13T04:39:57Z master c7530f0d56) [x86_64-linux] $ ruby -Itest -Ilib -I../activesupport/lib -I../actionpack/lib -I../actionview/lib -I../activemodel/lib test/commands/server_test.rb ... snip ... Run options: --seed 54404 .E Error: Rails::Command::ServerCommandTest#test_served_url: LoadError: cannot load such file -- webrick test/commands/server_test.rb:292:in `test_served_url' rails test test/commands/server_test.rb:289 ........................ Finished in 0.303746s, 85.5977 runs/s, 177.7799 assertions/s. 26 runs, 54 assertions, 0 failures, 1 errors, 0 skips $ ``` Related to https://github.com/ruby/ruby/pull/3729 https://bugs.ruby-lang.org/issues/17303
2020-12-13 15:34:39 +08:00
webrick (1.7.0)
Upgrade all the gems to make sure we are testing with the latest versions locally
2021-01-22 05:22:41 +08:00
websocket (1.2.9)
Upgrade development gems
2021-06-18 04:26:38 +08:00
websocket-driver (0.7.5)
Use released redis-namespace instead of master branch https://rubygems.org/gems/redis-namespace/versions/1.8.1
2021-02-22 17:48:02 +08:00
websocket-extensions (>= 0.1.0)
Upgrade all the gems
2020-11-04 14:39:41 +08:00
websocket-extensions (0.1.5)
bundle update
2018-11-10 06:21:08 +08: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 19:55:34 +08:00
nokogiri (~> 1.8)
Use `ActiveRecord::FixtureSet.signed_global_id` defined by the globalid gem Also make explicit that actiontext depends on the globalid gem.
2021-11-25 06:33:45 +08:00
zeitwerk (2.5.1)
Track Gemfile.lock at the repository The main reason is to make bisect easier. In some points, we have a lot of git dependencies. Since we don't have the information of which commit we are referring to, bundler get the latest commit of the master branch of the dependency. This sometimes returns a version that is not compatible with Rails anymore, making the tests fail and the harder to identify the commit that introduced a bug. Also this will make sure that a contributor will always get a set of dependencies that are passing with our tests. In our CI server we delete the lock file to make sure we are always testing against the newest release of our dependencies.
2015-02-19 00:30:25 +08:00
PLATFORMS
Simplify the implementation by only calling the checks in the right places
2021-06-17 05:17:34 +08:00
ruby
Update platforms in Gemfile.lock This keeps popping up after bundle on my local machine. We can just add this to the lock file so there's no diff after bunding.
2021-01-14 04:12:23 +08:00
x86_64-darwin-19
Add x86_64-darwin-20 platform to the Gemfile Otherwise people developping on Big Sur will have to rebundle
2021-06-10 21:33:10 +08:00
x86_64-darwin-20
Update development gems
2021-06-09 07:27:47 +08:00
x86_64-linux
Track Gemfile.lock at the repository The main reason is to make bisect easier. In some points, we have a lot of git dependencies. Since we don't have the information of which commit we are referring to, bundler get the latest commit of the master branch of the dependency. This sometimes returns a version that is not compatible with Rails anymore, making the tests fail and the harder to identify the commit that introduced a bug. Also this will make sure that a contributor will always get a set of dependencies that are passing with our tests. In our CI server we delete the lock file to make sure we are always testing against the newest release of our dependencies.
2015-02-19 00:30:25 +08:00
DEPENDENCIES
activerecord-jdbcmysql-adapter (>= 1.3.0)
activerecord-jdbcpostgresql-adapter (>= 1.3.0)
activerecord-jdbcsqlite3-adapter (>= 1.3.0)
Use v3 of the AWS SDK
2017-09-10 11:22:10 +08:00
aws-sdk-s3
Accept inbound emails from a variety of ingresses
2018-10-07 10:02:08 +08:00
aws-sdk-sns
Upgrade azure-storage-blob to use at least 2.0.0 azure-storage-blob 1.1.0 supports ruby 1.9.3 to 2.5: https://github.com/Azure/azure-storage-ruby/blob/v1.1.0-common/common/README.md azure-storage-blob 2.0.0 supports ruby 2.3 to 2.7: https://github.com/Azure/azure-storage-ruby/blob/v2.0.0-blob/common/README.md
2021-08-24 03:17:59 +08:00
azure-storage-blob (~> 2.0)
Track Gemfile.lock at the repository The main reason is to make bisect easier. In some points, we have a lot of git dependencies. Since we don't have the information of which commit we are referring to, bundler get the latest commit of the master branch of the dependency. This sometimes returns a version that is not compatible with Rails anymore, making the tests fail and the harder to identify the commit that introduced a bug. Also this will make sure that a contributor will always get a set of dependencies that are passing with our tests. In our CI server we delete the lock file to make sure we are always testing against the newest release of our dependencies.
2015-02-19 00:30:25 +08:00
backburner
Fix Gemfile.lock
2016-03-11 03:28:02 +08:00
bcrypt (~> 3.1.11)
Revert "Lock benchmark-ips version "< 2.9.0"" This reverts commit b63e1477eaccfa6416db4f09bb82880ecb0797d1.
2021-05-25 05:11:38 +08:00
benchmark-ips
Update Blade and its Sauce Labs plugin for EventMachine 1.2 compatibility
2016-06-05 06:54:34 +08:00
blade
Bump bootsnap to a version with disables iseq_cache for Ruby 2.5 - Refs https://github.com/Shopify/bootsnap/pull/257
2019-04-26 15:25:28 +08:00
bootsnap (>= 1.4.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-25 10:19:21 +08:00
capybara (>= 3.26)
Support for connection pooling on mem cache store
2017-12-13 08:11:47 +08:00
connection_pool
Add --css app generator option (#43177) * Add --css to preconfigure a CSS bundler/processor * Simpler conditional * Add CSS gems * Test CSS options
2021-09-07 23:48:13 +08:00
cssbundling-rails
Require Dalli 3 in our test suite The code itself still works with Dailli 2, but we are now only testing against Dalli 3.
2021-10-15 01:48:04 +08:00
dalli (>= 3.0.1)
Use debug 1.1+ for the debugger + log quieting
2021-09-20 21:18:30 +08:00
debug (>= 1.1.0)
Use released `delayed_job` instead of master version Ref: https://github.com/collectiveidea/delayed_job/blob/master/CHANGELOG.md#414---2017-12-29
2017-12-30 05:57:28 +08:00
delayed_job
delayed_job and delayed_job_active_record gems with AR5 support are available
2017-01-29 08:05:06 +08:00
delayed_job_active_record
Support streaming downloads from Google Cloud Storage
2018-05-02 11:20:56 +08:00
google-cloud-storage (~> 1.11)
Switch the default redis adapter to a single-stream model This new adapter does get a little more intimate with the redis-rb gem's implementation than I would like, but it's the least bad of the approaches I've come up with.
2016-01-31 23:00:00 +08:00
hiredis
Use ImageProcessing gem for ActiveStorage variants ImageProcessing gem is a wrapper around MiniMagick and ruby-vips, and implements an interface for common image resizing and processing. This is the canonical image processing gem recommended in [Shrine], and that's where it developed from. The initial implementation was extracted from Refile, which also implements on-the-fly transformations. Some features that ImageProcessing gem adds on top of MiniMagick: * resizing macros - #resize_to_limit - #resize_to_fit - #resize_to_fill - #resize_and_pad * automatic orientation * automatic thumbnail sharpening * avoids the complex and inefficient MiniMagick::Image class * will use "magick" instead of "convert" on ImageMagick 7 However, the biggest feature of the ImageProcessing gem is that it has an alternative implementation that uses libvips. Libvips is an alternative to ImageMagick that can process images very rapidly (we've seen up 10x faster than ImageMagick). What's great is that the ImageProcessing gem provides the same interface for both implementations. The macros are named the same, and the libvips implementation does auto orientation and thumbnail sharpening as well; only the operations/options specific to ImageMagick/libvips differ. The integration provided by this PR should work for both implementations. The plan is to introduce the ImageProcessing backend in Rails 6.0 as the default backend and deprecate the MiniMagick backend, then in Rails 6.1 remove the MiniMagick backend.
2018-04-06 07:48:29 +08:00
image_processing (~> 1.2)
Replace webpack with importmapped Hotwire as default js (#42999) * Turbolinks is being replaced with Hotwire * Make --webpack opt-in * Don't use specific webpacker installers any more in preparation for next Webpacker * Update railties/lib/rails/app_updater.rb Co-authored-by: Alex Ghiculescu <alex@tanda.co> * Trailing whitespace * Convert to Turbo data attribute for tracking * Default is no webpack, no hotwire * Swap out turbolinks references for hotwire * Drop explicit return * Only generate package.json if using webpack * Only create package.json in webpack mode * Only create app/javascript in webpack mode * Generate correct style/js links based on js mode * Fix tests from changed output format Not sure why these are showing up in this PR, though. * Rubocopping * Stick with webpack for the test app for now * Adjust tests * Replace minitest-reporters with minitest-ci (#43016) minitest-reporters is used to create junit xml reports on CI. But when it loads before rails minitest plugin makes `Rails::TestUnitReporter` not being added as a reporter. minitest-ci is now only loaded at ci and does not interferes with rails minitest plugins. And keeps junit reports workings * Too heavy handed to actually run bundle Just like we don't auto-migrate * Pin js frameworks in importmap Instead of having importmap preconfigure it. * Match updated app/javascript path * No need for the explaining comment * Fixes test cases for replace webpack with importmapped Hotwire as default js (#42999) * Fix rubocop issues * Fix more railities test cases * Fix plugin generator railties shared test cases * Fix Action Text install generator asset pipeline spec * They're modules, not files * Let dev use the latest release as well So we don't have to replace unexisting dev releases with latest release * Make Webpack responsible for generating all the JS files it needs Webpacker 6 has already moved from app/javascript to app/packs. * Don't add rails/ujs by default any longer All the ajax/form functionality has been superseded by Turbo. The rest lives in a weird inbetween land we need to address through other means. * Use new importmap location * Switch to using turbo-rails and stimulus-rails directly The hotwire-rails gem does not offer enough value for its indirection * Use latest Webpacker * Prevent version resolution requests from getting swallowed * Use ESM syntax for imports * Move management of yarn, package.json, etc to Webpacker 6 * Update for Webpacker 6 * Move bin/setup addition to Webpacker as well * Remove dead tests * Bump to Webpacker 6.0.0.rc.2 * No longer relevant given the new default is no webpacker * Rely on Webpacker 6 * No longer relevant * No longer relevant * Make cable channel generator work for both webpacker and importmap setups * Fix tests * For tests testing importmap way * Use Webpacker 6 dummy * RuboCopping * One more bump to fix webpack-dev-server * Another bump. Hopefully the last one! * Also enough to not want turbo tracking on * Fix tests * Latest * Fix tests * Fix more tests * Fix tests Co-authored-by: Alex Ghiculescu <alex@tanda.co> Co-authored-by: André Luis Leal Cardoso Junior <andrehjr@gmail.com> Co-authored-by: Abhay Nikam <nikam.abhay1@gmail.com> Co-authored-by: Guillermo Iguaran <guilleiguaran@gmail.com>
2021-08-26 16:39:36 +08:00
importmap-rails
Use the combined jsbundling-rails gem instead of individual js bundler gems (#43172) * Use the combined jsbundling-rails gem instead of individual js bundler gems * Remove Webpacker remnants * Replace webpacker with jsbundling-rails
2021-09-06 22:44:44 +08:00
jsbundling-rails
Make sure to bundle json 2.x on CI Without this, bundler tries to bundle json 1.8 on Ruby 2.4 in some cases https://travis-ci.org/rails/rails/jobs/175874852
2016-11-15 08:26:03 +08:00
json (>= 2.0.0)
Fix rake guides:generate:kindle error
2016-12-18 23:13:50 +08:00
kindlerb (~> 1.2.0)
Install libxml-ruby gem so full XMLMini test suite can be run
2016-11-19 23:46:28 +08:00
libxml-ruby
Update listen gem to v3.3 Version 3.3 fixes memory leaks that occur when stopping individual listeners (see guard/listen#476).
2020-11-10 23:52:20 +08:00
listen (~> 3.3)
Add minitest-bisect as part of the gemfile
2016-07-12 14:06:25 +08:00
minitest-bisect
Replace webpack with importmapped Hotwire as default js (#42999) * Turbolinks is being replaced with Hotwire * Make --webpack opt-in * Don't use specific webpacker installers any more in preparation for next Webpacker * Update railties/lib/rails/app_updater.rb Co-authored-by: Alex Ghiculescu <alex@tanda.co> * Trailing whitespace * Convert to Turbo data attribute for tracking * Default is no webpack, no hotwire * Swap out turbolinks references for hotwire * Drop explicit return * Only generate package.json if using webpack * Only create package.json in webpack mode * Only create app/javascript in webpack mode * Generate correct style/js links based on js mode * Fix tests from changed output format Not sure why these are showing up in this PR, though. * Rubocopping * Stick with webpack for the test app for now * Adjust tests * Replace minitest-reporters with minitest-ci (#43016) minitest-reporters is used to create junit xml reports on CI. But when it loads before rails minitest plugin makes `Rails::TestUnitReporter` not being added as a reporter. minitest-ci is now only loaded at ci and does not interferes with rails minitest plugins. And keeps junit reports workings * Too heavy handed to actually run bundle Just like we don't auto-migrate * Pin js frameworks in importmap Instead of having importmap preconfigure it. * Match updated app/javascript path * No need for the explaining comment * Fixes test cases for replace webpack with importmapped Hotwire as default js (#42999) * Fix rubocop issues * Fix more railities test cases * Fix plugin generator railties shared test cases * Fix Action Text install generator asset pipeline spec * They're modules, not files * Let dev use the latest release as well So we don't have to replace unexisting dev releases with latest release * Make Webpack responsible for generating all the JS files it needs Webpacker 6 has already moved from app/javascript to app/packs. * Don't add rails/ujs by default any longer All the ajax/form functionality has been superseded by Turbo. The rest lives in a weird inbetween land we need to address through other means. * Use new importmap location * Switch to using turbo-rails and stimulus-rails directly The hotwire-rails gem does not offer enough value for its indirection * Use latest Webpacker * Prevent version resolution requests from getting swallowed * Use ESM syntax for imports * Move management of yarn, package.json, etc to Webpacker 6 * Update for Webpacker 6 * Move bin/setup addition to Webpacker as well * Remove dead tests * Bump to Webpacker 6.0.0.rc.2 * No longer relevant given the new default is no webpacker * Rely on Webpacker 6 * No longer relevant * No longer relevant * Make cable channel generator work for both webpacker and importmap setups * Fix tests * For tests testing importmap way * Use Webpacker 6 dummy * RuboCopping * One more bump to fix webpack-dev-server * Another bump. Hopefully the last one! * Also enough to not want turbo tracking on * Fix tests * Latest * Fix tests * Fix more tests * Fix tests Co-authored-by: Alex Ghiculescu <alex@tanda.co> Co-authored-by: André Luis Leal Cardoso Junior <andrehjr@gmail.com> Co-authored-by: Abhay Nikam <nikam.abhay1@gmail.com> Co-authored-by: Guillermo Iguaran <guilleiguaran@gmail.com>
2021-08-26 16:39:36 +08:00
minitest-ci
Add test retries for railties
2018-10-11 06:33:09 +08:00
minitest-retry
Use mysql2 from git to fix warnings with Ruby 2.7 Closes #40272.
2020-09-23 03:40:47 +08:00
mysql2 (~> 0.5)!
Avoid nokogiri v1.11.0 to make our CI green https://buildkite.com/rails/rails/builds/73847#8a8b56c0-ebdf-4a34-8072-62b688412970/986-995 I think it is definitely an issue for nokogiri, so I'll avoid the version to make our CI green.
2021-01-05 20:52:07 +08:00
nokogiri (>= 1.8.1, != 1.11.0)
Update pg gem required version to 1.1 This is required for #39063 to use `PG::TextDecoder::Numeric`. Ref https://github.com/ged/ruby-pg/pull/25. The pg gem 1.1.0 was released at August 24, 2018, so I think it is good timing to bump the required version for improving and cleaning up the code base. https://rubygems.org/gems/pg/versions
2020-04-27 01:50:44 +08:00
pg (~> 1.1)
Make Sprockets more optional, offer Propshaft as alternative (#43261) * Make Sprockets more optional, offer Propshaft as alternative * Whups, local reference * No longer used * Spacing * Need explicit sprockets-rails inclusion now * Manually require the sprockets railtie * Don't need these changes right now * Kick off another build * Fix tests * DRY up test * Require railtie when using sprockets * Introduce option to skip asset pipeline * No longer relevant * Always have to return * Gone * Add helper for skip_sprockets? * Fix guard statement * Use latest gems * Include propshaft * fix tests for #43261 (#43277) * help fix tests for #43261 skip_sprockets? should not be called on options :skip_sprockets is no longer a value in the option hash, so skip_sprockets? should not be called on it move --asset-pipeline to shared generator skip_sprockets? is defined on app_base, and used in the plugin generator to determine whether to add the engine's assets to the dummy sprockets manifest, so I believe it makes sense to include in both generators Because of this change, I also changed the shared test back to testing against non-sprockets add skip_sprockets to Gemfile template vars Mocking skip_sprockets? in app_base generator fix more generator tests * use skip_sprockets? everywhere * Use latest propshaft * Update `AssetUrlHelper` docs to list both asset pipeline gems (#43328) * Update to latest Propshaft * Bump Propshaft again * Ask for latest * Use latest propshaft Co-authored-by: Hartley McGuire <skipkayhil@gmail.com> Co-authored-by: Richard Macklin <1863540+rmacklin@users.noreply.github.com>
2021-10-09 23:03:05 +08:00
propshaft (>= 0.1.7)
update psych gem to 3.2 stable release
2018-03-10 04:14:36 +08:00
psych (~> 3.0)
Initial stab at adding Action Cable to rails/master
2015-12-14 23:38:37 +08:00
puma
Track Gemfile.lock at the repository The main reason is to make bisect easier. In some points, we have a lot of git dependencies. Since we don't have the information of which commit we are referring to, bundler get the latest commit of the master branch of the dependency. This sometimes returns a version that is not compatible with Rails anymore, making the tests fail and the harder to identify the commit that introduced a bug. Also this will make sure that a contributor will always get a set of dependencies that are passing with our tests. In our CI server we delete the lock file to make sure we are always testing against the newest release of our dependencies.
2015-02-19 00:30:25 +08:00
que
implement `provider_job_id` for `queue_classic`. The latest, currently unreleased, version of queue_classic is required for this to work. See https://github.com/QueueClassic/queue_classic/pull/262 for more details.
2015-08-13 15:56:06 +08:00
queue_classic!
Track Gemfile.lock at the repository The main reason is to make bisect easier. In some points, we have a lot of git dependencies. Since we don't have the information of which commit we are referring to, bundler get the latest commit of the master branch of the dependency. This sometimes returns a version that is not compatible with Rails anymore, making the tests fail and the harder to identify the commit that introduced a bug. Also this will make sure that a contributor will always get a set of dependencies that are passing with our tests. In our CI server we delete the lock file to make sure we are always testing against the newest release of our dependencies.
2015-02-19 00:30:25 +08:00
racc (>= 1.4.6)
rack-cache (~> 1.2)
rails!
Update Gemfile.lock 'rake' gem is bundled to '>= 11.1' by 30279704646fff33e64c71ee3c4de34bf75232c4 (#23499), but it seems the commit did not fully include Gemfile.lock's.
2016-03-31 00:12:20 +08:00
rake (>= 11.1)
redcarpet 3.2.2 has an XSS vulnerability see: http://www.openwall.com/lists/oss-security/2015/04/07/11
2015-04-09 17:20:53 +08:00
redcarpet (~> 3.2.3)
redis-rb 4.0 support * Use `gem 'redis', '~> 4.0'` for new app Gemfiles * Loosen Action Cable redis-rb dep to `>= 3.3, < 5` * Bump redis-namespace for looser Redis version dep * Avoid using the underlying `redis.client` directly * Use `Redis.new` instead of `Redis.connect`
2017-09-29 12:54:00 +08:00
redis (~> 4.0)
Use released redis-namespace instead of master branch https://rubygems.org/gems/redis-namespace/versions/1.8.1
2021-02-22 17:48:02 +08:00
redis-namespace
Use released resque
2017-02-10 14:31:41 +08:00
resque
Use released `resque-scheduler` instead of master version The v4.3.1 has already released that includes Redis 4.0 support. https://github.com/resque/resque-scheduler/blob/master/CHANGELOG.md#431---2017-11-20
2017-12-14 06:49:08 +08:00
resque-scheduler
Don't make rexml an dependency of activesupport rexml is only used in the xml_mini backend and it should be the users choice if they want to use that feature or not. If they do we will warn them that installing rexml is needed like we do with all backends.
2020-09-25 06:41:04 +08:00
rexml
Use Rouge for guides code highlighting [ci skip] Replace javascript highlighting using Prism with the Rouge markdown highlighter. Uses the github theme.
2020-07-04 16:59:08 +08:00
rouge
Update RuboCop to v0.90 Signed-off-by: Utkarsh Gupta <utkarsh@debian.org>
2020-09-06 09:07:04 +08:00
rubocop (>= 0.90)
Tweak unreachable assertion tests in the block of `assert_raises` I found an unexpected use of assertion in the block of `assert_raise` when I implemented https://github.com/rubocop/rubocop-minitest/pull/137. It is expected to be asserted after an exception is raised in `assert_raise` block, but in actually it is not asserted after an exception is raised. Therefore, this PR removes or updates assertions that have not been asserted after an exception has raised. This PR will add `rubocop-minitest` and enable `Minitest/UnreachableAssertion` cop to able similar auto-detection, but will remove `rubocop-minitest` from this PR if you don't like it.
2021-06-24 18:46:21 +08:00
rubocop-minitest
Update Gemfile.lock with rubocop-packaging Follow-up to #40185.
2020-09-07 03:46:11 +08:00
rubocop-packaging
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 16:05:50 +08:00
rubocop-performance
Bump rubocop to 0.71
2019-06-06 13:38:19 +08:00
rubocop-rails
Upgrade sdoc to 2.2.0 Sdoc 2.2.0 has improved accessibility and bug fixes. Changelog: * #161 Add 'skip to content' link and improve shortcut keys * #170 Fix link hovers in headings * #169 Fix clearing search results * #167 Update Merge script to work with sdoc v2 * #160 Remove outline from reset stylesheet * #159 Remove TAB override in panel * #157 Move to GitHub action for tests * #155 Fix Ctrl+C copying Jan Schär
2021-05-21 16:06:22 +08:00
sdoc (>= 2.2.0)
Rails 7.0 requires selenium-webdriver >= 4.0.0 New Rails 7.0 generator produces a Gemfile with "selenium-webdriver", ">= 4.0.0" to support Ruby 3.0 (#43270), and latest webdrivers 5.0.0 requires selenium-webdriver ~ 4.0. https://rubygems.org/gems/webdrivers/versions/5.0.0 It is time to drop selenium-webdriver 3.x support for Rails 7.0.
2021-10-20 21:31:26 +08:00
selenium-webdriver (>= 4.0.0)
Track Gemfile.lock at the repository The main reason is to make bisect easier. In some points, we have a lot of git dependencies. Since we don't have the information of which commit we are referring to, bundler get the latest commit of the master branch of the dependency. This sometimes returns a version that is not compatible with Rails anymore, making the tests fail and the harder to identify the commit that introduced a bug. Also this will make sure that a contributor will always get a set of dependencies that are passing with our tests. In our CI server we delete the lock file to make sure we are always testing against the newest release of our dependencies.
2015-02-19 00:30:25 +08:00
sequel
Use released `sidekiq` instead of master version The sidekiq 5.0.5 includes redis-rb 4.0 support. Ref: https://github.com/mperham/sidekiq/blob/90db3b84208cbb73a50d1a77a1dea97d3490ce70/Changes.md#505
2017-10-09 19:49:55 +08:00
sidekiq
Unlock sneakers adapter version
2015-04-26 15:44:18 +08:00
sneakers
Restore action_cable.js UMD module support. Fixes #28366
2017-03-12 01:33:11 +08:00
sprockets-export
Make Sprockets more optional, offer Propshaft as alternative (#43261) * Make Sprockets more optional, offer Propshaft as alternative * Whups, local reference * No longer used * Spacing * Need explicit sprockets-rails inclusion now * Manually require the sprockets railtie * Don't need these changes right now * Kick off another build * Fix tests * DRY up test * Require railtie when using sprockets * Introduce option to skip asset pipeline * No longer relevant * Always have to return * Gone * Add helper for skip_sprockets? * Fix guard statement * Use latest gems * Include propshaft * fix tests for #43261 (#43277) * help fix tests for #43261 skip_sprockets? should not be called on options :skip_sprockets is no longer a value in the option hash, so skip_sprockets? should not be called on it move --asset-pipeline to shared generator skip_sprockets? is defined on app_base, and used in the plugin generator to determine whether to add the engine's assets to the dummy sprockets manifest, so I believe it makes sense to include in both generators Because of this change, I also changed the shared test back to testing against non-sprockets add skip_sprockets to Gemfile template vars Mocking skip_sprockets? in app_base generator fix more generator tests * use skip_sprockets? everywhere * Use latest propshaft * Update `AssetUrlHelper` docs to list both asset pipeline gems (#43328) * Update to latest Propshaft * Bump Propshaft again * Ask for latest * Use latest propshaft Co-authored-by: Hartley McGuire <skipkayhil@gmail.com> Co-authored-by: Richard Macklin <1863540+rmacklin@users.noreply.github.com>
2021-10-09 23:03:05 +08:00
sprockets-rails (>= 2.0.0)
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-04 02:19:08 +08: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-19 00:30:25 +08:00
stackprof
Replace webpack with importmapped Hotwire as default js (#42999) * Turbolinks is being replaced with Hotwire * Make --webpack opt-in * Don't use specific webpacker installers any more in preparation for next Webpacker * Update railties/lib/rails/app_updater.rb Co-authored-by: Alex Ghiculescu <alex@tanda.co> * Trailing whitespace * Convert to Turbo data attribute for tracking * Default is no webpack, no hotwire * Swap out turbolinks references for hotwire * Drop explicit return * Only generate package.json if using webpack * Only create package.json in webpack mode * Only create app/javascript in webpack mode * Generate correct style/js links based on js mode * Fix tests from changed output format Not sure why these are showing up in this PR, though. * Rubocopping * Stick with webpack for the test app for now * Adjust tests * Replace minitest-reporters with minitest-ci (#43016) minitest-reporters is used to create junit xml reports on CI. But when it loads before rails minitest plugin makes `Rails::TestUnitReporter` not being added as a reporter. minitest-ci is now only loaded at ci and does not interferes with rails minitest plugins. And keeps junit reports workings * Too heavy handed to actually run bundle Just like we don't auto-migrate * Pin js frameworks in importmap Instead of having importmap preconfigure it. * Match updated app/javascript path * No need for the explaining comment * Fixes test cases for replace webpack with importmapped Hotwire as default js (#42999) * Fix rubocop issues * Fix more railities test cases * Fix plugin generator railties shared test cases * Fix Action Text install generator asset pipeline spec * They're modules, not files * Let dev use the latest release as well So we don't have to replace unexisting dev releases with latest release * Make Webpack responsible for generating all the JS files it needs Webpacker 6 has already moved from app/javascript to app/packs. * Don't add rails/ujs by default any longer All the ajax/form functionality has been superseded by Turbo. The rest lives in a weird inbetween land we need to address through other means. * Use new importmap location * Switch to using turbo-rails and stimulus-rails directly The hotwire-rails gem does not offer enough value for its indirection * Use latest Webpacker * Prevent version resolution requests from getting swallowed * Use ESM syntax for imports * Move management of yarn, package.json, etc to Webpacker 6 * Update for Webpacker 6 * Move bin/setup addition to Webpacker as well * Remove dead tests * Bump to Webpacker 6.0.0.rc.2 * No longer relevant given the new default is no webpacker * Rely on Webpacker 6 * No longer relevant * No longer relevant * Make cable channel generator work for both webpacker and importmap setups * Fix tests * For tests testing importmap way * Use Webpacker 6 dummy * RuboCopping * One more bump to fix webpack-dev-server * Another bump. Hopefully the last one! * Also enough to not want turbo tracking on * Fix tests * Latest * Fix tests * Fix more tests * Fix tests Co-authored-by: Alex Ghiculescu <alex@tanda.co> Co-authored-by: André Luis Leal Cardoso Junior <andrehjr@gmail.com> Co-authored-by: Abhay Nikam <nikam.abhay1@gmail.com> Co-authored-by: Guillermo Iguaran <guilleiguaran@gmail.com>
2021-08-26 16:39:36 +08:00
stimulus-rails
Update ActiveJob adapter for sucker_punch 2.0 This PR includes two changes for 2.0.0: - Breaking API change around `async.perform` --> `perform_async` - New addition of `perform_in`, which now allows end users of the adapter to use the `enqueued_at` public API method.
2016-01-28 00:29:18 +08:00
sucker_punch
Add --css app generator option (#43177) * Add --css to preconfigure a CSS bundler/processor * Simpler conditional * Add CSS gems * Test CSS options
2021-09-07 23:48:13 +08:00
tailwindcss-rails
Replace uglifier with terser in dummy applications Terser is more up to date with modern javascript features, and the uglifier gem repository recommends using it for minifying ES6+. Followup for 955041b
2021-06-28 12:48:56 +08:00
terser (>= 1.1.4)
Replace webpack with importmapped Hotwire as default js (#42999) * Turbolinks is being replaced with Hotwire * Make --webpack opt-in * Don't use specific webpacker installers any more in preparation for next Webpacker * Update railties/lib/rails/app_updater.rb Co-authored-by: Alex Ghiculescu <alex@tanda.co> * Trailing whitespace * Convert to Turbo data attribute for tracking * Default is no webpack, no hotwire * Swap out turbolinks references for hotwire * Drop explicit return * Only generate package.json if using webpack * Only create package.json in webpack mode * Only create app/javascript in webpack mode * Generate correct style/js links based on js mode * Fix tests from changed output format Not sure why these are showing up in this PR, though. * Rubocopping * Stick with webpack for the test app for now * Adjust tests * Replace minitest-reporters with minitest-ci (#43016) minitest-reporters is used to create junit xml reports on CI. But when it loads before rails minitest plugin makes `Rails::TestUnitReporter` not being added as a reporter. minitest-ci is now only loaded at ci and does not interferes with rails minitest plugins. And keeps junit reports workings * Too heavy handed to actually run bundle Just like we don't auto-migrate * Pin js frameworks in importmap Instead of having importmap preconfigure it. * Match updated app/javascript path * No need for the explaining comment * Fixes test cases for replace webpack with importmapped Hotwire as default js (#42999) * Fix rubocop issues * Fix more railities test cases * Fix plugin generator railties shared test cases * Fix Action Text install generator asset pipeline spec * They're modules, not files * Let dev use the latest release as well So we don't have to replace unexisting dev releases with latest release * Make Webpack responsible for generating all the JS files it needs Webpacker 6 has already moved from app/javascript to app/packs. * Don't add rails/ujs by default any longer All the ajax/form functionality has been superseded by Turbo. The rest lives in a weird inbetween land we need to address through other means. * Use new importmap location * Switch to using turbo-rails and stimulus-rails directly The hotwire-rails gem does not offer enough value for its indirection * Use latest Webpacker * Prevent version resolution requests from getting swallowed * Use ESM syntax for imports * Move management of yarn, package.json, etc to Webpacker 6 * Update for Webpacker 6 * Move bin/setup addition to Webpacker as well * Remove dead tests * Bump to Webpacker 6.0.0.rc.2 * No longer relevant given the new default is no webpacker * Rely on Webpacker 6 * No longer relevant * No longer relevant * Make cable channel generator work for both webpacker and importmap setups * Fix tests * For tests testing importmap way * Use Webpacker 6 dummy * RuboCopping * One more bump to fix webpack-dev-server * Another bump. Hopefully the last one! * Also enough to not want turbo tracking on * Fix tests * Latest * Fix tests * Fix more tests * Fix tests Co-authored-by: Alex Ghiculescu <alex@tanda.co> Co-authored-by: André Luis Leal Cardoso Junior <andrehjr@gmail.com> Co-authored-by: Abhay Nikam <nikam.abhay1@gmail.com> Co-authored-by: Guillermo Iguaran <guilleiguaran@gmail.com>
2021-08-26 16:39:36 +08:00
turbo-rails
Ruby 2.2.3 in windows need nokogiri 1.6.7.rc3 as it's the only version having correct pre-compiled so
2015-09-12 22:04:31 +08:00
tzinfo-data
Update w3c_validtors for Ruby 3 compatibility (#40227) * Update w3c_validtors for Ruby 3 compatibility * Update google-api-client for Ruby 3 compatibility
2020-09-21 13:19:59 +08:00
w3c_validators (~> 1.3.6)
Make file update checker tests more resilient on Windows Without the `wdm` gem, it appears that `listen` keeps an open handle to each of these files, causing them not to be removed when the tempdir tries to clean iteslf up, and then directory to fail to unlink. In addition to fixing that particular failure, we now construct OS agnostic paths, and capture exceptions if the directory fails to unlink so that minitest will report it rather than crash
2016-04-22 00:54:54 +08:00
wdm (>= 0.1.0)
No need to specify webdrivers version to support selenium-webdriver 4.0.0 `webdrivers` 4.7.0 has been released including https://github.com/titusfortner/webdrivers/pull/218 which supports selenium-webdriver 4.0.0 Refer https://github.com/titusfortner/webdrivers/blob/main/CHANGELOG.md#470-2021-10-14 Related to #43456
2021-10-15 07:34:03 +08:00
webdrivers
Extract ActionMailbox::PostfixRelayer
2018-11-26 03:30:05 +08:00
webmock
Ruby 3 does not have webrick by default Railties CI against Ruby 3.0.0-dev has been failing since https://buildkite.com/rails/rails/builds/73338#51165eef-b631-4f9c-8e98-fc210e71e6d1 This pull request addresses the following error. ```ruby $ ruby -v ruby 3.0.0dev (2020-12-13T04:39:57Z master c7530f0d56) [x86_64-linux] $ ruby -Itest -Ilib -I../activesupport/lib -I../actionpack/lib -I../actionview/lib -I../activemodel/lib test/commands/server_test.rb ... snip ... Run options: --seed 54404 .E Error: Rails::Command::ServerCommandTest#test_served_url: LoadError: cannot load such file -- webrick test/commands/server_test.rb:292:in `test_served_url' rails test test/commands/server_test.rb:289 ........................ Finished in 0.303746s, 85.5977 runs/s, 177.7799 assertions/s. 26 runs, 54 assertions, 0 failures, 1 errors, 0 skips $ ``` Related to https://github.com/ruby/ruby/pull/3729 https://bugs.ruby-lang.org/issues/17303
2020-12-13 15:34:39 +08:00
webrick
Use a branch of websocket-client-simple, to work around read/close race
2016-10-06 09:11:18 +08:00
websocket-client-simple!
Generate Bundler 1.10.1 lockfile
2015-05-29 13:40:29 +08:00
BUNDLED WITH
Fix the development container to set the right permissions to bundler
2021-10-13 06:16:38 +08:00
2.2.29