Adjust multisite network cron Behat expectation for new WordPress privacy cleanup event

[Copilot]

WordPress 7.1 adds a scheduled wp_privacy_personal_data_cleanup_requests cron event, which increases events executed in the multisite --network --due-now Behat scenario. This caused the scenario to fail because the test’s exclusion list no longer matched current core behavior.

• Problem alignment

  • Updated the multisite network cron run scenario in features/cron-event.feature to exclude the new core privacy cleanup hook alongside existing excluded core hooks.

• Targeted test fixture change

  • Modified only the --exclude= list in the affected scenario (Run cron events with --network flag on multisite).
  • No runtime command implementation changes; this is a test expectation update to track WordPress core cron defaults.

• Patch excerpt

  When I run `wp cron event run --due-now --network --exclude=wp_privacy_delete_old_export_files,wp_privacy_personal_data_cleanup_requests,wp_version_check,wp_update_plugins,wp_update_themes,wp_site_health_scheduled_check,wp_update_user_counts,wp_scheduled_delete,wp_scheduled_auto_draft_delete`

[codecov]

Codecov Report

✅ All modified and coverable lines are covered by tests.

📢 Thoughts on this report? Let us know!

[Copilot]

Pull request overview

Updates the Behat acceptance test for multisite wp cron event run --due-now --network to stay aligned with WordPress core’s default scheduled events by excluding the newly-added privacy cleanup hook, preventing the scenario from counting an extra executed event.

Changes:

• Extend the multisite --network --due-now scenario’s --exclude= list to include wp_privacy_personal_data_cleanup_requests.

---

💡 Add Copilot custom instructions for smarter, more guided reviews. Learn how to get started.