zenspec 0.1.0 → 0.2.0

checksums.yaml

@@ -1,7 +1,7 @@
 ---
 SHA256:
-  metadata.gz: d022d22c4b5fc8c2ffee7d14364279e78349e1e37a09482ee73fcbd0dd01f11e
-  data.tar.gz: d855d7386485b32de6072fccd59264e7339eb9ad3f47e6d8e6100801b595a907
+  metadata.gz: 7737ee41815ffc6e727f44826dda5052addaa5925860cd1421665ffed41e85e0
+  data.tar.gz: 37c0da188f214be5efe29ac58496a24b2831f2e076d4fb247a1bbbaaec57fa59
 SHA512:
-  metadata.gz: e18625bc7f0ae81b315aa863f88630e5840484f2420f4312e535f872b6ef2e831857847ae41ee7a63bdd29d276ccfbb73cffa300fbd3af4c32e785fadf941560
-  data.tar.gz: 0a4eae628dc12d2b01b49767a6aacca0f55d75cf4abeff5717e598e46554459c31d0dc37c3a620a9f58b39015be0762686ac265faabe129f002778882c195229
+  metadata.gz: cb5d249f606858f4f5835c7889cc6aeacc157ed30e79bac209758c42e5b8abb076e84afdb978ec1c0cbc537d4f1e6c6ba672d53fbcf2f87ae5faa8d3428cbe6b
+  data.tar.gz: 4796a8d28823742fa70c5417918d310f0ebfaed055a26cd7a8938919b35e2d5cc2de5d18b22622af4d46296d41ea861850b66bf28b76fb955243703f1f1f64e3

data/CHANGELOG.md

@@ -1,5 +1,11 @@
 ## [Unreleased]
 
+## [0.2.0] - 2025-11-16
+
+### Changed
+- Updated graphql dependency from ~> 1.12 to ~> 2.5
+- **Breaking**: Requires GraphQL 2.5 or higher
+
 ## [0.1.0] - 2025-11-15
 
 - Initial release

data/README.md

@@ -1,6 +1,6 @@
 # Zenspec
 
-A comprehensive RSpec matcher library for testing GraphQL APIs, Interactor service objects, and Rails applications. Includes Shoulda Matchers integration for clean, expressive tests.
+A comprehensive RSpec matcher library for testing GraphQL APIs, Interactor service objects, and Rails applications.
 
 ## Installation
 
@@ -16,23 +16,9 @@ And then execute:
 bundle install
 ```
 
-Or install it yourself as:
+## Quick Start
 
-```bash
-gem install zenspec
-```
-
-## Features
-
-- **GraphQL Matchers** - Test GraphQL queries, mutations, types, and schemas
-- **Interactor Matchers** - Test service objects with clean syntax
-- **GraphQL Helpers** - Execute queries and mutations with ease
-- **Progress Loader** - Docker-style progress bars for terminal output
-- **Shoulda Matchers** - Automatically configured for Rails models and controllers
-- **Rails Integration** - Automatically loads in Rails applications
-- **Non-Rails Support** - Works in any Ruby project
-
-## Usage
+### 1. Add to your spec helper
 
 ```ruby
 # In your spec/rails_helper.rb or spec/spec_helper.rb
@@ -41,179 +27,24 @@ require "zenspec"
 # Everything is automatically configured!
 ```
 
----
-
-## Progress Loader
-
-Docker-style progress bars for displaying terminal progress.
-
-### RSpec Formatters
-
-Zenspec includes two custom RSpec formatters for displaying test progress:
-
-#### Progress Bar Formatter (Recommended)
-
-Clean, colorful output with status icons:
-
-```bash
-# Use the progress bar formatter
-rspec --require zenspec/formatters/progress_bar_formatter \
-      --format ProgressBarFormatter
-
-# Or add to .rspec file:
-# --require zenspec/formatters/progress_bar_formatter
-# --format ProgressBarFormatter
-```
-
-Output example:
-```
-✔ user_spec.rb creates a new user successfully                        [10% 1/10]
-✔ user_spec.rb validates email presence                               [20% 2/10]
-⠿ user_spec.rb --> sends welcome email                                [30% 3/10]
-✗ post_spec.rb publishes post with valid data                         [40% 4/10]
-⊘ auth_spec.rb authenticates with OAuth                               [50% 5/10]
-```
-
-Format:
-- **Running tests** show an arrow (-->) between filename and description
-- **Completed tests** (passed/failed/pending) show only a space between filename and description
-
-Colors:
-- **Green** ✔ - Passed tests
-- **Red** ✗ - Failed tests
-- **Yellow** ⠿ - Currently running test (with arrow)
-- **Cyan** ⊘ - Pending/skipped tests
-
-#### Docker-Style Progress Formatter
-
-Alternative formatter with Docker-style progress bars:
-
-```bash
-# Use the Docker-style formatter
-rspec --require zenspec/formatters/progress_formatter \
-      --format Zenspec::Formatters::ProgressFormatter
-```
-
-Output example:
-```
-[=====================>            ] 65% 13/20 spec/models/user_spec.rb:42
-```
-
-### Programmatic Usage
-
-Use the progress loader in your code:
-
-```ruby
-# Basic usage
-loader = Zenspec::ProgressLoader.new(total: 100, description: "Processing files")
-
-100.times do |i|
-  # Do some work...
-  loader.update(i + 1, description: "Processing file #{i + 1}/100")
-  sleep(0.1)
-end
+### 2. (Optional) Add progress bar formatter to `.rspec`
 
-loader.finish(description: "Processing complete!")
 ```
-
-### Custom Width
-
-```ruby
-# Custom progress bar width (default is 40)
-loader = Zenspec::ProgressLoader.new(
-  total: 50,
-  width: 60,
-  description: "Downloading layers"
-)
-
-loader.increment(description: "Layer 1/50")
-loader.increment(description: "Layer 2/50")
-# ...
-loader.finish
+--require zenspec/formatters/progress_bar_formatter
+--format ProgressBarFormatter
+--color
+--require spec_helper
 ```
 
-### Time Estimates
-
-The progress loader automatically calculates and displays time information:
-
-```ruby
-loader = Zenspec::ProgressLoader.new(total: 1000)
-
-loader.update(250)
-# Output: [==========>                     ] 25% 250/1000 1s/4s
-
-loader.update(500)
-# Output: [====================>           ] 50% 500/1000 2s/4s
-```
+That's it! You can now use all GraphQL and Interactor matchers in your tests.
 
 ---
 
-## Interactor Matchers
-
-### Basic Usage
-
-```ruby
-RSpec.describe CreateUser do
-  subject(:result) { described_class.call(params) }
+## GraphQL Testing
 
-  context "with valid params" do
-    let(:params) { { name: "John", email: "john@example.com" } }
+### Response Matchers
 
-    # Shoulda-style one-liners
-    it { is_expected.to succeed }
-    it { is_expected.to set_context(:user) }
-    it { is_expected.to succeed.with_data(kind_of(User)) }
-  end
-
-  context "with invalid params" do
-    let(:params) { { name: "", email: "invalid" } }
-
-    it { is_expected.to fail_interactor }
-    it { is_expected.to fail_interactor.with_error("validation_failed") }
-    it { is_expected.to have_error_code("validation_failed") }
-  end
-end
-```
-
-### Available Matchers
-
-#### `succeed`
-
-```ruby
-expect(result).to succeed
-expect(result).to succeed.with_data("expected value")
-expect(result).to succeed.with_context(:user_id, 123)
-expect(CreateUser).to succeed  # Works with classes too
-```
-
-#### `fail_interactor`
-
-```ruby
-expect(result).to fail_interactor
-expect(result).to fail_interactor.with_error("invalid_input")
-expect(result).to fail_interactor.with_errors("error1", "error2")
-```
-
-#### `have_error_code` / `have_error_codes`
-
-```ruby
-expect(result).to have_error_code("not_found")
-expect(result).to have_error_codes("error1", "error2")
-```
-
-#### `set_context`
-
-```ruby
-expect(result).to set_context(:user)
-expect(result).to set_context(:user_id, 123)
-expect(result).to set_context(:data).to(expected_value)
-```
-
----
-
-## GraphQL Response Matchers
-
-### Basic Usage
+Test GraphQL query and mutation responses with clean, expressive matchers.
 
 ```ruby
 RSpec.describe "User Queries" do
@@ -231,383 +62,209 @@ RSpec.describe "User Queries" do
     GQL
   end
 
-  # Shoulda-style
+  # Basic checks
   it { is_expected.to succeed_graphql }
   it { is_expected.to have_graphql_data("user") }
   it { is_expected.to have_graphql_data("user", "name").with_value("John") }
-end
-```
-
-### Available Matchers
-
-#### `have_graphql_data`
-
-```ruby
-# Basic checks
-expect(result).to have_graphql_data
-expect(result).to have_graphql_data("user")
-expect(result).to have_graphql_data("user", "id")
-
-# With specific value
-expect(result).to have_graphql_data("user", "name").with_value("John Doe")
-
-# Partial matching (subset)
-expect(result).to have_graphql_data("user").matching(
-  id: "123",
-  name: "John"
-  # other fields can exist but aren't checked
-)
-
-# Inclusion (contains these values)
-expect(result).to have_graphql_data("user").that_includes(name: "John")
-
-# Presence checks
-expect(result).to have_graphql_data("users").that_is_present
-expect(result).to have_graphql_data("deletedAt").that_is_null
-
-# Array count
-expect(result).to have_graphql_data("users").with_count(5)
-```
-
-#### `have_graphql_errors`
-
-```ruby
-# Basic error check
-expect(result).to have_graphql_errors
 
-# With specific message
-expect(result).to have_graphql_error.with_message("Not found")
-
-# With extensions
-expect(result).to have_graphql_error.with_extensions(code: "NOT_FOUND")
-
-# At specific path
-expect(result).to have_graphql_error.at_path(["user", "email"])
-```
-
-#### `succeed_graphql`
-
-```ruby
-expect(result).to succeed_graphql
-```
-
-#### `have_graphql_field` / `have_graphql_fields`
-
-```ruby
-data = result.dig("data", "user")
+  # Matching data
+  it "returns correct user data" do
+    expect(result).to have_graphql_data("user").matching(
+      id: user.id,
+      name: "John Doe",
+      email: "john@example.com"
+    )
+  end
 
-expect(data).to have_graphql_field("name")
-expect(data).to have_graphql_field(:email)
+  # Array checks
+  it { is_expected.to have_graphql_data("users").with_count(5) }
+  it { is_expected.to have_graphql_data("users").that_is_present }
 
-expect(data).to have_graphql_fields(
-  id: "123",
-  name: "John Doe",
-  email: "john@example.com"
-)
+  # Error handling
+  expect(result).to have_graphql_error.with_message("Not found")
+  expect(result).to have_graphql_error.with_extensions(code: "NOT_FOUND")
+  expect(result).to have_graphql_error.at_path(["user", "email"])
+end
 ```
 
----
+**Available matchers:**
+- `succeed_graphql` - Verify successful query/mutation
+- `have_graphql_data(path...)` - Check response data
+- `have_graphql_error` / `have_graphql_errors` - Verify errors
+- `have_graphql_field(name)` / `have_graphql_fields(hash)` - Check field presence
 
-## GraphQL Type Matchers
+**Data matchers:**
+- `.with_value(expected)` - Exact value match
+- `.matching(hash)` - Partial hash match
+- `.that_includes(hash)` - Includes these values
+- `.that_is_present` / `.that_is_null` - Presence checks
+- `.with_count(n)` - Array size
 
-Test your GraphQL schema types, queries, and mutations.
+### Type Matchers
 
-### Type Field Testing
+Test your GraphQL schema types, fields, and arguments.
 
 ```ruby
 RSpec.describe UserType do
   subject { described_class }
 
-  # Shoulda-style
+  # Field testing
   it { is_expected.to have_field(:id).of_type("ID!") }
   it { is_expected.to have_field(:name).of_type("String!") }
   it { is_expected.to have_field(:email).of_type("String") }
   it { is_expected.to have_field(:posts).of_type("[Post!]!") }
 
-  # With arguments
+  # Fields with arguments
   it do
     is_expected.to have_field(:posts)
       .with_argument(:limit, "Int")
       .with_argument(:offset, "Int")
   end
 end
-```
-
-### Enum Testing
 
-```ruby
+# Enum testing
 RSpec.describe StatusEnum do
   subject { described_class }
 
   it { is_expected.to have_enum_values("ACTIVE", "INACTIVE", "PENDING") }
 end
-```
 
-### Schema Query/Mutation Testing
-
-```ruby
+# Schema queries and mutations
 RSpec.describe AppSchema do
   subject { described_class }
 
-  # Query fields
   it { is_expected.to have_query(:user).with_argument(:id, "ID!") }
-  it { is_expected.to have_query(:users).of_type("[User!]!") }
-
-  # Mutation fields
-  it { is_expected.to have_mutation(:createUser).with_argument(:input, "CreateUserInput!") }
-  it { is_expected.to have_mutation(:deleteUser).of_type("Boolean!") }
-end
-```
-
-### Field Argument Testing
-
-```ruby
-RSpec.describe "UserType posts field" do
-  subject(:field) { UserType.fields["posts"] }
-
-  it { is_expected.to have_argument(:limit).of_type("Int") }
-  it { is_expected.to have_argument(:status).of_type("Status!") }
+  it { is_expected.to have_mutation(:createUser).of_type("UserPayload!") }
 end
 ```
 
----
-
-## GraphQL Execution Helpers
+**Available matchers:**
+- `have_field(name)` - Check field exists
+- `of_type(type)` - Verify field type
+- `with_argument(name, type)` - Check field arguments
+- `have_argument(name)` - Check argument on field
+- `have_enum_values(*values)` - Verify enum values
+- `have_query(name)` / `have_mutation(name)` - Schema-level checks
 
-Execute GraphQL queries and mutations with ease.
+### GraphQL Helpers
 
-### `graphql_execute`
+Execute queries and mutations easily in your tests.
 
 ```ruby
-# Basic execution
+# Execute query
 result = graphql_execute(query, variables: { id: "123" }, context: { current_user: user })
 
-# With custom schema
-result = graphql_execute(query, schema: MySchema)
-```
-
-### `graphql_execute_as`
-
-```ruby
-# Automatically adds user to context
+# Execute as user (automatically adds to context)
 result = graphql_execute_as(user, query, variables: { id: "123" })
 
-# Custom context key
-result = graphql_execute_as(user, query, context_key: :admin)
-```
-
-### `graphql_mutate`
-
-```ruby
-# Execute mutations
+# Execute mutation
 result = graphql_mutate(mutation, input: { name: "John" }, context: { current_user: user })
-```
-
-### `graphql_mutate_as`
 
-```ruby
 # Execute mutation as user
 result = graphql_mutate_as(user, mutation, input: { name: "John" })
 ```
 
 ---
 
-## Shoulda Matchers
-
-Automatically includes and configures [Shoulda Matchers](https://github.com/thoughtbot/shoulda-matchers) for Rails projects.
-
-### Model Validations
-
-```ruby
-RSpec.describe User do
-  subject { build(:user) }
-
-  # Validations
-  it { is_expected.to validate_presence_of(:email) }
-  it { is_expected.to validate_uniqueness_of(:email).case_insensitive }
-  it { is_expected.to validate_length_of(:password).is_at_least(8) }
-
-  # Associations
-  it { is_expected.to have_many(:posts).dependent(:destroy) }
-  it { is_expected.to belong_to(:organization) }
-
-  # Database columns
-  it { is_expected.to have_db_column(:email).of_type(:string) }
-  it { is_expected.to have_db_index(:email).unique }
-end
-```
-
-### Controller Testing
-
-```ruby
-RSpec.describe UsersController do
-  describe "GET #index" do
-    it { is_expected.to respond_with(:success) }
-    it { is_expected.to render_template(:index) }
-  end
-
-  describe "POST #create" do
-    it { is_expected.to permit(:name, :email).for(:create) }
-  end
-end
-```
-
----
-
-## Complete Examples
+## Interactor Testing
 
-### Full Interactor Test Suite
+Test your Interactor service objects with clean, expressive matchers.
 
 ```ruby
 RSpec.describe CreateUser do
   subject(:result) { described_class.call(params) }
 
-  describe "success cases" do
-    let(:params) { { name: "John Doe", email: "john@example.com" } }
+  context "with valid params" do
+    let(:params) { { name: "John", email: "john@example.com" } }
 
+    # Basic checks
     it { is_expected.to succeed }
     it { is_expected.to set_context(:user) }
     it { is_expected.to succeed.with_context(:user, kind_of(User)) }
-
-    it "creates a user with correct attributes" do
-      expect(result).to succeed
-      expect(result.user.name).to eq("John Doe")
-      expect(result.user.email).to eq("john@example.com")
-    end
   end
 
-  describe "failure cases" do
-    context "with blank name" do
-      let(:params) { { name: "", email: "john@example.com" } }
-
-      it { is_expected.to fail_interactor }
-      it { is_expected.to fail_interactor.with_error("blank_name") }
-      it { is_expected.to have_error_code("blank_name") }
-    end
-
-    context "with duplicate email" do
-      before { create(:user, email: "john@example.com") }
-
-      let(:params) { { name: "John", email: "john@example.com" } }
+  context "with invalid params" do
+    let(:params) { { name: "", email: "invalid" } }
 
-      it { is_expected.to fail_interactor.with_error("duplicate_email") }
-    end
+    it { is_expected.to fail_interactor }
+    it { is_expected.to fail_interactor.with_error("validation_failed") }
+    it { is_expected.to have_error_code("validation_failed") }
   end
 end
 ```
 
-### Full GraphQL Test Suite
-
-```ruby
-RSpec.describe "User Queries" do
-  let(:user) { create(:user, name: "John Doe", email: "john@example.com") }
-
-  describe "user query" do
-    subject(:result) { graphql_execute_as(user, query, variables: { id: user.id }) }
-
-    let(:query) do
-      <<~GQL
-        query GetUser($id: ID!) {
-          user(id: $id) {
-            id
-            name
-            email
-            posts {
-              id
-              title
-            }
-          }
-        }
-      GQL
-    end
-
-    it { is_expected.to succeed_graphql }
-    it { is_expected.to have_graphql_data("user") }
+**Available matchers:**
+- `succeed` - Verify interactor succeeded
+  - `.with_context(key, value)` - Check context value
+  - `.with_data(value)` - Check context.data value
+- `fail_interactor` - Verify interactor failed
+  - `.with_error(code)` - Check single error code
+  - `.with_errors(*codes)` - Check multiple error codes
+- `set_context(key, value)` - Check context was set
+- `have_error_code(code)` / `have_error_codes(*codes)` - Check error codes
 
-    it "returns correct user data" do
-      expect(result).to have_graphql_data("user").matching(
-        id: user.id,
-        name: "John Doe",
-        email: "john@example.com"
-      )
-    end
+---
 
-    it { is_expected.to have_graphql_data("user", "posts").that_is_present }
+## Shoulda Matchers
 
-    context "when user has posts" do
-      before { create_list(:post, 3, user: user) }
+Automatically includes and configures [Shoulda Matchers](https://github.com/thoughtbot/shoulda-matchers) for Rails projects.
 
-      it { is_expected.to have_graphql_data("user", "posts").with_count(3) }
-    end
+```ruby
+RSpec.describe User do
+  subject { build(:user) }
 
-    context "when not authenticated" do
-      subject(:result) { graphql_execute(query, variables: { id: user.id }) }
+  # Validations
+  it { is_expected.to validate_presence_of(:email) }
+  it { is_expected.to validate_uniqueness_of(:email).case_insensitive }
 
-      it { is_expected.to have_graphql_error.with_message("Authentication required") }
-      it { is_expected.to have_graphql_error.with_extensions(code: "UNAUTHENTICATED") }
-    end
-  end
+  # Associations
+  it { is_expected.to have_many(:posts).dependent(:destroy) }
+  it { is_expected.to belong_to(:organization) }
 end
 ```
 
-### Full GraphQL Type Test Suite
-
-```ruby
-RSpec.describe Types::UserType do
-  subject { described_class }
+---
 
-  # Basic fields
-  it { is_expected.to have_field(:id).of_type("ID!") }
-  it { is_expected.to have_field(:name).of_type("String!") }
-  it { is_expected.to have_field(:email).of_type("String") }
-  it { is_expected.to have_field(:createdAt).of_type("ISO8601DateTime!") }
+## Progress Bar Formatter
 
-  # Associations
-  it { is_expected.to have_field(:posts).of_type("[Post!]!") }
-  it { is_expected.to have_field(:organization).of_type("Organization") }
+Clean, colorful test output with status icons.
 
-  # Fields with arguments
-  describe "posts field" do
-    subject(:field) { described_class.fields["posts"] }
+### Setup
 
-    it { is_expected.to have_argument(:limit).of_type("Int") }
-    it { is_expected.to have_argument(:offset).of_type("Int") }
-    it { is_expected.to have_argument(:status).of_type("PostStatus") }
-  end
-end
+Add to your `.rspec` file:
 
-RSpec.describe Types::PostStatusEnum do
-  subject { described_class }
+```
+--require zenspec/formatters/progress_bar_formatter
+--format ProgressBarFormatter
+```
 
-  it { is_expected.to have_enum_values("DRAFT", "PUBLISHED", "ARCHIVED") }
-end
+Or use via command line:
 
-RSpec.describe AppSchema do
-  subject { described_class }
+```bash
+rspec --require zenspec/formatters/progress_bar_formatter --format ProgressBarFormatter
+```
 
-  describe "queries" do
-    it { is_expected.to have_query(:user).with_argument(:id, "ID!") }
-    it { is_expected.to have_query(:users).of_type("[User!]!") }
-    it { is_expected.to have_query(:currentUser).of_type("User") }
-  end
+### Output
 
-  describe "mutations" do
-    it { is_expected.to have_mutation(:createUser).with_argument(:input, "CreateUserInput!") }
-    it { is_expected.to have_mutation(:updateUser).with_argument(:input, "UpdateUserInput!") }
-    it { is_expected.to have_mutation(:deleteUser).of_type("Boolean!") }
-  end
-end
 ```
+✔ user_spec.rb                                                [10% 1/10]
+✔ post_spec.rb                                                [20% 2/10]
+⠿ auth_spec.rb --> authenticates with OAuth                   [30% 3/10]
+```
+
+**Icons:**
+- ✔ Green - Passed
+- ✗ Red - Failed
+- ⠿ Yellow - Running (shows test description)
+- ⊘ Cyan - Pending
 
 ---
 
 ## Configuration
 
-Zenspec works out of the box with sensible defaults. For Rails applications, it automatically configures itself through a Railtie.
+Zenspec works out of the box with sensible defaults. For Rails applications, it automatically configures itself.
 
-### Manual Configuration (Non-Rails)
-
-If you're not using Rails, the matchers are still automatically included when you require zenspec:
+### Non-Rails Projects
 
 ```ruby
 # spec/spec_helper.rb
@@ -620,18 +277,14 @@ require "zenspec"
 
 ## Development
 
-After checking out the repo, run `bin/setup` to install dependencies. Then, run `rake spec` to run the tests. You can also run `bin/console` for an interactive prompt that will allow you to experiment.
+After checking out the repo, run `bin/setup` to install dependencies. Then, run `rake spec` to run the tests.
 
-To install this gem onto your local machine, run `bundle exec rake install`. To release a new version, update the version number in `version.rb`, and then run `bundle exec rake release`, which will create a git tag for the version, push git commits and the created tag, and push the `.gem` file to [rubygems.org](https://rubygems.org).
+To install this gem onto your local machine, run `bundle exec rake install`.
 
 ## Contributing
 
-Bug reports and pull requests are welcome on GitHub at https://github.com/zyxzen/zenspec. This project is intended to be a safe, welcoming space for collaboration, and contributors are expected to adhere to the [code of conduct](https://github.com/zyxzen/zenspec/blob/main/CODE_OF_CONDUCT.md).
+Bug reports and pull requests are welcome on GitHub at https://github.com/zyxzen/zenspec.
 
 ## License
 
 The gem is available as open source under the terms of the [MIT License](https://opensource.org/licenses/MIT).
-
-## Code of Conduct
-
-Everyone interacting in the Zenspec project's codebases, issue trackers, chat rooms and mailing lists is expected to follow the [code of conduct](https://github.com/zyxzen/zenspec/blob/main/CODE_OF_CONDUCT.md).

data/lib/zenspec/version.rb

@@ -1,5 +1,5 @@
 # frozen_string_literal: true
 
 module Zenspec
-  VERSION = "0.1.0"
+  VERSION = "0.2.0"
 end

metadata

@@ -1,7 +1,7 @@
 --- !ruby/object:Gem::Specification
 name: zenspec
 version: !ruby/object:Gem::Version
-  version: 0.1.0
+  version: 0.2.0
 platform: ruby
 authors:
 - Wilson Anciro
@@ -15,14 +15,14 @@ dependencies:
     requirements:
     - - "~>"
       - !ruby/object:Gem::Version
-        version: '1.12'
+        version: '2.5'
   type: :runtime
   prerelease: false
   version_requirements: !ruby/object:Gem::Requirement
     requirements:
     - - "~>"
       - !ruby/object:Gem::Version
-        version: '1.12'
+        version: '2.5'
 - !ruby/object:Gem::Dependency
   name: interactor
   requirement: !ruby/object:Gem::Requirement