From bebe34a5b13ea2c1877cbba4e2d8be61a908cef7 Mon Sep 17 00:00:00 2001 From: Keith Smiley Date: Thu, 14 May 2026 17:13:20 -0700 Subject: [PATCH] Switch to ge_same_major for is_tool_configuration_public If you test with commits this is annoying since there's a long range that doesn't have them that are not that old. I don't know the best way to handle this besides being more strict --- features.bzl | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/features.bzl b/features.bzl index a28387c..2d16914 100644 --- a/features.bzl +++ b/features.bzl @@ -179,7 +179,7 @@ _rules = struct( # Whether ctx.configuration.is_tool_configuration is public API # https://github.com/bazelbuild/bazel/commit/84c0253add3784b75ff08b6d049a7f152c7b7532 - is_tool_configuration_public = ge_same_major("8.7.0") or ge_same_major("9.1.0") or ge("10.0.0-pre.20260329.2"), + is_tool_configuration_public = ge_same_major("8.7.0") or ge_same_major("9.1.0") or ge_same_major("10.0.0-pre.20260329.2"), # Internal only, don't use outside rules_java, rules_python & rules_shell. # TODO: Use a larger version range after cherry-picking