Skip to content

Comments

Bump actions/checkout to v6 and use DAPPNODE_ACTIONS_PR_CREATOR token#73

Open
Copilot wants to merge 2 commits intomainfrom
copilot/update-auto-check-workflow
Open

Bump actions/checkout to v6 and use DAPPNODE_ACTIONS_PR_CREATOR token#73
Copilot wants to merge 2 commits intomainfrom
copilot/update-auto-check-workflow

Conversation

Copy link
Contributor

Copilot AI commented Feb 19, 2026

Updates .github/workflows/auto_check.yml workflow configuration.

Changes

  • Bump actions/checkout@v4actions/checkout@v6
  • Set GITHUB_TOKEN env to ${{ secrets.DAPPNODE_ACTIONS_PR_CREATOR }}
steps:
  - uses: actions/checkout@v6
  - run: npx @dappnode/dappnodesdk github-action bump-upstream --use-variants
    env:
      GITHUB_TOKEN: ${{ secrets.DAPPNODE_ACTIONS_PR_CREATOR }}
Original prompt

Repository: dappnode/DAppNodePackage-erigon-generic

Create a pull request updating .github/workflows/auto_check.yml with:

  1. Bump actions/checkout to v6.
  2. Set env GITHUB_TOKEN to ${{ secrets.DAPPNODE_ACTIONS_PR_CREATOR }}.

Acceptance criteria:

  • Only .github/workflows/auto_check.yml is changed unless strictly necessary.
  • YAML remains valid.
  • PR title/description summarize both changes.

This pull request was created from Copilot chat.


💬 We'd love your input! Share your thoughts on Copilot coding agent in our 2 minute survey.

…CTIONS_PR_CREATOR token

Co-authored-by: pablomendezroyo <41727368+pablomendezroyo@users.noreply.github.com>
Copilot AI changed the title [WIP] Update GitHub Actions checkout and token settings Bump actions/checkout to v6 and use DAPPNODE_ACTIONS_PR_CREATOR token Feb 19, 2026
@pablomendezroyo pablomendezroyo marked this pull request as ready for review February 23, 2026 08:07
@github-actions
Copy link
Contributor

✅ 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-erigon.dnp.dappnode.eth 0.1.1
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 erigon/3.2.0/linux-amd64/go1.24.7
After Install erigon/3.3.7/linux-amd64/go1.25.6

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 1m1.397s
PackageInstall 37.624s

Test Execution

Operation Duration Status
WaitForBeaconchainSync 0s
WaitForExecutionSync 0s

Total Duration: 2m10s


📋 View full CI logs

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants