rabbitkit 0.19.0__tar.gz → 0.20.0__tar.gz

{rabbitkit-0.19.0/src/rabbitkit.egg-info → rabbitkit-0.20.0}/PKG-INFO

@@ -1,6 +1,6 @@
 Metadata-Version: 2.4
 Name: rabbitkit
-Version: 0.19.0
+Version: 0.20.0
 Summary: Production-grade RabbitMQ toolkit — sync/async, decorator routing, retry, compression, full configurability
 Author-email: Talaat Magdy <talaatmagdy75@gmail.com>
 License-Expression: MIT
@@ -258,9 +258,12 @@ async def publish_order() -> None:
     outcome.raise_for_status()
 ```
 
-A publish can be `CONFIRMED`, `SENT`, `RETURNED`, `NACKED`, `TIMEOUT`, or
-`ERROR`. Application code can treat those as different states instead of
-assuming "publish called" means "message safe".
+A publish can be `CONFIRMED`, `SENT`, `RETURNED`, `NACKED`, `NOT_SENT`
+(definitely never left the client: safe to publish again), `UNKNOWN` or
+`TIMEOUT` (may have reached the broker: publish again only with the same
+`message_id`), or `ERROR`. `outcome.reason` says why. Application code can
+treat those as different states instead of assuming "publish called" means
+"message safe".
 
 ### 3. Add retry and DLQ handling
 
@@ -291,7 +294,11 @@ orders.created
 Transient failures retry with backoff. Permanent failures skip the ladder
 and go straight to the DLQ. By default, rejected messages do not disappear
 silently — every rejecting route gets a DLQ unless you explicitly opt into
-discard behavior.
+discard behavior. A terminal failure reaches the DLQ as a broker-confirmed
+copy carrying the final attempt's error class, sanitized message, failure
+category, attempt count, timestamps and original queue/exchange/routing key;
+`RetryConfig.max_retry_age` bounds the total retry time and
+`RetryConfig.exponential(...)` builds the delay ladder.
 
 ### 4. Test it without RabbitMQ
 
@@ -420,8 +427,11 @@ def commit_batch(successful: list[RabbitMessage], failed: list[RabbitMessage]) -
 
 Opt-in **reliability profiles** (`critical_config()`, `broker.preflight("critical",
 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
+cap, bounded in-flight publish bytes, quorum queues with at-least-once
+dead-lettering, a quorum retry chain with a metadata-stamped DLQ copy, a
+required processing deadline and no `ACK_FIRST` — and report anything they
+cannot verify as *unverified*, never green
+([reliable messaging contract](docs/reliable-messaging.md)). Retry/DLQ triage headers are sanitized by
 default, and a failing delay-queue handoff backs off instead of hot-looping.
 `CoalescingAcker` (and `AsyncCoalescingAcker`) is the only place a cumulative
 `basic.ack(multiple=True)` may originate: it knows every delivery on the
@@ -475,9 +485,13 @@ duplicates). The rule is simple:
 | Handler raises forever | Retry ladder, then DLQ |
 | Malformed payload | Classified permanent, preserved in DLQ |
 | Reject with no DLX | Safe default auto-provisions a DLQ — no silent discard |
-| Retry publish times out | Original is **not** acked as if the retry succeeded |
+| Retry publish times out | Original is **not** acked as if the retry succeeded; the delivery is held for a capped backoff before it is requeued, so it cannot hot-loop |
+| Handler raises `AckMessage`/`RejectMessage` | Settled exactly as asked — never retried |
+| Result publish fails after dedup | The redelivery is processed again, not acked as a duplicate |
+| Infrastructure-managed topology | `TopologyMode.PASSIVE_ONLY` performs no writes; `broker.verify_topology(management_client)` detects type/argument/binding drift |
 | DLQ replay publish fails | DLQ message is **not** removed as if replay succeeded |
 | Message unroutable | Mandatory publishing returns a distinct `RETURNED` outcome |
+| Oversized delivery (`ConsumerConfig.max_body_bytes`) | Dead-lettered as `invalid_message` before any middleware or the handler runs |
 | Broker blips | Readiness changes; liveness does **not** kill the pod |
 | Pod gets SIGTERM | Consumers stop first, in-flight work drains |
 | CI has no RabbitMQ | `TestBroker` runs the real pipeline in memory |
@@ -489,8 +503,8 @@ Settlement is a decision, not a side effect hidden in a callback.
 
 | Policy | Behavior | Use case |
 |---|---|---|
-| `AUTO` | Ack on success, retry/reject on failure | Most consumers |
-| `MANUAL` | Handler owns ack/nack/reject | Custom settlement flows |
+| `AUTO` | Ack on success, retry/reject on failure (without retry: a transient failure is requeued once, then dead-lettered) | Most consumers |
+| `MANUAL` | Handler owns ack/nack/reject; if it raises without settling, the `AUTO` failure settlement applies | Custom settlement flows |
 | `NACK_ON_ERROR` | Ack on success, nack on failure | Never silently accept failed work |
 | `ACK_FIRST` | Ack before the handler runs | At-most-once workloads |
 
@@ -511,14 +525,22 @@ handlers. Migrating existing classic queues to quorum? There's a tool:
 ## Observability
 
 Structured logs carry message context (`message_id`, `correlation_id`,
-routing, queue, handler, retry count, settlement, duration, error type) with
-secret redaction on by default. Metrics cover consumed/acked/nacked/
+routing, queue, handler, retry count, settlement, duration, error type) and
+redact secrets once logging is configured
+(`RabbitConfig(logging=LoggingConfig())`; redaction is opt-in). Metrics cover consumed/acked/nacked/
 retried/dead-lettered counts, publish outcomes, handler latency,
 redeliveries, reconnects, confirm latency, in-flight handlers, broker/consumer
 lifecycle gauges, bulk-publish and settlement outcomes, retry-handoff
-failures, and — via the management API poller — queue depth and consumer lag. Tracing is standard OpenTelemetry
+failures, resource alarms by cause (disk or memory, from `connection.blocked`), and — via the management API
+poller — queue depth, consumer lag and quorum-queue member health. Tracing is standard OpenTelemetry
 (`pip install rabbitkit[otel]`): W3C context propagation over AMQP headers,
-one continuous trace from publish to consume.
+one continuous trace from publish to consume. Prometheus alert rules with
+`promtool` tests ship in `deploy/prometheus/rabbitkit-alerts.yaml`, each linked
+to a runbook in `docs/runbooks/` and each threshold explained; they need only
+rabbitkit's own metrics (the broker's `rabbitmq_prometheus` plugin is an
+optional alternative group). For the full reliability contract (publish
+outcomes, settlement, failure taxonomy, durability scope) see
+`docs/reliable-messaging.md`.
 
 ## Advanced & experimental
 
@@ -528,12 +550,16 @@ with per-item outcomes, safe ack coalescing (`CoalescingAcker`), reliability
 profiles + `preflight`, pipelined sync confirms (`SyncBatchPublisher`), DLQ inspector + replay CLI, management API client,
 topology validation/drift/migration CLI, health watcher, circuit-breaker
 middleware (bring any `CircuitBreakerProtocol` implementation, e.g.
-pybreaker).
+pybreaker), and RabbitMQ streams: `subscriber(stream_offset="first")` on a
+`QueueType.STREAM` queue, per-delivery `message.stream_offset`, retention
+options, and an `OffsetStore` protocol (in-memory by default; plug in your
+own storage) so restarts and reconnects resume where they left off (at-least-once; no retry/DLQ on streams). See
+[Streams](https://github.com/talaatmagdyx/rabbitkit/blob/main/docs/streams.md).
 
 **Experimental** (may change without a deprecation cycle — read the
 [stability policy](https://github.com/talaatmagdyx/rabbitkit/blob/main/docs/stability-policy.md)): RPC over direct reply-to,
-distributed locking, message signing, result backends, stream queues, the
-monitoring dashboard. Notable caveats: the default signing nonce cache is
+distributed locking, message signing, result backends, the monitoring
+dashboard. Notable caveats: the default signing nonce cache is
 per-process (use a shared cache for real replay protection), and never
 expose the dashboard publicly without authentication.
 
@@ -594,7 +620,9 @@ rabbitkit health myapp.main:broker
 ```
 
 The DLQ replay acks a message only after its republish is broker-confirmed —
-the recovery tool cannot itself lose messages.
+the recovery tool cannot itself lose messages. Every replay is audit-logged
+and stamps `x-rabbitkit-replay-count`; a message replayed 3 times is refused
+unless you pass `--ignore-replay-limit`.
 
 <p align="center"><img src="https://raw.githubusercontent.com/talaatmagdyx/rabbitkit/main/assets/demo.svg" alt="rabbitkit dlq inspect and replay demo" width="720"></p>
 
@@ -735,6 +763,8 @@ Python ≥ 3.11 (tested: 3.11 / 3.12 / 3.13 / 3.14; 3.15 pre-release experimenta
 - [Full Guide](https://github.com/talaatmagdyx/rabbitkit/blob/main/docs/guide/full-guide.md)
 - [Message Safety](https://github.com/talaatmagdyx/rabbitkit/blob/main/docs/message-safety.md)
 - [Retry & DLQ](https://github.com/talaatmagdyx/rabbitkit/blob/main/docs/retry-and-dlq.md)
+- [Reliable Messaging — contract & CRITICAL profile](https://github.com/talaatmagdyx/rabbitkit/blob/main/docs/reliable-messaging.md)
+- [Streams — offsets, replay, retention](https://github.com/talaatmagdyx/rabbitkit/blob/main/docs/streams.md)
 - [Production Patterns — reference code](https://github.com/talaatmagdyx/rabbitkit/blob/main/docs/production/patterns.md)
 - [Scale & Reliability Handbook — millions of messages](https://github.com/talaatmagdyx/rabbitkit/blob/main/docs/production/scale.md)
 - [Production Checklist](https://github.com/talaatmagdyx/rabbitkit/blob/main/docs/production/checklist.md)

{rabbitkit-0.19.0 → rabbitkit-0.20.0}/README.md

@@ -177,9 +177,12 @@ async def publish_order() -> None:
     outcome.raise_for_status()
 ```
 
-A publish can be `CONFIRMED`, `SENT`, `RETURNED`, `NACKED`, `TIMEOUT`, or
-`ERROR`. Application code can treat those as different states instead of
-assuming "publish called" means "message safe".
+A publish can be `CONFIRMED`, `SENT`, `RETURNED`, `NACKED`, `NOT_SENT`
+(definitely never left the client: safe to publish again), `UNKNOWN` or
+`TIMEOUT` (may have reached the broker: publish again only with the same
+`message_id`), or `ERROR`. `outcome.reason` says why. Application code can
+treat those as different states instead of assuming "publish called" means
+"message safe".
 
 ### 3. Add retry and DLQ handling
 
@@ -210,7 +213,11 @@ orders.created
 Transient failures retry with backoff. Permanent failures skip the ladder
 and go straight to the DLQ. By default, rejected messages do not disappear
 silently — every rejecting route gets a DLQ unless you explicitly opt into
-discard behavior.
+discard behavior. A terminal failure reaches the DLQ as a broker-confirmed
+copy carrying the final attempt's error class, sanitized message, failure
+category, attempt count, timestamps and original queue/exchange/routing key;
+`RetryConfig.max_retry_age` bounds the total retry time and
+`RetryConfig.exponential(...)` builds the delay ladder.
 
 ### 4. Test it without RabbitMQ
 
@@ -339,8 +346,11 @@ def commit_batch(successful: list[RabbitMessage], failed: list[RabbitMessage]) -
 
 Opt-in **reliability profiles** (`critical_config()`, `broker.preflight("critical",
 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
+cap, bounded in-flight publish bytes, quorum queues with at-least-once
+dead-lettering, a quorum retry chain with a metadata-stamped DLQ copy, a
+required processing deadline and no `ACK_FIRST` — and report anything they
+cannot verify as *unverified*, never green
+([reliable messaging contract](docs/reliable-messaging.md)). Retry/DLQ triage headers are sanitized by
 default, and a failing delay-queue handoff backs off instead of hot-looping.
 `CoalescingAcker` (and `AsyncCoalescingAcker`) is the only place a cumulative
 `basic.ack(multiple=True)` may originate: it knows every delivery on the
@@ -394,9 +404,13 @@ duplicates). The rule is simple:
 | Handler raises forever | Retry ladder, then DLQ |
 | Malformed payload | Classified permanent, preserved in DLQ |
 | Reject with no DLX | Safe default auto-provisions a DLQ — no silent discard |
-| Retry publish times out | Original is **not** acked as if the retry succeeded |
+| Retry publish times out | Original is **not** acked as if the retry succeeded; the delivery is held for a capped backoff before it is requeued, so it cannot hot-loop |
+| Handler raises `AckMessage`/`RejectMessage` | Settled exactly as asked — never retried |
+| Result publish fails after dedup | The redelivery is processed again, not acked as a duplicate |
+| Infrastructure-managed topology | `TopologyMode.PASSIVE_ONLY` performs no writes; `broker.verify_topology(management_client)` detects type/argument/binding drift |
 | DLQ replay publish fails | DLQ message is **not** removed as if replay succeeded |
 | Message unroutable | Mandatory publishing returns a distinct `RETURNED` outcome |
+| Oversized delivery (`ConsumerConfig.max_body_bytes`) | Dead-lettered as `invalid_message` before any middleware or the handler runs |
 | Broker blips | Readiness changes; liveness does **not** kill the pod |
 | Pod gets SIGTERM | Consumers stop first, in-flight work drains |
 | CI has no RabbitMQ | `TestBroker` runs the real pipeline in memory |
@@ -408,8 +422,8 @@ Settlement is a decision, not a side effect hidden in a callback.
 
 | Policy | Behavior | Use case |
 |---|---|---|
-| `AUTO` | Ack on success, retry/reject on failure | Most consumers |
-| `MANUAL` | Handler owns ack/nack/reject | Custom settlement flows |
+| `AUTO` | Ack on success, retry/reject on failure (without retry: a transient failure is requeued once, then dead-lettered) | Most consumers |
+| `MANUAL` | Handler owns ack/nack/reject; if it raises without settling, the `AUTO` failure settlement applies | Custom settlement flows |
 | `NACK_ON_ERROR` | Ack on success, nack on failure | Never silently accept failed work |
 | `ACK_FIRST` | Ack before the handler runs | At-most-once workloads |
 
@@ -430,14 +444,22 @@ handlers. Migrating existing classic queues to quorum? There's a tool:
 ## Observability
 
 Structured logs carry message context (`message_id`, `correlation_id`,
-routing, queue, handler, retry count, settlement, duration, error type) with
-secret redaction on by default. Metrics cover consumed/acked/nacked/
+routing, queue, handler, retry count, settlement, duration, error type) and
+redact secrets once logging is configured
+(`RabbitConfig(logging=LoggingConfig())`; redaction is opt-in). Metrics cover consumed/acked/nacked/
 retried/dead-lettered counts, publish outcomes, handler latency,
 redeliveries, reconnects, confirm latency, in-flight handlers, broker/consumer
 lifecycle gauges, bulk-publish and settlement outcomes, retry-handoff
-failures, and — via the management API poller — queue depth and consumer lag. Tracing is standard OpenTelemetry
+failures, resource alarms by cause (disk or memory, from `connection.blocked`), and — via the management API
+poller — queue depth, consumer lag and quorum-queue member health. Tracing is standard OpenTelemetry
 (`pip install rabbitkit[otel]`): W3C context propagation over AMQP headers,
-one continuous trace from publish to consume.
+one continuous trace from publish to consume. Prometheus alert rules with
+`promtool` tests ship in `deploy/prometheus/rabbitkit-alerts.yaml`, each linked
+to a runbook in `docs/runbooks/` and each threshold explained; they need only
+rabbitkit's own metrics (the broker's `rabbitmq_prometheus` plugin is an
+optional alternative group). For the full reliability contract (publish
+outcomes, settlement, failure taxonomy, durability scope) see
+`docs/reliable-messaging.md`.
 
 ## Advanced & experimental
 
@@ -447,12 +469,16 @@ with per-item outcomes, safe ack coalescing (`CoalescingAcker`), reliability
 profiles + `preflight`, pipelined sync confirms (`SyncBatchPublisher`), DLQ inspector + replay CLI, management API client,
 topology validation/drift/migration CLI, health watcher, circuit-breaker
 middleware (bring any `CircuitBreakerProtocol` implementation, e.g.
-pybreaker).
+pybreaker), and RabbitMQ streams: `subscriber(stream_offset="first")` on a
+`QueueType.STREAM` queue, per-delivery `message.stream_offset`, retention
+options, and an `OffsetStore` protocol (in-memory by default; plug in your
+own storage) so restarts and reconnects resume where they left off (at-least-once; no retry/DLQ on streams). See
+[Streams](https://github.com/talaatmagdyx/rabbitkit/blob/main/docs/streams.md).
 
 **Experimental** (may change without a deprecation cycle — read the
 [stability policy](https://github.com/talaatmagdyx/rabbitkit/blob/main/docs/stability-policy.md)): RPC over direct reply-to,
-distributed locking, message signing, result backends, stream queues, the
-monitoring dashboard. Notable caveats: the default signing nonce cache is
+distributed locking, message signing, result backends, the monitoring
+dashboard. Notable caveats: the default signing nonce cache is
 per-process (use a shared cache for real replay protection), and never
 expose the dashboard publicly without authentication.
 
@@ -513,7 +539,9 @@ rabbitkit health myapp.main:broker
 ```
 
 The DLQ replay acks a message only after its republish is broker-confirmed —
-the recovery tool cannot itself lose messages.
+the recovery tool cannot itself lose messages. Every replay is audit-logged
+and stamps `x-rabbitkit-replay-count`; a message replayed 3 times is refused
+unless you pass `--ignore-replay-limit`.
 
 <p align="center"><img src="https://raw.githubusercontent.com/talaatmagdyx/rabbitkit/main/assets/demo.svg" alt="rabbitkit dlq inspect and replay demo" width="720"></p>
 
@@ -654,6 +682,8 @@ Python ≥ 3.11 (tested: 3.11 / 3.12 / 3.13 / 3.14; 3.15 pre-release experimenta
 - [Full Guide](https://github.com/talaatmagdyx/rabbitkit/blob/main/docs/guide/full-guide.md)
 - [Message Safety](https://github.com/talaatmagdyx/rabbitkit/blob/main/docs/message-safety.md)
 - [Retry & DLQ](https://github.com/talaatmagdyx/rabbitkit/blob/main/docs/retry-and-dlq.md)
+- [Reliable Messaging — contract & CRITICAL profile](https://github.com/talaatmagdyx/rabbitkit/blob/main/docs/reliable-messaging.md)
+- [Streams — offsets, replay, retention](https://github.com/talaatmagdyx/rabbitkit/blob/main/docs/streams.md)
 - [Production Patterns — reference code](https://github.com/talaatmagdyx/rabbitkit/blob/main/docs/production/patterns.md)
 - [Scale & Reliability Handbook — millions of messages](https://github.com/talaatmagdyx/rabbitkit/blob/main/docs/production/scale.md)
 - [Production Checklist](https://github.com/talaatmagdyx/rabbitkit/blob/main/docs/production/checklist.md)

{rabbitkit-0.19.0 → rabbitkit-0.20.0}/pyproject.toml

@@ -1,6 +1,6 @@
 [project]
 name = "rabbitkit"
-version = "0.19.0"
+version = "0.20.0"
 description = "Production-grade RabbitMQ toolkit — sync/async, decorator routing, retry, compression, full configurability"
 readme = "README.md"
 license = "MIT"
@@ -153,7 +153,10 @@ warn_unused_configs = true
 [tool.pytest.ini_options]
 asyncio_mode = "auto"
 testpaths = ["tests"]
-markers = ["integration: integration tests (may need RabbitMQ)"]
+markers = [
+    "integration: integration tests (may need RabbitMQ)",
+    "cluster_chaos: slow multi-container failure tests (3-node cluster, toxiproxy); nightly only, not part of -m integration",
+]
 filterwarnings = [
     # rabbitkit's own operator-guidance warnings, exercised deliberately by
     # tests (dedicated pytest.warns tests still assert they fire — pytest.warns

{rabbitkit-0.19.0 → rabbitkit-0.20.0}/src/rabbitkit/__init__.py

@@ -38,16 +38,27 @@ from rabbitkit.core.config import (
     WorkerConfig,
 )
 from rabbitkit.core.errors import (
+    AuthenticationFailedError,
     BackpressureError,
     BrokerNotStartedError,
     ConfigurationError,
     ConfigValidationError,
+    DLQOperationDeniedError,
+    HandlerTimeoutError,
+    InboundMessageTooLargeError,
+    InfrastructureError,
+    InvalidMessageError,
     MessageTooLargeError,
     MissingDependencyError,
+    PermanentConnectionError,
+    ReconnectBudgetExhaustedError,
     SettlementError,
+    TerminalConnectionError,
+    TLSVerificationError,
     TopologyValidationError,
     UnsafeToBrowseError,
     UnsafeTopologyError,
+    VhostAccessRefusedError,
 )
 from rabbitkit.core.logging import DEFAULT_REDACT_KEYS, LoggingConfig, configure_structlog
 from rabbitkit.core.message import AckMessage, NackMessage, RabbitMessage, RejectMessage
@@ -79,30 +90,36 @@ from rabbitkit.core.settlement import (
     UnknownDeliveryError,
 )
 from rabbitkit.core.topology import RabbitExchange, RabbitQueue
+from rabbitkit.core.topology_validation import TopologyFinding, TopologyReport, verify_topology
 from rabbitkit.core.types import (
     AckPolicy,
     BulkPublishStatus,
     ClassifiedError,
+    DeadLetterStrategy,
     DeduplicationMarkPolicy,
     DeliveryState,
+    ErrorCategory,
     ErrorSeverity,
     ExchangeType,
+    FailureCategory,
     FlushReason,
     HandoffState,
     MessageEnvelope,
     PreflightStatus,
     PublishOutcome,
+    PublishReason,
     PublishStatus,
     QueueType,
     RejectWithoutDLXPolicy,
     ReliabilityProfile,
     SettlementAction,
     SettlementItemStatus,
+    TerminalAction,
     TopologyMode,
 )
 from rabbitkit.di import Context, ContextRepo, Depends, DIResolver, Header, Path
 from rabbitkit.di.resolver import DependencyScope
-from rabbitkit.dlq import DLQInspector, ReplayResult
+from rabbitkit.dlq import DLQInspector, ReplayRequest, ReplayResult
 from rabbitkit.fastapi import rabbitkit_lifespan
 from rabbitkit.health import (
     AsyncHealthWatcher,
@@ -153,6 +170,13 @@ from rabbitkit.serialization.pipeline import (
     RawDecoder,
     SerializationPipeline,
 )
+from rabbitkit.streams import (
+    InMemoryOffsetStore,
+    OffsetStore,
+    StreamConsumerConfig,
+    StreamOffset,
+    StreamOffsetType,
+)
 from rabbitkit.sync.batch import SyncBatchPublisher
 from rabbitkit.sync.broker import SyncBroker
 
@@ -168,6 +192,7 @@ __all__ = [
     "AsyncCoalescingAcker",
     "AsyncHealthWatcher",
     "AsyncWorkerPool",
+    "AuthenticationFailedError",
     "BackpressureConfig",
     "BackpressureError",
     "BatchAckConfig",
@@ -201,26 +226,35 @@ __all__ = [
     "CoordinatorError",
     "DIResolver",
     "DLQInspector",
+    "DLQOperationDeniedError",
     "DataclassDecoder",
+    "DeadLetterStrategy",
     "DeduplicationConfig",
     "DeduplicationMarkPolicy",
     "DeduplicationMiddleware",
     "DeliveryState",
     "DependencyScope",
     "Depends",
+    "ErrorCategory",
     "ErrorSanitizer",
     "ErrorSeverity",
     "ExchangeType",
+    "FailureCategory",
     "FlowController",
     "FlushItem",
     "FlushReason",
     "FlushReport",
     "GroupFlushReport",
+    "HandlerTimeoutError",
     "HandoffState",
     "Header",
     "HealthCheckConfig",
     "HealthStatus",
     "HealthWatcher",
+    "InMemoryOffsetStore",
+    "InboundMessageTooLargeError",
+    "InfrastructureError",
+    "InvalidMessageError",
     "JsonParser",
     "LedgerFullError",
     "LoggingConfig",
@@ -235,7 +269,9 @@ __all__ = [
     "MissingDependencyError",
     "NackMessage",
     "OTelTracingMiddleware",
+    "OffsetStore",
     "Path",
+    "PermanentConnectionError",
     "PolicyTemplate",
     "PoolConfig",
     "PreflightCheck",
@@ -245,6 +281,7 @@ __all__ = [
     "PrometheusCollector",
     "PublishOutcome",
     "PublishPreparer",
+    "PublishReason",
     "PublishStatus",
     "PublisherConfig",
     "PydanticDecoder",
@@ -260,9 +297,11 @@ __all__ = [
     "RateLimitConfig",
     "RateLimitMiddleware",
     "RawDecoder",
+    "ReconnectBudgetExhaustedError",
     "RejectMessage",
     "RejectWithoutDLXPolicy",
     "ReliabilityProfile",
+    "ReplayRequest",
     "ReplayResult",
     "RetryConfig",
     "RetryDisabled",
@@ -283,14 +322,23 @@ __all__ = [
     "SettlementReportError",
     "SocketConfig",
     "StaleGenerationError",
+    "StreamConsumerConfig",
+    "StreamOffset",
+    "StreamOffsetType",
     "SyncBatchPublisher",
     "SyncBroker",
     "SyncWorkerPool",
+    "TLSVerificationError",
+    "TerminalAction",
+    "TerminalConnectionError",
+    "TopologyFinding",
     "TopologyMode",
+    "TopologyReport",
     "TopologyValidationError",
     "UnknownDeliveryError",
     "UnsafeToBrowseError",
     "UnsafeTopologyError",
+    "VhostAccessRefusedError",
     "WorkerConfig",
     "__version__",
     "apply_profile",
@@ -312,4 +360,5 @@ __all__ = [
     "standard_config",
     "start_metrics_server",
     "validate_profile",
+    "verify_topology",
 ]

{rabbitkit-0.19.0 → rabbitkit-0.20.0}/src/rabbitkit/_version.py

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