The 2.8 series release notes contain important changes in this release series.
- MEDIUM: GitHub Services webhooks could be configured to use non-HTTP protocols.
- Packages have been updated to the latest security versions.
admin:pre_receive_hook scope wasn't displayed when authorizing an Oauth application requesting this particular scope.
- Cloning or pushing repositories with Git LFS assets could fail with a '500 Internal Server Error'.
- The Alambic service, which serves avatars, release downloads, and image attachments, could crash and not recover.
- Visiting a user's profile page whilst signed out failed with a '500 Internal Server Error'.
- Memcached could fail to start if another process claimed its port first.
- SSH keys added to a user via LDAP sync are automatically verified.
Upcoming deprecation of GitHub Enterprise 2.8
GitHub Enterprise 2.8 will be deprecated as of November 9, 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.
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.
- Deleting a search index doesn't delete all associated metadata, which are then incorrectly reused if a new search index is created. This causes search index repair jobs to be reported as finished in the site admin when they were not.
- After changing the visibility of a repository, wiki search results have a conflicting number of displayed search results. Administrators can reindex the wiki through the site admin dashboard. (updated 2017-11-09)
The GitHub Team