The individual modules that make up KUSANAGI have been updated.
The updated module versions are as follows:

PHP	7.3.0

The module update can be applied with the following command:

# yum update

The individual modules that make up KUSANAGI have been updated.
The updated module versions are as follows:

nginx	1.15.7
OpenSSL	1.1.1a

The module update can be applied with the following command:

# yum update

The individual modules that make up KUSANAGI have been updated.
The updated module versions are as follows:

nginx	1.15.6
PHP7	7.2.12
httpd	2.4.37
WP-CLI	2.0.1

Please confirm before updating:

With this update, when you update your PHP version, the PHP execution path will reflect the change. There are a few things that need to be confirmed:

# kusanagi php7
use php7
Done.
# php -v
PHP 7.2.12 (cli) (built: Nov 12 2018 10:24:25) ( NTS )
Copyright (c) 1997-2018 The PHP Group
Zend Engine v3.2.0, Copyright (c) 1998-2018 Zend Technologies
    with Zend OPcache v7.2.12, Copyright (c) 1999-2018, by Zend Technologies

Are there any scripts (cron, etc) calling php?

With calls like the one below, it is likely that without any specific settings php will point to PHP7 after updating.

# crontab -e
10 9 * * * php /home/kusanagi/example.php > /dev/null

To deliberately choose PHP5.6 for the interpreter, you need to make the following changes:

# crontab -e
10 9 * * * /usr/bin/php /home/kusanagi/example.php > /dev/null

Please make any necessary changes to other ‘php’ scripts not specifying the full path.

How to deliberately run PHP5.6

In a PHP5.6 environment, the php execution path will still point to PHP 5.6.

# kusanagi php-fpm
# php -v
PHP 5.6.38 (cli) (built: Oct 24 2018 12:50:38) 
Copyright (c) 1997-2016 The PHP Group
Zend Engine v2.6.0, Copyright (c) 1998-2016 Zend Technologies
    with Zend OPcache v7.0.6-dev, Copyright (c) 1999-2016, by Zend Technologies

However, in a PHP7 environment, if you want to run PHP5.6, you will need to use the /usr/bin/php full path as follows:

# kusanagi php7
# /usr/bin/php -v
PHP 5.6.38 (cli) (built: Oct 24 2018 12:50:38) 
Copyright (c) 1997-2016 The PHP Group
Zend Engine v2.6.0, Copyright (c) 1998-2016 Zend Technologies
    with Zend OPcache v7.0.6-dev, Copyright (c) 1999-2016, by Zend Technologies

What about the php7 command?

The php7 command still points to PHP7.

# php7 -v
PHP 7.2.12 (cli) (built: Nov 12 2018 10:24:25) ( NTS )
Copyright (c) 1997-2018 The PHP Group
Zend Engine v3.2.0, Copyright (c) 1998-2018 Zend Technologies
    with Zend OPcache v7.2.12, Copyright (c) 1999-2018, by Zend Technologies

If the message below appears, it is possible that the old PHP execution path is still in the cache, so follow the instructions and run the hash command.

NOTICE: Please run the following command to change the php command path in the current shell.

$ hash -r

The module update can be applied with the following command:

# yum update