Skip to content

fix: align Go version across go.work and CI with go.mod requirement#48

Open
rennerdo30 wants to merge 1 commit into
mainfrom
fix/go-version-alignment
Open

fix: align Go version across go.work and CI with go.mod requirement#48
rennerdo30 wants to merge 1 commit into
mainfrom
fix/go-version-alignment

Conversation

@rennerdo30

Copy link
Copy Markdown
Owner

Problem

The repository had a pre-existing Go version mismatch that broke every Backend CI job at module download/verification:

  • go.mod requires go 1.25.0
  • go.work declared go 1.24.0
  • .github/workflows/ci.yml pinned GO_VERSION: "1.24"

Because the module's required Go version (1.25.0) exceeds the toolchain configured in CI (1.24), Go's version checking fails before/at module download, failing the Backend CI jobs. This is unrelated to any dependency bump.

Fix

Align the workspace and CI to satisfy go.mod without downgrading it:

  • go.work: go 1.24.0go 1.25.0
  • .github/workflows/ci.yml: GO_VERSION "1.24""1.25"

go.mod is left at 1.25.0 (not downgraded).

Verification

Verified locally with the default workspace (GOWORK on, local Go 1.26.4):

  • go build ./... — passes
  • go test ./... — all packages pass

🤖 Generated with Claude Code

go.mod requires 'go 1.25.0', but go.work declared 'go 1.24.0' and the CI
workflow pinned GO_VERSION "1.24". With Go's toolchain checking, the lower
toolchain in CI fails module download/verification because the module's
required Go version (1.25.0) exceeds the configured 1.24, breaking every
Backend CI job.

This aligns the workspace and CI to satisfy go.mod without downgrading it:
- go.work: go 1.24.0 -> go 1.25.0
- .github/workflows/ci.yml: GO_VERSION "1.24" -> "1.25"

Verified locally with the default workspace (GOWORK on):
`go build ./...` and `go test ./...` both pass.

Co-Authored-By: Claude Opus 4.8 <noreply@anthropic.com>
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