bazelbuild
publish-to-BCR setup
@bergsieker: I volunteered you to be a module maintainer :) it should be very low maintenance, but let me know if you would rather not.
We can cut a release after this gets merged and watch it show up in BCR. (Note that we'll need to attach a release archive -- I can do this part.)
hmm, maybe this is a good opportunity to actually split this module into several ones (one per language). For example, Bazel's own use of remote-apis requires the Java gRPC targets, which aren't currently in this repo. I'll probably send another change tomorrow.
hmm, maybe this is a good opportunity to actually split this module into several ones (one per language). For example, Bazel's own use of remote-apis requires the Java gRPC targets, which aren't currently in this repo. I'll probably send another change tomorrow.
Can this be done orthogonally to getting this into bcr? Reclient and remote-apis-sdks's usage of this module would be greatly simplified if we can get this deployed to bcr.
Sorry, I've been busy with managing Bazel's 8.0 release. Are you blocked on this change? I think you mentioned a few action items from your side in a previous email thread (including setting a new release schedule, etc). Are those completed already?
Sorry, I've been busy with managing Bazel's 8.0 release. Are you blocked on this change? I think you mentioned a few action items from your side in a previous email thread (including setting a new release schedule, etc). Are those completed already?
We've agreed to move to a monthly release model, skipping months where there are no (meaningful) commits). We're also moving to date-based versioning. Ideally we'll cut the first such release around next Tuesday. Is it better to get this in place before that release, or do we need to wait for that release and use it as a baseline for the first BCR release the following month?