The 2.18 series release notes contain important changes in this release series.
- Packages have been updated to the latest security versions.
- Live updates for pull requests and issues would fail due to an incorrect list of allowed origin domains.
- A Git operation could fail to connect to the server with a SIGABRT error in certain cases.
- WireGuard private keys were missing in some cases, causing a failure to connect.
- Restarting replication after an upgrade using
ghe-repl-start could fail to detect an existing configuration run and break the replication between HA nodes.
- Promotion of an HA replica would cause a memory leak in some cases.
- Site administrators could have two-factor authentication disabled via the Site Admin dashboard when two-factor authentication was enabled on the global enterprise account.
- A background job that doesn't apply to GitHub Enterprise Server was enqueued but never processed.
- 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