Repository navigation
fix: migrate legacy upstream metadata (SPEC-M03) - #64
Conversation
|
Dappnode bot has built and pinned the built packages to an IPFS node, for commit: 7b90238 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 regressions were found. The candidate starts the same services and reaches setup and dashboard readiness as the baseline; all candidate warnings are also present in the baseline. The reduced skill-update count is a non-error state difference and is not evidence of a 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 }]:NousResearch/hermes-agent,v2026.9.11,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.