Release v19.108.0

Added

• When a kernel node is lost or an append grain call times out while an append is in flight, the append now fails with AppendError.AppendOutcomeUnknown instead of a generic failure. The events may or may not have been stored, so reconcile using the correlation id, or retry with the same idempotency key, rather than retrying blindly. Unit-of-work commits report the same error through GetAppendErrors(). See Appending events. (#5231)

Fixed

• The kernel now closes a client connection whose keep-alive has lapsed, so the client registers again instead of staying attached to a dead connection. (#5240)