Repository navigation
#4: Drop the paratest conflict pin - #5
Merged
jayjfletcher merged 1 commit intoOct 28, 2026
Merged
Conversation
…p the paratest conflict Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
jayjfletcher
deleted the
ring-master/2026-10-28-0117-drop-paratest-conflict-pin
branch
October 28, 2026 06:53
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
Dependencies only, in
composer.json: thepestphp/pestrequirement goes from^5.3.1to^5.3.4, and theconflictblock that blockedbrianium/paratest >=7.26.1is removed. Nothing else changed: no source, tests, config or docs.composer.lockis gitignored, so it is not in the diff.Why
The conflict pin was temporary. Removing it and requiring Pest
^5.3.4(which bringsbrianium/paratest ^7.27.4) lines Polycart up with the rest of the suite (campaign #1; Keystone PR #8 did the same).Look at
composer.json:30: the Pest constraint bump to^5.3.4.composer.json:158-162: theconflictblock is gone and therepositoriesarray now closes the file.Acceptance criteria
conflictentry forbrianium/paratestcomposer.jsonhas noconflictkeypestphp/pest ^5.3.4composer.json:30^7.27.4, pest>=5.3.4composer show: paratest v7.27.4 (lock is gitignored)composer validatepassescomposer testpasseslint:checkand ringside check green--parallelpest --parallel: 246 passedmain:composer.jsononlyRisks
--with-dependenciesmay have moved other transitive dev packages; the full suite passes. Consumers are unaffected (dev tooling only).Nits: none.
Closes #4
🤖 Generated with Claude Code