The 2026 Drupal Business Survey is open. Your response will help shape the future of the Drupal business ecosystem.Problem/Motivation
As part of deprecating ReadinessCheckEvent, we need to first ensure that none of our validators are listening to it.
In the case of PackageManagerReadinessCheck, we may want to just remove it outright.
In all other cases, though, we should stop listening to ReadinessCheckEvent and ensure our tests keep passing with minimal changes.
Issue fork automatic_updates-3314764
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 #3
phenaproximaI'm happy with this. Assigning to @tedbow for review and commit.
Comment #4
tedbowLooking good. Had a view questions on the MR
Comment #5
phenaproximaComment #7
phenaproximaTransferring credit from #3304417: Deprecate ReadinessCheckEvent in favor of StatusCheckEvent in package manager, which is a duplicate.
Comment #8
tedbowThis is great to get done!
Comment #10
phenaproximaI agree, @tedbow. Merged into 8.x-2.x and published the change record!
Comment #12
tedbow