Bump dependencies, update release_prep.sh, docs
#1745
Conversation
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Updates a few dependencies, enables `release_prep.sh` to handle tags with or without a `v` prefix, and updates `//specs2:specs2` for `rules_java` 8.12.0. Fixes bazel-contrib#1741. - Go: 1.24.2 => 1.24.3 - `google-common-protos`: 2.55.3 => 2.57.0 - `jline`: 3.29.0 => 3.30.3 - `protobuf`: 30.2 => 31.0 - `protobuf-java`: 4.30.2 => 4.31.0 - `rules_go`: 0.54.0 => 0.54.1 - `rules_java`: 8.11.0 => 8.12.0 - `rules_python`: 1.4.0 => 1.4.1 - `util-interface`: 1.10.11 => 1.11.0 Also: - Touches up `test_reproducibility.sh` slightly and fixes documentation errors pointed out privately by @gergelyfabian. - Updates `test_scala_import_source_jar.sh` to use `bazel query` via the new `target_file_location` helper to get the srcjar path. - Renames `_print_error_msg` to `fail` in `test_helper.sh` and updates it to return nonzero. - Adds `bazel_features_deps()` to `WORKSPACE` and a commented out `--repositories_without_autoloads` line to `.bazelrc` for `rules_java` 8.12.0 `WORKSPACE` builds. --- This is to keep dependencies up to date with the latest versions. Updating `test_scala_import_source_jar.sh` to use `bazel query` became necessary because: - Switching from running under Bzlmod to running under `WORKSPACE` would break. - Removing the repo to force it to regenerate caused `last_green` Bazel runs to break. This wouldn't only break this test, but it broke _all_ tests until running `bazel clean --expunge`. `last_green` Bazel seems to hold onto state, even across `bazel shutdown`, such that it doesn't notice that it needs to regenerate a deleted repo.
- `grpc`: 1.72.0 => 1.73.0 - `jline`: 3.30.3 => 3.30.4 - `platforms`: 0.0.11 => 1.0.0 - `protobuf`: 31.0 => 31.1 - `protobuf-java`: 4.31.0 => 4.31.1
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Description
Updates a few dependencies, enables
release_prep.shto handle tags with or without avprefix, and updates//specs2:specs2forrules_java8.12.0. Fixes #1741.google-common-protos: 2.55.3 => 2.57.0grpc: 1.72.0 => 1.73.0jline: 3.29.0 => 3.30.4platforms: 0.0.11 => 1.0.0protobuf: 30.2 => 31.1protobuf-java: 4.30.2 => 4.31.1rules_go: 0.54.0 => 0.54.1rules_java: 8.11.0 => 8.12.0rules_python: 1.4.0 => 1.4.1util-interface: 1.10.11 => 1.11.0Also:
Touches up
test_reproducibility.shslightly and fixes documentation errors pointed out privately by @gergelyfabian.Updates
test_scala_import_source_jar.shto usebazel queryvia the newtarget_file_locationhelper to get the srcjar path.Renames
_print_error_msgtofailintest_helper.shand updates it to return nonzero.Adds
bazel_features_deps()toWORKSPACEand a commented out--repositories_without_autoloadsline to.bazelrcforrules_java8.12.0WORKSPACEbuilds.Motivation
This is to keep dependencies up to date with the latest versions.
Updating
test_scala_import_source_jar.shto usebazel querybecame necessary because:Switching from running under Bzlmod to running under
WORKSPACEwould break.Removing the repo to force it to regenerate caused
last_greenBazel runs to break. This wouldn't only break this test, but it broke all tests until runningbazel clean --expunge.last_greenBazel seems to hold onto state, even acrossbazel shutdown, such that it doesn't notice that it needs to regenerate a deleted repo.