fix: bump Go to 1.25.11 + auto-trigger dependency-image build [DEVX-3134]#30
Open
Hammond95 wants to merge 2 commits into
Open
fix: bump Go to 1.25.11 + auto-trigger dependency-image build [DEVX-3134]#30Hammond95 wants to merge 2 commits into
Hammond95 wants to merge 2 commits into
Conversation
The linux-bench-dependency image (built from Dockerfile with golang:1.25.10) embeds a linux-bench binary affected by two HIGH, network-vector, fixable Go runtime CVEs, which fails the Sysdig "secure-components-vuln-check" policy on the downstream compliance-benchmark-runner image: - CVE-2026-27145 (fixed in Go 1.25.11) - CVE-2026-42504 (fixed in Go 1.25.11) Bump all Go references to 1.25.11: - Dockerfile (the builder for linux-bench-dependency) 1.25.10 -> 1.25.11 - Dockerfile_linux_arm64 / Dockerfile_linux_s390x 1.25.9 -> 1.25.11 - go.mod language version 1.25.9 -> 1.25.11 - CI setup-go (build.yml, release.yml) 1.25.9 -> 1.25.11 Mirrors the kube-bench fix (draios/kube-bench#50). After this merges, the compliance-linux-bench Jenkins job must rebuild and publish a new linux-bench-dependency tag, which secure-backend then pins via LINUX_BENCH_TAG. Co-Authored-By: Claude Opus 4.8 <noreply@anthropic.com>
Mirror the kube-bench automation: on push of a 4-part numeric dependency tag, trigger the compliance-linux-bench Jenkins job with TAG=<tag>, which builds and publishes linux-bench-dependency:<tag> to GAR (registry tag == git tag). Registry tags are immutable, so each newly pushed tag is a fresh release by construction — no bump/collision handling needed here. Uses the org-standard tools-runner + draios/jenkins-job-trigger-action + JENKINS_INTERNAL_URL / JENKINS_QA_API_USER / JENKINS_QA_API_TOKEN secrets. Co-Authored-By: Claude Opus 4.8 <noreply@anthropic.com>
Hammond95
changed the title
haresh-suresh
approved these changes
Jul 1, 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
2 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.
Proposed changes
Two related changes for the
linux-bench-dependencyimage (consumed bysecure-backend'scompliance-benchmark-runnerviaLINUX_BENCH_TAG), mirroring what was done for kube-bench (aquasecurity#50 + aquasecurity#51):1. Bump Go 1.25.10/1.25.9 → 1.25.11 (the CVE fix)
The dependency image embeds a
linux-benchbinary built with Go 1.25.10, failing the Sysdigsecure-components-vuln-checkpolicy on two HIGH, network-vector, fixable Go runtime CVEs:Verified by scanning the built
compliance-benchmark-runner: after bumpingKUBE_BENCH_TAGto the fixed1.2.0.7, the runner still reportedGo 1.25.10, traced to thelinux-benchbinary fromlinux-bench-dependency:1.1.0.14.Dockerfilegolang:1.25.10 → 1.25.11(builds thelinux-bench-dependencyimage viamake build-dependency-image-gar --file Dockerfile)Dockerfile_linux_arm64/Dockerfile_linux_s390xgolang:1.25.9 → 1.25.11go.modgo 1.25.9 → 1.25.11.github/workflows/build.yml/release.ymlgo-version: 1.25.9 → 1.25.112. Auto-trigger the dependency-image build on tag push
Adds
.github/workflows/build-dependency-image.yml: on push of a 4-part numeric dependency tag (e.g.1.1.0.15), it triggers thesecure/compliance/compliance-linux-benchJenkins job withTAG=<tag>, which builds and publisheslinux-bench-dependency:<tag>to GAR (registry tag == git tag, 1:1). Removes the manual Jenkins trigger step. Same pattern as kube-bench#51 (tools-runner+draios/jenkins-job-trigger-action).Requires before the workflow can run
The trigger step needs the org Jenkins secrets granted to this repo — done in draios/infra-config-github (companion PR). Also assumes the
tools-runnerself-hosted runner group is available todraios/linux-bench.Follow-up (after merge)
1.1.0.15tag → workflow publisheslinux-bench-dependency:1.1.0.15.secure-backend#57203 bumpsLINUX_BENCH_TAG=1.1.0.15→ compliance scan passes.Types of changes
🤖 Generated with Claude Code