From 896387447bdcfd999117c7e2d9319eb5a241d982 Mon Sep 17 00:00:00 2001 From: Kensuke Nagae Date: Wed, 16 Oct 2024 21:39:32 +0900 Subject: [PATCH 1/2] Update release notes (#52713) --- data/release-notes/enterprise-server/3-13/0.yml | 2 ++ data/release-notes/enterprise-server/3-13/2.yml | 2 ++ data/release-notes/enterprise-server/3-14/0.yml | 4 +++- data/release-notes/enterprise-server/3-14/1.yml | 2 ++ data/release-notes/enterprise-server/3-14/2.yml | 2 ++ 5 files changed, 11 insertions(+), 1 deletion(-) diff --git a/data/release-notes/enterprise-server/3-13/0.yml b/data/release-notes/enterprise-server/3-13/0.yml index 9e61b5e3bb48..a2ffba974f15 100644 --- a/data/release-notes/enterprise-server/3-13/0.yml +++ b/data/release-notes/enterprise-server/3-13/0.yml @@ -185,6 +185,8 @@ sections: Memory utilization may increase after the upgrade. During periods of high traffic, interruptions in service may occur due to insufficient memory allocations for internal components. - | Following an upgrade, Elasticsearch search migrations are sometimes incorrectly reported as failing in the audit log, even though the migrations completed successfully. [Updated: 2024-08-02] + - | + Images embedded in wiki pages may stop rendering shortly after being published. [Updated: 2024-10-16] deprecations: # https://github.com/github/releases/issues/2732 diff --git a/data/release-notes/enterprise-server/3-13/2.yml b/data/release-notes/enterprise-server/3-13/2.yml index 68bb53c9cc1f..2709cd53e56b 100644 --- a/data/release-notes/enterprise-server/3-13/2.yml +++ b/data/release-notes/enterprise-server/3-13/2.yml @@ -169,3 +169,5 @@ sections: If a hotpatch upgrade requires the `haproxy-frontend` service to be restarted, the restart will hang if there are existing long-lived connections, such as browser web sockets or Git operations. No new connections will be accepted for up to 5 minutes. Any existing unfinished connections at this time will be disconnected. - | Following an upgrade, Elasticsearch search migrations are sometimes incorrectly reported as failing in the audit log, even though the migrations completed successfully. [Updated: 2024-08-02] + - | + Images embedded in wiki pages may stop rendering shortly after being published. [Updated: 2024-10-16] diff --git a/data/release-notes/enterprise-server/3-14/0.yml b/data/release-notes/enterprise-server/3-14/0.yml index 88083677c9be..aebcfe34f7a9 100644 --- a/data/release-notes/enterprise-server/3-14/0.yml +++ b/data/release-notes/enterprise-server/3-14/0.yml @@ -220,6 +220,8 @@ sections: 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. - | Following an upgrade, Elasticsearch search migrations are sometimes incorrectly reported as failing in the audit log, even though the migrations completed successfully. [Updated: 2024-09-27] + - | + Images embedded in wiki pages may stop rendering shortly after being published. [Updated: 2024-10-16] deprecations: - | @@ -230,4 +232,4 @@ sections: These release notes previously indicated as a known issue that on GitHub Enterprise Server 3.14.0 when log forwarding is enabled, some forwarded log entries may be duplicated. The fix for this problem was already included prior to the release of GitHub Enterprise Server 3.14.0. [Updated: 2024-09-16] - | - These release notes did not include a note for support of the `directories` key in `dependabot.yml` files. [Updated: 2024-10-07] \ No newline at end of file + These release notes did not include a note for support of the `directories` key in `dependabot.yml` files. [Updated: 2024-10-07] diff --git a/data/release-notes/enterprise-server/3-14/1.yml b/data/release-notes/enterprise-server/3-14/1.yml index 6d07e8a84b91..70c5bda5781a 100644 --- a/data/release-notes/enterprise-server/3-14/1.yml +++ b/data/release-notes/enterprise-server/3-14/1.yml @@ -72,3 +72,5 @@ sections: When restoring from a backup snapshot, a large number of `mapper_parsing_exception` errors may be displayed. - | Services may respond with a `503` status due to an out of date `haproxy` configuration. This can usually be resolved with a `ghe-config-apply` run. + - | + Images embedded in wiki pages may stop rendering shortly after being published. [Updated: 2024-10-16] diff --git a/data/release-notes/enterprise-server/3-14/2.yml b/data/release-notes/enterprise-server/3-14/2.yml index e569ef47c4ec..cd75c747023d 100644 --- a/data/release-notes/enterprise-server/3-14/2.yml +++ b/data/release-notes/enterprise-server/3-14/2.yml @@ -76,3 +76,5 @@ sections: When restoring from a backup snapshot, a large number of `mapper_parsing_exception` errors may be displayed. - | Services may respond with a `503` status due to an out of date `haproxy` configuration. This can usually be resolved with a `ghe-config-apply` run. + - | + Images embedded in wiki pages may stop rendering shortly after being published. [Updated: 2024-10-16] From 6893804c1496114a759d83bda46e8ba90eadac8f Mon Sep 17 00:00:00 2001 From: Sophie <29382425+sophietheking@users.noreply.github.com> Date: Wed, 16 Oct 2024 17:00:21 +0200 Subject: [PATCH 2/2] Adding a note to "Connecting an Azure subscription" (#52714) Co-authored-by: Ben Ahmady <32935794+subatoi@users.noreply.github.com> --- .../connecting-an-azure-subscription.md | 2 ++ 1 file changed, 2 insertions(+) diff --git a/content/billing/managing-the-plan-for-your-github-account/connecting-an-azure-subscription.md b/content/billing/managing-the-plan-for-your-github-account/connecting-an-azure-subscription.md index e16e7c20a25c..e29aa29ac058 100644 --- a/content/billing/managing-the-plan-for-your-github-account/connecting-an-azure-subscription.md +++ b/content/billing/managing-the-plan-for-your-github-account/connecting-an-azure-subscription.md @@ -74,6 +74,8 @@ For example, you link your Azure subscription to your organization {% ifversion * Alternatively, before following the instructions in this article, users who are not able to provide tenant-wide admin consent can work with an Azure AD global administrator to configure an admin consent workflow. See [User and admin consent in Azure Active Directory](https://learn.microsoft.com/en-us/azure/active-directory/manage-apps/user-admin-consent-overview#admin-consent-workflow) in Microsoft Docs. + >[!NOTE] If your tenant provides user consent settings, users included in those settings might not require admin consent to install {% data variables.product.company_short %}'s Subscription Permission Validation app. See [User consent](https://learn.microsoft.com/en-us/entra/identity/enterprise-apps/user-admin-consent-overview#user-consent) in Microsoft Docs. + * To select an Azure subscription from the list of available subscriptions, the user must be an owner of the Azure subscription. See [Assign a user as an administrator of an Azure subscription](https://learn.microsoft.com/azure/role-based-access-control/role-assignments-portal-subscription-admin) in Microsoft docs. * You must know your Azure subscription ID. See [Get subscription and tenant IDs in the Azure portal](https://learn.microsoft.com/en-us/azure/azure-portal/get-subscription-tenant-id) in the Microsoft Docs or [contact Azure support](https://azure.microsoft.com/support/).