ci: use default GitHub token for auto_check PRs

[3alpha]

No description provided.

[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-besu.dnp.dappnode.eth	0.1.4
Consensus	lighthouse-hoodi.dnp.dappnode.eth	0.1.6
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	besu/v25.9.0/linux-x86_64/openjdk-java-21
After Install	besu/v26.4.0/linux-x86_64/openjdk-java-25

Consensus Client Versions

Stage	Version
Before Install	Lighthouse/v8.1.3-176cce5/x86_64-linux
After Install	Lighthouse/v8.1.3-176cce5/x86_64-linux

⏱️ Timing Measurements

Environment Setup

Operation	Duration	Status
SetStakerConfig	57.322s	✅
PackageInstall	35.297s	✅

Test Execution

Operation	Duration	Status
WaitForBeaconchainSync	0s	✅
WaitForExecutionSync	2ms	✅

Total Duration: 1m55s

---

📋 View full CI logs