MODULE.bazel.lock update failure when bumping Stardoc dep from 0.7.0 to 0.7.1

[calebzulawski]

I am upgrading stardoc from 0.7.0 to 0.7.1 and get the following warning when updating MODULE.bazel.lock:

$ bazel mod deps --lockfile_mode=update
WARNING: The module extension @@rules_jvm_external~//:extensions.bzl%maven produced an invalid lockfile entry because it referenced @@[unknown repo '' requested from @@rules_jvm_external~]. Please report this issue to its maintainers.

MODULE.bazel.lock ends up broken:

$ bazel mod deps --lockfile_mode=error
ERROR: MODULE.bazel.lock is no longer up-to-date because: The repo mappings of certain repos used by the extension 'ModuleExtensionId{bzlFileLabel=@@rules_jvm_external~//:extensions.bzl, extensionName=maven, isolationKey=Optional.empty}' have changed. Please run `bazel mod deps --lockfile_mode=update` to update your lockfile. Type 'bazel help mod' for syntax and help.

I am using Bazel 7.4.0. Thanks!

[tetromino]

I can reproduce the failure:

mkdir x
cd x
echo 'bazel_dep(name = "stardoc", version = "0.7.0")' > MODULE.bazel
USE_BAZEL_VERSION=7.4.0 bazelisk mod deps
sed -e 's/0.7.0/0.7.1/' -i MODULE.bazel
USE_BAZEL_VERSION=7.4.0 bazelisk mod deps --lockfile_mode=update
USE_BAZEL_VERSION=7.4.0 bazelisk mod deps --lockfile_mode=error

Result: mod deps --lockfile_mode=update prints WARNING: The module extension @@rules_jvm_external~//:extensions.bzl%maven produced an invalid lockfile entry because it referenced @@[unknown repo '' requested from @@rules_jvm_external~]. Please report this issue to its maintainers., and mod deps --lockfile_mode=error fails.

@Wyverald - any suggestions for what is happening here?

[tetromino]

This breakage appears only with Bazel 7.4.0 (reproducer works fine in Bazel 7.3.2)

[fmeum]

This is ultimately an issue in r_j_e that should be fixed by bazel-contrib/rules_jvm_external#1265. The warning comes from bazelbuild/bazel@8cee5f5. I recall that it didn't result in failures when I tried it on r_j_e a while back, but that may have changed in the meantime.

[calebzulawski]

Thank you for looking into this! I'll hold off upgrading for now.

[chickenandpork]

I ran into this problem; I found that putting a redundant dependency in my MODULE.bazel fixed:

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

I don't need rules_jvm_external directly, but by placing this dependency, it overrides the 6.1 in stardoc's MODULE.bazel file:

stardoc/MODULE.bazel

Line 10 in 46fd77a

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

Really, version 6.5 is available, but I found you really need to get off 6.1. Something with rules_jvm_external-6.1 fights with Bazel-7.4

If this release that mitigates is almost shipping, it's probably too late, but if you're stuck, claiming an unnecessary direct dependency unblocked me.