WP Sudo v4.0.0 — Research Snapshot

Versions before 4.9.0 automatically replayed an intercepted request after reauthentication (#322). Do not use this version.

RESEARCH PROTOTYPE ONLY. Do not install on production, public staging, or any site containing real users, credentials, or data. Use only in WordPress Playground or a disposable local test environment.

First WordPress.org-ready release. WP Sudo is action-gated reauthentication for WordPress: dangerous admin actions (plugin/theme/user/settings/network changes) require reauthentication before they proceed — regardless of role.

⚠️ Breaking changes

• Removed the deprecated sudo_can() function — switch any calls to wp_sudo_can().
• Removed the compatibility governance mode; governance is now always strict. The leftover wp_sudo_governance_mode option is removed automatically on upgrade (one-time dismissible notice, no manual cleanup).
• Minimum requirements raised: WordPress 6.4, PHP 8.2.
• WP_SUDO_RECOVERY_MODE remains the only break-glass lockout-recovery path.

Features

• Connectors registry-aware matcher — gates connector credential writes (including core's wordpress_api_key) to POST /wp/v2/settings, including on WordPress 7.0.
• WordPress.org readiness — listing name "Sudo – Admin Action Gating", SECURITY.md, submission checklist, and 9 listing screenshots.
• Manual release environment matrix plus Connectors-credential manual verification in tests/MANUAL-TESTING.md.

Reliability / CI

• Fixed a WordPress 7.0 upgrade-path fatal (prime wp_roles() before the capability query in the upgrader).
• Added the Plugin Check (PCP) CI lane; rebalanced the E2E test groups.

Upgrade notes

If you used compatibility mode, no action is needed — the option is removed automatically. Confirm your host meets WP 6.4 / PHP 8.2 before upgrading.

Requirements: WordPress 6.4+, PHP 8.2+