Skip to content

[25.12] tailscale: update to 1.94.2#28692

Closed
SuperSandro2000 wants to merge 3 commits into
openwrt:openwrt-25.12from
SuperSandro2000:tailscale-25.12
Closed

[25.12] tailscale: update to 1.94.2#28692
SuperSandro2000 wants to merge 3 commits into
openwrt:openwrt-25.12from
SuperSandro2000:tailscale-25.12

Conversation

@SuperSandro2000
Copy link
Copy Markdown
Contributor

@SuperSandro2000 SuperSandro2000 commented Mar 5, 2026

Changelog: https://tailscale.com/changelog#2026-01-26

I could not cherry-pick #28654 since the merged commit is somehow a merge commit with many, many changes.

📦 Package Details

Maintainer: me / @mochaaP

Description: update tailscale to 1.94.2


🧪 Run Testing Details

None, I have no device with apk but I build it and I think it should work.


✅ Formalities

  • I have reviewed the CONTRIBUTING.md file for detailed contributing guidelines.

If your PR contains a patch:

  • It can be applied using git am
  • It has been refreshed to avoid offsets, fuzzes, etc., using
    make package/<your-package>/refresh V=s
  • It is structured in a way that it is potentially upstreamable
    (e.g., subject line, commit description, etc.)
    We must try to upstream patches to reduce maintenance burden.

@github-actions github-actions Bot added the OpenWrt 25.12 Issues/PR on branch 25.12 label Mar 6, 2026
@wehagy
Copy link
Copy Markdown
Member

wehagy commented Mar 7, 2026

I don't know what you're talking about, #28654 is a simple commit. But you need to cherry-pick 09c1481, f24ebb4, and 04dd276, or you are going to have a drift between stable and master. Also, remember to SoB any commit not made by you.

nrobinson2000 and others added 3 commits March 13, 2026 23:33
Set TS_NO_LOGS_NO_SUPPORT=true as documented here:

https://tailscale.com/kb/1011/log-mesh-traffic?tab=linux#opt-out-of-client-logging

Signed-off-by: Nate Robinson <nrobinson2000@me.com>
(cherry picked from commit 09c1481)
Signed-off-by: Sandro Jäckel <sandro.jaeckel@gmail.com>
(cherry picked from commit f24ebb4)
Signed-off-by: Sandro Jäckel <sandro.jaeckel@gmail.com>
The previous commit 09c1481 introduced TS_NO_LOGS_NO_SUPPORT but
used procd_set_param for a subsequent environment variable. This
overwrote the previous env setting, causing fw_mode to be missed.

Switch to procd_append_param to ensure all environment variables are
properly passed to the process.

Signed-off-by: Tung-Yi Chen <cmtsij@gmail.com>
(cherry picked from commit 04dd276)
Signed-off-by: Sandro Jäckel <sandro.jaeckel@gmail.com>
@SuperSandro2000
Copy link
Copy Markdown
Contributor Author

I think I figured it out.

@KA2107
Copy link
Copy Markdown

KA2107 commented Mar 14, 2026

Tailscale v1.96.1 is tagged in the upstream repo https://github.com/tailscale/tailscale/releases/tag/v1.96.1 but it is not mentioned in the upstream releases page https://github.com/tailscale/tailscale/releases. Does it mean Tailscale v1.96.1 is released or not?

@wehagy
Copy link
Copy Markdown
Member

wehagy commented Mar 17, 2026

@SuperSandro2000, the commit 7ed08ef has an incorrect message and title.

@BKPepe
Copy link
Copy Markdown
Member

BKPepe commented Apr 7, 2026

Kind reminder.

@BKPepe BKPepe closed this Apr 28, 2026
@SuperSandro2000
Copy link
Copy Markdown
Contributor Author

SuperSandro2000 commented Apr 28, 2026

Tailscale v1.96.1 is tagged in the upstream repo tailscale/tailscale@v1.96.1 (release) but it is not mentioned in the upstream releases page tailscale/tailscale/releases. Does it mean Tailscale v1.96.1 is released or not?

It's a prerelease.


This somehow got lost in the hundreds of other notifications. I open another PR.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Projects

None yet

Development

Successfully merging this pull request may close these issues.

6 participants