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.
Add 26.9.21 to Releases and move the current version
The release notes for what shipped today: Android reporting real peer
connection states, so a call whose transport died finally ends there;
RestartIce working on all five platforms rather than one, and the
IceRestart offer option that four bindings silently ignored; automatic
recovery of a failed transport on the signalling path; a Windows
sender that can be capped mid-call; the frame sink deadlock and the
Media tile that ignored a changed stream. M153 underneath.
The Apple camera preview delay is written up as a known issue rather
than left for someone to find: it is in this release and fixed after
it.
Current version moved from 26.9.18 across Home, Getting started,
Platform prerequisites, Testing and the feature matrix, whose body was
already written for 26.9.21.
Add 26.9.18 to Releases and bump the current version
One bug across three platforms, filed as several issues: peer connection awaits
resumed on libwebrtc own signalling thread, so a Dispose after an await ran
inside libwebrtc callback and closed the connection a few lines before libwebrtc
used what the close destroyed. EXC_BAD_ACCESS at 0x30 on Apple, a destroyed-mutex
abort on Android, and asynchronous either way so it killed unrelated work.
Also records OnTrack finally firing on Apple, and the -NativeLog switch.
Connection-Signaling said "the release following 26.9.16" in three places for
things that have now shipped; they name 26.9.18.
Release as 26.9.16, today's date
The scheme is the build date and 26.9.17 was tomorrow's. Also corrects the
one sentence a blind replace would have left wrong - the example that maps
the version back to a calendar date.
Co-Authored-By: Claude Opus 5 <noreply@anthropic.com>
Wiki: the five reference pages
Platform prerequisites leads with the three failures that say nothing when
you hit them, symptom first, because that is how a reader arrives.
What works where separates implemented from run. A lot of Apple code was
written on reasoning alone and compiles perfectly, and a matrix that shows
only yes or no would hide exactly that. Two rows were corrected against the
source while writing it: OnDeviceChange is dead on iOS and Mac Catalyst, and
simulcast outside Blazor and Android is unverified rather than working.
Testing carries the real numbers - 114 tests, 2.0s - from a run, not from
counting attributes.
Troubleshooting is organised by what the reader sees, never by which layer
is at fault, since a reader who knew the layer would not need the page.
Releases records what the packages embed and that attribution is the
consumer's to satisfy, and says plainly that NOTICE is empty rather than
letting an empty file read as nothing being required.
Co-Authored-By: Claude Opus 5 <noreply@anthropic.com>