Skip to content

deps: Update dependency rules_jvm_external to v6.10#607

Open
ffortier wants to merge 1 commit into
mainfrom
renovate/rules_jvm_external-6.x
Open

deps: Update dependency rules_jvm_external to v6.10#607
ffortier wants to merge 1 commit into
mainfrom
renovate/rules_jvm_external-6.x

Conversation

@ffortier
Copy link
Copy Markdown
Owner

@ffortier ffortier commented Feb 5, 2026

This PR contains the following updates:

Package Type Update Change
rules_jvm_external bazel_dep minor 6.96.10

Release Notes

bazelbuild/rules_jvm_external (rules_jvm_external)

v6.10

Compare Source

Please note The lock file format was changed in rules_jvm_external 5.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_external requires 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.bazel file:

bazel_dep(name = "rules_jvm_external", version = "6.10")

To add dependencies, later in your MODULE.bazel file:

maven = use_extension("@​rules_jvm_external//:extensions.bzl", "maven")

maven.install(
    artifacts = [
        "org.seleniumhq.selenium:selenium-java:4.40.0",
    ],
    lock_file = "//:maven_install.json",
)

use_repo(maven, "maven")
Workspace-based builds

In your WORKSPACE file, add:

load("@​bazel_tools//tools/build_defs/repo:http.bzl", "http_archive")

RULES_JVM_EXTERNAL_TAG = "6.10"
RULES_JVM_EXTERNAL_SHA = "e5f83b8f2678d2b26441e5eafefb1b061826608417b8d24e5e8e15e585eab1ba"

http_archive(
    name = "rules_jvm_external",
    strip_prefix = "rules_jvm_external-%s" % RULES_JVM_EXTERNAL_TAG,
    sha256 = RULES_JVM_EXTERNAL_SHA,
    url = "https://github.com/bazel-contrib/rules_jvm_external/releases/download/%s/rules_jvm_external-%s.tar.gz" % (RULES_JVM_EXTERNAL_TAG, RULES_JVM_EXTERNAL_TAG)
)

load("@​rules_jvm_external//:repositories.bzl", "rules_jvm_external_deps")

rules_jvm_external_deps()

load("@​rules_jvm_external//:setup.bzl", "rules_jvm_external_setup")

rules_jvm_external_setup()

Then, later in your WORKSPACE file, you can pull in dependencies from a maven repository:

load("@​rules_jvm_external//:defs.bzl", "maven_install")

maven_install(
    artifacts = [
        "org.seleniumhq.selenium:selenium-java:4.38.0",
    ],
    repositories = [
        "https://repo1.maven.org/maven2",
    ],
    maven_install_json = "//:maven_install.json",
)
Using dependencies

In your BUILD.bazel file, reference the targets directly:

java_library(
    name = "example",
    exports = [
        "@​maven//:org_seleniumhq_selenium_selenium_java",
    ],
)

What's Changed

New Contributors

Full Changelog: bazel-contrib/rules_jvm_external@6.9...6.10


Configuration

📅 Schedule: (UTC)

  • 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.


  • If you want to rebase/retry this PR, check this box

This PR has been generated by Mend Renovate.

@ffortier
Copy link
Copy Markdown
Owner Author

ffortier commented Feb 5, 2026

⚠️ Artifact update problem

Renovate failed to update an artifact related to this branch. You probably do not want to merge this PR as-is.

♻ Renovate will retry this branch, including artifacts, only when one of the following happens:

  • any of the package files in this branch needs updating, or
  • the branch becomes conflicted, or
  • you click the rebase/retry checkbox if found above, or
  • you rename this PR's title to start with "rebase!" to trigger it manually

The artifact failure details are included below:

File name: undefined
Command failed: ./.github/renovate/post-upgrade.sh
+ bzl_opts=(--override_module=toolchains_llvm=./third_party/cpp/no_toolchains_llvm)
+ git diff --exit-code third_party/python/requirements.in
+ git diff --exit-code third_party/java/deps.MODULE.bazel
+ git diff --exit-code third_party/dotnet/paket.dependencies
+ git diff --exit-code deno.jsonc
+ git diff --exit-code third_party/deno/toolchains.MODULE.bazel
+ REPIN=1
+ bazel build --nobuild //... --override_module=toolchains_llvm=./third_party/cpp/no_toolchains_llvm
Computing main repo mapping: 
Computing main repo mapping: 
Loading: 
Loading: 2 packages loaded
Analyzing: 169 targets (84 packages loaded, 6 targets configured)
ERROR: /tmp/containerbase/cache/.cache/bazel/_bazel_ubuntu/1b5ffcdd61e73605eab60db158621164/external/rules_go+/go/private/rules/cgo.bzl:101:12: The CcInfo symbol has been removed, add the following to your BUILD/bzl file:

load("@rules_cc//cc/common:cc_info.bzl", "CcInfo")
ERROR: /tmp/containerbase/cache/.cache/bazel/_bazel_ubuntu/1b5ffcdd61e73605eab60db158621164/external/rules_go+/go/private/rules/cgo.bzl:102:39: The CcInfo symbol has been removed, add the following to your BUILD/bzl file:

load("@rules_cc//cc/common:cc_info.bzl", "CcInfo")
ERROR: /tmp/containerbase/cache/.cache/bazel/_bazel_ubuntu/1b5ffcdd61e73605eab60db158621164/external/rules_go+/go/private/rules/cgo.bzl:107:28: The CcInfo symbol has been removed, add the following to your BUILD/bzl file:

load("@rules_cc//cc/common:cc_info.bzl", "CcInfo")
ERROR: /tmp/containerbase/cache/.cache/bazel/_bazel_ubuntu/1b5ffcdd61e73605eab60db158621164/external/rules_go+/go/private/rules/cgo.bzl:109:29: The CcInfo symbol has been removed, add the following to your BUILD/bzl file:

load("@rules_cc//cc/common:cc_info.bzl", "CcInfo")
ERROR: /tmp/containerbase/cache/.cache/bazel/_bazel_ubuntu/1b5ffcdd61e73605eab60db158621164/external/rules_go+/go/private/rules/cgo.bzl:112:35: The CcInfo symbol has been removed, add the following to your BUILD/bzl file:

load("@rules_cc//cc/common:cc_info.bzl", "CcInfo")
ERROR: /tmp/containerbase/cache/.cache/bazel/_bazel_ubuntu/1b5ffcdd61e73605eab60db158621164/external/rules_go+/go/private/rules/cgo.bzl:115:36: The CcInfo symbol has been removed, add the following to your BUILD/bzl file:

load("@rules_cc//cc/common:cc_info.bzl", "CcInfo")
ERROR: /tmp/containerbase/cache/.cache/bazel/_bazel_ubuntu/1b5ffcdd61e73605eab60db158621164/external/rules_go+/go/private/rules/cgo.bzl:191:22: The CcInfo symbol has been removed, add the following to your BUILD/bzl file:

load("@rules_cc//cc/common:cc_info.bzl", "CcInfo")
ERROR: /tmp/renovate/repos/github/ffortier/mono/experiments/bforth/BUILD.bazel:10:12: While resolving toolchains for target //experiments/bforth:bforth (816f791): invalid registered toolchain '@go_toolchains//:all': while parsing '@go_toolchains//:all': error loading package '@@rules_go++go_sdk+go_toolchains//': at /tmp/containerbase/cache/.cache/bazel/_bazel_ubuntu/1b5ffcdd61e73605eab60db158621164/external/rules_go+/go/private/go_toolchain.bzl:22:6: at /tmp/containerbase/cache/.cache/bazel/_bazel_ubuntu/1b5ffcdd61e73605eab60db158621164/external/rules_go+/go/private/actions/archive.bzl:36:5: compilation of module 'go/private/rules/cgo.bzl' failed
ERROR: Analysis of target '//experiments/bforth:bforth' failed; build aborted
INFO: Elapsed time: 2.128s
INFO: 0 processes.
ERROR: Build did NOT complete successfully

@coderabbitai
Copy link
Copy Markdown
Contributor

coderabbitai Bot commented Feb 5, 2026

Note

Reviews paused

It looks like this branch is under active development. To avoid overwhelming you with review comments due to an influx of new commits, CodeRabbit has automatically paused this review. You can configure this behavior by changing the reviews.auto_review.auto_pause_after_reviewed_commits setting.

Use the following commands to manage reviews:

  • @coderabbitai resume to resume automatic reviews.
  • @coderabbitai review to trigger a single review.

Use the checkboxes below for quick actions:

  • ▶️ Resume reviews
  • 🔍 Trigger review
📝 Walkthrough

Walkthrough

Updated the rules_jvm_external Bazel module dependency from version 6.9 to 6.10 in third_party/java/toolchains.MODULE.bazel; no other modifications.

Changes

Cohort / File(s) Summary
Dependency Version Bump
third_party/java/toolchains.MODULE.bazel
Single-line change: bazel_dep(name = "rules_jvm_external", version = "6.9")version = "6.10".

Estimated code review effort

🎯 1 (Trivial) | ⏱️ ~2 minutes

Possibly related PRs

Poem

🐰 A tiny hop on module ground,
I nudged a number, quiet, sound.
Six dot nine leapt into six dot ten,
A hopeful tumble, then again.
Builds hum softly — rabbit grinned.

🚥 Pre-merge checks | ✅ 3
✅ Passed checks (3 passed)
Check name Status Explanation
Title check ✅ Passed The title accurately describes the main change: updating the rules_jvm_external dependency from version 6.9 to 6.10, which is directly reflected in the changeset.
Docstring Coverage ✅ Passed No functions found in the changed files to evaluate docstring coverage. Skipping docstring coverage check.
Description Check ✅ Passed Check skipped - CodeRabbit’s high-level summary is enabled.

✏️ Tip: You can configure your own custom pre-merge checks in the settings.

✨ Finishing Touches
🧪 Generate unit tests (beta)
  • Create PR with unit tests
  • Commit unit tests in branch renovate/rules_jvm_external-6.x

Thanks for using CodeRabbit! It's free for OSS, and your support helps us grow. If you like it, consider giving us a shout-out.

❤️ Share

Comment @coderabbitai help to get the list of available commands and usage tips.

Copy link
Copy Markdown
Contributor

@coderabbitai coderabbitai Bot left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Actionable comments posted: 1

🤖 Fix all issues with AI agents
In `@third_party/java/toolchains.MODULE.bazel`:
- Line 2: The PR bumped bazel_dep(name = "rules_jvm_external", version = "6.10")
but the lock file format changed; regenerate the maven_install.json lock by
running REPIN=1 bazel run `@maven//`:pin and commit the updated
maven_install.json, and while doing so verify the build to see if the reported
rules_android "label_list provider" initialization error reproduces—if it does,
update the rules_android dependency to a compatible version or pin a transient
fix before merging; ensure the updated lock file and any rules_android changes
are included in the same commit.

Comment thread third_party/java/toolchains.MODULE.bazel
@ffortier ffortier force-pushed the renovate/rules_jvm_external-6.x branch 18 times, most recently from 9943464 to 525a7f7 Compare February 12, 2026 21:20
@ffortier ffortier force-pushed the renovate/rules_jvm_external-6.x branch 9 times, most recently from 2139580 to f7ec45b Compare February 18, 2026 03:33
@ffortier ffortier force-pushed the renovate/rules_jvm_external-6.x branch 14 times, most recently from 6565e10 to 3f37cb5 Compare March 4, 2026 03:18
@ffortier ffortier force-pushed the renovate/rules_jvm_external-6.x branch 13 times, most recently from 09c0f2c to afc905c Compare March 11, 2026 05:42
@ffortier ffortier force-pushed the renovate/rules_jvm_external-6.x branch 2 times, most recently from 169ce88 to 89d593a Compare March 12, 2026 03:25
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants