What probably matters to youSection of the release
What
Every stream event between the start of a reply (message_start) and its end (message_stop) now carries an api_message_id field naming the reply it belongs to. Before, a program reading the stream had to remember the message_start to know which reply later events were part of.
The field is marked internal, and it is not present in Remote Control sessions.
Why
A program that joins a stream partway, or misses a message_start, can still tell which reply each event belongs to. Because the field is marked internal, code that relies on it should be ready for it to change.
