Repository navigation
Bash WP-CLI Update v9.0.0
Two changes in one release: the selective update path is repaired, and the minimum
bash version is now 5.1. The floor is why this is a major version — a documented
runtime requirement went up, so a host that only has bash 4.x must either upgrade
bash or stay on 8.1.1, which does contain the selection bug.
Changed
- The floor is bash 5.1. Bash 4.2 (2011) ships only on CentOS 7, which reached
end of life in June 2024, and on distributions that stopped receiving updates
years ago; every distribution still supported in 2026 ships 5.1 or newer (Ubuntu
22.04+, Debian 11+, RHEL/Rocky/Alma 9+; Alpine 3.14+). The manager, the finder
andinstall.shrefuse anything older with exit 3 and the version they found.
Hosts on RHEL/Rocky/Alma 8 (bash 4.4) can no longer run 9.0.0; 8.1.1 remains the
last release they can use. - CI takes the floor from a distribution image (
ubuntu-22.04, bash 5.1) instead
of compiling bash 4.2 from source, which stopped working whenubuntu-latest
moved to a compiler that defaults to C23 in November 2026. A published bash is
also a better floor test than a hand-built one. -j Nis still a batch barrier, not a continuous pool.wait -nwould allow a
pool now, but the barrier keeps every site's output contiguous and costs at most
one slow site per batch, so the shape stays.
Fixed
- The manager asked WP-CLI for a
slugfield that does not exist.wp plugin listandwp theme listhave noslug:nameis the slug, and the display
name is the optionaltitlefield.--fields=name,slug,status,updatewas a hard
error (Invalid field: slug., exit 1), so the enumeration failed before a single
plugin was considered. All three call sites (plugin_select_targets,
theme_select_targets,plugin_resolve_slug) now ask forname,status[,update]
plustitle, and take the slug fromname. - mu-plugins and dropins were added to the
plugin updatecommand. They appear
inplugin listbut are not installable packages, sowp plugin update disable-cf7-updates zbs-supportanswers “could not be found” and fails a site
that is perfectly healthy. Entries with statusmust-useordropinare skipped
and the reason is logged at debug level. - The dropin filter could be defeated by an empty column.
json_to_tsvemits an
empty cell for an absent value, andreadwithIFS=$'\t'collapses an empty
field, which shiftedstatusintotitlefor every dropin (they have no display
name) and let it through. The optional column is now requested last, so an empty
value can only land in the last variable. --debugcrashed the pending-update check.pending_countand
site_core_versionreturn their answer on stdout; under--debugthe console
echo of their ownwpcall was captured by the caller's$( )and the arithmetic
died with “DBG: unbound variable”. Reachable on any host that follows the
documented production profile (SKIP_IF_NO_UPDATES=1) and turns debugging on.
Changed
- Exclusion, holding and
--namematching run against the slug and the display
name, both from the same singlewp <kind> listcall (title), which is what the
documentation has promised since 6.0. Comparison is case-insensitive and
whitespace-insensitive, so--exclude-plugins 'All in One SEO'works even though
the list parser strips spaces from the entries. - On a WP-CLI that predates the
titlefield the call is retried once without it
and matching falls back to the slug; the capability is probed once per run, not
per site.