Repository navigation
Prepare Runtime 0.1.0 and verify recovery compatibility - #9
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.
Prepare Runtime 0.1.0 with completed contract acceptance, bounded Composer recovery dependencies and practical deployment guidance.
~2.10.3. Exercise real WPackagist recovery with Composer 2.10.3 and a pinned upcoming library revision, recording both CLI and library versions.Validation: full local QA passes with 1,063 tests, 7,411 assertions and no skipped tests; PHPStan max and PHPCS pass. All 407 contract mappings and 251 differential cases pass. Documentation checks cover 66 Markdown files, 40 options and 157 constants. Starter/demo QA, kernel commands, login/browser checks and normal-versus-no-plugins replays pass (607/728 artifacts). Both Composer CI matrix entries pass.
Publish
v0.1.0after the final checks and merge, then replace the consumer branch requirements with exact0.1.0requirements in separate reviewed PRs.