The 2.20 series release notes contain important changes in this release series.
- Packages have been updated to the latest security versions.
- Excessively large log events could lead to log forwarding instability when UDP was used as the transport mechanism.
- Automatic unsuspension of a user through SSO did not complete if the SSH keys attribute had keys already associated with the user's account.
- The repository permission hash from the REST API indicated no access for business members who have pull access to internal repositories.
- Previewing a GitHub App description written in markdown was not properly rendered.
- The audit log did not include branch protection changes events.
- Trying to assign code review to a member of an empty team would result in a '500 Internal Server Error'.
- Code review assignment using the load balancing algorithm could repeatedly assign to the same team member.
- 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.
- 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.
- Dependency graph is not detecting dependencies when deployed in a cluster configuration with multiple Redis nodes. (updated 2020-06-30)
The GitHub Team