MySQL 9.7 — lifecycle date eolFrom is now 2034-04-30
For MySQL 9.7, product is mysql; field changed is eolFrom; previous value is 2034-04-21; new value is 2034-04-30; detected is 2026-09-28, recorded from its source on 2026-09-28; source re-checked 2026-10-26.
- Product
- mysql
- Product label
- MySQL
- Release cycle
- 9.7 verified
- Field changed
- eolFrom verified
- Previous value
- 2034-04-21 our reading
- New value
- 2034-04-30 verified
- Detected
- 2026-09-28 our reading
Values marked our reading are our classification of what the source says — the source does not print them in those words. The quote below is the evidence for each one; judge it yourself.
What the source says
{"name":"9.7","codename":null,"label":"9.7 (LTS)","releaseDate":"2026-04-21","isLts":true,"ltsFrom":null,"isEoas":false,"eoasFrom":"2031-04-30","isEol":false,"eolFrom":"2034-04-30"
— endoflife.date, retrieved 2026-09-28
Source
- endoflife.datehttps://endoflife.date/api/v1/products/mysql
This one changes, and we watch it.Software end-of-life date changes — which dates moved and what they were before is re-read on a schedule and every change is dated. Subscribe: Atom feed · JSON · what has changed so far.