You'll notice
Fixed a bug where session event posting logged the wrong sequence number
What
The internal function that posts session events (SessionsV2Client.postEvents) was reading the sequence_num value from the wrong variable — one that wasn't the actual result returned by the request. It now correctly reads sequence_num from the parsed result.
Why
This fixes incorrect sequence numbers being recorded for session events, which could otherwise throw off anything that relies on events being tracked in the right order.