Repository navigation
fix: use build argument mappings (SPEC-C05) - #16
Conversation
|
Dappnode bot has built and pinned the built packages to an IPFS node, for commit: a44a3c1 This is a development version and should only be installed for testing purposes.
Hash: (by dappnodebot/build-action) |
🛠️ Package harness hit an infrastructure error
Run overview
Baseline vs candidate
Hard-check reasons
Container comparison
Container inventoryBaseline No container snapshot was available. Candidate No container snapshot was available. Runtime analysis advisory⚪ Inconclusive — Log analysis was unavailable
✅ No new runtime findings were reported. Analyzer diagnostics
Cleanup and diagnostics
Deterministic checks decide the verdict. Runtime log analysis is advisory. TropiBot publishes bounded summaries and never posts raw logs. |
Context
Correct SPEC-C05 from the package specification checks.
Stacked on #15 (base
fix/spec-m03-upstream-metadata). Merge the base PR first; this diff contains only the next focused fix.Approach
Replace list-style build arguments with a mapping while preserving every argument name and exact string value. Core package container names remain unchanged.
Test instructions
Run the SDK package-spec validation on this branch for all package variants.
Verified locally:
docker compose config --quietpass for every variant.git diff --checkand replay of the complete PR stack pass.Full container images were not built locally.