Skip to content

chore: update BoringSSL to be08ef39#299

Closed
github-actions[bot] wants to merge 1 commit into
masterfrom
update-boringssl-be08ef39
Closed

chore: update BoringSSL to be08ef39#299
github-actions[bot] wants to merge 1 commit into
masterfrom
update-boringssl-be08ef39

Conversation

@github-actions

Copy link
Copy Markdown

Updates vendored BoringSSL to be08ef39e96191146b978ecbfd8eb8c3b50babb9 using tool/bump-boringssl-revision.sh.

This workflow is intentionally thin: it just provisions the environment, runs the script, and opens a PR if the script produced a diff.

@github-actions github-actions Bot added boringssl-update dependencies Pull requests that update a dependency file labels Jun 29, 2026
@google-cla

google-cla Bot commented Jun 29, 2026

Copy link
Copy Markdown

Thanks for your pull request! It looks like this may be your first contribution to a Google open source project. Before we can look at your pull request, you'll need to sign a Contributor License Agreement (CLA).

View this failed invocation of the CLA check for more information.

For the most up to date status, view the checks section at the bottom of the pull request.

@mosuem

mosuem commented Jul 17, 2026

Copy link
Copy Markdown
Collaborator

Closing as no CLA, re-opening once the workflow is migrated to use the dart bot and this repo is in labs/.

@mosuem mosuem closed this Jul 17, 2026
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

boringssl-update dependencies Pull requests that update a dependency file

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants