flow_chat 0.10.0 → 0.10.1

checksums.yaml

@@ -1,7 +1,7 @@
 ---
 SHA256:
-  metadata.gz: a748d7d7a637ca0dc2e0f7c5d8dde213df8fd46eec9117417f141ed6d8aff91d
-  data.tar.gz: ae52d99625691a839cda0e6884ab065bfc5851aa427ceafc4c19ded649c13da7
+  metadata.gz: 6ae06aa071a9ac6f07a9b2555e4e35dcaf98512962625b45426865484d989f7c
+  data.tar.gz: 583ef52a86cd6462dd3d0bb5e6b1cf76267ea3bbfcd0d9b33b2d7ceffa065e9e
 SHA512:
-  metadata.gz: 05e3a2dc63c3c678f0da32f180121caece864af244181f1deb1b668118244e4c342e5656aac7533b79eb3d6f0b3f9f87c62c0ca9faa14243cf9c1ab04c06bea6
-  data.tar.gz: 804ca337d0842bd077f2f2fbde1c864d993ba22d87915e92d869103b8d9adb8ff898cd598dc476bff7625772151be8f49e3853ec93d010cb646e19d9b54e8a06
+  metadata.gz: 22a819e0db8e6784933ff311b48aa3d9f62eb38aa456df985ee2b4d5c7d8fb683bc866efebe3643294b3ef49c1f5b041b1c6bd77a514e2f9dd63d913cc4e8a3a
+  data.tar.gz: bc2057d4d6aed38010c635fa56d91f756d5ecbbfc527d5b21ff2c4d04457b5672367321d00499d8e7a37c374352891ce15c14210c94738ef52114ff2676fdb1d

data/.github/workflows/ci.yml

@@ -28,6 +28,35 @@ jobs:
     - name: Build gem
       run: bundle exec gem build *.gemspec
 
+  # Watches unreleased Rails, because flow_chat's activesupport and actionpack
+  # dependencies are deliberately unbounded above (see flow_chat.gemspec).
+  #
+  # Allowed to fail. A red run here means Rails main changed something this gem
+  # relies on, and is a prompt to look rather than a broken build - the point is
+  # to find out while the change is still unreleased, instead of from a bug
+  # report the week the major ships.
+  rails-main:
+    runs-on: ubuntu-latest
+    continue-on-error: true
+    env:
+      BUNDLE_GEMFILE: gemfiles/rails_main.gemfile
+
+    steps:
+    - uses: actions/checkout@v4
+
+    # Newest stable, deliberately ahead of the matrix above. Rails main already
+    # requires Ruby >= 3.3 (via ractor-dispatch) and that floor keeps rising, so
+    # pinning this job to the minimum would fail it for a Ruby version rather
+    # than for the API change it exists to catch.
+    - name: Set up Ruby
+      uses: ruby/setup-ruby@v1
+      with:
+        ruby-version: '3.4'
+        bundler-cache: true
+
+    - name: Run tests against rails main
+      run: bundle exec rake test
+
   lint:
     runs-on: ubuntu-latest
     steps:

data/.gitignore

@@ -12,4 +12,7 @@
 
 # Ignore Gemfile.lock for our gem
 /Gemfile.lock
-.DS_Store
+.DS_Store
+# Resolved fresh on every CI run, so the rails-main job sees the latest main
+# rather than a pinned revision.
+gemfiles/*.lock

data/CHANGELOG.md

@@ -2,8 +2,30 @@
 
 All notable changes to this project will be documented in this file.
 
+## [0.10.1] - 2026-08-17
+
+### Bug Fixes
+
+- Publish side events when no foreground pass ran
+
+### Documentation
+
+- Record #9 in the 0.10.0 release notes
+
+### Miscellaneous Tasks
+
+- State the Ruby floor, and watch unreleased Rails instead of capping ([#10](https://github.com/radioactive-labs/flow_chat/issues/10))
+- Prepend the changelog instead of regenerating it
+
 ## [0.10.0] - 2026-08-17
 
+> **Note.** [#9](https://github.com/radioactive-labs/flow_chat/pull/9) was squash-merged with a non-conventional title, so git-cliff did not pick it up when this section was generated. It is the largest change in the release and is listed by hand below. Releases now prepend rather than regenerate, so this survives.
+
+### Behaviour changes
+
+- **Intercom resolves numbers only.** The renderer already prints a number beside every option and asks for one; matching typed labels as well is what allowed two options reading the same to collapse onto a single mapping entry. Typing the words now falls through to the flow's own validation.
+- **HTTP matches replies exactly**, with no case or whitespace folding. A web client echoes back the string it was handed, so nothing drifts in transit. A client that lowercases its reply will stop resolving.
+
 ### Bug Fixes
 
 - Correct runtime-breaking session and API misuse
@@ -18,6 +40,7 @@ All notable changes to this project will be documented in this file.
 
 ### Features
 
+- Add Facebook Messenger and Instagram DM gateways, unify choice resolution, and fix delivery instrumentation ([#9](https://github.com/radioactive-labs/flow_chat/pull/9))
 - Map choices on Intercom and HTTP ([#4](https://github.com/radioactive-labs/flow_chat/issues/4))
 - Let a flow declare that it consumed the turn ([#6](https://github.com/radioactive-labs/flow_chat/issues/6))
 - Report a reply the platform would not take ([#7](https://github.com/radioactive-labs/flow_chat/issues/7))

data/flow_chat.gemspec

@@ -14,7 +14,11 @@ Gem::Specification.new do |spec|
   DESC
   spec.homepage = "https://github.com/radioactive-labs/flow_chat"
   spec.license = "MIT"
-  spec.required_ruby_version = Gem::Requirement.new(">= 2.3.0")
+  # Matches the versions CI actually exercises. The previous ">= 2.3.0" was
+  # three Rubies out of date and promised a floor nothing here could honour:
+  # activesupport 8 requires Ruby 3.2, so a 2.x user hit an unexplained
+  # resolution failure rather than a clear statement of what this gem needs.
+  spec.required_ruby_version = Gem::Requirement.new(">= 3.0")
 
   spec.metadata["allowed_push_host"] = "https://rubygems.org"
   spec.metadata["rubygems_mfa_required"] = "true"
@@ -32,9 +36,25 @@ Gem::Specification.new do |spec|
   spec.executables = spec.files.grep(%r{^exe/}) { |f| File.basename(f) }
   spec.require_paths = ["lib"]
 
-  spec.add_dependency "zeitwerk"
+  # Deliberately unbounded above, and RubyGems' warning about that is
+  # overridden knowingly rather than overlooked.
+  #
+  # A "< N" cap does not protect this gem from the next major - it decides
+  # where the breakage surfaces. Capping blocks every downstream application on
+  # the day that major ships, until this gem cuts a release, which is a cost
+  # paid by everyone for a break that may never come.
+  #
+  # Leaving it open moves the risk from install time to runtime, and the CI job
+  # against rails main is what pays for that: an incompatible change is found
+  # while it is still unreleased, rather than in a bug report the week it lands.
+  # If that job is ever removed, these bounds should be revisited.
+  #
+  # No floor is needed beyond ">= 6" either. Bundler resolves an activesupport
+  # that suits the running Ruby, so a Ruby 3.0 application lands on Rails 7.x
+  # without this gem having to say so.
   spec.add_dependency "activesupport", ">= 6"
   spec.add_dependency "actionpack", ">= 6"
+  spec.add_dependency "zeitwerk"
   spec.add_dependency "phonelib"
   spec.add_dependency "ibsciss-middleware", "~> 0.4.2"
   spec.add_dependency "intercom", "~> 4.2"

data/gemfiles/rails_main.gemfile

@@ -0,0 +1,18 @@
+# Resolves against unreleased Rails, for the CI job that watches for breaking
+# changes before they ship.
+#
+# This exists because flow_chat's activesupport and actionpack dependencies are
+# deliberately unbounded above (see flow_chat.gemspec). Without an upper bound,
+# an incompatible major would otherwise be discovered by an application that
+# upgraded, rather than here. The job is allowed to fail: a red run is a signal
+# to look, not a broken build.
+#
+# The root Gemfile is evaluated rather than restated, so this file carries the
+# development dependencies too - rake, minitest, standard and the rest. Listing
+# only the gemspec here left the suite unable to load its own Rakefile, which
+# failed the job for a reason that had nothing to do with Rails.
+eval_gemfile File.expand_path("../Gemfile", __dir__)
+
+# Overrides the activesupport/actionpack the gemspec resolved, which is the
+# whole point of this file.
+gem "rails", github: "rails/rails", branch: "main"

data/lib/flow_chat/async_job.rb

@@ -70,9 +70,19 @@ module FlowChat
     def initialize(request_data)
       FlowChat.logger.debug { "BackgroundController: Initializing with request data" }
       @request = BackgroundRequest.new(request_data)
+      @side_events_published = request_data[:side_events_published] || false
       @response = nil
     end
 
+    # Whether the pass that enqueued this job already announced the delivery's
+    # side events. Only the gem sets it, when it enqueues a job of its own.
+    # An application that builds a request context by hand and enqueues
+    # directly has no earlier pass behind it, so the answer is false and the
+    # job is the one that announces them.
+    def side_events_published?
+      @side_events_published
+    end
+
     # Delegate params to request (mimics Rails controller behavior)
     def params
       request.params

data/lib/flow_chat/gateway_async_support.rb

@@ -17,6 +17,18 @@ module FlowChat
       @controller.is_a?(::FlowChat::BackgroundController)
     end
 
+    # Whether an earlier pass already announced this delivery's side events,
+    # which is the case only for a job the gem enqueued after publishing them
+    # itself. Being in the background is not enough on its own: an application
+    # may build a request context and enqueue a job with no foreground pass
+    # ahead of it, and then this pass is the first to see the delivery.
+    #
+    # in_background? short-circuits because a foreground controller is a Rails
+    # controller, which knows nothing about side events.
+    def side_events_already_published?
+      in_background? && @controller.side_events_published?
+    end
+
     # Check if async processing should be used
     # Returns true if:
     # - Not already in background mode
@@ -40,6 +52,11 @@ module FlowChat
       FlowChat.logger.info { "#{self.class.name}: Async enabled - enqueuing background job" }
 
       # Serialize request data for BackgroundController
+      #
+      # side_events_published records that this pass has already announced the
+      # delivery's side events, so the job it is about to enqueue does not
+      # announce them a second time. It rides in the request context rather
+      # than in params, where a platform's own webhook fields live.
       request_data = {
         params: @controller.request.params.to_h,
         method: @controller.request.method,
@@ -47,7 +64,8 @@ module FlowChat
         host: extract_host(@controller.request),
         path: extract_path(@controller.request),
         body: extract_body_for_background(@controller.request),
-        remote_ip: extract_remote_ip(@controller.request)
+        remote_ip: extract_remote_ip(@controller.request),
+        side_events_published: true
       }
 
       # Enqueue user's job with request context and job params

data/lib/flow_chat/meta/messaging_gateway.rb

@@ -111,20 +111,23 @@ module FlowChat
         flow_ran = false
 
         entries.each do |entry|
-          # Published in the foreground only, and always - whether this turn
-          # goes on to run a flow inline or hand one to a background job.
+          # Published by whichever pass is first to see this delivery, and
+          # only once.
           #
-          # With async enabled the job re-enters this method on the same body,
-          # so publishing here as well as there announced every receipt, echo
-          # and standby event twice: once by the request, once by the job.
-          # Skipping them in the background leaves exactly one publisher, and
-          # leaves it the one that is already holding the delivery - so a
-          # receipt is announced when it arrives rather than whenever the queue
-          # gets to it, and survives a job that is never picked up.
+          # With async enabled the gem publishes here, enqueues, and the job
+          # re-enters this method on the same body, so publishing in both
+          # announced every receipt, echo and standby event twice. The job the
+          # gem enqueues therefore carries word that they are already out, and
+          # skips them. The request is the better publisher of the two: it
+          # already holds the delivery, so a receipt is announced when it
+          # arrives rather than whenever the queue gets to it, and survives a
+          # job that is never picked up.
           #
-          # Nothing changes for an app that does not use async: it never runs
-          # in the background, so it takes this branch every time.
-          publish_side_events(entry) unless in_background?
+          # A background pass with nothing behind it publishes. An application
+          # is free to build its own request context and enqueue a job itself,
+          # which is what fanning one shared webhook out to several accounts
+          # takes, and no foreground pass ever runs for those.
+          publish_side_events(entry) unless side_events_already_published?
 
           events = entry["messaging"]
           next unless events.is_a?(Array)

data/lib/flow_chat/version.rb

@@ -1,3 +1,3 @@
 module FlowChat
-  VERSION = "0.10.0"
+  VERSION = "0.10.1"
 end

data/lib/flow_chat/whatsapp/gateway/cloud_api.rb

@@ -147,13 +147,18 @@ module FlowChat
                 # slot is claimed, or a status arriving ahead of a message in the
                 # same delivery would spend the slot and drop the message.
                 #
-                # Foreground only. With async enabled the job re-enters this
-                # method on the same body, so publishing in both announced every
-                # status twice and delivery receipts double-counted. The request
-                # publishes them: it already holds the delivery, so a receipt is
-                # announced when it arrives rather than when the queue reaches
-                # it, and survives a job that is never picked up.
-                handle_statuses(value) if value["statuses"].present? && !in_background?
+                # Announced by whichever pass is first to see the delivery, and
+                # only once. With async enabled the gem publishes here, enqueues,
+                # and the job re-enters this method on the same body, so
+                # publishing in both double-counted every receipt. The job the
+                # gem enqueues carries word that they are already out and skips
+                # them, which leaves the request publishing: it already holds
+                # the delivery, so a receipt is announced when it arrives rather
+                # than when the queue reaches it, and survives a job that is
+                # never picked up. A background pass with no foreground pass
+                # behind it, as an application enqueuing its own jobs has,
+                # publishes them itself.
+                handle_statuses(value) if value["statuses"].present? && !side_events_already_published?
 
                 next if value["messages"].blank?
 
@@ -171,13 +176,13 @@ module FlowChat
               when "statuses"
                 # Only reachable for a payload built without a field name, which
                 # our own fixtures do and Meta does not.
-                handle_statuses(value) unless in_background?
+                handle_statuses(value) unless side_events_already_published?
               else
                 # Anything that is not a message or its delivery. Coexistence
                 # echoes, contact syncs, imported history, account bans, template
                 # approvals: all of it is the application's domain, so it is
                 # published rather than interpreted here.
-                handle_unmodelled_field(change["field"], value, entry["id"]) unless in_background?
+                handle_unmodelled_field(change["field"], value, entry["id"]) unless side_events_already_published?
               end
             end
           end

data/lib/tasks/release.rake

@@ -94,8 +94,18 @@ namespace :release do
     end
 
     # Changelog — same config CI uses for release notes, so they agree.
+    #
+    # Prepends the new section rather than regenerating the file. `-o` rewrote
+    # CHANGELOG.md from the commit history every time, so anything hand-written
+    # was silently discarded at the next release. That is not hypothetical: #9
+    # was squash-merged with a non-conventional title, git-cliff could not
+    # categorise it, and the largest change in v0.10.0 had to be written in by
+    # hand — which `-o` would have erased.
+    #
+    # --unreleased limits the run to commits since the last tag, so only the
+    # section being cut is generated and everything below it is left alone.
     abort "git-cliff not found. Install with: brew install git-cliff" unless git_cliff?
-    system("git-cliff", "--config", RELEASE_CLIFF_CONFIG, "--tag", "v#{version}", "-o", "CHANGELOG.md") ||
+    system("git-cliff", "--config", RELEASE_CLIFF_CONFIG, "--tag", "v#{version}", "--unreleased", "--prepend", "CHANGELOG.md") ||
       abort("Changelog generation failed")
     puts "✓ CHANGELOG.md"
 

metadata

@@ -1,7 +1,7 @@
 --- !ruby/object:Gem::Specification
 name: flow_chat
 version: !ruby/object:Gem::Version
-  version: 0.10.0
+  version: 0.10.1
 platform: ruby
 authors:
 - Stefan Froelich
@@ -11,21 +11,21 @@ cert_chain: []
 date: 2026-08-17 00:00:00.000000000 Z
 dependencies:
 - !ruby/object:Gem::Dependency
-  name: zeitwerk
+  name: activesupport
   requirement: !ruby/object:Gem::Requirement
     requirements:
     - - ">="
       - !ruby/object:Gem::Version
-        version: '0'
+        version: '6'
   type: :runtime
   prerelease: false
   version_requirements: !ruby/object:Gem::Requirement
     requirements:
     - - ">="
       - !ruby/object:Gem::Version
-        version: '0'
+        version: '6'
 - !ruby/object:Gem::Dependency
-  name: activesupport
+  name: actionpack
   requirement: !ruby/object:Gem::Requirement
     requirements:
     - - ">="
@@ -39,19 +39,19 @@ dependencies:
       - !ruby/object:Gem::Version
         version: '6'
 - !ruby/object:Gem::Dependency
-  name: actionpack
+  name: zeitwerk
   requirement: !ruby/object:Gem::Requirement
     requirements:
     - - ">="
       - !ruby/object:Gem::Version
-        version: '6'
+        version: '0'
   type: :runtime
   prerelease: false
   version_requirements: !ruby/object:Gem::Requirement
     requirements:
     - - ">="
       - !ruby/object:Gem::Version
-        version: '6'
+        version: '0'
 - !ruby/object:Gem::Dependency
   name: phonelib
   requirement: !ruby/object:Gem::Requirement
@@ -183,6 +183,7 @@ files:
 - examples/whatsapp_controller.rb
 - examples/whatsapp_media_examples.rb
 - flow_chat.gemspec
+- gemfiles/rails_main.gemfile
 - lib/flow_chat.rb
 - lib/flow_chat/app.rb
 - lib/flow_chat/async_job.rb
@@ -285,7 +286,7 @@ required_ruby_version: !ruby/object:Gem::Requirement
   requirements:
   - - ">="
     - !ruby/object:Gem::Version
-      version: 2.3.0
+      version: '3.0'
 required_rubygems_version: !ruby/object:Gem::Requirement
   requirements:
   - - ">="