Skip to content

Fix Go e2e test toolchain version#16

Open
dagger-codex[bot] wants to merge 1 commit into
mainfrom
codex/fix-go-e2e-version
Open

Fix Go e2e test toolchain version#16
dagger-codex[bot] wants to merge 1 commit into
mainfrom
codex/fix-go-e2e-version

Conversation

@dagger-codex
Copy link
Copy Markdown

@dagger-codex dagger-codex Bot commented Jun 2, 2026

Summary

  • update the e2e harness from Go 1.25 to Go 1.26 runners
  • keep fixture module go versions unchanged
  • restore compatibility with helpers/go-includes requiring Go 1.26.1

Verification

  • dagger --x-release v0.21.3 check -m .dagger/modules/e2e
  • go test ./... (in helpers/go-includes)
  • git diff --check

The helper module now requires Go 1.26.1, but the e2e harness still built and ran helpers in Go 1.25 containers. That makes the documented e2e check fail before it reaches the module assertions.\n\nRun the e2e checks with Go 1.26 so the helper module can build while keeping the fixture module go versions unchanged.

Signed-off-by: dagger-codex[bot] <dagger-codex[bot]@users.noreply.github.com>
@dagger-codex
Copy link
Copy Markdown
Author

dagger-codex Bot commented Jun 2, 2026

Local verification passed from the VM with the stable repo engine:

  • dagger --x-release v0.21.3 check -m .dagger/modules/e2e
  • go test ./... in helpers/go-includes
  • git diff --check

The GitHub dagger-dogfood load check is failing before running those checks, so I am leaving this open rather than bypassing CI.

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.

0 participants