Tailscale
Tailnets become API-provisioned resources while Tailscale hardens SSH and thins the control plane.
◆Recent moves
- 5d ago
Container image v1.102.2: library updates only
The container image ships with no changes beyond library updates, alongside a tsrecorder tweak that stops it indexing empty placeholder recordings on startup. Packaging catch-up to the 1.102.2 client release, with nothing user-facing.
- 8d ago
v1.102.2 fixes a Funnel incoming-connection regression
A single-fix release resolving a regression that broke incoming Tailscale Funnel connections. Fast follow-up to 1.102.1, which is where this cycle's actual feature work landed.
- 9d ago
v1.102.1 adds Services CLI and constant-time node churn
The substantive release of the cycle: new get, whoami and service list CLI commands, Serve inbound and outbound byte metrics for Tailscale Services, and constant-time node addition and removal that measurably cuts CPU on large tailnets. The scaling fix and the Services CLI vocabulary both feed the same direction of tailnets as managed infrastructure.
- 14d ago
Tailnet creation API
⚡ SPARKTailnets stop being org-level constructs an admin sets up once and become objects that can be created and destroyed by API. That is the logical endpoint of the scaling work elsewhere in this window, and it changes who the product is for as much as what it does.
- 15d ago
v1.98.10 backports two Tailscale SSH security fixes
A backport to the 1.98 branch closing two Tailscale SSH issues: Unix socket forwarding now respects symlink permissions, and additional checks reject UIDs and numeric-only usernames. Maintaining security fixes on the older line signals a meaningful install base that has not moved to 1.102.
- 20d ago
Admin console URL change
The admin console moves to console.tailscale.com while authentication stays on login.tailscale.com, with the old admin path redirecting. Cosmetic on the surface, but it separates the console from the auth endpoint, which matters to anyone maintaining allowlists.