The 2.3 series release notes contain important changes in this release series.
- We didn't accept OAuth application credentials using Basic Authentication when exchanging the code for a token. This meant developers couldn't use the standard Go OAuth2 library with GitHub Enterprise forcing developers to maintain their own fork of the library.
- When a member of a team with admin access tried to add a new team member, it failed without an error. Only the Owners team could add new team members.
- SNMP did not start on the high availability replica.
- It was not possible to upload files larger than 1GB with Git LFS.
- GitHub Pages reported a vague error message when page builds failed due to the use of an unsupported syntax highlighter.
- Some repositories could have temporary merge-trees directories left from git operations that timed out but weren't automatically cleaned up.
- MED Unvalidated parameters passed to the GitHub Enterprise metrics could be used to generate a denial of service attack against the appliance.
- LOW Large Git updates could trigger an overflow in Git xdiff.
- Packages have been updated to the latest security versions.
- We now retain more of the MySQL binlog files. This helps ensure MySQL replication can be automatically setup following an extended period without any replication.
- Setting up high availability replication can sometimes fail when establishing the VPN connection. We've made the output more verbose to help with determining the cause of these failures.
- We incorrectly redirect to the dashboard if you accessed GitHub Enterprise using an alias while in private mode. This might happen if you set a fully qualified domain name but the subdomain resolves correctly.
- Email can't be sent over TLS when SSL is disabled.
Deleting a user doesn't delete their gists, which can cause problems with replication.
- Images uploaded to issues save with an absolute URL, so they can be broken if the hostname changes.
- On a freshly set up GitHub Enterprise without any users, an attacker could create the first admin user.
- The management console settings interface doesn't clearly show if you have previously uploaded certificate files or a private key.
- Management console sessions can expire too quickly for Safari users.
- Gist repositories are not garbage collected by the maintenance scheduler.
- Custom firewall rules aren't maintained during an upgrade.
- Repositories that are in an incomplete state, which is a rare problem, can cause the migration to the new repository disk layout to fail.
- Enqueued background jobs are sometimes not purged when a repository is deleted.
- When a fork is detached from its repository network by an administrator or by changing visibility, its filesystem path won't be updated on a high availability replica until at least one commit has been pushed.
- Viewing raw files in repositories owned by a user or organization named "github" fails with a 400 error. (updated 2015-12-15)
- Trying to add a file to a repository with Subversion 1.9 clients incorrectly detects the file already exists and fails. (updated 2016-01-14)
- Not deleting a user's gists when deleting the user was fixed in 2.3.0. (updated 2015-10-12)
The GitHub Team