Navigation Menu

Skip to content

Commit

Permalink
docs: clarify lack of vcs info when building from proxy
Browse files Browse the repository at this point in the history
closes #3491

Signed-off-by: Carlos A Becker <caarlos0@users.noreply.github.com>
  • Loading branch information
caarlos0 committed Oct 26, 2022
1 parent 1447ac8 commit 10586bd
Show file tree
Hide file tree
Showing 2 changed files with 6 additions and 1 deletion.
3 changes: 2 additions & 1 deletion www/docs/cookbooks/build-go-modules.md
Expand Up @@ -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

Expand Down
4 changes: 4 additions & 0 deletions www/docs/customization/verifiable_builds.md
Expand Up @@ -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

0 comments on commit 10586bd

Please sign in to comment.