The 2.17 series release notes contain important changes in this release series.
- Packages have been updated to the latest security versions.
- Resque workers may not have been cleaned up following a configuration run leading to a growing number of stale workers which in turn could lead to high memory consumption.
- Viewing the profile of a user with a username similar to a common HTML error page, for example
404-html, would display the error page and not the user's profile.
- Reattaching a forked repository to its parent after changing the visibility would fail for the second and subsequent forks.
- The global enterprise account members page did not list all members of the installation.
- Creating a new repository could fail with a 404 error if the user is an owner of a large number of organizations.
- On a freshly set up GitHub Enterprise Server without any users, an attacker could create the first admin user.
- Custom firewall rules aren't maintained during an upgrade.
- Subversion (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.
- Issues cannot be closed if they contain a permalink to a blob in the same repository where the file path is longer than 255 characters.
- Hypervisor type and root volumes are incorrectly detected on AWS Nitro instance types, preventing non-hotpatch upgrades. (updated: 2019-07-09)
- Lines in gists are not selectable. (updated: 2019-07-19)
- When "Users can search GitHub.com" is enabled with GitHub Connect, issues in private and internal repositories are not included in GitHub.com search results.
The GitHub Team