ci: add Discord notification to sync workflow

[Copilot]

Adds Discord notifications for sync workflow completion, matching the implementation in the Geth generic repo (commit 7552d5b6).

Changes

• Added notify job to .github/workflows/sync.yml that runs after sync completes
• Configured to notify on both success and failure, but skips if the sync job was skipped
• Uses reusable workflow from dappnode/staker-test-util with result status and test type

notify:
  needs: sync
  if: always() && needs.sync.result != 'skipped'
  uses: dappnode/staker-test-util/.github/workflows/notify-discord.yml@main
  with:
    result: ${{ needs.sync.result }}
    test_type: "sync"
  secrets: inherit

Original prompt

Context

A change was already implemented in the Geth generic repo that adds a Discord notification job to the sync workflow:
dappnode/DAppNodePackage-geth-generic@7552d5b

This same change needs to be applied to this repository.

Task

Add a new notify job at the END of the .github/workflows/sync.yml file.

The job to add is:

  notify:
    needs: sync
    if: always() && needs.sync.result != 'skipped'
    uses: dappnode/staker-test-util/.github/workflows/notify-discord.yml@main
    with:
      result: ${{ needs.sync.result }}
      test_type: "sync"
    secrets: inherit

Requirements

1. Open the file .github/workflows/sync.yml
2. Add the notify job at the END of the workflow file (after all existing jobs)
3. Do NOT modify any other jobs
4. Do NOT refactor workflow formatting
5. Do NOT reorder existing jobs
6. The notify job must depend on sync
7. Ensure indentation remains valid YAML

Branch and Commit

• Create branch: add-sync-notify-job
• Commit message: ci: add discord notify job to sync workflow
• Open PR to main
• Do NOT merge the PR

This pull request was created from Copilot chat.

---

✨ Let Copilot coding agent set things up for you — coding agent works faster and does higher quality work when set up for your repo.

[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	nimbus-hoodi.dnp.dappnode.eth	0.1.3
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	Nimbus/v25.9.2-9839f1-stateofus
After Install	Nimbus/v25.9.2-9839f1-stateofus

⏱️ Timing Measurements

Environment Setup

Operation	Duration	Status
SetStakerConfig	40.204s	✅
PackageInstall	12.338s	✅

Test Execution

Operation	Duration	Status
WaitForBeaconchainSync	54.032s	✅
WaitForExecutionSync	1m18.048s	✅

Total Duration: 3m33s

🔴 Container Error Logs

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

DAppNodePackage-reth.hoodi-reth.dnp.dappnode.eth:

2026-02-06T16:02:59.402747753Z �[2m2026-02-06T16:02:59.402717Z�[0m �[31mERROR�[0m Failed to send event: Ok(PayloadStatus { status: Syncing, latest_valid_hash: None }) �[3mpayload�[0m�[2m=�[0mNumHash { number: 2181826, hash: 0x2b4ff64b2bbf4fb24eadda6170de15ba1677e903fc0e1ad5b0be0cef088f0282 } �[3melapsed�[0m�[2m=�[0m157.445µs
2026-02-06T16:02:59.575296719Z �[2m2026-02-06T16:02:59.575262Z�[0m �[31mERROR�[0m Failed to send event: Ok(PayloadStatus { status: Syncing, latest_valid_hash: None }) �[3mpayload�[0m�[2m=�[0mNumHash { number: 2181828, hash: 0x5da7bf42f74a18713106c2c22bef4f48d4863dbb91c5daf928b89a008b66e57f } �[3melapsed�[0m�[2m=�[0m410.046µs
2026-02-06T16:02:59.667054004Z �[2m2026-02-06T16:02:59.667020Z�[0m �[31mERROR�[0m Failed to send event: Ok(PayloadStatus { status: Syncing, latest_valid_hash: None }) �[3mpayload�[0m�[2m=�[0mNumHash { number: 2181829, hash: 0x822f6cd8fc69c7419a9546824287d71c9b7ff245d3659bb3366366f77a2371ca } �[3melapsed�[0m�[2m=�[0m418.712µs

---

📋 View full CI logs