Open
Conversation
Contributor
Author
Branch automerge failureThis PR was configured for branch automerge. However, this is not possible, so it has been raised as a PR instead.
|
5727a71 to
b5ef569
Compare
bb85d54 to
c46ecf8
Compare
e4bf3d0 to
a7579ad
Compare
a7579ad to
324de4b
Compare
324de4b to
d8e8c5f
Compare
82aa8a5 to
da9f68d
Compare
da9f68d to
bfb4e95
Compare
bfb4e95 to
21ac59d
Compare
21ac59d to
b216fd9
Compare
b216fd9 to
a7af99d
Compare
a7af99d to
8e48e94
Compare
8e48e94 to
f394115
Compare
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
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.
This PR contains the following updates:
5.3→6.10Warning
Some dependencies could not be looked up. Check the warning logs for more information.
Release Notes
bazelbuild/rules_jvm_external (rules_jvm_external)
v6.10Compare Source
Please note The lock file format was changed in
rules_jvm_external5.1 and again in 6.10. 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.5.0 or Bazel 9.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
ba7310cby @ahumesky in bazel-contrib#1297amend_artifactfor explicit unset state by @JonathanPerry651 in bazel-contrib#1499COURSIER_SHA256environment variable by @albertocavalcante in bazel-contrib#1527New Contributors
Full Changelog: bazel-contrib/rules_jvm_external@6.9...6.10
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
v6.7Compare 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.5.0 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
New Contributors
Full Changelog: bazel-contrib/rules_jvm_external@6.6...6.7
v6.6Compare 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 5.4.1, Bazel 6.5.0, or Bazel 7 or above.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
Full Changelog: bazel-contrib/rules_jvm_external@6.5...6.6
v6.5Compare 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 5.4.1, Bazel 6.5.0, or Bazel 7 or above.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
@//labels with Bzlmod by @fmeum in bazel-contrib#1265New Contributors
Full Changelog: bazel-contrib/rules_jvm_external@6.4...6.5
v6.4Compare 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 5.4.1, Bazel 6.5.0, or Bazel 7 or above.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
aliasgenerated when usingbzlmodand themavenresolver by @shs96c in #1249pomclassifier isn't always downloaded by @shs96c in #1251Full Changelog: bazel-contrib/rules_jvm_external@6.3...6.4
v6.3Compare 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 5.4.1, Bazel 6.5.0, or Bazel 7 or above.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
maven.artifacttag example into the bzlmod readme. by @jin in #1195jvm_importto accept ajarparameter by @shs96c in #1242jvm_importandjava_exporttargets now include aPackageInfoprovider @shs96c in #1232New Contributors
Full Changelog: bazel-contrib/rules_jvm_external@6.2...6.3
v6.2Compare 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 5.4.1, Bazel 6.5.0, or Bazel 7 or above.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
pom.xmlfiles by @vinnybod in #1113rules_jvm_external's own dependencies by @honnix in #1133mavenextension as reproducible by @fmeum in #1141testonlyattribute to generated plugins by @rdesgroppes in #1142New Contributors
Full Changelog: bazel-contrib/rules_jvm_external@6.1...6.2
v6.1Compare 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 5.4.1, Bazel 6.5.0, or Bazel 7 or above.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
manifest_entriestojava_exportby @shs96c in #1050Configuration
📅 Schedule: Branch creation - At any time (no schedule defined), Automerge - At any time (no schedule defined).
🚦 Automerge: Enabled.
♻ Rebasing: Whenever PR is behind base branch, 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.