Repository navigation
Fix unpacking packs leaving their dev dependencies in the "packages" section of composer.lock - #1132
Merged
Merged
Conversation
…section of composer.lock
nicolas-grekas
force-pushed
the
unpack-dev-lock
branch
from
October 29, 2026 17:22
cbec7bc to
aa7e755
Compare
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.
Found while testing the next release. After
composer req webapp, the dev dependencies of the packs (phpunit, maker-bundle...) stayed in thepackagessection of composer.lock, socomposer install --no-devinstalled them. Flex now moves the packages that onlyrequire-devneeds topackages-dev, like Composer does on the nextcomposer update.