Repository navigation
Define the 1.x contract and public release gates - #13
Merged
Merged
Conversation
brianvarskonst
marked this pull request as ready for review
September 30, 2026 17:45
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.
Runtime now defines the 1.x extension and configuration contract and adds
wp runtimebefore WordPress bootstrap. The WP-CLI bridge executes the existing standalone binary in a separate process, and Composer providesruntimealiases. Existing compatibility profiles stay functional and are deprecated for removal in 2.0.The change also validates persisted file formats, uses stable Kernel/QA dependencies, adds Linux/Windows/macOS minimum/latest Composer contracts, lowest-runtime dependency QA, a scheduled Composer compatibility check, PHP security analysis and signed, QA-gated release automation. Public documentation records the supported API, configuration defaults and platform limits.
The new platform tests also fix real portability defects: copying or moving a case alias cannot truncate/delete its own inode; Windows context filenames retain the required full prefix; trusted layout inputs are normalized without relaxing journal validation; Composer proxy ownership uses the same physical bin path as Composer, including Windows short paths. Unknown/tampered proxies remain protected.
Validation: full coding standards, PHPStan and 1,249 tests / 9,313 assertions passed with real database, WordPress and WP-CLI fixtures and no skips. The same full suite passed at the lowest supported production dependencies. Subsequent proxy, WP-CLI quiet/negated-option and Windows journal regressions pass. Real Demo source smoke passed 27 tests / 213 assertions and authenticated browser/root-route checks. Both Windows platform jobs pass after retaining file synchronization while documenting the unsupported directory-entry durability guarantee. The final full matrix is running at the current head. Starter #31 and Demo #51 already adopted 0.2.0 with reviewed download locks and green CI/smoke tests.
Release review also pins the exact verified annotated tag object through publication, preventing a different tag pointing to the same commit from passing the final check. A fresh full-history secret scan through the final implementation found no leaks across 76 scanned commits.
Final-head validation at
53161d4: all 16 checks pass. The integration job completes 1,253 tests / 9,329 assertions with--fail-on-skipped, followed by the isolated differential harness. All six platform/Composer combinations, lowest stable dependencies, QA, package installation, documentation, actionlint and security checks are green.Packagist registration remains a publication gate. Tags are verified against the pinned SSH signing key; GitHub's account-level Verified badge is optional. This PR prepares the beta contract milestone.