Remove buildinfo package#34
Merged
Merged
Conversation
No longer needed: the dagger repo inlined its own copy (dagger/dagger#13508) and is moving to stamp VCS metadata into native build info directly. No consumers remain.
shykes
force-pushed
the
remove-buildinfo-package
branch
from
July 18, 2026 18:54
0f1460c to
a321d70
Compare
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.
buildinfowrappedruntime/debug.ReadBuildInfoso sandboxed builds — which have no.gitfor the Go toolchain's native VCS stamping to read — could inject commit/dirty/time metadata via-ldflags. It lived here as a standalone module to serve as a stable-ldflags -Xinjection point for the dagger repo and any other consumers.That rationale no longer holds: the dagger repo has inlined its own copy (dagger/dagger#13508), and the injection approach is being superseded by stamping directly into native build info. With no remaining consumers, keeping it in a separate repo is pure maintenance surface — so this removes it.