Repository navigation
fix(capver): track Tailscale 1.104 and refuse clients older than 1.84 - #65
Merged
Merged
Conversation
Tailscale 1.104 shipped at capability version 148, so the supported window of ten minor releases now runs 1.84 to 1.104 and the generated check on every branch failed until the tables moved. What 1.104 brings over 1.102 (capvers 143-148) needs nothing new here: Node.StableTailnetID is already sent, scope-quad100-macos and debug-conn-reject pass through policy nodeAttrs as written, and the TSMP disco advertisement is client to client. 429/503 with Retry-After on /machine/ is taken up separately. The policy reference said network map caching was expected with 1.104; it needs 149, a later release. Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
Merged
trancong12102
added a commit
that referenced
this pull request
Oct 14, 2026
A release is ready. Read the notes below as an operator would, fix a wrong line by editing the commit's PR body with a BEGIN_COMMIT_OVERRIDE block, and merge to tag and publish. --- ## [0.58.2](v0.58.1...v0.58.2) (2026-10-14) ### Fixes * **capver:** track Tailscale 1.104 and refuse clients older than 1.84 ([#65](#65)) ([53a652f](53a652f)) * **mapper:** stop a slow control plane from piling up abandoned sessions ([#66](#66)) ([f4f8b87](f4f8b87)) * **state:** skip an app on every connector for machines at one connector's site ([#64](#64)) ([03bfc35](03bfc35)) --- This PR was generated with [Release Please](https://github.com/googleapis/release-please). See [documentation](https://github.com/googleapis/release-please#release-please).
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
1 participant
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Tailscale 1.104 was released at capability version 148. Until the capver tables include it, the
generatedcheck fails on every branch, including #62 and #64.Changes
go generate ./hscontrol/capver/only, not the fullmake generate. It addsv1.104 → 148, andMinSupportedCapabilityVersionmoves from 115 to 116, so the supported window is now 1.84–1.104. The oldest client in production is 1.98.5, so nobody is refused.docs/content/ref/policy.mdxclaimed netmap caching was expected with 1.104. It needs capver 149, which is a later release.What 1.104 adds over 1.102 (capvers 143–148), reviewed for drop, change or adopt
scope-quad100-macosand 146debug-conn-reject: policynodeAttrsalready pass any attribute through, so operators can set both today.Retry-Afteron/machine/: will be adopted in a follow-up for load shedding, motivated by the 2026-10-14 incident.Node.StableTailnetID: already sent (mapper/builder.go).CanOldCodeBeCleanedUpis not tripped, since the threshold is 148 and the minimum is now 116.🤖 Generated with Claude Code