Enterprise Server 3.1 release notes
Enterprise Server 3.1.6
DownloadAugust, 24, 2021
Packages have been updated to the latest security versions.
Attaching very large images or animated GIFs to images or pull requests would fail.
Journald messages related to automatic updates (
Adding h/m/s random time.) were logged to syslog.Custom pre-receive hooks that created named pipes (FIFOs) would crash or hang, resulting in a timeout error.
Adding filters to the audit log advanced search page did not populate the query text box in real-time with the correct facet prefix and value.
Git hooks to the internal API that result in failing requests returned the exception
undefined method body for "success":String (NoMethodError)instead of returning an explicitnil.When an integration was removed, it was possible for an unrelated OAuth application or integration to also be removed.
When a mandatory message containing an emoji character was added, attempting to view or change the message would return a 500 Internal Server Error.
Adds
triageandmaintainto the list of permissions returned by the REST API.
The GitHub Packages npm registry no longer returns a time value in metadata responses. This was done to allow for substantial performance improvements. We continue to have all the data necessary to return a time value as part of the metadata response and will resume returning this value in the future once we have solved the existing performance issues.
On a freshly set up GitHub Enterprise Server without any users, an attacker could create the first admin user.
Custom firewall rules are removed during the upgrade process.
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 blob's 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.
Enterprise Server 3.1.5
DownloadAugust, 10, 2021
📣 This is not the latest patch release of Enterprise Server. Please use the latest release for the latest security, performance, and bug fixes.
Custom pre-receive hooks that used a bash subshell would return an error:
No such file or directory.When GitHub Actions is enabled without running regular scheduled backups the MSSQL Transaction Log could grow unbounded and can consume all available space on the appliance's Data Disk causing a possible outage.
Unnecessary database logging consumed a large amount of disk space on instances with heavy LFS usage.
Audit log entries for changes made to "Repository creation" organization settings were inaccurate.
Excessive logging of
ActionController::UnknownFormatexceptions caused unnecessary disk usage.LDAP
group_dnvalues longer than 255 characters would result in errors being logged:Data truncated for column 'group_dn' at row 1.
Abuse rate limits are now called Secondary rate limits, since the behavior they limit is not always abusive.
The GitHub Packages npm registry no longer returns a time value in metadata responses. This was done to allow for substantial performance improvements. We continue to have all the data necessary to return a time value as part of the metadata response and will resume returning this value in the future once we have solved the existing performance issues.
On a freshly set up GitHub Enterprise Server without any users, an attacker could create the first admin user.
Custom firewall rules are removed during the upgrade process.
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 blob's 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.
Enterprise Server 3.1.4
DownloadJuly, 27, 2021
📣 This is not the latest patch release of Enterprise Server. Please use the latest release for the latest security, performance, and bug fixes.
Packages have been updated to the latest security versions.
The counts on packages pages were not being incremented when a package was downloaded.
ghe-config-applywould timeout, ask for a prompt or fail for a customer that had secret scanning enabled, and had either disabled or never enabled GitHub Actions on their instance.Log files were not reopened after rotation in some cases leading to high disk space usage on instances with high uptime.
Upgrade could fail from older version of GitHub Enterprise Server due to a missing job in GitHub Actions.
Custom pre-receive hooks could lead to an error like
error: object directory /data/user/repositories/0/nw/12/34/56/7890/network.git/objects does not exist; check .git/objects/info/alternates.Unauthenticated HTTP proxy for the pages containers build was not supported for any users that use HTTP proxies.
A significant number of 503 errors were logged every time a user visited a repository's
/settingspage if the dependency graph was not enabled.Internal repositories were only returned when a user had affiliations with the repository through a team or through collaborator status, or queried with the
?type=internalparameter.Failed background jobs had unlimited retries which could cause large queue depths.
A significant number of 503 errors were being created if the scheduled job to sync vulnerabilities with GitHub.com attempted to run when dependency graph was not enabled and content analysis was enabled.
When GitHub Actions is enabled without running regular scheduled backups, the MSSQL transaction log could grow unbounded and can consume all available space on the appliance's data disk, causing a possible outage.
If you have configured regularly scheduled MSSQL backups, no further actions is required. Otherwise, if you have GitHub Actions previously enabled, run the following commands after installing this patch.
ghe-actions-console -s Mps -c 'Update-Service -Force' ghe-actions-console -s Token -c 'Update-Service -Force' ghe-actions-console -s Actions -c 'Update-Service -Force'
The logs for
babeldnow include acmdfield for HTTP ref advertisement requests instead of only including it during the negotiation requests.
The GitHub Packages npm registry no longer returns a time value in metadata responses. This was done to allow for substantial performance improvements. We continue to have all the data necessary to return a time value as part of the metadata response and will resume returning this value in the future once we have solved the existing performance issues.
On a freshly set up GitHub Enterprise Server without any users, an attacker could create the first admin user.
Custom firewall rules are removed during the upgrade process.
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 blob's 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.
Enterprise Server 3.1.3
DownloadJuly, 14, 2021
📣 This is not the latest patch release of Enterprise Server. Please use the latest release for the latest security, performance, and bug fixes.
HIGH: A path traversal vulnerability was identified in GitHub Enterprise Server that could be exploited when building a GitHub Pages site. User-controlled configuration options used by GitHub Pages were not sufficiently restricted and made it possible to read files on the GitHub Enterprise Server instance. To exploit this vulnerability, an attacker would need permission to create and build a GitHub Pages site on the GitHub Enterprise Server instance. This vulnerability affected all versions of GitHub Enterprise Server prior to 3.1.3 and has been assigned CVE-2021-22867. This vulnerability was reported via the GitHub Bug Bounty program.
Packages have been updated to the latest security versions.
SAML expiration date variable was not configurable.
Application services would fail their health checks during config apply before they could enter a healthy state.
ghe-cluster-config-node-initwould fail during cluster setup if HTTP proxy is enabled.Pre-receive hooks could encounter an error
Failed to resolve full path of the current executabledue to/procnot being mounted on the container.Collectd would not resolve the forwarding destination hostname after the initial startup.
The job that purged stale deleted repositories could fail to make progress if some of those repositories were protected from deletion by legal holds.
Background jobs were being queued to the
spamqueue which were not being processed.The preferred merge method would be reset when retrying after a failed PR merge.
Git pushes could result in a 500 Internal Server Error during the user reconciliation process on instances using LDAP authentication mode.
After upgrading from 3.0.x to 3.1.x, in some cases GitHub Actions would fail with an error:
An unexpected error occurred when executing this workflow.
Improved the efficiency of config apply by skipping IP allow firewall rules that had not changed, which saved significant time on large clusters.
The GitHub Packages npm registry no longer returns a time value in metadata responses. This was done to allow for substantial performance improvements. We continue to have all the data necessary to return a time value as part of the metadata response and will resume returning this value in the future once we have solved the existing performance issues.
On a freshly set up GitHub Enterprise Server without any users, an attacker could create the first admin user.
Custom firewall rules are removed during the upgrade process.
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 blob's 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.
Enterprise Server 3.1.2
DownloadJune, 24, 2021
📣 This is not the latest patch release of Enterprise Server. Please use the latest release for the latest security, performance, and bug fixes.
Packages have been updated to the latest security versions.
A large number of
gauge-dependency-graph-api-dispatch_dispatchmetrics could accumulate in the Management Console.The sshd service would sometimes fail to start on instances running on Google Cloud Platform.
Old upgrade files would persist on the user disk, sometimes resulting in out of space conditions.
gh-migratordisplayed an incorrect path to its log output.An export archive would silently fail to import pull requests if they contained review requests from teams not present in the archive.
Update the GitHub Actions Runner version in GHES 3.1 to v2.278.0
The GitHub Packages npm registry no longer returns a time value in metadata responses. This was done to allow for substantial performance improvements. We continue to have all the data necessary to return a time value as part of the metadata response and will resume returning this value in the future once we have solved the existing performance issues.
On a freshly set up GitHub Enterprise Server without any users, an attacker could create the first admin user.
Custom firewall rules are removed during the upgrade process.
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 blob's 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.
After upgrading from 3.0.x to 3.1.x, in some cases GitHub Actions can fail with an error:
An unexpected error occurred when executing this workflow.To workaround this problem, connect to the administrative shell (ssh) and run:ghe-actions-console -s actions -c "Queue-ServiceJob -JobId 4DB1F4CF-19FD-40E0-A253-91288813DE8B"
Enterprise Server 3.1.1
DownloadJune, 10, 2021
📣 This is not the latest patch release of Enterprise Server. Please use the latest release for the latest security, performance, and bug fixes.
Packages have been updated to the latest security versions.
SVN 1.7 and older clients showed an error when using the
svn coandsvn exportcommands.Accessing a repository through the administrative shell using
ghe-repo <owner>/<reponame>would hang.After upgrading, users experienced reduced availability during heavy usage, because services restarted too frequently. This would occur due to timeout mismatches between the nomad configuration and that of the internal services.
In some instances, running
ghe-repl-statusafter setting up GitHub Actions would produce an error andghe-actions-teardownwould fail.ghe-dbconsolewould return errors under some circumstances.Import failures of organizations or repositories from non-GitHub sources could produce an
undefined method '[]' for nil:NilClasserror.GitHub profile names might have changed unintentionally when using SAML authentication, if the GitHub profile name did not match the value of the attribute mapped to the
Full namefield in the Management Console.Upgrading an instance that had previously ran a 2.13 release, but not a 2.14 release, resulted in a database migration error relating to the
AddRepositoryIdToCheckRunsdata transition.
Users of the GraphQL API can query the public field
closingIssuesReferenceson thePullRequestobject. This field retrieves issues that will be automatically closed when the related pull request is merged. This approach will also allow this data to be migrated in future, as part of a higher fidelity migration process.
The GitHub Packages npm registry no longer returns a time value in metadata responses. This was done to allow for substantial performance improvements. We continue to have all the data necessary to return a time value as part of the metadata response and will resume returning this value in the future once we have solved the existing performance issues.
On a freshly set up GitHub Enterprise Server without any users, an attacker could create the first admin user.
Custom firewall rules are removed during the upgrade process.
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 blob's 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.
After upgrading from 3.0.x to 3.1.x, in some cases GitHub Actions can fail with an error:
An unexpected error occurred when executing this workflow.To workaround this problem, connect to the administrative shell (ssh) and run:ghe-actions-console -s actions -c "Queue-ServiceJob -JobId 4DB1F4CF-19FD-40E0-A253-91288813DE8B"When a replica node is offline in a high availability configuration, GitHub Enterprise Server may still route GitHub Pages requests to the offline node, reducing the availability of GitHub Pages for users.
Enterprise Server 3.1.0
DownloadJune, 03, 2021
📣 This is not the latest patch release of Enterprise Server. Please use the latest release for the latest security, performance, and bug fixes.