MySQL 8.3 — lifecycle date eoasFrom is now 2024-04-30
For MySQL 8.3, product is mysql; field changed is eoasFrom; previous value is 2024-04-10; new value is 2024-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
- 8.3 verified
- Field changed
- eoasFrom verified
- Previous value
- 2024-04-10 our reading
- New value
- 2024-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":"8.3","codename":null,"label":"8.3","releaseDate":"2024-01-16","isLts":false,"ltsFrom":null,"isEoas":true,"eoasFrom":"2024-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.