2f65a6e502
## Motivation and Context json 3.0.2 loads on Ruby 2.7.0 through 2.7.2 again: it no longer forwards arguments after a leading parameter, the syntax those patch levels could not parse, so the Gemfile no longer has to keep json below 3.0 there, and the CI job pinned to 2.7.0, the minimum the gemspec supports, resolves json 3.0.2 like every other job. The maintainers intend to raise json's own Ruby floor to 2.7.3 in the release after 3.0.2, so those patch levels stay on 3.0.2 by json's gemspec from then on, and no pin of this Gemfile's own is needed for that either. ## How Has This Been Tested? A fresh `bundle install` on Ruby 2.7.2 resolves json 3.0.2, `require "json"` loads it there, and `bundle exec rake test` passes. Ruby 3.0 and later were never affected by the pin. ## Breaking Changes None. The Gemfile is not part of the gem.
33 lines
890 B
Ruby
33 lines
890 B
Ruby
# frozen_string_literal: true
|
|
|
|
source "https://rubygems.org"
|
|
|
|
# Specify runtime dependencies in the gemspec
|
|
gemspec
|
|
|
|
# Specify development dependencies below
|
|
gem "rubocop-minitest", ">= 0.39.0", require: false
|
|
gem "rubocop-rake", require: false
|
|
gem "rubocop-shopify", ">= 2.18", require: false if RUBY_VERSION >= "3.1"
|
|
|
|
gem "puma", ">= 5.0.0"
|
|
gem "rack-cors"
|
|
gem "rackup", ">= 2.1.0"
|
|
|
|
gem "activesupport"
|
|
# Fix io-console install error when Ruby 3.0.
|
|
gem "debug" if RUBY_VERSION >= "3.1"
|
|
# Avoid i18n 1.15.0, which breaks on Ruby 3.1 (ruby-i18n/i18n#735).
|
|
gem "i18n", "!= 1.15.0"
|
|
gem "rake", "~> 13.0"
|
|
gem "sorbet-static-and-runtime" if RUBY_VERSION >= "3.0"
|
|
gem "yard", "~> 0.9"
|
|
gem "yard-sorbet", "~> 0.9" if RUBY_VERSION >= "3.1"
|
|
|
|
group :test do
|
|
gem "event_stream_parser", ">= 1.0"
|
|
gem "faraday", ">= 2.0"
|
|
gem "minitest", "~> 5.1", require: false
|
|
gem "mocha"
|
|
gem "webmock"
|
|
end
|