rules_proto release build fails with wrong bazel-cache

[meteorcloudy]

https://github.com/bazelbuild/rules_proto/actions/runs/9520256013/job/26245280441

ERROR: error loading package under directory '': error loading package '~/.cache/bazel-repo/bazel/_bazel_runner/43914acf8bee29fb1d82f3e3dee22a49/external/bazel_tools/src/java_tools/buildjar/java/com/google/devtools/build/buildjar/jarhelper': Unable to find package for @@[unknown repo 'rules_java' requested from @@]//java:defs.bzl: The repository '@@[unknown repo 'rules_java' requested from @@]' could not be resolved: No repository visible as '@rules_java' from main repository.

This error is not reproducible locally from rules_proto @ bazelbuild/rules_proto@8df2b70

The previous run was with 7.1.1 and this one is with Bazel 7.2.0, therefore I suspect the wrong cache was used in the build.

[meteorcloudy]

@alexeagle Does my assumption make any sense?

[meteorcloudy]

/cc @comius

[meteorcloudy]

Maybe it's related to bazelbuild/bazel#16937 where XDG_CACHE_HOME is now respected by Bazel.

[meteorcloudy]

.github/.github/workflows/release_ruleset.yaml

Lines 40 to 41 in b134b73

	# Bazelisk will download bazel to here.
	XDG_CACHE_HOME: ~/.cache/bazel-repo

Looks like XDG_CACHE_HOME was only meant for Bazelisk previously.

[alexeagle]

Ah nice! Thanks for tracking that down.

[alexeagle]

https://github.com/bazel-contrib/.github/pull/13/files fixed this by switching this reusable workflow to use https://github.com/bazel-contrib/setup-bazel

rules_proto is still on v5 of this repo, so it missed that upgrade v5...v6

I'll update rules_proto and also check why it isn't getting regular updates from Renovate.