CI: Enroll LudicrousDB connection integration - #92
Merged
Merged
Conversation
Bind LudicrousDB’s live WordPress/MySQL smoke test to its reviewed SHA-256 contract and schedule the multisite integration matrix from central policy.
JJJ
force-pushed
the
contracts/ludicrousdb-integration
branch
from
September 20, 2026 12:06
0ad9217 to
f550644
Compare
JJJ
marked this pull request as ready for review
September 20, 2026 17:15
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
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.
LudicrousDB now has a focused live database smoke test in stuttter/ludicrousdb#221. This enrolls that exact reviewed payload in the central WordPress integration matrix.
The matrix follows LudicrousDB’s existing compatibility contract: multisite on WordPress 6.4 with PHP 7.4, current stable WordPress with PHP 8.4, and WordPress trunk with PHP 8.4. I ran all three combinations against the branch payload before adding its SHA-256 contract here.
This should merge after the repository PR so the declared file is present on LudicrousDB’s default branch.