Add allow-plugins config value by Seldaek · Pull Request #10314 · composer/composer
…sting plugins impossible
…o enable/disable some packages, so we can suppress warnings for things we never want enabled, and add a way to update the config for the user if run interactively
Co-authored-by: Nils Adermann <naderman@naderman.de>
nicolas-grekas added a commit to symfony/skeleton that referenced this pull request
This PR was merged into the 4.4 branch. Discussion ---------- Add allow-plugins in the skeleton config Refs composer/composer#10314 For now, the default value in Composer is still to allow all plugins implicitly for BC. But the behavior will change in July 2022 to default to an empty list of allowed plugins. This PR has 2 effects: - it makes new project use the new Composer behavior directly instead of relying on the BC layer - it marks `symfony/flex` as an allowed plugin, as our skeleton is meant to be used with Flex The first point means that projects installing other composer plugins will need to mark them as allowed for them to run (but `composer update` running in an interactive shell will ask for that anyway) Commits ------- f757a29 Add allow-plugins in the skeleton config
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