Skip to content
Database

MySQL Releases

Track every MySQL release from latest stable to end-of-life. Version timelines, Oracle vs community forks, upgrade paths, and migration guidance.

Total Versions

Supported

Latest

Version Timeline

All tracked releases with lifecycle status and EOL dates.

Loading version data…

Lifecycle Timeline

Visual overview of active support and maintenance windows.

5.7
8.0
8.4 LTS
9.0 Inn
9.1 Inn
2022 2023 2024 2025 2026 2027 2028 2029 2030 2031 2032
Active
Maint
Active
Maint
Active
Maint
Active
Maint
Active
Maint
Active / LTS
Maintenance
Today

Upgrade Paths

Migration guidance between major versions — breaking changes, effort estimates, and tips.

5.7 8.0 High Difficulty
Est. 1-2 days for production databases

Breaking Changes

  • Default auth plugin: caching_sha2_password (breaks older clients)
  • utf8mb4 is the default character set
  • Explicit GROUP BY required (ONLY_FULL_GROUP_BY default)
  • Query optimizer changes may alter execution plans
  • mysql_upgrade required (automatic since 8.0.16)
  • Removed query cache
  • JSON functions overhauled

Migration Notes

Run mysql-shell upgrade checker first (util.checkForServerUpgrade()). The auth plugin change breaks most PHP/Python/Node drivers unless updated. Test all queries — the optimizer changes can cause performance regressions on complex joins. Use mysql_native_password temporarily if clients cannot update.

8.0 8.4 LTS Medium Difficulty
Est. 4-8 hours

Breaking Changes

  • mysql_native_password plugin deprecated
  • Binary log transaction compression default
  • InnoDB redo log archiving changes
  • Several deprecated functions removed

Migration Notes

More incremental than 5.7→8.0. Ensure all clients support caching_sha2_password. Test with mysql-shell upgrade checker. This is the target LTS — once you are here, you have support until 2032.

Version Risk Assessment

Evaluate risk factors before choosing a version for production.

Version EOL Risk CVE Risk Ecosystem Cloud Support Overall Recommended Action
MySQL 5.7 Critical High EOL Dropping Critical EOL Oct 2023 — no patches, upgrade urgently
MySQL 8.0 High Low Maintenance Full High Extended support ends Apr 2026 — migrate to 8.4 LTS
MySQL 8.4 LTS None Low Active Full Low Recommended — supported until 2032
MySQL 9.x Inn High Low Innovation Partial High Innovation track — not for production

Risk combines EOL status, security patch availability, driver/ORM support, and cloud provider compatibility. Assessed as of March 2026.

MySQL Version Feature Comparison

Side-by-side feature differences across major versions.

Feature 5.7 8.0 8.4 LTS
JSON support Basic Full Enhanced
Window functions No Stable Stable
CTEs (WITH clause) No Stable Stable
Default auth plugin native_password sha2_password sha2_password
Default charset latin1 utf8mb4 utf8mb4
InnoDB Cluster Basic Stable Enhanced
Hash joins No Stable Stable
Invisible indexes No Stable Stable
Multi-valued indexes No Stable Stable
Binary log compression No Optional Default
Query cache Deprecated Removed Removed
Support ends Oct 2023 Apr 2026 Apr 2032

Embed Badges

Add live MySQL status badges to your README, docs, or dashboard.

Health Status

Overall support health

MySQL Health Status
![MySQL Health Status](https://img.releaserun.com/badge/health/mysql.svg)

EOL Countdown

Next end-of-life date

MySQL EOL Countdown
![MySQL EOL Countdown](https://img.releaserun.com/badge/eol/mysql.svg)

Latest Version

Current stable release

MySQL Latest Version
![MySQL Latest Version](https://img.releaserun.com/badge/v/mysql.svg)

CVE Status

Known vulnerabilities

MySQL CVE Status
![MySQL CVE Status](https://img.releaserun.com/badge/cve/mysql.svg)

Frequently Asked Questions

Common questions about MySQL releases and lifecycle.

How long are MySQL versions supported?
Oracle provides 5 years of Premier Support and 3 years of Extended Support for each major release, totaling 8 years. MySQL 8.0 Premier Support ended April 2026. MySQL 8.4 LTS will be supported until 2032.
Should I use MySQL 8.0, 8.4 LTS, or 9.x?
MySQL 8.4 LTS is the recommended choice for production. It is the first Long-Term Support release under the new versioning model. MySQL 9.x is the Innovation track for testing new features. MySQL 8.0 is approaching EOL.
What changed with MySQL versioning?
Starting 2024, MySQL uses two tracks: LTS releases (8.4, future 8.x) get bug and security fixes for 8+ years. Innovation releases (9.0, 9.1, etc.) ship new features every quarter but have short support windows. This mirrors Oracle database versioning.
MySQL vs MariaDB: which should I choose?
MySQL has better JSON support, the InnoDB Cluster for HA, and Oracle backing. MariaDB has Columnstore, Galera Cluster built in, and is fully open source (no Oracle CLA). They diverged significantly after MySQL 5.7. MariaDB is NOT a drop-in replacement for MySQL 8.0+.
MySQL vs PostgreSQL: which should I choose?
PostgreSQL has richer SQL compliance, better JSON/JSONB, advanced indexing (GIN, GiST), and extensions. MySQL is simpler to operate, has better replication tooling, and dominates in web hosting. For new projects, PostgreSQL is generally recommended unless you specifically need MySQL compatibility.
How hard is the MySQL 5.7 to 8.0 upgrade?
The 5.7 to 8.0 upgrade requires careful planning: the default authentication plugin changed (mysql_native_password to caching_sha2_password), utf8mb4 became default, GROUP BY behavior changed, and the query optimizer was overhauled. Run mysql_upgrade and test thoroughly. Budget 1-2 days for production databases.

Related Tools

Browse All Version History