rabbitkit 0.14.0__tar.gz → 0.15.0__tar.gz

{rabbitkit-0.14.0/src/rabbitkit.egg-info → rabbitkit-0.15.0}/PKG-INFO

@@ -1,6 +1,6 @@
 Metadata-Version: 2.4
 Name: rabbitkit
-Version: 0.14.0
+Version: 0.15.0
 Summary: Production-grade RabbitMQ toolkit — sync/async, decorator routing, retry, compression, full configurability
 Author-email: Talaat Magdy <talaatmagdy75@gmail.com>
 License-Expression: MIT
@@ -423,9 +423,14 @@ management_client=...)`) verify confirms/mandatory/persistence, a 256 KiB body
 cap, quorum queues and a quorum retry chain — and report anything they cannot
 verify as *unverified*, never green. Retry/DLQ triage headers are sanitized by
 default, and a failing delay-queue handoff backs off instead of hot-looping.
-`CoalescingAcker` is the only place a cumulative `basic.ack(multiple=True)`
-may originate: it knows every delivery on the channel and coalesces only
-through a completed prefix, so a still-running sibling is never acked early.
+`CoalescingAcker` (and `AsyncCoalescingAcker`) is the only place a cumulative
+`basic.ack(multiple=True)` may originate: it knows every delivery on the
+channel and coalesces only through a completed prefix, so a still-running
+sibling is never acked early. Settlement follows a **plan / emit / commit**
+protocol — the ledger advances only for frames the broker actually accepted,
+and emission stops at the first failure, because a cumulative ack that
+follows a nack which never landed would acknowledge the very delivery meant
+to be requeued.
 Every bulk path emits bounded-label metrics
 (`rabbitkit_bulk_publish_items_total{status,reason}`,
 `rabbitkit_settlement_items_total{action,status}`,

{rabbitkit-0.14.0 → rabbitkit-0.15.0}/README.md

@@ -342,9 +342,14 @@ management_client=...)`) verify confirms/mandatory/persistence, a 256 KiB body
 cap, quorum queues and a quorum retry chain — and report anything they cannot
 verify as *unverified*, never green. Retry/DLQ triage headers are sanitized by
 default, and a failing delay-queue handoff backs off instead of hot-looping.
-`CoalescingAcker` is the only place a cumulative `basic.ack(multiple=True)`
-may originate: it knows every delivery on the channel and coalesces only
-through a completed prefix, so a still-running sibling is never acked early.
+`CoalescingAcker` (and `AsyncCoalescingAcker`) is the only place a cumulative
+`basic.ack(multiple=True)` may originate: it knows every delivery on the
+channel and coalesces only through a completed prefix, so a still-running
+sibling is never acked early. Settlement follows a **plan / emit / commit**
+protocol — the ledger advances only for frames the broker actually accepted,
+and emission stops at the first failure, because a cumulative ack that
+follows a nack which never landed would acknowledge the very delivery meant
+to be requeued.
 Every bulk path emits bounded-label metrics
 (`rabbitkit_bulk_publish_items_total{status,reason}`,
 `rabbitkit_settlement_items_total{action,status}`,

{rabbitkit-0.14.0 → rabbitkit-0.15.0}/pyproject.toml

@@ -1,6 +1,6 @@
 [project]
 name = "rabbitkit"
-version = "0.14.0"
+version = "0.15.0"
 description = "Production-grade RabbitMQ toolkit — sync/async, decorator routing, retry, compression, full configurability"
 readme = "README.md"
 license = "MIT"

{rabbitkit-0.14.0 → rabbitkit-0.15.0}/src/rabbitkit/__init__.py

@@ -115,6 +115,7 @@ from rabbitkit.health import (
     broker_readiness,
     broker_readiness_async,
 )
+from rabbitkit.highload.async_acker import AsyncCoalescingAcker
 from rabbitkit.highload.backpressure import FlowController
 from rabbitkit.highload.batch import (
     BatchAcker,
@@ -163,6 +164,7 @@ __all__ = [
     "AsyncAPIGeneratorConfig",
     "AsyncBatchPublisher",
     "AsyncBroker",
+    "AsyncCoalescingAcker",
     "AsyncHealthWatcher",
     "AsyncWorkerPool",
     "BackpressureConfig",

{rabbitkit-0.14.0 → rabbitkit-0.15.0}/src/rabbitkit/_version.py

@@ -1,3 +1,3 @@
 """rabbitkit version — single source of truth."""
 
-__version__ = "0.14.0"
+__version__ = "0.15.0"