Disable VCS metadata in Go build - #6607
Merged
vimtor merged 1 commit intoMar 18, 2026
Merged
Conversation
Add -buildvcs=false to the go build invocation in platform/scripts/build for the bridge binary. This prevents embedding VCS metadata into the output, avoiding build failures when VCS info is unavailable and improving reproducibility of the built artifact.
Contributor
Author
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.
Add -buildvcs=false to the go build invocation in platform/scripts/build for the bridge binary. This prevents embedding VCS metadata into the output, improving reproducibility of the built artifact.
Problem
This is another issue related to sst dev.
At the moment, the hash of the build bridge bootstrap binary changes with every commit. As a result, all Lambda functions are treated as changed after every SST release.
#6465 already reduced this to a single upload, but the S3 key for every Lambda is still changing, which can still slow deployments down.
Changes
Validation
I tested this by switching between commits, with this change the hash stays stable, without it changed every time.
@vimtor this is the other problem i mentioned in my #6465.