Release v0.4.0

Added

• Passkey Logs shows named events, IP addresses, filters, and paginated results.
• A must-use watchdog restores the plugin after silent deactivation and keeps password restrictions in effect while the plugin cannot run.
• Upgrade tests check that v0.3.0 account data survives migration and that failed upgrades can retry.

Changed

• Passkey Logs replaces the old diagnostics log. Logging is enabled by default for new installations. Existing saved logging preferences are preserved.
• Clearing logs requires confirmation and records who cleared them and how many entries were removed, even when logging is disabled.

Fixed

• Deactivating the plugin on one WordPress network preserves watchdog protection for other networks. Uninstall removes watchdog state across all networks.
• Passkey operations handle database connection loss without replaying writes outside their transaction.
• Settings validation and sign-in checks enforce the current passkey policy before completing a change or creating a session.
• Unmatched passkey completions do not fill the logs. Unreadable log entries no longer break the page, and privacy erasure clears unreadable data.
• Deleting a network site removes its Passkey Logs entries.

Upgrade from v0.3.0

• Existing passkeys, account handles, settings, and password restrictions are preserved. Users do not need to register their passkeys again.
• The old diagnostic log table and its history are permanently deleted. Export or back up that history before upgrading if you need to retain it.
• The schema update runs automatically on the next request. A failed migration retries after five minutes.
• The watchdog installs in wp-content/mu-plugins. If that directory is not writable, an administrator notice reports that deactivation protection is off, and installation retries after an hour.

Latest

fix: direct translation bug reports to GitHub

Override the WordPress.org support URL generated by WP-CLI and use the project issue tracker in the translation template and French catalogs.

Co-Authored-by: Codex <codex@openai.com>

Release v0.3.0

Added

• New passkeys are named after the browser and device that created them, such as "Chrome on Mac". A second passkey from the same browser and device becomes "Chrome on Mac (2)". Unrecognised devices get "Passkey".

Changed

• The "passkey added" email names the authenticator, such as iCloud Keychain or a security key model, along with the passkey's name.
• In Passkey only mode, or when the account cannot sign in with a password, that email says to tell a site administrator instead of changing the password.
• Tested up to WordPress 7.1.