Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

4.0 | Composer: set conflict directive #114

Closed
wants to merge 2 commits into from

Conversation

jrfnl
Copy link
Member

@jrfnl jrfnl commented Dec 2, 2023

Description

Sister-PR to #113 for the 4.0 branch.

Set conflict directive to prevent the Squiz version of the package and this package being installed together.

Ref:

@jrfnl jrfnl added this to the 4.0.0 milestone Dec 2, 2023
... to prevent the Squiz version of the package and this package being installed together.

Ref:
* https://getcomposer.org/doc/04-schema.md#conflict
@jrfnl jrfnl force-pushed the feature/4.0/composer-set-conflict-directive branch from 3758b0c to dc87f0f Compare December 6, 2023 01:17
@jrfnl
Copy link
Member Author

jrfnl commented Dec 6, 2023

Looks like this may not be needed after all - #135

@jrfnl jrfnl removed this from the 4.0.0 milestone Dec 6, 2023
@jrfnl
Copy link
Member Author

jrfnl commented Dec 6, 2023

Thank you @derrabus for your help and advise. The package rename has been reverted. The package will continue under its original name, so this is no longer relevant.

@jrfnl jrfnl closed this Dec 6, 2023
@jrfnl jrfnl deleted the feature/4.0/composer-set-conflict-directive branch December 6, 2023 23:30
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

Successfully merging this pull request may close these issues.

2 participants