From 10586bdba7b1f6f4a8a84bdb2fbc5d6c4da939fa Mon Sep 17 00:00:00 2001 From: Carlos A Becker Date: Tue, 25 Oct 2022 22:16:06 -0300 Subject: [PATCH] docs: clarify lack of vcs info when building from proxy closes #3491 Signed-off-by: Carlos A Becker --- www/docs/cookbooks/build-go-modules.md | 3 ++- www/docs/customization/verifiable_builds.md | 4 ++++ 2 files changed, 6 insertions(+), 1 deletion(-) diff --git a/www/docs/cookbooks/build-go-modules.md b/www/docs/cookbooks/build-go-modules.md index 2e80f7c0a68..9d5e65d52ca 100644 --- a/www/docs/cookbooks/build-go-modules.md +++ b/www/docs/cookbooks/build-go-modules.md @@ -90,7 +90,8 @@ You can also use `go version -m my_program` to display the go module information ## Limitations 1. Extra files will still be copied from the current project's root folder and not from the proxy cache; -1. You can't build packages that are not contained in the main module. +1. You can't build packages that are not contained in the main module; +1. VCS info will not be available. ## More information diff --git a/www/docs/customization/verifiable_builds.md b/www/docs/customization/verifiable_builds.md index 2a7fd559a16..5e22f97eded 100644 --- a/www/docs/customization/verifiable_builds.md +++ b/www/docs/customization/verifiable_builds.md @@ -46,4 +46,8 @@ gomod: You can use `debug.ReadBuildInfo()` to get the version/checksum/dependencies of the module. +!!! warning + VCS Info will not be embedded in the binary, as in practice it is not being + built from the source, but from the Go Mod Proxy. + [vgo]: https://research.swtch.com/vgo-repro