strong_migrations 2.7.0 → 2.8.0

checksums.yaml

@@ -1,7 +1,7 @@
 ---
 SHA256:
-  metadata.gz: 250e255ba679a0e581fb86ed13b2824cf5749b7dc3ac5bf0a26bfffebe314fb8
-  data.tar.gz: d91882cb145d2f59a688e41e0d20301c6ca41d3e5e9790be9996eb256cc26dd2
+  metadata.gz: 506dc7670dbae5a7f4bb621d39da43e67098b9629cc76a854d2677d006f0919a
+  data.tar.gz: 3cfd8d8f74a1575b23485ca16ef26f04de5f52b8c059fcded94d1a42410afc41
 SHA512:
-  metadata.gz: b0bba6d87fd23e3bf68d8a8274cc6d22346a73f0001e8078f99f3c7a039772e39ded14138a2ad87eb7476f855a56647a1e07f84e7dadc96d5f3df53aebd27c9a
-  data.tar.gz: b985a53c42f12ec3268f6fd2570bdb2cdf777f80217b17a68872e86d4366b5939a702c0b8551b0ddab4f44ddfb9ef5da8a3f74ca97365124a086d46c2fe66f10
+  metadata.gz: 0b55091991fdba05bbc088a3b8967a66473e150ccce62f2065d671fa1b61f2dc70b0cd149f5a9645135b9fdcc9e10f344b7ea548e391ab9bcca371bdff35443c
+  data.tar.gz: '09a1b778c608aa600a3e84ca99da6fb8ad5771cec839092b2f77e0788e6dc6a0940442665de94ec5ea07487fcdb7b665bc41a258c44266f79f322616336986e9'

data/CHANGELOG.md

@@ -1,3 +1,7 @@
+## 2.8.0 (2026-05-14)
+
+- Added check for `rename_enum_value`
+
 ## 2.7.0 (2026-04-25)
 
 - Added check for `add_foreign_key` with MySQL and MariaDB

data/README.md

@@ -80,6 +80,7 @@ Postgres-specific checks:
 - [adding a json column](#adding-a-json-column)
 - [adding a column with a volatile default value](#adding-a-column-with-a-volatile-default-value)
 - [setting NOT NULL on an existing column](#setting-not-null-on-an-existing-column)
+- [renaming an enum value](#renaming-an-enum-value)
 - [renaming a schema](#renaming-a-schema)
 
 MySQL and MariaDB-specific checks:
@@ -686,6 +687,38 @@ class ValidateSomeColumnNotNull < ActiveRecord::Migration[8.1]
 end
 ```
 
+### Renaming an enum value
+
+#### Bad
+
+Renaming an enum value that’s in use will cause errors in your application.
+
+```ruby
+class RenameDoneToCompleted < ActiveRecord::Migration[8.1]
+  def change
+    rename_enum_value :status, from: "done", to: "completed"
+  end
+end
+```
+
+#### Good
+
+A safer approach is to:
+
+1. Add a new enum value before or after the old value
+2. Update application code to handle both values and write the new value
+3. Backfill data from the old value to the new value
+
+```ruby
+class AddCompletedToStatus < ActiveRecord::Migration[8.1]
+  def up
+    add_enum_value :status, "completed", after: "done"
+  end
+end
+```
+
+Removing enum values is not supported in Postgres (without creating a new enum).
+
 ### Renaming a schema
 
 #### Bad

data/lib/strong_migrations/checker.rb

@@ -79,6 +79,8 @@ module StrongMigrations
           check_remove_index(*args)
         when :rename_column
           check_rename_column
+        when :rename_enum_value
+          check_rename_enum_value(*args)
         when :rename_schema
           check_rename_schema
         when :rename_table

data/lib/strong_migrations/checks.rb

@@ -467,6 +467,14 @@ module StrongMigrations
       raise_error :rename_column
     end
 
+    def check_rename_enum_value(*args)
+      options = args.extract_options!
+      type_name, _ = args
+
+      raise_error :rename_enum_value,
+        command: command_str("add_enum_value", [type_name, options[:to], {after: options[:from]}])
+    end
+
     def check_rename_schema
       raise_error :rename_schema
     end

data/lib/strong_migrations/error_messages.rb

@@ -117,6 +117,20 @@ in your application. A safer approach is to:
 5. Stop writing to the old column
 6. Drop the old column",
 
+    rename_enum_value:
+"Renaming an enum value that's in use will cause errors
+in your application. A safer approach is to:
+
+1. Add a new enum value before or after the old value
+2. Update application code to handle both values and write the new value
+3. Backfill data from the old value to the new value
+
+class %{migration_name} < ActiveRecord::Migration%{migration_suffix}
+  def up
+    %{command}
+  end
+end",
+
     rename_schema:
 "Renaming a schema that's in use will cause errors
 in your application. A safer approach is to:

data/lib/strong_migrations/version.rb

@@ -1,3 +1,3 @@
 module StrongMigrations
-  VERSION = "2.7.0"
+  VERSION = "2.8.0"
 end

metadata

@@ -1,7 +1,7 @@
 --- !ruby/object:Gem::Specification
 name: strong_migrations
 version: !ruby/object:Gem::Version
-  version: 2.7.0
+  version: 2.8.0
 platform: ruby
 authors:
 - Andrew Kane
@@ -72,7 +72,7 @@ required_rubygems_version: !ruby/object:Gem::Requirement
     - !ruby/object:Gem::Version
       version: '0'
 requirements: []
-rubygems_version: 4.0.6
+rubygems_version: 4.0.10
 specification_version: 4
 summary: Catch unsafe migrations in development
 test_files: []