Repository navigation
Validate native CLI host values and fix production archive checks - #6
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
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.
The 1.0.3 production archive failed Plugin Check at the native WP-CLI subprocess boundary. This patch scopes documented PHPCS exceptions to argv-array execution and private pipe I/O, removes five broad package exclusions, and validates forwarded host environment tokens.
Commands retain shell-free execution and incremental stdout/stderr draining. Regression tests prove literal shell metacharacters, validated DNS/IP/ports and rejection of unsafe host values.
Validation: full PHP QA, 12 tests / 71 assertions; exact pinned Plugin Check source scan, zero findings. The mandatory hosted archive check remains enabled; publish a new immutable 1.0.4 tag and a freshly checked ZIP.