swal_rails 0.3.1.beta2 → 0.3.2

checksums.yaml

@@ -1,7 +1,7 @@
 ---
 SHA256:
-  metadata.gz: 8bb7a427540f6d06a45d6f18b7a4b29c9771a4890080bbab90dc6806e59502fb
-  data.tar.gz: e39bf17dfad033eb1d23b57710ae48f729ebb26da77139ef359a12f3bf88732b
+  metadata.gz: d9c8d829f1cd2f384c7a40bde0a723bd3a3fd04dccb6fea15b3bd6c543e2a3a7
+  data.tar.gz: d1b4801ab03a209a14051665b0d410c35971dcc2e0bb17ca16d72e724f446a0f
 SHA512:
-  metadata.gz: 72f6a4f2df33ecc991599e09e59bcbcb46f9f328b27803c53c0d4d06f3ad6eb665d9fe23170850e52cf1b277ce211cffe6762edf300ca8525225a3fc8d798cc1
-  data.tar.gz: 770db1bd51acd17a16e0601d67217bd44428d38fdcff73abcc753192371ce49a5ba451735dd181b476465f90db5de65c6ece483a8ed20d79ec8f30106f427133
+  metadata.gz: a72b02157f593c15a9886e2e7c20ebcf6140048cd7f231742096f91215f28cb9273c50b9772405c8d611450d68b89715805f3015393ac15177e28cc981354f22
+  data.tar.gz: e4590aa66cbd7429b85b5d4a194911a3c1011144f96903293b40eb02ddc72ebb8153da0c0e0bb6fb0b41b327058bfb6a81e81108a66287845af7e4169fcfcf41

data/CHANGELOG.md

@@ -6,44 +6,18 @@ and this project adheres to [Semantic Versioning](https://semver.org/spec/v2.0.0
 
 ## [Unreleased]
 
-## [0.3.1.beta2] - 2026-04-24
+## [0.3.2] - 2026-04-25
 
-### Fixed
-- Flash runtime now also boots on `turbo:render`, not just `turbo:load`.
-  Form submissions that render in place (`render :index, status:
-  :unprocessable_entity` for `flash.now` payloads) trigger `turbo:render`
-  but not `turbo:load`, so the `swal-flash` meta tag emitted in the new
-  body never reached the runtime. The existing `data-swal-consumed`
-  guard on the meta tag dedupes the double-fire on full navigations.
-- Stacked-mode clones now render at SA2's standard toast width (360px,
-  capped at viewport width minus 2rem) instead of stretching to the full
-  page. The fix applies CSS to `#swal-rails-stack` mirroring SA2's
-  internal `body.swal2-toast-shown .swal2-container` rules — necessary
-  because the cloned popups live outside SA2's container hierarchy.
-- Confirm `:turbo_override` / `:both` now writes to
-  `Turbo.config.forms.confirm` first (Turbo 8.1+) and only falls back to
-  the deprecated `Turbo.setConfirmMethod`. Silences the Turbo deprecation
-  warning logged on every page load.
-
-### Changed
-- `default_options` no longer ships with `focusConfirm: true` /
-  `returnFocus: true`. Both are already SA2's internal defaults, so
-  behavior is unchanged — but listing them explicitly made SA2 warn
-  ("incompatible with toasts") on every toast fire. The generator
-  template is updated to match.
-- `flash_map[:alert]` and `flash_map[:error]` now default to a toast
-  (top-end, 4s, error icon) instead of a blocking modal. This makes every
-  built-in flash key a toast out of the box — more consistent and more in
-  line with how Rails apps typically use `flash[:alert]`. Users who want
-  the old modal behavior can still opt in:
-  `config.flash_map[:alert] = { icon: "error", toast: false }`.
+First stable release on top of the `0.3.1.beta1` + `0.3.1.beta2`
+prereleases. End users upgrading from `0.3.0` should read the
+consolidated entry below.
 
 ### Added
 - `config.flash_array_mode` (`:sequential` default | `:stacked`) — how a
   multi-entry flash payload is played. Sequential waits for each Swal to
-  close before firing the next (current behavior); stacked renders every
-  toast in parallel in a fixed top-right container with a configurable
-  delay between each appearance.
+  close before firing the next; stacked renders every toast in parallel in
+  a fixed top-right container with a configurable delay between each
+  appearance.
 - `config.flash_stack_delay` (ms, default 500) — gap between stacked
   toasts in `:stacked` mode.
 - `swal_flash(key, messages, mode:, delay:, now:, **options)` helper,
@@ -53,15 +27,52 @@ and this project adheres to [Semantic Versioning](https://semver.org/spec/v2.0.0
 - Reserved meta-keys `_arrayMode` / `_stackDelay` on flash entry options,
   stripped by the JS runtime before being passed to `Swal.fire`.
 
-## [0.3.1.beta1] - 2026-04-21
-
 ### Changed
-- First public release on [RubyGems.org](https://rubygems.org/gems/swal_rails). Prior `0.x` tags lived on GitHub Packages only.
+- `flash_map[:alert]` and `flash_map[:error]` now default to a toast
+  (top-end, 4s, error icon) instead of a blocking modal. Every built-in
+  flash key is a toast out of the box — more consistent and in line with
+  how Rails apps typically use `flash[:alert]`. The old modal behavior is
+  still opt-in: `config.flash_map[:alert] = { icon: "error", toast: false }`.
+- `default_options` no longer ships with `focusConfirm: true` /
+  `returnFocus: true`. Both are SA2's internal defaults already, so
+  behavior is unchanged — but listing them explicitly made SA2 warn
+  ("incompatible with toasts") on every toast fire. Generator template
+  updated to match.
+- Generator initializer comment for `:turbo_override` now mentions
+  `Turbo.config.forms.confirm` (Turbo 8.1+) with a fallback to the legacy
+  `setConfirmMethod`.
 - Release workflow now publishes to RubyGems via [Trusted Publishing](https://guides.rubygems.org/trusted-publishing/) (OIDC), no long-lived API key.
+- First public release on [RubyGems.org](https://rubygems.org/gems/swal_rails). Prior `0.x` tags lived on GitHub Packages only.
+
+### Fixed
+- Flash runtime also boots on `turbo:render`, not just `turbo:load`. Form
+  submissions that render in place (`render :index, status:
+  :unprocessable_entity` for `flash.now` payloads) trigger `turbo:render`
+  but not `turbo:load`, so the `swal-flash` meta tag emitted in the new
+  body never reached the runtime. The `data-swal-consumed` guard on the
+  meta tag dedupes the double-fire on full navigations.
+- Stacked-mode clones render at SA2's standard toast width (360px, capped
+  at `calc(100vw - 2rem)`) instead of stretching to the full page. CSS on
+  `#swal-rails-stack` mirrors SA2's `body.swal2-toast-shown .swal2-container`
+  rules — necessary because the cloned popups live outside SA2's container
+  hierarchy.
+- Confirm `:turbo_override` / `:both` writes to `Turbo.config.forms.confirm`
+  first (Turbo 8.1+) and falls back to the deprecated
+  `Turbo.setConfirmMethod`. Silences the Turbo deprecation warning.
 
 ### Security
-- `.gitignore` hardened preventively against `.env`, `master.key`, `config/credentials/*.key`, `*.pem`, `*.key`.
-- Gemspec now pins `allowed_push_host` to `https://rubygems.org` as a safety net against accidental push to other hosts.
+- `.gitignore` hardened preventively against `.env`, `master.key`,
+  `config/credentials/*.key`, `*.pem`, `*.key`.
+- Gemspec pins `allowed_push_host` to `https://rubygems.org` as a safety
+  net against accidental push to other hosts.
+
+## [0.3.1.beta2] - 2026-04-24
+
+Prerelease snapshot — superseded by [0.3.2].
+
+## [0.3.1.beta1] - 2026-04-21
+
+Prerelease snapshot — superseded by [0.3.2].
 
 ## [0.3.0] - 2026-04-21
 

data/gemfiles/rails_7_2.gemfile

@@ -14,12 +14,12 @@ group :development, :test do
   gem "appraisal", "~> 2.5"
   gem "capybara", "~> 3.40"
   gem "cuprite", "~> 0.15"
-  gem "puma", "~> 6.4"
+  gem "puma", "~> 8.0"
   gem "rspec", "~> 3.12"
-  gem "rspec-rails", "~> 6.1"
+  gem "rspec-rails", "~> 8.0"
   gem "rubocop", "~> 1.60", require: false
   gem "rubocop-rspec", require: false
-  gem "sqlite3", "~> 1.7"
+  gem "sqlite3", "~> 2.9"
 end
 
 gemspec path: "../"

data/gemfiles/rails_8_0.gemfile

@@ -14,12 +14,12 @@ group :development, :test do
   gem "appraisal", "~> 2.5"
   gem "capybara", "~> 3.40"
   gem "cuprite", "~> 0.15"
-  gem "puma", "~> 6.4"
+  gem "puma", "~> 8.0"
   gem "rspec", "~> 3.12"
-  gem "rspec-rails", "~> 6.1"
+  gem "rspec-rails", "~> 8.0"
   gem "rubocop", "~> 1.60", require: false
   gem "rubocop-rspec", require: false
-  gem "sqlite3", "~> 1.7"
+  gem "sqlite3", "~> 2.9"
 end
 
 gemspec path: "../"

data/gemfiles/rails_8_1.gemfile

@@ -14,12 +14,12 @@ group :development, :test do
   gem "appraisal", "~> 2.5"
   gem "capybara", "~> 3.40"
   gem "cuprite", "~> 0.15"
-  gem "puma", "~> 6.4"
+  gem "puma", "~> 8.0"
   gem "rspec", "~> 3.12"
-  gem "rspec-rails", "~> 6.1"
+  gem "rspec-rails", "~> 8.0"
   gem "rubocop", "~> 1.60", require: false
   gem "rubocop-rspec", require: false
-  gem "sqlite3", "~> 1.7"
+  gem "sqlite3", "~> 2.9"
 end
 
 gemspec path: "../"

data/gemfiles/rails_8_1_sprockets.gemfile

@@ -14,12 +14,12 @@ group :development, :test do
   gem "appraisal", "~> 2.5"
   gem "capybara", "~> 3.40"
   gem "cuprite", "~> 0.15"
-  gem "puma", "~> 6.4"
+  gem "puma", "~> 8.0"
   gem "rspec", "~> 3.12"
-  gem "rspec-rails", "~> 6.1"
+  gem "rspec-rails", "~> 8.0"
   gem "rubocop", "~> 1.60", require: false
   gem "rubocop-rspec", require: false
-  gem "sqlite3", "~> 1.7"
+  gem "sqlite3", "~> 2.9"
 end
 
 gemspec path: "../"

data/lib/generators/swal_rails/install/templates/initializer.rb

@@ -4,7 +4,8 @@ SwalRails.configure do |config|
   # How confirmation modals are wired.
   #   :off             — do nothing, use Swal manually
   #   :data_attribute  — intercept clicks/submits on [data-swal-confirm] (default, non-intrusive)
-  #   :turbo_override  — replace Turbo.setConfirmMethod globally
+  #   :turbo_override  — replace Turbo.config.forms.confirm globally (Turbo 8.1+),
+  #                      falls back to legacy Turbo.setConfirmMethod on older Turbo
   #   :both            — both mechanisms at once
   config.confirm_mode = :<%= options[:confirm_mode] %>
 

data/lib/swal_rails/version.rb

@@ -1,6 +1,6 @@
 # frozen_string_literal: true
 
 module SwalRails
-  VERSION = "0.3.1.beta2"
+  VERSION = "0.3.2"
   SWEETALERT2_VERSION = "11.26.24"
 end

metadata

@@ -1,7 +1,7 @@
 --- !ruby/object:Gem::Specification
 name: swal_rails
 version: !ruby/object:Gem::Version
-  version: 0.3.1.beta2
+  version: 0.3.2
 platform: ruby
 authors:
 - Florian Gagnaire