|
| 1 | +date: '2025-07-01' |
| 2 | +sections: |
| 3 | + security_fixes: |
| 4 | + - | |
| 5 | + Packages have been updated to the latest security versions. |
| 6 | + bugs: |
| 7 | + - | |
| 8 | + The Management Console would become unresponsive when saving settings after a failed config apply run. |
| 9 | + - | |
| 10 | + Users sometimes received a JSON response instead of a web page when clicking "Back" after viewing files in raw format. |
| 11 | + - | |
| 12 | + The secret scanning metrics page displayed data for expired delegated bypass requests. |
| 13 | + - | |
| 14 | + Users could not create or view secret scanning push protection bypass requests for forked repositories because bypass requests were incorrectly associated with the root repository rather than the fork. Forked repositories now support their own bypass requests. |
| 15 | + - | |
| 16 | + When users added a team with a repository role to the `CODEOWNERS` file, an unknown error was displayed. Teams with repository roles are now correctly recognized as valid owners of files. |
| 17 | + changes: |
| 18 | + - | |
| 19 | + The babeld service no longer reports log messages about some common client-induced networking errors, reducing noise in the logs. |
| 20 | + known_issues: |
| 21 | + - | |
| 22 | + Applying a new GitHub Enterprise Server license using the Management Console can sometimes fail with an HTTP 500 error. |
| 23 | + - | |
| 24 | + Custom firewall rules are removed during the upgrade process. |
| 25 | + - | |
| 26 | + During the validation phase of a configuration run, a `No such object` error may occur for the Notebook and Viewscreen services. This error can be ignored as the services should still correctly start. |
| 27 | + - | |
| 28 | + If the root site administrator is locked out of the Management Console after failed login attempts, the account does not unlock automatically after the defined lockout time. Someone with administrative SSH access to the instance must unlock the account using the administrative shell. For more information, see "[AUTOTITLE](/admin/configuration/administering-your-instance-from-the-management-console/troubleshooting-access-to-the-management-console#unlocking-the-root-site-administrator-account)." |
| 29 | + - | |
| 30 | + On an instance with the HTTP `X-Forwarded-For` header configured for use behind a load balancer, all client IP addresses in the instance's audit log erroneously appear as 127.0.0.1. |
| 31 | + - | |
| 32 | + {% data reusables.release-notes.large-adoc-files-issue %} |
| 33 | + - | |
| 34 | + Admin stats REST API endpoints may timeout on appliances with many users or repositories. Retrying the request until data is returned is advised. |
| 35 | + - | |
| 36 | + When following the steps for [Replacing the primary MySQL node](/admin/monitoring-managing-and-updating-your-instance/configuring-clustering/replacing-a-cluster-node#replacing-the-primary-mysql-node), step 14 (running `ghe-cluster-config-apply`) might fail with errors. If this occurs, re-running `ghe-cluster-config-apply` is expected to succeed. |
| 37 | + - | |
| 38 | + Running a config apply as part of the steps for [Replacing a node in an emergency](/admin/monitoring-managing-and-updating-your-instance/configuring-clustering/replacing-a-cluster-node#replacing-a-node-in-an-emergency) may fail with errors if the node being replaced is still reachable. If this occurs, shutdown the node and repeat the steps. |
| 39 | + - | |
| 40 | + {% data reusables.release-notes.2024-06-possible-frontend-5-minute-outage-during-hotpatch-upgrade %} |
| 41 | + - | |
| 42 | + When restoring data originally backed up from a 3.13 or greater appliance version, the Elasticsearch indices need to be reindexed before some of the data will show up. This happens via a nightly scheduled job. It can also be forced by running `/usr/local/share/enterprise/ghe-es-search-repair`. |
| 43 | + - | |
| 44 | + An organization-level code scanning configuration page is displayed on instances that do not use GitHub Advanced Security or code scanning. |
| 45 | + - | |
| 46 | + When enabling automatic update checks for the first time in the Management Console, the status is not dynamically reflected until the "Updates" page is reloaded. |
| 47 | + - | |
| 48 | + When restoring from a backup snapshot, a large number of `mapper_parsing_exception` errors may be displayed. |
| 49 | + - | |
| 50 | + When initializing a new GHES cluster, nodes with the `consul-server` role should be added to the cluster before adding additional nodes. Adding all nodes simultaneously creates a race condition between nomad server registration and nomad client registration. |
| 51 | + - | |
| 52 | + Admins setting up cluster high availability (HA) may encounter a spokes error when running `ghe-cluster-repl-status` if a new organization and repositories are created before using the `ghe-cluster-repl-bootstrap` command. To avoid this issue, complete the cluster HA setup with `ghe-cluster-repl-bootstrap` before creating new organizations and repositories. |
| 53 | + - | |
| 54 | + In a cluster, the host running restore requires access the storage nodes via their private IPs. |
| 55 | + - | |
| 56 | + On an instance hosted on Azure, commenting on an issue via email meant the comment was not added to the issue. |
| 57 | + - | |
| 58 | + After a restore, existing outside collaborators cannot be added to repositories in a new organization. This issue can be resolved by running `/usr/local/share/enterprise/ghe-es-search-repair` on the appliance. |
| 59 | + - | |
| 60 | + After a geo-replica is promoted to be a primary by running `ghe-repl-promote`, the actions workflow of a repository does not have any suggested workflows. |
0 commit comments