fix: Unity package now ships project runner 3.12.3, which reports MAIN_THREAD_BLOCKED and the stall notice
Merged
HA
1d ago+29+29+01234567890123456789-3-3-0123456789
Summary
- The Unity package docs now describe
uloop statusand what happens when a command meets a blocked main thread. - This
fix:change lets release-please cut Unity package 3.21.3, whose pin carries project runner 3.12.3.
Why this commit exists
- Package 3.21.2 was cut before the project runner 3.12.3 release pull request merged, so its pin still resolves runner 3.12.2.
- Runner 3.12.2 shows the blocked-main-thread fail-fast as
UNITY_RPC_ERRORand prints no stall notice on stderr. - Main already records 3.12.3 in the pin, but release-please opens a package release only after a
fix:orfeat:commit touchesPackages/src. This commit is that change; it touches only the two package docs (no empty commit, noRelease-As).
After merge
- release-please opens
chore(main): release 3.21.3(3.21.2 → 3.21.3). release-please.ymlmerges it automatically.unity-package-releasepublishesv3.21.3withprojectRunnerVersion: 3.12.3in the pin.
Changes
Packages/src/Documentation~/tools.mdandtools_ja.md: a new section 18 forstatus. It lists the states, explains the 30-secondMAIN_THREAD_BLOCKEDfail-fast and the stall notice for commands whose own code blocks the main thread, and shows an example.
Verification
git diff --stat origin/mainshows only the two doc files.- The state names and
SecondsSinceLastMainThreadTickmatch the status skill.