livechat 0.10.1 → 1.0.0

checksums.yaml

@@ -1,7 +1,7 @@
 ---
 SHA256:
-  metadata.gz: 5f7868af4ac547374ec04ba6aac09d12db7f9ae53776cceb7967cc32c7bf56ef
-  data.tar.gz: 40faba066cf75b325672728f1317a9dd1e56771cb2436c1e3a621ad36a560516
+  metadata.gz: 3784d2aa4059d1cc6faa8b79321ef0ec669dd69fac0b5543a3b881a5342b1961
+  data.tar.gz: d31ff12aa8a32a70315f38216fa4c423f0e130147e21bde0473ae189f337ed45
 SHA512:
-  metadata.gz: 429aaa62a6b365b2314c2193faa3377879aee0b0c564c935065cc4df798e5471a5571c7e2f8b229fec2490b6ca382dfe8e50c2d88d809c063b5bf83b8d9183c3
-  data.tar.gz: 8658bd68fe0bfd233f3ddddd30079bd71f6443394650c306171ecc7db2184602e93bff51622d049b1e0d33b6e355676e077eab8177f9c3c833a13f924cbd71d8
+  metadata.gz: b9a7ceca8836ce9238635a4dce4083eb5e04c60d1fb8241957b85a7c2ac5bff69099a8f19ceee1fa7075f1177075511790e783c9ff41df75cb01651a826f9ce0
+  data.tar.gz: 6fe9125a8525af6a62d4e40f728a4260d12aba7bcef2bc9fb75f12eb89fea1ebe1f75b125c20b47a36597eebe91321e3d94d4d43fe622912e35aea42ae34bb26

data/AGENTS.md

@@ -5,7 +5,7 @@ Instructions for coding agents. Two audiences:
 - **[Installing livechat into a Rails app](#installing-into-a-rails-app)** — you are working in a host app and were asked to add support chat, live chat, or an in-app inbox.
 - **[Working on the gem itself](#working-on-the-gem-itself)** — you are working in this repository.
 
-Requirements: Ruby >= 3.2, Rails >= 7.1. Active Storage only for file attachments. **No Redis and no Action Cable** — the transport is polling unless you opt in.
+Requirements: Ruby >= 3.2, Rails >= 7.1 and < 9. Active Storage only for file attachments. **No Redis and no Action Cable** — the transport is polling unless you opt in.
 
 If you are in a host app and this file is not in front of you, it ships inside the gem: `cat "$(bundle show livechat)/AGENTS.md"`.
 
@@ -104,6 +104,21 @@ Leave it off unless the app already has Action Cable working. Polling is not a d
 
 `config.attach_files` is on by default but **silently inert without Active Storage** in the host app (`rails active_storage:install`) — the widget keeps working, just without a paperclip. Caps: `max_attachments` (5), `max_attachment_size` (10 MB), `allowed_attachment_types` (nil = any). Files are served through the engine at `/livechat/attachments/:id`, gated per request — never a public blob URL. Do not build your own blob links.
 
+Every authorized agent can read every conversation; visitor reads are scoped to
+the signed-in id or guest cookie. There is no tenant-isolated agent inbox in
+1.x. No retention job runs automatically. Hosts should schedule their own
+cutoff and use the destroy lifecycle so messages and attachments follow it:
+
+```ruby
+Livechat::Conversation.purge_resolved(older_than: 90.days.ago)
+```
+
+For an account-erasure request, destroy that user's conversations with
+`where(visitor_id: user.id.to_s).find_each(&:destroy!)`. Do not use
+`delete_all` when attachments must be purged. Confirm storage jobs, backups,
+email notifications and hook destinations separately. The content-type
+allowlist is not malware scanning.
+
 ### Do not
 
 - **Do not copy the widget JavaScript into `app/javascript`, or add a `<script>` tag for it.** `livechat_tag` renders what is needed, and the engine serves the code with a content fingerprint. There is no build step and nothing for esbuild/importmap/Tailwind to know about.
@@ -161,8 +176,14 @@ Turbo Drive and strict nonce-based CSP work out of the box. 26 locales ship with
 
 ## Working on the gem itself
 
+The development toolchain is pinned to Ruby 4.0.5 in `mise.toml`. Do not use
+macOS's `/usr/bin/ruby`. In shells, hooks, or automation where mise activation
+is uncertain, explicitly prepend the configured Ruby, for example
+`PATH="$(mise where ruby)/bin:$PATH" bundle exec rake test`.
+
 ```bash
 bundle exec rake test            # minitest, dummy app under test/dummy
+bundle exec rake test:system     # real headless-Chrome visitor/agent loop
 bundle exec rubocop              # must be clean
 BUNDLE_GEMFILE=gemfiles/rails_7.1.gemfile bundle exec rake test   # 7.1, 7.2, 8.0, 8.1 in gemfiles/
 ```

data/CHANGELOG.md

@@ -1,5 +1,40 @@
 # Changelog
 
+## 1.0.0 - 2026-08-11
+
+- **The 1.x record names are settled.** `Livechat::Conversation` and
+  `Livechat::Message` are now documented as stable model constants rather than
+  being collapsed into a generic `Post`; the distinction preserves the thread
+  aggregate and the messages it owns.
+- **A real Chrome test now proves the core support loop:** a visitor opens the
+  widget and sends a message, an agent reads and answers it in the inbox, and
+  the same visitor sees the reply back in the widget. Capybara and Selenium are
+  development/test dependencies only.
+- **Attachments stay behind the conversation gate.** Full and byte-range data
+  now streams directly with a private, `no-store` cache policy after the
+  request is authorized. The URL is unchanged; audio playback gains seeking,
+  and no reusable Active Storage service URL leaves the engine.
+- Added `Livechat::Conversation.purge_resolved(older_than:)` for explicit host
+  retention jobs. It destroys only resolved conversations older than the
+  supplied cutoff, cascades through messages and the configured Active Storage
+  lifecycle, and returns the number destroyed. Nothing is deleted
+  automatically.
+- Added a security policy documenting stored visitor/message data, the shared
+  agent-inbox boundary, attachment risks, notifications, deletion, retention,
+  and private vulnerability reporting. Submitted page URLs now accept only
+  HTTP(S) and drop credentials, query strings, and fragments before storage,
+  keeping tokens out of the database and notification emails.
+- Hosts that load Action View from an initializer boot normally. The widget
+  helper is loaded from `lib` before the engine registers its Action View hook;
+  `livechat_tag` and `livechat_button` are unchanged.
+- Supported combinations are Ruby 3.2 through 4.0 and Rails 7.1 through 8.1;
+  Rails now has a `< 9` upper bound. Release validation runs the browser test,
+  lint and JavaScript checks, builds the gem, verifies RubyGems indexing, and
+  creates the GitHub Release.
+- Existing 0.x installs need no migration, initializer change, constant alias,
+  or model rename. The new Rails upper bound, query-free stored page URLs, and
+  direct attachment streaming behavior are the compatibility costs.
+
 ## 0.10.1
 
 - **The demo inbox is now a live setup walkthrough.** The open conversation

data/README.md

@@ -50,7 +50,7 @@ demo messages instead of duplicating conversations.
 > The inbox defaults to **development only**. Set `authorize_agent` before you
 > deploy — see [Configure](#configure).
 
-Ruby >= 3.2 · Rails >= 7.1 · Active Storage only if you want file attachments.
+Ruby >= 3.2 · Rails >= 7.1, < 9 · Active Storage only if you want file attachments.
 
 Installing with a coding agent? Point it at [AGENTS.md](AGENTS.md) — the same
 steps in the order an agent needs them, plus the gates it tends to get wrong and
@@ -228,10 +228,11 @@ bin/rails active_storage:install && bin/rails db:migrate
 ```
 
 Visitors get a paperclip in the composer; agents get a file field on the reply
-form. Images render inline, other files as download links. Every file is served
+form. Safe image formats render inline, other files as download links. Every file is served
 through the engine's own route and gated the same way the chat is — an agent,
 or the visitor who owns that conversation — so nothing leaks through a
-guessable or long-lived blob URL.
+guessable or long-lived blob URL. Responses are private and `no-store`; audio
+supports byte ranges for playback and seeking.
 
 Where Active Storage isn't installed, the widget quietly stays text-only.
 
@@ -244,6 +245,38 @@ config.storage_service = :livechat_uploads
 
 </details>
 
+## Privacy, retention, and deletion
+
+Livechat stores conversation identity and context, message bodies and
+attribution, read/status timestamps, and optional attachments in the host
+application. Captured page URLs are limited to HTTP(S) and stored without
+credentials, query strings, or fragments. The engine does not send data to a
+Livechat service, but configured notification emails and message hooks can send
+message content, visitor context, and attachment filenames wherever the host
+chooses.
+
+Every authorized agent can read every conversation in this one shared inbox.
+Visitors can read only the conversation resolved from their signed-in id or
+guest cookie. Livechat does not provide tenant-isolated agent inboxes in 1.x;
+do not use one mount for mutually isolated tenant support teams.
+
+No record is deleted automatically. Delete one conversation (including its
+messages), all conversations for a user, or resolved history past a host-chosen
+cutoff explicitly:
+
+```ruby
+Livechat::Conversation.find(id).destroy!
+Livechat::Conversation.where(visitor_id: user.id.to_s).find_each(&:destroy!)
+Livechat::Conversation.purge_resolved(older_than: 90.days.ago)
+```
+
+Use `destroy!`, not `delete_all`, when attachments must follow Rails' Active
+Storage lifecycle. Confirm object-storage jobs, replicas, backups, notification
+emails, hook destinations, logs, and exports separately: deleting live database
+rows cannot retract those copies. `allowed_attachment_types` is an upload
+allowlist, not malware scanning; choose a restrictive list and storage policy
+for your application. See [SECURITY.md](SECURITY.md) for the full boundary.
+
 <details>
 <summary><b>Realtime with Action Cable</b></summary>
 
@@ -293,6 +326,36 @@ Contextual buttons are where a Rails app beats a generic support widget:
 </button>
 ```
 
+## Compatibility and public API
+
+The following are the model and integration contracts that 1.x will keep
+stable under semantic versioning:
+
+- `Livechat::Conversation`, including `STATUSES`, `TYPING_TTL`, its persisted
+  fields, `messages`, `recent_first`, `for_visitor`, `claim!`, posting and
+  read/status methods, `display_name`, and `purge_resolved`.
+- `Livechat::Message`, including `AUTHOR_TYPES`, `EVENTS`, `MAX_BODY_LENGTH`,
+  its persisted fields, optional `files`, documented scopes, author/read
+  predicates, `public_label`, `attached_files`, and `preview`.
+- `Livechat.configure`, `mount_livechat`, `livechat_tag`, `livechat_button`,
+  `window.Livechat.open/close`, `data-livechat-open`, and
+  `data-livechat-message`.
+- `config.on_visitor_message` and `config.on_agent_message`, each called with
+  the saved `Livechat::Message` documented by the initializer.
+
+`Conversation` and `Message` are intentionally distinct and will not become a
+generic `Post` during 1.x. Engine controllers, partials, CSS classes, generated
+HTML, and widget implementation objects are private. Incompatible changes to
+the public list above wait for a new major version; a deprecation normally
+ships first.
+
+### Upgrading from 0.x
+
+There is no migration, initializer change, constant alias, or model rename.
+Stored page URLs become query-free on the next visitor message, attachment
+responses stay on the same engine URL but now stream privately instead of being
+buffered, and Rails 9 is excluded until a compatible release is tested.
+
 ## Use cases
 
 - SaaS apps: answer billing, onboarding and account questions from inside the app.
@@ -313,6 +376,7 @@ worth of exactly that.
 
 ```bash
 bundle exec rake test
+bundle exec rake test:system
 bundle exec rubocop
 ```
 

data/Rakefile

@@ -5,7 +5,15 @@ require 'rake/testtask'
 
 Rake::TestTask.new(:test) do |t|
   t.libs << 'test'
-  t.pattern = 'test/**/*_test.rb'
+  t.test_files = FileList['test/**/*_test.rb'].exclude('test/system/**/*')
+end
+
+namespace :test do
+  desc 'Run browser (system) tests'
+  Rake::TestTask.new(:system) do |task|
+    task.libs << 'test'
+    task.test_files = FileList['test/system/**/*_test.rb']
+  end
 end
 
 task default: :test

data/SECURITY.md

@@ -0,0 +1,71 @@
+# Security policy
+
+## Supported versions
+
+Security fixes are released for the latest 1.x version. If a report also
+affects the newest 0.x release, a backport may be published when the fix is
+small and the affected application cannot upgrade immediately.
+
+## Reporting a vulnerability
+
+Please do not open a public issue for a vulnerability. Use
+[GitHub private vulnerability reporting](https://github.com/yshmarov/livechat/security/advisories/new)
+and include the affected version, a minimal reproduction, impact, and any known
+workaround. Do not include credentials, session cookies, visitor tokens,
+private application URLs, customer messages, uploaded files, or production
+database contents.
+
+Public disclosure should wait until a fixed version is available and affected
+users have had a reasonable opportunity to upgrade.
+
+## Data and authorization boundary
+
+The widget and visitor endpoints are controlled by `config.enabled`; the agent
+inbox is separately protected by `authorize_agent` and fails closed outside
+development until the host grants access. A visitor can read only the
+conversation resolved from their signed-in id or opaque guest cookie. Every
+authorized agent can read and answer every conversation in the mounted inbox.
+Livechat 1.x does not provide tenant-isolated agent inboxes.
+
+Conversations can store a visitor token, host user id and label, email, status,
+query-free HTTP(S) page URL, locale, message preview, activity timestamps, and
+record timestamps. Messages can store bodies, author type, agent id and label,
+system events, read state, timestamps, and optional files. Page credentials,
+query strings, fragments, executable URL schemes, and invalid URLs are not
+stored. Message bodies are plain text and length-capped; rendering escapes
+them rather than interpreting Markdown or HTML.
+
+Attachments stream through the engine only after the request is authorized as
+an agent or the owning visitor. Responses are private and `no-store`, support
+byte ranges, and never redirect to a reusable signed blob URL. Hosts own the
+storage service, bucket policy, backups, retention, malware controls, access
+logs, and incident response. `allowed_attachment_types` is an application
+allowlist, not content inspection or malware scanning.
+
+Livechat has no vendor service and does not transmit conversation data to this
+project. Host-configured notification email can include message content,
+visitor context, and attachment filenames. `on_visitor_message` and
+`on_agent_message` receive the saved message and can send it anywhere the host
+chooses. Those email and hook destinations are part of the host's privacy and
+retention boundary.
+
+## Deletion and retention
+
+Nothing is deleted automatically. Use the Active Record destroy lifecycle so
+messages and Active Storage attachments follow their configured dependencies:
+
+```ruby
+Livechat::Conversation.find(id).destroy!
+Livechat::Conversation.where(visitor_id: user.id.to_s).find_each(&:destroy!)
+Livechat::Conversation.purge_resolved(older_than: 90.days.ago)
+```
+
+`purge_resolved` removes only resolved conversations whose last activity is
+older than the supplied cutoff and returns the number destroyed. Open threads
+are never removed by it. Do not use `delete_all` when dependent messages and
+attachments must be removed.
+
+Active Storage may enqueue blob purging through the host's Active Job adapter.
+Confirm those jobs and deletion from object storage, replicas, backups, caches,
+notification mailboxes, hook destinations, logs, analytics, and exports;
+deleting live database rows does not rewrite those systems.

data/app/controllers/concerns/livechat/request_context.rb

@@ -1,5 +1,7 @@
 # frozen_string_literal: true
 
+require 'uri'
+
 module Livechat
   # Who is asking — visitor or agent — and the gates that answer it.
   #
@@ -55,6 +57,24 @@ module Livechat
       render json: { errors: [message] }, status: :too_many_requests
     end
 
+    # The widget sends window.location.href so an agent knows where the visitor
+    # got stuck. Store only a normal HTTP(S) location, never credentials,
+    # fragments, or query parameters that can carry tokens and customer data.
+    def clean_page_url(value)
+      raw = value.to_s
+      return if raw.blank? || raw.length > 2_048
+
+      uri = URI.parse(raw)
+      return unless %w[http https].include?(uri.scheme&.downcase)
+      return if uri.host.blank? || uri.userinfo.present?
+
+      uri.query = nil
+      uri.fragment = nil
+      uri.to_s.first(255)
+    rescue URI::InvalidURIError
+      nil
+    end
+
     # Guests get a permanent random token — their key to the conversation
     # across visits. Signed-in visitors are keyed by id and only need the
     # cookie to carry a guest history into their account.

data/app/controllers/livechat/attachments_controller.rb

@@ -7,6 +7,8 @@ module Livechat
   # visitor whose conversation it belongs to. Streamed inline (not redirected
   # to a signed blob URL), so no long-lived link ever escapes the gate.
   class AttachmentsController < ApplicationController
+    include ActiveStorage::Streaming if defined?(::ActiveStorage::Streaming)
+
     def show
       attachment = find_attachment
       return head :not_found unless attachment
@@ -47,15 +49,72 @@ module Livechat
     end
 
     # Images and audio render inline (so the clients can show native media
-    # controls); anything else downloads. nosniff keeps the browser from
-    # second-guessing the type of a visitor-supplied file.
+    # controls); anything else downloads. Responses are private and never
+    # stored, and byte ranges keep audio seek/playback working without handing
+    # out an Active Storage service URL.
     def stream(blob)
       response.headers['X-Content-Type-Options'] = 'nosniff'
-      inline = blob.content_type.to_s.start_with?('image/', 'audio/')
-      send_data blob.download,
-                filename: blob.filename.to_s,
-                type: blob.content_type.presence || 'application/octet-stream',
-                disposition: inline ? 'inline' : 'attachment'
+      response.headers['Cache-Control'] = 'private, no-store'
+      disposition = inline?(blob) ? 'inline' : 'attachment'
+
+      if request.headers['Range'].present?
+        if inline_audio?(blob)
+          send_audio_byte_range_data(blob, request.headers['Range'])
+        else
+          send_blob_byte_range_data(blob, request.headers['Range'], disposition:)
+        end
+      elsif inline_audio?(blob)
+        stream_audio(blob)
+      else
+        response.headers['Accept-Ranges'] = 'bytes'
+        response.headers['Content-Length'] = blob.byte_size.to_s
+        send_blob_stream(blob, disposition:)
+      end
+    end
+
+    # Active Storage deliberately forces types outside its image/PDF allowlist
+    # to download. The widget's recorded voice notes are a small explicit
+    # exception; nosniff plus an audio Content-Type keeps them media-only.
+    def inline?(blob)
+      AttachmentPolicy.inline?(blob.content_type)
+    end
+
+    def inline_audio?(blob)
+      AttachmentPolicy.audio?(blob.content_type)
+    end
+
+    def stream_audio(blob)
+      response.headers['Accept-Ranges'] = 'bytes'
+      response.headers['Content-Length'] = blob.byte_size.to_s
+      send_stream(filename: blob.filename.sanitized, disposition: 'inline', type: blob.content_type) do |stream|
+        blob.download { |chunk| stream.write(chunk) }
+      end
+    rescue ActiveStorage::FileNotFoundError
+      expires_now
+      head :not_found
+    end
+
+    def send_audio_byte_range_data(blob, range_header)
+      ranges = Rack::Utils.get_byte_ranges(range_header, blob.byte_size)
+      range = ranges.first if ranges&.one?
+      return head :range_not_satisfiable unless range
+      return head :range_not_satisfiable if range.end - range.begin >= streaming_chunk_max_size
+
+      data = blob.download_chunk(range)
+      response.headers['Content-Range'] = "bytes #{range.begin}-#{range.end}/#{blob.byte_size}"
+      response.headers['Accept-Ranges'] = 'bytes'
+      response.headers['Content-Length'] = data.bytesize.to_s
+      send_data data, filename: blob.filename.sanitized, disposition: 'inline',
+                      status: :partial_content, type: blob.content_type
+    end
+
+    # Rails 8 exposes this knob; Rails 7.1/7.2 do not. Match the newer default
+    # on older supported releases so a Range header cannot force an unbounded
+    # in-memory chunk.
+    def streaming_chunk_max_size
+      return ActiveStorage.streaming_chunk_max_size if ActiveStorage.respond_to?(:streaming_chunk_max_size)
+
+      100 * 1024 * 1024
     end
   end
 end

data/app/controllers/livechat/visitor_controller.rb

@@ -90,7 +90,7 @@ module Livechat
         visitor_token: current_visitor_id ? visitor_token : ensure_visitor_token,
         visitor_label: visitor_label,
         visitor_email: (current_visitor.try(:email).presence if current_visitor),
-        page_url: params[:page_url].to_s.first(255).presence,
+        page_url: clean_page_url(params[:page_url]),
         locale: params[:locale].to_s.first(10).presence
       )
     end
@@ -105,7 +105,8 @@ module Livechat
     # "where are they stuck right now" is what an answering agent needs.
     def refresh_context(conversation)
       updates = {}
-      updates[:page_url] = params[:page_url].to_s.first(255) if params[:page_url].present?
+      page_url = clean_page_url(params[:page_url])
+      updates[:page_url] = page_url if page_url
       updates[:locale] = params[:locale].to_s.first(10) if params[:locale].present?
       conversation.update_columns(updates) if updates.any?
     end

data/app/models/livechat/conversation.rb

@@ -19,6 +19,20 @@ module Livechat
 
     scope :recent_first, -> { order(last_activity_at: :desc, id: :desc) }
 
+    # Host-controlled retention. Only resolved threads whose last activity is
+    # older than the supplied cutoff are removed; open conversations are never
+    # deleted automatically. Destroying (rather than delete_all) lets Rails run
+    # the message and Active Storage attachment lifecycle. Returns the number
+    # of conversations destroyed so a scheduled job can report what it did.
+    def self.purge_resolved(older_than:)
+      destroyed = 0
+      where(status: 'resolved', last_activity_at: ...older_than).find_each do |conversation|
+        conversation.destroy!
+        destroyed += 1
+      end
+      destroyed
+    end
+
     STATUSES.each do |status|
       define_method(:"#{status}?") { self.status == status }
     end

data/app/models/livechat/message.rb

@@ -108,8 +108,8 @@ module Livechat
         { id: file.id,
           name: file.filename.to_s,
           url: "#{base}/attachments/#{file.id}",
-          image: content_type.start_with?('image/'),
-          audio: content_type.start_with?('audio/'),
+          image: AttachmentPolicy.image?(content_type),
+          audio: AttachmentPolicy.audio?(content_type),
           size: file.byte_size }
       end
     end

data/lib/livechat/attachment_policy.rb

@@ -0,0 +1,27 @@
+# frozen_string_literal: true
+
+module Livechat
+  # The small set of uploads the engine renders in a browser instead of
+  # downloading. Active Storage owns the safe image/PDF allowlist; Livechat
+  # adds common audio formats because voice messages are a first-class feature.
+  module AttachmentPolicy
+    INLINE_AUDIO_TYPES = %w[
+      audio/mpeg audio/mp4 audio/ogg audio/wav audio/webm audio/x-wav
+    ].freeze
+
+    module_function
+
+    def inline?(content_type)
+      audio?(content_type) || ActiveStorage.content_types_allowed_inline.include?(content_type)
+    end
+
+    def image?(content_type)
+      content_type.to_s.start_with?('image/') &&
+        ActiveStorage.content_types_allowed_inline.include?(content_type)
+    end
+
+    def audio?(content_type)
+      INLINE_AUDIO_TYPES.include?(content_type)
+    end
+  end
+end

data/lib/livechat/version.rb

@@ -1,5 +1,5 @@
 # frozen_string_literal: true
 
 module Livechat
-  VERSION = '0.10.1'
+  VERSION = '1.0.0'
 end

data/{app/helpers → lib}/livechat/widget_helper.rb

@@ -1,11 +1,10 @@
 # frozen_string_literal: true
 
 module Livechat
-  # Included into the host's ActionView. Drop `<%= livechat_tag %>` before
-  # </body> in your layout; it renders nothing unless chat is enabled for the
-  # request. The widget shows a floating launcher (unless show_launcher is
-  # off) and also opens from any element carrying `data-livechat-open`, or
-  # from `window.Livechat.open()`.
+  # Included into the host's ActionView. Kept under lib and required before the
+  # engine registers its Action View load hook: a host initializer may load
+  # Action View before Rails sets up application autoloaders, when a helper
+  # living only under app/helpers is not yet a resolvable constant.
   module WidgetHelper
     def livechat_tag
       return unless Livechat.enabled?(request)
@@ -29,7 +28,7 @@ module Livechat
       data = (options.delete(:data) { {} } || {}).merge(livechat_open: '')
       data[:livechat_message] = message if message.present?
 
-      tag.button(label, type: 'button', data: data, **options)
+      tag.button(label, type: 'button', data:, **options)
     end
 
     private

data/lib/livechat.rb

@@ -3,6 +3,8 @@
 require 'livechat/version'
 require 'livechat/configuration'
 require 'livechat/widget'
+require 'livechat/widget_helper'
+require 'livechat/attachment_policy'
 require 'livechat/notifications'
 require 'livechat/seeds'
 require 'livechat/engine'

metadata

@@ -1,7 +1,7 @@
 --- !ruby/object:Gem::Specification
 name: livechat
 version: !ruby/object:Gem::Version
-  version: 0.10.1
+  version: 1.0.0
 platform: ruby
 authors:
 - Yaroslav Shmarov
@@ -16,6 +16,9 @@ dependencies:
     - - ">="
       - !ruby/object:Gem::Version
         version: '7.1'
+    - - "<"
+      - !ruby/object:Gem::Version
+        version: '9'
   type: :runtime
   prerelease: false
   version_requirements: !ruby/object:Gem::Requirement
@@ -23,6 +26,9 @@ dependencies:
     - - ">="
       - !ruby/object:Gem::Version
         version: '7.1'
+    - - "<"
+      - !ruby/object:Gem::Version
+        version: '9'
 description: |
   A mountable Rails engine that adds support chat to your app — the thing
   you'd otherwise pay Crisp or Intercom for, or deploy Chatwoot to get. A
@@ -43,6 +49,7 @@ files:
 - MIT-LICENSE
 - README.md
 - Rakefile
+- SECURITY.md
 - app/controllers/concerns/livechat/request_context.rb
 - app/controllers/livechat/application_controller.rb
 - app/controllers/livechat/attachments_controller.rb
@@ -52,7 +59,6 @@ files:
 - app/controllers/livechat/visitor_controller.rb
 - app/controllers/livechat/widgets_controller.rb
 - app/helpers/livechat/inbox_helper.rb
-- app/helpers/livechat/widget_helper.rb
 - app/mailers/livechat/mailer.rb
 - app/models/livechat/application_record.rb
 - app/models/livechat/conversation.rb
@@ -96,6 +102,7 @@ files:
 - lib/generators/livechat/install/templates/initializer.rb
 - lib/generators/livechat/migration_helpers.rb
 - lib/livechat.rb
+- lib/livechat/attachment_policy.rb
 - lib/livechat/channels.rb
 - lib/livechat/configuration.rb
 - lib/livechat/dashboard.css
@@ -106,13 +113,14 @@ files:
 - lib/livechat/version.rb
 - lib/livechat/widget.js
 - lib/livechat/widget.rb
+- lib/livechat/widget_helper.rb
 - lib/tasks/livechat_tasks.rake
 homepage: https://github.com/yshmarov/livechat
 licenses:
 - MIT
 metadata:
   homepage_uri: https://github.com/yshmarov/livechat
-  source_code_uri: https://github.com/yshmarov/livechat
+  source_code_uri: https://github.com/yshmarov/livechat/tree/main
   changelog_uri: https://github.com/yshmarov/livechat/blob/main/CHANGELOG.md
   bug_tracker_uri: https://github.com/yshmarov/livechat/issues
   rubygems_mfa_required: 'true'
@@ -130,7 +138,7 @@ required_rubygems_version: !ruby/object:Gem::Requirement
     - !ruby/object:Gem::Version
       version: '0'
 requirements: []
-rubygems_version: 4.0.10
+rubygems_version: 4.0.16
 specification_version: 4
 summary: 'Open-source live chat for Rails: a drop-in support widget plus a team inbox,
   in your own database.'