Skip to content

fix: migrate legacy upstream metadata (SPEC-M03) - #35

Merged
3alpha merged 1 commit into
mainfrom
fix/spec-m03-upstream-metadata
Nov 9, 2026
Merged

3alpha merged 1 commit into
mainfrom
fix/spec-m03-upstream-metadata

Conversation

@3alpha

@3alpha 3alpha commented Nov 9, 2026

Copy link
Copy Markdown
Member

Context

Fix the SPEC-M03 warning reported by the package specification checks. The legacy upstreamRepo, upstreamVersion and upstreamArg fields 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:

  • Loaded 2 packages using the SDK, including merged variant manifests where present.
  • SPEC-M03 findings: 1 → 0; total spec findings: 2 → 1; no new findings under other rules.
  • Compared manifest schemas and effective compose against the default branch: no new schema failures or service runtime changes.
  • git diff --check passes.

Container images were not built locally.

@tropibot

tropibot Bot commented Nov 9, 2026

Copy link
Copy Markdown

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.

  1. Package juno-sepolia.dnp.dappnode.eth

Install link

Hash: /ipfs/QmX1P9Bc4p4trMMKg7Lui4TKJDpxtnomGJsicZvpmrEZrg

(by dappnodebot/build-action)

@tropibot

tropibot Bot commented Nov 9, 2026

Copy link
Copy Markdown

✅ Package harness passed

Baseline and candidate containers became stably running

Package Verdict Reason Duration Cleanup
juno-sepolia.dnp.dappnode.eth ✅ Passed Candidate containers stable (candidate_containers_stable) 6m 5s ✅ Passed

Run overview

Context Value
Pull request dappnode/DAppNodePackage-juno-generic#35
Tested commit 51a4949b12ec
Candidate artifact Install on DAppNode · /ipfs/QmX1P9Bc4p4trMMKg7Lui4TKJDpxtnomGJsicZvpmrEZrg
Baseline request automatic
Worker dappnode-near-5
Run ID gh-pr-35-51a4949b12ec-9083968f5c5f7dd4
Execution 2026-11-09T11:26:44.644007447+00:00 → 2026-11-09T11:32:50.026098072+00:00 (✅ Completed)

Baseline vs candidate

Check Baseline Candidate
Version 0.1.6 0.1.6
Install ✅ Passed · 1m 20s ✅ Passed · 3m 56s
Hard check ✅ Passed · 3 stable samples ✅ Passed · 3 stable samples
Containers 1 observed 1 observed
Stabilization 10s 10s
Log collection ✅ Passed · 1 container ✅ Passed · 1 container

Container comparison

  • Added: none
  • Removed: none
  • Baseline inventory: DAppNodePackage-juno.juno-sepolia.dnp.dappnode.eth
  • Candidate inventory: DAppNodePackage-juno.juno-sepolia.dnp.dappnode.eth
  • Baseline non-running states: none
  • Candidate non-running states: none
  • Deterministic regressions: ✅ none
Container inventory

Baseline

Container Service State Image Created
DAppNodePackage-juno.juno-sepolia.dnp.dappnode.eth juno ✅ Running juno.juno-sepolia.dnp.dappnode.eth:0.1.6 1794223687

Candidate

Container Service State Image Created
DAppNodePackage-juno.juno-sepolia.dnp.dappnode.eth juno ✅ Running juno.juno-sepolia.dnp.dappnode.eth:0.1.6 1794223926

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.

Analyzer Status Summary
Composite ✅ 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.
Heuristic ✅ Clean No configured candidate-only suspicious signature was found
Nexus ✅ Clean 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.
Baseline evidence ✅ Clean No configured suspicious signature was found
Candidate evidence ✅ Clean No configured suspicious signature was found

✅ No new runtime findings were reported.

Cleanup and diagnostics

Check Result
Cleanup ✅ Passed
Leftover packages none
Cleanup error none

✅ No run errors were recorded.


Deterministic checks decide the verdict. Runtime log analysis is advisory. TropiBot publishes bounded summaries and never posts raw logs.

@3alpha
3alpha added this pull request to stack #37 November 9, 2026 12:13
@3alpha
3alpha merged commit 0498224 into main Nov 9, 2026
3 checks passed
@3alpha
3alpha deleted the fix/spec-m03-upstream-metadata branch November 10, 2026 10:08
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant