Changelog · Airworthy

Version 1.1.3

Improved: the "Did Airworthy help?" request now appears at a good moment. When there's nothing left to fix, or a rescan has just cleared a Blocker, it sits near the top of the results and names the plugin you fixed. Otherwise it stays below the results. It is still asked once, and "Maybe later" asks again in 30 days.

Upgrade notice: The review request now shows at a better moment, when your results are good or a rescan has fixed something.

Version 1.1.2

Improved: the screen's title and tabs are now one panel, with an icon on each tab and a blue line under the open one, so the tabs are easy to spot. Notices from other plugins now appear above Airworthy's header instead of between the title and the tabs. On a phone the tabs scroll sideways and the open tab is brought into view.
Readme: new answers on whether you need an account or licence to see results (you don't), and on why a site on PHP 7.2 or 7.3 can't update to WordPress 7.0.

Upgrade notice: A clearer header and tab bar on the Airworthy screen.

Version 1.1.1

Fix: the PHP security-fixes check no longer calls a patched server unpatched. CloudLinux, cPanel, Plesk, Debian, Ubuntu and Red Hat ship PHP security fixes as an update that keeps the old version number, so a version below php.net's fixed release doesn't mean the fixes are missing. Airworthy now reads when your PHP was built: built on or after the release day, it very likely has the fixes (shown as good, with a note to confirm with your host); built before, on one of those hosts, Airworthy asks you to get your host to apply the PHP update; built before anywhere else, it's still flagged as missing them. When the build date can't be read, Airworthy says it can't tell from the version alone instead of raising an alarm. Nothing is sent anywhere: the build date and vendor are read on your server.

Upgrade notice: Fixes a false "missing security fixes" alarm on hosts that ship PHP fixes without changing the version number (CloudLinux, cPanel, Plesk, Debian, Ubuntu, Red Hat).

Version 1.1.0

New: PHP 8.6. Check against PHP 8.6, due on 19 November 2026 (a release candidate until then, so it's never the default). PHPCompatibility doesn't cover PHP 8.6 yet, so Airworthy brings its own checks for its deprecations, such as spl_object_hash(), is_long(), return in finally and constructors that return a value. PHP 8.6 removes nothing, so these are Warnings: the code works on 8.6 but should be updated before a later version.
New: What to do first. Under the overall answer, up to three next steps for your site, most important first: replace closed plugins, install updates that fix problems, ask a plugin's developers for a fix, send findings for custom code to its developer, check files that couldn't be read. Each links to the plugin's details.
New: plain-English explanations. Each finding's details say what changed in PHP, what happens on the new version and how to fix it, with a before-and-after code example for the common cases. The CSV export has a new Explanation column.
New: verdicts on the Plugins screen. After a scan, each plugin's row shows its verdict for the PHP version you checked, linking to its details. It says when a plugin hasn't been checked since it was updated or installed, and it disappears once your server runs that PHP version.

Upgrade notice: Adds PHP 8.6, a What to do first list, plain-English explanations with fixes, and verdicts on the Plugins screen.

Version 1.0.3

New: a PHP security-fixes check on the start screen, in the results and in Tools > Site Health. Airworthy knows the PHP security release of 21 October 2026 (PHP 8.5.12, 8.4.27, 8.3.36 and 8.2.35, fixing two critical vulnerabilities, CVE-2026-109618 and CVE-2026-109619). If your server's PHP is older than those, it tells you to ask your host to update: an update within the same version is routine and doesn't change how your plugins work. PHP 8.1 and older got no release from the PHP project, so for those it says to ask your host whether they patched it and to move to a newer version. The data is bundled with the plugin; nothing is fetched.
PHP support dates checked against php.net on 21 October 2026: no change.

Upgrade notice: Tells you when your server's PHP is missing the critical PHP security fixes of 21 October 2026.

Version 1.0.2

Fix: code that fails on every PHP version, such as $this inside a static closure (found in the latest version of a widely used plugin), is now listed as a problem that already applies on your current PHP, not as a Blocker for the upgrade. It isn't caused by changing PHP, so it shouldn't hold the upgrade back.

Upgrade notice: Code that fails on every PHP version is no longer counted as a Blocker for the upgrade.

Version 1.0.1

New: Copy summary, next to Export CSV on the results. Copies a plain-text summary (the overall answer, then each plugin and theme grouped by what to do next, with updates waiting and closed plugins) to paste into an email or support ticket for your host or developer.
New: after a finished scan, the results ask once whether you'd leave a review on WordPress.org. Maybe later asks again in 30 days; Don't ask again means never. It only appears on Airworthy's own screen, below the results.
PHP support dates checked against php.net on 16 October 2026: PHP 8.2 gets security fixes until 31 December 2026.
WP-CLI: the note about problems that already apply on your current PHP version now says how to list them (wp airworthy results --fields=name,verdict,existing); it pointed to a column the scan table doesn't show.

Upgrade notice: Adds Copy summary on the results, for sending to your host or developer.

Version 1.0.0

First release.
Checks every plugin and theme against PHP 8.0 to 8.5, with a clear verdict for each: Blocker, Unknown, Suppressed by author, Guarded legacy code, Warnings or Ready.
Tells real problems from old code that never runs on the new PHP version, including code that falls back to a replacement PHP extension.
Marks problems that already apply on the PHP version your site runs now, so they aren't counted as new with this upgrade.
Optional WordPress.org check (you choose): plugins removed from WordPress.org, not updated in two years, or needing a newer PHP version.
Results grouped by what to do next: fix before you upgrade, keep an eye on, all good.
Shows which plugins and themes have an update waiting, with a one-click update; Airworthy checks them again after they're updated, including when a plugin is replaced by uploading a zip.
Shows how long your server's PHP version keeps getting security fixes.
Runs in the background with live progress, so a large site never times out. A stopped scan can be continued where it left off.
Settings: skip inactive plugins, never scan chosen plugins or themes, and choose how hard scans work your server.
A PHP upgrade readiness check in Tools > Site Health.
CSV export and WP-CLI commands.

Upgrade notice: First release.

What's new