-
v1.9.2 Stable
released this
2026-11-04 18:32:24 +00:00 | 0 commits to main since this release1.9.2
Release date: 2026-11-04
Changed
- Minimum requirements raised to the ecosystem support window: WordPress 7.0 (was 4.4) and PHP 8.3 (was 8.0). The code itself is unchanged and still runs on older versions (see Compatibility for the scan floors), but 7.0/8.3 are the only versions supported and tested from now on.
- The admin menu icon is now an inline SVG (base64
data:image/svg+xmlURI — the icon format WordPress documents foradd_menu_page()) instead of thedashicons-screenoptionsfont glyph. Follows the direction of WordPress 7.2, where core replaces the admin's dashicons with SVG icons (wordpress-develop PR #12270) and the frozen dashicons font is legacy. Same 2×2 "screen options" motif in the standard admin icon gray; uses only the long-documented menu-icon format (wp-compat clean at WordPress 7.0 — no new WordPress API is used). - Development tooling updated via
composer update: phpstan 2.2.14 → 2.3.5, php-stubs/wordpress-stubs 7.1.0 → 7.1.2, phpunit 9.6.36 → 9.6.38. PHPCStestVersionand the preflight scan range now cover PHP 8.3-8.6.
Fixed
- readme.txt: the Multisite FAQ incorrectly said "not compatible" — the plugin has been Multisite-compatible (network-activated, network admin menus, network-level storage) since 1.6.0.
- License URI in the plugin header aligned with readme.txt and the documentation template (
gpl-3.0.txt, was.html).
Compatibility
- WordPress: 7.0 - 7.2 (scan-verified 2026-11-04: wp-compat ladder clean from 4.4 through 7.0 — no WordPress API newer than 4.4 is in use; suite green against WordPress 7.2-beta4 trunk with the test library rebuilt 2026-11-03;
Tested up tofollows the dev install, which runs WordPress 7.2) - PHP: 8.3 - 8.6 (scan-verified 2026-11-04: PHPCompatibility ladder 5.6-8.6 — the code remains scan-clean from PHP 7.4 (runtime floor 8.0:
mixedhints,str_contains(),str_starts_with()), but the supported and declared floor is now 8.3 per the ecosystem window; verified running on PHP 8.3.36, and on 8.6.0RC3 ahead of its GA)
Tests
- PHPCS (WordPress-Core, WordPress-Docs, WordPress-Extra) + PHPCompatibility (8.3-8.6): pass
- PHPStan max (level 10) + wp-compat, without baseline: pass, 0 errors
- PHPUnit: 159 tests, 427 assertions on WordPress 7.2-beta4 / PHP 8.5 (also green on PHP 8.3 and 8.6RC3); line coverage 82.9%
- composer audit: no known CVEs
Downloads
-
v1.9.1 Stable
released this
2026-09-23 06:12:16 +00:00 | 1 commits to main since this release1.9.1
Release date: 2026-09-23
Changed
- Maintenance pass over the 1.9.0 security-patch feature:
composer update(no changes — dependencies already current, no known CVEs), full code + security review of the 1.9.0 diff (clean-context pre-deploy audit: escaping, capability gating, CSRF, and the 1.8.1 updater invariants all verified correct; its two suggestions were applied — see below), and floors re-verified. - Pre-deploy audit hardening:
security_patch_for()only accepts declarations that strictly increase the version — a store typo (self-mapping or downgrade) can no longer produce a downgrade/re-install "update" notice; theversionargument in premium/free package URLs is nowrawurlencoded, matching the installer. POT regenerated at 1.9.1.
Compatibility
- WordPress: 4.4 - 7.1 (scan-verified 2026-09-23: wp-compat ladder clean at 4.4 through 4.7; no WordPress API newer than 4.4 in use; the dev environment here runs WordPress 7.2-alpha trunk with the suite green, but 7.2 is not GA and
Tested up tostays at the AGENTS window top) - PHP: 8.0 - 8.5 (scan-verified 2026-09-23: PHPCompatibility ladder 5.6-8.5 — scan-clean from 7.4; manual audit keeps the real floor at 8.0:
mixedhints,str_contains(),str_starts_with())
Tests
- PHPCS (WordPress-Core, WordPress-Docs, WordPress-Extra): pass
- PHPStan max (level 10) + wp-compat: pass
- PHPUnit: 158 tests, 423 assertions (also green against WordPress 7.2-alpha trunk / test library rebuilt from wordpress-develop master)
1.9.0
Release date: 2026-09-22
Added
- Security-update notices (with Core 1.16.0+): when the store declares a security patch for the exact version this site runs (e.g. 1.2.3.1 applies to 1.2.3), Manager shows a red "Security update available: %name% (vX → vY) — Update now" notice on its catalog page and on the Plugins screen, and the catalog row status reads "Security update available (vX → vY)". The Update action installs the declared patch — never the feature mainline — so sites receive the security fix without being pushed across feature versions.
- The native update integration (update badge,
wp plugin update, auto-updates) also targets the declared patch: the injected update entry carries the patch version and a versioned, authenticated package URL. Patches declared for other versions never apply (exact match on the installed version). Chained patches work (1.2.3.1 → 1.2.3.2 once declared). - Spanish (es_ES) and Catalan (ca) translations for the new strings; POT regenerated.
Requires Core 1.16.0+ on the store for patch data and versioned downloads (older Core: the catalog simply carries no patches and Manager behaves as before).
Tests
- PHPCS (WordPress-Core, WordPress-Docs, WordPress-Extra): pass
- PHPStan max (level 10) + wp-compat: pass
- PHPUnit: 157 tests, 420 assertions
Compatibility
- WordPress: 4.4 - 7.1 (unchanged)
- PHP: 8.0 - 8.5 (unchanged)
Downloads
- Maintenance pass over the 1.9.0 security-patch feature:
-
v1.8.1 Stable
released this
2026-09-23 06:10:24 +00:00 | 2 commits to main since this release1.8.1
Release date: 2026-09-22
Fixed
- Pending updates now appear on sites where the WordPress.org update check never completes (api.wordpress.org unreachable, blocked, or firewalled hosts — common on a lot of servers).
Robotstxt_Manager_Updatermoved from the write-side hook (pre_set_site_transient_update_plugins, which only fires when a fullwp_update_plugins()cycle finishes) to the read-side filter (site_transient_update_plugins, which fires every time anything reads the update data: Plugins screen, Updates page, WP-CLI, auto-updates). Local versions are resolved fromget_plugins()instead of the transient'scheckedlist, which never exists in those environments. Diagnosed and verified end-to-end against the live store: update detection, listing (wp plugin list), dry-run, and the actual update run all work now even with api.wordpress.org blocked. - Stale Manager-owned update entries no longer mask newer versions: WordPress persists the filtered read during a (failed) update check, so a previously injected entry can sit in the stored transient forever. The updater now recognizes its own entries (package URL host matches the store) and replaces or removes them with fresh catalog data — killing stale-version masking, phantom "update available" badges after updating, and expired download tokens in one guard. Entries from other update servers (bundled SDKs pointing elsewhere, WordPress.org) are never touched.
- Premium download-token exchanges are now cached (5-minute site transient, failures negatively cached for 1 minute): without the cache, every read of the update data while a premium update is pending triggered a blocking HTTP call to the store — several per admin page load.
- Opt-in data deletion on uninstall now also removes the cached subscriptions site transient (
robotstxt_manager_subscriptions) — previously only the catalog transient was deleted, so subscription data could outlive the plugin when "Delete all plugin data" was enabled. - A hardcoded "Subscribed" fallback label in the multi-license catalog pill (unknown subscription status with more than one license) is now translatable like every other pill label.
Changed
-
PHPStan raised from level 9 to
max(level 10); the twomixed-strictness findings it surfaced were fixed with real narrowing (AUTH_KEY/AUTH_SALTstring checks in the encryption key derivation, theplugins_apislug check). -
Robotstxt_Manager_Core_Client::get_subscriptions()normalizes rows restored from the transient cache the same wayget_catalog()does (string keys enforced) — resolves the single level-9 error surfaced by PHPStan 2.2.14; no behavior change. -
Development tooling updated via
composer update: phpstan 2.2.8 → 2.2.14, phpstan-wordpress 2.0.3 → 2.0.4, wordpress-stubs 6.9.4 → 7.1.0, wp-hooks/wordpress-core 1.12.0 → 1.13.0, nikic/php-parser 5.8.0 → 5.9.0. -
Tests: dropped
ReflectionMethod::setAccessible()calls (no-op since PHP 8.1, deprecated on PHP 8.5) so the suite runs notice-free on the maximum supported PHP version. Regression tests cover the "WordPress.org check never completed" transient shape, thefalsetransient, stale own-entry replacement/removal, and download-token caching.
Compatibility
- WordPress: 4.4 - 7.1 (scan-verified 2026-09-22: wp-compat ladder clean from 4.4; verified across 4.4-7.1 with WordPress stubs 7.1.0 — no API newer than 4.4 in use, so 7.1 GA remains covered; 7.2 is not GA)
- PHP: 8.0 - 8.5 (scan-verified 2026-09-22: PHPCompatibility ladder 5.6-8.5 + manual audit —
str_contains(),str_starts_with(), andmixedtype hints keep the real floor at 8.0)
Tests
- PHPCS (WordPress-Core, WordPress-Docs, WordPress-Extra): pass
- PHPStan max (level 10) + wp-compat: pass
- PHPUnit: 152 tests, 401 assertions
- composer audit: no known CVEs
Downloads
- Pending updates now appear on sites where the WordPress.org update check never completes (api.wordpress.org unreachable, blocked, or firewalled hosts — common on a lot of servers).
-
v1.8.0 Stable
released this
2026-09-11 10:45:54 +00:00 | 3 commits to main since this release1.8.0
Release date: 2026-08-24
Added
- Multi-domain license awareness (with Core 1.14.0):
Robotstxt_Manager_Core_Client::get_subscriptions()groups the flat/me/subscriptionsrows per plugin slug — any-active status wins, the first bound domain is shown, and alicense_countis kept. Catalog subscription pills render the count when a plugin has more than one license (e.g. "Subscribed @ example.com ×2").
Tests
- PHPCS (WordPress-Core, WordPress-Docs, WordPress-Extra): pass
- PHPStan level 9 + wp-compat: pass
- PHPUnit: 149 tests, 391 assertions
Downloads
- Multi-domain license awareness (with Core 1.14.0):
-
v1.7.0 Stable
released this
2026-08-24 06:43:07 +00:00 | 4 commits to main since this release1.7.0
Release date: 2026-08-18
Added
- Per-domain license support (Core 1.11.0+): install/update downloads and the download-token exchange now send this site's normalized domain, so premium licenses bind to this site and the store rejects requests from other domains. Catalog subscription pills show the bound domain when the store reports one (e.g. "Subscribed @ example.com").
Changed
- Download failures now surface the store's own error message from the JSON body (e.g. the domain-mismatch explanation) instead of only "Download failed (HTTP 403)." — falls back to the bare code when no message is present.
Tests
- PHPCS (WordPress-Core, WordPress-Docs, WordPress-Extra): pass
- PHPStan level 9 + wp-compat: pass
- PHPUnit: 149 tests, 391 assertions
Downloads
-
v1.6.1 Stable
released this
2026-08-18 10:49:20 +00:00 | 5 commits to main since this release1.6.1
Release date: 2026-08-18
Fixed
- "Cannot modify header information — headers already sent" warning after saving the settings: the form handler ran inside the page renderer (after output started). It now runs on
admin_init, before any output, so the redirect succeeds.
Downloads
- "Cannot modify header information — headers already sent" warning after saving the settings: the form handler ran inside the page renderer (after output started). It now runs on
-
v1.6.0 Stable
released this
2026-08-18 10:48:35 +00:00 | 6 commits to main since this release1.6.0
Release date: 2026-08-18
Added
- WordPress Multisite compatibility:
Network: trueheader forces network-wide activation. Menus appear in the network admin on Multisite, in the regular admin on single-site. All options and transients use network-level storage (get_site_option/get_site_transient). Settings form handles submission manually (the Settings APIoptions.phpdoes not handle network options).
Fixed
- API key not saving when the browser auto-fills the password field with the stored encrypted value — the sanitizer now detects already-encrypted input (
v2:prefix) and returns it as-is instead of failing UUID validation. - "Test connection" validated against the public catalog endpoint (
/plugins), so invalid API keys reported "Connected". Now uses the authenticated/me/subscriptionsendpoint; a 401 response produces "Invalid API key". - "Test connection" read the key from saved options only — entering a new key and testing before saving always tested the old (or empty) key. The AJAX handler now accepts the key from the form field.
Added
settings_errors()call on the settings page so validation messages (e.g. "invalid API key format") are actually visible to the user.- Registration link (
https://www.robotstxt.software/wp-login.php?action=register) in the API key field description.
Tests
- PHPCS (WordPress-Core, WordPress-Docs, WordPress-Extra): pass
- PHPStan level 9 + wp-compat: pass
- PHPUnit: 146 tests, 385 assertions
Downloads
- WordPress Multisite compatibility:
-
v1.5.0 Stable
released this
2026-08-18 10:47:39 +00:00 | 7 commits to main since this release1.5.0
Release date: 2026-08-17
Changed
- Plugin identity now points at the ROBOTSTXT software site: Plugin URI and the new Update URI header are
https://www.robotstxt.software/plugins/robotstxt-manager/, Author URI ishttps://www.robotstxt.software/, and the readme.txt full-changelog link points to the same page. - Contributors list reordered: robotstxt first, then javiercasares.
- readme.txt changelog section trimmed to the 3 latest versions per the documentation template.
- Tooling aligned with the declared real floors: PHPCS
testVersionand the preflight scan range now cover PHP 8.0-8.5 (previously 7.4-8.5 / 8.4-8.5).
Compatibility
- WordPress: 4.4 - 7.1 (scan-verified: wp-compat ladder clean from 4.4; 10 errors at 4.0)
- PHP: 8.0 - 8.5 (scan-verified: PHPCompatibility ladder + manual audit —
mixedhints andstr_contains()are the 8.0 floor)
Tests
- PHPCS (WordPress-Core, WordPress-Docs, WordPress-Extra): pass
- PHPStan level 9 + wp-compat: pass
Downloads
- Plugin identity now points at the ROBOTSTXT software site: Plugin URI and the new Update URI header are
-
v1.4.1 Stable
released this
2026-08-17 18:10:08 +00:00 | 8 commits to main since this release1.4.1
Release date: 2026-08-17
Changed
- Plugin identity now points at the ROBOTSTXT software site: Plugin URI and the new Update URI header are
https://www.robotstxt.software/plugins/robotstxt-manager/, Author URI ishttps://www.robotstxt.software/, and the readme.txt full-changelog link points to the same page. - Contributors list reordered: robotstxt first, then javiercasares.
- readme.txt changelog section trimmed to the 3 latest versions per the documentation template.
- Tooling aligned with the declared real floors: PHPCS
testVersionand the preflight scan range now cover PHP 8.0-8.5 (previously 7.4-8.5 / 8.4-8.5).
Compatibility
- WordPress: 4.4 - 7.1 (scan-verified: wp-compat ladder clean from 4.4; 10 errors at 4.0)
- PHP: 8.0 - 8.5 (scan-verified: PHPCompatibility ladder + manual audit —
mixedhints andstr_contains()are the 8.0 floor)
Tests
- PHPCS (WordPress-Core, WordPress-Docs, WordPress-Extra): pass
- PHPStan level 9 + wp-compat: pass
Downloads
- Plugin identity now points at the ROBOTSTXT software site: Plugin URI and the new Update URI header are
-
v1.4.0 Stable
released this
2026-08-17 16:07:34 +00:00 | 9 commits to main since this release1.4.0
Release date: 2026-08-17
Changed
- Premium package URLs use short-lived download tokens (Core 1.9.0+
POST /me/download-token): the updater exchanges the account key each update cycle and embeds the 15-minute token instead of the API key, so the long-lived key no longer sits in theupdate_pluginstransient or server access logs. Falls back to the API-key flow automatically on older Core. (Closes the 0.5.1 audit finding.)
Compatibility
- WordPress: 4.4 - 7.1 (scan-verified: wp-compat clean from 4.4)
- PHP: 8.0 - 8.5 (scan-verified: PHPCompatibility + manual feature audit)
Downloads
- Premium package URLs use short-lived download tokens (Core 1.9.0+