GitHub Enterprise 2.0.1 November 20, 2014 Series notes · Download

The 2.0 series release notes contain important changes in this release series.

Bug Fixes and Changes

DNS Servers

Major change: DNS settings are no longer configured via the the Management Console, and any custom nameservers specified via the console will be lost after upgrading to 2.0.1.

When configured to use DHCP, GitHub Enterprise now relies on the DNS nameservers provided by the DHCP server. This is the default configuration for GitHub on AWS, and no changes are required when upgrading an EC2 instance.

If you are using DHCP on VMWare and your server does not provide nameservers, or if you need custom nameservers that are different from your DHCP lease, please add them to /etc/resolvconf/resolv.conf.d/head after upgrading.

If you are using a static IP configuration, please reconfigure static network configuration after upgrading to 2.0.1, either via tty1 or sudo ghe-setup-network -v.

Note: You may also choose to add custom nameservers to /etc/resolvconf/resolv.conf.d/head before running ghe-upgrade. These settings will be retained across the upgrade to 2.0.1 and future releases.

Known Issues

The 2.0.1 release ships with some known issues that we were unable to fix before release. If any of these will cause major problems for your organization, we recommending waiting for 2.1.0 or 2.0.2 before upgrading.