jalogut / magento2-deployer-plus Goto Github PK

It seems it's trying to cd into src, while already in src:

 $ php vendor/bin/dep build -vvv
 ➤ Executing task build
 ➤ Executing task files:remove-generated
 [localhost] > cd . && (cd src && rm -rf generated/*)
 [localhost] < sh: 1: cd:
 [localhost] < can't cd to src
 In Process.php line 250:
                                                                 
   [Symfony\Component\Process\Exception\ProcessFailedException]  
   The command "cd . && (cd src && rm -rf generated/*)" failed.  
                                                                 
   Exit Code: 2(Misuse of shell builtins)                        
                                                                 
   Working directory: /builds/mystore/magento-sandbox/src   
                                                                 
   Output:                                                       
   ================                                              
                                                                 
                                                                 
   Error Output:                                                 
   ================                                              
   sh: 1: cd: can't cd to src                                    

I added this piece of code that fails myself here: https://github.com/jalogut/magento2-deployer-plus/pull/34/files (at the time I had tested Magento being in the root project dir, and it would have worked).

What's the recommended way of fixing this?

Simply changing

cd {{magento_dir}} && rm -rf generated/*

into

rm -rf generated/* (how would you know for sure you're in the right directory?)

or instead doing something like

cd {{release_path}}/{{magento_dir}} && rm -rf generated/*

Using docker image markoshust/magento-php:7.4-fpm I'm getting this error.

Fatal error: require(): Failed opening required 'recipe/common.php' (include_path='phar:///data/vendor/deployer/dist/dep/bin/../:.:/usr/local/lib/php') in /data/vendor/jalogut/magento2-deployer-plus/recipe/magento_2_2_5.php on line 13

The fix is to change require to require_once, also for files magento_2_2.php and magento_2_1.php.

Try:
docker run --volume ${PWD}:/data --workdir /data -it markoshust/magento-php:7.4-fpm vendor/bin/dep build -vvv

During our recent deployments we were facing the issue, that running bin/magento module:enable resp. bin/magento module:disable on the server after a deployer deployment crushes the whole page.
The error message said, that specific proxies could not be found and debugging a bit further we found out, that the generated folder was completely empty.
Checking #29 and magento/magento2#23251 we found out, that this is default Magento behavior to remove the generated folder for these commans. This happens in \Magento\Setup\Console\CompilerPreparation::handleCompilerEnvironment.
So obviously the problem is, that the folder is not properly regenerated again.
We used some approaches of the issues mentioned above and found out the following:

• Removing the generated folder from composer.json solves the issue
• running composer dump-autoload between deployment and bin/magento module:enable also solves the issue
• Running 'composer dump-autoload --optimize --apcu` (see #51) after deployment does NOT solve the issue

So it seems as if composer stops Magento from regenerating the generated folder somehow if these flags are set.
I assume that this happens because composer already throws the error before Magento is ready again.
Please be so kind and take a look at it. I hope this is generally reproducible. Maybe it makes sense to think again about #51

@jalogut In this commit b4c4960#diff-208cd8f19512e36ea5e04343f5d39c1d you disabled crontab:update command. Do you plan to fix it or may be you have ideas how to do it?

Sometimes I get strange errors from deployer, for example:

In Client.php line 103:
                                                                        
  The command "rm -rf ~/shared/./var/cache" failed.                     
                                                                        
  Exit Code: 1 (General error)                                          
                                                                        
  Host Name: production                                                 
                                                                        
  ================                                                      
  rm: cannot remove '/var/www/shared/./var/cache': Directory not empty

How is it possible that a force remove directory command fails? Isn't that the purpose of the command, is it? 😂

With the upgrade to symfony/console from 4.1.11 to 4.1.12
magento2-deployer-plus will fail, because of the type declaration introduced there and the missing description in magento2-deployer-plus.

/**
     * Sets the description for the command.
     *
     * @return $this
     */
    public function setDescription(string $description)
    {
        $this->description = $description;
        return $this;
    }

I'll do a pull request in a while...

Best regards,
Willi

My node_modules directory is +/- 160mb in size and it is included in the build artifact. Magento doesn't need this directory in production. Can we ignore it for the artifact?

What is the usage or use-cases for "deploy:override_shared" ?

Thanks

Just got this error on a running production server when trying to load any page.
Fatal error: Uncaught Magento\Framework\Exception\FileSystemException: The directory "/srv/releases/20180723163849/var/cache" cannot be deleted Warning!rmdir(/srv/releases/20180723163849/var/cache): Not a directory in /srv/releases/20180723163849/vendor/magento/framework/Filesystem/Driver/File.php:410 Stack trace: #0 /srv/releases/20180723163849/vendor/magento/framework/Filesystem/Directory/Write.php(174): Magento\Framework\Filesystem\Driver\File->deleteDirectory('/srv/releases/2...') #1 /srv/releases/20180723163849/vendor/magento/framework/Code/GeneratedFiles.php(97): Magento\Framework\Filesystem\Directory\Write->delete('var/cache') #2 /srv/releases/20180723163849/vendor/magento/framework/App/ObjectManagerFactory.php(110): Magento\Framework\Code\GeneratedFiles->cleanGeneratedFiles() #3 /srv/releases/20180723163849/vendor/magento/framework/App/Bootstrap.php(208): Magento\Framework\App\ObjectManagerFactory->create(Array) #4 /srv/releases/20180723163849/vendor/magento/framework/App/Bootstrap.php(123): Magento\Framework\App\ in /srv/releases/20180723163849/vendor/magento/framework/Filesystem/Driver/File.php on line 410

Something is causing Magento to try to delete the cache folder but it gives up because it's a symlink. The code that triggers this is in magento/framework/Code/GeneratedFiles.php whenever the .regenerate file exists in /var. Not sure what created it but it seem just part of the normal magento operations.

We may have to do something else with var/cache or modify the code to do rm var/cache/*

We keep running into permission issues after a deployment, and, while permissions are set correctly when creating the archive, it seems that they're not retained when extracting the archive.

Permissions are set correctly here: https://github.com/jalogut/magento2-deployer-plus/blob/master/recipe/magento_2_1/files.php#L20

But are not retained here: https://github.com/jalogut/magento2-deployer-plus/blob/master/recipe/magento_2_2/artifact.php#L30

I think a -p flag is needed: https://www.gnu.org/software/tar/manual/html_node/Setting-Access-Permissions.html#SEC82

I just thought I'd post here first before creating a PR, because I find it strange I'm only running into this issue now (after having used this for years).

It could be that I'm only running into this issue now because of different umask settings, and that most writable directories are shared between deployments anyway (and so setting perms once manually would fix it for good). On top of that, some directories don't need to be writable, such as vendor, pub/static (other than bug #13225) and app/etc, unless you're in developer mode and would like to change env.php through the admin).

I use git-deployment, so Deployer checks out a branch on the remote server. When using config:remove-dev-modules, this removes the dev-modules on my local machine which causes two problems:

1. The changed file is never sent to the remote server, so I still get the error bin/magento setup:db:status for which this function was designed.
2. In theory I could have checked out a branch in which more or less dev-modules are enabled, so just sending the local file to remote can cause problems.

This is my first time using Deployer, so I don't know what are the possibilities to solve this. I can think of two solutions:

1. config:remove-dev-modules should run on the server instead of running locally. Maybe this can be done using a replace with sed: sed -i '/<module>/d' ./app/etc/config.php

2. Download deploy.sh and ./app/etc/config.php from remote, replace locally and send the replaced document back to remote.

If I can be of any assistance to solve this issue, please let me know.

Is this project still maintained? Seems to gone quiet for the last 10 months.

I haven't tested it, but apparently composer dumpautoload -o --apcucan be run after DI compile to speed up PHP class lookups. Might be worth looking into.

"File system is a bottleneck - make sure composer is optimized and class map is generated after setup di compile. Refer to this tweet of mine:"

https://twitter.com/IvanChepurnyi/status/1179280000400465920

Hi

I have started using this package for deploying my magento 2 application.

However, as many time I run dep deploy staging command, it clone the repository again and again. Is this needed? Shouldn't it just git pull?

Cloning into '/home/public_html/releases/20200821073703'...
Enumerating objects: 32141, done.
Counting objects: 100% (32141/32141), done.
Delta compression using up to 4 threads
Compressing objects: 100% (16152/16152), done.
Writing objects: 100% (32141/32141), done.
Total 32141 (delta 10212), reused 32141 (delta 10212)
Updating files: 100% (16694/16694), done.

How to skip clone on every deployment?

This change has a side effect that causes an error if app/etc/config.php contains anything that looks like a variable to Deployer: f8615cf

The issue is that the whole contents of the config file is passed as part of an argument to run():

    run("cat <<EOF > {{release_path}}/$configFile $updatedConfigEof");

Deployer parses the argument.

This fails if the file contains dumped configuration with CMS variables, e.g. address templates:

            'address_templates' => [
                'html' => '{{depend prefix}}{{var prefix}} {{/depend}}{{var firstname}} {{depend middlename}}{{var middlename}} {{/depend}}{{var lastname}}{{depend suffix}} {{var suffix}}{{/depend}}{{depend firstname}}<br />{{/depend}}{{depend company}}{{var company}}<br />{{/depend}}{{if street1}}{{var street1}}{{depend street2}} {{var street2}}{{/depend}}<br />{{/if}}{{depend street3}}{{var street3}}<br />{{/depend}}{{depend street4}}{{var street4}}<br />{{/depend}}{{if city}}{{var city}},  {{/if}}{{if region}}{{var region}}, {{/if}}{{if postcode}}{{var postcode}}{{/if}}<br />{{var country}}<br />{{depend telephone}}T: <a href="tel:{{var telephone}}">{{var telephone}}</a>{{/depend}}{{depend fax}}<br />F: {{var fax}}{{/depend}}{{depend vat_id}}<br />VAT: {{var vat_id}}{{/depend}}'
            ]

In this case:

[Deployer\Exception\ConfigurationException]
 Configuration parameter `/depend` does not exist.

Well, actually i'm not big fan of "building" the app on the target server : The "build / deploy-artifact" approach makes more sense to me.

Only issue is that the build actually packages the current application version (local).

Actually the standard Deployer "deploy" can handle branch and tag options...

I think that would make sense to enhance the "build" task to grab (git clone) a specific branch / tag version and package it. Then the "deploy-package" would accept an archive parameter to deploy this specific archive.

This way a tagged version artifact could be deployed on staging server, then, exactly same archive could be deployed to production.

Deploying a developper snapshot version archive (what the tools do right now) would just be a particular scenario of the "archive" deployment mecanism.

Something I've noticed when building an artifact locally is if you're in developer mode, the artifact is built using the symlinks of your local environment. This casuses broken symlinks to be pushed to the remote.

I've been doing this to get around this issue:

// Put into production mode for artifact generation
task('mode:production', '{{bin/php}} {{current_path}}/{{magento_bin}} deploy:mode:set production -s')->once();
before('deploy:vendors', 'mode:production');

// Back to developer mode after artifact generation
task('mode:developer', '{{bin/php}} {{current_path}}/{{magento_bin}} deploy:mode:set developer -s')->once();
after('artifact:package', 'mode:developer');

Symlinks are set by the value for view_preprocessed in app/etc/di.xml:

<virtualType name="developerMaterialization" type="Magento\Framework\App\View\Asset\MaterializationStrategy\Factory">
    <arguments>
        <argument name="strategiesList" xsi:type="array">
            <item name="view_preprocessed" xsi:type="object">Magento\Framework\App\View\Asset\MaterializationStrategy\Symlink</item>
            <item name="default" xsi:type="object">Magento\Framework\App\View\Asset\MaterializationStrategy\Copy</item>
        </argument>
    </arguments>
</virtualType>

Which causes files in pub/static/adminhtml/Magento/backend/en_GB to be symlinks. I'm guessing symlinks are used in other places but this was the main issue for as it was breaking assets for the admin area.

Not sure if anyone else has had this issue and have any other solutions?

Here's what am trying to do:

• I have two seperate magento2.2.7 instances on the same server
• One am using as my dev instance and other one as staging
• I installed the deployment tool on my dev instance, so that what ever changes I make on my dev instance i'd be able to deploy it on my staging server

Here's what I did

1. composer require "jalogut/magento2-deployer-plus"
2. cp vendor/jalogut/magento2-deployer-plus/deploy.php.sample_2_2_5 deploy.php ( as am using 2.2.7 version of Magento )

That's how my deploy.php looks like

<?php

namespace Deployer;

require 'vendor/jalogut/magento2-deployer-plus/recipe/magento_2_2_5.php';

// Use timestamp for release name
set('release_name', function () {
    return date('YmdHis');
});

// Magento dir into the project root. Set "." if magento is installed on project root
set('magento_dir', '');
// [Optional] Git repository. Only needed if not using build + artifact strategy
set('repository', '');
// Space separated list of languages for static-content:deploy
set('languages', 'en_US');

set('magento_bin', 'bin/magento');

set('shared_files', ['/var/www/staging/app/etc/env.php']);
// OPcache configuration
task('cache:clear:opcache', 'sudo systemctl reload php-fpm');
after('cache:clear', 'cache:clear:opcache');

// Build host
localhost('build');

// Remote Servers 
host('dev_master')
    ->hostname('68.xxx.xxx.124') 
    ->user('root')
    ->set('deploy_path', '/var/www/html')
    ->stage('dev')
    ->roles('master');

I'm using build artifact:

• php vendor/bin/dep build
  this goes fine and creates an archived for release

• php vendor/bin/dep deploy-artifact dev

It produces the following error:

[dev_master] > /usr/bin/php /var/www/html/releases/20190305070046/bin/magento setup:db:status
[dev_master] < No information is available: the Magento application is not installed.
In Client.php line 99:
  [Deployer\Exception\RuntimeException (1)]
  The command "/usr/bin/php /var/www/html/releases/20190305070046/bin/magento setup:db:status" failed.
  Exit Code: 1 (General error)
  Host Name: dev_master
  ================
  No information is available: the Magento application is not installed.

Can any of you guide me through what am I doing wrong here?

When I try to run files:compile, I get the following error:

The command "cd /srv/public_html/releases/20201105100601 && (/usr/local/bin/php ./bin/magento setup:di:compile)" failed.

  Exit Code: 1 (General error)

  Host Name: xxxxxxxxxx

  ================

  In Write.php line 200:

    The directory "/srv/public_html/releases/20201105100601/var/cache/" cannot
    be deleted Warning!rmdir(/srv/public_html/releases/20201105100601/var/cache
    /): Not a directory


  setup:di:compile

The permissions on the symlink are drwxr-xr-x and I'm running as the directory owner.

We're using absolute symlinks, not sure if that's the issue? Running files:compile works when I do it in the context of a full deploy.

Hi,

I was playing around with this project and ran into some errors on build machines with multiple versions of php installed.

TL;DR: {{magento_bin}} ignores deployers {{bin/php}} setting and executes the wrong php binary

The {{magento_bin}} command just executes the /bin/magneot command, which in turn uses the env command in the shebang to determine which php executable to use
(#!/usr/bin/env php)

In deployer it is possible to set another php executable with set('bin/php', ...) like this:

set('bin/php', function () {
    return locateBinaryPath('php7.1');
});

The easiest fix would be to use "{{bin/php}}" to execute bin/magento.

To do this, in file recipe/magento_2_1.php change Line 27:

From:

set('magento_bin', '{{bin/php}} {{magento_dir}}/bin/magento');

To:

set('magento_bin', '{{magento_dir}}/bin/magento');

When running

php vendor/bin/dep -n deploy develop

PHP Fatal error: Declaration of Symfony\Component\Console\Input\Input::getArgument($name) must be compatible with Symfony\Component\Console\Input\InputInterface::getArgument(string $name) in phar:///opt/atlassian/pipelines/agent/build/vendor/deployer/dist/dep/vendor/symfony/console/Input/Input.php on line 28

Hi I am trying to use your build artifacts deploy recipe.

1. Building step goes fine.

2. Sending and deploying:

• When sending to my production server I have trouble understanding how to specify my production "env.php" file. Obviously my artifact archive don't contain my local "env.php" (as it would put my local env on my production server) but when deploying on my production server bin/magento setup:upgrade can't be run and gives me error because the env.php production file is not there.

How do you set or specify the production env.php that must be use on the production server ?

I am encountering the following error when deploying:

➤ Executing task files:compile [production] > cd ~/magento2/releases/20191121160900 && (/usr/bin/php ./bin/magento setup:di:compile) [production] < You cannot run this command because modules are not enabled. You can enable modules by running the 'module:enable --all' command. ➤ Executing task deploy:failed

Is there something i am missing here? I'm not sure why the modules are disabled in the first place..

When I run dep deploy staging, I get this error message when it gets to the files:static_assets task:

NOTE: Manual static content deployment is not required in "default" and "developer" modes.
In "default" and "developer" modes static contents are being deployed automatically on demand.
If you still want to deploy in these modes, use -f option: 'bin/magento setup:static-content:deploy -f'

My environment is in production mode though.

There is not a documentation on this value. Can you please share the use cases of this variable?
I'm not quite understand the idea of copying content of var/cache in release path to shared/var/cache
Thank in advance.

In recipe/magento_2_1.php shared_dirs are set as:

set('shared_dirs', [
    '{{magento_dir}}/var',
    '{{magento_dir}}/pub/media',
    '{{magento_dir}}/pub/static/_cache',
]);

Seems like it the media folder should be the only shared dir.
Commands like

bin/magento deploy:mode:set production
Enabling maintenance mode
Config "dev/debug/debug_logging = 0" has been saved.
Disabling maintenance mode
The directory "/srv/releases/20180628170504/pub/static/_cache" cannot be deleted Warning!rmdir(/srv/releases/20180628170504/pub/static/_cache): Not a directory

fail when pub/static/_cache is a symlink and I see no advantage to making it a shared dir.

Also I would think /var shouldn't be a shared dir as any cache clearing or setting in one release would affect all the others causing all possible problems with version mismatches.

According to deployphp/deployer#2282 deployer works with Composer 2 only in version 7 and higher.
In the current version of this repo, only deployer 6 is supported.
So it would be great to include version 7.

Since Deployer heavily relies on symlinks and symlinks are cached by the OpCache, a PHP reload or any other OpCache reset command is necessary during the deployment. Currently, this is done via a sudo command:

I suggest using the project CacheTool for it, because it does not rely on sudoer rights if I understand correctly.

What do you think?

Hi @jalogut

While deploying the release on server, the task maintenance:set:if-needed always set the site into maintenance mode. Hence it's not zero downtime deployment.

Executing task maintenance:set:if-needed
✔ Executing task maintenance:set
✔ Ok

Hi Team

How to include vendor as the shared directory? I tried it to simply add in the list of shared directories but getting error during deployment.

In Client.php line 103:
                                                                                                                                                                                                                                       
  [Deployer\Exception\RuntimeException (255)]                                                                                                                                                                                          
  The command "cd /mnt/data/home/ccusr/public_html/releases/20210805172238 && (/usr/bin/php ./bin/magento setup:di:compile)" failed.                                                                                                
                                                                                                                                                                                                                                       
  Exit Code: 255 (Unknown error)                                                                                                                                                                                                       
                                                                                                                                                                                                                                       
  Host Name: ccusr-staging                                                                                                                                                                                                            
                                                                                                                                                                                                                                       
  ================                                                                                                                                                                                                                     
  PHP Warning:  require(/mnt/data/home/ccusr/public_html/shared/vendor/composer/../../app/etc/NonComposerComponentRegistration.php): failed to open stream: No such file or directory in /mnt/data/home/ccusr/public_html/shared/vendor/composer/autoload_real.php on line 73                                                                                                                                                                                       
  PHP Fatal error:  require(): Failed opening required '/mnt/data/home/ccusr/public_html/shared/vendor/composer/../../app/etc/NonComposerComponentRegistration.php' (include_path='/mnt/data/home/ccusr/public_html/shared/vendor/magento/zendframework1/library:.:/usr/share/pear:/usr/share/php:/mnt/data/home/ccusr/public_html/shared/vendor/jalogut/magento2-deployer-plus') in /mnt/data/home/ccusr/public_html/shared/vendor/composer/autoload_real.php on line 73        

Specifications:

• magento version: 2.1.12 Open Source
• jalogut/magento2-deployer-plus: 1.1.1
• php version: 7.0.28

Problem:

When I try to install this package inside a Magento 2 project (version < 2.2) I get the following dependency conflict error:

Problem 1
- symfony/console v4.0.9 requires php ^7.1.3 -> your PHP version (7.0.28) does not satisfy that requirement.
- symfony/console v4.0.8 requires php ^7.1.3 -> your PHP version (7.0.28) does not satisfy that requirement.
- symfony/console v4.0.7 requires php ^7.1.3 -> your PHP version (7.0.28) does not satisfy that requirement.
- symfony/console v4.0.6 requires php ^7.1.3 -> your PHP version (7.0.28) does not satisfy that requirement.
- symfony/console v4.0.5 requires php ^7.1.3 -> your PHP version (7.0.28) does not satisfy that requirement.
- symfony/console v4.0.4 requires php ^7.1.3 -> your PHP version (7.0.28) does not satisfy that requirement.
- symfony/console v4.0.3 requires php ^7.1.3 -> your PHP version (7.0.28) does not satisfy that requirement.
- symfony/console v4.0.2 requires php ^7.1.3 -> your PHP version (7.0.28) does not satisfy that requirement.
- symfony/console v4.0.1 requires php ^7.1.3 -> your PHP version (7.0.28) does not satisfy that requirement.
- symfony/console v4.0.0 requires php ^7.1.3 -> your PHP version (7.0.28) does not satisfy that requirement.
- Conclusion: don't install jalogut/magento2-deployer-plus 1.1.1
- Conclusion: don't install jalogut/magento2-deployer-plus 1.1
- Conclusion: don't install jalogut/magento2-deployer-plus 1.1.1
- Conclusion: remove symfony/console v2.6.13
- Installation request for jalogut/magento2-deployer-plus ^1.1 -> satisfiable by jalogut/magento2-deployer-plus[1.1, 1.1.1].
- Conclusion: don't install symfony/console v2.6.13
- jalogut/magento2-deployer-plus 1.1 requires deployer/deployer ^6.0 -> satisfiable by deployer/deployer[v6.0.0, v6.0.1, v6.0.2, v6.0.3, v6.0.4, v6.0.5, v6.1.0, v6.2.0].
- deployer/deployer v6.0.0 requires symfony/console ~2.7|~3.0 -> satisfiable by symfony/console[v2.7.0, v2.7.1, v2.7.10, v2.7.11, v2.7.12, v2.7.13, v2.7.14, v2.7.15, v2.7.16, v2.7.17, v2.7.18, v2.7.19, v2.7.2, v2.7.20, v2.7.21, v2.7.22, v2.7.23, v2.7.24, v2.7.25, v2.7.26, v2.7.27, v2.7.28, v2.7.29, v2.7.3, v2.7.30, v2.7.31, v2.7.32, v2.7.33, v2.7.34, v2.7.35, v2.7.36, v2.7.37, v2.7.38, v2.7.39, v2.7.4, v2.7.40, v2.7.41, v2.7.42, v2.7.43, v2.7.44, v2.7.45, v2.7.46, v2.7.5, v2.7.6, v2.7.7, v2.7.8, v2.7.9, v2.8.0, v2.8.1, v2.8.10, v2.8.11, v2.8.12, v2.8.13, v2.8.14, v2.8.15, v2.8.16, v2.8.17, v2.8.18, v2.8.19, v2.8.2, v2.8.20, v2.8.21, v2.8.22, v2.8.23, v2.8.24, v2.8.25, v2.8.26, v2.8.27, v2.8.28, v2.8.29, v2.8.3, v2.8.30, v2.8.31, v2.8.32, v2.8.33, v2.8.34, v2.8.35, v2.8.36, v2.8.37, v2.8.38, v2.8.39, v2.8.4, v2.8.5, v2.8.6, v2.8.7, v2.8.8, v2.8.9, v3.0.0, v3.0.1, v3.0.2, v3.0.3, v3.0.4, v3.0.5, v3.0.6, v3.0.7, v3.0.8, v3.0.9, v3.1.0, v3.1.1, v3.1.10, v3.1.2, v3.1.3, v3.1.4, v3.1.5, v3.1.6, v3.1.7, v3.1.8, v3.1.9, v3.2.0, v3.2.1, v3.2.10, v3.2.11, v3.2.12, v3.2.13, v3.2.14, v3.2.2, v3.2.3, v3.2.4, v3.2.5, v3.2.6, v3.2.7, v3.2.8, v3.2.9, v3.3.0, v3.3.1, v3.3.10, v3.3.11, v3.3.12, v3.3.13, v3.3.14, v3.3.15, v3.3.16, v3.3.2, v3.3.3, v3.3.4, v3.3.5, v3.3.6, v3.3.7, v3.3.8, v3.3.9, v3.4.0, v3.4.1, v3.4.2, v3.4.3, v3.4.4, v3.4.5, v3.4.6, v3.4.7, v3.4.8, v3.4.9].
- deployer/deployer v6.0.1 requires symfony/console ~2.7|~3.0 -> satisfiable by symfony/console[v2.7.0, v2.7.1, v2.7.10, v2.7.11, v2.7.12, v2.7.13, v2.7.14, v2.7.15, v2.7.16, v2.7.17, v2.7.18, v2.7.19, v2.7.2, v2.7.20, v2.7.21, v2.7.22, v2.7.23, v2.7.24, v2.7.25, v2.7.26, v2.7.27, v2.7.28, v2.7.29, v2.7.3, v2.7.30, v2.7.31, v2.7.32, v2.7.33, v2.7.34, v2.7.35, v2.7.36, v2.7.37, v2.7.38, v2.7.39, v2.7.4, v2.7.40, v2.7.41, v2.7.42, v2.7.43, v2.7.44, v2.7.45, v2.7.46, v2.7.5, v2.7.6, v2.7.7, v2.7.8, v2.7.9, v2.8.0, v2.8.1, v2.8.10, v2.8.11, v2.8.12, v2.8.13, v2.8.14, v2.8.15, v2.8.16, v2.8.17, v2.8.18, v2.8.19, v2.8.2, v2.8.20, v2.8.21, v2.8.22, v2.8.23, v2.8.24, v2.8.25, v2.8.26, v2.8.27, v2.8.28, v2.8.29, v2.8.3, v2.8.30, v2.8.31, v2.8.32, v2.8.33, v2.8.34, v2.8.35, v2.8.36, v2.8.37, v2.8.38, v2.8.39, v2.8.4, v2.8.5, v2.8.6, v2.8.7, v2.8.8, v2.8.9, v3.0.0, v3.0.1, v3.0.2, v3.0.3, v3.0.4, v3.0.5, v3.0.6, v3.0.7, v3.0.8, v3.0.9, v3.1.0, v3.1.1, v3.1.10, v3.1.2, v3.1.3, v3.1.4, v3.1.5, v3.1.6, v3.1.7, v3.1.8, v3.1.9, v3.2.0, v3.2.1, v3.2.10, v3.2.11, v3.2.12, v3.2.13, v3.2.14, v3.2.2, v3.2.3, v3.2.4, v3.2.5, v3.2.6, v3.2.7, v3.2.8, v3.2.9, v3.3.0, v3.3.1, v3.3.10, v3.3.11, v3.3.12, v3.3.13, v3.3.14, v3.3.15, v3.3.16, v3.3.2, v3.3.3, v3.3.4, v3.3.5, v3.3.6, v3.3.7, v3.3.8, v3.3.9, v3.4.0, v3.4.1, v3.4.2, v3.4.3, v3.4.4, v3.4.5, v3.4.6, v3.4.7, v3.4.8, v3.4.9].
- deployer/deployer v6.0.2 requires symfony/console ~2.7|~3.0 -> satisfiable by symfony/console[v2.7.0, v2.7.1, v2.7.10, v2.7.11, v2.7.12, v2.7.13, v2.7.14, v2.7.15, v2.7.16, v2.7.17, v2.7.18, v2.7.19, v2.7.2, v2.7.20, v2.7.21, v2.7.22, v2.7.23, v2.7.24, v2.7.25, v2.7.26, v2.7.27, v2.7.28, v2.7.29, v2.7.3, v2.7.30, v2.7.31, v2.7.32, v2.7.33, v2.7.34, v2.7.35, v2.7.36, v2.7.37, v2.7.38, v2.7.39, v2.7.4, v2.7.40, v2.7.41, v2.7.42, v2.7.43, v2.7.44, v2.7.45, v2.7.46, v2.7.5, v2.7.6, v2.7.7, v2.7.8, v2.7.9, v2.8.0, v2.8.1, v2.8.10, v2.8.11, v2.8.12, v2.8.13, v2.8.14, v2.8.15, v2.8.16, v2.8.17, v2.8.18, v2.8.19, v2.8.2, v2.8.20, v2.8.21, v2.8.22, v2.8.23, v2.8.24, v2.8.25, v2.8.26, v2.8.27, v2.8.28, v2.8.29, v2.8.3, v2.8.30, v2.8.31, v2.8.32, v2.8.33, v2.8.34, v2.8.35, v2.8.36, v2.8.37, v2.8.38, v2.8.39, v2.8.4, v2.8.5, v2.8.6, v2.8.7, v2.8.8, v2.8.9, v3.0.0, v3.0.1, v3.0.2, v3.0.3, v3.0.4, v3.0.5, v3.0.6, v3.0.7, v3.0.8, v3.0.9, v3.1.0, v3.1.1, v3.1.10, v3.1.2, v3.1.3, v3.1.4, v3.1.5, v3.1.6, v3.1.7, v3.1.8, v3.1.9, v3.2.0, v3.2.1, v3.2.10, v3.2.11, v3.2.12, v3.2.13, v3.2.14, v3.2.2, v3.2.3, v3.2.4, v3.2.5, v3.2.6, v3.2.7, v3.2.8, v3.2.9, v3.3.0, v3.3.1, v3.3.10, v3.3.11, v3.3.12, v3.3.13, v3.3.14, v3.3.15, v3.3.16, v3.3.2, v3.3.3, v3.3.4, v3.3.5, v3.3.6, v3.3.7, v3.3.8, v3.3.9, v3.4.0, v3.4.1, v3.4.2, v3.4.3, v3.4.4, v3.4.5, v3.4.6, v3.4.7, v3.4.8, v3.4.9].
- deployer/deployer v6.0.3 requires symfony/console ~2.7|~3.0 -> satisfiable by symfony/console[v2.7.0, v2.7.1, v2.7.10, v2.7.11, v2.7.12, v2.7.13, v2.7.14, v2.7.15, v2.7.16, v2.7.17, v2.7.18, v2.7.19, v2.7.2, v2.7.20, v2.7.21, v2.7.22, v2.7.23, v2.7.24, v2.7.25, v2.7.26, v2.7.27, v2.7.28, v2.7.29, v2.7.3, v2.7.30, v2.7.31, v2.7.32, v2.7.33, v2.7.34, v2.7.35, v2.7.36, v2.7.37, v2.7.38, v2.7.39, v2.7.4, v2.7.40, v2.7.41, v2.7.42, v2.7.43, v2.7.44, v2.7.45, v2.7.46, v2.7.5, v2.7.6, v2.7.7, v2.7.8, v2.7.9, v2.8.0, v2.8.1, v2.8.10, v2.8.11, v2.8.12, v2.8.13, v2.8.14, v2.8.15, v2.8.16, v2.8.17, v2.8.18, v2.8.19, v2.8.2, v2.8.20, v2.8.21, v2.8.22, v2.8.23, v2.8.24, v2.8.25, v2.8.26, v2.8.27, v2.8.28, v2.8.29, v2.8.3, v2.8.30, v2.8.31, v2.8.32, v2.8.33, v2.8.34, v2.8.35, v2.8.36, v2.8.37, v2.8.38, v2.8.39, v2.8.4, v2.8.5, v2.8.6, v2.8.7, v2.8.8, v2.8.9, v3.0.0, v3.0.1, v3.0.2, v3.0.3, v3.0.4, v3.0.5, v3.0.6, v3.0.7, v3.0.8, v3.0.9, v3.1.0, v3.1.1, v3.1.10, v3.1.2, v3.1.3, v3.1.4, v3.1.5, v3.1.6, v3.1.7, v3.1.8, v3.1.9, v3.2.0, v3.2.1, v3.2.10, v3.2.11, v3.2.12, v3.2.13, v3.2.14, v3.2.2, v3.2.3, v3.2.4, v3.2.5, v3.2.6, v3.2.7, v3.2.8, v3.2.9, v3.3.0, v3.3.1, v3.3.10, v3.3.11, v3.3.12, v3.3.13, v3.3.14, v3.3.15, v3.3.16, v3.3.2, v3.3.3, v3.3.4, v3.3.5, v3.3.6, v3.3.7, v3.3.8, v3.3.9, v3.4.0, v3.4.1, v3.4.2, v3.4.3, v3.4.4, v3.4.5, v3.4.6, v3.4.7, v3.4.8, v3.4.9].
- deployer/deployer v6.0.4 requires symfony/console ~2.7|~3.0 -> satisfiable by symfony/console[v2.7.0, v2.7.1, v2.7.10, v2.7.11, v2.7.12, v2.7.13, v2.7.14, v2.7.15, v2.7.16, v2.7.17, v2.7.18, v2.7.19, v2.7.2, v2.7.20, v2.7.21, v2.7.22, v2.7.23, v2.7.24, v2.7.25, v2.7.26, v2.7.27, v2.7.28, v2.7.29, v2.7.3, v2.7.30, v2.7.31, v2.7.32, v2.7.33, v2.7.34, v2.7.35, v2.7.36, v2.7.37, v2.7.38, v2.7.39, v2.7.4, v2.7.40, v2.7.41, v2.7.42, v2.7.43, v2.7.44, v2.7.45, v2.7.46, v2.7.5, v2.7.6, v2.7.7, v2.7.8, v2.7.9, v2.8.0, v2.8.1, v2.8.10, v2.8.11, v2.8.12, v2.8.13, v2.8.14, v2.8.15, v2.8.16, v2.8.17, v2.8.18, v2.8.19, v2.8.2, v2.8.20, v2.8.21, v2.8.22, v2.8.23, v2.8.24, v2.8.25, v2.8.26, v2.8.27, v2.8.28, v2.8.29, v2.8.3, v2.8.30, v2.8.31, v2.8.32, v2.8.33, v2.8.34, v2.8.35, v2.8.36, v2.8.37, v2.8.38, v2.8.39, v2.8.4, v2.8.5, v2.8.6, v2.8.7, v2.8.8, v2.8.9, v3.0.0, v3.0.1, v3.0.2, v3.0.3, v3.0.4, v3.0.5, v3.0.6, v3.0.7, v3.0.8, v3.0.9, v3.1.0, v3.1.1, v3.1.10, v3.1.2, v3.1.3, v3.1.4, v3.1.5, v3.1.6, v3.1.7, v3.1.8, v3.1.9, v3.2.0, v3.2.1, v3.2.10, v3.2.11, v3.2.12, v3.2.13, v3.2.14, v3.2.2, v3.2.3, v3.2.4, v3.2.5, v3.2.6, v3.2.7, v3.2.8, v3.2.9, v3.3.0, v3.3.1, v3.3.10, v3.3.11, v3.3.12, v3.3.13, v3.3.14, v3.3.15, v3.3.16, v3.3.2, v3.3.3, v3.3.4, v3.3.5, v3.3.6, v3.3.7, v3.3.8, v3.3.9, v3.4.0, v3.4.1, v3.4.2, v3.4.3, v3.4.4, v3.4.5, v3.4.6, v3.4.7, v3.4.8, v3.4.9].
- deployer/deployer v6.0.5 requires symfony/console ~2.7|~3.0 -> satisfiable by symfony/console[v2.7.0, v2.7.1, v2.7.10, v2.7.11, v2.7.12, v2.7.13, v2.7.14, v2.7.15, v2.7.16, v2.7.17, v2.7.18, v2.7.19, v2.7.2, v2.7.20, v2.7.21, v2.7.22, v2.7.23, v2.7.24, v2.7.25, v2.7.26, v2.7.27, v2.7.28, v2.7.29, v2.7.3, v2.7.30, v2.7.31, v2.7.32, v2.7.33, v2.7.34, v2.7.35, v2.7.36, v2.7.37, v2.7.38, v2.7.39, v2.7.4, v2.7.40, v2.7.41, v2.7.42, v2.7.43, v2.7.44, v2.7.45, v2.7.46, v2.7.5, v2.7.6, v2.7.7, v2.7.8, v2.7.9, v2.8.0, v2.8.1, v2.8.10, v2.8.11, v2.8.12, v2.8.13, v2.8.14, v2.8.15, v2.8.16, v2.8.17, v2.8.18, v2.8.19, v2.8.2, v2.8.20, v2.8.21, v2.8.22, v2.8.23, v2.8.24, v2.8.25, v2.8.26, v2.8.27, v2.8.28, v2.8.29, v2.8.3, v2.8.30, v2.8.31, v2.8.32, v2.8.33, v2.8.34, v2.8.35, v2.8.36, v2.8.37, v2.8.38, v2.8.39, v2.8.4, v2.8.5, v2.8.6, v2.8.7, v2.8.8, v2.8.9, v3.0.0, v3.0.1, v3.0.2, v3.0.3, v3.0.4, v3.0.5, v3.0.6, v3.0.7, v3.0.8, v3.0.9, v3.1.0, v3.1.1, v3.1.10, v3.1.2, v3.1.3, v3.1.4, v3.1.5, v3.1.6, v3.1.7, v3.1.8, v3.1.9, v3.2.0, v3.2.1, v3.2.10, v3.2.11, v3.2.12, v3.2.13, v3.2.14, v3.2.2, v3.2.3, v3.2.4, v3.2.5, v3.2.6, v3.2.7, v3.2.8, v3.2.9, v3.3.0, v3.3.1, v3.3.10, v3.3.11, v3.3.12, v3.3.13, v3.3.14, v3.3.15, v3.3.16, v3.3.2, v3.3.3, v3.3.4, v3.3.5, v3.3.6, v3.3.7, v3.3.8, v3.3.9, v3.4.0, v3.4.1, v3.4.2, v3.4.3, v3.4.4, v3.4.5, v3.4.6, v3.4.7, v3.4.8, v3.4.9].
- deployer/deployer v6.1.0 requires symfony/console ~2.7|~3.0|~4.0 -> satisfiable by symfony/console[v2.7.0, v2.7.1, v2.7.10, v2.7.11, v2.7.12, v2.7.13, v2.7.14, v2.7.15, v2.7.16, v2.7.17, v2.7.18, v2.7.19, v2.7.2, v2.7.20, v2.7.21, v2.7.22, v2.7.23, v2.7.24, v2.7.25, v2.7.26, v2.7.27, v2.7.28, v2.7.29, v2.7.3, v2.7.30, v2.7.31, v2.7.32, v2.7.33, v2.7.34, v2.7.35, v2.7.36, v2.7.37, v2.7.38, v2.7.39, v2.7.4, v2.7.40, v2.7.41, v2.7.42, v2.7.43, v2.7.44, v2.7.45, v2.7.46, v2.7.5, v2.7.6, v2.7.7, v2.7.8, v2.7.9, v2.8.0, v2.8.1, v2.8.10, v2.8.11, v2.8.12, v2.8.13, v2.8.14, v2.8.15, v2.8.16, v2.8.17, v2.8.18, v2.8.19, v2.8.2, v2.8.20, v2.8.21, v2.8.22, v2.8.23, v2.8.24, v2.8.25, v2.8.26, v2.8.27, v2.8.28, v2.8.29, v2.8.3, v2.8.30, v2.8.31, v2.8.32, v2.8.33, v2.8.34, v2.8.35, v2.8.36, v2.8.37, v2.8.38, v2.8.39, v2.8.4, v2.8.5, v2.8.6, v2.8.7, v2.8.8, v2.8.9, v3.0.0, v3.0.1, v3.0.2, v3.0.3, v3.0.4, v3.0.5, v3.0.6, v3.0.7, v3.0.8, v3.0.9, v3.1.0, v3.1.1, v3.1.10, v3.1.2, v3.1.3, v3.1.4, v3.1.5, v3.1.6, v3.1.7, v3.1.8, v3.1.9, v3.2.0, v3.2.1, v3.2.10, v3.2.11, v3.2.12, v3.2.13, v3.2.14, v3.2.2, v3.2.3, v3.2.4, v3.2.5, v3.2.6, v3.2.7, v3.2.8, v3.2.9, v3.3.0, v3.3.1, v3.3.10, v3.3.11, v3.3.12, v3.3.13, v3.3.14, v3.3.15, v3.3.16, v3.3.2, v3.3.3, v3.3.4, v3.3.5, v3.3.6, v3.3.7, v3.3.8, v3.3.9, v3.4.0, v3.4.1, v3.4.2, v3.4.3, v3.4.4, v3.4.5, v3.4.6, v3.4.7, v3.4.8, v3.4.9, v4.0.0, v4.0.1, v4.0.2, v4.0.3, v4.0.4, v4.0.5, v4.0.6, v4.0.7, v4.0.8, v4.0.9].
- deployer/deployer v6.2.0 requires symfony/console ~2.7|~3.0|~4.0 -> satisfiable by symfony/console[v2.7.0, v2.7.1, v2.7.10, v2.7.11, v2.7.12, v2.7.13, v2.7.14, v2.7.15, v2.7.16, v2.7.17, v2.7.18, v2.7.19, v2.7.2, v2.7.20, v2.7.21, v2.7.22, v2.7.23, v2.7.24, v2.7.25, v2.7.26, v2.7.27, v2.7.28, v2.7.29, v2.7.3, v2.7.30, v2.7.31, v2.7.32, v2.7.33, v2.7.34, v2.7.35, v2.7.36, v2.7.37, v2.7.38, v2.7.39, v2.7.4, v2.7.40, v2.7.41, v2.7.42, v2.7.43, v2.7.44, v2.7.45, v2.7.46, v2.7.5, v2.7.6, v2.7.7, v2.7.8, v2.7.9, v2.8.0, v2.8.1, v2.8.10, v2.8.11, v2.8.12, v2.8.13, v2.8.14, v2.8.15, v2.8.16, v2.8.17, v2.8.18, v2.8.19, v2.8.2, v2.8.20, v2.8.21, v2.8.22, v2.8.23, v2.8.24, v2.8.25, v2.8.26, v2.8.27, v2.8.28, v2.8.29, v2.8.3, v2.8.30, v2.8.31, v2.8.32, v2.8.33, v2.8.34, v2.8.35, v2.8.36, v2.8.37, v2.8.38, v2.8.39, v2.8.4, v2.8.5, v2.8.6, v2.8.7, v2.8.8, v2.8.9, v3.0.0, v3.0.1, v3.0.2, v3.0.3, v3.0.4, v3.0.5, v3.0.6, v3.0.7, v3.0.8, v3.0.9, v3.1.0, v3.1.1, v3.1.10, v3.1.2, v3.1.3, v3.1.4, v3.1.5, v3.1.6, v3.1.7, v3.1.8, v3.1.9, v3.2.0, v3.2.1, v3.2.10, v3.2.11, v3.2.12, v3.2.13, v3.2.14, v3.2.2, v3.2.3, v3.2.4, v3.2.5, v3.2.6, v3.2.7, v3.2.8, v3.2.9, v3.3.0, v3.3.1, v3.3.10, v3.3.11, v3.3.12, v3.3.13, v3.3.14, v3.3.15, v3.3.16, v3.3.2, v3.3.3, v3.3.4, v3.3.5, v3.3.6, v3.3.7, v3.3.8, v3.3.9, v3.4.0, v3.4.1, v3.4.2, v3.4.3, v3.4.4, v3.4.5, v3.4.6, v3.4.7, v3.4.8, v3.4.9, v4.0.0, v4.0.1, v4.0.2, v4.0.3, v4.0.4, v4.0.5, v4.0.6, v4.0.7, v4.0.8, v4.0.9].
- Can only install one of: symfony/console[v2.7.1, v2.6.13].
- Can only install one of: symfony/console[v2.7.10, v2.6.13].
- Can only install one of: symfony/console[v2.7.11, v2.6.13].
- Can only install one of: symfony/console[v2.7.12, v2.6.13].
- Can only install one of: symfony/console[v2.7.13, v2.6.13].
- Can only install one of: symfony/console[v2.7.14, v2.6.13].
- Can only install one of: symfony/console[v2.7.15, v2.6.13].
- Can only install one of: symfony/console[v2.7.16, v2.6.13].
- Can only install one of: symfony/console[v2.7.17, v2.6.13].
- Can only install one of: symfony/console[v2.7.18, v2.6.13].
- Can only install one of: symfony/console[v2.7.19, v2.6.13].
- Can only install one of: symfony/console[v2.7.2, v2.6.13].
- Can only install one of: symfony/console[v2.7.20, v2.6.13].
- Can only install one of: symfony/console[v2.7.21, v2.6.13].
- Can only install one of: symfony/console[v2.7.22, v2.6.13].
- Can only install one of: symfony/console[v2.7.23, v2.6.13].
- Can only install one of: symfony/console[v2.7.24, v2.6.13].
- Can only install one of: symfony/console[v2.7.25, v2.6.13].
- Can only install one of: symfony/console[v2.7.26, v2.6.13].
- Can only install one of: symfony/console[v2.7.27, v2.6.13].
- Can only install one of: symfony/console[v2.7.28, v2.6.13].
- Can only install one of: symfony/console[v2.7.29, v2.6.13].
- Can only install one of: symfony/console[v2.7.3, v2.6.13].
- Can only install one of: symfony/console[v2.7.30, v2.6.13].
- Can only install one of: symfony/console[v2.7.31, v2.6.13].
- Can only install one of: symfony/console[v2.7.32, v2.6.13].
- Can only install one of: symfony/console[v2.7.33, v2.6.13].
- Can only install one of: symfony/console[v2.7.34, v2.6.13].
- Can only install one of: symfony/console[v2.7.35, v2.6.13].
- Can only install one of: symfony/console[v2.7.36, v2.6.13].
- Can only install one of: symfony/console[v2.7.37, v2.6.13].
- Can only install one of: symfony/console[v2.7.38, v2.6.13].
- Can only install one of: symfony/console[v2.7.39, v2.6.13].
- Can only install one of: symfony/console[v2.7.4, v2.6.13].
- Can only install one of: symfony/console[v2.7.40, v2.6.13].
- Can only install one of: symfony/console[v2.7.41, v2.6.13].
- Can only install one of: symfony/console[v2.7.42, v2.6.13].
- Can only install one of: symfony/console[v2.7.43, v2.6.13].
- Can only install one of: symfony/console[v2.7.44, v2.6.13].
- Can only install one of: symfony/console[v2.7.45, v2.6.13].
- Can only install one of: symfony/console[v2.7.46, v2.6.13].
- Can only install one of: symfony/console[v2.7.5, v2.6.13].
- Can only install one of: symfony/console[v2.7.6, v2.6.13].
- Can only install one of: symfony/console[v2.7.7, v2.6.13].
- Can only install one of: symfony/console[v2.7.8, v2.6.13].
- Can only install one of: symfony/console[v2.7.9, v2.6.13].
- Can only install one of: symfony/console[v2.8.0, v2.6.13].
- Can only install one of: symfony/console[v2.8.1, v2.6.13].
- Can only install one of: symfony/console[v2.8.10, v2.6.13].
- Can only install one of: symfony/console[v2.8.11, v2.6.13].
- Can only install one of: symfony/console[v2.8.12, v2.6.13].
- Can only install one of: symfony/console[v2.8.13, v2.6.13].
- Can only install one of: symfony/console[v2.8.14, v2.6.13].
- Can only install one of: symfony/console[v2.8.15, v2.6.13].
- Can only install one of: symfony/console[v2.8.16, v2.6.13].
- Can only install one of: symfony/console[v2.8.17, v2.6.13].
- Can only install one of: symfony/console[v2.8.18, v2.6.13].
- Can only install one of: symfony/console[v2.8.19, v2.6.13].
- Can only install one of: symfony/console[v2.8.2, v2.6.13].
- Can only install one of: symfony/console[v2.8.20, v2.6.13].
- Can only install one of: symfony/console[v2.8.21, v2.6.13].
- Can only install one of: symfony/console[v2.8.22, v2.6.13].
- Can only install one of: symfony/console[v2.8.23, v2.6.13].
- Can only install one of: symfony/console[v2.8.24, v2.6.13].
- Can only install one of: symfony/console[v2.8.25, v2.6.13].
- Can only install one of: symfony/console[v2.8.26, v2.6.13].
- Can only install one of: symfony/console[v2.8.27, v2.6.13].
- Can only install one of: symfony/console[v2.8.28, v2.6.13].
- Can only install one of: symfony/console[v2.8.29, v2.6.13].
- Can only install one of: symfony/console[v2.8.3, v2.6.13].
- Can only install one of: symfony/console[v2.8.30, v2.6.13].
- Can only install one of: symfony/console[v2.8.31, v2.6.13].
- Can only install one of: symfony/console[v2.8.32, v2.6.13].
- Can only install one of: symfony/console[v2.8.33, v2.6.13].
- Can only install one of: symfony/console[v2.8.34, v2.6.13].
- Can only install one of: symfony/console[v2.8.35, v2.6.13].
- Can only install one of: symfony/console[v2.8.36, v2.6.13].
- Can only install one of: symfony/console[v2.8.37, v2.6.13].
- Can only install one of: symfony/console[v2.8.38, v2.6.13].
- Can only install one of: symfony/console[v2.8.39, v2.6.13].
- Can only install one of: symfony/console[v2.8.4, v2.6.13].
- Can only install one of: symfony/console[v2.8.5, v2.6.13].
- Can only install one of: symfony/console[v2.8.6, v2.6.13].
- Can only install one of: symfony/console[v2.8.7, v2.6.13].
- Can only install one of: symfony/console[v2.8.8, v2.6.13].
- Can only install one of: symfony/console[v2.8.9, v2.6.13].
- Can only install one of: symfony/console[v2.7.0, v2.6.13].
- Can only install one of: symfony/console[v3.0.0, v2.6.13].
- Can only install one of: symfony/console[v3.0.1, v2.6.13].
- Can only install one of: symfony/console[v3.0.2, v2.6.13].
- Can only install one of: symfony/console[v3.0.3, v2.6.13].
- Can only install one of: symfony/console[v3.0.4, v2.6.13].
- Can only install one of: symfony/console[v3.0.5, v2.6.13].
- Can only install one of: symfony/console[v3.0.6, v2.6.13].
- Can only install one of: symfony/console[v3.0.7, v2.6.13].
- Can only install one of: symfony/console[v3.0.8, v2.6.13].
- Can only install one of: symfony/console[v3.0.9, v2.6.13].
- Can only install one of: symfony/console[v3.1.0, v2.6.13].
- Can only install one of: symfony/console[v3.1.1, v2.6.13].
- Can only install one of: symfony/console[v3.1.10, v2.6.13].
- Can only install one of: symfony/console[v3.1.2, v2.6.13].
- Can only install one of: symfony/console[v3.1.3, v2.6.13].
- Can only install one of: symfony/console[v3.1.4, v2.6.13].
- Can only install one of: symfony/console[v3.1.5, v2.6.13].
- Can only install one of: symfony/console[v3.1.6, v2.6.13].
- Can only install one of: symfony/console[v3.1.7, v2.6.13].
- Can only install one of: symfony/console[v3.1.8, v2.6.13].
- Can only install one of: symfony/console[v3.1.9, v2.6.13].
- Can only install one of: symfony/console[v3.2.0, v2.6.13].
- Can only install one of: symfony/console[v3.2.1, v2.6.13].
- Can only install one of: symfony/console[v3.2.10, v2.6.13].
- Can only install one of: symfony/console[v3.2.11, v2.6.13].
- Can only install one of: symfony/console[v3.2.12, v2.6.13].
- Can only install one of: symfony/console[v3.2.13, v2.6.13].
- Can only install one of: symfony/console[v3.2.14, v2.6.13].
- Can only install one of: symfony/console[v3.2.2, v2.6.13].
- Can only install one of: symfony/console[v3.2.3, v2.6.13].
- Can only install one of: symfony/console[v3.2.4, v2.6.13].
- Can only install one of: symfony/console[v3.2.5, v2.6.13].
- Can only install one of: symfony/console[v3.2.6, v2.6.13].
- Can only install one of: symfony/console[v3.2.7, v2.6.13].
- Can only install one of: symfony/console[v3.2.8, v2.6.13].
- Can only install one of: symfony/console[v3.2.9, v2.6.13].
- Can only install one of: symfony/console[v3.3.0, v2.6.13].
- Can only install one of: symfony/console[v3.3.1, v2.6.13].
- Can only install one of: symfony/console[v3.3.10, v2.6.13].
- Can only install one of: symfony/console[v3.3.11, v2.6.13].
- Can only install one of: symfony/console[v3.3.12, v2.6.13].
- Can only install one of: symfony/console[v3.3.13, v2.6.13].
- Can only install one of: symfony/console[v3.3.14, v2.6.13].
- Can only install one of: symfony/console[v3.3.15, v2.6.13].
- Can only install one of: symfony/console[v3.3.16, v2.6.13].
- Can only install one of: symfony/console[v3.3.2, v2.6.13].
- Can only install one of: symfony/console[v3.3.3, v2.6.13].
- Can only install one of: symfony/console[v3.3.4, v2.6.13].
- Can only install one of: symfony/console[v3.3.5, v2.6.13].
- Can only install one of: symfony/console[v3.3.6, v2.6.13].
- Can only install one of: symfony/console[v3.3.7, v2.6.13].
- Can only install one of: symfony/console[v3.3.8, v2.6.13].
- Can only install one of: symfony/console[v3.3.9, v2.6.13].
- Can only install one of: symfony/console[v3.4.0, v2.6.13].
- Can only install one of: symfony/console[v3.4.1, v2.6.13].
- Can only install one of: symfony/console[v3.4.2, v2.6.13].
- Can only install one of: symfony/console[v3.4.3, v2.6.13].
- Can only install one of: symfony/console[v3.4.4, v2.6.13].
- Can only install one of: symfony/console[v3.4.5, v2.6.13].
- Can only install one of: symfony/console[v3.4.6, v2.6.13].
- Can only install one of: symfony/console[v3.4.7, v2.6.13].
- Can only install one of: symfony/console[v3.4.8, v2.6.13].
- Can only install one of: symfony/console[v3.4.9, v2.6.13].
- Installation request for symfony/console (locked at v2.6.13) -> satisfiable by symfony/console[v2.6.13].

Actually magento < 2.2 implements this restriction for symfony/console: ~2.3 <2.7 and deployer/deployer: ~2.7|~3.0|~4.0

So only deployer <= 3 should be compatible with a Magento < 2.2 installation, but other conflicts could happen (monolog for example).

In order to avoid all this dependency hell you could use deployer/dist instead of deployer/deployer, of this way you will avoid all the dependency incompatibilities.

  "require": {
    "deployer/dist": "^6.0"
  }

If you want I can make a PR.

Thank you!

When magento_dir is set to '.' in my deploy.php, if I run dep build I get the following error:

The command "cd . && (/usr/bin/php .//bin/magento setup:di:compile)" failed.                                                    
                                                                                                                                  
Exit Code: 1(General error)                                                                                                     
                                                                                                                                  
Working directory: /home/user/www/site.uk                                                                               
                                                                                                                                  
Output:                                                                                                                         
================                                                                                                                
Warning: include(/home/user/www/site.uk/vendor/composer/../../generated/code/Magento/Framework/App/ResourceConnection/  
Proxy.php): failed to open stream: No such file or directory in /home/user/www/site.uk/vendor/composer/ClassLoader.php on line 444                                                                                                                    
                                                                                                                                  
                                                                                                                                  
Error Output:                                                                                                                   
================  

If I set the magento_dir to an absolute path, it works for the local build but when pushing to production, this path is incorrect and breaks deployment. If I then change it back to '.' it works for production.

It seems like it should just '.' for local but it throws the ClassLoader.php error. Any ideas?

Creating artifacts on my MacOS system also brings .DS_Store & ._.DS_Store files to the server. These should be excluded when creating artifacts.

Hi, packagist.org still shows 2.3.0 as the most recent version. Can you please fix this?

I found that the current order of commands during a deploy doesn't (fully) import the configuration properly.

The setup:db-data:upgrade command sets the config_hash in the flag table. This in turns makes the app:config:import think it doesn't need importing. In my case it turns out new website and stores are not created.

Reversing the order of commands helps out but I'm not sure if that has any side effects.

When switching to a new release occurs, the contents of folders var and pub are lost with the exception of these shared folders

set ('shared_dirs', [
'{{magento_dir}}/pub/media',
'{{magento_dir}}/var/log',
'{{magento_dir}}/var/backups',
'{{magento_dir}}/var/session',
]);

The problem is that many modules save files directly to the root of folders var and pub.

For example,
pub/google_sitemap_3_1008.xml

Do I understand correctly that this is the right behavior and can this problem be solved in some way?

Added app:config:status : https://devdocs.magento.com/guides/v2.2/release-notes/ReleaseNotes2.2.4CE.html.

Apply this change and avoid workaround as we were doing so far

During our recent update from Magento 2.3.4-p2 to Magento 2.3.5-p2 we had the issue, that the cache:flush process failed during the cleanup task.
This issue was, that the Class Magento\GoogleShoppingAds\Model\Cache\Type did not exist anymore, as it was removed during this update.
I assume that the cache:flush command tried to flush this cache as well, even if it was not there anymore.
However, as the deployment failed, the symlink of the shop system was correctly set back to the version before.
Unfortunately the maintenance mode has not been disabled, which led to a downtime until we found out, what is wrong.
Would it be possible to add this as a general backup plan?

Hi,

As a noob I try to figuring out how to install the deployment tool.
Do I have to install this in the Magento root? Or outside the root?

It would be a little more clear if I know where to cd to.
This also applies to the setup part. Where should the file deploy.php copied to?

I hope you can make it a little more clear for noobs like me ;-)

Thank you in advanced!

Could you please manually update the package on packagist.org? It still shows 2.6.0 as the latest version:

Additionally, it would make sense to configure auto-updates.

Would it be possible to have both git and artifacts deployment, whereby all code on the web servers would be coming from git, and only what requires to be compiled gets built as an artifact locally (or on the build server) and copied to the web servers?

This setup would be closer to what Magento docs classifies as pipeline deployment

I am encountering exactly the same issue as #20
There has been no change in the modules.

~/magento2$ bin/magento setup:di:compile

In Write.php line 202:

The directory "/data/web/release_production/releases/20191125192232/var/cache/" cannot be deleted Warning!rmdir(/data/web/release_production/releases/20191125192232/var/cache/): Not a
directory

If i replace the symlink with a real folder it works like expected. Tried to give the folders 777 permissions but to no avail.

Magento 2.3.2, PHP7.2

Considering if the document root is /var/www/html/mymagento

What would be ideal directory structure to deploy using deployer-plus?

Ideal directory structure in documentation would be useful

Below is my code

<?php

namespace Deployer;

require 'vendor/jalogut/magento2-deployer-plus/recipe/magento_2_2_5.php';

// Use timestamp for release name
set('release_name', function () {
    return date('YmdHis');
});

// Magento dir into the project root. Set "." if magento is installed on project root
set('magento_dir', '/var/www/html/area51');
// [Optional] Git repository. Only needed if not using build + artifact strategy
set('repository', 'https://github.com/USER/area51.git');
// Space separated list of languages for static-content:deploy
set('languages', 'en_US');
// Enable all caches after deployment
set('cache_enabled_caches', 'all');
task('files:static_assets')->onRoles('Skip');
// OPcache configuration
task('cache:clear:opcache', 'sudo systemctl reload php-fpm');
after('cache:clear', 'cache:clear:opcache');
set('deploy_path', '/var/www/html/area51');
//set('shared_files', ['/var/www/html/area51/app/etc/env.php']);
// set('release_path', '/var/www/html/area51');
// Build host
localhost('build');

However it fails, at
                                                                              
  [Symfony\Component\Process\Exception\ProcessFailedException]                 
  The command "/usr/bin/php /var/www/html/area51/releases/20200510042953//var  
  /www/html/area51/bin/magento setup:db:status" failed.                        
                                                                               
  Exit Code: 1(General error)                                                  
                                                                               
  Working directory: /var/www/html/DeployerMagento                             
                                                                               
  Output:                                                                      
  ================                                                             
  Could not open input file: /var/www/html/area51/releases/20200510042953//va  
  r/www/html/area51/bin/magento                                                
                                                                               
                                                                               
  Error Output:                                                                
  ================    

In recipe/magento_2_1/files.php theres a files:permissions task:

task(
    'files:permissions',
    'cd {{magento_dir}} && find var vendor pub/static pub/media app/etc -type f -exec chmod g+w {} \; ' .
    '&& find var vendor pub/static pub/media app/etc -type d -exec chmod g+w {} \; && chmod u+x bin/magento'
);

For both files and directories it's executing chmod g+w. I assume this is meant to give directories execute permissions as well? If not, why not just use chmod -R g+w var vendor ..., it's much faster.

file config/artifact.excludes contains the path "pub/media".
This will exclude every path where this pattern is contained.
E.g. the amasty module "product-attachment" contains this path
vendor/amasty/product-attachment/pub/media/amasty/...
which will be excluded too.
Solution is to use a leading slash, which is no absolute path but relative to the sync root folder.
The other paths are imo not critic.

I try to execute following command

./vendor/deployer/dist/dep deploy stage_master

I get this following error (screenshot attached)

There is nothing much i have changed using same sample file, What am i doing wrong here

<?php

namespace Deployer;

require 'vendor/jalogut/magento2-deployer-plus/recipe/magento_2_2_5.php';

// Use timestamp for release name
set('release_name', function () {
    return date('YmdHis');
});

set('static_content_locales', 'en_US');

desc('Upgrades magento database restore');

// Magento dir into the project root. Set "." if magento is installed on project root
set('magento_dir', '.');
// [Optional] Git repository. Only needed if not using build + artifact strategy
set('repository', '*****************************************');
// Space separated list of languages for static-content:deploy
set('languages', 'en_US');
// Enable all caches after deployment
set('cache_enabled_caches', 'all');

// OPcache configuration
task('cache:clear:opcache', 'sudo systemctl reload php-fpm');
after('cache:clear', 'cache:clear:opcache');

// Build host
localhost('build');

// Remote Servers
host('stage_master')
    ->hostname('157.245.***.***')
    ->user('root')
    ->set('deploy_path', '~/test_m2')
    ->stage('stage')
    ->roles('master');

Using version ^1.1 for jalogut/magento2-deployer-plus
./composer.json has been updated
Loading composer repositories with package information
Updating dependencies (including require-dev)
Your requirements could not be resolved to an installable set of packages.

Problem 1
- Conclusion: don't install jalogut/magento2-deployer-plus 1.1.1
- Conclusion: remove symfony/console v2.8.34
- Conclusion: don't install symfony/console v2.8.34
- symfony/yaml v3.4.0 conflicts with symfony/console[v2.8.34].
- symfony/yaml v3.4.1 conflicts with symfony/console[v2.8.34].
- symfony/yaml v3.4.2 conflicts with symfony/console[v2.8.34].
- symfony/yaml v3.4.3 conflicts with symfony/console[v2.8.34].
- symfony/yaml v3.4.4 conflicts with symfony/console[v2.8.34].
- symfony/yaml v3.4.5 conflicts with symfony/console[v2.8.34].
- symfony/yaml v3.4.6 conflicts with symfony/console[v2.8.34].
- symfony/yaml v3.4.7 conflicts with symfony/console[v2.8.34].
- symfony/yaml v3.4.8 conflicts with symfony/console[v2.8.34].
- symfony/yaml v4.0.0 conflicts with symfony/console[v2.8.34].
- symfony/yaml v4.0.1 conflicts with symfony/console[v2.8.34].
- symfony/yaml v4.0.2 conflicts with symfony/console[v2.8.34].
- symfony/yaml v4.0.3 conflicts with symfony/console[v2.8.34].
- symfony/yaml v4.0.4 conflicts with symfony/console[v2.8.34].
- symfony/yaml v4.0.5 conflicts with symfony/console[v2.8.34].
- symfony/yaml v4.0.6 conflicts with symfony/console[v2.8.34].
- symfony/yaml v4.0.7 conflicts with symfony/console[v2.8.34].
- symfony/yaml v4.0.8 conflicts with symfony/console[v2.8.34].
- Conclusion: don't install symfony/dependency-injection v3.4.4|install symfony/yaml v3.4.0|install symfony/yaml v3.4.1|install symfony/yaml v3.4.2|install symfony/yaml v3.4.3|install symfony/yaml v3.4.4|install symfony/yaml v3.4.5|install symfony/yaml v3.4.6|install symfony/yaml v3.4.7|install symfony/yaml v3.4.8|install symfony/yaml v4.0.0|install symfony/yaml v4.0.1|install symfony/yaml v4.0.2|install symfony/yaml v4.0.3|install symfony/yaml v4.0.4|install symfony/yaml v4.0.5|install symfony/yaml v4.0.6|install symfony/yaml v4.0.7|install symfony/yaml v4.0.8
- Conclusion: don't install jalogut/magento2-deployer-plus 1.1.1|remove symfony/dependency-injection v3.4.4|install symfony/yaml v3.4.0|install symfony/yaml v3.4.1|install symfony/yaml v3.4.2|install symfony/yaml v3.4.3|install symfony/yaml v3.4.4|install symfony/yaml v3.4.5|install symfony/yaml v3.4.6|install symfony/yaml v3.4.7|install symfony/yaml v3.4.8|install symfony/yaml v4.0.0|install symfony/yaml v4.0.1|install symfony/yaml v4.0.2|install symfony/yaml v4.0.3|install symfony/yaml v4.0.4|install symfony/yaml v4.0.5|install symfony/yaml v4.0.6|install symfony/yaml v4.0.7|install symfony/yaml v4.0.8
- Conclusion: don't install jalogut/magento2-deployer-plus 1.1.1|don't install symfony/dependency-injection v3.4.4|install symfony/yaml v3.4.0|install symfony/yaml v3.4.1|install symfony/yaml v3.4.2|install symfony/yaml v3.4.3|install symfony/yaml v3.4.4|install symfony/yaml v3.4.5|install symfony/yaml v3.4.6|install symfony/yaml v3.4.7|install symfony/yaml v3.4.8|install symfony/yaml v4.0.0|install symfony/yaml v4.0.1|install symfony/yaml v4.0.2|install symfony/yaml v4.0.3|install symfony/yaml v4.0.4|install symfony/yaml v4.0.5|install symfony/yaml v4.0.6|install symfony/yaml v4.0.7|install symfony/yaml v4.0.8
- Installation request for symfony/console (locked at v2.8.34) -> satisfiable by symfony/console[v2.8.34].
- Conclusion: don't install jalogut/magento2-deployer-plus 1.1.1|remove symfony/dependency-injection v3.4.4|install symfony/yaml v3.4.0|install symfony/yaml v3.4.1|install symfony/yaml v3.4.2|install symfony/yaml v3.4.3|install symfony/yaml v3.4.4|install symfony/yaml v3.4.5|install symfony/yaml v3.4.6|install symfony/yaml v3.4.7|install symfony/yaml v3.4.8|install symfony/yaml v4.0.0|install symfony/yaml v4.0.1|install symfony/yaml v4.0.2|install symfony/yaml v4.0.3|install symfony/yaml v4.0.4|install symfony/yaml v4.0.5|install symfony/yaml v4.0.6|install symfony/yaml v4.0.7|install symfony/yaml v4.0.8
- Conclusion: don't install jalogut/magento2-deployer-plus 1.1.1|don't install symfony/dependency-injection v3.4.4|install symfony/yaml v3.4.0|install symfony/yaml v3.4.1|install symfony/yaml v3.4.2|install symfony/yaml v3.4.3|install symfony/yaml v3.4.4|install symfony/yaml v3.4.5|install symfony/yaml v3.4.6|install symfony/yaml v3.4.7|install symfony/yaml v3.4.8|install symfony/yaml v4.0.0|install symfony/yaml v4.0.1|install symfony/yaml v4.0.2|install symfony/yaml v4.0.3|install symfony/yaml v4.0.4|install symfony/yaml v4.0.5|install symfony/yaml v4.0.6|install symfony/yaml v4.0.7|install symfony/yaml v4.0.8
- Installation request for jalogut/magento2-deployer-plus ^1.1 -> satisfiable by jalogut/magento2-deployer-plus[1.1, 1.1.1].
- Conclusion: remove symfony/dependency-injection v3.4.4|install symfony/yaml v3.4.0|install symfony/yaml v3.4.1|install symfony/yaml v3.4.2|install symfony/yaml v3.4.3|install symfony/yaml v3.4.4|install symfony/yaml v3.4.5|install symfony/yaml v3.4.6|install symfony/yaml v3.4.7|install symfony/yaml v3.4.8|install symfony/yaml v4.0.0|install symfony/yaml v4.0.1|install symfony/yaml v4.0.2|install symfony/yaml v4.0.3|install symfony/yaml v4.0.4|install symfony/yaml v4.0.5|install symfony/yaml v4.0.6|install symfony/yaml v4.0.7|install symfony/yaml v4.0.8
- jalogut/magento2-deployer-plus 1.1 requires deployer/deployer ^6.0 -> satisfiable by deployer/deployer[v6.0.0, v6.0.1, v6.0.2, v6.0.3, v6.0.4, v6.0.5, v6.1.0].
- deployer/deployer v6.0.0 requires symfony/yaml ~2.7|~3.0 -> satisfiable by symfony/yaml[v2.7.0, v2.7.1, v2.7.10, v2.7.11, v2.7.12, v2.7.13, v2.7.14, v2.7.15, v2.7.16, v2.7.17, v2.7.18, v2.7.19, v2.7.2, v2.7.20, v2.7.21, v2.7.22, v2.7.23, v2.7.24, v2.7.25, v2.7.26, v2.7.27, v2.7.28, v2.7.29, v2.7.3, v2.7.30, v2.7.31, v2.7.32, v2.7.33, v2.7.34, v2.7.35, v2.7.36, v2.7.37, v2.7.38, v2.7.39, v2.7.4, v2.7.40, v2.7.41, v2.7.42, v2.7.43, v2.7.44, v2.7.45, v2.7.5, v2.7.6, v2.7.7, v2.7.8, v2.7.9, v2.8.0, v2.8.1, v2.8.10, v2.8.11, v2.8.12, v2.8.13, v2.8.14, v2.8.15, v2.8.16, v2.8.17, v2.8.18, v2.8.19, v2.8.2, v2.8.20, v2.8.21, v2.8.22, v2.8.23, v2.8.24, v2.8.25, v2.8.26, v2.8.27, v2.8.28, v2.8.29, v2.8.3, v2.8.30, v2.8.31, v2.8.32, v2.8.33, v2.8.34, v2.8.35, v2.8.36, v2.8.37, v2.8.38, v2.8.4, v2.8.5, v2.8.6, v2.8.7, v2.8.8, v2.8.9, v3.0.0, v3.0.1, v3.0.2, v3.0.3, v3.0.4, v3.0.5, v3.0.6, v3.0.7, v3.0.8, v3.0.9, v3.1.0, v3.1.1, v3.1.10, v3.1.2, v3.1.3, v3.1.4, v3.1.5, v3.1.6, v3.1.7, v3.1.8, v3.1.9, v3.2.0, v3.2.1, v3.2.10, v3.2.11, v3.2.12, v3.2.13, v3.2.14, v3.2.2, v3.2.3, v3.2.4, v3.2.5, v3.2.6, v3.2.7, v3.2.8, v3.2.9, v3.3.0, v3.3.1, v3.3.10, v3.3.11, v3.3.12, v3.3.13, v3.3.14, v3.3.15, v3.3.16, v3.3.2, v3.3.3, v3.3.4, v3.3.5, v3.3.6, v3.3.7, v3.3.8, v3.3.9, v3.4.0, v3.4.1, v3.4.2, v3.4.3, v3.4.4, v3.4.5, v3.4.6, v3.4.7, v3.4.8].
- deployer/deployer v6.0.1 requires symfony/yaml ~2.7|~3.0 -> satisfiable by symfony/yaml[v2.7.0, v2.7.1, v2.7.10, v2.7.11, v2.7.12, v2.7.13, v2.7.14, v2.7.15, v2.7.16, v2.7.17, v2.7.18, v2.7.19, v2.7.2, v2.7.20, v2.7.21, v2.7.22, v2.7.23, v2.7.24, v2.7.25, v2.7.26, v2.7.27, v2.7.28, v2.7.29, v2.7.3, v2.7.30, v2.7.31, v2.7.32, v2.7.33, v2.7.34, v2.7.35, v2.7.36, v2.7.37, v2.7.38, v2.7.39, v2.7.4, v2.7.40, v2.7.41, v2.7.42, v2.7.43, v2.7.44, v2.7.45, v2.7.5, v2.7.6, v2.7.7, v2.7.8, v2.7.9, v2.8.0, v2.8.1, v2.8.10, v2.8.11, v2.8.12, v2.8.13, v2.8.14, v2.8.15, v2.8.16, v2.8.17, v2.8.18, v2.8.19, v2.8.2, v2.8.20, v2.8.21, v2.8.22, v2.8.23, v2.8.24, v2.8.25, v2.8.26, v2.8.27, v2.8.28, v2.8.29, v2.8.3, v2.8.30, v2.8.31, v2.8.32, v2.8.33, v2.8.34, v2.8.35, v2.8.36, v2.8.37, v2.8.38, v2.8.4, v2.8.5, v2.8.6, v2.8.7, v2.8.8, v2.8.9, v3.0.0, v3.0.1, v3.0.2, v3.0.3, v3.0.4, v3.0.5, v3.0.6, v3.0.7, v3.0.8, v3.0.9, v3.1.0, v3.1.1, v3.1.10, v3.1.2, v3.1.3, v3.1.4, v3.1.5, v3.1.6, v3.1.7, v3.1.8, v3.1.9, v3.2.0, v3.2.1, v3.2.10, v3.2.11, v3.2.12, v3.2.13, v3.2.14, v3.2.2, v3.2.3, v3.2.4, v3.2.5, v3.2.6, v3.2.7, v3.2.8, v3.2.9, v3.3.0, v3.3.1, v3.3.10, v3.3.11, v3.3.12, v3.3.13, v3.3.14, v3.3.15, v3.3.16, v3.3.2, v3.3.3, v3.3.4, v3.3.5, v3.3.6, v3.3.7, v3.3.8, v3.3.9, v3.4.0, v3.4.1, v3.4.2, v3.4.3, v3.4.4, v3.4.5, v3.4.6, v3.4.7, v3.4.8].
- deployer/deployer v6.0.2 requires symfony/yaml ~2.7|~3.0 -> satisfiable by symfony/yaml[v2.7.0, v2.7.1, v2.7.10, v2.7.11, v2.7.12, v2.7.13, v2.7.14, v2.7.15, v2.7.16, v2.7.17, v2.7.18, v2.7.19, v2.7.2, v2.7.20, v2.7.21, v2.7.22, v2.7.23, v2.7.24, v2.7.25, v2.7.26, v2.7.27, v2.7.28, v2.7.29, v2.7.3, v2.7.30, v2.7.31, v2.7.32, v2.7.33, v2.7.34, v2.7.35, v2.7.36, v2.7.37, v2.7.38, v2.7.39, v2.7.4, v2.7.40, v2.7.41, v2.7.42, v2.7.43, v2.7.44, v2.7.45, v2.7.5, v2.7.6, v2.7.7, v2.7.8, v2.7.9, v2.8.0, v2.8.1, v2.8.10, v2.8.11, v2.8.12, v2.8.13, v2.8.14, v2.8.15, v2.8.16, v2.8.17, v2.8.18, v2.8.19, v2.8.2, v2.8.20, v2.8.21, v2.8.22, v2.8.23, v2.8.24, v2.8.25, v2.8.26, v2.8.27, v2.8.28, v2.8.29, v2.8.3, v2.8.30, v2.8.31, v2.8.32, v2.8.33, v2.8.34, v2.8.35, v2.8.36, v2.8.37, v2.8.38, v2.8.4, v2.8.5, v2.8.6, v2.8.7, v2.8.8, v2.8.9, v3.0.0, v3.0.1, v3.0.2, v3.0.3, v3.0.4, v3.0.5, v3.0.6, v3.0.7, v3.0.8, v3.0.9, v3.1.0, v3.1.1, v3.1.10, v3.1.2, v3.1.3, v3.1.4, v3.1.5, v3.1.6, v3.1.7, v3.1.8, v3.1.9, v3.2.0, v3.2.1, v3.2.10, v3.2.11, v3.2.12, v3.2.13, v3.2.14, v3.2.2, v3.2.3, v3.2.4, v3.2.5, v3.2.6, v3.2.7, v3.2.8, v3.2.9, v3.3.0, v3.3.1, v3.3.10, v3.3.11, v3.3.12, v3.3.13, v3.3.14, v3.3.15, v3.3.16, v3.3.2, v3.3.3, v3.3.4, v3.3.5, v3.3.6, v3.3.7, v3.3.8, v3.3.9, v3.4.0, v3.4.1, v3.4.2, v3.4.3, v3.4.4, v3.4.5, v3.4.6, v3.4.7, v3.4.8].
- deployer/deployer v6.0.3 requires symfony/yaml ~2.7|~3.0 -> satisfiable by symfony/yaml[v2.7.0, v2.7.1, v2.7.10, v2.7.11, v2.7.12, v2.7.13, v2.7.14, v2.7.15, v2.7.16, v2.7.17, v2.7.18, v2.7.19, v2.7.2, v2.7.20, v2.7.21, v2.7.22, v2.7.23, v2.7.24, v2.7.25, v2.7.26, v2.7.27, v2.7.28, v2.7.29, v2.7.3, v2.7.30, v2.7.31, v2.7.32, v2.7.33, v2.7.34, v2.7.35, v2.7.36, v2.7.37, v2.7.38, v2.7.39, v2.7.4, v2.7.40, v2.7.41, v2.7.42, v2.7.43, v2.7.44, v2.7.45, v2.7.5, v2.7.6, v2.7.7, v2.7.8, v2.7.9, v2.8.0, v2.8.1, v2.8.10, v2.8.11, v2.8.12, v2.8.13, v2.8.14, v2.8.15, v2.8.16, v2.8.17, v2.8.18, v2.8.19, v2.8.2, v2.8.20, v2.8.21, v2.8.22, v2.8.23, v2.8.24, v2.8.25, v2.8.26, v2.8.27, v2.8.28, v2.8.29, v2.8.3, v2.8.30, v2.8.31, v2.8.32, v2.8.33, v2.8.34, v2.8.35, v2.8.36, v2.8.37, v2.8.38, v2.8.4, v2.8.5, v2.8.6, v2.8.7, v2.8.8, v2.8.9, v3.0.0, v3.0.1, v3.0.2, v3.0.3, v3.0.4, v3.0.5, v3.0.6, v3.0.7, v3.0.8, v3.0.9, v3.1.0, v3.1.1, v3.1.10, v3.1.2, v3.1.3, v3.1.4, v3.1.5, v3.1.6, v3.1.7, v3.1.8, v3.1.9, v3.2.0, v3.2.1, v3.2.10, v3.2.11, v3.2.12, v3.2.13, v3.2.14, v3.2.2, v3.2.3, v3.2.4, v3.2.5, v3.2.6, v3.2.7, v3.2.8, v3.2.9, v3.3.0, v3.3.1, v3.3.10, v3.3.11, v3.3.12, v3.3.13, v3.3.14, v3.3.15, v3.3.16, v3.3.2, v3.3.3, v3.3.4, v3.3.5, v3.3.6, v3.3.7, v3.3.8, v3.3.9, v3.4.0, v3.4.1, v3.4.2, v3.4.3, v3.4.4, v3.4.5, v3.4.6, v3.4.7, v3.4.8].
- deployer/deployer v6.0.4 requires symfony/yaml ~2.7|~3.0 -> satisfiable by symfony/yaml[v2.7.0, v2.7.1, v2.7.10, v2.7.11, v2.7.12, v2.7.13, v2.7.14, v2.7.15, v2.7.16, v2.7.17, v2.7.18, v2.7.19, v2.7.2, v2.7.20, v2.7.21, v2.7.22, v2.7.23, v2.7.24, v2.7.25, v2.7.26, v2.7.27, v2.7.28, v2.7.29, v2.7.3, v2.7.30, v2.7.31, v2.7.32, v2.7.33, v2.7.34, v2.7.35, v2.7.36, v2.7.37, v2.7.38, v2.7.39, v2.7.4, v2.7.40, v2.7.41, v2.7.42, v2.7.43, v2.7.44, v2.7.45, v2.7.5, v2.7.6, v2.7.7, v2.7.8, v2.7.9, v2.8.0, v2.8.1, v2.8.10, v2.8.11, v2.8.12, v2.8.13, v2.8.14, v2.8.15, v2.8.16, v2.8.17, v2.8.18, v2.8.19, v2.8.2, v2.8.20, v2.8.21, v2.8.22, v2.8.23, v2.8.24, v2.8.25, v2.8.26, v2.8.27, v2.8.28, v2.8.29, v2.8.3, v2.8.30, v2.8.31, v2.8.32, v2.8.33, v2.8.34, v2.8.35, v2.8.36, v2.8.37, v2.8.38, v2.8.4, v2.8.5, v2.8.6, v2.8.7, v2.8.8, v2.8.9, v3.0.0, v3.0.1, v3.0.2, v3.0.3, v3.0.4, v3.0.5, v3.0.6, v3.0.7, v3.0.8, v3.0.9, v3.1.0, v3.1.1, v3.1.10, v3.1.2, v3.1.3, v3.1.4, v3.1.5, v3.1.6, v3.1.7, v3.1.8, v3.1.9, v3.2.0, v3.2.1, v3.2.10, v3.2.11, v3.2.12, v3.2.13, v3.2.14, v3.2.2, v3.2.3, v3.2.4, v3.2.5, v3.2.6, v3.2.7, v3.2.8, v3.2.9, v3.3.0, v3.3.1, v3.3.10, v3.3.11, v3.3.12, v3.3.13, v3.3.14, v3.3.15, v3.3.16, v3.3.2, v3.3.3, v3.3.4, v3.3.5, v3.3.6, v3.3.7, v3.3.8, v3.3.9, v3.4.0, v3.4.1, v3.4.2, v3.4.3, v3.4.4, v3.4.5, v3.4.6, v3.4.7, v3.4.8].
- deployer/deployer v6.0.5 requires symfony/yaml ~2.7|~3.0 -> satisfiable by symfony/yaml[v2.7.0, v2.7.1, v2.7.10, v2.7.11, v2.7.12, v2.7.13, v2.7.14, v2.7.15, v2.7.16, v2.7.17, v2.7.18, v2.7.19, v2.7.2, v2.7.20, v2.7.21, v2.7.22, v2.7.23, v2.7.24, v2.7.25, v2.7.26, v2.7.27, v2.7.28, v2.7.29, v2.7.3, v2.7.30, v2.7.31, v2.7.32, v2.7.33, v2.7.34, v2.7.35, v2.7.36, v2.7.37, v2.7.38, v2.7.39, v2.7.4, v2.7.40, v2.7.41, v2.7.42, v2.7.43, v2.7.44, v2.7.45, v2.7.5, v2.7.6, v2.7.7, v2.7.8, v2.7.9, v2.8.0, v2.8.1, v2.8.10, v2.8.11, v2.8.12, v2.8.13, v2.8.14, v2.8.15, v2.8.16, v2.8.17, v2.8.18, v2.8.19, v2.8.2, v2.8.20, v2.8.21, v2.8.22, v2.8.23, v2.8.24, v2.8.25, v2.8.26, v2.8.27, v2.8.28, v2.8.29, v2.8.3, v2.8.30, v2.8.31, v2.8.32, v2.8.33, v2.8.34, v2.8.35, v2.8.36, v2.8.37, v2.8.38, v2.8.4, v2.8.5, v2.8.6, v2.8.7, v2.8.8, v2.8.9, v3.0.0, v3.0.1, v3.0.2, v3.0.3, v3.0.4, v3.0.5, v3.0.6, v3.0.7, v3.0.8, v3.0.9, v3.1.0, v3.1.1, v3.1.10, v3.1.2, v3.1.3, v3.1.4, v3.1.5, v3.1.6, v3.1.7, v3.1.8, v3.1.9, v3.2.0, v3.2.1, v3.2.10, v3.2.11, v3.2.12, v3.2.13, v3.2.14, v3.2.2, v3.2.3, v3.2.4, v3.2.5, v3.2.6, v3.2.7, v3.2.8, v3.2.9, v3.3.0, v3.3.1, v3.3.10, v3.3.11, v3.3.12, v3.3.13, v3.3.14, v3.3.15, v3.3.16, v3.3.2, v3.3.3, v3.3.4, v3.3.5, v3.3.6, v3.3.7, v3.3.8, v3.3.9, v3.4.0, v3.4.1, v3.4.2, v3.4.3, v3.4.4, v3.4.5, v3.4.6, v3.4.7, v3.4.8].
- deployer/deployer v6.1.0 requires symfony/yaml ~2.7|~3.0|~4.0 -> satisfiable by symfony/yaml[v2.7.0, v2.7.1, v2.7.10, v2.7.11, v2.7.12, v2.7.13, v2.7.14, v2.7.15, v2.7.16, v2.7.17, v2.7.18, v2.7.19, v2.7.2, v2.7.20, v2.7.21, v2.7.22, v2.7.23, v2.7.24, v2.7.25, v2.7.26, v2.7.27, v2.7.28, v2.7.29, v2.7.3, v2.7.30, v2.7.31, v2.7.32, v2.7.33, v2.7.34, v2.7.35, v2.7.36, v2.7.37, v2.7.38, v2.7.39, v2.7.4, v2.7.40, v2.7.41, v2.7.42, v2.7.43, v2.7.44, v2.7.45, v2.7.5, v2.7.6, v2.7.7, v2.7.8, v2.7.9, v2.8.0, v2.8.1, v2.8.10, v2.8.11, v2.8.12, v2.8.13, v2.8.14, v2.8.15, v2.8.16, v2.8.17, v2.8.18, v2.8.19, v2.8.2, v2.8.20, v2.8.21, v2.8.22, v2.8.23, v2.8.24, v2.8.25, v2.8.26, v2.8.27, v2.8.28, v2.8.29, v2.8.3, v2.8.30, v2.8.31, v2.8.32, v2.8.33, v2.8.34, v2.8.35, v2.8.36, v2.8.37, v2.8.38, v2.8.4, v2.8.5, v2.8.6, v2.8.7, v2.8.8, v2.8.9, v3.0.0, v3.0.1, v3.0.2, v3.0.3, v3.0.4, v3.0.5, v3.0.6, v3.0.7, v3.0.8, v3.0.9, v3.1.0, v3.1.1, v3.1.10, v3.1.2, v3.1.3, v3.1.4, v3.1.5, v3.1.6, v3.1.7, v3.1.8, v3.1.9, v3.2.0, v3.2.1, v3.2.10, v3.2.11, v3.2.12, v3.2.13, v3.2.14, v3.2.2, v3.2.3, v3.2.4, v3.2.5, v3.2.6, v3.2.7, v3.2.8, v3.2.9, v3.3.0, v3.3.1, v3.3.10, v3.3.11, v3.3.12, v3.3.13, v3.3.14, v3.3.15, v3.3.16, v3.3.2, v3.3.3, v3.3.4, v3.3.5, v3.3.6, v3.3.7, v3.3.8, v3.3.9, v3.4.0, v3.4.1, v3.4.2, v3.4.3, v3.4.4, v3.4.5, v3.4.6, v3.4.7, v3.4.8, v4.0.0, v4.0.1, v4.0.2, v4.0.3, v4.0.4, v4.0.5, v4.0.6, v4.0.7, v4.0.8].
- symfony/yaml v2.7.0 conflicts with symfony/dependency-injection[v3.4.4].
- symfony/yaml v2.7.1 conflicts with symfony/dependency-injection[v3.4.4].
- symfony/yaml v2.7.10 conflicts with symfony/dependency-injection[v3.4.4].
- symfony/yaml v2.7.11 conflicts with symfony/dependency-injection[v3.4.4].
- symfony/yaml v2.7.12 conflicts with symfony/dependency-injection[v3.4.4].
- symfony/yaml v2.7.13 conflicts with symfony/dependency-injection[v3.4.4].
- symfony/yaml v2.7.14 conflicts with symfony/dependency-injection[v3.4.4].
- symfony/yaml v2.7.15 conflicts with symfony/dependency-injection[v3.4.4].
- symfony/yaml v2.7.16 conflicts with symfony/dependency-injection[v3.4.4].
- symfony/yaml v2.7.17 conflicts with symfony/dependency-injection[v3.4.4].
- symfony/yaml v2.7.18 conflicts with symfony/dependency-injection[v3.4.4].
- symfony/yaml v2.7.19 conflicts with symfony/dependency-injection[v3.4.4].
- symfony/yaml v2.7.2 conflicts with symfony/dependency-injection[v3.4.4].
- symfony/yaml v2.7.20 conflicts with symfony/dependency-injection[v3.4.4].
- symfony/yaml v2.7.21 conflicts with symfony/dependency-injection[v3.4.4].
- symfony/yaml v2.7.22 conflicts with symfony/dependency-injection[v3.4.4].
- symfony/yaml v2.7.23 conflicts with symfony/dependency-injection[v3.4.4].
- symfony/yaml v2.7.24 conflicts with symfony/dependency-injection[v3.4.4].
- symfony/yaml v2.7.25 conflicts with symfony/dependency-injection[v3.4.4].
- symfony/yaml v2.7.26 conflicts with symfony/dependency-injection[v3.4.4].
- symfony/yaml v2.7.27 conflicts with symfony/dependency-injection[v3.4.4].
- symfony/yaml v2.7.28 conflicts with symfony/dependency-injection[v3.4.4].
- symfony/yaml v2.7.29 conflicts with symfony/dependency-injection[v3.4.4].
- symfony/yaml v2.7.3 conflicts with symfony/dependency-injection[v3.4.4].
- symfony/yaml v2.7.30 conflicts with symfony/dependency-injection[v3.4.4].
- symfony/yaml v2.7.31 conflicts with symfony/dependency-injection[v3.4.4].
- symfony/yaml v2.7.32 conflicts with symfony/dependency-injection[v3.4.4].
- symfony/yaml v2.7.33 conflicts with symfony/dependency-injection[v3.4.4].
- symfony/yaml v2.7.34 conflicts with symfony/dependency-injection[v3.4.4].
- symfony/yaml v2.7.35 conflicts with symfony/dependency-injection[v3.4.4].
- symfony/yaml v2.7.36 conflicts with symfony/dependency-injection[v3.4.4].
- symfony/yaml v2.7.37 conflicts with symfony/dependency-injection[v3.4.4].
- symfony/yaml v2.7.38 conflicts with symfony/dependency-injection[v3.4.4].
- symfony/yaml v2.7.39 conflicts with symfony/dependency-injection[v3.4.4].
- symfony/yaml v2.7.4 conflicts with symfony/dependency-injection[v3.4.4].
- symfony/yaml v2.7.40 conflicts with symfony/dependency-injection[v3.4.4].
- symfony/yaml v2.7.41 conflicts with symfony/dependency-injection[v3.4.4].
- symfony/yaml v2.7.42 conflicts with symfony/dependency-injection[v3.4.4].
- symfony/yaml v2.7.43 conflicts with symfony/dependency-injection[v3.4.4].
- symfony/yaml v2.7.44 conflicts with symfony/dependency-injection[v3.4.4].
- symfony/yaml v2.7.45 conflicts with symfony/dependency-injection[v3.4.4].
- symfony/yaml v2.7.5 conflicts with symfony/dependency-injection[v3.4.4].
- symfony/yaml v2.7.6 conflicts with symfony/dependency-injection[v3.4.4].
- symfony/yaml v2.7.7 conflicts with symfony/dependency-injection[v3.4.4].
- symfony/yaml v2.7.8 conflicts with symfony/dependency-injection[v3.4.4].
- symfony/yaml v2.7.9 conflicts with symfony/dependency-injection[v3.4.4].
- symfony/yaml v2.8.0 conflicts with symfony/dependency-injection[v3.4.4].
- symfony/yaml v2.8.1 conflicts with symfony/dependency-injection[v3.4.4].
- symfony/yaml v2.8.10 conflicts with symfony/dependency-injection[v3.4.4].
- symfony/yaml v2.8.11 conflicts with symfony/dependency-injection[v3.4.4].
- symfony/yaml v2.8.12 conflicts with symfony/dependency-injection[v3.4.4].
- symfony/yaml v2.8.13 conflicts with symfony/dependency-injection[v3.4.4].
- symfony/yaml v2.8.14 conflicts with symfony/dependency-injection[v3.4.4].
- symfony/yaml v2.8.15 conflicts with symfony/dependency-injection[v3.4.4].
- symfony/yaml v2.8.16 conflicts with symfony/dependency-injection[v3.4.4].
- symfony/yaml v2.8.17 conflicts with symfony/dependency-injection[v3.4.4].
- symfony/yaml v2.8.18 conflicts with symfony/dependency-injection[v3.4.4].
- symfony/yaml v2.8.19 conflicts with symfony/dependency-injection[v3.4.4].
- symfony/yaml v2.8.2 conflicts with symfony/dependency-injection[v3.4.4].
- symfony/yaml v2.8.20 conflicts with symfony/dependency-injection[v3.4.4].
- symfony/yaml v2.8.21 conflicts with symfony/dependency-injection[v3.4.4].
- symfony/yaml v2.8.22 conflicts with symfony/dependency-injection[v3.4.4].
- symfony/yaml v2.8.23 conflicts with symfony/dependency-injection[v3.4.4].
- symfony/yaml v2.8.24 conflicts with symfony/dependency-injection[v3.4.4].
- symfony/yaml v2.8.25 conflicts with symfony/dependency-injection[v3.4.4].
- symfony/yaml v2.8.26 conflicts with symfony/dependency-injection[v3.4.4].
- symfony/yaml v2.8.27 conflicts with symfony/dependency-injection[v3.4.4].
- symfony/yaml v2.8.28 conflicts with symfony/dependency-injection[v3.4.4].
- symfony/yaml v2.8.29 conflicts with symfony/dependency-injection[v3.4.4].
- symfony/yaml v2.8.3 conflicts with symfony/dependency-injection[v3.4.4].
- symfony/yaml v2.8.30 conflicts with symfony/dependency-injection[v3.4.4].
- symfony/yaml v2.8.31 conflicts with symfony/dependency-injection[v3.4.4].
- symfony/yaml v2.8.32 conflicts with symfony/dependency-injection[v3.4.4].
- symfony/yaml v2.8.33 conflicts with symfony/dependency-injection[v3.4.4].
- symfony/yaml v2.8.34 conflicts with symfony/dependency-injection[v3.4.4].
- symfony/yaml v2.8.35 conflicts with symfony/dependency-injection[v3.4.4].
- symfony/yaml v2.8.36 conflicts with symfony/dependency-injection[v3.4.4].
- symfony/yaml v2.8.37 conflicts with symfony/dependency-injection[v3.4.4].
- symfony/yaml v2.8.38 conflicts with symfony/dependency-injection[v3.4.4].
- symfony/yaml v2.8.4 conflicts with symfony/dependency-injection[v3.4.4].
- symfony/yaml v2.8.5 conflicts with symfony/dependency-injection[v3.4.4].
- symfony/yaml v2.8.6 conflicts with symfony/dependency-injection[v3.4.4].
- symfony/yaml v2.8.7 conflicts with symfony/dependency-injection[v3.4.4].
- symfony/yaml v2.8.8 conflicts with symfony/dependency-injection[v3.4.4].
- symfony/yaml v2.8.9 conflicts with symfony/dependency-injection[v3.4.4].
- symfony/yaml v3.0.0 conflicts with symfony/dependency-injection[v3.4.4].
- symfony/yaml v3.0.1 conflicts with symfony/dependency-injection[v3.4.4].
- symfony/yaml v3.0.2 conflicts with symfony/dependency-injection[v3.4.4].
- symfony/yaml v3.0.3 conflicts with symfony/dependency-injection[v3.4.4].
- symfony/yaml v3.0.4 conflicts with symfony/dependency-injection[v3.4.4].
- symfony/yaml v3.0.5 conflicts with symfony/dependency-injection[v3.4.4].
- symfony/yaml v3.0.6 conflicts with symfony/dependency-injection[v3.4.4].
- symfony/yaml v3.0.7 conflicts with symfony/dependency-injection[v3.4.4].
- symfony/yaml v3.0.8 conflicts with symfony/dependency-injection[v3.4.4].
- symfony/yaml v3.0.9 conflicts with symfony/dependency-injection[v3.4.4].
- symfony/yaml v3.1.0 conflicts with symfony/dependency-injection[v3.4.4].
- symfony/yaml v3.1.1 conflicts with symfony/dependency-injection[v3.4.4].
- symfony/yaml v3.1.10 conflicts with symfony/dependency-injection[v3.4.4].
- symfony/yaml v3.1.2 conflicts with symfony/dependency-injection[v3.4.4].
- symfony/yaml v3.1.3 conflicts with symfony/dependency-injection[v3.4.4].
- symfony/yaml v3.1.4 conflicts with symfony/dependency-injection[v3.4.4].
- symfony/yaml v3.1.5 conflicts with symfony/dependency-injection[v3.4.4].
- symfony/yaml v3.1.6 conflicts with symfony/dependency-injection[v3.4.4].
- symfony/yaml v3.1.7 conflicts with symfony/dependency-injection[v3.4.4].
- symfony/yaml v3.1.8 conflicts with symfony/dependency-injection[v3.4.4].
- symfony/yaml v3.1.9 conflicts with symfony/dependency-injection[v3.4.4].
- symfony/yaml v3.2.0 conflicts with symfony/dependency-injection[v3.4.4].
- symfony/yaml v3.2.1 conflicts with symfony/dependency-injection[v3.4.4].
- symfony/yaml v3.2.10 conflicts with symfony/dependency-injection[v3.4.4].
- symfony/yaml v3.2.11 conflicts with symfony/dependency-injection[v3.4.4].
- symfony/yaml v3.2.12 conflicts with symfony/dependency-injection[v3.4.4].
- symfony/yaml v3.2.13 conflicts with symfony/dependency-injection[v3.4.4].
- symfony/yaml v3.2.14 conflicts with symfony/dependency-injection[v3.4.4].
- symfony/yaml v3.2.2 conflicts with symfony/dependency-injection[v3.4.4].
- symfony/yaml v3.2.3 conflicts with symfony/dependency-injection[v3.4.4].
- symfony/yaml v3.2.4 conflicts with symfony/dependency-injection[v3.4.4].
- symfony/yaml v3.2.5 conflicts with symfony/dependency-injection[v3.4.4].
- symfony/yaml v3.2.6 conflicts with symfony/dependency-injection[v3.4.4].
- symfony/yaml v3.2.7 conflicts with symfony/dependency-injection[v3.4.4].
- symfony/yaml v3.2.8 conflicts with symfony/dependency-injection[v3.4.4].
- symfony/yaml v3.2.9 conflicts with symfony/dependency-injection[v3.4.4].
- symfony/yaml v3.3.0 conflicts with symfony/dependency-injection[v3.4.4].
- symfony/yaml v3.3.1 conflicts with symfony/dependency-injection[v3.4.4].
- symfony/yaml v3.3.10 conflicts with symfony/dependency-injection[v3.4.4].
- symfony/yaml v3.3.11 conflicts with symfony/dependency-injection[v3.4.4].
- symfony/yaml v3.3.12 conflicts with symfony/dependency-injection[v3.4.4].
- symfony/yaml v3.3.13 conflicts with symfony/dependency-injection[v3.4.4].
- symfony/yaml v3.3.14 conflicts with symfony/dependency-injection[v3.4.4].
- symfony/yaml v3.3.15 conflicts with symfony/dependency-injection[v3.4.4].
- symfony/yaml v3.3.16 conflicts with symfony/dependency-injection[v3.4.4].
- symfony/yaml v3.3.2 conflicts with symfony/dependency-injection[v3.4.4].
- symfony/yaml v3.3.3 conflicts with symfony/dependency-injection[v3.4.4].
- symfony/yaml v3.3.4 conflicts with symfony/dependency-injection[v3.4.4].
- symfony/yaml v3.3.5 conflicts with symfony/dependency-injection[v3.4.4].
- symfony/yaml v3.3.6 conflicts with symfony/dependency-injection[v3.4.4].
- symfony/yaml v3.3.7 conflicts with symfony/dependency-injection[v3.4.4].
- symfony/yaml v3.3.8 conflicts with symfony/dependency-injection[v3.4.4].
- symfony/yaml v3.3.9 conflicts with symfony/dependency-injection[v3.4.4].
- Installation request for symfony/dependency-injection (locked at v3.4.4) -> satisfiable by symfony/dependency-injection[v3.4.4].

Installation failed, reverting ./composer.json to its original content.