Repository navigation
fix: use boolean notification flags (SPEC-F03) - #206
Conversation
|
Dappnode bot has built and pinned the built packages to an IPFS node, for commit: 5e85cb7 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⚪ Inconclusive — Heuristic and Nexus analysis: No likely new runtime regression is visible in the candidate cAdvisor logs, whose startup behavior matches the baseline. A candidate-wide comparison is not possible because the supplied candidate evidence is truncated after cAdvisor and does not expose the other containers.
✅ 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-F03 from the package specification checks.
Stacked on #205 (base
fix/spec-m08-repository-url). Merge the base PR first; this diff contains only the next focused fix.Approach
Write all four isBanner flags as booleans so the notification source already matches the validated release object.
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.isBannerflags already typed as booleans.Full container images were not built locally.