MySQL 8.0 End of LIfe

Documentation Feedback
1

Hi Temporal team,

With MySQL 8.0 having reached End of Life in April 2026 and major cloud providers (AWS RDS, Aurora, Azure, GCP) already pushing users toward MySQL 8.4 LTS, we’d like to understand where Temporal stands on supporting this version.

We are part of a team running Temporal in production in a regulated financial services environment. With MySQL 8.0 no longer receiving security patches from Oracle, staying on it is increasingly difficult to justify from a compliance and audit standpoint — especially as cloud providers are now charging extended support fees for 8.0 instances.

We are aware of the recent thread where a Temporal team member acknowledged that MySQL 8.4 (and 9.x) have not yet been formally tested, and that the server team has been notified. We appreciate the transparency, but given the urgency of the MySQL 8.0 EOL situation, we would like to ask a few follow-up questions:

  1. Is there a tracked issue or milestone on the roadmap for officially validating and supporting MySQL 8.4?
  2. Are there known blockers beyond schema compatibility testing — such as the mysql_native_password authentication plugin being disabled by default in 8.4?
  3. Is the team considering adding MySQL 8.4 to the CI test matrix as a near-term step?
  4. In the meantime, are there any recommended workarounds or configurations for teams that need to run Temporal against MySQL 8.4 today?

We understand the team has many priorities, but MySQL 8.4 LTS offers support through 2032 and is clearly the intended upgrade path for the ecosystem. Any guidance — even a rough timeline or a confirmation that this is actively being worked on — would be very helpful for our planning.

Thank you for the great work on Temporal. Looking forward to hearing from the team.

2

Can some one answer?

3

Its currently being looked at and tracked internally. Testing on Aurora 8.4 has shown some setup issues that are being addressed.
Will share more info when available.