Quick answer: PHP 8.6 is scheduled for release on 19 November. It adds features such as partial function application, a clamp() function, a Time\Duration class and a new polling API, and it tightens PHP’s default session security settings for new installations. For most Australian businesses the practical advice is simple: if you are still on PHP 8.2 or older, upgrade to a supported version now (PHP 8.2 reaches end of life on 31 December), test your code against 8.6 on a staging copy, and plan the move to 8.6 for after the first patch releases rather than on release day.
A new PHP version arrives every November, and every year the same question follows: is it worth upgrading, and when? This year the question matters more than usual, because PHP 8.2 stops receiving security fixes at the end of December, which means many business websites and applications must move anyway.
This guide explains what is new in PHP 8.6 in plain English, what it means for your business, which version you should be running today, and how to prepare so the upgrade does not break anything. If you are still on an older version, read our guide to the PHP 8.2 end of life first.
PHP 8.6 release date
The PHP project releases a new minor version each year in late November. PHP 8.6 is scheduled for general availability on 19 November, following alpha, beta and release candidate stages through the year. The feature freeze has already passed, so the list of features is now locked, and the release candidates are being tested.
Release dates can move if a serious problem is found, so check the official PHP 8.6 release page on php.net before you plan around the exact day.
What is new in PHP 8.6?
The table below summarises the main changes reported for PHP 8.6 and why each one matters. This list is based on pre-release documentation and developer write-ups, so confirm details against the final release notes on php.net once 8.6 is out.
| Feature | What it does | Why it matters |
|---|---|---|
| Partial function application | Lets developers create a new function from an existing one by filling in some arguments and leaving a placeholder for the rest | Cleaner, shorter code in data-processing and callback-heavy parts of an application |
| clamp() function | Returns a value if it falls within set limits, or the nearest limit if it does not | Replaces repeated min and max logic, reducing small bugs |
| Default values for readonly properties | Allows readonly properties to have a default value | Easier to write safe, unchangeable data objects |
| Time\Duration class | A standard type for representing a span of time | A consistent way to handle timeouts and intervals in code |
| Polling API (Io\Poll) | A unified interface to the operating system’s I/O polling mechanisms | Mostly benefits low-level internals and server tooling, and does not add new async features by itself |
| SortDirection enum | A built-in way to describe ascending and descending order | Clearer, more consistent sorting code |
| Better reflection and error handling | New reflection helpers and improved structured error reporting for streams | Easier debugging and tooling |
| Tighter session defaults | New installations get safer session settings, including strict mode, HTTP-only cookies and a SameSite cookie default | Better security out of the box for sites that use sessions and logins |
What does this mean for a business?
Most of the headline features are conveniences for developers rather than visible changes for your customers. The practical benefits for a business are:
- Security. The safer default session settings reduce the risk of session hijacking and cross-site request attacks on new servers, although existing servers keep their current configuration.
- Cleaner, more maintainable code. Newer language features help developers write code that is shorter and easier to review, which lowers long-term maintenance costs.
- Staying current. Running a supported PHP version is the foundation of a secure, insurable and supportable application.
If you are waiting for a feature that will transform your site, PHP 8.6 is not that release. It is an incremental, steady improvement, and the main reason to care about it is staying supported and secure.
What was new in PHP 8.5?
PHP 8.5 was released last November and is the version most businesses should be targeting today. It introduced the pipe operator, which lets developers chain operations in a readable left-to-right style, and a new URI extension for parsing and building web addresses safely. Because it has been out for nearly a year, plugins, frameworks and hosting providers have had time to support it, which makes 8.5 a solid, low-risk target.
Which PHP version should your business be running?
Each PHP release gets two years of active support, followed by two years of security-only fixes. After that it receives nothing, and any newly found vulnerability stays open. Use this table to decide what to do:
| If you are on | What to do |
|---|---|
| PHP 7.x, 8.0 or 8.1 | Your version is already unsupported. Upgrade urgently, in stages if needed, and treat it as a security priority |
| PHP 8.2 | Support ends on 31 December. Move to PHP 8.4 or 8.5 now, before the deadline |
| PHP 8.3 | Still supported, but plan your move to 8.5 or 8.6 over the coming year |
| PHP 8.4 or 8.5 | Stay put, and test your site against 8.6 on a staging copy |
| A new project | Build on 8.5, and adopt 8.6 after its first patch releases |
Check the supported versions page on php.net for the exact support dates of each release. If your site is very old, our guide to legacy PHP migration explains why waiting makes the job harder and more expensive.
Should you upgrade to PHP 8.6 on release day?
In almost every case, no. New PHP versions are stable for developers, but the surrounding ecosystem takes time to catch up:
- Frameworks and CMS platforms such as Laravel, CodeIgniter, Symfony and WordPress need to confirm compatibility.
- Plugins and packages may use functions that are deprecated or changed.
- Hosting providers usually add a new PHP version some weeks or months after release.
- Early patch releases (8.6.1, 8.6.2 and so on) fix issues found by the first wave of users.
A sensible approach is to test against 8.6 during the release candidate period or soon after launch, fix any problems on a staging site, and move production once your framework, plugins and hosting all officially support it.
How to prepare your site or application for an upgrade
- Find out which PHP version you run today. Ask your host, or check the server information in your control panel or application.
- Take a full backup. Include both files and database, and store a copy off the server.
- Build a staging copy. Never test an upgrade on your live site.
- Audit your dependencies. List your framework, CMS, plugins and Composer packages, and check each one’s supported PHP versions.
- Run static analysis and automated upgrade tools. Tools such as PHPStan, Psalm and Rector can find deprecated code and fix many issues automatically.
- Read the deprecation notices. Turn on error logging on staging and note every deprecation warning, because deprecations today become errors in later versions.
- Upgrade to a supported version first. If you are on 8.2 or older, move to 8.4 or 8.5 before thinking about 8.6.
- Test thoroughly. Check forms, logins, payments, imports, scheduled tasks, emails and any third-party integrations.
- Schedule the live upgrade for a quiet period. Late evening or early morning AEST works for most Australian businesses, and avoid peak trading periods for online stores.
- Monitor after the change. Watch your error logs and uptime for the first few days, and keep your backup ready.
Upgrade checklist for your team
- Current PHP version identified
- Full backup taken and tested
- Staging site created
- Framework, CMS and plugins checked for compatibility
- Static analysis run and deprecations reviewed
- Composer packages updated
- Forms, logins, payments and integrations tested
- Scheduled tasks and background jobs tested
- Hosting confirmed to support the target version
- Rollback plan agreed
How long does a PHP upgrade take?
These are typical ranges. Real timing depends on the age of your code, the number of dependencies and how much testing your application needs.
| Project type | Typical timeframe |
|---|---|
| Small website or CMS site with up-to-date plugins | 1 to 3 days |
| Mid-size custom application on a recent PHP version | 1 to 3 weeks |
| Large or older application with many dependencies | 1 to 3 months |
| Very old legacy application (PHP 5.x or 7.x) | Often a staged migration project |
For cost, our PHP development pricing guide explains typical Australian rates, which commonly range from AU$80 to AU$200 per hour depending on the team and the scope.
| Problem | Likely cause | What to try |
|---|---|---|
| White screen or fatal error | Code or a plugin using a removed or changed function | Check the error log, then update or replace the plugin or fix the code |
| Deprecation warnings flooding the logs | Code written for older PHP versions | Fix each warning on staging, and use automated tools for bulk changes |
| Composer install fails | A package does not support the new version | Update the package, find an alternative or pin to a compatible release |
| Sessions or logins behave differently | Changes in session settings | Review your session configuration and test login flows |
| Site is slower or uses more memory | Settings not carried across to the new version | Recheck OPcache, memory limits and extensions on the new PHP version |
| A needed extension is missing | The new PHP install lacks an extension your site uses | Install the extension for the new version on the server |
Why upgrading PHP matters for security and compliance
Running an unsupported PHP version means newly discovered vulnerabilities are never patched. For a business that stores customer details, takes payments or handles personal information, that is a real exposure. The Australian Privacy Act expects you to take reasonable steps to protect personal information, and running outdated software is hard to defend if a breach occurs. Cyber insurers and enterprise customers also increasingly ask which software versions you run.
Keeping your application on a supported PHP version is one of the cheapest and most effective security measures available. It also keeps your options open: modern frameworks, hosting plans and developers all assume a current version.
Frequently asked questions
When is PHP 8.6 released?
PHP 8.6 is scheduled for general availability on 19 November. Release dates can move, so check php.net.
What is new in PHP 8.6?
Reported features include partial function application, a clamp() function, default values for readonly properties, a Time\Duration class, a polling API, a SortDirection enum and tighter default session settings.
Is PHP 8.6 a major release?
No. It is a minor release in the PHP 8 series, following PHP 8.5, so it adds features without breaking most existing code.
Should I upgrade to PHP 8.6 straight away?
Not usually. Test it on staging, wait for your framework, plugins and host to confirm support, and move after the first patch releases.
What if I am still on PHP 8.2?
Support ends on 31 December. Upgrade to PHP 8.4 or 8.5 now rather than waiting for 8.6.
Will PHP 8.6 break my website?
Most well-maintained sites will run fine, but older code, unmaintained plugins and deprecated functions can cause errors. Testing on staging finds these before your customers do.
How much does a PHP upgrade cost?
It depends on the size and age of your application. Simple sites can be quick, while large legacy applications need a staged project. A developer can give you a fixed estimate after reviewing the code.
Can I upgrade PHP myself?
Small, well-maintained sites sometimes can. Custom applications, online stores and older codebases are safer in the hands of an experienced PHP team.
Need help upgrading PHP?
PHP Professionals audits, upgrades and maintains PHP websites and applications for Australian businesses, including staging, testing and a safe go-live. Explore our PHP migration and upgrade services, our website development and maintenance service and our custom PHP application development. You can also read how to choose the right PHP development partner. When you are ready, contact us or call 1300 72 50 90 for a free PHP upgrade assessment.