Chiebot-Mirror/grpc - grpc - Gitea: Git with a cup of tea

Tag: Branch: Tree: 122aa335f6

Author	SHA1	Message	Date
Esun Kim	1ce1159a75	[CI] Moved to Bazel 7 (#36105 ) Let's use Bazel 7 by default. Closes #36105 PiperOrigin-RevId: 617653203	8 months ago
Esun Kim	0703276770	[CI] Bazel upgrade (#36104 ) Upgraded Bazel as follows; - Bazel 6.4 to 6.5 - Bazel 7.0 to 7.1 Closes #36104 PiperOrigin-RevId: 616237591	9 months ago
Esun Kim	d77e5c0dd3	[Build] Dropped Bazel 5.x and Upgraded Bazel 6.4.0 (#34813 ) - Dropped Bazel 5.x support aligned with [Foundational C++ support policy: Bazel](https://opensource.google/documentation/policies/cplusplus-support). - Upgraded Bazel 6 to 6.4.0 (the latest) - Updated gRPC Bazel documentation to be aligned with the policy above.	1 year ago
Jan Tattermusch	d3548a3941	[bazel] Upgrade bazel repo-wide to 6.3.2 (#34088 ) - Upgrade bazel - Reduce the number of places where bazel version needs to be upgraded in future. - also make sure the list of bazel versions to test by bazelified tests is loaded from supported_versions.txt (it was hardcoded before). - ~~Try upgrading windows RBE build to bazel 6.3.2 as well.~~ The core idea: - the source of truth for supported bazel versions is in `bazel/supported_versions.txt` - the first version listed in `bazel/supported_versions.txt` is considered to be the "primary" bazel version and is going to be used in most places thoroughout the repo. - use templates to include the primary bazel version in testing dockerfiles and in a newly introduced `.bazelversion` files (which gets loaded by our existing `tools/bazel` wrapper). ~~Supersedes https://github.com/grpc/grpc/pull/33880~~	1 year ago