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

Bug Fixes and Changes

• Ubuntu packages have been updated to the latest bugfix/security versions.
• Data migration failed if there were organizations without administrators.
• Services could fail to start correctly if configuration was applied without storage being prepared.
• A race condition could cause a configuration failure to be incorrectly reported.
• When saving Management Console settings, redirecting to the progress page could fail.
• Saving Management Console settings with an inaccessible LDAP server caused an error.
• Static network settings would be lost across upgrades.
• Gist Git repositories could not be pushed to directly.
• The number of Rails worker processes was static, and now depends on the provisioned memory.
• GitHub OAuth did not redirect to the requested page when login was required.
• Diagnostic output did not include the EC2 instance type.
• MySQL replication was shown as a running query in the Management Console maintenance page.
• A SAML single logout URL was incorrectly published. GitHub Enterprise does not currently support single logout.
• Excessive log entries were generated because the MySQL slow transaction threshold was set too low.
• The default memory for the OVA was incorrectly set to 8GB, instead of the recommended 16GB.
• Lowercase hostnames were not enforced in the Management Console settings.
• collectd and log data are were not preserved through upgrades.
• Support bundles did not include configuration logs.
• SAML times did not append Z for compliance with the SAML Core 1.3.3 standard.
• Incorrect license information was shown in diagnostic output.
• The Git HTTPS daemon contained a file descriptor leak.
• Added ghe-mysql-checksum script to checksum InnoDB tables.
• Management Console restore messaging was imprecise.
• Subdomain isolation caused a redirect loop when accessing the Pages root URL.
• The crash kernel was unnecessarily enabled, causing 128M of memory to be used.
• Webhook logs did not include timestamps.
• Excessive log entries were generated if Gitmon could not open its data store.
• Non-DST time changes caused ambiguous Russian timezones.

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.

• News feed activity links point to the hostname and protocol used when they were generated (affects renamed hosts).
• "Test domain settings" will fail when a DNS server is invalid or not reachable.
• ghe-restore should require that maintenance mode is enabled before restoring.
• ghe-repl-status-git is CPU intensive and may be slow on the primary node.
• The Site Admin dashboard has an autofocus issue in Firefox.
• Accessing the Gist raw subdomain can cause an error.
• Git replication is slow and CPU intense during initial push of large or complex repositories.
• Webhook deliveries may be delayed when search indexing jobs are running.
• The lock issue dialog does not link to the versioned Enterprise Help URL: https://help.github.com/enterprise/2.0/user/articles/what-are-the-different-access-permissions
• Search on Pages 404 pages does not work.
• 404 pages are not consistent across Assets, Gist and GitHub URLs.
• ghe-user-csv script doesn't return valid email addresses.
• SMTP over SSL/SMTPS on port 465 is not supported.
• We display the time in the scheduled maintenance banner in UTC instead of the viewer's timezone. (updated 2015-06-18)
• Images uploaded to issues save with an absolute URL, so they can be broken if the hostname changes. (updated 2015-07-14)
• With private mode enabled, a Pages site with no default page serves a generic error rather than an informative message. (updated 2015-07-14)