Skip to content

fix(go): bump go.work go directive to 1.26.4#36

Merged
alaudabot merged 1 commit into
alauda-v5.8.0from
fix/go-work-go-1264
Jun 8, 2026
Merged

fix(go): bump go.work go directive to 1.26.4#36
alaudabot merged 1 commit into
alauda-v5.8.0from
fix/go-work-go-1264

Conversation

@l-qing

@l-qing l-qing commented Jun 8, 2026

Copy link
Copy Markdown

What

Bump the go.work go directive from go 1.26.3 to go 1.26.4.

Why

PR #35 raised kustomize/go.mod to go 1.26.4 (to rebuild with the fixed Go stdlib), but go.work was left at go 1.26.3. The Alauda release build then failed in goreleaser:

failed to get module path: go: module kustomize listed in go.work file
requires go >= 1.26.4, but go.work lists go 1.26.3

As a result the v5.8.1-alauda-29 tag was created but no CLI artifact was produced — the latest release stayed at v5.8.1-alauda-28.

go.work's go directive must be >= the highest module requirement. The other 43 modules are still at 1.26.3, so 1.26.4 satisfies all of them.

Verification

With local go 1.26.4, go list -m (which goreleaser runs to load module info) now succeeds; previously it errored on the version mismatch.

PR #35 bumped kustomize/go.mod to go 1.26.4 to rebuild with the fixed Go
stdlib, but go.work was left at go 1.26.3. The Alauda release build then
failed in goreleaser with "go.work file requires go >= 1.26.4, but go.work
lists go 1.26.3", so no CLI artifact was produced. Align the go.work go
directive with the highest module requirement to unblock the release build.
@alaudabot alaudabot merged commit f88d456 into alauda-v5.8.0 Jun 8, 2026
2 checks passed
@alaudabot alaudabot deleted the fix/go-work-go-1264 branch June 8, 2026 04:59
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