v1.2.0

CHANGELOG.md

@@ -2,6 +2,14 @@
 
 ## 1.1.x
 
+### 1.2.0
+
+- support rails 7.2 ([#126](https://github.com/jenseng/hair_trigger/pull/126))
+- add support for litedb adapter ([#120](https://github.com/jenseng/hair_trigger/pull/120))
+- add support for mysql2rgeo adapter ([#121](https://github.com/jenseng/hair_trigger/pull/121))
+- support referencing old and new tables ([#125](https://github.com/jenseng/hair_trigger/pull/125))
+- testing fixes, minor refactors (([#124](https://github.com/jenseng/hair_trigger/pull/124)), ([#127](https://github.com/jenseng/hair_trigger/pull/127)))
+
 ### 1.1.0
 
 - fix for rails 7+ compatibility ([#118](https://github.com/jenseng/hair_trigger/pull/118))

README.md

@@ -126,7 +126,7 @@ end
 ```
 
 #### new_as(name) or old_as(name)
-PostgreSQL-specific option for accessing in the after trigger the table as it was before the operation (old) or as it is after the operation (new). This is useful in statement trigger when you want to compare the old and new values of all rows changed during an update trigger. For example:
+PostgreSQL-specific option for "after" triggers to allow accessing the row as it was before the operation (`old`) or as it is after the operation (`new`). This is useful in statement trigger when you want to compare the old and new values of all rows changed during an update trigger. For example:
 
 ```ruby
 trigger.after(:update).for_each(:statement).new_as(:new_users).old_as(:old_users) do

lib/hair_trigger/version.rb

@@ -1,5 +1,5 @@
 module HairTrigger
-  VERSION = "1.1.1"
+  VERSION = "1.2.0"
 
   def VERSION.<=>(other)
     split(/\./).map(&:to_i) <=> other.split(/\./).map(&:to_i)