What is the recommended approach for upgrading GitHub Enterprise Server from version 3.x to the next major version?
Select an answer to reveal the explanation.
Short Explanation and Infographic
GHES upgrades aren't always direct. GitHub publishes an upgrade matrix showing which version hops are supported. You might need to hit a specific intermediate release before jumping to the latest. Always check before you patch.
Full explanation below image
Full Explanation
GitHub Enterprise Server upgrades must follow supported upgrade paths defined in GitHub's upgrade matrix documentation. GitHub does not support arbitrary version jumps — certain intermediate versions may be required. For example, upgrading from 3.0 to 3.8 might require upgrading to 3.4 first. The upgrade process: (1) Check the supported upgrade path for your current and target version. (2) Download upgrade packages for each required intermediate version. (3) Create a pre-upgrade backup. (4) Apply each upgrade in sequence via the Management Console. (5) Verify each upgrade completes before proceeding. Skipping versions can result in failed migrations, data corruption, or unsupported states. GitHub publishes detailed release notes and upgrade guides for each version.