From 1d2d75303704d3a5ec6631863e484dc3c3a94779 Mon Sep 17 00:00:00 2001 From: Ryo Nakao Date: Fri, 28 May 2021 14:36:22 +0900 Subject: [PATCH] Bump Bazel from 4.0.0 to 4.1.0 (#2024) **What this PR does / why we need it**: [v4.1.0](https://github.com/bazelbuild/bazel/releases/tag/4.1.0) got released last week. This release includes https://github.com/bazelbuild/bazel/pull/12882, which fixes what we were facing; no longer needed to come with the workaround. I've confirmed that it works fine without passing the workaround flag `--features=-debug_prefix_map_pwd_is_dot`. **Which issue(s) this PR fixes**: Fixes https://github.com/pipe-cd/pipe/issues/1913 **Does this PR introduce a user-facing change?**: ```release-note NONE ``` This PR was merged by Kapetanios. --- .bazelrc | 4 ---- .bazelversion | 2 +- 2 files changed, 1 insertion(+), 5 deletions(-) diff --git a/.bazelrc b/.bazelrc index afb376b4dd..eb1bf2035e 100644 --- a/.bazelrc +++ b/.bazelrc @@ -25,10 +25,6 @@ build --define DOCKER_REGISTRY=localhost:5000 # https://github.com/bazelbuild/rules_docker/issues/842 build --host_force_python=PY2 -# TODO: Remove the workaround flag after bumping Bazel to greater than 4.0.0 -# Workaround for this: https://github.com/bazelbuild/bazel/issues/12905 -build --features=-debug_prefix_map_pwd_is_dot - # CI configurations build:ci --define DOCKER_REGISTRY=gcr.io/pipecd build:ci --remote_http_cache=https://storage.googleapis.com/pipecd-bazel-cache diff --git a/.bazelversion b/.bazelversion index fcdb2e109f..ee74734aa2 100644 --- a/.bazelversion +++ b/.bazelversion @@ -1 +1 @@ -4.0.0 +4.1.0