46fe8fb8b4
This has a couple benefits: - we now use a .bazelversion file rather than package.json to pin the version of bazel we want. This means even if you install bazel on your computer rather than via yarn, you'll still get a warning if your bazel version is wrong. - you no longer end up downloading three copies of bazel due to bugs in both npm and yarn where they download all tarballs before checking the metadata to see which are usable on the local platform. - bazelisk correctly handles the tools/bazel trick for wrapping functionality, which we want to use to instrument developer build latencies PR Close #36078 |
||
|---|---|---|
| .. | ||
| BAZEL.md | ||
| CARETAKER.md | ||
| COMMITTER.md | ||
| DEBUG.md | ||
| DEBUG_COMPONENTS_REPO_IVY.md | ||
| DEVELOPER.md | ||
| GITHUB_PROCESS.md | ||
| NAMING.md | ||
| PR_REVIEW.md | ||
| PUBLIC_API.md | ||
| RELEASE_SCHEDULE.md | ||
| SAVED_REPLIES.md | ||
| TOOLS.md | ||
| TRIAGE_AND_LABELS.md | ||