Error happened during detecting available versions for bazel-rules. Skipping this dependency kind...

[vorburger]

E.g. this contains Error happened during detecting available versions for bazel-rules. here:

[DefaultDispatcher-worker-1] INFO org.virtuslab.bazelsteward.config.repo.RepoConfigParser - Loading configuration from .bazel-steward.yaml
[main] INFO org.virtuslab.bazelsteward.core.common.CommandRunner - /usr/bin/git rev-parse --show-toplevel
[main] INFO org.virtuslab.bazelsteward.core.common.CommandRunner - /usr/bin/git checkout --quiet main
[main] INFO org.virtuslab.bazelsteward.app.App - Update suggestions (0):

[DefaultDispatcher-worker-1] INFO org.virtuslab.bazelsteward.core.common.CommandRunner - bazel mod graph --depth=1
[main] INFO org.virtuslab.bazelsteward.bzlmod.BzlModDependencyKind - Repositories [https://bcr.bazel.build/]
[main] INFO org.virtuslab.bazelsteward.bzlmod.BzlModDependencyKind - Dependencies: [gazelle 0.42.0, googleapis 0.0.0-20240819-fe8ba054a, protobuf 29.2, re2 2024-07-02.bcr.1, rules_apple 3.19.1, rules_go 0.51.0, rules_graalvm 0.11.1, rules_java 8.9.0, rules_jvm_external 6.7]
[main] INFO org.virtuslab.bazelsteward.app.App - Update suggestions (2):
protobuf 29.2 -> 29.3
rules_go 0.51.0 -> 0.53.0
[DefaultDispatcher-worker-3] INFO org.virtuslab.bazelsteward.core.common.CommandRunner - bazel build @all_external_repositories//:result.json
[main] WARN org.virtuslab.bazelsteward.app.App - Error happened during detecting available versions for bazel-rules. Skipping this dependency kind...
[main] WARN org.virtuslab.bazelsteward.app.App - Error details: bazel build @all_external_repositories//:result.json

Computing main repo mapping: 
Loading: 
Loading: 0 packages loaded
WARNING: Target pattern parsing failed.
ERROR: Skipping '@all_external_repositories//:result.json': No repository visible as '@all_external_repositories' from main repository
ERROR: No repository visible as '@all_external_repositories' from main repository
INFO: Elapsed time: 0.163s
INFO: 0 processes.
ERROR: Build did NOT complete successfully

[main] INFO org.virtuslab.bazelsteward.app.App - Update suggestions (0):

[DefaultDispatcher-worker-3] INFO org.virtuslab.bazelsteward.core.common.CommandRunner - bazel query @enola_maven//:outdated.repositories --output xml --noshow_progress
[DefaultDispatcher-worker-3] INFO org.virtuslab.bazelsteward.core.common.CommandRunner - bazel query @enola_maven//:outdated.artifacts --output xml --noshow_progress
[main] INFO org.virtuslab.bazelsteward.maven.MavenDependencyKind - Repositories [https://repo.maven.apache.org/maven2/, https://jitpack.io]/
[main] INFO org.virtuslab.bazelsteward.maven.MavenDependencyKind - Dependencies: [junit:junit 4.13.2, ...

It seems to come from here.

Is this perhaps something which doesn't work with "modern" empty WORKSPACE.bazel, and needs to be handled differently?

[lukaszwawrzyk]

Yes, it passes with --noenable_bzlmod --enable_workspace flags. I think we never tested it with bzlmod + workspace deps. In your case, given the file is empty, you can simply disable this kind

update-rules:
  - kinds: bazel-rules
    enabled: false

I think we don't want to invest into this scenario, given that workspace will be removed relatively soon and even rules_scala are about to support bzlmod :p