Refactor CI workflows for improved release and sync testing

[pablomendezroyo]

Remove the main CI workflow and introduce new workflows for release, sync testing, and execution client sync production. This refactor enhances the structure and efficiency of the CI process.

[github-actions]

✅ SYNC TEST REPORT - PASSED

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. The self-hosted runner is pre-loaded with synced (or near-synced) execution client volumes, enabling fast sync and attestation tests with any client combination. Consensus clients use checkpoint sync, so no pre-synced volume is required.

Sync Test: Verifies that both execution and consensus clients reach a synced state. This test ensures the staker configuration is valid and clients can synchronize with the network.

📦 Clients Used

Component	DNP Name	DNP Version
Execution	hoodi-reth.dnp.dappnode.eth	0.1.4
Consensus	prysm-hoodi.dnp.dappnode.eth	0.1.5
Web3Signer	web3signer-hoodi.dnp.dappnode.eth	0.1.3
MEV Boost	mev-boost-hoodi.dnp.dappnode.eth	0.1.1
Network	hoodi

🔖 Version Tracking

Execution Client Versions

Stage	Version
Before Install	reth/v1.9.2-74351d9/x86_64-unknown-linux-gnu
After Install	reth/v1.10.1-c9dad47/x86_64-unknown-linux-gnu

Consensus Client Versions

Stage	Version
Before Install	Prysm/v7.0.1 (linux amd64)
After Install	Prysm/v7.0.1 (linux amd64)

⏱️ Timing Measurements

Environment Setup

Operation	Duration	Status
SetStakerConfig	29.607s	✅
PackageInstall	12.876s	✅

Test Execution

Operation	Duration	Status
WaitForBeaconchainSync	42.025s	✅
WaitForExecutionSync	3m0.1s	✅

Total Duration: 4m32s

🔴 Container Error Logs

⚠️ Showing up to 3 error lines per container. See CI logs for complete details.

DAppNodePackage-beacon-chain.prysm-hoodi.dnp.dappnode.eth:

2026-02-05T20:50:14.535441927Z time="2026-02-05 20:50:14.53" level=warning msg="Block processing failure" error="validator execution and consensus: could not notify the engine of the new payload: got an unexpected error in JSON-RPC response: Post "http://execution.hoodi.staker.dappnode:8551": dial tcp 172.24.0.2:8551: connect: connection refused: received an undefined execution engine error" firstSlot=2342496 lastSlot=2342529 prefix=initial-sync root=0xf8fd57b9c42b6782eebb53f9681decebd959c95734a...
2026-02-05T20:50:31.943652407Z time="2026-02-05 20:50:31.94" level=warning msg="Could not update head" error="head at slot 2342528 with weight 125625 is not eligible, finalizedEpoch, justified Epoch 73202, 73203 != 73204, 73204" prefix=blockchain
2026-02-05T20:50:33.154500432Z time="2026-02-05 20:50:33.15" level=warning msg="Could not update head" error="head at slot 2342528 with weight 248402 is not eligible, finalizedEpoch, justified Epoch 73202, 73203 != 73204, 73204" prefix=blockchain

---

📋 View full CI logs