Name | Date | Size | #Lines | LOC | ||
---|---|---|---|---|---|---|
.. | - | - | ||||
BUILD.bazel | H A D | 25-Apr-2025 | 808 | 28 | 24 | |
README.md | H A D | 25-Apr-2025 | 1.1 KiB | 22 | 14 |
README.md
1# Releasing rules_java 2 31. Update version in [MODULE.bazel](/MODULE.bazel) and merge it 42. Build the release running `bazel build //distro:rules_java-{version}` 53. Prepare release notes running `bazel build //distro:relnotes` 64. Create a new release on GitHub 75. Copy/paste the produced `relnotes.txt` into the notes. Adjust as needed. 86. Upload the produced tar.gz file as an artifact. 9 10------ 11 12**Note:** Steps 2-6 have been automated. Trigger a new build of the [rules_java release pipeline](https://buildkite.com/bazel-trusted/rules-java-release/). Set the message to "rules_java [version]" (or anything else), and leave the commit and branch fields as is. 13 14A new release will be created [here](https://github.com/bazelbuild/rules_java/releases) -- edit the description as needed. A PR will be submitted against the [bazel-central-registry](https://github.com/bazelbuild/bazel-central-registry) repo. 15 16rules_java 6.5.0 example: 17 18- Build: https://buildkite.com/bazel-trusted/rules-java-release/builds/1 19- Release: https://github.com/bazelbuild/rules_java/releases/tag/6.5.0 20- BCR PR: bazelbuild/bazel-central-registry#818 21 22