The 2.2 series release notes contain important changes in this release series.
- We've added more graphs to the monitoring dashboard.
- The Linux Out-Of-Memory killer is configured to deprioritize killing MySQL in cases of memory shortage.
- Setting up replication now ensures that the replica passes the preflight checks.
- Upgrading to GitHub Enterprise 2.2 with a lot of repositories could be slow due to unnecessary permission changes.
- In some circumstances, after an upgrade we prompted you to upload a license, even though there was already a valid license.
- Creating diagnostics could time out due to large numbers of webhook delivery logs.
- The number of diffs for non-text file types displayed in pull requests was often too small. It's been increased from 25 to 100.
- Management console monitoring graphs were refreshed too often, and the application server could fail to keep up.
- Checking the high availability Git replication status could throw an error when working out what repositories need to be replicated.
- Upgrading caused private mode to become enabled.
- SAML authentication always provided the optional
KeyInfo element with no signing certificate in the
AuthnRequest response, which caused errors for some identity providers. We don't include the optional
KeyInfo element at all now.
- Events in the
github_audit log stream were being logged twice.
- Empty Git LFS objects caused errors.
- The Subversion bridge would skip revisions or number them incorrectly.
- Background jobs running during a backup would never be processed if the backup was restored.
- Suspended LDAP users were unsuspended if no LDAP restricted groups were configured.
- We didn't recognize email addresses with trailing whitespace as valid when inviting users, and showed a confusing error message.
- Enabling Hyper-V Dynamic Memory caused kernel panics.
- A high availability replica set up multiple times could show an out of sync repository as up to date.
- The merge button could break when a high availability replica was promoted to primary.
- Session cookies could become very large and fill the HAProxy buffer when CAS authentication is enabled, causing server errors.
- PubSubHubbub requests could be slow.
- Browsing to the HTTP or HTTPS clone URL didn't redirect to the repository, which wasn't consistent with previous versions or GitHub.com.
- On very busy instances, the worker processes delivering webhooks in the background could fall behind. Now there are more worker processes, if you have provisioned enough memory.
- On instances with thousands of users, requests to the discover Gists page could time out.
- The endpoint for marking notifications as read was behind authentication, which caused unneeded traffic and meant that read notifications weren't correctly archived.
- GitHub Enterprise could become briefly unstable if a Pages site build timed out, for example for very large Pages sites.
- On busy instances, the GitHub application server's backlog could fill up, causing the web server to time out.
- Git LFS objects were limited to 1 GB. We've bumped the limit to 2 GB
- Ubuntu kernel has been updated to include security fixes.
- Service hooks may log passwords used for HTTP Basic authentication to disk. (updated 2015-07-28)
- The site admin shows errors in the "repo reflogs" section, which isn't fully implemented on GitHub Enterprise.
- Promoting a high availability replica can fail if Elasticsearch takes too long to restart.
- Gists can't be created when using Safari 8.x in Private Mode.
- Dashboard activity feed links point to wrong hostname after restoring from backup if the hostname has changed.
- Jobs stuck on code indexing can delay other jobs from running.
- The management console settings interface doesn't clearly show if you have previously uploaded certificate files or a private key.
- On a freshly set up GitHub Enterprise without any users, an attacker could create the first admin user.
- Organization invitation emails are sent from the configured support email address rather than the no-reply address.
- Replication setup fails for IPv6 hosts.
- SNMP can't be run on high availability replicas.
- We can fail to properly create the key for the secure connection between a high availability replica and the primary, which causes replication setup to fail.
- Gist profile pages don't have proper styling when subdomain isolation is disabled.
- Management console sessions can expire too quickly for Safari users.
- A high availability replica that's been promoted to primary and then set up as a replica again doesn't properly show the replica status page, but shows "Starting..." instead.
- Custom firewall rules aren't maintained during an upgrade.
Mail delivery to localhost fails. (updated 2015-07-14)
- Images uploaded to issues save with an absolute URL, so they can be broken if the hostname changes.
- With private mode enabled, a Pages site with no default page serves a generic error rather than an informative message.
- Enqueued background jobs are sometimes not purged when a repository is deleted.
- Gist repositories are not garbage collected by the maintenance scheduler.
- Deleting a user doesn't delete their gists, which can cause problems with replication.
- In our instructions to merge a pull request on the command line, we show the steps to merge using the Git protocol even when private mode is on. Private mode forces authentication but the Git protocol is unauthenticated so the steps will always fail. We also don't show the steps to merge using SSH.
- We incorrectly redirect to the dashboard if you access 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.
- We show your gravatar or identicon on Gists instead of your custom profile picture. (updated 2015-06-15)
ghe-resque-info script incorrectly shows all background job queues as empty. (updated 2015-06-16)
- We display the time in the scheduled maintenance banner in UTC instead of the viewer's timezone. (updated 2015-06-18)
- Users with LDAP DNs longer than 255 characters are suspended if LDAP Sync is enabled. (updated 2015-06-19)
- Editing a Gist can cause a 500 error. This is an authentication problem between Gist and GitHub Enterprise, so logging out and back in again should fix the problem. (updated 2015-07-15)
- Using uppercase characters in the hostname causes a redirect loop. (updated 2015-07-28)
- 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. (updated 2015-08-13)
- Updates to Wiki pages by users without a primary email address set throw errors. (updated 2015-08-25)
- 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)
- Failure to deliver mail to localhost was fixed in 2.2.0. (updated 2015-07-14)
The GitHub Team