Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Bump Bazel from 4.0.0 to 4.1.0 #2024

Merged
merged 1 commit into from
May 28, 2021
Merged

Bump Bazel from 4.0.0 to 4.1.0 #2024

merged 1 commit into from
May 28, 2021

Conversation

nakabonne
Copy link
Member

What this PR does / why we need it:
v4.1.0 got released last week. This release includes bazelbuild/bazel#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 #1913

Does this PR introduce a user-facing change?:

NONE

@khanhtc1202
Copy link
Member

finally 🎉

@khanhtc1202
Copy link
Member

/approve

@pipecd-bot
Copy link
Collaborator

APPROVE

This pull request is APPROVED by khanhtc1202.

Approvers can cancel the approval by writing /approve cancel in a comment. Any additional commits also will change this pull request to be not-approved.

@pipecd-bot
Copy link
Collaborator

COVERAGE

Code coverage for golang is 32.38%. This pull request does not change code coverage.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

Successfully merging this pull request may close these issues.

Remove the workaround flag after bumping Bazel to greater than 4.0.0
3 participants