omen 0.2.1 → 0.2.2

checksums.yaml

@@ -1,7 +1,7 @@
 ---
 SHA256:
-  metadata.gz: c5ce1b7049f103291d3d3aabb7d02bb80271bb7dca022bb1250db4855b59a4e9
-  data.tar.gz: e323629870bf6d657fa4f43b0c47018eeed8af9946733f962d0e51889297ddcf
+  metadata.gz: 7bff8c4c873f1cbc8923e3dbc7cebe42e282126624a56cab8d2461b8c879fb0d
+  data.tar.gz: e8bd747cf8234259e52e7bf5d1ab24e607dc5ba6ba09deef01f037692bd3a6f7
 SHA512:
-  metadata.gz: ff778fcc7568f43a7b0252793443c18ab0aee925c9030dcdef9af262934eb62bfb3a9e34af21c0cb7a4f6d096cdde812fd216fc4c64008095443f44ffea3ab70
-  data.tar.gz: 1aea2af528735383465416dd6dcbd24770b983e630934e4ecf170e36d90120e9fbbf21e85efbd25eb6aa59860ba3c753cb66c97983f61ca5ea9785041a72d3e3
+  metadata.gz: 1c82de79367f41a2712f44bdf21d6ca715c263fbc097dae9d7dcd032ba28a152ebf4c1976b02b37f62992781f98981fab99fd49173a4925bea3664ba668cbff1
+  data.tar.gz: 0a2a09480ee44f60283db5db8976d6c97d6373fca2af7f6e1b2526de51052e5aba96b171ba989af70ef7bf5e9acd1fb01bbd6933cb9ec1b6cf00a10be80f0a8e

data/CHANGELOG.md

@@ -7,6 +7,14 @@ For more information about changelogs, check [Keep a Changelog](http://keepachan
 
 ## [Unreleased]
 
+## 0.2.2 - 2026-08-24
+
+* [Fix] Run a load hook as each model loads, so a host declares `broadcasts_refreshes` and the
+  rest through `ActiveSupport.on_load :omen_reading` rather than by naming the class while
+  initializers run, which loaded Active Record before Rails was up
+* [Fix] Read the adapter through the `:active_record` load hook, so a boot that never touches
+  the database is not the boot that loads it early
+
 ## 0.2.1 - 2026-08-24
 
 * [Fix] Declare `eastern()` over an instant as well as a stored timestamp, so a reply that

data/README.md

@@ -119,7 +119,7 @@ Two things a subclass cannot reach, because the gem's own class is what a job lo
 line in the host does it:
 
 ```ruby
-Rails.application.config.to_prepare { Omen::Reading.broadcasts_refreshes }
+ActiveSupport.on_load(:omen_reading) { broadcasts_refreshes }
 ```
 
 ## After the first deploy

data/app/models/omen/answer.rb

@@ -35,3 +35,5 @@ class Omen::Answer < Omen.config.record
   # @return [Boolean] whether the answer ran past what is shown.
   def truncated? = result.size > Omen.config.maximum_rows
 end
+
+ActiveSupport.run_load_hooks :omen_answer, Omen::Answer

data/app/models/omen/question.rb

@@ -11,3 +11,5 @@ class Omen::Question < Omen.config.record
   # @return [String] the side of the conversation this was said on, in the words the API uses.
   def role = 'user'
 end
+
+ActiveSupport.run_load_hooks :omen_question, Omen::Question

data/app/models/omen/reading.rb

@@ -16,3 +16,5 @@ class Omen::Reading < Omen.config.record
   # @return [String] the default representation (used in views).
   def to_s = questions.first&.text.to_s.truncate 80
 end
+
+ActiveSupport.run_load_hooks :omen_reading, Omen::Reading

data/lib/omen/engine.rb

@@ -7,10 +7,12 @@ module Omen
     # initializer has already said where its schema is. The declared format rather than the
     # applied one, so nothing here depends on which after_initialize hook ran first.
     config.after_initialize do
-      configured = ActiveRecord::Base.configurations.configs_for env_name: Rails.env,
-        name: 'primary'
-      Omen::Requirements.met adapter: configured&.adapter, schema: Omen.config.schema,
-        schema_format: Rails.application.config.active_record.schema_format
+      ActiveSupport.on_load :active_record do
+        configured = ActiveRecord::Base.configurations.configs_for env_name: Rails.env,
+          name: 'primary'
+        Omen::Requirements.met adapter: configured&.adapter, schema: Omen.config.schema,
+          schema_format: Rails.application.config.active_record.schema_format
+      end
     end
   end
 end

data/lib/omen/version.rb

@@ -1,4 +1,4 @@
 module Omen
   # The version of this gem, as RubyGems knows it.
-  VERSION = '0.2.1'
+  VERSION = '0.2.2'
 end

metadata

@@ -1,7 +1,7 @@
 --- !ruby/object:Gem::Specification
 name: omen
 version: !ruby/object:Gem::Version
-  version: 0.2.1
+  version: 0.2.2
 platform: ruby
 authors:
 - Claudio Baccigalupo