The NameID Format dropdown in the Management Console would be reset to "unspecified" after setting it to "persistent".
Upgrading using a hotpatch could fail with an error:
'libdbi1' was not found
Saving settings via the management console would append a newline to the TLS/SSL certificate and key files which triggered unnecessary reloading of some services.
System logs for Dependency Graph were not rotating, allowing unbounded storage growth.
The MS SQL Server performance graph showed statistics from the primary instance even when a replica was selected.
ghe-actions-precheck would silently exit without running the storage checks if Actions was not enabled.
Upgrade could fail if the resqued workers override setting is in use.
Some services running in containers were not sending logs to the journal.
Links to GitHub Security Advisories would use a URL with the hostname of the GitHub Enterprise Server instance instead of GitHub.com, directing the user to a nonexistent URL.
When importing a repository with
ghe-migrator, an unexpected exception could occur when inconsistent data is present.
The enterprise account security settings page showed a "View your organizations' current configurations" link for the "Two-factor authentication" setting when the authentication mode in use does not support built in two-factor authentication.
OAuth refresh tokens would be removed prematurely.
Search repair tasks would generate exceptions during the migration phase of configuration.
On the settings page for GitHub Apps, the "Beta Features" tab was not visible in some circumstances.
ghe-migrator to import PR review requests, records associated with deleted users would result in extraneous database records.
When importing users with
ghe-migrator, an error of "Emails is invalid" would occur if the system-generated email address were longer than 100 characters.
Logging webhook activity could use large amounts of disk space and cause the root disk to become full.
Users experienced slower Git clone and fetch performance on an instance with high availability replicas due to reads being forwarded to a different node.
The repository Settings page of a repository for a user or organization GitHub Pages sites would fail with a "500 Internal Server Error".
Repository network maintenance operations could become stuck in a
A repository being deleted immediately after uploading a code scanning result could cause a stall in the processing of code scanning results for all repositories.
When a large number of code scanning results were submitted at the same time, processing of batches could time out resulting in a stall in processing of code scanning results.
Creating a GitHub App from a manifest would fail.
GitHub usernames were changed unintentionally when using SAML authentication, when the GitHub username did not match the value of the attribute mapped to the
username field in the Management Console.