ci: Add CI guardrail for BoringSSL fork#5715
Merged
kaukabrizvi merged 10 commits intoaws:mainfrom Feb 17, 2026
Merged
Conversation
CarolYeh910
reviewed
Feb 9, 2026
CarolYeh910
approved these changes
Feb 12, 2026
dougch
approved these changes
Feb 16, 2026
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
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.
Goal
Resolves #5692 by adding a workflow that runs on pull requests to check the status of the BoringSSL fork used in integration tests.
Why
To add a layer of assurance that our integration tests run with a recent state of BoringSSL.
How
Added a script that compares the most recent commit date on the fork to the current date. The script fails if the time exceeds a set time threshold (currently set to 60 days) and is called from a github workflow.
Callouts
I am working on granting s2n-core access to the fork repository so that all team members can refresh the repository if it has gone stale.
Testing
I ran the workflow in this PR, once with the threshold at 180 days to observe the success case and once with the threshold at 1 day to observe the faliure case.
Related
Resolves #5692, the BoringSSL fork dependency was added in #5659.
By submitting this pull request, I confirm that my contribution is made under the terms of the Apache 2.0 license.