The First Release Candidate of Automatic Updates 2.0 is Available
The first release candidate of Automatic Updates 2.0 was released on 30th June 2022. The Release candidate of Automatic Updates is a milestone to get this feature ready to be the part of Drupal 10 core. Automatic but safe update of the core and the contributed modules is the ultimate goal of this initiative.
Right now it’s a contributing module, but the plan is to move it to Drupal core. When this happens, all you will need to do is upgrade to the version of Drupal that includes the feature. It is meant to make the upgrade process a lot easier.
Here are some important changes in the recent release:
1. Make Everything Internal: Most of Automatic Updates' code has been marked internal, and many classes have been made final to prevent them from being extended. The logic in them has been carefully thought out and adding extension points prematurely could produce unintentional, potentially dangerous side effects. Internal code makes no guarantee of backwards compatibility.
2. Show Next Minor or Current Minor Updates in Update Form: If configured to do so, Automatic Updates will give you the ability to update Drupal core to the next minor release in the UI! Because updating to a different minor release is inherently more disruptive and prone to problems than updating within the currently installed minor release, this feature must be enabled by a hidden configuration switch.
3. Create a Validator to Check for Symlinks Anywhere in the Project: If there are symbolic links anywhere in the Drupal code base, Automatic Updates will refuse to do any work. Symbolic links are tricky to support and can cause major problems in certain situations. In the future there might be support for symbolic links or at least document some workarounds, but for now, symbolic links are not supported.
4. Drop Support for Drupal 9.2: Drupal 9.2 is end-of-life, and Automatic Updates has dropped support for it. The minimum supported version of Drupal core is 9.3.
5. Validation Messages: Previously, error messages generated by Automatic Updates were shown in a confusing way, where it wasn't obvious that they were coming from Automatic Updates. This is now fixed, and Automatic Updates errors are grouped under a helpful heading.
6. Allow Determining Required Packages in PreRequire and PostRequire Events: Package Manager's PreRequireEvent and PostRequireEvent classes now include helpful lists of the packages that are being required into the staging area.
7. New Request in Update Process: Previously, updating Drupal could put the PHP request into an inconsistent, unreliable state, because there is no way to reload changed code into the PHP runtime environment. This flaw has been mitigated by making the update process finish in a new request that starts from a clean, reliable state.
8. Reminder to Back up Database Before Update: Automatic Updates will now remind you to back up your database before starting an update in the UI.
For More Details and Source Visit:
Note: The vision of this web portal is to help promote news and stories around the Drupal community and promote and celebrate the people and organizations in the community. We strive to create and distribute our content based on these content policy. If you see any omission/variation on this please let us know in the comments below and we will try to address the issue as best we can.