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

[BoringSSL] Update third_party/boringssl-with-bazel #33150

Merged
merged 7 commits into from May 17, 2023

Conversation

yijiem
Copy link
Member

@yijiem yijiem commented May 16, 2023

Change was created by the release automation script. See go/grpc-release

@yijiem yijiem added the release notes: no Indicates if PR should not be in release notes label May 16, 2023
@yijiem yijiem changed the title [Release 1.56] Update third_party/boringssl-with-bazel [BoringSSL] Update third_party/boringssl-with-bazel May 16, 2023
@yijiem yijiem marked this pull request as ready for review May 17, 2023 05:33
@yijiem yijiem enabled auto-merge (squash) May 17, 2023 05:33
@yijiem yijiem disabled auto-merge May 17, 2023 05:33
@yijiem yijiem enabled auto-merge (squash) May 17, 2023 16:04
@yijiem yijiem merged commit 004ddbe into grpc:master May 17, 2023
64 of 65 checks passed
@copybara-service copybara-service bot added the imported Specifies if the PR has been imported to the internal repository label May 17, 2023
wanlin31 pushed a commit that referenced this pull request May 18, 2023
Change was created by the release automation script. See go/grpc-release
@yijiem yijiem added release notes: yes Indicates if PR needs to be in release notes and removed release notes: no Indicates if PR should not be in release notes labels Jun 1, 2023
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
bloat/none imported Specifies if the PR has been imported to the internal repository lang/core lang/ObjC per-call-memory/neutral per-channel-memory/neutral release notes: yes Indicates if PR needs to be in release notes
Projects
None yet
Development

Successfully merging this pull request may close these issues.

None yet

2 participants