Ever since v4, the action runs tailscale status --json as part of its connection to the tailnet, which can show a lot of information about the netmap and state of the tailnet you hook it up to. This can be problematic for public GitHub repos, exposing data on peers, their endpoints, configured app connectors, etc.
Example from this repo: https://github.com/tailscale/github-action/actions/runs/18319442514/job/52168457172#step:6:112
Ever since v4, the action runs
tailscale status --jsonas part of its connection to the tailnet, which can show a lot of information about the netmap and state of the tailnet you hook it up to. This can be problematic for public GitHub repos, exposing data on peers, their endpoints, configured app connectors, etc.Example from this repo: https://github.com/tailscale/github-action/actions/runs/18319442514/job/52168457172#step:6:112