You can use hotpatching to upgrade to a newer patch release, but not a feature release.

You can upgrade GitHub Enterprise Server to the latest patch release using a hotpatch.When upgrading using an upgrade package, schedule a maintenance window for GitHub Enterprise Server end users.For example, to upgrade to GitHub Enterprise 3.11, you must be on GitHub Enterprise 3.10 or 3.9. You must upgrade from a feature release that's at most two releases behind.For more information, see the GitHub Enterprise Server Backup Utilities README.md file. Ensure you have a recent, successful backup of your instance.For more information, see ' Upgrading GitHub Enterprise Server.' Take a snapshot before upgrading your virtual machine.When running multiple upgrades, wait at least 24 hours between feature upgrades to allow data migrations and upgrade tasks running in the background to fully complete.For more information, see ' Setting up a staging instance.' Use a staging instance to test the upgrade steps.Next to the release you are upgrading to, click Download, then click the Upgrading tab. Browse to the GitHub Enterprise Server Releases page. Use the latest patch release when upgrading.For example, you could upgrade from GitHub Enterprise 2.7 to 2.8 to 2.10, but upgrading from GitHub Enterprise 2.7 to 2.9 to 2.10 uses a later version in the second step.

Using the latest version possible on each upgrade allows you to take advantage of performance improvements and bug fixes.

If you’re several versions behind, upgrade your GitHub Enterprise Server instance as far forward as possible with each step of your upgrade process.

Use the Upgrade assistant to find the upgrade path from your current release version. For example, instead of upgrading from GitHub Enterprise 3.9 to 3.10 to 3.11, you could upgrade from GitHub Enterprise 3.9 to 3.11.

Include as few upgrades as possible in your upgrade process.

For more information, see the releases page.

The release notes for GitHub Enterprise Server provide a comprehensive list of new features for every version of GitHub Enterprise Server.

If you're using GitHub Enterprise Server Clustering, see ' Upgrading a cluster' in the GitHub Enterprise Server Clustering Guide for specific instructions unique to clustering.

If a package is not available, visit GitHub Enterprise Support and contact us for assistance. Verify the availability of the upgrade packages you will need to complete the upgrade.

Upgrade packages are available at for supported versions.

Free instals Process Monitor 3.9