Enterprise Server 3.6 release notes
Enterprise Server 3.6.11
Download GitHub Enterprise Server 3.6.11March 23, 2023
📣 This is not the latest release of Enterprise Server. Please use the latest release for the latest security, performance, and bug fixes.
3.6.11: Bug fixes
In the Management Console's monitor dashboard, the
Cached RequestsandServed Requestsgraphs, which are retrieved by thegit fetch catchingcommand, did not display metrics for the instance.After a site administrator exempted the @github-actions[bot] user from rate limiting by using the
ghe-config app.github.rate-limiting-exempt-users "github-actions[bot]"command, runningghe-config-checkcaused aValidation is-valid-characterset failedwarning to appear.GitHub Actions (
actions) and Microsoft SQL (mssql) did not appear in the list of processes within the instances monitor dashboard.After an administrator used the
/setup/api/startREST API endpoint to upload a license, the configuration run failed with aConnection refusederror during the migrations phase.In some cases, on an instance with a GitHub Advanced Security license and secret scanning enabled, users may have seen a discrepancy between the number of alerts displayed on a repositorys "Security" tab and in the sidebar for the "Security" tab.
On an instance in a cluster configuration, when a site administrator set maintenance mode using
ghe-maintenance -s, aPermission deniederror appeared when the utility tried to access/data/user/common/cluster.conf.On an instance in a high availability configuration, if an administrator tore down replication from a replica node using
ghe-repl-teardownimmediately after runningghe-repl-setup, but beforeghe-repl-start, an error indicated that the scriptcannot launch /usr/local/bin/ghe-single-config-apply - run is locked.ghe-repl-teardownnow displays an informational alert and continues the teardown.During configuration of high availability, if a site administrator interrupted the
ghe-repl-startutility, the utility erroneously reported that replication was configured, and the instance would not perform expected clean-up operations.Responses from the
/repositoriesREST API endpoint erroneously included deleted repositories.When a site administrator used
ghe-migratorto migrate data to GitHub Enterprise Server, in some cases, nested team relationships would not persist after teams were imported.If a repository contained a
CODEOWNERSfile with check annotations, pull requests "Files changed" tab returned a500error and displayed "Oops, something went wrong" in the "Unchanged files with check annotations" section.After upgrading an instance with a GitHub Advanced Security license to GitHub Enterprise Server 3.6 or 3.7, creating a repository or viewing the security settings page for an organization or repository could result in a
500error due to a GitHub Advanced Security backfill job not completing before the upgrade started.On an instance with GitHub Actions enabled, if a user manually triggered a workflow using the REST API but did not specify values for optional booleans, the API failed to validate the request and returned a
422error.The CSV reports for all users and all active users, available from the site admin dashboard, did not consider recent access using SSH or personal access tokens.
On an instance with GitHub Connect enabled, if "Users can search GitHub.com" was enabled, users would not see issues in private and internal repositories in search results for GitHub.com.
GitHub Enterprise Server published distribution metrics that cannot be processed by collectd. The metrics included
pre_receive.lfsintegrity.dist.referenced_oids,pre_receive.lfsintegrity.dist.unknown_oids, andgit.hooks.runtime.On an instance with a GitHub Advanced Security license, if code scanning had been used while running GitHub Enterprise Server 3.4 or earlier, a subsequent upgrade from 3.5 to 3.6 or 3.7 could fail when attempting to add a unique index to a database table.
3.6.11: Changes
After an enterprise owner enables Dependabot updates, the instance creates the initial set of updates faster.
On an instance in a cluster configuration, when a site administrator sets maintenance mode on a single cluster node using
ghe-maintenance -s, the utility warns the administrator to useghe-cluster-maintenance -sto set maintenance mode on all of the clusters nodes. For more information, see "Enabling and scheduling maintenance mode."When a site administrator configures an outbound web proxy server for GitHub Enterprise Server, the instance now validates top-level domains (TLDs) excluded from the proxy configuration. By default, you can exclude public TLDs that the IANA specifies. Site administrators can specify a list of unregistered TLDs to exclude using
ghe-config. The.prefix is required for any public TLDs. For example,.example.comis valid, butexample.comis invalid. For more information, see "Configuring an outbound web proxy server."To avoid intermittent issues with the success of Git operations on an instance with multiple nodes, GitHub Enterprise Server checks the status of the MySQL container before attempting a SQL query. The timeout duration has also been reduced.
The default path for output from
ghe-saml-mapping-csv -dis/data/user/tmpinstead of/tmp. For more information, see "Command-line utilities."
3.6.11: Known issues
On a freshly set up GitHub Enterprise Server instance 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.
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.
Instances experiencing a high sustained number of concurrent Git requests may experience performance issues. If you suspect that this issue is affecting your instance, contact GitHub Support. For more information, see "Creating a support ticket." [Updated: 2022-12-07]
In a repository's settings, enabling the option to allow users with read access to create discussions does not enable this functionality.
Custom patterns for secret scanning have
.*as an end delimiter, specifically in the "After secret" field. This delimiter causes inconsistencies in scans for secrets across repositories, and you may notice gaps in a repository's history where no scans completed. Incremental scans may also be impacted. To prevent issues with scans, modify the end of the pattern to remove the.*delimiter.Following an upgrade to GitHub Enterprise Server 3.6 or later, existing inconsistencies in a repository such as broken refs or missing objects, may now be reported as errors like
invalid sha1 pointer 0000000000000000000000000000000000000000,Zero-length loose reference file, orZero-length loose object file. Previously, these indicators of repository corruption may have been silently ignored. GitHub Enterprise Server now uses an updated Git version with more diligent error reporting enabled. For more information, see this upstream commit in the Git project.If you suspect a problem like this exists in one of your repositories, contact GitHub Enterprise Support for assistance.
Enterprise Server 3.6.10
Download GitHub Enterprise Server 3.6.10March 02, 2023
📣 This is not the latest patch release of this release series, and this is not the latest release of Enterprise Server. Please use the latest release for the latest security, performance, and bug fixes.
3.6.10: Security fixes
"HIGH: A path traversal vulnerability was identified in GitHub Enterprise Server that allowed remote code execution when building a GitHub Pages site. 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 was reported via the GitHub Bug Bounty Program and has been assigned CVE-2023-23760.
3.6.10: Bug fixes
When viewing a list of open sessions for the devices logged into a user account, the GitHub Enterprise Server web UI could display an incorrect location.
In the rare case when primary shards for Elasticsearch were located on a replica node, the
ghe-repl-stopcommand would fail withERROR: Running migrations.The settings page for discussions in an organization returned a
500error after a repository owned by the organization was deleted.
3.6.10: Known issues
On a freshly set up GitHub Enterprise Server instance 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.
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.
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.
Resource limits that are specific to processing pre-receive hooks may cause some pre-receive hooks to fail.
Actions services need to be restarted after restoring an instance from a backup taken on a different host.
In a repository's settings, enabling the option to allow users with read access to create discussions does not enable this functionality.
Custom patterns for secret scanning have
.*as an end delimiter, specifically in the "After secret" field. This delimiter causes inconsistencies in scans for secrets across repositories, and you may notice gaps in a repository's history where no scans completed. Incremental scans may also be impacted. To prevent issues with scans, modify the end of the pattern to remove the.*delimiter.Following an upgrade to GitHub Enterprise Server 3.6 or later, existing inconsistencies in a repository such as broken refs or missing objects, may now be reported as errors like
invalid sha1 pointer 0000000000000000000000000000000000000000,Zero-length loose reference file, orZero-length loose object file. Previously, these indicators of repository corruption may have been silently ignored. GitHub Enterprise Server now uses an updated Git version with more diligent error reporting enabled. For more information, see this upstream commit in the Git project.If you suspect a problem like this exists in one of your repositories, contact GitHub Enterprise Support for assistance.
Instances experiencing a high sustained number of concurrent Git requests may experience performance issues. If you suspect that this issue is affecting your instance, contact GitHub Support. For more information, see "Creating a support ticket." [Updated: 2022-12-07]
In some cases, while converting an issue to a discussion, the conversion process may hang. In this situation, an enterprise owner can try the following troubleshooting steps to resolve the issue.
- At the end of the stuck discussion's URL, note the discussion's number.