chore(go): rebuild with Go 1.26.4 to fix stdlib CVEs#35
Merged
Conversation
Rebuild released binaries with Go 1.26.4 to clear stdlib CVE-2026-42504, CVE-2026-27145 and CVE-2026-42507. The Alauda release workflow resolves the toolchain via setup-go go-version-file: kustomize/go.mod, so bumping this directive is sufficient for the next -alauda-N release to build on Go 1.26.4. Consumed downstream by AlaudaDevops/catalog.
yuzichen12123
approved these changes
Jun 8, 2026
alaudabot
approved these changes
Jun 8, 2026
alaudabot
pushed a commit
that referenced
this pull request
Jun 8, 2026
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.
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
3 participants
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.
Why
Released binaries on
alauda-v5.8.0build with Go 1.26.3 and carry stdlibCVE-2026-42504 (HIGH), CVE-2026-27145 (MEDIUM) and CVE-2026-42507
(MEDIUM), all fixed in Go 1.26.4.
What
Bump the
godirective inkustomize/go.modfrom1.26.3to1.26.4.The Alauda release workflow (
reusable-release-alauda.yaml) usesactions/setup-gowithgo-version-file: kustomize/go.mod, so the nextauto-cut
-alauda-Nrelease will build on Go 1.26.4 and scan clean.Module
kustomize/go.mod(the CLI submodule — this is the modulethe release workflow builds, not a repo-root go.mod which does not exist)
go 1.26.3→go 1.26.4Downstream impact
Consumed downstream by AlaudaDevops/catalog images, which currently fail their
Trivy gate due to the stdlib CVEs present in the kustomize binary.