/docs/schema/versions/Recent content in Version history on ObserveRTCHugoenCopyright (c) 2020-2024 ThuliteSun, 16 Aug 2026 10:00:00 +0200/docs/schema/versions/v3-3-0/Sun, 09 Aug 2026 10:00:00 +0200/docs/schema/versions/v3-3-0/<div class="callout callout-caution d-flex flex-row mt-4 mb-4 pt-4 pe-4 pb-2 ps-3"> <div class="callout-content"> <div class="callout-title"> <p>Wire-format warning</p> </div> <div class="callout-body"> <p><code>ClientIssue</code> field numbers shift, because protobuf numbering follows sorted field order and <code>key</code> sorts before <code>payload</code>:</p>/docs/schema/versions/v3-2-0/Wed, 18 Mar 2026 10:00:00 +0200/docs/schema/versions/v3-2-0/<p>Entirely additive on the record level: no field was removed or renamed. Several counters were widened from <code>int</code> to <code>long</code>.</p>/docs/schema/versions/v3-1-0/Sun, 01 Jun 2025 10:00:00 +0200/docs/schema/versions/v3-1-0/<p>A small release that touches the encoder and decoder rather than the schema records themselves.</p> <h2 id="changed">Changed</h2> <h3 id="byte-counters-on-outbound-rtp-are-encoded-and-decoded-as-bigint">Byte counters on outbound RTP are encoded and decoded as <code>BigInt</code></h3> <p><code>OutboundRtpEncoder</code> and <code>OutboundRtpDecoder</code> now use <code>NumberToBigIntEncoder</code> and <code>BigIntToNumberDecoder</code> for the bytes-sent and bytes-received fields, so values above <code>Number.MAX_SAFE_INTEGER</code> (2⁵³ − 1) survive a round trip.</p>/docs/schema/versions/v3-0-0/Sun, 01 Jun 2025 10:00:00 +0200/docs/schema/versions/v3-0-0/<p><code>3.0.0</code> was a complete rewrite. It is the baseline every later 3.x release is additive against, and it is <strong>not</strong> compatible with 2.x data or 2.x tooling.</p>