Skip to content

Conversation

wouterj
Copy link
Member

@wouterj wouterj commented May 10, 2025

It took me ages to find this hidden bug.

When fetching the locked repository, Composer by default does not include dev packages. This means that conflicts for dev packages defined by Flex recipes were always completely ignored (like the phpunit/phpunit: <9.6 conflict in our symfony/phpunit-bridge recipe).

This creates big issues for my new PHPUnit recipe (symfony/recipes#1401), as the 10+ recipe is run for applications using PHPUnit 9.

@fabpot fabpot changed the base branch from 2.x to 1.x May 10, 2025 14:05
@fabpot fabpot closed this May 10, 2025
@fabpot fabpot force-pushed the check-dev-conflicts branch from 05bcffd to 5cc9859 Compare May 10, 2025 14:05
fabpot added a commit that referenced this pull request May 10, 2025
This PR was merged into the 2.x branch.

Discussion
----------

Always include locked dev packages

It took me ages to find this hidden bug.

When fetching the locked repository, Composer by default does not include dev packages. This means that conflicts for dev packages defined by Flex recipes were always completely ignored (like the `phpunit/phpunit: <9.6` conflict in our `symfony/phpunit-bridge` recipe).

This creates big issues for my new PHPUnit recipe (symfony/recipes#1401), as the 10+ recipe is run for applications using PHPUnit 9.

Commits
-------

05bcffd Always include locked dev packages
@fabpot
Copy link
Member

fabpot commented May 10, 2025

Merged in 2.x

@fabpot
Copy link
Member

fabpot commented May 10, 2025

Thank you so much @wouterj

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

2 participants