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
{{ message }}
This repository was archived by the owner on Jun 20, 2025. It is now read-only.
In #15, I switched from hardcoding Bazel 1.0.1 in the .travis.yml config to installing Bazel via their published APT repository. This has the advantage that we pick up the latest stable release on every PR, but we lose build reproducibility -- reverting and resending a previous PR can result in an entirely different result if we pick up a new version of Bazel.
We should create create an auto-roller that periodically checks for new Bazel versions, sends a PR to upgrade the linux and macos versions, and lands it if all tests pass.
In #15, I switched from hardcoding Bazel 1.0.1 in the .travis.yml config to installing Bazel via their published APT repository. This has the advantage that we pick up the latest stable release on every PR, but we lose build reproducibility -- reverting and resending a previous PR can result in an entirely different result if we pick up a new version of Bazel.
We should create create an auto-roller that periodically checks for new Bazel versions, sends a PR to upgrade the linux and macos versions, and lands it if all tests pass.