Treat a major version as a planned change

PHP 8.6.0 is a general availability release. A new major version can change language behaviour and extension support. Do not upgrade a live application only because the new version is available.

List every application that uses the runtime. Record the framework, packages, PHP extensions, scheduled jobs and command-line tools that depend on it. Check the project migration notes and vendor support first.

Test the same work your users perform

Build a staging environment with the same PHP extensions and configuration as production. Run automated checks, then test sign-in, forms, payments, file uploads, email and background jobs.

Review logs for deprecation notices and runtime errors. Confirm that monitoring and backups work. Ask the hosting provider when its supported PHP packages will be available.

Roll out with a rollback path

Back up the application and database. Deploy to a small or low-risk environment first. Monitor errors and response times after the change. Keep the previous supported runtime available until the application passes its checks.

Do not use a release candidate or preview build for production. If the site depends on an unsupported extension, resolve that dependency before the old runtime reaches end of support.