From b06a6914a6fd673d7477ac257ebbc837742b75f0 Mon Sep 17 00:00:00 2001 From: nektru Date: Thu, 28 Jul 2016 14:51:46 +0300 Subject: [PATCH] `composer update` should be run by developer before testing new release. Users should perform `composer install` to install the same version of the dependencies that have been used by the developer during testing --- Updating-PHPCI.md | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/Updating-PHPCI.md b/Updating-PHPCI.md index 74656e9..fbc0861 100644 --- a/Updating-PHPCI.md +++ b/Updating-PHPCI.md @@ -3,6 +3,6 @@ Updating PHPCI to the latest release, or even dev-master updates is something th 1. Go to your PHPCI root folder in a Terminal. 2. Pull the latest code. On Linux and Mac this would look like this: `git pull` 3. Update the PHPCI database: `./console phpci:update` -4. Update the composer and its packages: `composer self-update && composer update` +4. Update the composer and its packages: `composer self-update && composer install` 5. Return to the PHPCI admin screens and check your desired plugins are still installed correctly. 7. Run a build to make sure everything is working as expected. \ No newline at end of file