[stdevMac]

Adds an opt-in skip_tests input to the manual Release run, identical to DAppNodePackage-erigon-generic (13d338b). Pushes to main still run the test (inputs.skip_tests is empty there and falls back to false).

Why

Release run 38993424916 (nethermind 2.2.0, #91) failed in release / Test before Nethermind was installed:

[FAIL] SetStakerConfig
test API call 'stakerConfigSet' returned HTTP 500: {"name":"TypeError","message":"fetch failed", ...
  at async HttpsPortalApiClient.get (packages/httpsPortal/dist/apiClient.js:85:21)
  at async HttpsPortalApiClient.list (packages/httpsPortal/dist/apiClient.js:68:25)
  at async HttpsPortal.hasApiMapping (...)

This is a problem with the test machine, not with the package:

• The DAPPMANAGER on runner staking-test (machine tropi-1) cannot reach the HTTPS portal API (http://https.dappnode:5000), even though the https.dnp.dappnode.eth container reports itself as running (isRunningHttps() passes and then the fetch fails).
• It started between 2026-10-12 05:08Z and 2026-10-13 05:03Z. Sync Production passed on 10-11 and 10-12 and has failed every day since 10-13 with the same error. Both the passing and the failing runs used the same machine (tropi-1) and the same dappnode/tropibot:latest image (sha256:40fbe63a…, published 10-06). Neither dappnode/workflows nor DNP_HTTPS has changed since then.
• Other packages fail the same way on the same step: besu-generic, teku-generic, prysm-generic and nimbus-generic Sync Tests (10-15 and 10-16).

Root-cause fix (needs access to tropi-1): restart the HTTPS portal core package, or check that it is still attached to dncore_network with the https.dappnode alias. Then re-run 38993424916.

Release path once this is merged

Run Release manually on main with skip_tests ticked. This publishes 2.2.0 without waiting for the runner fix. Hoodi's Glamsterdam fork activates on 2026-10-26 17:42:48 UTC and needs Nethermind 2.2.0.

[tropibot]

❌ TropiBot report: SYNC TEST REPORT - FAILED

This CI runs on a real DAppNode using the same RPC calls a user would make to configure a staker setup: execution client, consensus client, web3signer, MEV-boost, and relays.

📦 Package Under Test

• IPFS Hash: QmNuGAK8yHn4CEHQnPnUMnNFJy8GgCuQpFS4D9bMJw5Axe
• Install on DAppNode

📦 Clients Used

Component	DNP Name
Execution	hoodi-nethermind.dnp.dappnode.eth
Consensus	lodestar-hoodi.dnp.dappnode.eth
Web3Signer	web3signer-hoodi.dnp.dappnode.eth
MEV Boost	mev-boost-hoodi.dnp.dappnode.eth
Network	hoodi

🔖 Version Tracking

Client	Before	After
Execution	n/a	n/a
Consensus	n/a	n/a

⏱️ Timing

Operation	Duration	Status
SetStakerConfig	12.5s	❌

Total Duration: 12.5s

❌ Error Details

Setup failed: test API call 'stakerConfigSet' returned HTTP 500: {"name":"TypeError","message":"fetch failed","stack":"TypeError: fetch failed\n    at node:internal/deps/undici/undici:13502:13\n    at process.processTicksAndRejections (node:internal/process/task_queues:105:5)\n    at async HttpsPortalApiClient.get (file:///usr/src/app/packages/httpsPortal/dist/apiClient.js:85:21)\n    at async HttpsPortalApiClient.list (file:///usr/src/app/packages/httpsPortal/dist/apiClient.js:68:25)\n    at async HttpsPortal.hasApiMapping (file:///usr/src/app/packages/https…

---

📋 View full CI logs