Repository navigation
[REA-6846] Release 3.7.0 with data-channel chunking and step sessions - #240
Merged
Merged
Conversation
New public surface with nothing on the wire moved is a minor release: WebRtcConfig.dc_chunking, which answers clients that ask for chunked data channels, and the step-session surface (starting input and a step count on the start body, complete_step(), the runtime.step_results manifest block and the step folders served over HTTP). Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com> Signed-off-by: Douglas Ferreira <douglaseel@gmail.com>
Contributor
Author
This stack of pull requests is managed by Graphite. Learn more about stacking. |
Dere-Wah
approved these changes
Oct 5, 2026
0.21.0 keeps per-frame metadata on the frame it belongs to when libwebrtc drops a frame before render (it was matched by queue order, so every later frame got its predecessor's metadata), and keeps a FrameTransform's replace_data through the metadata step. 0.20.0 is additive. Neither changes the Python API the runtime uses. Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com> Signed-off-by: Douglas Ferreira <douglaseel@gmail.com>
Contributor
Author
Merge activity
|
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.

Why
Releases what has landed since 3.6.1. It adds new public surface and moves nothing on the wire, which makes it a minor release:
WebRtcConfig.dc_chunkingis on by default. The runtime answers clients that ask for chunked data channels, so a command or a model message of up to 64 MiB passes, instead of being capped at 256 KiB. Refused frames are logged once per channel, and a teardown sends what a chunked channel still has queued. A client that doesn't ask keeps the plain channel.complete_step(), closing a session at its steps, theruntime.step_resultsmanifest block, and step output saved as an MP4 or a folder of files, served over HTTP.FrameTransform'sreplace_datathrough the metadata step.What Changed
Two commits:
uv version 3.7.0, which updates the version inpyproject.tomlanduv.lock;reactor-webrtc==0.21.0, relocked. Only that package moves inuv.lock.Merging tags
v3.7.0and publishes.Checked locally with a locked install of the published reactor-webrtc 0.21.0 wheel:
And with the release workflow's own gates:
mise run http-breaking-release: "3.6.1 -> 3.7.0 (minor) satisfies the mandated patch";mise run wire-check-release: the pin matchesproto/;mise run build: builds the 3.7.0 wheel and sdist.🤖 Generated with Claude Code