ci / web (pull_request) Successful in 1m23s
ci / docs-site (pull_request) Successful in 1m28s
android / android (pull_request) Successful in 5m0s
apple / swift (pull_request) Successful in 1m20s
apple / screenshots (pull_request) Skipped
ci / rust-arm64 (pull_request) Successful in 6m19s
windows / build (aarch64-pc-windows-msvc) (pull_request) Successful in 1m20s
windows / build (x86_64-pc-windows-msvc) (pull_request) Successful in 2m1s
ci / rust (pull_request) Successful in 12m53s
PRs #25 and #26 are going into this release, and neither was in the notes. Both are user-visible and easy to have lived with without knowing why: force-feedback stopping for good after a controller reconnect (roughly half of reconnects, every platform), and an unplugged pad staying visible to the game for the rest of the session (every time, if it was your only controller). The whatsnew line for the rumble fix is Play listing copy and that file has a 500-character ceiling, so "A decoder hiccup no longer snowballs into a burst of broken frames" loses "snowballs into" for "causes" — same meaning, and the new line is kept short. 498 of 500 used.