Thanks for noting this! Somehow I’d missed the report in the other topic.
The problem with the version check should now be fixed. Our version-check API now returns ‘out of date’ responses for 3.6.0.beta3-latest.
(the problem is that 3.6.0.beta3 was never actually released, because we renamed it to 2025.11.0)