Boringssl upgrade #27710
Merged
Boringssl upgrade #27710
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
|
Just out of curiosity, why do we need this upgrade? I upgraded it to the latest a week ago; #27606. |
|
I'm the release manager for the gRPC 1.42 release, and upgrading boringssl is one of the release steps the week before the branch cut. If I'd known that you just upgraded it a week ago, I might not have bothered, but since I've already done this, we might as well get it merged. |
|
Known issues: #27603 The other failures are infrastructure issues. |
dennycd
pushed a commit
to dennycd/grpc
that referenced
this pull request
Oct 15, 2021
* update submodule boringssl-with-bazel with origin/main-with-bazel * update build files * generate boringssl prefix headers * update podspecs
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
3 participants
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.
No description provided.