Changelog

Celeris releases the client and server packages together. Each useceleris-server release requires a minimum useceleris-client version. Install both with pip install.

1.0.0 — 2026-10-07

This is the first stable release of useceleris-client and useceleris-server. The changes since the betas are:

• create_client() has four new options: reconnect_timeout_ms, publish_queue_size, deduplication_window_size, and maximum_reconnect_attempts.
• Each timeout option accepts from 1 ms to 15 minutes. For a larger value, create_client() raises ConfigurationError.
• maximum_reconnect_attempts sets the reconnect budget: 10 failed attempts by default, from 1 to 100. The betas always used 10.
• channel.events().on_message() receives the messages of all segments of the channel, after the segment listeners.
• A publish during reconnecting waits in the publish queue. In the betas, it raised NotConnected.
• A publish that waits when the connection closes stays in the queue. In the betas, it raised NotConnected.
• After a successful reconnect, the SDK restores your subscriptions. Then it sends the queued publishes in the sequence of the calls.
• The queue limit also applies during a reconnect. A full queue raises Backpressure.
• When recovery stops in failed, each queued publish raises the error that stopped recovery.
• Each connection does its network work on its own thread. A listener that blocks your event loop does not stop the heartbeat pings.
• A presence subscription does not keep a segment. When you cancel the last message subscription, the SDK unsubscribes, also when you hold a presence subscription.
• useceleris-server 1.0.0 requires useceleris-client 1.0.0 or later. Its API does not change.

0.0.0b1 – 0.0.0b3 — 2026-10-03

These beta releases published useceleris-client and useceleris-server on PyPI, for Python 3.10 to 3.14 with asyncio. Version 1.0.0 replaces them. They contained:

• Channels and segments over one WebSocket, publish/subscribe, and presence.
• Replay, automatic recovery with jittered retries, fresh credentials per attempt, and rate-limit resend.
• Payload helpers for text and JSON, plus a codec adapter for your own format.
• A server-side credential signer with least-privilege claims.