Skip to content

Re-pin upstream LocalAPI capability to 148 - #42

Merged
dweekly merged 4 commits into
mainfrom
fix/upstream-capability-148
Sep 22, 2026
Merged

dweekly merged 4 commits into
mainfrom
fix/upstream-capability-148

Conversation

@dweekly

@dweekly dweekly commented Sep 22, 2026 •

Copy link
Copy Markdown
Owner

The weekly upstream check reports capability 148 while this client advertises the previously verified 144. Re-pin the manifest to tailscale/tailscale@7bf76690f09db74b1f48d49db056fac69c4b421e, update the default and its contract tests, and regenerate the provenance documentation. Explicit capability overrides remain supported.

The upstream review found no request-header capability gates and no changes to the maturity/gate facts covered by the verifier. Documentation/COMPATIBILITY-148.md records the review and validation evidence. Update the re-pin instructions to require Apple CI and read-only macOS daemon integration, consistent with the release scope. No Linux code or Linux workflow changes are included.

Validation on final revision d69e410cd1a849c1f79d62cd1e9ffe00b56e4808:

Fixes #39.

@dweekly
dweekly merged commit 6602ddc into main Sep 22, 2026
10 checks passed
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

Upstream drift: endpoint manifest no longer matches tailscale/tailscale main

2 participants