docs: correct upstream status in README and TAILSCALE.md - #11
Merged
Conversation
TAILSCALE.md listed tailscale#13937 (first-class Swift support) as Open. It has been closed as completed since 2025-05-05 — TailscaleKit, which this project depends on, is the result. Stating otherwise in a public-facing doc is the kind of claim a reader checks in ten seconds. Also adds: - tailscale#20985 is now approved (bradfitz), not merely open. - libtailscale#57, opened from this project: privacy manifests for the iOS slices (ITMS-91053), a macOS slice, and a validator for the failures that only appear at upload. If it lands, most of build-tailscalekit.sh becomes redundant. - tailscale#15410, previously unmentioned and worth reading — it anticipated the os.Executable problem #19052 later fixed, and ends with "The HelloTailscale sample should get ported over to iOS", which is essentially what this repo is. With a note that closed-as-completed does not mean finished in practice: the network.server sandbox requirement and the LocalAPIClient device hang were both found after those issues were closed. Co-Authored-By: Claude Opus 5 (1M context) <noreply@anthropic.com> Claude-Session: https://claude.ai/code/session_01Ri3jHCuKtxsWxfv8txbnm6
Three corrections and one addition. "Two bugs found here have gone upstream" is now three contributions — the count was stale the moment libtailscale#57 was opened. #20985 was listed as merely Open; it has been approved. #13937 and #15410 were listed flatly as "related upstream issues" with no indication that BOTH are closed as completed. A reader clicking through finds two closed issues and reasonably concludes the iOS story is handled upstream and this repo is redundant. The section now says they are closed, what the first produced (TailscaleKit, which this project is built on), and why closed does not mean finished here: the network.server sandbox requirement and the LocalAPIClient device hang were both found after those closures. Adds libtailscale#57 and its tracking issue tailscale#20992, including the consequence a reader cares about — if it lands, most of build-tailscalekit.sh becomes unnecessary and the xcframework can be taken straight from upstream. Also quotes the maintainer line from #15410, "The HelloTailscale sample should get ported over to iOS", which is the clearest one-sentence statement of what this repo is for. Every link in the section was checked against the API; the six states quoted match live data. Co-Authored-By: Claude Opus 5 (1M context) <noreply@anthropic.com> Claude-Session: https://claude.ai/code/session_01Ri3jHCuKtxsWxfv8txbnm6
prakashrj
changed the title
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.
Problem
Both docs described upstream inaccurately, in ways a reader checks in seconds.
TAILSCALE.mdlisted tailscale#13937 (first-class Swift support) as Open. It's been closed as completed since 2025-05-05 — TailscaleKit, which this project depends on, is the result.README.mdopened with "Two bugs found here have gone upstream" — stale the moment libtailscale#57 was opened — and listed #13937 and #15410 flatly as "related upstream issues" with no indication that both are closed as completed. A reader clicking through finds two closed issues and reasonably concludes the iOS story is handled upstream and this repo is redundant.Changes
Both files now state:
build-tailscalekit.shbecomes unnecessary and the xcframework can come straight from upstreamPlus the point that closed ≠ finished: the
network.serversandbox requirement and theLocalAPIClientdevice hang documented in these same files were both found after those issues were closed. That's the context a reader needs to judge how much upstream currently exercises this path.README also quotes the maintainer line from #15410 — "The HelloTailscale sample should get ported over to iOS" — which is the clearest one-sentence statement of what this repo is for.
Validation
Every referenced link was checked against the GitHub API rather than assumed:
Docs only — no build or CI changes.
🤖 Generated with Claude Code
https://claude.ai/code/session_01Ri3jHCuKtxsWxfv8txbnm6