Use shared CI for assurance and fuzz workflows - #10
Merged
Merged
Conversation
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.
Use the shared CI policy for source assurance, platform and toolchain compatibility checks, smoke/nightly fuzz campaigns, and releases. The assurance script uses centrally supplied binaries in CI and retains its self-contained local fallback.
Preserve the 90% coverage gate, SQLite race tests, repeated benchmarks, Go 1.26.0/1.27.1 compatibility jobs, and failing fuzz seeds. Coverage and benchmark outputs are retained together in source-assurance-.
Validation: actionlint and caller contracts pass. The full assurance script passed with OPEN_SHIPS_CI=true and the shared tools, including race tests, 90.7% coverage, vulnerability scanning, and SQLite integration.
Depends on open-ships/ci#1. Every shared workflow is pinned to commit 95d4b3ed5452a99525c240688de146553e57cee0 so this PR can run before a v1.2.0 tag exists. Merge the shared policy PR first; update all caller pins if its reviewed commit changes.