Skip to content

ci: bump Go to stable, refresh actions to v5#3

Merged
Giulio2002 merged 1 commit into
masterfrom
ci/fix-go-version
May 10, 2026
Merged

ci: bump Go to stable, refresh actions to v5#3
Giulio2002 merged 1 commit into
masterfrom
ci/fix-go-version

Conversation

@Giulio2002
Copy link
Copy Markdown
Owner

Summary

Master CI has been failing since the merge of #2:

go: errors parsing go.mod:
/home/runner/work/gevm/gevm/go.mod:3: invalid go version '1.25.5': must match format 1.23

The workflow pinned go-version: '1.20', but go.mod declares go 1.25.5. Go 1.20's parser only accepts two-part 1.X directives — three-part 1.X.Y was added in Go 1.21. Bump the workflow to stable (with check-latest: true).

While here, refresh the actions to v5 (Node 24) — the workflow log was warning about Node 20 deprecation on actions/checkout@v4 and actions/setup-go@v4.

Also drop the git submodule update --init --recursive from the test step. .gitmodules declares two fixture submodules (tests/fixtures/ethereum-tests, tests/fixtures/execution-spec-tests) but neither has a gitlink pointer in the tree, so git submodule update --init is a silent no-op on every CI run. The fixture-gated tests (TestSpecFixtureDir, TestBlockchainFixtureDir, etc.) already self-skip when GEVM_TESTS_DIR / GEVM_BLOCKCHAIN_TESTS_DIR / etc. are unset, which they are in stock CI.

Test plan

  • Workflow YAML lints
  • Re-run CI on this PR to verify green build + test on Go stable

🤖 Generated with Claude Code

go.mod declares `go 1.25.5` but the workflow installed Go 1.20, which
errors on three-part version directives:

    go: errors parsing go.mod:
    /home/runner/work/gevm/gevm/go.mod:3: invalid go version '1.25.5':
    must match format 1.23

Pin the workflow to Go `stable` (with check-latest so we pick up new
1.25.x patch releases). Also bump `actions/checkout` and
`actions/setup-go` to v5 so the runner's deprecation warning about
Node 20 goes away (v5 ships on Node 24).

Drop the `git submodule update --init --recursive` from the test step:
.gitmodules declares fixture submodules but the tree contains no
gitlink pointers, so the command was a silent no-op. Fixture-gated
tests already self-skip when their env vars (GEVM_TESTS_DIR / etc.)
are unset, which they are on stock CI.

Co-Authored-By: Claude Sonnet 4.6 <noreply@anthropic.com>
@Giulio2002 Giulio2002 merged commit 88a0ec5 into master May 10, 2026
1 check passed
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.

1 participant