chore: update BoringSSL submodule and bindings#10
Open
richard-ramos wants to merge 2 commits into
Open
Conversation
richard-ramos
force-pushed
the
automation/update-boringssl-submodule
branch
from
July 14, 2026 21:29
fd4b691 to
b3ea07c
Compare
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
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
1 participant
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.
Summary
Updates the
boringsslsubmodule tofba4f6f340428584ba0caccd9ba9520a60944827, regeneratesboringssl.nim, and bumps theboringssl.nimblepatch version.Verification
./build.shnimble installnimble test --styleCheck:off --verbose --debugThis PR is generated after the corresponding
vacp2p/boringsslupstream sync PR has been merged.