Skip to content

Upgrade MySQL from 5.7 to 8.0 (step 1 of LTS migration)#68

Merged
nesono merged 5 commits intomainfrom
upgrade/mysql-5.7-to-8.0
Mar 28, 2026
Merged

Upgrade MySQL from 5.7 to 8.0 (step 1 of LTS migration)#68
nesono merged 5 commits intomainfrom
upgrade/mysql-5.7-to-8.0

Conversation

@nesono
Copy link
Copy Markdown
Owner

@nesono nesono commented Mar 28, 2026

Summary

  • Upgrades mysql_mail and mysql_wordpress_noerpel from MySQL 5.7 to 8.0
  • This is step 1 of a safe migration path to MySQL 8.4 LTS (5.7 → 8.0 → 8.4)
  • MySQL only supports upgrading one major version at a time; the Renovate PR upgrade nextcloud from 31 -> 32 #66 jumping directly to 9.6 would break data compatibility

Pre-deployment checklist

  • Back up mysql_mail_data volume
  • Back up mysql_wordpress_noerpel_data volume

Post-deployment verification

  • Both MySQL containers start without errors
  • Dovecot/Postfix/Postfixadmin connect to mysql_mail successfully
  • WordPress connects to mysql_wordpress_noerpel successfully
  • Mail login/sending works end-to-end

Next steps

  • Step 2: Upgrade MySQL 8.0 → 8.4 LTS (separate PR)
  • Step 3: Pin Renovate to only allow patch updates within 8.4.x

🤖 Generated with Claude Code

nesono and others added 5 commits March 28, 2026 14:07
First step toward MySQL 8.4 LTS. MySQL only supports upgrading one
major version at a time, so we go 5.7 → 8.0 → 8.4.

Important: back up mysql_mail_data and mysql_wordpress_noerpel_data
volumes before deploying. MySQL 8.0 will auto-upgrade 5.7 data on
first start.

Co-Authored-By: Claude Opus 4.6 <noreply@anthropic.com>
@nesono nesono force-pushed the upgrade/mysql-5.7-to-8.0 branch from dd36b26 to 6fd7b16 Compare March 28, 2026 13:08
@nesono nesono merged commit f512d1a into main Mar 28, 2026
1 check passed
@nesono nesono deleted the upgrade/mysql-5.7-to-8.0 branch March 28, 2026 13:49
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant