ci: add Discord notification to sync workflow

[Copilot]

Adds Discord notification job to the sync workflow, matching the implementation already deployed in geth-generic.

Changes

• Added notify job to .github/workflows/sync.yml that:
  • Depends on sync job completion
  • Runs always (except when sync is skipped)
  • Uses dappnode/staker-test-util/.github/workflows/notify-discord.yml@main reusable workflow
  • Passes sync result and test type for notification context

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

Reference: dappnode/DAppNodePackage-geth-generic@7552d5b

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.

---

💡 You can make Copilot smarter by setting up custom instructions, customizing its development environment and configuring Model Context Protocol (MCP) servers. Learn more Copilot coding agent tips in the docs.

[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-nethermind.dnp.dappnode.eth	0.1.12
Consensus	teku-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	Nethermind/v1.36.0+31cb81b7/linux-x64/dotnet10.0.1
After Install	Nethermind/v1.36.0+31cb81b7/linux-x64/dotnet10.0.1

Consensus Client Versions

Stage	Version
Before Install	teku/v25.9.3/linux-x86_64/-eclipseadoptium-openjdk64bitservervm-java-21
After Install	teku/v25.9.3/linux-x86_64/-eclipseadoptium-openjdk64bitservervm-java-21

⏱️ Timing Measurements

Environment Setup

Operation	Duration	Status
SetStakerConfig	1m0.938s	✅
PackageInstall	22.736s	✅

Test Execution

Operation	Duration	Status
WaitForBeaconchainSync	2m42.122s	✅
WaitForExecutionSync	1ms	✅

Total Duration: 5m25s

🔴 Container Error Logs

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

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

2026-02-06T15:55:00.037819687Z 2026-02-06 15:55:00.037 INFO  - �[32mExecution Client is responding to requests again after a previous failure�[0m

DAppNodePackage-validator.teku-hoodi.dnp.dappnode.eth:

2026-02-06T15:55:05.243216440Z 2026-02-06 15:55:05.243 ERROR - Unable to check validators doppelgangers for keys b1a6afa. Unable to get validators liveness: tech.pegasys.teku.api.exceptions.RemoteServiceNotAvailableException: Server error from Beacon Node API (url = http://beacon-chain.teku-hoodi.dappnode:3500/eth/v1/validator/liveness/73385, status = 503, message = Beacon node is currently syncing and not serving requests)
2026-02-06T15:55:17.249814781Z 2026-02-06 15:55:17.249 ERROR - Unable to check validators doppelgangers for keys b1a6afa. Unable to get validators liveness: tech.pegasys.teku.api.exceptions.RemoteServiceNotAvailableException: Server error from Beacon Node API (url = http://beacon-chain.teku-hoodi.dappnode:3500/eth/v1/validator/liveness/73385, status = 503, message = Beacon node is currently syncing and not serving requests)
2026-02-06T15:55:29.100014442Z 2026-02-06 15:55:29.099 ERROR - Unable to check validators doppelgangers for keys b1a6afa. Unable to get validators liveness: tech.pegasys.teku.api.exceptions.RemoteServiceNotAvailableException: Server error from Beacon Node API (url = http://beacon-chain.teku-hoodi.dappnode:3500/eth/v1/validator/liveness/73384, status = 503, message = Beacon node is currently syncing and not serving requests)

DAppNodePackage-brain.web3signer-hoodi.dnp.dappnode.eth:

2026-02-06T15:55:17.095653294Z �[31m�[0m[ERROR]�[31m�[0m [CRON - reloadValidators]: Error posting fee recipient 0x0000000000000000000000000000000000000001 for pubkey 0xb1a6afab47a6402f8af1ed122e3838cc2989f29e96ee6f26409d65b1cf35a8d81cd0c37bc302f925a9956b3e51e4c204 to validator API: ValidatorApiError: Error setting fee recipient for pubkey 0xb1a6afab47a6402f8af1ed122e3838cc2989f29e96ee6f26409d65b1cf35a8d81cd0c37bc302f925a9956b3e51e4c204 to 0x0000000000000000000000000000000000000001 on validator. ...
2026-02-06T15:56:17.106821550Z �[31m�[0m[ERROR]�[31m�[0m [CRON - reloadValidators]: Error posting fee recipient 0x0000000000000000000000000000000000000001 for pubkey 0xb1a6afab47a6402f8af1ed122e3838cc2989f29e96ee6f26409d65b1cf35a8d81cd0c37bc302f925a9956b3e51e4c204 to validator API: ValidatorApiError: Error setting fee recipient for pubkey 0xb1a6afab47a6402f8af1ed122e3838cc2989f29e96ee6f26409d65b1cf35a8d81cd0c37bc302f925a9956b3e51e4c204 to 0x0000000000000000000000000000000000000001 on validator. ...
2026-02-06T15:57:17.130491088Z �[31m�[0m[ERROR]�[31m�[0m [CRON - reloadValidators]: Error posting fee recipient 0x0000000000000000000000000000000000000001 for pubkey 0xb1a6afab47a6402f8af1ed122e3838cc2989f29e96ee6f26409d65b1cf35a8d81cd0c37bc302f925a9956b3e51e4c204 to validator API: ValidatorApiError: Error setting fee recipient for pubkey 0xb1a6afab47a6402f8af1ed122e3838cc2989f29e96ee6f26409d65b1cf35a8d81cd0c37bc302f925a9956b3e51e4c204 to 0x0000000000000000000000000000000000000001 on validator. ...

---

📋 View full CI logs