.bazelrc: Update 'strict_action_env' flag
For the rationale see the change in gerrit core [1].
IIUC:
- The reason that '--action_env=PATH' is required is npm (Issue 10372),
- which in turn was only needed because of PolyGerrit support,
- which was not available in earlier stable branches than stable-2.16
for this plugin.
- From stable-3.0 onwards, delete-project is a core plugin and support
for standalone builds were removed, and this Bazel flag isn't
necessary any longer as it's taken from the main gerrit project.
This means that when merging this upwards to stable-3.0 and beyond, this
can be ignored.
[1]: https://gerrit-review.googlesource.com/c/gerrit/+/238112
Change-Id: Idad3a41eabb868b3f1b0f7115a90223105d64ee9
diff --git a/.bazelrc b/.bazelrc
index 73fc9ea..f5c0ae3 100644
--- a/.bazelrc
+++ b/.bazelrc
@@ -1,4 +1,10 @@
build --workspace_status_command=./tools/workspace-status.sh
-build --experimental_strict_action_env
+
+# Standalone build compatbility with npm requires PATH on action_env (Issue 10372).
build --action_env=PATH
+
+# See https://github.com/bazelbuild/bazel/issues/7026. Remove when flag is
+# flipped in Bazel again.
+build --incompatible_strict_action_env
+
test --build_tests_only
