Upgrading both the VM software and virtual hardware requires some downtime for your instance, so be sure to plan the upgrade in advance. You can schedule a maintenance window to notify your users.

Upgrading the GitHub Enterprise virtual machine

Upgrades are supported from the current and second most recent feature releases. For example, it's possible to upgrade from version 2.0.0 to either 2.1.0 or 2.2.5, but not from 2.0.0 to 2.3.0. If you're more than two feature versions behind, the upgrade will need to be performed in multiple passes.

What's new in this release?

Use this guide to learn about the new features, improvements, and changes in this GitHub Enterprise release.

Enabling automatic update checks

By enabling automatic update checks, your instance will determine if it's running the latest release of GitHub Enterprise. If it isn't, GitHub Enterprise will download the latest release for you. An administrator can then perform the upgrade.

Increasing storage capacity

You can increase or change the amount of storage available for Git repositories, databases, search indexes, and other persistent application data.

Increasing CPU or memory resources

To add CPU or memory resources to an existing GitHub Enterprise instance, shut down the instance and use the underlying virtual platform's tools to allocate the resources to the virtual machine. The newly allocated resources are automatically recognized on boot and no additional configuration is necessary.