[tropibot]

Automated version bump triggered by release v1.104.7.

Changes

• upstream version (tailscale/tailscale) → v1.104.7
• version 0.3.3 → 0.3.4
• tailscale build arg UPSTREAM_VERSION: v1.104.4 → v1.104.7

[tropibot]

Dappnode bot has built and pinned the built packages to an IPFS node, for commit: ed9f0b4

This is a development version and should only be installed for testing purposes.

1. Package tailscale.dnp.dappnode.eth

Install link

Hash: /ipfs/QmcZAkY3r9xotoGtEXkA2XzTgP77f5skFYHYJof6z4n7E8

(by dappnodebot/build-action)

[tropibot]

✅ Package harness passed

Baseline and candidate passed the configured readiness checks

Package	Verdict	Reason	Duration	Cleanup
tailscale.dnp.dappnode.eth	✅ Passed	Candidate containers stable (candidate_containers_stable)	6m 8s	✅ Passed

Run overview

Context	Value
Pull request	dappnode/DAppNodePackage-tailscale#57
Tested commit	ed9f0b4533d1
Candidate artifact	Install on DAppNode · /ipfs/QmcZAkY3r9xotoGtEXkA2XzTgP77f5skFYHYJof6z4n7E8
Baseline request	automatic
Worker	dappnode-near-5
Run ID	gh-pr-57-ed9f0b4533d1-31f47b0cdbaf7ff6
Execution	2026-11-13T00:44:03.202046520+00:00 → 2026-11-13T00:50:12.031963658+00:00 (✅ Completed)

Baseline vs candidate

Check	Baseline	Candidate
Version	0.3.3	0.3.4
Install	✅ Passed · 0s	✅ Passed · 4m 52s
Hard check	✅ Passed · 3 stable samples	✅ Passed · 3 stable samples
Containers	2 observed	2 observed
Stabilization	10s	10s
Log collection	✅ Passed · 2 containers	✅ Passed · 2 containers

Container comparison

• Added: none
• Removed: none
• Baseline inventory: DAppNodePackage-reporter.tailscale.dnp.dappnode.eth, DAppNodePackage-tailscale.tailscale.dnp.dappnode.eth
• Candidate inventory: DAppNodePackage-reporter.tailscale.dnp.dappnode.eth, DAppNodePackage-tailscale.tailscale.dnp.dappnode.eth
• Baseline non-running states: none
• Candidate non-running states: none
• Deterministic regressions: ✅ none

Container inventory

Baseline

Container	Service	State	Image	Created
DAppNodePackage-tailscale.tailscale.dnp.dappnode.eth	tailscale	✅ Running	tailscale.tailscale.dnp.dappnode.eth:0.3.3	1794227605
DAppNodePackage-reporter.tailscale.dnp.dappnode.eth	reporter	✅ Running	reporter.tailscale.dnp.dappnode.eth:0.3.3	1794227605

Candidate

Container	Service	State	Image	Created
DAppNodePackage-tailscale.tailscale.dnp.dappnode.eth	tailscale	✅ Running	tailscale.tailscale.dnp.dappnode.eth:0.3.4	1794530960
DAppNodePackage-reporter.tailscale.dnp.dappnode.eth	reporter	✅ Running	reporter.tailscale.dnp.dappnode.eth:0.3.4	1794530960

Runtime analysis _advisory

✅ Clean — Heuristic and Nexus analysis: Both collections are stable and contain all 2 expected containers. The candidate tailscaled v1.104.7 reaches Running, completes startup, obtains a control netmap, connects to DERP, and has the reporter resume status reporting. The new "netmap cache is not available" message is followed by successful netmap acquisition and cache update, so it is not an evident runtime regression. Other warnings are shared with baseline or recover successfully.

Analyzer	Status	Summary
Composite	✅ Clean	Heuristic and Nexus analysis: Both collections are stable and contain all 2 expected containers. The candidate tailscaled v1.104.7 reaches Running, completes startup, obtains a control netmap, connects to DERP, and has the reporter resume status reporting. The new "netmap cache is not available" message is followed by successful netmap acquisition and cache update, so it is not an evident runtime regression. Other warnings are shared with baseline or recover successfully.
Heuristic	✅ Clean	No configured candidate-only suspicious signature was found
Nexus	✅ Clean	Both collections are stable and contain all 2 expected containers. The candidate tailscaled v1.104.7 reaches Running, completes startup, obtains a control netmap, connects to DERP, and has the reporter resume status reporting. The new "netmap cache is not available" message is followed by successful netmap acquisition and cache update, so it is not an evident runtime regression. Other warnings are shared with baseline or recover successfully.
Baseline evidence	✅ Clean	No configured suspicious signature was found
Candidate evidence	✅ Clean	No configured suspicious signature was found

✅ No new runtime findings were reported.

Cleanup and diagnostics

Check	Result
Cleanup	✅ Passed
Leftover packages	none
Cleanup error	none

✅ No run errors were recorded.

---

_{Deterministic checks decide the verdict. Runtime log analysis is advisory. TropiBot publishes bounded summaries and never posts raw logs.}