-
v1.5.3 Stable
released this
2026-11-03 16:46:37 +00:00 | 0 commits to main since this release1.5.3
Release date: 2026-11-03
Highlights
- Support window realigned: WordPress 7.0-7.2 (7.2 beta tested) and PHP 8.3-8.6 (8.6 RC tested) —
Requires at leastraised 5.3 → 7.0 andRequires PHPraised 8.1 → 8.3 per the support policy - Includes the never-released 1.5.2 changeset (vendor PHP-floor integrity fix, WP 7.2 / PHP 8.6 verification)
Changed
- WordPress minimum raised 5.3 → 7.0 and PHP minimum raised 8.1 → 8.3 (support policy: WordPress 7.0-7.2, PHP 8.3-8.6). The code's real floors remain lower — WordPress 5.3 (wp-compat: the single pre-7.0 binding symbol is the
big_image_size_thresholdfilter, WP 5.3; 7.0 and 7.2 scan clean) and PHP 8.1 (aws/aws-sdk-php) — so the raise is a support-window decision, not a technical necessity composer.jsonplatform pin raised 8.1 → 8.3 together with the declared floor; dependency resolution stays locked to the supported minimum- Composer dependencies updated (net, from the last released 1.5.1):
aws/aws-sdk-php3.395.5 → 3.402.5 (3.402+ requires PHP >= 8.2, now allowed under the 8.3 floor — resolves KI-009),symfony/filesystemv8.1.6 → v7.4.21,guzzlehttp/guzzle8.2.0 → 8.3.1,guzzlehttp/psr73.1.0 → 3.2.0,guzzlehttp/promises3.0.2 → 3.1.0 (removes theUsing "is" as a class name is deprecated since 8.6deprecation raised on PHP 8.6), symfony polyfills updated (ctype stays at v1.37) (no known CVEs —composer auditclean for production and dev) - Dev tooling updated: PHPStan 2.2.14 → 2.3.5,
johnbillion/wp-compat2.0.1 → 3.0.1,php-stubs/wordpress-stubs7.1.0 → 7.1.2, PHPUnit 9.6.36 → 9.6.38
Fixed
- Declared PHP floor integrity: since 1.4.4 the locked
symfony/filesystemv8.1.x required PHP >= 8.4.1, so the installed vendor tree silently demanded PHP 8.4+ despite the declared minimum. Theplatform.phppin introduced with the 1.5.2 changeset guarantees dependency resolution can never exceed the declared floor (now 8.3)
Compatibility
- WordPress: 7.0 - 7.2 — floor verified with wp-compat 3.0.1 (
requiresAtLeast4.7 / 5.2 / 5.3 / 7.0 / 7.2): 7.0 and 7.2 are clean; runtime-verified on the WordPress 7.2-beta staging site — the onlydebug.logentries are core admin-bar icon notices introduced by WordPress 7.2 itself (core replacing its own dashicons with SVG viawp_get_icon(), wordpress-develop PR #12270) - PHP: 8.3 - 8.6 — declared-range PHPCompatibility scan 8.3-8.6 clean; runtime matrix green: full PHPUnit suite passes on PHP 8.3, 8.4, 8.5 and 8.6.0RC3, with no deprecations on 8.6; the full-range scan 5.6-8.6 documents the code's own (lower) syntax floor — the declared 8.3 is the supported policy window
- Icon assessment (wordpress-develop PR #12270): no action needed — the plugin registers no icons of its own (the Settings submenu inherits core's menu icon; no admin-bar nodes; no dashicon references in code or assets), so core's switch to SVG admin icons requires no adaptation
Security
composer audit(production and dev dependencies): no known CVEs- Full
AGENTS-security.mdchecklist re-verified against the codebase — no new findings; no runtime code changes in this release
Tests
- PHP Coding Standards: 3.13.6 (0 errors)
- WordPress Coding Standards: 3.4.1 (0 violations)
- PHPStan: 2.3.5, level 9, 0 errors
- PHPUnit: 96 tests, 211 assertions (green on PHP 8.3, 8.4, 8.5, 8.6.0RC3)
- composer audit: no known CVEs
Downloads
- Support window realigned: WordPress 7.0-7.2 (7.2 beta tested) and PHP 8.3-8.6 (8.6 RC tested) —