| commit | 581609f62863fdfef499027f157a42a0887d6759 | [log] [tgz] |
|---|---|---|
| author | Florian Weikert <fwe@google.com> | Wed Jul 12 15:29:47 2023 +0200 |
| committer | GitHub <noreply@github.com> | Wed Jul 12 15:29:47 2023 +0200 |
| tree | 4ac3619a8d65f04c5af348631a1b4e409be50fbe | |
| parent | 4badc93e0f2913828746712782f9d9e8d5949ef4 [diff] |
Add temporary rules_go bazel_dep to restore CI (#18912) https://github.com/bazelbuild/bazel-central-registry/pull/725 broke bazel CI asynchronously by yanking rules_go@0.34.0, listed as a dependency on BCR of grpc@1.48.1. From BCR recommendation on https://github.com/bazelbuild/bazel-central-registry/pull/733, specifying a rules_go@0.39.1 should coerce transitive selection through Minimum Version Selection (and bypass gazelle@0.27.0, also yanked). Closes #18828. PiperOrigin-RevId: 545205842 Change-Id: I574fc46b7c09e72e6d70ef77be726897aacc4358 Co-authored-by: George Gensure <werkt0@gmail.com>
{Fast, Correct} - Choose two
Build and test software of any size, quickly and reliably.
Speed up your builds and tests: Bazel rebuilds only what is necessary. With advanced local and distributed caching, optimized dependency analysis and parallel execution, you get fast and incremental builds.
One tool, multiple languages: Build and test Java, C++, Android, iOS, Go, and a wide variety of other language platforms. Bazel runs on Windows, macOS, and Linux.
Scalable: Bazel helps you scale your organization, codebase, and continuous integration solution. It handles codebases of any size, in multiple repositories or a huge monorepo.
Extensible to your needs: Easily add support for new languages and platforms with Bazel's familiar extension language. Share and re-use language rules written by the growing Bazel community.
Follow our tutorials:
To report a security issue, please email security@bazel.build with a description of the issue, the steps you took to create the issue, affected versions, and, if known, mitigations for the issue. Our vulnerability management team will respond within 3 working days of your email. If the issue is confirmed as a vulnerability, we will open a Security Advisory. This project follows a 90 day disclosure timeline.
See CONTRIBUTING.md
