Skip to content

2002.0.14
Compare
Choose a tag to compare
@shiftedreality shiftedreality released this 25 Sep 15:26
· 228 commits to 2002.0 since this release
2002.0.14
5e9645e
This commit was created on GitHub.com and signed with GitHub’s verified signature. The key has expired.
GPG key ID: 4AEE18F83AFDEB23
Expired
Learn about vigilant mode.

Changelog (20 related PRs)

  • Verify Ideal State—The ideal-state wizard now verifies the current configuration during each deployment and provides clear instructions for updating the configuration to achieve a faster, zero-downtime deployment.
  • PCI Compliance—Updated the messaging protocols for Magento to require Transport Layer Security (TLS) version 1.2 when connecting with third-party messaging services. If you are using a message service that does not support TLS version 1.2, you must upgrade your service. Otherwise, the following error message displays when your Magento application tries to connect to the message server to send an email: Unable to connect via TLS.
  • Deployment improvement—Added validation to warn customers if a Staging or Production environment has dev, debug, or debug_logging options enabled to prevent performance issues caused by excessive logging activity.
  • Deployment fixes—
    • Now maintenance mode is enabled at the start of the deploy phase and disabled at the end. If the deployment fails, the site remains in maintenance mode until the deployment issues are resolved. Previously, the site returned to production mode even if the deployment failed.
    • Reworked the deploy phase validation checks to downgrade the error level for the following deployment issues from CRITICAL to WARNING so that the deployment completes. Previously, these issues caused the deployment to fail.
      • Environment configuration contains incorrect values for deploy or cloud variables.
      • The Elasticsearch version on the cloud infrastructure is incompatible with the version of the elasticsearch/elasticsearch module supported by Magento. See the Elasticsearch troubleshooting article in the Magento Support Knowledgebase.
    • Fixed an issue with the shared configuration settings in the app/etc/config.php file that caused recursion detected errors during deployment.
  • Cron-related fixes—
    • Fixed a cron scheduling issue that prevented jobs from running if you specify a cron frequency other than the default (1 minute).
    • Fixed an issue in the deploy phase that allowed cron jobs to continue running during deployment, which can cause database locks and other critical issues. Now, all cron jobs are stopped before the deploy phase begins and restarted after the deployment completes.
    • Fixed the cron job workflow in versions 2.2.x to unlock frozen cron jobs so that they can be stopped before beginning deployment. Previously, a frozen cron job caused the deployment to stall.
  • Changed the format of the config.php file generated by the vendor/bin/ece-tools config:dump command to use short array syntax and 4-space indentation to comply with Magento coding standards.
  • Fixed a deployment error that occurs when the .magento.env.yaml contains {{ base_url }} and {{ unsecure_base_url }} placeholders for web configurations instead of the default URL configuration for a Cloud project.
Assets 2
Loading