Skip to content

Release v19.70.0

Choose a tag to compare

@github-actions github-actions released this 15 Oct 06:25
beccace

A new reactor catches up from the very beginning of the event sequence, and [OnceOnly] does not stop that. A reactor whose handlers cause side effects can now opt out of history with [StartAtTail].

Added

  • [StartAtTail] attribute for .NET reactors. The first time Chronicle sees the reactor, it begins at the tail of the event sequence and observes only what is appended afterwards. A reactor that already has a position keeps it, so the attribute is safe to leave in place. See https://github.com/Cratis/Chronicle/blob/main/Documentation/reactors/start-at-tail.mdx. (part of Cratis/Direct#1875)
  • Optional StartAtTail field on the reactor definition in the gRPC contract. Clients that do not send it behave as before.

Changed

  • Upgrade the Chronicle server before the clients: a server that predates this release ignores StartAtTail and the reactor catches up from the beginning.