From 815e3d16db790f368b4ef42586f5a745373f636d Mon Sep 17 00:00:00 2001 From: Kamil Grzebien Date: Thu, 24 Feb 2022 10:56:58 +0000 Subject: [PATCH] Add Actions known issue after restoring (#25516) Co-authored-by: hubwriter --- data/release-notes/enterprise-server/3-4/0-rc1.yml | 1 + 1 file changed, 1 insertion(+) diff --git a/data/release-notes/enterprise-server/3-4/0-rc1.yml b/data/release-notes/enterprise-server/3-4/0-rc1.yml index be87c4de6912..7729660fd7f2 100644 --- a/data/release-notes/enterprise-server/3-4/0-rc1.yml +++ b/data/release-notes/enterprise-server/3-4/0-rc1.yml @@ -234,6 +234,7 @@ sections: - When "Users can search GitHub.com" is enabled with GitHub Connect, issues in private and internal repositories are not included in GitHub.com 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 needs to be restarted after restoring appliance from backup taken on a different host. deprecations: - heading: Deprecation of GitHub Enterprise Server 3.0