You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
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.
The text was updated successfully, but these errors were encountered:
What version of gazelle are you using?
v0.38.0
What version of rules_go are you using?
v0.49.0
What version of Bazel are you using?
7.1.2
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.
The text was updated successfully, but these errors were encountered: