fix(go): bump go.work go directive to 1.26.4#36
Merged
Conversation
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
approved these changes
Jun 8, 2026
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
What
Bump the
go.workgo directive fromgo 1.26.3togo 1.26.4.Why
PR #35 raised
kustomize/go.modtogo 1.26.4(to rebuild with the fixed Go stdlib), butgo.workwas left atgo 1.26.3. The Alauda release build then failed in goreleaser:As a result the
v5.8.1-alauda-29tag was created but no CLI artifact was produced — the latest release stayed atv5.8.1-alauda-28.go.work's go directive must be>=the highest module requirement. The other 43 modules are still at1.26.3, so1.26.4satisfies 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.