Support for Drupal 7 is ending on 5 January 2025—it’s time to migrate to Drupal 10! Learn about the many benefits of Drupal 10 and find migration tools in our resource center.
Problem/Motivation
Right now we are actually calling the readiness checkers when \Drupal\automatic_updates\Updater::begin()
is called.
Proposed resolution
We should call the readiness checker and throw an exception if there are any errors.
Remaining tasks
Make a follow up issues for:
- Calling the checkers in
\Drupal\automatic_updates\Form\UpdaterForm::buildForm()
to not give the option to start an update if there are error and display warnings - Discuss switching from the current checker system to event subscriber system. This would allow checkers to run at different stages of the update. For instance checking that a staged update is correct and didn't update any modules that were not intended. see #3179266: Automatic Updates that require updates to contrib and custom extensions should be rejected and #3222608: Check for known security advisories on staged Automatic Updates
User interface changes
None
API changes
Data model changes
Issue fork 3222651-3224976
Show commands
Start within a Git clone of the project using the version control instructions.
Or, if you do not have SSH keys set up on git.drupalcode.org:
Comments
Comment #3
tedbowComment #4
phenaproximaComment #6
tedbowI created a follow up #3225099: Change Readiness checker services to event subscribers to allow checking at different stages