Releasesby Glyphtailscale 1.96.4
Please refer to the changelog available at https://tailscale.com/changelog
Also shipped Mar 27, 2026Tailscale in March 2026 →
Deploy from Codex with the Netlify Plugin
You can now deploy sites to Netlify directly from OpenAI Codex using the Netlify plugin in the Codex plugin directory. Netlify plugin in Codex Codex plugins extend Codex with apps, skills, and MCP servers, to access external tools, data, and workflows directly from your coding environment.
Rolling out selective 4-bit weight-only quantization for supported models, targeting non-sensitive layers...
Rolling out selective 4-bit weight-only quantization for supported models, targeting non-sensitive layers while preserving full precision for sensitive layers, in line with industry standards. Learn more in Supported Models.
Qdrant 1.17.1
Change log Improvements milestone#46 - Defer point updates, efficiently apply and optimize points with prevent_unoptimized=true #8188 - Make Gridstore flushes non-blocking to reduce search tail latencies #8235 - Improve performance of filtered search in case of singular payload value #8402 - Add request tracing ID into audit log #8460 - Propagate WAL errors...
Cache prewarm, Stripe Projects integration, Neon Auth webhooks with Resend, and more release - Mar 27, 2026
Neon Postgres in Stripe Projects. Neon is now part of Stripe Projects. Stripe Projects is a Stripe CLI workflow for hooking an app up to backends. You pick serv...
What's new in Sigma
Admin Support for Azure customer-owned cloud storage integration Admins can now add an Azure Blob Storage integration to use customer-owned cloud storage with the following features: CSV upload File upload column in input tables Export to cloud storage This adds Azure to the existing AWS and GCP storage options that give your organization control over where...
Workers - New RFC 9440 mTLS certificate fields in Workers
Four new fields are now available on request.cf.tlsClientAuth in Workers for requests that include a mutual TLS (mTLS) client certificate. These fields encode the client certificate and its intermediate chain in RFC 9440 ↗ format , the same standard format used by the Client-Cert and Client-Cert-Chain HTTP headers , so your Worker can forward them directly...
More from TailscaleEvery Tailscale release →
Tailscale v1.96.4
Linux Fixed: An issue on forks of Linux caused by fallback-on-ENOSYS logic is resolved. Fixed: An issue that could cause a segmentation violation during startup on MIPS devices is resolved. Android Fixed: An issue causing a deadlock when disconnecting from a tailnet is resolved.
Tailscale v1.96.5
iOS Fixed: An issue that could cause the network extension to encounter an out of memory condition on large tailnets is resolved. tvOS Fixed: An issue that could cause the network extension to encounter an out of memory condition on large tailnets is resolved.
Tailscale v1.96.3
Windows Fixed: DNS resolution issue caused by NRPT rule formatting is resolved.
Tailscale 1.96.3
Please refer to the changelog available at https://tailscale.com/changelog
Tailscale v1.96.2
Note : 1.96.0 and 1.96.1 were release candidates intended for testing only. All Platforms New: tailscale dns query|status command supports --json flag to return JSON output. New: tailscale wait [flags] command waits for Tailscale resources to become available for binding.
Tailscale 1.96.2
Please refer to the changelog available at https://tailscale.com/changelog
Tailscale container image v1.96.5
A new release of the Tailscale container image is available. You can download it from Docker Hub or from our GitHub packages repository . New: Services are now automatically advertised on startup. This can be disabled by setting the new environment variable, TS_EXPERIMENTAL_SERVICE_AUTO_ADVERTISEMENT , to false .
Tailscale Kubernetes Operator v1.96.5
A new release of the Tailscale Kubernetes Operator is available. For guidance on installing and updating, refer to our installation instructions . New: Ingress and Egress ProxyGroup pods are able to request a new authkey when required. New: Multiple tailnet access can be enabled with the use of the new Tailnet custom resource.