Repository navigation
docs: #58, #60 and #61 merged upstream — and what that does not yet mean - #62
Merged
Merged
Conversation
libtailscale merged three on 2026-08-31: 8564835 #60 gate the listener API -> retires 0003 61e8513 #58 run tailscale_up off the actor -> retires 0002 59d4bb8 #61 MACOS_TARGET ?= 15.0 -> never carried here The important part is what has NOT changed. All three sit *ahead of* the commit `vendor/libtailscale` pins (5e89501), so this repo still applies 0002 and 0003 and will keep doing so until the submodule is bumped. Recording them as simply "merged" would imply the patches are gone, which is exactly the kind of claim this section already refuses to make for tailscale#20985 — merged there too, and carried by no release. So each entry now says three things rather than one: it merged, which commit, and that the pin predates it. The delete-do-not-rebase instruction is kept and made conditional on the bump, because that is the moment it becomes actionable. #57 remains open with changes requested and still gates v0.2. #59 remains open and is still not on the critical path. Also refreshes the "states verified" date and extends its caveat: whether a fix has *shipped* was already distinguished from whether it merged, and now so is whether it has reached this repo's pinned submodule. Co-Authored-By: Claude <noreply@anthropic.com>
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
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.
libtailscalemerged three on 2026-08-31:85648350003-gate-listener-api.patch61e8513tailscale_upoff the actor0002-up-off-actor.patch59d4bb8MACOS_TARGET ?=The important part is what has not changed
All three sit ahead of the commit
vendor/libtailscalepins (5e89501):So this repo still applies
0002and0003, and will keep doing so until the submodule is bumped. Recording them as simply "merged" would imply the patches are gone — exactly the claim this section already refuses to make fortailscale#20985, which is merged upstream and carried by no release.Each entry now says three things instead of one: it merged, which commit, and that the pin predates it. The delete-do-not-rebase instruction is kept and made conditional on the bump, because that's the moment it becomes actionable.
Unchanged
Also
Refreshes the "states verified" date and extends its caveat: whether a fix has shipped was already distinguished from whether it merged; now so is whether it has reached this repo's pinned submodule.
Docs only.