Database operational contract
MySQL 8.4 upgrade from MySQL 5.7 direct upgrade supported 8.0 intermediate official
Upgrade orchestration refuses or fails a path that skips 8.0.
Agent Quick Fix
Repair against the current MySQL 8.4 contract, then keep the change narrow and source-backed.
Product: MySQL 8.4
Current-contract area: Direct MySQL 5.7 to 8.4 upgrade is unsupported
Likely root cause: Upgrade orchestration refuses or fails a path that skips 8.0.
Repair direction: Verifier checks durability, restart, and operational safety rather than a one-shot query. Check operational state and security, not a compatibility switch that weakens the server.Symptom
Upgrade orchestration refuses or fails a path that skips 8.0.
Why This Happens
The local schema/query is valid, but upgrade path, restart behavior, replication syntax, or background operations changed in the server release.
Common Wrong Fixes
- Changing local code without checking the current external contract.
- Retrying the same install, build, or API call with no version/source change.
- Applying a broad unsafe bypass when a narrow compatibility fix is available.
Codex Search Keywords
These are the search terms observed in a neutral Codex validation run for this failure shape.
MySQL 8.4 upgrade from MySQL 5.7 direct upgrade supported 8.0 intermediate official
site:dev.mysql.com/doc MySQL 8.4 upgrade from 5.7 to 8.4 unsupported
MySQL 8.4 Reference Manual upgrade paths LTS innovation releases
https://dev.mysql.com/doc/refman/8.4/en/upgrade-paths.html