Tailscale changed its API changelog

===================================================================
--- before
+++ after
@@ -5,8 +5,39 @@
 Updates to the Tailscale client and service.
 
 Subscribe via RSS
 
+AUG 19, 2026
+
+ALL PLATFORMS
+
+ * Go is updated to version 1.26.6.
+ * Tailscale refuses host-scoped IPv4 destinations at every point that acts on an unmapped 4via6 address. This fix addresses a security vulnerability described in TS-2026-011.
+ * When MagicDNS is disabled, unqualified hostnames are correctly forwarded to the configured nameservers.
+ * Resolved an issue where nodes with Tailnet Lock enabled on large tailnets would experience startup failures.
+
+WINDOWS
+
+ * Resolved an issue where the Windows installer would fail during an upgrade when the name of the user's home directory contained a space.
+ * tailscaled returns an error instead of panicking on devices where IPv6 or NetBios over TCP/IP is disabled.
+
+IOS
+
+ * Memory usage is reduced for iOS devices on large tailnets.
+
+TVOS
+
+ * Memory usage is reduced for tvOS devices on large tailnets.
+
+A new release of the Tailscale container image is available. You can download it from Docker Hub or from our GitHub packages repository.
+
+ * The container waits longer for its initial connection to the coordination server when you set the new TS_BOOT_TIMEOUT environment variable. It accepts a duration, such as 90s or 3m, and defaults to 60s.
+
+A new release of the Tailscale Kubernetes Operator is available. For guidance on installing and updating, refer to our installation instructions.
+
+ * Peer relays on AWS are reachable regardless of the availability zone their pod is scheduled in. Pinning Elastic IPs also requires pinning the pods to the same zone using a ProxyClass.
+ * Network Load Balancers fronting peer relays on AWS use HTTP instead of TCP for pod health checks. Peer relays listen only on UDP, so the default TCP health check could never succeed, causing every target to be reported as unhealthy.
+
 AUG 18, 2026
 
  * The list tailnets endpoint paginates results. By default, organizations with more than 100 tailnets now receive only the first 100 results, with totalCount and cursor parameters to retrieve additional results.
  * limit and cursor query parameters are supported on the list tailnets endpoint. If no limit is specified, the endpoint returns 100 results per page. Use the returned cursor value as the next request's cursor parameter to retrieve the next page until the returned cursor value is empty.