You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Fix wrappers issues in Bazelisk 1.28.0 on Windows (#762)
* Rework wrappers probation order according to #761:
* probe tools/bazel.exe on Windows after platform-specific executables and before Windows-specific scripts
* probe tools/bazel on Windows with lowest priority (for backward compatibility only)
Update core_test.go and README.md to reflect the changes.
* Bazel 8.4.2 is absent on https://downloads.sourceforge.net/project/bazel.mirror, use Bazel 8.5.1 instead in the test `test_path_is_consistent_regardless_of_base_url` from bazelisk_test.sh
Copy file name to clipboardExpand all lines: README.md
+9-5Lines changed: 9 additions & 5 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -219,11 +219,15 @@ Bazelisk will try to run a Bazel wrapper from the `tools` directory if present,
219
219
220
220
Bazelisk looks for the following wrappers, in order:
221
221
222
-
*`tools/bazel.<OSNAME>-<ARCH>`: An executable that's OS- and platform-specific.
223
-
*`tools/bazel.<ARCH>`: An executable that's platform-specific (for cases where your project only supports one operating system anyway).
224
-
*`tools/bazel`: An executable or shell script.
225
-
*`tools/bazel.ps1`: A PowerShell script on Windows.
226
-
*`tools/bazel.bat`: A batch file on Windows.
222
+
*`tools/bazel.<OSNAME>-<ARCH>[.exe]`: An executable that's OS- and platform-specific
223
+
*`tools/bazel.<ARCH>[.exe]`: An executable that's platform-specific (for cases where your project only supports one operating system anyway)
224
+
*`tools/bazel[.exe]`: An executable or shell script
225
+
*`tools/bazel.ps1`: A PowerShell script on Windows
226
+
*`tools/bazel.bat`: A batch file on Windows
227
+
228
+
where `.exe` extension is required on Windows.
229
+
230
+
Also, on Windows `tools/bazel` is allowed with the lowest priority. It is not recommended and can cause issues, but it's supported for backward compatibility.
227
231
228
232
This behavior can be disabled by setting the environment variable `BAZELISK_SKIP_WRAPPER` to any value (except the empty string) before launching Bazelisk.
0 commit comments