Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Jump to bottom

MODULE.bazel and REPO.bazel are not supported #502

Closed
crncnnr opened this issue Oct 2, 2023 · 0 comments · Fixed by #503
Closed

MODULE.bazel and REPO.bazel are not supported #502

crncnnr opened this issue Oct 2, 2023 · 0 comments · Fixed by #503

Comments

@crncnnr
Copy link
Contributor

crncnnr commented Oct 2, 2023 •
edited
Loading

As of Bazel 6.3.0, MODULE.bazel and REPO.bazel are also considered workspace boundaries. Bazelisk currently does not search for these, so in situations where either is present but WORKSPACE.bazel or WORKSPACE is absent, it will fail to find the workspace root and any relative .bazeliskrc or .bazelversion.
@crncnnr crncnnr mentioned this issue Oct 2, 2023
Merged
@mering mering mentioned this issue May 13, 2024
Open
copybara-service bot pushed a commit to google/bazel-common that referenced this issue Dec 17, 2024
@cpovirk
Bump versions of Bazel and some deps.
f7ad8bf 
This was prompted by the fact that my build used Bazel 8.0.0 when I didn't want it during cl/706839076 because I was running an [old](bazelbuild/bazelisk#502) version of Bazelisk. I fixed that by upgrading Bazelisk, but I figured I might as well update Bazel, too.

Along the way, I noticed this:

```
WARNING: For repository 'rules_java', the root module requires module version rules_java@7.12.1, but got rules_java@8.6.1 in the resolved dependency graph. Please update the version in your MODULE.bazel or set --check_direct_dependencies=off
```

So I upgraded `rules_java`, too, and `rules_jvm_external` while I was in the area.

RELNOTES=n/a
PiperOrigin-RevId: 707067355
@copybara-service copybara-service bot mentioned this issue Dec 17, 2024
Merged
copybara-service bot pushed a commit to google/bazel-common that referenced this issue Dec 17, 2024
@cpovirk
Bump versions of Bazel and some deps.
0aa5acb 
This was prompted by the fact that my build used Bazel 8.0.0 when I didn't want it during cl/706839076 because I was running an [old](bazelbuild/bazelisk#502) version of Bazelisk. I fixed that by upgrading Bazelisk, but I figured I might as well update Bazel, too.

Along the way, I noticed this:

```
WARNING: For repository 'rules_java', the root module requires module version rules_java@7.12.1, but got rules_java@8.6.1 in the resolved dependency graph. Please update the version in your MODULE.bazel or set --check_direct_dependencies=off
```

So I upgraded `rules_java`, too, and `rules_jvm_external` while I was in the area.

RELNOTES=n/a
PiperOrigin-RevId: 707159453
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees
No one assigned
Labels
None yet
Projects
None yet
Milestone
No milestone
Development

Successfully merging a pull request may close this issue.

Support MODULE.bazel and REPO.bazel
1 participant
@crncnnr