Takeaway: On November 19, 2026, the PHP project released PHP 8.6.0, a major language update it describes as “Faster, Safer, More Powerful.” The headline features are partial function application, a new \Time\Duration class, the Io\Poll API, a clamp() function, a SortDirection enum, and default values for readonly properties. Official support, according to the supported versions table, is active until 31 December 2028 and security-only until 31 December 2030. The 8.6.0 NEWS file also includes the same-day November 19 security fixes. That does not mean every site must migrate to 8.6 in order to be patched.
Source downloads are linked from the 8.6.0 announcement and the project downloads pages. Before you move production traffic, read the official PHP 8.6 migration guide, including the pages for new features, backward-incompatible changes, and deprecated features. The notes below summarize selected official items. They are not a substitute for the manual.
Headline features in PHP 8.6
Partial function application
Partial application lets you supply some of a function’s arguments now and get back a Closure for the rest. Placeholders are ? and .... The original function runs only after the remaining arguments are passed into that Closure. The official announcement uses a compact array_filter() example, where a comparison can be written directly as a partially applied version_compare() call instead of wrapping it in an arrow function:
$versions = ['8.4', '8.5', '8.6', '8.7', '9.0'];
$supportsPfa = array_filter(
$versions,
version_compare(?, '8.6', '>='),
);
A new Duration class
The new \Time\Duration class represents elapsed time the way a stopwatch would: independent of a wall clock or timezone, with nanosecond precision and a documented range of more than 250 years. The release announcement presents it as a fit for timeouts and benchmark timings, with values that can be added, multiplied, and compared directly.
The Io\Poll API
Io\Poll is a new I/O multiplexing API. Officially, it uses the best available mechanism on each platform — epoll, kqueue, event ports, or WSAPoll — and is meant to avoid the scalability limits of stream_select(). PHP describes it as a common foundation that event-loop libraries such as ReactPHP and AMPHP can build on, not as a replacement for those libraries themselves.
clamp(), SortDirection, and readonly defaults
The new clamp() function, in the project’s wording, ensures that a given value — numeric or otherwise — falls within a specified range. A new SortDirection enum gives libraries a shared, type-safe way to express sort order.
Readonly properties may now declare default values. Per the manual, that default counts as initialization, and the property cannot be assigned again, not even from the constructor. That is a change in how fixed values can be written, not a loosening of readonly after the property has been initialized.
Support window and the same-day security fixes
PHP’s standard policy is two years of active support, then two years of security-only support. For the 8.6 branch, the supported versions table lists an initial release of 19 November 2026, active support until 31 December 2028, and security support until 31 December 2030.
8.6.0 also carries the November 19 security GHSA and CVE fixes recorded in its NEWS file. Operators who want those fixes without a major-version migration should use the matching point releases instead: 8.5.13, 8.4.28, 8.3.37, or 8.2.36, as described in our November 2026 PHP security update. A move to 8.6 is a language and runtime upgrade, and it should be tested against the migration guide first.
Official incompatibilities and deprecations worth testing
The incompatible-changes page is longer than this summary. A few official items are especially easy to trip over in existing code:
trim(),ltrim(), andrtrim()now strip the form-feed character (\f) by default.- The null-coalescing operator (
??) andempty()on a magic property no longer call__get()when__isset()has already written the property into the property table; the freshly written value is used instead. unpack()now treats a<or>immediately after a format code as an endianness modifier, not as the first character of the element name. A format such as"s<value"now produces the key"value".
The official 8.6 announcement also notes tighter session defaults: session.use_strict_mode and session.cookie_httponly are enabled, and session.cookie_samesite is set to Lax. If your application depended on the previous defaults, test cookie and session behavior before you cut over.
Among the deprecations, the manual now warns against a return inside a finally block, and against returning a value from __construct() or __destruct(). It also deprecates naming a function readonly. The official deprecation text says readonly is a reserved keyword, and that “a lexer exception was added in PHP 8.1 solely to keep an existing WordPress function of that name working.” This is a deprecation in 8.6, not a removal. This article does not attempt to say whether WordPress core has already renamed that function. Site owners who plan to move a WordPress stack to 8.6 should test their own code, plugins, and themes against the official migration notes rather than assume the outcome.
Other official deprecations include using let or is as identifiers reserved for possible future syntax, passing an object where an array is expected to functions such as array_walk(), and several older aliases and extension APIs. Check the deprecated-features page for the complete list.
Key facts
| Item | What official sources say |
|---|---|
| Release date | November 19, 2026, according to the PHP 8.6 announcement and the 8.6.0 release page. |
| Kind of release | A major update of the PHP language. |
| Headline features | Partial function application, \Time\Duration, Io\Poll, clamp(), SortDirection, and readonly property defaults. |
| Active support until | 31 December 2028. |
| Security support until | 31 December 2030. |
| Security fixes in 8.6.0 | The 8.6.0 NEWS file includes the November 19 GHSA/CVE fixes. Supported older branches received separate point releases the same day. |
| Migration documentation | The official PHP 8.6 migration guide, plus the new-features, incompatible-changes, and deprecated-features pages. |
| Notable official wording | Naming a function readonly is deprecated; the manual notes a PHP 8.1 lexer exception that existed to keep an existing WordPress function of that name working. |
FAQ
When was PHP 8.6.0 released?
November 19, 2026. That is the date on the official 8.6 announcement, the 8.6.0 release page, and the supported versions table.
What are the headline features in PHP 8.6?
The project highlights partial function application, a new \Time\Duration class, the Io\Poll API, a clamp() function, a SortDirection enum, and default values for readonly properties. The migration guide and new-features manual page cover these and other additions in more detail.
How long will PHP 8.6 be supported?
According to php.net’s supported versions table, the 8.6 branch has active support until 31 December 2028 and security support until 31 December 2030. That follows PHP’s usual two years of active support and two additional years of security-only support.
Does PHP 8.6.0 include the November 19 security fixes?
Yes. The 8.6.0 NEWS file lists the same-day GHSA and CVE fixes. Older supported branches were also patched in 8.5.13, 8.4.28, 8.3.37, and 8.2.36, so a major-version upgrade is not the only way to install those fixes.
What should I read before upgrading?
Start with the official PHP 8.6 migration guide, then the manual pages for new features, backward-incompatible changes, and deprecated features. Test your application, and any CMS or framework it uses, against those notes rather than relying on a summary.
What happened to naming a function readonly?
Declaring a function named readonly is deprecated in PHP 8.6. The official manual says a lexer exception was added in PHP 8.1 solely to keep an existing WordPress function of that name working. The change in 8.6 is a deprecation, not a removal. This article does not claim a current WordPress core status for that function; test before you migrate.
Do I have to move to 8.6 to stay patched?
No. If you are not ready to migrate, install the November 19 security release for your current supported branch. PHP 8.6.0 is the new major version and happens to include those fixes as well.
What are some official backward-incompatible changes?
Official examples include form-feed now being trimmed by default, a change in how ?? and empty() behave on magic properties after __isset() materializes them, and unpack() treating < and > after a format code as endianness modifiers. See the incompatible-changes page for the full list.

Leave a Reply
You must be logged in to post a comment.