Under the hood
CCR client now stamps an acknowledgement timestamp on every event in a batch, not just one
What
When a batch of durable events is successfully sent to the server, the client that handles this (CCR) now loops through all events in the batch and stamps each one with ackedAtMs, the time it was acknowledged. Previously only a single event in the batch was stamped.
Why
This fixes a bug where only one event in a batch would be marked as acknowledged, even though the whole batch succeeded, which could have caused the other events to be treated as unacknowledged.