Repository navigation
fix: migrate legacy upstream metadata (SPEC-M03) - #35
Conversation
|
Dappnode bot has built and pinned the built packages to an IPFS node, for commit: 51a4949 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 was observed. Baseline and candidate initialize Juno with identical parameters and begin the same snapshot download. The candidate progresses farther (589824K versus 491520K) at generally higher throughput, with no new errors or warnings in either log.
✅ 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 }]:NethermindEth/juno,v0.16.2,UPSTREAM_VERSION.Test instructions
Validate this branch with the SDK package-spec checker from the linked PR for all variants and confirm that no SPEC-M03 findings remain.
Verified locally:
git diff --checkpasses.Container images were not built locally.