2002.0.8
shiftedreality
released this
25 Jan 13:13
·
460 commits
to 2002.0
since this release
Changelog (23 related PRs)
We merged vendor/magento/ece-patches
into vendor/magento/ece-tools
in this release. You no longer need to update the vendor/magento/ece-patches
package separately.
- New features
- Improved logging
- We improved log messaging to provide better explanations when the build or deploy process overrides an environment variable.
- You can now view installation and upgrade progress in real time. Tail the
install_update.log
file to view progress. For example,tail -f var/log/install_upgrade.log
- New cron command—You can now unlock specific stuck cron jobs instead of stopping and re-launching all of them with the
cron:unlock
command. Not available in 2.1. - Unified configuration file—You can now configure build and deploy stages using a
.magento.env.yaml
file. - Backup configuration files—The deployment process now automatically creates a backup of the
app/etc/env.php
andapp/etc/config.php
configuration files after deployment. We also added a new CLI command to restore these configuration files from a backup. - Troubleshooting validation errors—We changed the command you must use to resolve validation errors when
config.php
does not contain enough data for static content deployment. Previously, the error message instructed you to runbin/magento app:config:dump
. Now, you must runphp ./vendor/bin/ece-tools config:dump
. - New environment variables—You can now use environment variables to connect custom search and AMQP-based services to your site.
- We implemented smart patching. Now the package applies patches based not on Magento version, but on patched package version.
- Improved logging
- Resolved issues
- We fixed a logging issue that was causing build errors.
- We fixed an issue that was causing timeout exceptions when running deployments in interactive mode.
- We fixed an issue that was causing errors when using the compact strategy for static content generation. Not available in 2.1.
- We fixed an issue that was preventing the deployment script from properly identifying staging and production environments.
- We fixed an issue that was causing network issues to disrupt database connections and cause failures during the installation and upgrade process.
- We fixed an issue preventing you from exporting the configuration files using
app:config:dump
more than once. Not available in 2.1. - We fixed a Redis session locking issue that caused an Admin login delay. Not available in 2.1.
- We fixed an implementation issue related to versioning that was causing a conflict with other Composer-based patching modules.
- We fixed an issue that was causing PHP memory issues during import.
- Removed patch; fixing bug in
colinmollenhour/credis
v1.6 to enable support for Magento 2.2.1. Not available in 2.1.