karafka 2.5.9 → 2.6.0.beta1

checksums.yaml

@@ -1,7 +1,7 @@
 ---
 SHA256:
-  metadata.gz: 0a43645cb0713b1565aa8ff9b3779d5d19225f08d2449e816ab17aaa532a6ffd
-  data.tar.gz: 438e1dcb6d6b65fd29e2d4f2feb6cee80cf8c629cba273b3e2936637379cda75
+  metadata.gz: 04dfc2086393c6d3d1b8c78eca503c425842453163b014dcba68a5c4231fe090
+  data.tar.gz: 5f62160e469b6eb2383234f630654b46fe704e9dedd896e863771c945ab8e30e
 SHA512:
-  metadata.gz: 44a2d60d274f70321846a4190e007f4d5c75f22e995835fe92cf29a5a658ed7eb99bd96147d6cfa08e9821676ca7064fcd095ecf17b6ac4014c018d885621e27
-  data.tar.gz: 4eb201aeb1e1d416008913c58b7f39637dce2342506f0032d8556b285025cf23f1475f8cf08f2d91a4ee00a9241902e26fc8ca7297547a41cd0b1126d09029ac
+  metadata.gz: 3f1bb0b95294bb925b71ff4cd91d0603b538b4f7f9a222a4789aa9aeef89f7f80b8b26ebf2623f1c44585e1de1d87d4be6dbb55748f61de9b1dd90cab68059d7
+  data.tar.gz: 1c79e3b072d6b53c0062f0ade986f357f677cae6d476297389732c3c130fd89e84687526729ba2590763d15d5f0279e08e3ca9fceec386401b2d9d5ec3ef2096

data/CHANGELOG.md

@@ -1,5 +1,39 @@
 # Karafka Framework Changelog
 
+## 2.6.0 (Unreleased)
+- [Maintenance] Replace manual per-version `Warning[:performance]` / `Warning[:deprecated]` flag setup in specs with a dynamic `Warning.categories`-based approach that enables all non-experimental warning categories automatically, keeping spec warning configuration in sync with karafka-rdkafka.
+- [Enhancement] Replace per-partition `query_watermark_offsets` consumer calls in `Admin::Topics#read_watermark_offsets` with two batch `list_offsets` admin calls (`:earliest` and `:latest`), reducing N sequential consumer roundtrips to 2 admin roundtrips regardless of how many topics or partitions are queried. Replace per-partition `query_watermark_offsets` fallback in `Admin::ConsumerGroups#seek` (when a time-based offset resolves beyond the last message) with a single batch `list_offsets` call covering all affected partitions. Replace per-partition `query_watermark_offsets` loop in `Pro::Iterator::TplBuilder#resolve_partitions_with_negative_offsets` with one batched `offsets_for_times(epoch)` call for consumer metadata warm-up plus two batch admin `list_offsets` calls for LWM/HWM resolution, reducing N sequential calls to 3 total (Pro).
+- **[Feature]** Add `Karafka::Admin.read_partition_offsets` (and `Admin::Topics#read_partition_offsets`) to expose the `rd_kafka_ListOffsets` admin API. Allows querying partition offsets by spec (`:earliest`, `:latest`, `:max_timestamp`, or a timestamp in ms) without a consumer group. Accepts an optional `isolation_level:` keyword — pass `Karafka::Admin::IsolationLevels::READ_COMMITTED` to get the Last Stable Offset (LSO) instead of the high-watermark, giving accurate lag figures on transactionally-produced topics.
+- **[Feature]** Add `Karafka::Admin::IsolationLevels` module with `READ_UNCOMMITTED` and `READ_COMMITTED` constants. These wrap the underlying `Rdkafka::Bindings` integer constants so callers do not need to reference rdkafka internals directly.
+- **[Feature]** Introduce standalone `Karafka::Declaratives` subsystem (`Declaratives::Topic`, `Declaratives::Repository`, `Declaratives::Builder`) decoupled from routing. Topic declarations can now be defined via `Karafka::App.declaratives.draw` independently of routing blocks. The existing `routing#config(partitions:, ...)` DSL continues to work as a backwards-compatible bridge that populates the shared declaratives repository.
+- [Enhancement] CLI topic commands (`create`, `delete`, `reset`, `repartition`, `align`, `migrate`, `plan`) now read from `Karafka::App.declaratives.topics` instead of walking the routing tree. Topics declared via the standalone `declaratives.draw` DSL are now managed by all CLI commands without requiring a routing entry. The routing bridge sets `bootstrap_servers` on declarations for cluster filtering.
+- [Enhancement] Move consumer-group-specific `Processing` components (`Coordinator`, `CoordinatorsBuffer`, `Executor`, `ExecutorsBuffer`, `Partitioner`, `ExpansionsSelector`, `InlineInsights`) and Pro equivalents (including `SubscriptionGroupsCoordinator`, `Collapser`, `AdaptiveIterator`, `PeriodicJob`, `ParallelSegments`, `VirtualPartitions`, `Filters`, `OffsetMetadata`, `Piping`) under the `ConsumerGroups` namespace (internal). The `config.processing.coordinator_class`, `executor_class`, `partitioner_class`, and `expansions_selector` defaults are updated accordingly; user-provided classes are unaffected. Generic processing components (`JobsQueue`, `Worker`, `WorkersPool`, `Schedulers::*`, `Jobs::Base`) stay in their original locations.
+- [Enhancement] Move processing strategies (`Karafka::Processing::Strategies::*` and `Karafka::Pro::Processing::Strategies::*`) under the `ConsumerGroups` namespace (internal). Prepares the processing layer for parallel `ShareGroups::Strategies` once KIP-932 lands.
+- [Enhancement] Move `Karafka::Processing::StrategySelector` and `Karafka::Pro::Processing::StrategySelector` under the `ConsumerGroups` namespace (internal). The `config.processing.strategy_selector` default is updated accordingly; user-provided selectors are unaffected.
+- [Enhancement] Move `Karafka::Connection::RebalanceManager` to `Karafka::Connection::ConsumerGroups::RebalanceManager` (internal). Prepares the connection layer for a parallel `ShareGroups` namespace once KIP-932 lands.
+- [Enhancement] Move the rebalance librdkafka callback to `Karafka::Instrumentation::Callbacks::ConsumerGroups::Rebalance` (internal). Published event names (`rebalance.*`) and payload shape are unchanged.
+- [Enhancement] Move `Karafka::Instrumentation::Callbacks::Error` and `Karafka::Instrumentation::Callbacks::Statistics` to `Karafka::Instrumentation::Callbacks::ConsumerGroups::Error` and `ConsumerGroups::Statistics` (internal). Completes the callbacks layer namespacing — all consumer-group-specific librdkafka callbacks now live under `Callbacks::ConsumerGroups`. Published event names and payload shape are unchanged.
+- [Enhancement] Namespace consumer-group-specific processing job classes under `Karafka::Processing::ConsumerGroups::Jobs` (OSS: `Consume`, `Eofed`, `Revoked`, `Shutdown`, `Idle`) and `Karafka::Pro::Processing::ConsumerGroups::Jobs` (Pro: `ConsumeNonBlocking`, `EofedNonBlocking`, `Periodic`, `PeriodicNonBlocking`, `RevokedNonBlocking`). Only `Jobs::Base` stays under `Karafka::Processing::Jobs` as the generic base class. Internal move only — no public API changes; prepares the processing layer for parallel `ShareGroups::Jobs` (KIP-932).
+- [Enhancement] Move `Karafka::Processing::JobsBuilder` to `Karafka::Processing::ConsumerGroups::JobsBuilder` and `Karafka::Pro::Processing::JobsBuilder` to `Karafka::Pro::Processing::ConsumerGroups::JobsBuilder` (internal). The jobs builder only creates consumer-group-specific jobs; prepares the processing layer for a parallel `ShareGroups::JobsBuilder` once KIP-932 lands.
+- [Enhancement] Nest consumer-group-specific processing config settings (`coordinator_class`, `errors_tracker_class`, `partitioner_class`, `strategy_selector`, `expansions_selector`, `executor_class`, `jobs_builder`) under `config.internal.processing.consumer_groups`. Shared settings (`jobs_queue_class`, `scheduler_class`, `worker_job_call_wrapper`) remain at the `config.internal.processing` level. Prepares the config structure for a parallel `config.internal.processing.share_groups` sub-namespace once KIP-932 lands.
+- [Enhancement] Move OSS consumer-group-specific routing features (`ActiveJob`, `DeadLetterQueue`, `Eofed`, `InlineInsights`, `ManualOffsetManagement`) from `Routing::Features` to `Routing::Features::ConsumerGroups` (internal). Agnostic features (`Declaratives`, `Deserializers`) remain at the `Routing::Features` level. Prepares the routing layer for a parallel `Routing::Features::ShareGroups` namespace once KIP-932 lands.
+- [Enhancement] Move Pro consumer-group-specific routing features (`ActiveJob`, `AdaptiveIterator`, `DeadLetterQueue`, `Delaying`, `DirectAssignments`, `InlineInsights`, `LongRunningJob`, `Multiplexing`, `NonBlockingJob`, `OffsetMetadata`, `ParallelSegments`, `Patterns`, `PeriodicJob`, `RecurringTasks`, `ScheduledMessages`, `Swarm`, `VirtualPartitions`) from `Pro::Routing::Features` to `Pro::Routing::Features::ConsumerGroups` (internal). Agnostic features (`Expiring`, `Filtering`, `Pausing`, `Throttling`) remain at the `Pro::Routing::Features` level.
+- [Enhancement] Introduce polymorphic `Routing::Topic#group` and `Routing::SubscriptionGroup#group` accessors (with `#consumer_group` kept as a backwards-compatible alias), expose `group_id` alongside `consumer_group_id` in `Routing::Topic#to_h`, emit parallel `group:` / `group_id:` keys alongside `consumer_group:` / `consumer_group_id:` in `rebalance.*` payloads, and emit parallel `group_id:` alongside `consumer_group_id:` in `error.occurred` and `statistics.emitted` payloads (these callbacks only carry the group id, not the group object). Prepares routing for additional group types (e.g. KIP-932 share groups); legacy keys remain and will be retired in Karafka 3.0 once share groups land.
+- **[Feature]** Add `Processing::WorkersPool` with dynamic thread pool scaling via `#scale`, `nil` sentinel-based worker exit for downscaling, and `worker.scaling.up`/`worker.scaling.down` instrumentation events.
+- [Enhancement] Add per-partition generation tracking to `AssignmentsTracker` to distinguish first-time assignments from reassignments.
+- [Enhancement] Make liveness listeners fiber-safe.
+- [Fix] Include orphaned node detection in Pro swarm liveness listener.
+- [Fix] Report liveness on `connection.listener.before_fetch_loop` so nodes send an initial healthy report before the first consumption.
+- [Fix] Fire liveness events during `wait_pinging` so nodes continue reporting health status during shutdown with active LRJ jobs.
+- [Maintenance] Use namespaced topic naming format in all integration specs for consistent traceability.
+- [Fix] Fix `DataCollector::SPEC_HASH` producing non-deterministic hashes for pristine and poro specs by passing the original spec path via `KARAFKA_SPEC_PATH` env var.
+- [Fix] Fix swarm supervisor leaking reader pipe file descriptors on node restarts by closing the old reader before creating a new pipe in `Node#start`.
+- [Maintenance] Add `bin/tests_topics_hashes` script for looking up spec files by their topic name hash prefix.
+- [Change] Require `karafka-rdkafka` `>=` `0.27.1` to pick up the fix for `poll_batch` and `poll_batch_nb` raising `RdkafkaError` with only the integer error code, which discarded topic/partition/offset context from `e.details` and caused `partition_eof` handling to call `@buffer.eof(nil, nil)`, resulting in a `TopicNotFoundError` crash.
+- [Fix] Raise `InvalidLicenseTokenError` when a manually-defined `Karafka::License` module is missing required methods (`#token` or `#version`) instead of silently skipping pro component loading, which previously caused confusing `NameError` exceptions later in the boot process.
+- [Enhancement] Bump swarm supervisor `SHUTDOWN_GRACE_PERIOD` from 1s to 15s to give forked nodes enough time to finish post-`shutdown_timeout` cleanup (at_exit handlers, librdkafka finalization, connection pool close) before the supervisor forcefully terminates them, especially on CI where `sleep` granularity and `waitpid` cost stretch each supervision loop iteration.
+- [Maintenance] Fix flaky `pro/admin/recovery/coordinator_for_spec.rb` by warming up the `__consumer_offsets` internal topic with a produce + `seek_consumer_group` and retrying the first `Recovery.coordinator_for` call with exponential backoff on `MetadataError`.
+
 ## 2.5.9 (2026-03-30)
 - [Enhancement] Validate that `statistics.interval.ms` is not zero when dynamic multiplexing is enabled (Pro).
 - [Fix] Fix swarm liveness reporting to also use `on_connection_listener_fetch_loop` so nodes stay alive when `statistics.interval.ms` is disabled.

data/certs/expired.txt

@@ -1,2 +1,85 @@
 # Expired/revoked license checksums (SHA256 of license token)
 # One checksum per line, lines starting with # are comments
+
+01603767339fd25cf874e6fe29315fb27b6f6bbdf2e769c3b88e6efcf4096d37
+024e2c943693c4ea9eea852eb02d32acc9cb34df21aea90af5ab39dcf3b1d8cf
+0371303ba704d8f256b40932aa7840a1adb1cdc6fd032ac902794320d0d35ff1
+051dc2d8176df8d3bde1595e01af786a3f58ccab4cc48743d624e68125d80bd6
+06e3d91c9881ebf9686f3492e53400adc2c6a5fd4a409f6775cd36094b24f181
+0ae8daf74b8ccd6c4828ed707edf0d05df3e7d328e91ddc973e160ae8b120787
+0b4420e202d9c6075bb108ac4bd5917e35e89aa7d1741afaab93ca07839d06fc
+11936f8e0637565a309157d1fd4e84a3c44e5a3f9f226435e7d38bc43e452db6
+122ecfd0493596239995b9e7425046737b4893e28e33f31815eb4727c3f607d9
+17c14c38e10d0d2bd4a9c847a2c23fd0726459337af1d9815b6e34d1fd9af8be
+227f48f0b22974c43f120de28d5ca33a77e58d33064f9a73748501ba700f1474
+24d59b10d982e5642dfda3ec54cd56dda9022927c89584bbe12d31f3df28e17d
+2634761cc75479548003f941346f0a51a6c535415696f386b40ae28f88f63efa
+284967207a93e9c989d05ad6e5bb0dbe3e0a8a871c3fba48324558f127166bda
+2e2b4ccd902e43feb418cc8b3aed5874ec194ae8495ded864aff917538d91f7a
+39aeae710122bf14729a05f24f5bd702d2a1127e5c7fb9bd90de0e20890575dc
+3ada575caaf0b8bdeca0686a93074de9ed830751e6f46251849475f70e84e408
+4367e57ca36a4b447f23745d76611514df61b56611225be4c8f9a90560bbace9
+47380207ca3041b14c7d4c81a69f820852069ecab4d80a068d39133f61a6e641
+4d49b497ece81604358afc8e9adc7d1163995c4c08446bcd5c0bbfe3d7ebc1e7
+4d97c95c46e51105705964aecbfa5219120295e7d0a172f5c098d12c3a5cbf7e
+60171be4b327d48b2445b00f1fca3d2a3554d06c69f63f3e97742b29030a0a69
+630907de3c6bf258bfc2c51d768d51ca446ebd49fb29b29a0b24d363d46d1a6e
+68db4a9700f6cc3494f8eac1e0df2471f11ef7312e7b58dae839b193e226fae5
+6a06fb85cee01a27a5e819e464b0b5fd84051d234540d11774bc17e90c91abd4
+6d79bcac25c0026dad0f1871ccae79fc07d696df2e0f080ce1d1038454545a05
+6e2ed71a0925d59815c49ea1e72dfd0ba28bdbb57f93d81fa34a31c50db53830
+711a3cced55062707b64f6d652e107d0f1318fd9f3762c732fad23d04884cdd2
+71c2d2ab89a11010c41c9938fbc2565297364b4e8378e78ddf58b22ea2c43ca2
+72b19e6e274b1f36799eea65b07f4849db44c82315647266608ebdb6fde0cad6
+731c0d75d9b47cca49d9d95fc8d291fda452383f920e70849373959892443329
+77b6974b96701d82a0670c79830543e345bf0a00d9e5b5a1bbf8443439d75987
+77e461a9a4534870cfb7cca350d56ed0a504643bb39eeb750b338179d05069a9
+7c06718c4314e28561f337b3ecc66fb012c2510f1ed5fcb82dbab5ba009a8f7d
+7ca5a6183ed9c97e4da2c7030f809bfb32da49319d106377bd0e6d7d52734141
+7ce4cade640a4f34e2909360c4c0ceb8a647b7bfead7a57880d8ce2bf6eea26c
+7d3a2cb0ab08f2f25324124973370da30210dab04abaeeed97192576238a03e0
+7dc790fd8bf18e663c2e4276f4362b0c14795945b508807ef03a92ece266cff8
+81e69732cc6e9c5266fffea08fd1c69fd12c1d841b979723a77533c5efef244e
+839f4a449e0d68acccc0f6a2d0209d2d137375d740ae6d0244dde17e63131fbb
+85d26e4fedf364e20ea33c1b0102d34cea19156243fe781ddf597f6677cf2de3
+8609d26341a5c4e908af8b63bcc6895d99d8cc13f0403dc7b36a2920bb8e048a
+8d3e09a94bd00710a49b186be832f74cc3340ec3d87e780e10159e5e8d048b81
+8e933669352c272935c310d7ce798b3ea2687611378b978e412491e7fddfce4d
+8f3190524285a5c0a0d1e24bdc2a5c417416c2cb92b9da26f0e492aaa4600bd7
+9221a49b42e05d39e1939cf9353805abea2042457c2247859e3274976ac2fbc6
+96c8dde1a7f938899f3f5bd764eff295f090e1c40635e7efd25d69ef55881db2
+9b0b791259e86740d4a2cab736802614938b7043479ac8770c570b1b37f38fb7
+a0db6c5e7c8714a2d33adff3b69d2d688d5a34e6d5ba871d1cbdfcba3edf1e89
+a7ce882d45a00ad82e653b60d14f1a1ebefdc9033d6cc60ed0a2ed507949a9a2
+ac2941c112f397543fde83cc1b0dcf70ec34d77e149d3e90ad07a0f1bc809933
+adea773fadaaaeadf0f20643e84ae6c40bcb55fb73ecee5894a41836453e4abb
+b1411e92ad939b59c898e78520c8ec82547950493a45004b747f12820aa7d390
+b3984622fbc6ba91a2180283a6ada7e1bbe01fb705dbaae37c831e9c893b8e00
+b5ed1ff168e86300735e59dc2786be6d535fc9e0f3c6c8a76bc4354cbbed4ae0
+b9e38e9c1b34db847a4b82ae35382b06e61a5872aa8c24f988d7d5246ded4648
+bdc4f155153a59c25c7c52932f77973487d6336e99eb0beeb90edf4a4120a94a
+bf6c5c58b02fa5e7c7dc845213ad943c5b6613f12ac6012be00b1484bb85aa04
+c011c3d168a159c135ef35bf55121edaf1a4cc94f663a1f461595776b0313160
+c311cb6cfb38a8b2e83b3080c1f87444a52f3f645be8337559a123aaacf1344a
+c87222a94f98c3a2191dda9254bd6ed031fd8ca190f75b40c67a0fcd4b56f795
+ca53af70cd7e67abbb9dbf0a8da6788a9b2192aa3a5a1dd8720aaa68a2511722
+d02da0cbd2c1d83432a2cee7984dd311249692373554002d1d543dd5007f6a58
+d13295e597120b88bf4c4f36de63d0aa3e5a68e3578c09a2e026bd1f6aaaf04f
+d862dd776d5b42a73a63574dc00187c587403101cd211ed348fc422f6460844e
+d9f25b56eae6a62b9383c068c2a7c22ef6b051f1cf4137164ba3dd1baf0bac61
+db1f2c50f3dc6956c498b06f67f82412a76f0b138265a55713076b2a4a35725f
+ded7405c91e9bb1994c58c728f83b705fdc5e816ce0cb3fdf16887127fff27f0
+dfe08da10ae5e74e9bbf648261860f3b94201a11ab4269cd4db7c73017452dde
+dff7372b5ee3136af892561507602423bbae42d12d3a65277ae2af1add666723
+e1a040c0c9a6c5e4603d9aebbc4201075238b47446348ab635b53704b3095a63
+e3b94496b65bb626e723637926e729a33be673fe0355d964306bde563ff6fbf7
+e577d74987f1d31c10fc4ec67dd74084486514f844668d7d01bd4cad2d8f09c4
+e7a91a5ce0e68b888026bbddb57c92c7d5ad61e9416c8188721eee0a8ba85bc1
+eda2ab2c99f769d646dd6fff564af9ec6f32e4462390e3b3246bf953cd7a9c70
+f031aa98b2375c6573f6f775f6000dc81e07b1034694742a900a9115eb124900
+f1ade1306fd64c2e32b15e505d87c0a9ec7a8392f5bea014fc4e70acd17f9935
+f397ccd272b6ee7b33595aa93a6e40b725af265b681efca05bb26f9a7766d6c2
+f54723b14f7cfc4e3c88b946cab881b907dd5ac8372b4600213241ab82778979
+f9cc7b7d9c7d81ba477a70749d166edbc2b44f1714096fce10118bb18fd9696c
+fb417a807d7595a4aff44cc79712e9bc887181e64eb9a98fe9f200b585856ae7
+fd5009f463fe0c38cfe66677ff9b8e5031cbc4ce354883c99c392109ae8ae3b8

data/config/locales/errors.yml

@@ -25,22 +25,25 @@ en:
           Decrease max_wait_time or increase node_report_timeout
         kafka_format: needs to be a filled hash
         key_must_be_a_symbol: All keys under the kafka settings scope need to be symbols
+        managed_key_not_supported: >
+          this kafka setting is managed internally by Karafka and should not be set directly.
+          Setting it manually may cause misbehaviours and other unexpected issues
         pause.timeout_max_timeout_vs_pause_max_timeout: pause.timeout must be less or equal to pause.max_timeout
         shutdown_timeout_vs_max_wait_time: shutdown_timeout must be more than max_wait_time
         worker_thread_priority_format: must be between -3 and 3
 
         oauth.token_provider_listener_format: 'must be false or respond to #on_oauthbearer_token_refresh'
 
-        internal.processing.jobs_builder_format: cannot be nil
         internal.processing.jobs_queue_class_format: cannot be nil
         internal.processing.scheduler_class_format: cannot be nil
-        internal.processing.coordinator_class_format: cannot be nil
-        internal.processing.partitioner_class_format: cannot be nil
-        internal.processing.strategy_selector_format: cannot be nil
-        internal.processing.expansions_selector_format: cannot be nil
-        internal.processing.executor_class_format: cannot be nil
         internal.processing.worker_job_call_wrapper_format: 'needs to be false or respond to #wrap'
-        internal.processing.errors_tracker_class_format: 'needs to be nil or a class'
+        internal.processing.consumer_groups.jobs_builder_format: cannot be nil
+        internal.processing.consumer_groups.coordinator_class_format: cannot be nil
+        internal.processing.consumer_groups.errors_tracker_class_format: 'needs to be nil or a class'
+        internal.processing.consumer_groups.partitioner_class_format: cannot be nil
+        internal.processing.consumer_groups.strategy_selector_format: cannot be nil
+        internal.processing.consumer_groups.expansions_selector_format: cannot be nil
+        internal.processing.consumer_groups.executor_class_format: cannot be nil
 
         internal.active_job.dispatcher_format: cannot be nil
         internal.active_job.job_options_contract_format: cannot be nil
@@ -173,6 +176,13 @@ en:
           all topic names within a single consumer group must be unique considering namespacing styles
           disable this validation by setting config.strict_topics_namespacing to false
 
+    declaratives:
+      topic:
+        declaratives.partitions_format: needs to be more or equal to 1
+        declaratives.active_format: needs to be either true or false
+        declaratives.replication_factor_format: needs to be more or equal to 1
+        declaratives.details_format: needs to be a hash with only symbol keys
+
     job_options:
       missing: needs to be present
       dispatch_method_format: needs to be either :produce_async or :produce_sync

data/karafka.gemspec

@@ -21,9 +21,9 @@ Gem::Specification.new do |spec|
     without having to focus on things that are not your business domain.
   DESC
 
-  spec.add_dependency "karafka-core", ">= 2.5.6", "< 2.6.0"
-  spec.add_dependency "karafka-rdkafka", ">= 0.24.0"
-  spec.add_dependency "waterdrop", ">= 2.8.14", "< 3.0.0"
+  spec.add_dependency "karafka-core", ">= 2.6.0", "< 2.7.0"
+  spec.add_dependency "karafka-rdkafka", ">= 0.27.2"
+  spec.add_dependency "waterdrop", ">= 2.10.1", "< 3.0.0"
   spec.add_dependency "zeitwerk", "~> 2.3"
 
   spec.required_ruby_version = ">= 3.2.0"

data/lib/active_job/queue_adapters/karafka_adapter.rb

@@ -28,8 +28,7 @@ module ActiveJob
       Object
     end
 
-    # Karafka adapter for enqueuing jobs
-    # This is here for ease of integration with ActiveJob.
+    # Karafka adapter for enqueuing jobs This is here for ease of integration with ActiveJob.
     class KarafkaAdapter < base
       include ::Karafka::Helpers::ConfigImporter.new(
         dispatcher: %i[internal active_job dispatcher]

data/lib/karafka/active_job/job_extensions.rb

@@ -19,8 +19,7 @@ module Karafka
       def karafka_options(new_options = {})
         return _karafka_options if new_options.empty?
 
-        # Make sure, that karafka options that someone wants to use are valid before assigning
-        # them
+        # Make sure, that karafka options that someone wants to use are valid before assigning them
         App.config.internal.active_job.job_options_contract.validate!(
           new_options,
           scope: %w[active_job]

data/lib/karafka/admin/configs/resource.rb

@@ -76,8 +76,7 @@ module Karafka
 
         private
 
-        # Recognizes whether the type is provided and remaps it to a symbol representation if
-        # needed
+        # Recognizes whether the type is provided and remaps it to a symbol representation if needed
         #
         # @param type [Symbol, Integer]
         # @return [Symbol]