bazelbuild / bazelbuild/remote-apis
Bazel version to use to run hooks/pre-commit unclear
- Dominant language
- Go
- Stars
- 445
- Forks
- 141
- PR merge metrics
- No merged PRs in 30d
Description
Running a current Bazel version (e.g. 6.3.2) fails with errors related to the deprecation of @bazel_tools//platforms:windows
I got it to run using bazelisk and a .bazelversion file specifying 5.3.2 as version. This is not ideal, probably it should work with Bazel 6 and newer and the version should be specified in a .bazelversion file, removing usage of deprecated packages as well
Contributor guide
Research direction
Start with hooks/pre-commit and reproduce the failure using a current Bazel version such as 6.3.2, then compare it with bazelisk using the reported 5.3.2 version. Done means the hooks run with Bazel 6 or newer, the version is specified in .bazelversion, and the deprecated @bazel_tools//platforms:windows usage is removed.
Written by the indexing model from the issue text.
Assessment
- Domain
- build-system
- Issue type
- Bug
- Difficulty
- 3/5
- Estimated time
- 1-2 days
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 35/100