flipper-notifications 0.1.10 → 0.1.11

checksums.yaml

@@ -1,7 +1,7 @@
 ---
 SHA256:
-  metadata.gz: 5f6ffe2530157b223628713342f83960c5a89dc2a8fca928df146c9553552279
-  data.tar.gz: c4fba936bef2a2629c6171bfd2418a08c7b8b379b12b87cbcc97808f0b8a4815
+  metadata.gz: b89e1c2fa5d254aebc89291bb50eec14b5687d9ea95f17f061e8f4972cc452f8
+  data.tar.gz: 870159e8ebf702200423b873448e8ac63140322fb4dbe6f811c746805ecdbf5b
 SHA512:
-  metadata.gz: c576ff049c4ff0000dc628793e293a83e6a8814d0d73278bb62094207133c64860f0dc43028a800fd6e2b0072ff86a7bf01a790b20b70db5055eda9e73ca4ec9
-  data.tar.gz: 54d2344c796fbafa721d18e55cfc68d46bd703df8a7b06bb9e5ef38b27171c144fb9757492ce26428937febaa6bdeeae2c24abdb07aa4243db7866153ad8cc55
+  metadata.gz: 63da6fdb0abb5067d5f1c6dd09e7103c1172fa3e294fb9e30817205ba75986c07c3f4aa9ba84328ac41790306e41d256657fdca09a7751a7135faad149d6ebf4
+  data.tar.gz: cf2ead088adc75c0aa2fb4c8c82b818264c89bd9bdd7d551a22dc16acb7808136b3a268f680e72b72069143d62172a0e3df5c3b7f5c3f4823c4263c9b2aba8df

data/Gemfile.lock

@@ -1,7 +1,7 @@
 PATH
   remote: .
   specs:
-    flipper-notifications (0.1.10)
+    flipper-notifications (0.1.11)
       activesupport (>= 7, < 8.2)
       flipper (>= 0.24, < 2.0)
       httparty (~> 0.17)
@@ -104,6 +104,7 @@ PLATFORMS
   arm64-darwin-21
   arm64-darwin-23
   arm64-darwin-24
+  arm64-darwin-25
   x86_64-linux
 
 DEPENDENCIES

data/README.md

@@ -53,6 +53,34 @@ Flipper::Notifications.configure do |config|
 end
 ```
 
+### Stale State with Cached Adapters
+
+Notifications are rendered inside a background job (`WebhookNotificationJob`),
+which may run in a **different process** from the one that changed the feature.
+The message ("The feature is now fully enabled/disabled", the list of groups,
+actors, and percentages) is built by reading the feature's current state at
+job-run time.
+
+If your Flipper adapter is fronted by a **per-process cache** — for example an
+in-memory `ActiveSupportCacheStore` layer — the process running the job can hold
+a stale value: enabling a feature in your web process does not invalidate a
+worker's in-memory cache. The notification then reports the wrong state.
+
+By default state is read through the global `Flipper`. Point `config.flipper` at
+a cache-free instance backed by your source of truth so notifications always
+render the real value:
+
+```ruby
+# config/initializers/flipper.rb
+
+Flipper::Notifications.configure do |config|
+  config.flipper = Flipper.new(Flipper::Adapters::ActiveRecord.new)
+end
+```
+
+This only affects how notifications **read** state; your application keeps using
+its cached `Flipper` everywhere else.
+
 ### Slack invalid_blocks Errors
 
 Slack limits the size of webhook messages.  The Slack API returns a 400 status

data/lib/flipper/notifications/configuration.rb

@@ -8,14 +8,31 @@ module Flipper
         @enabled   = false
         @notifiers = []
         @webhook_character_limit = nil
+        @flipper = nil
       end
 
       attr_accessor :enabled, :notifiers, :webhook_character_limit
+      attr_writer :flipper
 
       def enabled?
         @enabled
       end
 
+      # The Flipper instance used to READ feature state when rendering a
+      # notification. Defaults to the global `Flipper`.
+      #
+      # Notifications are rendered in a background job, which may run in a
+      # different process from the one that changed the feature. If your Flipper
+      # adapter is fronted by a per-process cache (e.g. an in-memory
+      # ActiveSupportCacheStore), the reading process can hold a stale value and
+      # the message reports the wrong state. Point this at a cache-free instance
+      # backed by your source of truth to always render the real value, e.g.:
+      #
+      #   config.flipper = Flipper.new(Flipper::Adapters::ActiveRecord.new)
+      def flipper
+        @flipper || Flipper
+      end
+
     end
   end
 end

data/lib/flipper/notifications/feature_event.rb

@@ -20,7 +20,7 @@ module Flipper
       end
 
       def initialize(feature_name:, operation:)
-        @feature   = Flipper.feature(feature_name)
+        @feature   = Flipper::Notifications.configuration.flipper.feature(feature_name)
         @operation = operation.to_s
       end
 

data/lib/flipper/notifications/version.rb

@@ -2,6 +2,6 @@
 
 module Flipper
   module Notifications
-    VERSION = "0.1.10"
+    VERSION = "0.1.11"
   end
 end

metadata

@@ -1,14 +1,14 @@
 --- !ruby/object:Gem::Specification
 name: flipper-notifications
 version: !ruby/object:Gem::Version
-  version: 0.1.10
+  version: 0.1.11
 platform: ruby
 authors:
 - Joel Lubrano
 autorequire:
 bindir: bin
 cert_chain: []
-date: 2026-06-10 00:00:00.000000000 Z
+date: 2026-07-30 00:00:00.000000000 Z
 dependencies:
 - !ruby/object:Gem::Dependency
   name: activesupport
@@ -256,7 +256,7 @@ required_rubygems_version: !ruby/object:Gem::Requirement
     - !ruby/object:Gem::Version
       version: '0'
 requirements: []
-rubygems_version: 3.5.9
+rubygems_version: 3.4.10
 signing_key:
 specification_version: 4
 summary: Rails-compatible Slack notifications for Flipper feature flags