Bloks 2.5.12
Bloks Cloud recovers on its own after a re-activation
- Cloud follows a re-activation. If you run the app and a headless
bloks-serveron the same computer, activating Cloud in one of them used to leave the other knocking on a retired space until you restarted it. Now it picks up the new tokens and reconnects by itself. (Running just one of the two is still the better setup.) - Clearer Cloud errors. When Bloks Cloud no longer recognises your computer, usually because Cloud was activated again with the same licence, the status and the pairing page now say so, instead of "That link was already used or has expired".
- The engine banner can be dismissed. Every "isn't signed in" or "isn't ready" banner now has a close button. OpenCode is no longer reported as signed out when it's answering on its free models with no provider connected. (#103)
- Dependency updates. Analytics and type packages are up to date. (#104, #105)