This commit is contained in:
Javier Casares 2026-11-04 14:37:18 +00:00
commit 7379505d20

View file

@ -1,10 +1,10 @@
=== 2FA (by ROBOTSTXT) ===
Contributors: robotstxt, javiercasares
Tags: security, two-factor authentication, login, otp
Requires at least: 5.6
Tested up to: 7.0
Requires PHP: 8.0
Stable tag: 1.6.8
Requires at least: 7.0
Tested up to: 7.2
Requires PHP: 8.3
Stable tag: 1.6.9
License: GPLv3 or later
License URI: https://www.gnu.org/licenses/gpl-3.0.html
@ -53,12 +53,37 @@ Yes. Activate the plugin at the network level. Network administrators can set an
== Compatibility ==
* WordPress: 5.6 – 7.0
* PHP: 8.0 – 8.5
* WordPress: 7.0 - 7.2
* PHP: 8.3 - 8.6
* MariaDB: 11.4 or newer
== Changelog ==
= 1.6.9 =
_Release date: 2026-11-03_
**Changed**
* Compatibility floors raised to WordPress 7.0 and PHP 8.3, verified with full-range compatibility scans (WordPress 4.7-7.2, PHP 5.6-8.6). WordPress 7.2 and PHP 8.6 are now tested and documented.
* The admin menu icon is now a brand SVG (shield with keyhole) instead of the Dashicons shield. Rendered through WordPress' native SVG menu-icon support, it stays crisp on high-density screens, works identically on WordPress 7.0/7.1/7.2, and is future-proof against the ongoing move from Dashicons to SVG icons in the WordPress admin.
**Fixed**
* PHP 8.6 deprecation removed: a REST-controller class constant named `namespace` (case-insensitive) triggered a deprecation notice on PHP 8.6 and would become a fatal error on PHP 9.
**Compatibility**
* WordPress: 7.0 - 7.2
* PHP: 8.3 - 8.6
**Tests**
* PHP Coding Standards: PHP_CodeSniffer 3.13.6 / WPCS 3.4.1 — 0 errors
* PHPStan: level max (10), no baseline — 0 errors
* PHPCompatibility: 8.3-8.6 — 0 issues
* PHPUnit: 9.6.38 — 110 tests, 220 assertions
= 1.6.8 =
_Release date: 2026-09-21_
@ -79,14 +104,6 @@ _Release date: 2026-09-17_
* The forced-setup wizard felt like a broken redirect loop: the wizard redirect bounced users to the profile with no explanation (it now carries a flag that renders a clear "activate at least one verification method, then save" warning), and saving with an expired form nonce silently did nothing (it now raises a visible "form session expired" error so users know to try again).
= 1.6.6 =
_Release date: 2026-09-17_
**Added**
* Forced-enrollment warning on the profile 2FA section: when a user's role enforces 2FA but they have no verification method configured yet, the 2FA section of their profile (wp-admin and the frontend shortcode) opens with a warning notice asking them to activate at least one method. While a grace period is active, the notice appends the remaining days.
= Previous versions =
For the full changelog see the [changelog](https://www.robotstxt.software/plugins/robotstxt-2fa/) page.