MySQL 8.0 Reaches End of Life in April 2026: Time to Plan Your Upgrade
Oracle's MySQL 8.0 will reach end of life on April 30, 2026, ending security updates and vendor support for one of the world's most widely deployed database releases.
Oracle has scheduled MySQL 8.0 for end of life on April 30, 2026. After that date, MySQL 8.0 will no longer receive security patches, critical bug fixes, or vendor support. For organizations running 8.0 in production — which, given the release's long tenure, is still a substantial portion of MySQL deployments globally — the deadline requires immediate planning attention.
What End of Life Means in Practice
After April 30, unpatched MySQL 8.0 vulnerabilities will not be fixed by Oracle. For regulated industries operating under PCI DSS, HIPAA, or similar frameworks, running an EOL database can trigger compliance failures during audits. Oracle's HeatWave MySQL managed service has already ended support for MySQL 8.0-based instances, making cloud-hosted 8.0 deployments an additional migration priority beyond on-premises installations.
Recommended Upgrade Paths
MySQL introduced a Long-Term Support (LTS) versioning scheme in recent releases. MySQL 8.4 is the current LTS release, with support extended through 2032. MySQL 9 is an innovation release receiving shorter-term support. For most organizations prioritizing stability, the recommended path is from 8.0 to 8.4 LTS rather than to MySQL 9.
The 8.0 to 8.4 upgrade is considerably less disruptive than the 5.7 to 8.0 migration that many teams spent months managing. However, some deprecated functions and syntax changes do require attention, particularly around authentication plugin configurations and SQL mode settings. Percona Server for MySQL 8.4 and MariaDB are alternatives for teams evaluating options, though the divergence between MariaDB and upstream MySQL has grown enough that migration requires thorough testing.
Action Plan
Organizations should inventory all MySQL 8.0 instances now, stand up a MySQL 8.4 LTS staging environment for compatibility testing, and target completion of the upgrade well before April 30 to allow time for unexpected issues. The Oracle EOL notice is available at mysql.com/support/eol-notice.html.
Related Articles
Redis 8.4 Brings Hybrid Search, Atomic Multi-Key Operations, and Auto-Repair AOF
Redis 8.4 is now generally available, delivering hybrid search that combines full-text and vector queries using Reciprocal Rank Fusion, new atomic string commands like MSETEX and DELEX, and automatic repair for corrupted append-only files. Lookahead prefetching and JSON memory optimizations round out a performance-focused release.
Deno 2.7 Stabilizes Temporal API and Ships Native Windows ARM Builds
Deno 2.7 has stabilized the TC39 Temporal API, bringing immutable, timezone-aware date and time objects to replace the legacy JavaScript Date API. The release also delivers official Windows ARM builds for Surface and Snapdragon devices, npm overrides support, and global install compilation for standalone executables.
Laravel 13 Ships with PHP Attributes, Passkeys, and Zero Breaking Changes
Taylor Otwell unveiled Laravel 13 at Laracon EU, delivering PHP 8 Attributes as an alternative to class properties, built-in passkey authentication in starter kits, and a new Reverb database driver for horizontal WebSocket scaling. The release requires PHP 8.3+ and promises the smoothest upgrade path in Laravel history.