Skip to content

docs: Clarify BCR (non)publishing, and document git_override tip #12135

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Open
wants to merge 1 commit into
base: master
Choose a base branch
from
Open
Changes from all commits
Commits
File filter

Filter by extension

Filter by extension

Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
14 changes: 14 additions & 0 deletions README.md
Original file line number Diff line number Diff line change
Expand Up @@ -216,6 +216,20 @@ and the [`java_proto_library`](https://bazel.build/reference/be/java#java_proto_
and `load("@io_grpc_grpc_java//:java_grpc_library.bzl", "java_grpc_library")` (from this project), as in
[this example `BUILD.bazel`](https://github.com/grpc/grpc-java/blob/master/examples/BUILD.bazel).

Note that [this project does not publish](https://github.com/grpc/grpc-java/issues/12055) the `grpc-java` module
to the Bazel Central Registry (BCR); and [the existing one](https://registry.bazel.build/modules/grpc-java) is by someone
else than this project's maintainers - and thus may well not contain latest versions. You can still use it like this:

```bazel
bazel_dep(name = "grpc-java", version = "1.73.0", repo_name = "io_grpc_grpc_java")

git_override(
module_name = "grpc-java",
remote = "https://github.com/grpc/grpc-java.git",
tag = "v1.73.0",
)
```

API Stability
-------------

Expand Down