activejob-debounce 1.0.0 → 1.0.1

checksums.yaml

@@ -1,7 +1,7 @@
 ---
 SHA256:
-  metadata.gz: e1f75d298bfa0f6d3465458cfbae9b6c1e0aa478931d7239bb3165313513cef2
-  data.tar.gz: 2f5878e7ceb1d785a24084491fab650cebea2b9a477a8dac492cd1ca46ce5091
+  metadata.gz: 8f40ec6b49b4676e713a84da8b7264805b55f43d40187c852ba26a9d92ae03ce
+  data.tar.gz: 0e9f036e06b186d1b9574ce77b41323dbfd03d4776a195b484b9af9ec24222c5
 SHA512:
-  metadata.gz: a37dad2992e3def5f3876ce2126a21f711b93ca7746d027b5099c12f070fb48c1529252f600dfcc9c638c8af2f785fc617e91f75d37bd5be146f9791c45df21b
-  data.tar.gz: f981f5b6a520b3811642c45b0dd6062ed11e69e4400fb3f9448cc82a63e5cd0c1342303f6eff72b940ca20e305f3afe03585399dc2850e9e5f796414e3d5eeeb
+  metadata.gz: b1275539d5e7bc204532ba80d7bbc873bfec298e3d45e14517eed9eb8f1b8cfd811ecc5c5278a6684bae5ab05b75e1da1421d9a4885a2221612f3d5a427a7941
+  data.tar.gz: 53b3bebbeeee33f58acc8d83956735d81fae12b0ece64065178e6272bcb2a5735a3a56c65c16007fd7c1c4322fce7e508fd2589b980704dee97b4bfce4855e05

data/CHANGELOG.md

@@ -5,6 +5,12 @@ All notable changes to this project will be documented in this file.
 The format is based on [Keep a Changelog](https://keepachangelog.com/en/1.0.0/),
 and this project adheres to [Semantic Versioning](https://semver.org/spec/v2.0.0.html).
 
+## [1.0.1] - 2026-07-02
+
+### Fixed
+- Preserve keyword arguments through `perform_debounce` on Ruby 3 (`ruby2_keywords`); jobs whose `perform` takes keyword arguments no longer raise `ArgumentError` on execution
+- Repair test suite left broken by the activejob-debounce rebrand (stale `sidekiq-debouncer` require and `Sidekiq::Debouncer` configuration reset)
+
 ## [1.0.0] - 2025-01-13
 
 ### Added

data/README.md

@@ -1,6 +1,6 @@
 # ActiveJob::Debounce
 
-Leading-edge debounce for ActiveJob. One job per debounce window, atomic Redis gating, crash recovery.
+Dispatch-time debounce for ActiveJob. One job per debounce window, atomic Redis gating, crash recovery.
 
 Works with **any ActiveJob backend**: Sidekiq, GoodJob, Solid Queue, Resque, etc.
 
@@ -141,7 +141,7 @@ Uses Redis `GETSET` for atomic dispatch-time gating:
 3. If old value is in the future → job already pending, skip
 4. `after_perform` deletes the key → opens the window for next cycle
 
-This is a **leading-edge** debounce: first event triggers execution after the delay. Subsequent events during the window are dropped.
+The first event triggers execution after the delay. Subsequent events during the window are dropped.
 
 ## Redis key format
 

data/lib/activejob/debounce/concern.rb

@@ -73,6 +73,7 @@ module ActiveJob
 
           set(wait: delay + buffer).perform_later(*params)
         end
+        ruby2_keywords :perform_debounce
 
         # Generate a unique Redis key for this job + arguments combination.
         #

data/lib/activejob/debounce/version.rb

@@ -2,6 +2,6 @@
 
 module ActiveJob
   module Debounce
-    VERSION = "1.0.0"
+    VERSION = "1.0.1"
   end
 end

metadata

@@ -1,7 +1,7 @@
 --- !ruby/object:Gem::Specification
 name: activejob-debounce
 version: !ruby/object:Gem::Version
-  version: 1.0.0
+  version: 1.0.1
 platform: ruby
 authors:
 - Mohamed Bouzentm