The 2.6 series release notes contain important changes in this release series.
- LOW: An internal upload policies API disclosed which users had push access to a repository.
- LOW: An internal administrative API was vulnerable to cross-site request forgery (CSRF).
- Packages have been updated to the latest security versions.
- Git LFS objects could take up to an hour to replicate in a High Availability configuration.
- Migrations failed to preserve a label with a
- The Management Console Add new SSH key field incorrectly allowed an SSH fingerprint instead of the contents of the key.
- A former primary appliance failed to create or update pre-receive hook environments.
<Destination> element is no longer optional in the SAML response.
Deprecation of GitHub Enterprise 2.4
GitHub Enterprise 2.4 is now deprecated as of February 9, 2017. That means that no patch releases will be made, even for critical security issues, after this release. For better performance, improved security, and new features, upgrade to the newest version of GitHub Enterprise as soon as possible.
Upcoming deprecation of GitHub Enterprise 2.5
GitHub Enterprise 2.5 will be deprecated as of March 14, 2017. That means that no patch releases will be made, even for critical security issues, after this date. For better performance, improved security, and new features, upgrade to the newest version of GitHub Enterprise as soon as possible.
- 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.
- On instances upgraded from 2.3 and earlier, restoring a protected branch archived whilst running 2.3, will not restore all the settings correctly. This does not affect new instances or protected branches archived on later releases.
- Editing custom messages in the Admin Center doesn't provide emoji suggestions.
- Native emoji are lost when saving custom messages in the Admin Center.
- Repository push logs don't record whether a push was forced.
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.
- Uploading PNG images with through the web interface can fail with the error 'Something went really wrong, and we can't process that file.'
- GitHub Enterprise clustering can not be configured without https.
- Console text is difficult to read on OpenStack KVM.
- 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.
- An issue or pull request comment containing the string "User-Agent: GitHub-Hookshot" incorrectly triggers a firewall rule and causes an internal server error on several pages, including the author's profile page. (updated 2017-03-30)
The GitHub Team