From 219f46af814e992d02f095a413b5b72ed7eaefc1 Mon Sep 17 00:00:00 2001 From: Kamil Grzebien Date: Fri, 22 Apr 2022 15:14:06 +0200 Subject: [PATCH] Remove known issue description --- data/release-notes/enterprise-server/3-4/1.yml | 1 - data/release-notes/enterprise-server/3-4/2.yml | 1 - 2 files changed, 2 deletions(-) diff --git a/data/release-notes/enterprise-server/3-4/1.yml b/data/release-notes/enterprise-server/3-4/1.yml index 752f5a67ae..46aace2f09 100644 --- a/data/release-notes/enterprise-server/3-4/1.yml +++ b/data/release-notes/enterprise-server/3-4/1.yml @@ -46,7 +46,6 @@ sections: - When "Users can search GitHub.com" is enabled with {% data variables.product.prodname_github_connect %}, issues in private and internal repositories are not included in {% data variables.product.prodname_dotcom_the_website %} search results. - The {% data variables.product.prodname_registry %} 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 appliance from backup taken on a different host. - | When using SAML encrypted assertions with {% data variables.product.prodname_ghe_server %} 3.4.0 and 3.4.1, a new XML attribute `WantAssertionsEncrypted` in the `SPSSODescriptor` contains an invalid attribute for SAML metadata. IdPs that consume this SAML metadata endpoint may encounter errors when validating the SAML metadata XML schema. A fix will be available in the next patch release. [Updated: 2022-04-11] diff --git a/data/release-notes/enterprise-server/3-4/2.yml b/data/release-notes/enterprise-server/3-4/2.yml index 906e50aa6d..d4b2f95d8d 100644 --- a/data/release-notes/enterprise-server/3-4/2.yml +++ b/data/release-notes/enterprise-server/3-4/2.yml @@ -32,7 +32,6 @@ sections: - When "Users can search GitHub.com" is enabled with {% data variables.product.prodname_github_connect %}, issues in private and internal repositories are not included in {% data variables.product.prodname_dotcom_the_website %} search results. - The {% data variables.product.prodname_registry %} 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 appliance from backup taken on a different host. - | When using SAML encrypted assertions with {% data variables.product.prodname_ghe_server %} 3.4.0 and 3.4.1, a new XML attribute `WantAssertionsEncrypted` in the `SPSSODescriptor` contains an invalid attribute for SAML metadata. IdPs that consume this SAML metadata endpoint may encounter errors when validating the SAML metadata XML schema. A fix will be available in the next patch release. [Updated: 2022-04-11]