chore: update dependencies and buildbarn components

[rszamszur]

This change updates all dependencies and Buildbarn components to the latest versions available as of 2026-03-21.

[moroten]

Thank you for the dependency update.

[rszamszur]

I noticed that toolchains_protoc doesn't include protoc v34.0 in its version map. It's also been deprecated and upstreamed into protobuf@33.4. I've updated the PR accordingly: https://github.com/buildbarn/bb-deployments/compare/58aae1c3d2e75ad54fc0ad2a2cb3062598b22377..adbc526415c1b5c392d4cf6f3ec97911c818df81

However, some other tests are still failing locally. I'll investigate tomorrow.

---

Edit:

The //tools/github_workflows:github_workflows target was failing to build because the output was renamed in the template in commit: buildbarn/bb-storage@267d619

[rszamszur]

@moroten The upstream bb-storage commit f49dccc added the flag --@bazel_tools//tools/test:incompatible_use_default_test_toolchain to workflows_template.libsonnet, from which the GitHub actions are rendered. However, this flag doesn't exist in Bazel 8, which this project still uses.

To workaround this, I've introduced a temporary patch for the bb-storage dependency. The patch can be removed after migrating to Bazel 9 (I'm willing to handle that in a follow-up PR).

Let me know what you think,
Have a good one!

[moroten]

I'm fine with a temporary patch unless you just go for Bazel 9 straight away. I'm fine either way.

[moroten]

@rszamszur There is another unpublished PR which has done more job on this. Please wait a bit with your work and let's see if that one get finished soon. There is some fix regarding PID1 and signal handling needed in bb-storage and maybe something more to get it all in place.

[moroten]

Forwarding termination signals in buildbarn/bb-storage#332 is needed to get CI to pass.

[rszamszur]

Updated:

• bb-storage to d0c6f2633bb9e199fc7285687cdd677660dc688c
• bb-remote-execution to e6ab874a1bc0cf690ae43f6f98bace2fb1f92cf2

[moroten]

I think the unpublished update is coming next week.

[moroten]

#187 has been merged, but it is still Bazel 8.

@rszamszur Is there something in this PR that should be kept? Would you like to upgrade to Bazel 9?

[rszamszur]

Closing in favor of #187

Would you like to upgrade to Bazel 9?
I'll give it a try in my spare time.