Repository navigation
#13: Drop the paratest conflict pin (Impex) - #14
Merged
jayjfletcher merged 4 commits intoOct 28, 2026
Merged
Conversation
…es and verify Drop the brianium/paratest conflict pin and require pestphp/pest ^5.3.4, which brings paratest ^7.27.4. Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
…e composer.json edit in the job worktree Remove the brianium/paratest conflict pin and require pestphp/pest ^5.3.4, which brings paratest ^7.27.4 with the parallel fix. Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
jayjfletcher
deleted the
ring-master/2026-10-28-0130-drop-paratest-conflict-pin
branch
October 28, 2026 06:00
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.
Risk: low
What changed
composer.jsononly: theconflictkey (brianium/paratest >=7.26.1) is removed and thepestphp/pestdev constraint is raised from^5.3.1to^5.3.4. No code, config or test changes.composer.lockis gitignored, so it is not part of the diff.Why
The conflict pin was a temporary workaround for a paratest bug that broke
pest --parallel. Pest 5.3.4 pulls in a fixed paratest (7.27.4), so the pin can go. The^5.3.4floor is what guarantees the fixed paratest in CI, which resolves dependencies fresh.Look at
composer.json:34: thepestphp/pestfloor^5.3.4; this is the only guard against resolving a broken paratest.composer.json:166: theconflictblock is gone and therepositoriesarray now ends the file; check the JSON is still well formed.Acceptance criteria
conflictkey: thecomposer.jsondiff.pestphp/pest^5.3.4:composer.json; installed v5.3.4.composer why-not brianium/paratest 7.27.4reports no blocker.composer testexits 0 (phpstan 0 errors, pint, type coverage 100%).composer testrunstest:unit(pest --parallel): 363/363 tests passed.git diff --name-only main...branchlists onlycomposer.json.Risks
This changes a dev dependency only, with no runtime or consumer impact (Roster and Showroom unaffected). CI resolves dependencies fresh, so transitive versions could differ from the local lock; the
^5.3.4floor limits that.Nits: none.
Closes #13
🤖 Generated with Claude Code