The 2.21 series release notes contain important changes in this release series.
This release provides a fix for the major bug affecting the 2.21.0 release. We appreciate your patience in upgrading to 2.21 while we fixed these issues.
- 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.
- The internal communication service used to access MySQL could restart more often than required, including part way through the upgrade process, which could cause the upgrade to partially fail. We have reduced the rate of restarts and made the code more robust.
- 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.
- The "Repository issue deletion" Enterprise account policy did not reflect the currently saved setting.
- The audit log did not include branch protection changes events.
- 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.
The GitHub Team