PHP moved from alpha to beta on August 13, 2026, with the release of PHP 8.6.0 Beta 1. The beta locks in the feature set for the next major version of the language that still runs the majority of the web, including most WordPress installs. It ships partial function application, a new clamp() helper, a Time\Duration class, a lower-level polling API for async frameworks, and a batch of deprecations aimed squarely at PHP 9. Beta 2 is due August 27, 2026, with general availability targeted for November 19, 2026, according to the official PHP release schedule.
What’s Actually New in PHP 8.6
A handful of the additions are the kind you will reach for immediately rather than admire from a distance. Partial function application lets you prefill some arguments of a function using a “?” placeholder and get back a closure, which pairs cleanly with the pipe operator for functional-style pipelines. The clamp() function bounds a value between a minimum and maximum in a single call, replacing the nested min(max()) pattern most PHP developers have typed a hundred times, and it works across numbers, strings, and DateTime objects.
Two additions are aimed more at framework authors than everyday app code. The new Time\Duration class represents a span of time and supports arithmetic on it directly, so something like sleep(Duration::fromMilliseconds(500)) reads as what it does. The polling API is a lower-level I/O multiplexing layer, an alternative to stream_select() that uses epoll or WSAPoll depending on the platform, built with async frameworks like ReactPHP and Amp in mind rather than typical WordPress or Laravel work.
The Deprecations Are the Part Worth Testing Now
PHP 8.6 also tightens a number of things in preparation for PHP 9, and this is the half of the release that can actually break something. Returning a value from inside a finally block is deprecated. Using reserved words like let, is, and namespace as regular identifiers is deprecated. Older type-checking functions such as is_double() and is_integer(), along with several SPL and MySQLi methods, are marked for removal. None of this changes behavior in 8.6 itself, but code that trips these deprecation notices today is code that will fail outright once PHP 9 arrives.
None of this is urgent for a production WordPress site. Hosts won’t default to 8.6 until well after the November GA, and WordPress core itself is conservative about minimum and target PHP versions. But if your team maintains a custom PHP application, an older plugin with legacy string-handling code, or anything that leans on the functions above, running your test suite against the beta now, even on a throwaway branch, is a cheap way to find out early rather than during a forced upgrade later. That kind of compatibility pass is exactly the sort of thing to fold into a web application development engagement rather than discover mid-migration, and it applies just as much to agencies running WordPress development work on custom plugins and themes as it does to standalone PHP apps.
