Bring Releases up to 26.11.2, and the MAUI pin to 10.0.120
The page still called 26.9.21 current, with an "Unreleased - fixed on master"
section, although 26.9.29, 26.10.25, 26.10.26 and 26.10.28 had all shipped.
- 26.11.2: the three advisories cleared (SignalR.Common high, SignalR MessagePack
protocol, MessagePack), every dependency updated, and the MAUI 10.0.120 step.
- 26.10.25 to 26.10.28: the Windows ReplaceTrack, transceiver release (#50), tile
sizing and track Enabled fixes, and the Android foreground-service crash.
- 26.9.29: the old Unreleased section, attributed to the release that shipped it.
It was published by manual dispatch, so it has no tag; the attribution comes
from the commit that was published, not from tag ancestry, which would have
credited all of it to 26.10.25.
MAUI 10.0.120 in Getting started, Platform prerequisites, Troubleshooting and
Releases, and the current version on six pages. "Since/before 26.9.21" history
is left as written, as is the 2.0.0 summary line naming MAUI 10.0.101.
How a release is cut: publish.yml now creates the GitHub release from the
annotated tag's message, so the notes belong in the tag.
What is fixed on master since 26.9.21, and what 26.9.21 users should know
Releases gains an Unreleased section. It opens with the known issues in
26.9.21:
- Apple sends video only on the first call and never turns the camera off.
- MAUI error dialogs hang up the call.
- A join can silently never connect.
- Closing a call on Apple's UI thread can freeze the app.
It then gives the fixes, and what an application will notice when they
ship. What works where points to it. Middleware now describes the native
MAUI dialogs and VideoMuted's move to the observable side.
Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
Wiki: the seven stack pages
One page per layer, bottom to top, each ending in a pointer to the next:
WebRTCnative, Bindings, The unified API, Middleware, Connection and its two
implementations, and the demo apps.
The unified API page is named for what it is rather than for the package,
because a sidebar with WebRTCme nested under WebRTCme reads as a mistake.
Connection is split three ways. One page covering two topologies, two server
deployments and two sequence diagrams would have been six hundred lines, and
the two implementations have almost nothing in common below IConnection.
Twelve mermaid diagrams, all parsed and rendered under the strict security
level GitHub uses before being committed. Mermaid rather than SVG pairs: it
themes itself for dark mode and stays editable in place.
Connection-Signaling records that the server's tracked appsettings.json
carries a real Xirsys credential, because a reader who forks this needs to
know not to rely on it.
Co-Authored-By: Claude Opus 5 <noreply@anthropic.com>