Repository navigation
fix: use build argument mappings (SPEC-C05) - #20
Conversation
|
Dappnode bot has built and pinned the built packages to an IPFS node, for commit: 535ab57 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 are evident. The candidate completes database backup and migration, retains the pre-existing Chisel key, and starts Chisel plus HTTP/HTTPS listeners without errors or panics.
✅ 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
Correct SPEC-C05 from the package specification checks.
Based on the default branch
main.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.