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
Certain checks depended on the version you are updating to so we should clear readiness result. maybe also when caches are cleared.
Proposed resolution
Remaining tasks
User interface changes
API changes
Data model changes
Issue fork automatic_updates-3257845
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:
changes
Comments
Comment #4
phenaproximaComment #5
tedbowWe could test this functionality in build test also to get more complete test coverage.
Create a scenario where
1. ensure cron updates are enabled(I think this the default
2. The site would need to be more than 1 patch update behind
3. assert there is readiness check on an admin page that displays an error that the site is more than 1 patch release behind and will not be able to update via cron.
4. run the update
5 assert the message from 3) is not shown on the same admin page.
I think without the current change 5) would fail
Comment #6
tedbowComment #8
phenaproxima