Yun Peng

This is implemented now: https://github.com/bazelbuild/bazelisk#--bisect

I'm closing this one since bazel docker images are already published to gcr.io/bazel-public/bazel for every new Bazel version

@yogurtearl SGTM, sent https://github.com/bazelbuild/bazel/pull/17113 We also have documentation in our release process: https://github.com/bazelbuild/continuous-integration/blob/master/docs/release-playbook.md#push-new-docker-image

This is on downstream projects owners' responsibility now.

The Windows issue has been fixed in https://github.com/bazelbuild/continuous-integration/issues/1845, and I just deployed the fix to the trusted VMs. Usually the publish bazel binary is way faster than the postsubmit, so...

I don't think there is any internal policy for this. Let's update to reflect the reality.

SG, I'll add [vogelsgesang](https://github.com/vogelsgesang) as a maintainer for this project.

> sorry, I didn't realize we were already in the examples repo... Np! ;D @alexeagle Any idea on how to address this flaky failure?

@shs96c Are `maven.install` with the same `name` resolved together or separately? How do you recommend to address the warning message? /cc @Wyverald

Not really, it was added as a patch file at https://github.com/bazelbuild/bazel-central-registry/blob/918ea9ff0a8c5d3f8719c84c2109c5a25631fc47/modules/protobuf/21.7/patches/add_module_dot_bazel.patch#L37, we can make a BCR patch version for protobuf to fix this issue.