[5.6] Move tightenco/collect to 'conflict' #23379
Merged
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.
According to this issue: composer/composer#7129, since
tighenco/collect
is not an illuminate's subtree, it must be set as a conflict and not a replacement.Tested this change in a framework clone, and this this is what happens now, when installing spatie/crawler:
Currently, if we try to install
spatie/crawler 4
along withlaravel/framework 5.6
, we get this: