Update dependency rules_jvm_external to v6.9 #93
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.
This PR contains the following updates:
6.7->6.9Release Notes
bazelbuild/rules_jvm_external (rules_jvm_external)
v6.9Compare Source
Please note The lock file format was changed in
rules_jvm_external5.1. If you update and repin your dependencies, your lock file will use the new format.Usage
This version of
rules_jvm_externalrequires Bazel 6.5.0, Bazel 7.6.1 or Bazel 8.This release requires Java 11 or above to run, both as the host JDK and the build and tool JDK.
Bzlmod
If you are using Bazel 7 or above, in your
MODULE.bazelfile:To add dependencies, later in your
MODULE.bazelfile:Workspace-based builds
In your
WORKSPACEfile, add:Then, later in your
WORKSPACEfile, you can pull in dependencies from a maven repository:Using dependencies
In your
BUILD.bazelfile, reference the targets directly:What's Changed
packagein gradle versions files properly by @shs96c in bazel-contrib#1419installtag has duplicate coordinates by @shs96c in bazel-contrib#1422force_versionfor root module artifact to take precedence by @shs96c in bazel-contrib#1423@package_metadatainfo forjvm_importtargets by @Yannic in bazel-contrib#1410RJE_UNSAFE_CACHEis set by @shs96c in bazel-contrib#1448New Contributors
Full Changelog: bazel-contrib/rules_jvm_external@6.8...6.9
v6.8Compare Source
Please note The lock file format was changed in
rules_jvm_external5.1. If you update and repin your dependencies, your lock file will use the new format.Usage
This version of
rules_jvm_externalrequires Bazel 6.5.0, Bazel 7.6.1 or Bazel 8.This release requires Java 11 or above to run, both as the host JDK and the build and tool JDK.
Bzlmod
If you are using Bazel 7 or above, in your
MODULE.bazelfile:To add dependencies, later in your
MODULE.bazelfile:Workspace-based builds
In your
WORKSPACEfile, add:Then, later in your
WORKSPACEfile, you can pull in dependencies from a maven repository:Using dependencies
In your
BUILD.bazelfile, reference the targets directly:What's Changed
outdatedfor BOMs by @cheister in bazel-contrib#1341copy_fileinstead of agenruleto link things in the generated workspaces by @shs96c in bazel-contrib#1361fail_if_repin_requiredtoTrueby default by @shs96c in bazel-contrib#1371New Contributors
Full Changelog: bazel-contrib/rules_jvm_external@6.7...6.8
Configuration
📅 Schedule: Branch creation - At any time (no schedule defined), Automerge - At any time (no schedule defined).
🚦 Automerge: Disabled by config. Please merge this manually once you are satisfied.
♻ Rebasing: Whenever PR becomes conflicted, or you tick the rebase/retry checkbox.
🔕 Ignore: Close this PR and you won't be reminded about this update again.
This PR was generated by Mend Renovate. View the repository job log.