moonlet 0.1.31

Apple Silicon build, signed with a Developer ID and notarized by Apple. Installed apps update themselves from Settings › Updates.

Cloud workers, after the first real test

0.1.30's cloud workers have now run on a real Hetzner account. A machine was ready about 50 seconds after the request, ran a heavy command and was removed again. The test turned up these fixes.

• Location and Image are dropdowns, filled from the provider, as Machine type already was. Locations show as "Falkenstein, DE (fsn1)". Images include your Hetzner project's own snapshots, and only those for the picked machine type's architecture (x86 or Arm) are offered.
• Each dropdown waits for the one before it: Machine type until a location is picked, Image until a machine type is. Disabled fields now look disabled.
• Only machine types a location still makes. Hetzner is retiring the cpx11–cpx51 types in Europe, and moonlet still offered them, so making a machine failed with "unsupported location for server type". A saved type that the provider has since retired now shows an error, and the project page asks for another type before saving a changed cloud setting.
• A removed machine leaves your tailnet at once. Its logout was refused before, so a removed machine stayed in the tailnet until Tailscale removed it as an offline ephemeral node. The machine is now allowed exactly that one Tailscale command, nothing more.
• Clearer tailnet policy setup. Settings › Machines › Cloud workers says where each part of the policy goes, and warns when a rule letting everything reach everything would let cloud machines reach your whole tailnet. The snippet now names the central host's real Tailscale address, also when you set it up from another Mac, and shows in full.

Fixes

• A terminal test that failed now and then on CI waits for the output it checks.

Before you update

The protocol has not changed since 0.1.30: Macs, Linux hosts and phones on 0.1.30 keep working with this release. Cloud machines get the moonlet version of the central host that makes them, so update the central host to use the fixes above.