Gazelle is a Bazel build file generator for Bazel projects. It natively supports Go and protobuf, and it may be extended to support new languages and custom rule sets.
Apache License 2.0
1.19k
stars
378
forks
source link
go_deps should expose resolved versions for all Go modules it Bazelizes, for external bookkeeping #1905
Does this issue reproduce with the latest releases of all the above?
Yes
What operating system and processor architecture are you using?
macOS Sonoma 14.5, arm64 (Apple M1 Max)
This isn't a bug but a feature request. I'd like the go_deps module extension to expose the mapping between every Go module it bazelizes and its resolved version. This would be extremely useful for external bookkeeping (for e.g. we can easily communicate to CI systems that rely on native package manager metadata, precisely what version of each Go module was used in the build).
I'll shortly create a sample PR demonstrating what we might need although I'm not claiming that it would the optimal mechanism to surface this data.
What version of gazelle are you using?
v0.38.0What version of rules_go are you using?
v0.49.0What version of Bazel are you using?
7.1.2Does this issue reproduce with the latest releases of all the above?
Yes
What operating system and processor architecture are you using?
macOS Sonoma 14.5, arm64 (Apple M1 Max)
This isn't a bug but a feature request. I'd like the
go_depsmodule extension to expose the mapping between every Go module it bazelizes and its resolved version. This would be extremely useful for external bookkeeping (for e.g. we can easily communicate to CI systems that rely on native package manager metadata, precisely what version of each Go module was used in the build).I'll shortly create a sample PR demonstrating what we might need although I'm not claiming that it would the optimal mechanism to surface this data.