aboutsummaryrefslogtreecommitdiffstats
path: root/Gemfile.lock
Commit message (Collapse)AuthorAgeFilesLines
* Merge pull request #32471 from janko-m/use-image_processing-gemGeorge Claghorn2018-04-231-5/+10
|\ | | | | Use ImageProcessing gem for ActiveStorage variants
| * Use ImageProcessing gem for ActiveStorage variantsJanko Marohnić2018-04-181-5/+10
| | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | 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.
* | Rubocop 0.54Bart de Water2018-04-211-4/+4
|/ | | | Fix `.rubocop.yml: Lint/EndAlignment has the wrong namespace - should be Layout` warning
* Unlock dalli versionyuuji.yaginuma2018-04-111-2/+2
| | | | | The issue was fixed with https://github.com/petergoldstein/dalli/pull/679, and a new version containing that fix was released.
* Merge pull request #32496 from yhirano55/fix_turbolinks_warning_in_railtiesRafael França2018-04-101-3/+3
|\ | | | | Fix turbolinks warning in railties test
| * Fix turbolinks warning in railties testYoshiyuki Hirano2018-04-111-3/+3
| | | | | | | | | | | | | | | | * Upgrade turbolinks from v5.0.1 to v5.1.0 * Fix warning in railties test lib/turbolinks/assertions.rb:17: warning: assigned but unused variable - visit_action
* | Remove upper bound on Capybaraeileencodes2018-04-101-1/+1
|/ | | | | | | There's no reason to block future versions of Capybara since we don't _know_ they are going to break. How will we know if we have a conservative option set? This change prevents us from blocking users who want to upgrade in the future.
* Upgrade Mocha from v1.3.0 to v1.5.0James Mead2018-04-071-1/+1
| | | | Mocha v1.5.0 is currently the latest release.
* Upgrade capybara to 3.0.1 to make sure our tests are passingRafael Mendonça França2018-04-061-1/+3
|
* Fix broken `ServerTest` with Capybara 3.0.0yuuji.yaginuma2018-04-061-9/+9
| | | | | | | 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
* Merge pull request #32065 from ↵Kasper Timm Hansen2018-04-021-7/+5
|\ | | | | | | | | sikachu/move-SourceAnnotationExtractor-under-rails-namespec Move SourceAnnotationExtractor under Rails module
| * Run `bundle update` on bootsnapPrem Sichanugrist2018-03-231-7/+5
| | | | | | | | | | | | 1.2.1 fixes a bug in `Kernel.require` and resolve a test failure. See https://github.com/Shopify/bootsnap/pull/143
* | Bump rack-test to 1.0.0Yuji Yaginuma2018-03-281-1/+1
|/
* Fix `test_config_another_database` failureRyuta Kamizono2018-03-221-3/+3
| | | | | | | | | | | | | | | | | | | | | | | | | Somehow `test_config_another_database` didn't fail on CI, but it will fail locally. https://travis-ci.org/rails/rails/jobs/356212950#L2474-L2482 ``` % bundle exec ruby -w -Itest test/generators/app_generator_test.rb -n test_config_another_database Run options: -n test_config_another_database --seed 7260 # Running: F Failure: AppGeneratorTest#test_config_another_database [test/generators/app_generator_test.rb:417]: Expected /^\s*gem\s+["']mysql2["'], '~> 0.4.4'$*/ to match "source 'https://rubygems.org'\ngit_source(:github) { |repo| \"https://github.com/\#{repo}.git\" }\n\nruby '2.5.0'\n\n# Bundle edge Rails instead: gem 'rails', github: 'rails/rails'\ngem 'rails', '~> 6.0.0.alpha'\n# Use mysql as the database for Active Record\ngem 'mysql2', '>= 0.4.4', '< 0.6.0'\n# Use Puma as the app server\ngem 'puma', '~> 3.11'\n# Use SCSS for stylesheets\ngem 'sass-rails', '~> 5.0'\n# Use Uglifier as compressor for JavaScript assets\ngem 'uglifier', '>= 1.3.0'\n# See https://github.com/rails/execjs#readme for more supported runtimes\n# gem 'mini_racer', platforms: :ruby\n\n# Use CoffeeScript for .coffee assets and views\ngem 'coffee-rails', '~> 4.2'\n# Turbolinks makes navigating your web application faster. Read more: https://github.com/turbolinks/turbolinks\ngem 'turbolinks', '~> 5'\n# Build JSON APIs with ease. Read more: https://github.com/rails/jbuilder\ngem 'jbuilder', '~> 2.5'\n# Use Redis adapter to run Action Cable in production\n# gem 'redis', '~> 4.0'\n# Use ActiveModel has_secure_password\n# gem 'bcrypt', '~> 3.1.7'\n\n# Use ActiveStorage variant\n# gem 'mini_magick', '~> 4.8'\n\n# Use Capistrano for deployment\n# gem 'capistrano-rails', group: :development\n\n# Reduces boot times through caching; required in config/boot.rb\ngem 'bootsnap', '>= 1.1.0', require: false\n\ngroup :development, :test do\n # Call 'byebug' anywhere in the code to stop execution and get a debugger console\n gem 'byebug', platforms: [:mri, :mingw, :x64_mingw]\nend\n\ngroup :development do\n # Access an interactive console on exception pages or by calling 'console' anywhere in the code.\n gem 'web-console', '>= 3.3.0'\n gem 'listen', '>= 3.0.5', '< 3.2'\n # Spring speeds up development by keeping your application running in the background. Read more: https://github.com/rails/spring\n gem 'spring'\n gem 'spring-watcher-listen', '~> 2.0.0'\nend\n\ngroup :test do\n # Adds support for Capybara system testing and selenium driver\n gem 'capybara', '>= 2.15', '< 4.0'\n gem 'selenium-webdriver'\n # Easy installation and use of chromedriver to run system tests with Chrome\n gem 'chromedriver-helper'\nend\n\n# Windows does not include zoneinfo files, so bundle the tzinfo-data gem\ngem 'tzinfo-data', platforms: [:mingw, :mswin, :x64_mingw, :jruby]\n". bin/rails test test/generators/app_generator_test.rb:411 Finished in 0.174681s, 5.7247 runs/s, 34.3483 assertions/s. 1 runs, 6 assertions, 1 failures, 0 errors, 0 skips ```
* Update loofah to mitigate CVE-2018-8048Andrew White2018-03-211-5/+5
| | | | See flavorjones/loofah#144
* Allow any version of dalli less them 2.7.7Rafael Mendonça França2018-03-201-1/+1
|
* Avoid dalli 2.7.7 for nowyuuji.yaginuma2018-03-151-1/+1
| | | | | It's causing a test to fail. Ref: https://travis-ci.org/rails/rails/jobs/353758855#L1433-L1501
* update psych gem to 3.2 stable releaseGaurav Sharma2018-03-101-2/+2
|
* Update Gemfile.lock to reflect Capybara 3.xYuji Yaginuma2018-03-061-1/+1
| | | | Follow up of #32151
* Generate root-relative paths in Active Storage disk service URL methodsGeorge Claghorn2018-03-051-9/+0
| | | | Fixes #32129.
* Update rubocop to the latest versionutilum2018-02-231-10/+9
| | | | | | | | 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
* Update to sinatra 2.0.1Andrew White2018-02-211-5/+5
| | | | | | | | Although not a direct dependency, it's pulled in by Resque for Active Job integration tests so we need to update because the rack-protection gem has a security vulnerability[1]. [1]: https://nvd.nist.gov/vuln/detail/CVE-2018-7212
* Bump mysql2 versionutilum2018-02-151-4/+4
| | | | | Skip 0.4.8 and 0.4.9, which had [Compilation failures against MariaDB Connector/C 3.0.2](https://github.com/brianmario/mysql2/releases/tag/0.4.10).
* Don't force people to upgrade i18n gemRafael Mendonça França2018-02-141-1/+1
|
* Update Gemfile.lockRafael Mendonça França2018-02-141-2/+2
|
* Bump `minitest-server`yuuji.yaginuma2018-02-071-2/+2
| | | | | | In order to use `minitest_bisect` with Minitest 5.11.x, it needs to be updated. Ref: https://github.com/seattlerb/minitest-server/issues/2
* Merge pull request #31914 from utilum/bump_em-socksifyMatthew Draper2018-02-071-1/+1
|\ | | | | Update em-socksify to the latest version
| * Update em-socksify to the latest versionutilum2018-02-061-1/+1
| | | | | | | | Avoid warning: parentheses after method name is interpreted as an argument list, not a decomposed argument
* | Refer to a stable release of SDocRobin Dupret2018-02-061-10/+4
|/
* Start Rails 6.0 development!!!Rafael Mendonça França2018-01-301-39/+41
| | | | :tada::tada::tada:
* Relax minitest versionDaniel Colson2018-01-261-1/+0
| | | | | | | We locked Minitest to 5.11.1 in #31799 because 5.11.2 included a breaking change. The change was fixed in 5.11.3, so we no longer need to lock in the version.
* Lock Minitest 5.11.1Yasuo Honda2018-01-261-0/+1
| | | | | To workaround `undefined method `error?' for` reported at https://travis-ci.org/rails/rails/jobs/333456146
* Update Gemfile.lock to reflect websocket-driver 0.7.0yuuji.yaginuma2018-01-191-1/+1
| | | | Follow up to e1473e0cbfbd97eeea2bc6eefd73bec0d4863359
* Support for connection pooling on mem cache storeGabriel Sobrinho2018-01-181-2/+1
|
* Extract content types from blob dataGeorge Claghorn2018-01-151-0/+13
|
* Use my fork instead of an thrid-party forkRafael Mendonça França2018-01-111-8/+8
| | | | | This will avoid the branch being deleted by mistake making all builds to fail.
* Merge pull request #31671 from larskanis/pg-1.0Rafael Mendonça França2018-01-111-7/+7
|\ | | | | | | PostgreSQL: Allow pg-1.0 gem to be used with ActiveRecord
| * PostgreSQL: Update Gemfile to pg-1.0.0Lars Kanis2018-01-101-7/+7
| | | | | | | | | | | | | | | | | | | | Queue_classic currently limits pg to "< 0.20". It is therefore not used for rails CI tests. There has been a bull request for a while (by a co-worker of mine), which fixes the incompatibilities and extends dependencies to pg-1.x. This patch add this pull request to the Gemfile as an interim solution, until it is merged.
* | Bump Minitest to 5.11.1yuuji.yaginuma2018-01-031-2/+1
|/
* Avoid Minitest 5.11.0 for nowyuuji.yaginuma2018-01-021-1/+2
| | | | | | | | | Seems some tests not work with Minitest 5.11.0. * https://travis-ci.org/rails/rails/jobs/323997512#L1053 * https://travis-ci.org/rails/rails/jobs/323997486#L1055 Ref: https://github.com/seattlerb/minitest/issues/729
* Use released `delayed_job` instead of master versionyuuji.yaginuma2017-12-301-8/+3
| | | | Ref: https://github.com/collectiveidea/delayed_job/blob/master/CHANGELOG.md#414---2017-12-29
* Use `delayed_job` masteryuuji.yaginuma2017-12-231-3/+8
| | | | | For pass Active Job integration tests with Ruby 2.5. Ref: https://github.com/collectiveidea/delayed_job/pull/996
* Update nokogiri version on GemfileGuillermo Iguaran2017-12-141-9/+12
|
* Use released `resque-scheduler` instead of master versionyuuji.yaginuma2017-12-141-11/+6
| | | | | 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
* Use `credentials` instead of `keyfile` in GCS seviceyuuji.yaginuma2017-11-291-18/+18
| | | | | | | | | | | | | 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
* Preparing for 5.2.0.beta2 releaseRafael Mendonça França2017-11-281-36/+36
|
* Preparing for 5.2.0.beta1 releaseRafael Mendonça França2017-11-271-44/+44
|
* Update `rack-test` to 0.8.Guo Xiang Tan2017-11-211-1/+1
|
* Remove unused `em-hiredis`yuuji.yaginuma2017-11-211-7/+0
| | | | `em-hiredis` is unused since 48766e32d31651606b9f68a16015ad05c3b0de2c
* Fix `test_session_store_with_expire_after` failure with rack-test 0.7.1Ryuta Kamizono2017-11-201-1/+1
| | | | https://travis-ci.org/rails/rails/jobs/304428814#L1977
generated by cgit v1.2.3 (git 2.25.1) at 2024-11-03 00:10:16 +0000