Skip to content

ci(e2e-bot): build with go.mod's Go version, not pinned 1.22#3731

Merged
esengine merged 1 commit into
main-v2from
fix/e2ebot-go-version
Jun 9, 2026
Merged

ci(e2e-bot): build with go.mod's Go version, not pinned 1.22#3731
esengine merged 1 commit into
main-v2from
fix/e2ebot-go-version

Conversation

@esengine

@esengine esengine commented Jun 9, 2026

Copy link
Copy Markdown
Owner

Summary

The /e2e bot is broken: its first step ("Build harness + fallback agent from the default branch") fails because e2e-bot.yml pins go-version: '1.22' (with setup-go's GOTOOLCHAIN=local) while go.mod now requires go >= 1.25.0:

go: go.mod requires go >= 1.25.0 (running go 1.22.12; GOTOOLCHAIN=local)

This aborts every /e2e run before it can build the harness/agent (observed on a /e2e against #3586).

Fix

Use go-version-file: go.mod, exactly like ci.yml and the release-*.yml workflows already do. The bot then tracks the repo's Go version automatically and won't go stale on the next bump.

Test plan

  • 1-line value swap, indentation unchanged; mirrors the proven setup-go config used by every other workflow.
  • Validation is the next /e2e run after merge (the bot's workflow is read from the default branch).

The e2e-bot pinned go-version: '1.22' with setup-go's GOTOOLCHAIN=local, but
go.mod now requires go >= 1.25.0, so the very first step ("Build harness +
fallback agent from the default branch") fails with:

  go: go.mod requires go >= 1.25.0 (running go 1.22.12; GOTOOLCHAIN=local)

That breaks every /e2e invocation before it can build anything. Every other
workflow (ci.yml, release-*.yml) already uses go-version-file: go.mod; mirror
that here so the bot tracks the repo's Go version and never goes stale again.
@esengine esengine requested a review from SivanCola as a code owner June 9, 2026 16:25
@github-actions github-actions Bot added the v2 Go rewrite (1.x) — main-v2 branch, active development label Jun 9, 2026
@esengine esengine merged commit e634cfd into main-v2 Jun 9, 2026
13 of 14 checks passed
@esengine esengine deleted the fix/e2ebot-go-version branch June 9, 2026 16:29
SuMuxi66 pushed a commit to SuMuxi66/DeepSeek-Reasonix that referenced this pull request Jun 10, 2026
…e#3731)

The e2e-bot pinned go-version: '1.22' with setup-go's GOTOOLCHAIN=local, but
go.mod now requires go >= 1.25.0, so the very first step ("Build harness +
fallback agent from the default branch") fails with:

  go: go.mod requires go >= 1.25.0 (running go 1.22.12; GOTOOLCHAIN=local)

That breaks every /e2e invocation before it can build anything. Every other
workflow (ci.yml, release-*.yml) already uses go-version-file: go.mod; mirror
that here so the bot tracks the repo's Go version and never goes stale again.
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

v2 Go rewrite (1.x) — main-v2 branch, active development

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant