Repository navigation
Conversation
Ensure the Go binary embeds the exact semantic release version (runtime/debug.BuildInfo) rather than an untagged pseudo-version, so SBOM generators and vulnerability scanners accurately map the release. ai-assisted=yes
cf-foundation-community-automation
Bot
moved this to Inbox
in Foundational Infrastructure Working Group
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
1 participant
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.
Context
When Go compiles a binary using
go build, it embeds version information into the binary (runtime/debug.BuildInfo). If the build runs on an untagged checkout, Go generates a pseudo-version (e.g.v0.0.423-0.20261010100236-d3939dbbc728). When SBOM generators (such as Syft) catalog the compiled binary in stemcells, Black Duck and other vulnerability scanners fail to map the pseudo-version accurately and report security data against outdated versions.Changes
In
ci/tasks/build.sh, create a local git tagv${semver#v}before runninggo build. This ensures Go embeds the exact release version into the binary without altering the git history or release flow.