Skip to content

Disable VCS metadata in Go lambda and bridge task builds - #6976

Open
MaTTaDox wants to merge 1 commit into
anomalyco:devfrom
MaTTaDox:fix/buildvcs-go-lambdas
Open

Disable VCS metadata in Go lambda and bridge task builds#6976
MaTTaDox wants to merge 1 commit into
anomalyco:devfrom
MaTTaDox:fix/buildvcs-go-lambdas

Conversation

@MaTTaDox

@MaTTaDox MaTTaDox commented Aug 20, 2026

Copy link
Copy Markdown
Contributor

Follow-up to #6607
Go records vcs.revision/vcs.time into every main package, so a new commit alone changes the binary's bytes

  • pkg/runtime/golang/golang.go — user Go lambdas
  • platform/scripts/build — the bridge task

Verified: two builds at one commit are byte-identical, -buildvcs=false changes the bytes, gofmt clean, package compiles.

Follow-up to anomalyco#6607, which added -buildvcs=false to the bridge lambda but
left the remaining two Go builds stamped.

Go records vcs.revision/vcs.time into every main package, so a new commit
alone changes the bytes of the built binary. For user Go lambdas the zip
hash therefore changes on every commit, and since a function's code object
is keyed by that hash (assets/<name>-code-<hash>.zip), every deploy
replaces every code object and updates every function - even when no Go
source changed. For the bridge task it needlessly busts the image cache.

Co-Authored-By: Claude Opus 5 <noreply@anthropic.com>
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant