fix: validate prepared SQL through typed wpdb receivers - #4
Merged
Merged
Conversation
brianvarskonst
marked this pull request as ready for review
October 2, 2026 10:12
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.
Prepared SQL checks previously recognized only literal
$wpdbreceivers, leaving SQL passed through typed connection properties unchecked. The new PHPStan rule follows typedwpdbreceivers, including nullable and union types, and distinguishes prepared values from documented trusted SQL-generation boundaries.Stable dependency constraints and export rules make the next package reproducible. The weekly canary pins the reviewed reusable workflow and tests current allowed dependencies. PHPCompatibility remains on an actually available stable release; the documentation states its PHP-version coverage limits.
Validation: full PHPCS/PHPStan/PHPUnit passed, 111 tests / 378 assertions; fresh stable-only Composer installation and full QA passed; native actionlint passed. Candidate version:
v1.1.1; no historical tag is changed.Part of the organization review remediation. This package precedes QA and the remaining library release train.