Skip to content
Permalink

Comparing changes

Choose two branches to see what’s changed or to start a new pull request. If you need to, you can also or learn more about diff comparisons.

Open a pull request

Create a new pull request by comparing changes across two branches. If you need to, you can also . Learn more about diff comparisons here.
base repository: symfony/flex
Failed to load repositories. Confirm that selected base ref is valid, then try again.
Loading
base: v2.5.0
Choose a base ref
...
head repository: symfony/flex
Failed to load repositories. Confirm that selected head ref is valid, then try again.
Loading
compare: v2.5.1
Choose a head ref
  • 2 commits
  • 2 files changed
  • 2 contributors

Commits on May 10, 2025

  1. Always include locked dev packages

    @wouterj
    wouterj committed May 10, 2025
    Configuration menu
    Copy the full SHA
    05bcffd View commit details
    Browse the repository at this point in the history

  2. bug #1044 Always include locked dev packages (wouterj) 

    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
    fabpot committed May 10, 2025
    Configuration menu
    Copy the full SHA
    62d5c38 View commit details
    Browse the repository at this point in the history
Loading