cancel
Showing results for 
Search instead for 
Did you mean: 

Script update 2.3.1 to 2.3.2 success - version not updated

SOLVED

Script update 2.3.1 to 2.3.2 success - version not updated

Hi! I've just updated my 2.3.1 to 2.3.2 using

 pre_composer_update_2.3.php

 

$ php -f pre_composer_update_2.3.php -- --root='magento/' --repo=https://repo.magento.com/
**** Searching for a matching version of magento/project-community-edition ****

Checking https://repo.magento.com/
 Running command:
  composer --working-dir='magento/' create-project --repository=https://repo.magento.com/ magento/project-community-edition='2.3.*' magento//temp_project --no-install --no-interaction
    Installing magento/project-community-edition (2.3.2)
      - Installing magento/project-community-edition (2.3.2): Loading from cache
    Created project in magento//temp_project

 

Everything went smoothly, no errors, packages updated successfully, but when I run Magento admin is still showing version 2.3.1 in the bottom of the page. The

bin/magento -version 

command also returns version 2.3.1. How could that be? I've checked my composer.json file after update and it still has 

"require": { "magento/product-community-edition": "2.3.1", },

There's also a new folder in my Magento root folder that looks like some files left from update process. 

 

What did I do wrong?

1 ACCEPTED SOLUTION

Accepted Solutions

Re: Script update 2.3.1 to 2.3.2 success - version not updated

Solved this by updating manually via composer instead of script

View solution in original post

1 REPLY 1

Re: Script update 2.3.1 to 2.3.2 success - version not updated

Solved this by updating manually via composer instead of script