You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
as composer does not know anything about extra.symfony.require the command composer outdated results in a wrong output if the developer wants to stick with symfony lts.
being on symfony/console 3.4.1 should show an available update to 3.4.24 but not to 4.2.5 if extra.symfony.require is set to 3.4.*.
symfony/flex v1.2.0 v1.2.1 Composer plugin for Symfony
symfony/polyfill-apcu v1.10.0 v1.11.0 Symfony polyfill backporting apcu_* functions to lower PHP versions
symfony/polyfill-mbstring v1.10.0 v1.11.0 Symfony polyfill for the Mbstring extension
symfony/yaml v3.4.23 v3.4.24 Symfony Yaml Component
as extra.symfony.require is a symfony feature i suspected that the issue at composer/composer will be closed. so maybe this can be handled in flex.
Closing this because I don't think we wanna support such custom flags, and as discussed with the Flex folks, the need for this Flex feature is something we are trying to fix entirely in Composer 2, so I really don't want to add custom support for it in Composer now.
@nicolas-grekas thanks, already have seen that. wouldn't say conflicting would say "boolable" expectations. a way to solve this would be to add a flag for this.
composer outdated
to respectextra.symfony.require
(lts) composer/composer#8084 composer outdated -D don't work #436as composer does not know anything about
extra.symfony.require
the commandcomposer outdated
results in a wrong output if the developer wants to stick with symfony lts.being on symfony/console 3.4.1 should show an available update to 3.4.24 but not to 4.2.5 if
extra.symfony.require
is set to3.4.*
.My
composer.json
:composer create-project symfony/skeleton:~3.4.0 my_project
When I run this command:
I get the following output:
it would be nice to have the following output:
as
extra.symfony.require
is a symfony feature i suspected that the issue at composer/composer will be closed. so maybe this can be handled in flex.composer/composer#8084 (comment)
The text was updated successfully, but these errors were encountered: