strong_migrations 0.7.6 → 0.8.0

checksums.yaml

@@ -1,7 +1,7 @@
 ---
 SHA256:
-  metadata.gz: f16481df30c6b961477b4a537034097aa1d41a262bd7f2741c40b7e6dae9cb9e
-  data.tar.gz: 816bc9a4f9810bce6ac6d5e0a52b185800515794ca5e3d27b5f4d512a9190115
+  metadata.gz: 1f885cc0a8b0fb30e3bc4d000e82584fdf3850943563b4b426d3cfc39d70015c
+  data.tar.gz: d0dd29ea45ccc3b7c571e8bf03fa98c401d5489d1f5459488a0eff411cf6880e
 SHA512:
-  metadata.gz: 2ac9f7c38958c1cc2e80efa3f895730087ac92a3675be31c308f9f8df827ced3323ca8bc3e69c99e2a79b92ef0a5a8b595a76715bf55c45b5698fcdd43b5a586
-  data.tar.gz: 2cee8d3013ae8780f0bcbce33f22a219375c29f059335902cdfe2285ec557307229b7ec4544e6be59ea1ee7cd039f2b23e9b3693efc41f11f677cbbed1495896
+  metadata.gz: c03a023d4c593d2868e524ca0f3e7ebd93e07e087e02f0d7090210b00fdb1fdc50d2abb74ab7df4131bddc6052fc5b9c10ce902ede8c708927476e40ad49d07f
+  data.tar.gz: 479e34db0101a15e1db1a593f01773da5665baa5cda3403ad32ea58dca00a0d0faee0ef813cf1975b7e9f99f1591e7f4f2be5c456c96fd6ae4633b48b6a0b3b4

data/CHANGELOG.md

@@ -1,3 +1,20 @@
+## 0.8.0 (2022-02-09)
+
+- Fixed error with versioned schema with Active Record 7.0.2+
+- Dropped support for Ruby < 2.6 and Active Record < 5.2
+
+## 0.7.9 (2021-12-15)
+
+- Fixed error with multiple databases with Active Record 7
+
+## 0.7.8 (2021-08-03)
+
+- Fixed issue with `add_reference ..., foreign_key: {to_table: ...}` with `safe_by_default`
+
+## 0.7.7 (2021-06-07)
+
+- Removed timeouts and `auto_analyze` from schema load
+
 ## 0.7.6 (2021-01-17)
 
 - Fixed `NOT NULL` constraint check for quoted columns

data/LICENSE.txt

@@ -1,4 +1,4 @@
-Copyright (c) 2013 Bob Remeika and David Waller, 2015-2021 Andrew Kane
+Copyright (c) 2013 Bob Remeika and David Waller, 2015-2022 Andrew Kane
 
 MIT License
 

data/README.md

@@ -15,7 +15,7 @@ Supports for PostgreSQL, MySQL, and MariaDB
 Add this line to your application’s Gemfile:
 
 ```ruby
-gem 'strong_migrations'
+gem "strong_migrations"
 ```
 
 And run:
@@ -43,7 +43,7 @@ end
 
 Deploy the code, then wrap this step in a safety_assured { ... } block.
 
-class RemoveColumn < ActiveRecord::Migration[6.1]
+class RemoveColumn < ActiveRecord::Migration[7.0]
   def change
     safety_assured { remove_column :users, :name }
   end
@@ -90,7 +90,7 @@ You can also add [custom checks](#custom-checks) or [disable specific checks](#d
 Active Record caches database columns at runtime, so if you drop a column, it can cause exceptions until your app reboots.
 
 ```ruby
-class RemoveSomeColumnFromUsers < ActiveRecord::Migration[6.1]
+class RemoveSomeColumnFromUsers < ActiveRecord::Migration[7.0]
   def change
     remove_column :users, :some_column
   end
@@ -111,7 +111,7 @@ end
 3. Write a migration to remove the column (wrap in `safety_assured` block)
 
   ```ruby
-  class RemoveSomeColumnFromUsers < ActiveRecord::Migration[6.1]
+  class RemoveSomeColumnFromUsers < ActiveRecord::Migration[7.0]
     def change
       safety_assured { remove_column :users, :some_column }
     end
@@ -119,6 +119,7 @@ end
   ```
 
 4. Deploy and run migration
+5. Remove the line added in step 1
 
 ### Adding a column with a default value
 
@@ -127,7 +128,7 @@ end
 In earlier versions of Postgres, MySQL, and MariaDB, adding a column with a default value to an existing table causes the entire table to be rewritten. During this time, reads and writes are blocked in Postgres, and writes are blocked in MySQL and MariaDB.
 
 ```ruby
-class AddSomeColumnToUsers < ActiveRecord::Migration[6.1]
+class AddSomeColumnToUsers < ActiveRecord::Migration[7.0]
   def change
     add_column :users, :some_column, :text, default: "default_value"
   end
@@ -141,7 +142,7 @@ In Postgres 11+, MySQL 8.0.12+, and MariaDB 10.3.2+, this no longer requires a t
 Instead, add the column without a default value, then change the default.
 
 ```ruby
-class AddSomeColumnToUsers < ActiveRecord::Migration[6.1]
+class AddSomeColumnToUsers < ActiveRecord::Migration[7.0]
   def up
     add_column :users, :some_column, :text
     change_column_default :users, :some_column, "default_value"
@@ -162,7 +163,7 @@ See the next section for how to backfill.
 Active Record creates a transaction around each migration, and backfilling in the same transaction that alters a table keeps the table locked for the [duration of the backfill](https://wework.github.io/data/2015/11/05/add-columns-with-default-values-to-large-tables-in-rails-postgres/).
 
 ```ruby
-class AddSomeColumnToUsers < ActiveRecord::Migration[6.1]
+class AddSomeColumnToUsers < ActiveRecord::Migration[7.0]
   def change
     add_column :users, :some_column, :text
     User.update_all some_column: "default_value"
@@ -177,7 +178,7 @@ Also, running a single query to update data can cause issues for large tables.
 There are three keys to backfilling safely: batching, throttling, and running it outside a transaction. Use the Rails console or a separate migration with `disable_ddl_transaction!`.
 
 ```ruby
-class BackfillSomeColumn < ActiveRecord::Migration[6.1]
+class BackfillSomeColumn < ActiveRecord::Migration[7.0]
   disable_ddl_transaction!
 
   def up
@@ -196,7 +197,7 @@ end
 Changing the type of a column causes the entire table to be rewritten. During this time, reads and writes are blocked in Postgres, and writes are blocked in MySQL and MariaDB.
 
 ```ruby
-class ChangeSomeColumnType < ActiveRecord::Migration[6.1]
+class ChangeSomeColumnType < ActiveRecord::Migration[7.0]
   def change
     change_column :users, :some_column, :new_type
   end
@@ -235,7 +236,7 @@ A safer approach is to:
 Renaming a column that’s in use will cause errors in your application.
 
 ```ruby
-class RenameSomeColumn < ActiveRecord::Migration[6.1]
+class RenameSomeColumn < ActiveRecord::Migration[7.0]
   def change
     rename_column :users, :some_column, :new_name
   end
@@ -260,7 +261,7 @@ A safer approach is to:
 Renaming a table that’s in use will cause errors in your application.
 
 ```ruby
-class RenameUsersToCustomers < ActiveRecord::Migration[6.1]
+class RenameUsersToCustomers < ActiveRecord::Migration[7.0]
   def change
     rename_table :users, :customers
   end
@@ -285,7 +286,7 @@ A safer approach is to:
 The `force` option can drop an existing table.
 
 ```ruby
-class CreateUsers < ActiveRecord::Migration[6.1]
+class CreateUsers < ActiveRecord::Migration[7.0]
   def change
     create_table :users, force: true do |t|
       # ...
@@ -299,7 +300,7 @@ end
 Create tables without the `force` option.
 
 ```ruby
-class CreateUsers < ActiveRecord::Migration[6.1]
+class CreateUsers < ActiveRecord::Migration[7.0]
   def change
     create_table :users do |t|
       # ...
@@ -319,7 +320,7 @@ If you intend to drop an existing table, run `drop_table` first.
 Adding a check constraint blocks reads and writes in Postgres and blocks writes in MySQL and MariaDB while every row is checked.
 
 ```ruby
-class AddCheckConstraint < ActiveRecord::Migration[6.1]
+class AddCheckConstraint < ActiveRecord::Migration[7.0]
   def change
     add_check_constraint :users, "price > 0", name: "price_check"
   end
@@ -331,7 +332,7 @@ end
 Add the check constraint without validating existing rows:
 
 ```ruby
-class AddCheckConstraint < ActiveRecord::Migration[6.1]
+class AddCheckConstraint < ActiveRecord::Migration[7.0]
   def change
     add_check_constraint :users, "price > 0", name: "price_check", validate: false
   end
@@ -341,7 +342,7 @@ end
 Then validate them in a separate migration.
 
 ```ruby
-class ValidateCheckConstraint < ActiveRecord::Migration[6.1]
+class ValidateCheckConstraint < ActiveRecord::Migration[7.0]
   def change
     validate_check_constraint :users, name: "price_check"
   end
@@ -361,7 +362,7 @@ end
 Setting `NOT NULL` on an existing column blocks reads and writes while every row is checked.
 
 ```ruby
-class SetSomeColumnNotNull < ActiveRecord::Migration[6.1]
+class SetSomeColumnNotNull < ActiveRecord::Migration[7.0]
   def change
     change_column_null :users, :some_column, false
   end
@@ -375,7 +376,7 @@ Instead, add a check constraint.
 For Rails 6.1, use:
 
 ```ruby
-class SetSomeColumnNotNull < ActiveRecord::Migration[6.1]
+class SetSomeColumnNotNull < ActiveRecord::Migration[7.0]
   def change
     add_check_constraint :users, "some_column IS NOT NULL", name: "users_some_column_null", validate: false
   end
@@ -399,7 +400,7 @@ Then validate it in a separate migration. A `NOT NULL` check constraint is [func
 For Rails 6.1, use:
 
 ```ruby
-class ValidateSomeColumnNotNull < ActiveRecord::Migration[6.1]
+class ValidateSomeColumnNotNull < ActiveRecord::Migration[7.0]
   def change
     validate_check_constraint :users, name: "users_some_column_null"
 
@@ -437,7 +438,7 @@ end
 Strong Migrations can’t ensure safety for raw SQL statements. Make really sure that what you’re doing is safe, then use:
 
 ```ruby
-class ExecuteSQL < ActiveRecord::Migration[6.1]
+class ExecuteSQL < ActiveRecord::Migration[7.0]
   def change
     safety_assured { execute "..." }
   end
@@ -453,7 +454,7 @@ end
 In Postgres, adding an index non-concurrently blocks writes.
 
 ```ruby
-class AddSomeIndexToUsers < ActiveRecord::Migration[6.1]
+class AddSomeIndexToUsers < ActiveRecord::Migration[7.0]
   def change
     add_index :users, :some_column
   end
@@ -465,7 +466,7 @@ end
 Add indexes concurrently.
 
 ```ruby
-class AddSomeIndexToUsers < ActiveRecord::Migration[6.1]
+class AddSomeIndexToUsers < ActiveRecord::Migration[7.0]
   disable_ddl_transaction!
 
   def change
@@ -491,7 +492,7 @@ rails g index table column
 Rails adds an index non-concurrently to references by default, which blocks writes in Postgres.
 
 ```ruby
-class AddReferenceToUsers < ActiveRecord::Migration[6.1]
+class AddReferenceToUsers < ActiveRecord::Migration[7.0]
   def change
     add_reference :users, :city
   end
@@ -503,7 +504,7 @@ end
 Make sure the index is added concurrently.
 
 ```ruby
-class AddReferenceToUsers < ActiveRecord::Migration[6.1]
+class AddReferenceToUsers < ActiveRecord::Migration[7.0]
   disable_ddl_transaction!
 
   def change
@@ -521,7 +522,7 @@ end
 In Postgres, adding a foreign key blocks writes on both tables.
 
 ```ruby
-class AddForeignKeyOnUsers < ActiveRecord::Migration[6.1]
+class AddForeignKeyOnUsers < ActiveRecord::Migration[7.0]
   def change
     add_foreign_key :users, :orders
   end
@@ -531,7 +532,7 @@ end
 or
 
 ```ruby
-class AddReferenceToUsers < ActiveRecord::Migration[6.1]
+class AddReferenceToUsers < ActiveRecord::Migration[7.0]
   def change
     add_reference :users, :order, foreign_key: true
   end
@@ -540,52 +541,26 @@ end
 
 #### Good
 
-Add the foreign key without validating existing rows, then validate them in a separate migration.
-
-For Rails 5.2+, use:
+Add the foreign key without validating existing rows:
 
 ```ruby
-class AddForeignKeyOnUsers < ActiveRecord::Migration[6.1]
+class AddForeignKeyOnUsers < ActiveRecord::Migration[7.0]
   def change
     add_foreign_key :users, :orders, validate: false
   end
 end
 ```
 
-Then:
+Then validate them in a separate migration.
 
 ```ruby
-class ValidateForeignKeyOnUsers < ActiveRecord::Migration[6.1]
+class ValidateForeignKeyOnUsers < ActiveRecord::Migration[7.0]
   def change
     validate_foreign_key :users, :orders
   end
 end
 ```
 
-For Rails < 5.2, use:
-
-```ruby
-class AddForeignKeyOnUsers < ActiveRecord::Migration[5.1]
-  def change
-    safety_assured do
-      execute 'ALTER TABLE "users" ADD CONSTRAINT "fk_rails_c1e9b98e31" FOREIGN KEY ("order_id") REFERENCES "orders" ("id") NOT VALID'
-    end
-  end
-end
-```
-
-Then:
-
-```ruby
-class ValidateForeignKeyOnUsers < ActiveRecord::Migration[5.1]
-  def change
-    safety_assured do
-      execute 'ALTER TABLE "users" VALIDATE CONSTRAINT "fk_rails_c1e9b98e31"'
-    end
-  end
-end
-```
-
 ### Adding a json column
 
 #### Bad
@@ -593,7 +568,7 @@ end
 In Postgres, there’s no equality operator for the `json` column type, which can cause errors for existing `SELECT DISTINCT` queries in your application.
 
 ```ruby
-class AddPropertiesToUsers < ActiveRecord::Migration[6.1]
+class AddPropertiesToUsers < ActiveRecord::Migration[7.0]
   def change
     add_column :users, :properties, :json
   end
@@ -605,7 +580,7 @@ end
 Use `jsonb` instead.
 
 ```ruby
-class AddPropertiesToUsers < ActiveRecord::Migration[6.1]
+class AddPropertiesToUsers < ActiveRecord::Migration[7.0]
   def change
     add_column :users, :properties, :jsonb
   end
@@ -619,7 +594,7 @@ end
 Adding a non-unique index with more than three columns rarely improves performance.
 
 ```ruby
-class AddSomeIndexToUsers < ActiveRecord::Migration[6.1]
+class AddSomeIndexToUsers < ActiveRecord::Migration[7.0]
   def change
     add_index :users, [:a, :b, :c, :d]
   end
@@ -631,7 +606,7 @@ end
 Instead, start an index with columns that narrow down the results the most.
 
 ```ruby
-class AddSomeIndexToUsers < ActiveRecord::Migration[6.1]
+class AddSomeIndexToUsers < ActiveRecord::Migration[7.0]
   def change
     add_index :users, [:b, :d]
   end
@@ -645,7 +620,7 @@ For Postgres, be sure to add them concurrently.
 To mark a step in the migration as safe, despite using a method that might otherwise be dangerous, wrap it in a `safety_assured` block.
 
 ```ruby
-class MySafeMigration < ActiveRecord::Migration[6.1]
+class MySafeMigration < ActiveRecord::Migration[7.0]
   def change
     safety_assured { remove_column :users, :some_column }
   end
@@ -818,11 +793,15 @@ StrongMigrations.auto_analyze = true
 
 ## Faster Migrations
 
-Only dump the schema when adding a new migration. If you use Git, create an initializer with:
+Only dump the schema when adding a new migration. If you use Git, add to the end of your `Rakefile`:
 
-```ruby
-ActiveRecord::Base.dump_schema_after_migration = Rails.env.development? &&
-  `git status db/migrate/ --porcelain`.present?
+```rb
+task :faster_migrations do
+  ActiveRecord::Base.dump_schema_after_migration = Rails.env.development? &&
+    `git status db/migrate/ --porcelain`.present?
+end
+
+task "db:migrate": "faster_migrations"
 ```
 
 ## Schema Sanity

data/lib/strong_migrations/checker.rb

@@ -86,8 +86,7 @@ module StrongMigrations
           options ||= {}
           default = options[:default]
 
-          if !default.nil? && !((postgresql? && postgresql_version >= Gem::Version.new("11")) || (mysql? && mysql_version >= Gem::Version.new("8.0.12")) || (mariadb? && mariadb_version >= Gem::Version.new("10.3.2")))
-
+          if !default.nil? && !add_column_default_safe?
             if options[:null] == false
               options = options.except(:null)
               append = "
@@ -230,8 +229,10 @@ Then add the foreign key in separate migrations."
                 validate_code = constraint_str("ALTER TABLE %s VALIDATE CONSTRAINT %s", [table, constraint_name])
                 remove_code = constraint_str("ALTER TABLE %s DROP CONSTRAINT %s", [table, constraint_name])
 
+                constraint_methods = ar_version >= 6.1
+
                 validate_constraint_code =
-                  if ar_version >= 6.1
+                  if constraint_methods
                     String.new(command_str(:validate_check_constraint, [table, {name: constraint_name}]))
                   else
                     String.new(safety_assured_str(validate_code))
@@ -242,7 +243,7 @@ Then add the foreign key in separate migrations."
 
                   validate_constraint_code << "\n    #{command_str(:change_column_null, change_args)}"
 
-                  if ar_version >= 6.1
+                  if constraint_methods
                     validate_constraint_code << "\n    #{command_str(:remove_check_constraint, [table, {name: constraint_name}])}"
                   else
                     validate_constraint_code << "\n    #{safety_assured_str(remove_code)}"
@@ -252,7 +253,7 @@ Then add the foreign key in separate migrations."
                 return safe_change_column_null(add_code, validate_code, change_args, remove_code) if StrongMigrations.safe_by_default
 
                 add_constraint_code =
-                  if ar_version >= 6.1
+                  if constraint_methods
                     # only quote when needed
                     expr_column = column.to_s =~ /\A[a-z0-9_]+\z/ ? column : connection.quote_column_name(column)
                     command_str(:add_check_constraint, [table, "#{expr_column} IS NOT NULL", {name: constraint_name, validate: false}])
@@ -275,32 +276,14 @@ Then add the foreign key in separate migrations."
           from_table, to_table, options = args
           options ||= {}
 
-          # always validated before 5.2
-          validate = options.fetch(:validate, true) || ar_version < 5.2
+          validate = options.fetch(:validate, true)
 
           if postgresql? && validate
-            if ar_version < 5.2
-              # fk name logic from rails
-              primary_key = options[:primary_key] || "id"
-              column = options[:column] || "#{to_table.to_s.singularize}_id"
-              hashed_identifier = Digest::SHA256.hexdigest("#{from_table}_#{column}_fk").first(10)
-              fk_name = options[:name] || "fk_rails_#{hashed_identifier}"
-
-              add_code = constraint_str("ALTER TABLE %s ADD CONSTRAINT %s FOREIGN KEY (%s) REFERENCES %s (%s) NOT VALID", [from_table, fk_name, column, to_table, primary_key])
-              validate_code = constraint_str("ALTER TABLE %s VALIDATE CONSTRAINT %s", [from_table, fk_name])
-
-              return safe_add_foreign_key_code(from_table, to_table, add_code, validate_code) if StrongMigrations.safe_by_default
+            return safe_add_foreign_key(from_table, to_table, options) if StrongMigrations.safe_by_default
 
-              raise_error :add_foreign_key,
-                add_foreign_key_code: safety_assured_str(add_code),
-                validate_foreign_key_code: safety_assured_str(validate_code)
-            else
-              return safe_add_foreign_key(from_table, to_table, options) if StrongMigrations.safe_by_default
-
-              raise_error :add_foreign_key,
-                add_foreign_key_code: command_str("add_foreign_key", [from_table, to_table, options.merge(validate: false)]),
-                validate_foreign_key_code: command_str("validate_foreign_key", [from_table, to_table])
-            end
+            raise_error :add_foreign_key,
+              add_foreign_key_code: command_str("add_foreign_key", [from_table, to_table, options.merge(validate: false)]),
+              validate_foreign_key_code: command_str("validate_foreign_key", [from_table, to_table])
           end
         when :validate_foreign_key
           if postgresql? && writes_blocked?
@@ -340,11 +323,7 @@ Then add the foreign key in separate migrations."
 
       # outdated statistics + a new index can hurt performance of existing queries
       if StrongMigrations.auto_analyze && direction == :up && method == :add_index
-        if postgresql?
-          connection.execute "ANALYZE #{connection.quote_table_name(args[0].to_s)}"
-        elsif mariadb? || mysql?
-          connection.execute "ANALYZE TABLE #{connection.quote_table_name(args[0].to_s)}"
-        end
+        analyze_table(args[0])
       end
 
       result
@@ -396,8 +375,7 @@ Then add the foreign key in separate migrations."
     end
 
     def safe?
-      @safe || ENV["SAFETY_ASSURED"] || @migration.is_a?(ActiveRecord::Schema) ||
-        (direction == :down && !StrongMigrations.check_down) || version_safe?
+      @safe || ENV["SAFETY_ASSURED"] || (direction == :down && !StrongMigrations.check_down) || version_safe?
     end
 
     def version_safe?
@@ -508,6 +486,14 @@ Then add the foreign key in separate migrations."
       end
     end
 
+    def analyze_table(table)
+      if postgresql?
+        connection.execute "ANALYZE #{connection.quote_table_name(table.to_s)}"
+      elsif mariadb? || mysql?
+        connection.execute "ANALYZE TABLE #{connection.quote_table_name(table.to_s)}"
+      end
+    end
+
     def constraints(table_name)
       query = <<~SQL
         SELECT
@@ -595,5 +581,17 @@ Then add the foreign key in separate migrations."
     def new_table?(table)
       @new_tables.include?(table.to_s)
     end
+
+    def add_column_default_safe?
+      if postgresql?
+        postgresql_version >= Gem::Version.new("11")
+      elsif mysql?
+        mysql_version >= Gem::Version.new("8.0.12")
+      elsif mariadb?
+        mariadb_version >= Gem::Version.new("10.3.2")
+      else
+        false
+      end
+    end
   end
 end

data/lib/strong_migrations/database_tasks.rb

@@ -1,6 +1,7 @@
 module StrongMigrations
   module DatabaseTasks
-    def migrate
+    # Active Record 7 adds version argument
+    def migrate(*args)
       super
     rescue => e
       if e.cause.is_a?(StrongMigrations::Error)

data/lib/strong_migrations/migration.rb

@@ -7,6 +7,11 @@ module StrongMigrations
     end
 
     def method_missing(method, *args)
+      return super if is_a?(ActiveRecord::Schema)
+
+      # Active Record 7.0.2+ versioned schema
+      return super if defined?(ActiveRecord::Schema::Definition) && is_a?(ActiveRecord::Schema::Definition)
+
       strong_migrations_checker.perform(method, *args) do
         super
       end

data/lib/strong_migrations/safe_methods.rb

@@ -30,7 +30,11 @@ module StrongMigrations
                 (ActiveRecord::Base.pluralize_table_names ? reference.to_s.pluralize : reference).to_sym
               end
 
-            @migration.add_foreign_key(table, name)
+            if reference
+              @migration.add_foreign_key(table, name, column: "#{reference}_id")
+            else
+              @migration.add_foreign_key(table, name)
+            end
           end
         end
         dir.down do
@@ -52,21 +56,6 @@ module StrongMigrations
       end
     end
 
-    def safe_add_foreign_key_code(from_table, to_table, add_code, validate_code)
-      @migration.reversible do |dir|
-        dir.up do
-          @migration.safety_assured do
-            @migration.execute(add_code)
-            disable_transaction
-            @migration.execute(validate_code)
-          end
-        end
-        dir.down do
-          @migration.remove_foreign_key(from_table, to_table)
-        end
-      end
-    end
-
     def safe_add_check_constraint(table, expression, add_options, validate_options)
       @migration.reversible do |dir|
         dir.up do

data/lib/strong_migrations/version.rb

@@ -1,3 +1,3 @@
 module StrongMigrations
-  VERSION = "0.7.6"
+  VERSION = "0.8.0"
 end

metadata

@@ -1,7 +1,7 @@
 --- !ruby/object:Gem::Specification
 name: strong_migrations
 version: !ruby/object:Gem::Version
-  version: 0.7.6
+  version: 0.8.0
 platform: ruby
 authors:
 - Andrew Kane
@@ -10,7 +10,7 @@ authors:
 autorequire:
 bindir: bin
 cert_chain: []
-date: 2021-01-17 00:00:00.000000000 Z
+date: 2022-02-10 00:00:00.000000000 Z
 dependencies:
 - !ruby/object:Gem::Dependency
   name: activerecord
@@ -18,87 +18,17 @@ dependencies:
     requirements:
     - - ">="
       - !ruby/object:Gem::Version
-        version: '5'
+        version: '5.2'
   type: :runtime
   prerelease: false
   version_requirements: !ruby/object:Gem::Requirement
     requirements:
     - - ">="
       - !ruby/object:Gem::Version
-        version: '5'
-- !ruby/object:Gem::Dependency
-  name: bundler
-  requirement: !ruby/object:Gem::Requirement
-    requirements:
-    - - ">="
-      - !ruby/object:Gem::Version
-        version: '0'
-  type: :development
-  prerelease: false
-  version_requirements: !ruby/object:Gem::Requirement
-    requirements:
-    - - ">="
-      - !ruby/object:Gem::Version
-        version: '0'
-- !ruby/object:Gem::Dependency
-  name: rake
-  requirement: !ruby/object:Gem::Requirement
-    requirements:
-    - - ">="
-      - !ruby/object:Gem::Version
-        version: '0'
-  type: :development
-  prerelease: false
-  version_requirements: !ruby/object:Gem::Requirement
-    requirements:
-    - - ">="
-      - !ruby/object:Gem::Version
-        version: '0'
-- !ruby/object:Gem::Dependency
-  name: minitest
-  requirement: !ruby/object:Gem::Requirement
-    requirements:
-    - - ">="
-      - !ruby/object:Gem::Version
-        version: '0'
-  type: :development
-  prerelease: false
-  version_requirements: !ruby/object:Gem::Requirement
-    requirements:
-    - - ">="
-      - !ruby/object:Gem::Version
-        version: '0'
-- !ruby/object:Gem::Dependency
-  name: pg
-  requirement: !ruby/object:Gem::Requirement
-    requirements:
-    - - ">="
-      - !ruby/object:Gem::Version
-        version: '0'
-  type: :development
-  prerelease: false
-  version_requirements: !ruby/object:Gem::Requirement
-    requirements:
-    - - ">="
-      - !ruby/object:Gem::Version
-        version: '0'
-- !ruby/object:Gem::Dependency
-  name: mysql2
-  requirement: !ruby/object:Gem::Requirement
-    requirements:
-    - - ">="
-      - !ruby/object:Gem::Version
-        version: '0'
-  type: :development
-  prerelease: false
-  version_requirements: !ruby/object:Gem::Requirement
-    requirements:
-    - - ">="
-      - !ruby/object:Gem::Version
-        version: '0'
+        version: '5.2'
 description:
 email:
-- andrew@chartkick.com
+- andrew@ankane.org
 - bob.remeika@gmail.com
 executables: []
 extensions: []
@@ -131,14 +61,14 @@ required_ruby_version: !ruby/object:Gem::Requirement
   requirements:
   - - ">="
     - !ruby/object:Gem::Version
-      version: '2.4'
+      version: '2.6'
 required_rubygems_version: !ruby/object:Gem::Requirement
   requirements:
   - - ">="
     - !ruby/object:Gem::Version
       version: '0'
 requirements: []
-rubygems_version: 3.2.3
+rubygems_version: 3.3.3
 signing_key:
 specification_version: 4
 summary: Catch unsafe migrations in development