The 2.7 series release notes contain important changes in this release series.
- Packages have been updated to the latest security versions.
- Pushing an update could cause the
babeld service to segment fault under certain circumstances.
- The deletion of branches and tags rejected by a
pre-receive hook would have failed with the error "Something went wrong with the request. Please try again."
- Attempts were prematurely made to gather
redis performance statistics. This resulted in excessive logging to the collectd log files.
- Appliance settings saved using the
/setup/api/settings API endpoint failed to apply when applying at the same time as uploading the license for the first time.
- Access to a repository granted to teams during a transfer to an organization didn't take effect.
- GitHub Enterprise is now available in the EU West (London) and Canada (Central) AWS regions.
- We incorrectly redirect to the dashboard if you accessed GitHub Enterprise using an alias while in private mode. This might happen if you set a fully qualified domain name but the subdomain resolves correctly.
- Images uploaded to issues save with an absolute URL, so they can be broken if the hostname changes.
- On a freshly set up GitHub Enterprise without any users, an attacker could create the first admin user.
- Custom firewall rules aren't maintained during an upgrade.
- Enqueued background jobs are sometimes not purged when a repository is deleted.
svn checkout may timeout while the repository data cache is being built. In most cases, subsequent
svn checkout attempts will succeed.
- Git LFS tracked files uploaded through the web interface are incorrectly added directly to the repository.
- GitHub Enterprise clustering can not be configured without https.
- Additional white spacing can sometimes be seen above the Admin center header.
- The initial import of the VMware OVA image may fail when deployed via vCenter Server 6.0 or 6.5. The import will succeed when performed directly on an ESXi host. (updated 2017-02-23)
- Git LFS objects may take up to an hour to replicate in a High Availability configuration. (updated 2017-02-23)
- collectd metric paths can be truncated, which causes multiple write attempts to the same file for different metrics. (updated 2017-07-10)
The GitHub Team