Fabian Meumertzheim

@Wyverald Friendly ping

After the release of 7.1.0, I will add `reproducible`.

rules_go and gazelle both have proper support for Bzlmod by now. The warnings you see are emitted by old versions that are still fetched during version resolution but not used....

@cameron-martin Are you sure that's true? As far as I know the `args` parameter is treated specially for all rules, but `env` is only for native rules.

@redsun82 You could use `bazel_features`, which provides you a way to test for certain global symbols: https://github.com/bazel-contrib/bazel_features/tree/main?tab=readme-ov-file#accessing-globals `RunEnvironmentInfo` is already supported: https://github.com/bazel-contrib/bazel_features/blob/443861571a389ddc16d17690ab8e46ee87b4ea57/private/globals.bzl#L5

I really like this pattern. It's probably going to be most useful for C/C++ projects, which rarely use the Publish to BCR app. But suggesting it in the add module...

The correct solution is to use the settings in this file instead of OS settings (plus `@platforms//cpu` constraints if necessary): https://github.com/bazelbuild/rules_cc/blob/main/cc/compiler/BUILD

> Yes, that is part of the solution. How do I get the cross product of compiler and cpu? One option would be to use skylib's [selects.config_setting_group](https://github.com/bazelbuild/bazel-skylib/blob/main/docs/selects_doc.md#selectsconfig_setting_group) to define selectable...

I'm pretty sure this is caused by a race in skymeld that isn't related to caching and can't be worked around reliably: https://github.com/bazelbuild/bazel/issues/22073

@alexeagle Did you mean to close this with #445?