Updating BoringSSL from upstream

Normal rollup to upstream HEAD

• Start a new feature branch, e.g. repo start upstream-update .
• Run ./update-upstream.sh. This will update all of src/ from upstream HEAD and generate a git commit on the current branch with a commit message which is a summary of all the upstream commits since the last time this script was run.
• Amend the commit message with any special notes: git commit --amend. This step is required even if you make no edits in order to add a Change-Id tag for Gerrit. TODO(prb) automate this.
• Test locally, i.e. build, flash and run MtsConscryptTestCases.
• Upload for review: repo upload --cbr -o nokeycheck .

Update to an upstream branch

(e.g. for FIPS)

As per the previous section but add the branch name to the update command line, e.g. ./update-upstream.sh fips-20250305