Use the latest rules_erlang & rules_elixir (backport #11506) #11511
Conversation
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
michaelklishin
force-pushed
the
mergify/bp/v3.13.x/pr-11506
branch
from
a37c97e to
a0ccb99
Compare
(cherry picked from commit 3465eef)
michaelklishin
force-pushed
the
mergify/bp/v3.13.x/pr-11506
branch
from
a0ccb99 to
6ce5109
Compare
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Which fixes issues with erlang built inside of bazel. While we don't this currently, this avoids confusion if we start doing that again later.
This is an automatic backport of pull request #11506 done by Mergify.