|
| 1 | +date: '2025-07-29' |
| 2 | +sections: |
| 3 | + security_fixes: |
| 4 | + - | |
| 5 | + The maintenance page in the Management Console did not include cross-site request forgery (CSRF) protection. |
| 6 | + - | |
| 7 | + Packages have been updated to the latest security versions. |
| 8 | + bugs: |
| 9 | + - | |
| 10 | + On instances in a cluster configuration, builds of GitHub Pages sites timed out in GitHub Actions workflows. |
| 11 | + - | |
| 12 | + Administrators would occasionally encounter timeouts when downloading diagnostics via the Management Console. |
| 13 | + - | |
| 14 | + In full cluster topologies, some expensive stats queries are skipped during `ghe-cluster-support-bundle` to prevent overloading the nodes with identical requests. |
| 15 | + - | |
| 16 | + Unsuccessful attempts to sign in to the Management Console were reported in the audit log and were indistinguishable from successful attempts. |
| 17 | + - | |
| 18 | + Enterprise Managed Users (EMUs) who were restricted from creating user namespace repositories could still create repositories in organizations and transfer them to their user namespace. |
| 19 | + - | |
| 20 | + In some scenarios, during an upgrade from GHES 3.14 to GHES 3.16 the `BackfillDefaultLegacyEnterpriseConfigurationsTransition` migration step could fail. |
| 21 | + - | |
| 22 | + Administrators and users could experience delays due to performance regressions affecting the background processing of notification jobs. |
| 23 | + changes: |
| 24 | + - | |
| 25 | + For administrators performing a live upgrade, a new entry point has been added to the upgrade container to clean up database tables. This utility can be run manually via `ghe-live-migrations -cleanup`, and is also executed automatically via `ghe-config-apply` after a complete upgrade. |
| 26 | + - | |
| 27 | + During pre-upgrade operations of a live upgrade, tables are now renamed instead of being dropped immediately. The tables are then dropped at a later stage via `ghe-config-apply`. |
| 28 | + - | |
| 29 | + Events for adding or removing issues and pull requests from a project, or changing their status within a project, are now included in the items timeline alongside existing events. This update helps administrators and users more comprehensively track project-related activity. |
| 30 | + known_issues: |
| 31 | + - | |
| 32 | + Custom firewall rules are removed during the upgrade process. |
| 33 | + - | |
| 34 | + 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. |
| 35 | + - | |
| 36 | + 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)." |
| 37 | + - | |
| 38 | + 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. |
| 39 | + - | |
| 40 | + {% data reusables.release-notes.large-adoc-files-issue %} |
| 41 | + - | |
| 42 | + Admin stats REST API endpoints may timeout on appliances with many users or repositories. Retrying the request until data is returned is advised. |
| 43 | + - | |
| 44 | + 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. |
| 45 | + - | |
| 46 | + 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. |
| 47 | + - | |
| 48 | + {% data reusables.release-notes.2024-06-possible-frontend-5-minute-outage-during-hotpatch-upgrade %} |
| 49 | + - | |
| 50 | + 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`. |
| 51 | + - | |
| 52 | + An organization-level code scanning configuration page is displayed on instances that do not use GitHub Advanced Security or code scanning. |
| 53 | + - | |
| 54 | + 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. |
| 55 | + - | |
| 56 | + When restoring from a backup snapshot, a large number of `mapper_parsing_exception` errors may be displayed. |
| 57 | + - | |
| 58 | + 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. |
| 59 | + - | |
| 60 | + 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. |
| 61 | + - | |
| 62 | + In a cluster, the host running restore requires access the storage nodes via their private IPs. |
| 63 | + - | |
| 64 | + On an instance hosted on Azure, commenting on an issue via email meant the comment was not added to the issue. |
| 65 | + - | |
| 66 | + 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. |
| 67 | + - | |
| 68 | + 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. |
| 69 | + - | |
| 70 | + Customers operating at high scale or near capacity may experience unexpected performance degradation, such as slow response times, background job queue spikes, elevated CPU usage, and increased MySQL load. Consider upgrading to {% ifversion ghes = 3.16 %}3.16{% endif %} {% ifversion ghes = 3.17 %}3.17{% endif %} with caution. |
0 commit comments