Repository navigation
fix: migrate legacy upstream metadata (SPEC-M03) - #56
Conversation
|
Dappnode bot has built and pinned the built packages to an IPFS node, for commit: fbf4b83 This is a development version and should only be installed for testing purposes.
Hash: (by dappnodebot/build-action) |
✅ Package harness passed
Run overview
Baseline vs candidate
Container comparison
Container inventoryBaseline
Candidate
Runtime analysis advisory✅ Clean — Heuristic and Nexus analysis: No likely new runtime regression is evident. The candidate reaches Running, completes startup, restores the active login, connects to a DERP relay, and the reporter recovers. Candidate-only transient messages such as "active login: <missing-profile>" are resolved later and do not demonstrate an ongoing regression.
✅ No new runtime findings were reported. Cleanup and diagnostics
✅ No run errors were recorded. Deterministic checks decide the verdict. Runtime log analysis is advisory. TropiBot publishes bounded summaries and never posts raw logs. |
Context
Fix the SPEC-M03 warning reported by the package specification checks. The legacy
upstreamRepo,upstreamVersionandupstreamArgfields are deprecated.Approach
Replace the legacy fields with
upstream: [{ repo, version, arg }]:tailscale/tailscale,v1.104.4,UPSTREAM_VERSION.Test instructions
Validate this branch with the SDK package-spec checker from the linked PR and confirm that no SPEC-M03 findings remain.
Verified locally:
git diff --checkpasses.Container images were not built locally.