The 2.18 series release notes contain important changes in this release series.
- Packages have been updated to the latest security versions.
- Missing /etc/aliases.db file caused the deferred mail queue to fill with internal alert messages.
- The text toolbar and the subheading were overlapping on the global enterprise account Messages pages.
- It was possible for the two-factor authentication requirement on the global enterprise account to remain enabled after switching to an authentication mode that does not support built-in two-factor authentication (such as SAML).
- In large repos the protected branch settings page was loading slowly and triggering a timeout error.
- Attempting to unarchive a repository would fail due to schema mismatch.
- Viewing blobs in a repository was slow and could cause timeout errors under certain network conditions.
- Forking a private repository into an organization was erroneously blocked by an error that mentioned upgrading your plan.
- Added support for r5.8xlarge and r5.16xlarge EC2 instance types
- The number of pull requests that can be created from the same head SHA1 is limited to 100 by default.
- On a freshly set up GitHub Enterprise Server without any users, an attacker could create the first admin user.
- Custom firewall rules are not maintained during an upgrade.
- Subversion (SVN) checkout may timeout while the repository data cache is being built. In most cases, subsequent Subversion 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.
- 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.
- Security alerts are not reported when pushing to a repository on the command line. (updated 2020-06-23)
The GitHub Team