From 3b203adca31fe98f697e188ce86247f9b7d4121f Mon Sep 17 00:00:00 2001 From: Keegan Carruthers-Smith Date: Fri, 3 Jul 2026 14:31:19 +0200 Subject: [PATCH] fix: make esbuild action explicit about toolchains The --incompatible_auto_exec_groups flag requires Starlark actions to declare whether their executable/tools come from an action toolchain. This is not a Bazel default today, but it is exposed through strict preset configurations and is intended to catch rules that rely on implicit action toolchain inference. The esbuild action can run either a launcher selected from the esbuild toolchain or an explicit launcher attribute. Mark the action with toolchain = None so its action toolchain behavior is explicit without changing its inputs or execution model. --- esbuild/private/esbuild.bzl | 1 + 1 file changed, 1 insertion(+) diff --git a/esbuild/private/esbuild.bzl b/esbuild/private/esbuild.bzl index 7667ac2..9d7b36a 100644 --- a/esbuild/private/esbuild.bzl +++ b/esbuild/private/esbuild.bzl @@ -417,6 +417,7 @@ def _esbuild_impl(ctx): env = env, use_default_shell_env = True, executable = launcher, + toolchain = None, ) output_sources_depset = depset(output_sources)