From b372bd687d8b17de065dcfd9d84e3f522d2b0529 Mon Sep 17 00:00:00 2001 From: github-openapi-bot Date: Mon, 15 Aug 2022 15:13:42 -0700 Subject: [PATCH 1/4] Update OpenAPI Descriptions --- .../dereferenced/api.github.com.deref.json | 72 ++++++++++++++++++- 1 file changed, 70 insertions(+), 2 deletions(-) diff --git a/lib/rest/static/dereferenced/api.github.com.deref.json b/lib/rest/static/dereferenced/api.github.com.deref.json index 48d43958b3cd..16578a01865e 100644 --- a/lib/rest/static/dereferenced/api.github.com.deref.json +++ b/lib/rest/static/dereferenced/api.github.com.deref.json @@ -242553,8 +242553,8 @@ "examples": { "default": { "value": { - "repository_id": 1, - "ref": "main" + "ref": "main", + "machine": "standardLinux32gb" } } } @@ -248508,6 +248508,74 @@ } } }, + "400": { + "description": "Bad Request", + "content": { + "application/json": { + "schema": { + "title": "Basic Error", + "description": "Basic Error", + "type": "object", + "properties": { + "message": { + "type": "string" + }, + "documentation_url": { + "type": "string" + }, + "url": { + "type": "string" + }, + "status": { + "type": "string" + } + } + } + }, + "application/scim+json": { + "schema": { + "title": "Scim Error", + "description": "Scim Error", + "type": "object", + "properties": { + "message": { + "type": [ + "string", + "null" + ] + }, + "documentation_url": { + "type": [ + "string", + "null" + ] + }, + "detail": { + "type": [ + "string", + "null" + ] + }, + "status": { + "type": "integer" + }, + "scimType": { + "type": [ + "string", + "null" + ] + }, + "schemas": { + "type": "array", + "items": { + "type": "string" + } + } + } + } + } + } + }, "401": { "description": "Requires authentication", "content": { From cb641b3d8d7eb1baa4673ab49907d25139020f78 Mon Sep 17 00:00:00 2001 From: github-openapi-bot Date: Mon, 15 Aug 2022 22:29:49 +0000 Subject: [PATCH 2/4] Add decorated OpenAPI schema files --- lib/rest/static/decorated/api.github.com.json | 12 ++++++++---- 1 file changed, 8 insertions(+), 4 deletions(-) diff --git a/lib/rest/static/decorated/api.github.com.json b/lib/rest/static/decorated/api.github.com.json index 53593a1be67b..e6a833cb93fa 100644 --- a/lib/rest/static/decorated/api.github.com.json +++ b/lib/rest/static/decorated/api.github.com.json @@ -182922,8 +182922,8 @@ "description": "Example 1: Status Code 201", "acceptHeader": "application/vnd.github.v3+json", "bodyParameters": { - "repository_id": 1, - "ref": "main" + "ref": "main", + "machine": "standardLinux32gb" }, "parameters": { "owner": "OWNER", @@ -185903,8 +185903,8 @@ "description": "Example 2: Status Code 202", "acceptHeader": "application/vnd.github.v3+json", "bodyParameters": { - "repository_id": 1, - "ref": "main" + "ref": "main", + "machine": "standardLinux32gb" }, "parameters": { "owner": "OWNER", @@ -188889,6 +188889,10 @@ "httpStatusCode": "202", "description": "

Response when the codespace creation partially failed but is being retried in the background

" }, + { + "httpStatusCode": "400", + "description": "

Bad Request

" + }, { "httpStatusCode": "401", "description": "

Requires authentication

" From ba2391b15965450c6afbb8e1fe8dcc569be538b3 Mon Sep 17 00:00:00 2001 From: Ben Allen Date: Tue, 16 Aug 2022 11:31:12 -0400 Subject: [PATCH 3/4] Improve accessibility settings documentation (#29847) --- .../managing-accessibility-settings.md | 15 ++++++++------- 1 file changed, 8 insertions(+), 7 deletions(-) diff --git a/content/account-and-profile/setting-up-and-managing-your-personal-account-on-github/managing-personal-account-settings/managing-accessibility-settings.md b/content/account-and-profile/setting-up-and-managing-your-personal-account-on-github/managing-personal-account-settings/managing-accessibility-settings.md index 98dbc8ab8b73..fef42cd599de 100644 --- a/content/account-and-profile/setting-up-and-managing-your-personal-account-on-github/managing-personal-account-settings/managing-accessibility-settings.md +++ b/content/account-and-profile/setting-up-and-managing-your-personal-account-on-github/managing-personal-account-settings/managing-accessibility-settings.md @@ -12,7 +12,7 @@ miniTocMaxHeadingLevel: 3 ## About accessibility settings -To accommodate your vision, hearing, motor, cognitive, or learning needs, you can customize the user interface for {% data variables.product.product_location %}. +To create an experience on {% ifversion fpt or ghec or ghes %}{% data variables.product.product_location %}{% elsif ghae %}{% data variables.product.product_name %}{% endif %} that fits your needs, you can customize the user interface. Accessibility settings can be essential for people with disabilities, but can be useful to anyone. For example, customization of keyboard shortcuts is essential to people who navigate using voice control, but can be useful to anyone when a keyboard shortcut for {% data variables.product.product_name %} clashes with another application shortcut. ## Managing accessibility settings @@ -20,7 +20,7 @@ You can decide whether you want to use some or all keyboard shortcuts on {% ifve ### Managing keyboard shortcuts -You can perform actions across the {% data variables.product.product_name %} website without using your mouse by using your keyboard instead. Keyboard shortcuts can be useful to save time for some people, but may interfere with accessibility if you don't intend to use the shortcuts. +You can perform actions across the {% data variables.product.product_name %} website by using your keyboard alone. Keyboard shortcuts can be useful to save time, but can be activated accidentally or interfere with assistive technology. By default, all keyboard shortcuts are enabled on {% data variables.product.product_name %}. For more information, see "[Keyboard shortcuts](/get-started/using-github/keyboard-shortcuts)." @@ -28,16 +28,17 @@ By default, all keyboard shortcuts are enabled on {% data variables.product.prod {% data reusables.user-settings.accessibility_settings %} 1. Under "Keyboard shortcuts", manage settings for your keyboard shortcuts. - - Optionally, to disable or enable shortcut keys that don't use modifiers keys like Control or Command, under "General", deselect **Character keys**. If you disable character keys, you may still be able to trigger shortcuts for your web browser, and you can still trigger shortcuts for {% data variables.product.product_name %} that use a modifier key. + - To disable shortcut keys that don't use modifiers keys like Control or Command, under "General", deselect **Character keys**. + - If you disable character keys, you may still be able to trigger shortcuts for your web browser, and you can still trigger shortcuts for {% data variables.product.product_name %} that use a modifier key. {%- ifversion command-palette %} - - Optionally, to customize the keyboard shortcuts for triggering the command palette, under "Command palette", use the drop-down menus to choose a keyboard shortcut. For more information, see "[{% data variables.product.company_short %} Command Palette](/get-started/using-github/github-command-palette)." + - To customize the keyboard shortcuts for triggering the command palette, under "Command palette", use the drop-down menus to choose a keyboard shortcut. For more information, see "[{% data variables.product.company_short %} Command Palette](/get-started/using-github/github-command-palette)." {%- endif %} {% ifversion motion-management %} ### Managing motion -You can control how {% data variables.product.product_name %} displays animated images. +You can control how {% data variables.product.product_name %} displays animated _.gif_ images. By default, {% data variables.product.product_name %} syncs with your system-level preference for reduced motion. For more information, see the documentation or settings for your operating system. @@ -45,6 +46,6 @@ By default, {% data variables.product.product_name %} syncs with your system-lev {% data reusables.user-settings.accessibility_settings %} 1. Under "Motion", manage settings for motion. - - Optionally, to control how {% data variables.product.product_name %} displays animaged images, under "Autoplay animated images", select **Sync with system**, **Enabled**, or **Disabled**. + - To control how {% data variables.product.product_name %} displays animated images, under "Autoplay animated images", select **Sync with system**, **Enabled**, or **Disabled**. -{% endif %} \ No newline at end of file +{% endif %} From 058b1adf960efd5c2fb8166d8dfbb0424a5c9191 Mon Sep 17 00:00:00 2001 From: Mariam <15mariams@github.com> Date: Tue, 16 Aug 2022 08:41:17 -0700 Subject: [PATCH 4/4] Known issue for GHAS secret scanning customers who skip GHES 3.4 upgrade (#29871) --- .../release-notes/enterprise-server/3-2/0.yml | 1 + .../release-notes/enterprise-server/3-2/1.yml | 1 + .../enterprise-server/3-2/10.yml | 1 + .../enterprise-server/3-2/11.yml | 1 + .../enterprise-server/3-2/12.yml | 1 + .../enterprise-server/3-2/13.yml | 1 + .../enterprise-server/3-2/14.yml | 1 + .../enterprise-server/3-2/15.yml | 1 + .../enterprise-server/3-2/16.yml | 9 ++++++ .../release-notes/enterprise-server/3-2/2.yml | 1 + .../release-notes/enterprise-server/3-2/3.yml | 1 + .../release-notes/enterprise-server/3-2/4.yml | 1 + .../release-notes/enterprise-server/3-2/5.yml | 1 + .../release-notes/enterprise-server/3-2/6.yml | 1 + .../release-notes/enterprise-server/3-2/7.yml | 1 + .../release-notes/enterprise-server/3-2/8.yml | 1 + .../release-notes/enterprise-server/3-2/9.yml | 1 + .../release-notes/enterprise-server/3-3/0.yml | 2 +- .../release-notes/enterprise-server/3-3/1.yml | 1 + .../enterprise-server/3-3/10.yml | 1 + .../enterprise-server/3-3/11.yml | 11 +++++++ .../release-notes/enterprise-server/3-3/2.yml | 1 + .../release-notes/enterprise-server/3-3/3.yml | 1 + .../release-notes/enterprise-server/3-3/4.yml | 1 + .../release-notes/enterprise-server/3-3/5.yml | 1 + .../release-notes/enterprise-server/3-3/6.yml | 1 + .../release-notes/enterprise-server/3-3/7.yml | 1 + .../release-notes/enterprise-server/3-3/8.yml | 1 + .../release-notes/enterprise-server/3-3/9.yml | 1 + .../release-notes/enterprise-server/3-4/0.yml | 2 +- .../release-notes/enterprise-server/3-4/1.yml | 2 +- .../release-notes/enterprise-server/3-4/2.yml | 2 +- .../release-notes/enterprise-server/3-4/3.yml | 1 + .../release-notes/enterprise-server/3-4/4.yml | 1 + .../release-notes/enterprise-server/3-4/5.yml | 1 + .../release-notes/enterprise-server/3-4/6.yml | 3 +- .../release-notes/enterprise-server/3-5/0.yml | 1 + .../release-notes/enterprise-server/3-5/1.yml | 3 +- .../release-notes/enterprise-server/3-5/2.yml | 1 + .../release-notes/enterprise-server/3-5/3.yml | 29 ++++++++++--------- .../enterprise-server/3-6/0-rc1.yml | 1 + .../ghas-3.4-secret-scanning-known-issue.md | 16 ++++++++++ 42 files changed, 91 insertions(+), 20 deletions(-) create mode 100644 data/reusables/release-notes/ghas-3.4-secret-scanning-known-issue.md diff --git a/data/release-notes/enterprise-server/3-2/0.yml b/data/release-notes/enterprise-server/3-2/0.yml index 36f6c4c82cb3..ba34f7a61d3e 100644 --- a/data/release-notes/enterprise-server/3-2/0.yml +++ b/data/release-notes/enterprise-server/3-2/0.yml @@ -273,6 +273,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. + - '{% data reusables.release-notes.ghas-3.4-secret-scanning-known-issue %}' deprecations: - heading: Deprecation of GitHub Enterprise Server 2.21 diff --git a/data/release-notes/enterprise-server/3-2/1.yml b/data/release-notes/enterprise-server/3-2/1.yml index 9b770774ce5d..8396e4236a1e 100644 --- a/data/release-notes/enterprise-server/3-2/1.yml +++ b/data/release-notes/enterprise-server/3-2/1.yml @@ -25,3 +25,4 @@ 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. + - '{% data reusables.release-notes.ghas-3.4-secret-scanning-known-issue %}' \ No newline at end of file diff --git a/data/release-notes/enterprise-server/3-2/10.yml b/data/release-notes/enterprise-server/3-2/10.yml index 7065df1d894f..45ddff2f8196 100644 --- a/data/release-notes/enterprise-server/3-2/10.yml +++ b/data/release-notes/enterprise-server/3-2/10.yml @@ -13,3 +13,4 @@ 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. + - '{% data reusables.release-notes.ghas-3.4-secret-scanning-known-issue %}' \ No newline at end of file diff --git a/data/release-notes/enterprise-server/3-2/11.yml b/data/release-notes/enterprise-server/3-2/11.yml index 5e7f5dc02ca6..8e12cf93c0d6 100644 --- a/data/release-notes/enterprise-server/3-2/11.yml +++ b/data/release-notes/enterprise-server/3-2/11.yml @@ -41,3 +41,4 @@ 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. + - '{% data reusables.release-notes.ghas-3.4-secret-scanning-known-issue %}' \ No newline at end of file diff --git a/data/release-notes/enterprise-server/3-2/12.yml b/data/release-notes/enterprise-server/3-2/12.yml index 471d33f78082..61e2d9223866 100644 --- a/data/release-notes/enterprise-server/3-2/12.yml +++ b/data/release-notes/enterprise-server/3-2/12.yml @@ -21,3 +21,4 @@ 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. + - '{% data reusables.release-notes.ghas-3.4-secret-scanning-known-issue %}' \ No newline at end of file diff --git a/data/release-notes/enterprise-server/3-2/13.yml b/data/release-notes/enterprise-server/3-2/13.yml index 1fa2cd84780a..dab4acdb618d 100644 --- a/data/release-notes/enterprise-server/3-2/13.yml +++ b/data/release-notes/enterprise-server/3-2/13.yml @@ -25,3 +25,4 @@ 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. + - '{% data reusables.release-notes.ghas-3.4-secret-scanning-known-issue %}' \ No newline at end of file diff --git a/data/release-notes/enterprise-server/3-2/14.yml b/data/release-notes/enterprise-server/3-2/14.yml index 5f78b82a2ddc..3fb623097bfb 100644 --- a/data/release-notes/enterprise-server/3-2/14.yml +++ b/data/release-notes/enterprise-server/3-2/14.yml @@ -20,3 +20,4 @@ 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. + - '{% data reusables.release-notes.ghas-3.4-secret-scanning-known-issue %}' \ No newline at end of file diff --git a/data/release-notes/enterprise-server/3-2/15.yml b/data/release-notes/enterprise-server/3-2/15.yml index 436857b4343d..49fa7789c6a3 100644 --- a/data/release-notes/enterprise-server/3-2/15.yml +++ b/data/release-notes/enterprise-server/3-2/15.yml @@ -17,3 +17,4 @@ 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. + - '{% data reusables.release-notes.ghas-3.4-secret-scanning-known-issue %}' \ No newline at end of file diff --git a/data/release-notes/enterprise-server/3-2/16.yml b/data/release-notes/enterprise-server/3-2/16.yml index 794444dddb4c..c46d272363b3 100644 --- a/data/release-notes/enterprise-server/3-2/16.yml +++ b/data/release-notes/enterprise-server/3-2/16.yml @@ -15,3 +15,12 @@ sections: - The `ghe-set-password` command-line utility starts required services automatically when the instance is booted in recovery mode. - Metrics for `aqueduct` background processes are gathered for Collectd forwarding and display in the Management Console. - The location of the database migration and configuration run log, `/data/user/common/ghe-config.log`, is now displayed on the page that details a migration in progress. + known_issues: + - On a freshly set up {% data variables.product.prodname_ghe_server %} instance without any users, an attacker could create the first admin user. + - Custom firewall rules are removed during the upgrade process. + - Git LFS tracked files [uploaded through the web interface](https://github.com/blog/2105-upload-files-to-your-repositories) are incorrectly added directly to the repository. + - Issues cannot be closed if they contain a permalink to a blob in the same repository, where the blob's file path is longer than 255 characters. + - 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. + - '{% data reusables.release-notes.ghas-3.4-secret-scanning-known-issue %}' \ No newline at end of file diff --git a/data/release-notes/enterprise-server/3-2/2.yml b/data/release-notes/enterprise-server/3-2/2.yml index e15b7067ef9b..536365cd7deb 100644 --- a/data/release-notes/enterprise-server/3-2/2.yml +++ b/data/release-notes/enterprise-server/3-2/2.yml @@ -20,3 +20,4 @@ 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. + - '{% data reusables.release-notes.ghas-3.4-secret-scanning-known-issue %}' \ No newline at end of file diff --git a/data/release-notes/enterprise-server/3-2/3.yml b/data/release-notes/enterprise-server/3-2/3.yml index 5c1b3f7a323b..1d68a8ef6525 100644 --- a/data/release-notes/enterprise-server/3-2/3.yml +++ b/data/release-notes/enterprise-server/3-2/3.yml @@ -28,3 +28,4 @@ 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. + - '{% data reusables.release-notes.ghas-3.4-secret-scanning-known-issue %}' \ No newline at end of file diff --git a/data/release-notes/enterprise-server/3-2/4.yml b/data/release-notes/enterprise-server/3-2/4.yml index f3852870df9b..d35854b8764b 100644 --- a/data/release-notes/enterprise-server/3-2/4.yml +++ b/data/release-notes/enterprise-server/3-2/4.yml @@ -27,3 +27,4 @@ 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. + - '{% data reusables.release-notes.ghas-3.4-secret-scanning-known-issue %}' \ No newline at end of file diff --git a/data/release-notes/enterprise-server/3-2/5.yml b/data/release-notes/enterprise-server/3-2/5.yml index 76c2d66d0863..97310e09cd90 100644 --- a/data/release-notes/enterprise-server/3-2/5.yml +++ b/data/release-notes/enterprise-server/3-2/5.yml @@ -25,3 +25,4 @@ 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. + - '{% data reusables.release-notes.ghas-3.4-secret-scanning-known-issue %}' \ No newline at end of file diff --git a/data/release-notes/enterprise-server/3-2/6.yml b/data/release-notes/enterprise-server/3-2/6.yml index 0d23f8ad32e2..257725162c0d 100644 --- a/data/release-notes/enterprise-server/3-2/6.yml +++ b/data/release-notes/enterprise-server/3-2/6.yml @@ -11,3 +11,4 @@ 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. + - '{% data reusables.release-notes.ghas-3.4-secret-scanning-known-issue %}' \ No newline at end of file diff --git a/data/release-notes/enterprise-server/3-2/7.yml b/data/release-notes/enterprise-server/3-2/7.yml index 0781b380fb32..95b7aea41c68 100644 --- a/data/release-notes/enterprise-server/3-2/7.yml +++ b/data/release-notes/enterprise-server/3-2/7.yml @@ -20,3 +20,4 @@ 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. + - '{% data reusables.release-notes.ghas-3.4-secret-scanning-known-issue %}' \ No newline at end of file diff --git a/data/release-notes/enterprise-server/3-2/8.yml b/data/release-notes/enterprise-server/3-2/8.yml index 1d786a4e5425..02bd8c1b3176 100644 --- a/data/release-notes/enterprise-server/3-2/8.yml +++ b/data/release-notes/enterprise-server/3-2/8.yml @@ -23,3 +23,4 @@ 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. + - '{% data reusables.release-notes.ghas-3.4-secret-scanning-known-issue %}' \ No newline at end of file diff --git a/data/release-notes/enterprise-server/3-2/9.yml b/data/release-notes/enterprise-server/3-2/9.yml index 2fbe4fec9341..a096c338eddb 100644 --- a/data/release-notes/enterprise-server/3-2/9.yml +++ b/data/release-notes/enterprise-server/3-2/9.yml @@ -17,3 +17,4 @@ 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. + - '{% data reusables.release-notes.ghas-3.4-secret-scanning-known-issue %}' \ No newline at end of file diff --git a/data/release-notes/enterprise-server/3-3/0.yml b/data/release-notes/enterprise-server/3-3/0.yml index 5081ac623600..f321bb7caa44 100644 --- a/data/release-notes/enterprise-server/3-3/0.yml +++ b/data/release-notes/enterprise-server/3-3/0.yml @@ -253,7 +253,7 @@ sections: - Resource limits that are specific to processing pre-receive hooks may cause some pre-receive hooks to fail. - '{% data variables.product.prodname_actions %} storage settings cannot be validated and saved in the {% data variables.enterprise.management_console %} when "Force Path Style" is selected, and must instead be configured with the `ghe-actions-precheck` command line utility.' - '{% data variables.product.prodname_ghe_server %} 3.3 instances installed on Azure and provisioned with 32+ CPU cores would fail to launch, due to a bug present in the current Linux kernel. [Updated: 2022-04-08]' - + - '{% data reusables.release-notes.ghas-3.4-secret-scanning-known-issue %}' deprecations: - heading: Deprecation of GitHub Enterprise Server 2.22 notes: diff --git a/data/release-notes/enterprise-server/3-3/1.yml b/data/release-notes/enterprise-server/3-3/1.yml index 20fce5b88906..13b94fe0b115 100644 --- a/data/release-notes/enterprise-server/3-3/1.yml +++ b/data/release-notes/enterprise-server/3-3/1.yml @@ -14,3 +14,4 @@ sections: - Resource limits that are specific to processing pre-receive hooks may cause some pre-receive hooks to fail. - '{% data variables.product.prodname_actions %} storage settings cannot be validated and saved in the {% data variables.enterprise.management_console %} when "Force Path Style" is selected, and must instead be configured with the `ghe-actions-precheck` command line utility.' - '{% data variables.product.prodname_ghe_server %} 3.3 instances installed on Azure and provisioned with 32+ CPU cores would fail to launch, due to a bug present in the current Linux kernel. [Updated: 2022-04-08]' + - '{% data reusables.release-notes.ghas-3.4-secret-scanning-known-issue %}' \ No newline at end of file diff --git a/data/release-notes/enterprise-server/3-3/10.yml b/data/release-notes/enterprise-server/3-3/10.yml index b257e740b0ce..92fafb6e05c9 100644 --- a/data/release-notes/enterprise-server/3-3/10.yml +++ b/data/release-notes/enterprise-server/3-3/10.yml @@ -19,3 +19,4 @@ sections: - 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. - '{% data variables.product.prodname_actions %} storage settings cannot be validated and saved in the {% data variables.enterprise.management_console %} when "Force Path Style" is selected, and must instead be configured with the `ghe-actions-precheck` command line utility.' + - '{% data reusables.release-notes.ghas-3.4-secret-scanning-known-issue %}' \ No newline at end of file diff --git a/data/release-notes/enterprise-server/3-3/11.yml b/data/release-notes/enterprise-server/3-3/11.yml index 53969bede579..33c76ba28028 100644 --- a/data/release-notes/enterprise-server/3-3/11.yml +++ b/data/release-notes/enterprise-server/3-3/11.yml @@ -19,3 +19,14 @@ sections: - The `ghe-set-password` command-line utility starts required services automatically when the instance is booted in recovery mode. - Metrics for `aqueduct` background processes are gathered for Collectd forwarding and display in the Management Console. - The location of the database migration and configuration run log, `/data/user/common/ghe-config.log`, is now displayed on the page that details a migration in progress. + known_issues: + - After upgrading to {% data variables.product.prodname_ghe_server %} 3.3, {% data variables.product.prodname_actions %} may fail to start automatically. To resolve this issue, connect to the appliance via SSH and run the `ghe-actions-start` command. + - On a freshly set up {% data variables.product.prodname_ghe_server %} instance without any users, an attacker could create the first admin user. + - Custom firewall rules are removed during the upgrade process. + - Git LFS tracked files [uploaded through the web interface](https://github.com/blog/2105-upload-files-to-your-repositories) are incorrectly added directly to the repository. + - Issues cannot be closed if they contain a permalink to a blob in the same repository, where the blob's file path is longer than 255 characters. + - 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. + - '{% data variables.product.prodname_actions %} storage settings cannot be validated and saved in the {% data variables.enterprise.management_console %} when "Force Path Style" is selected, and must instead be configured with the `ghe-actions-precheck` command line utility.' + - '{% data reusables.release-notes.ghas-3.4-secret-scanning-known-issue %}' \ No newline at end of file diff --git a/data/release-notes/enterprise-server/3-3/2.yml b/data/release-notes/enterprise-server/3-3/2.yml index a74a6e856705..1bdf20667a50 100644 --- a/data/release-notes/enterprise-server/3-3/2.yml +++ b/data/release-notes/enterprise-server/3-3/2.yml @@ -29,3 +29,4 @@ sections: - Resource limits that are specific to processing pre-receive hooks may cause some pre-receive hooks to fail. - '{% data variables.product.prodname_actions %} storage settings cannot be validated and saved in the {% data variables.enterprise.management_console %} when "Force Path Style" is selected, and must instead be configured with the `ghe-actions-precheck` command line utility.' - '{% data variables.product.prodname_ghe_server %} 3.3 instances installed on Azure and provisioned with 32+ CPU cores would fail to launch, due to a bug present in the current Linux kernel. [Updated: 2022-04-08]' + - '{% data reusables.release-notes.ghas-3.4-secret-scanning-known-issue %}' \ No newline at end of file diff --git a/data/release-notes/enterprise-server/3-3/3.yml b/data/release-notes/enterprise-server/3-3/3.yml index b75c737e370e..21fe3e58ff9c 100644 --- a/data/release-notes/enterprise-server/3-3/3.yml +++ b/data/release-notes/enterprise-server/3-3/3.yml @@ -27,3 +27,4 @@ sections: - Resource limits that are specific to processing pre-receive hooks may cause some pre-receive hooks to fail. - '{% data variables.product.prodname_actions %} storage settings cannot be validated and saved in the {% data variables.enterprise.management_console %} when "Force Path Style" is selected, and must instead be configured with the `ghe-actions-precheck` command line utility.' - '{% data variables.product.prodname_ghe_server %} 3.3 instances installed on Azure and provisioned with 32+ CPU cores would fail to launch, due to a bug present in the current Linux kernel. [Updated: 2022-04-08]' + - '{% data reusables.release-notes.ghas-3.4-secret-scanning-known-issue %}' \ No newline at end of file diff --git a/data/release-notes/enterprise-server/3-3/4.yml b/data/release-notes/enterprise-server/3-3/4.yml index f27eb2ade717..c6e0ae3885c6 100644 --- a/data/release-notes/enterprise-server/3-3/4.yml +++ b/data/release-notes/enterprise-server/3-3/4.yml @@ -22,3 +22,4 @@ sections: - Resource limits that are specific to processing pre-receive hooks may cause some pre-receive hooks to fail. - '{% data variables.product.prodname_actions %} storage settings cannot be validated and saved in the {% data variables.enterprise.management_console %} when "Force Path Style" is selected, and must instead be configured with the `ghe-actions-precheck` command line utility.' - '{% data variables.product.prodname_ghe_server %} 3.3 instances installed on Azure and provisioned with 32+ CPU cores would fail to launch, due to a bug present in the current Linux kernel. [Updated: 2022-04-08]' + - '{% data reusables.release-notes.ghas-3.4-secret-scanning-known-issue %}' \ No newline at end of file diff --git a/data/release-notes/enterprise-server/3-3/5.yml b/data/release-notes/enterprise-server/3-3/5.yml index 5040c9ba66f4..7e03cef53692 100644 --- a/data/release-notes/enterprise-server/3-3/5.yml +++ b/data/release-notes/enterprise-server/3-3/5.yml @@ -16,3 +16,4 @@ sections: - Resource limits that are specific to processing pre-receive hooks may cause some pre-receive hooks to fail. - '{% data variables.product.prodname_actions %} storage settings cannot be validated and saved in the {% data variables.enterprise.management_console %} when "Force Path Style" is selected, and must instead be configured with the `ghe-actions-precheck` command line utility.' - '{% data variables.product.prodname_ghe_server %} 3.3 instances installed on Azure and provisioned with 32+ CPU cores would fail to launch, due to a bug present in the current Linux kernel. [Updated: 2022-04-08]' + - '{% data reusables.release-notes.ghas-3.4-secret-scanning-known-issue %}' \ No newline at end of file diff --git a/data/release-notes/enterprise-server/3-3/6.yml b/data/release-notes/enterprise-server/3-3/6.yml index 34b5d51e6f9c..49772b97bfcd 100644 --- a/data/release-notes/enterprise-server/3-3/6.yml +++ b/data/release-notes/enterprise-server/3-3/6.yml @@ -47,3 +47,4 @@ sections: - Resource limits that are specific to processing pre-receive hooks may cause some pre-receive hooks to fail. - '{% data variables.product.prodname_actions %} storage settings cannot be validated and saved in the {% data variables.enterprise.management_console %} when "Force Path Style" is selected, and must instead be configured with the `ghe-actions-precheck` command line utility.' - '{% data variables.product.prodname_ghe_server %} 3.3 instances installed on Azure and provisioned with 32+ CPU cores would fail to launch, due to a bug present in the current Linux kernel. [Updated: 2022-04-08]' + - '{% data reusables.release-notes.ghas-3.4-secret-scanning-known-issue %}' \ No newline at end of file diff --git a/data/release-notes/enterprise-server/3-3/7.yml b/data/release-notes/enterprise-server/3-3/7.yml index 77f06ecc5338..c499e7b7b4dd 100644 --- a/data/release-notes/enterprise-server/3-3/7.yml +++ b/data/release-notes/enterprise-server/3-3/7.yml @@ -29,3 +29,4 @@ sections: - Resource limits that are specific to processing pre-receive hooks may cause some pre-receive hooks to fail. - '{% data variables.product.prodname_actions %} storage settings cannot be validated and saved in the {% data variables.enterprise.management_console %} when "Force Path Style" is selected, and must instead be configured with the `ghe-actions-precheck` command line utility.' - '{% data variables.product.prodname_ghe_server %} 3.3 instances installed on Azure and provisioned with 32+ CPU cores would fail to launch, due to a bug present in the current Linux kernel. [Updated: 2022-04-08]' + - '{% data reusables.release-notes.ghas-3.4-secret-scanning-known-issue %}' \ No newline at end of file diff --git a/data/release-notes/enterprise-server/3-3/8.yml b/data/release-notes/enterprise-server/3-3/8.yml index ca6ef49b93c1..0aa6a32d8f25 100644 --- a/data/release-notes/enterprise-server/3-3/8.yml +++ b/data/release-notes/enterprise-server/3-3/8.yml @@ -31,3 +31,4 @@ sections: - 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. - '{% data variables.product.prodname_actions %} storage settings cannot be validated and saved in the {% data variables.enterprise.management_console %} when "Force Path Style" is selected, and must instead be configured with the `ghe-actions-precheck` command line utility.' + - '{% data reusables.release-notes.ghas-3.4-secret-scanning-known-issue %}' \ No newline at end of file diff --git a/data/release-notes/enterprise-server/3-3/9.yml b/data/release-notes/enterprise-server/3-3/9.yml index d7f19e7ced2b..02e461e5eac2 100644 --- a/data/release-notes/enterprise-server/3-3/9.yml +++ b/data/release-notes/enterprise-server/3-3/9.yml @@ -23,3 +23,4 @@ sections: - 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. - '{% data variables.product.prodname_actions %} storage settings cannot be validated and saved in the {% data variables.enterprise.management_console %} when "Force Path Style" is selected, and must instead be configured with the `ghe-actions-precheck` command line utility.' + - '{% data reusables.release-notes.ghas-3.4-secret-scanning-known-issue %}' \ No newline at end of file diff --git a/data/release-notes/enterprise-server/3-4/0.yml b/data/release-notes/enterprise-server/3-4/0.yml index 20b3b3d01981..4e3db0e1d58f 100644 --- a/data/release-notes/enterprise-server/3-4/0.yml +++ b/data/release-notes/enterprise-server/3-4/0.yml @@ -252,7 +252,7 @@ sections: To work around this problem, you can take one of the two following actions. - Reconfigure the IdP by uploading a static copy of the SAML metadata without the `WantAssertionsEncrypted` attribute. - Copy the SAML metadata, remove `WantAssertionsEncrypted` attribute, host it on a web server, and reconfigure the IdP to point to that URL. - + - '{% data reusables.release-notes.ghas-3.4-secret-scanning-known-issue %}' deprecations: - heading: Deprecation of GitHub Enterprise Server 3.0 notes: diff --git a/data/release-notes/enterprise-server/3-4/1.yml b/data/release-notes/enterprise-server/3-4/1.yml index 69613777acd7..85b5feeb650f 100644 --- a/data/release-notes/enterprise-server/3-4/1.yml +++ b/data/release-notes/enterprise-server/3-4/1.yml @@ -54,7 +54,7 @@ sections: To work around this problem, you can take one of the two following actions. - Reconfigure the IdP by uploading a static copy of the SAML metadata without the `WantAssertionsEncrypted` attribute. - Copy the SAML metadata, remove `WantAssertionsEncrypted` attribute, host it on a web server, and reconfigure the IdP to point to that URL. - + - '{% data reusables.release-notes.ghas-3.4-secret-scanning-known-issue %}' deprecations: - heading: Deprecation of GitHub Enterprise Server 3.0 notes: diff --git a/data/release-notes/enterprise-server/3-4/2.yml b/data/release-notes/enterprise-server/3-4/2.yml index 97fd1a49ef1e..be2036c2f41d 100644 --- a/data/release-notes/enterprise-server/3-4/2.yml +++ b/data/release-notes/enterprise-server/3-4/2.yml @@ -30,7 +30,7 @@ sections: - | After registering a self-hosted runner with the `--ephemeral` parameter on more than one level (for example, both enterprise and organization), the runner may get stuck in an idle state and require re-registration. [Updated: 2022-06-17] - After upgrading to {% data variables.product.prodname_ghe_server %} 3.4, releases may appear to be missing from repositories. This can occur when the required Elasticsearch index migrations have not successfully completed. - + - '{% data reusables.release-notes.ghas-3.4-secret-scanning-known-issue %}' deprecations: - heading: Deprecation of GitHub Enterprise Server 3.0 notes: diff --git a/data/release-notes/enterprise-server/3-4/3.yml b/data/release-notes/enterprise-server/3-4/3.yml index 8903216825fb..a15e8170baec 100644 --- a/data/release-notes/enterprise-server/3-4/3.yml +++ b/data/release-notes/enterprise-server/3-4/3.yml @@ -37,3 +37,4 @@ sections: - | After registering a self-hosted runner with the `--ephemeral` parameter on more than one level (for example, both enterprise and organization), the runner may get stuck in an idle state and require re-registration. [Updated: 2022-06-17] - After upgrading to {% data variables.product.prodname_ghe_server %} 3.4 releases may appear to be missing from repositories. This can occur when the required Elasticsearch index migrations have not successfully completed. + - '{% data reusables.release-notes.ghas-3.4-secret-scanning-known-issue %}' \ No newline at end of file diff --git a/data/release-notes/enterprise-server/3-4/4.yml b/data/release-notes/enterprise-server/3-4/4.yml index 89ec1973d0a1..ebf7d6769211 100644 --- a/data/release-notes/enterprise-server/3-4/4.yml +++ b/data/release-notes/enterprise-server/3-4/4.yml @@ -28,3 +28,4 @@ sections: - | After registering a self-hosted runner with the `--ephemeral` parameter on more than one level (for example, both enterprise and organization), the runner may get stuck in an idle state and require re-registration. [Updated: 2022-06-17] - After upgrading to {% data variables.product.prodname_ghe_server %} 3.4, releases may appear to be missing from repositories. This can occur when the required Elasticsearch index migrations have not successfully completed. + - '{% data reusables.release-notes.ghas-3.4-secret-scanning-known-issue %}' \ No newline at end of file diff --git a/data/release-notes/enterprise-server/3-4/5.yml b/data/release-notes/enterprise-server/3-4/5.yml index e12564652c18..f72408ff77eb 100644 --- a/data/release-notes/enterprise-server/3-4/5.yml +++ b/data/release-notes/enterprise-server/3-4/5.yml @@ -27,3 +27,4 @@ sections: - | After registering a self-hosted runner with the `--ephemeral` parameter on more than one level (for example, both enterprise and organization), the runner may get stuck in an idle state and require re-registration. - After upgrading to {% data variables.product.prodname_ghe_server %} 3.4, releases may appear to be missing from repositories. This can occur when the required Elasticsearch index migrations have not successfully completed. + - '{% data reusables.release-notes.ghas-3.4-secret-scanning-known-issue %}' \ No newline at end of file diff --git a/data/release-notes/enterprise-server/3-4/6.yml b/data/release-notes/enterprise-server/3-4/6.yml index 7b9ed1658c01..e9bd1dcf8f95 100644 --- a/data/release-notes/enterprise-server/3-4/6.yml +++ b/data/release-notes/enterprise-server/3-4/6.yml @@ -28,5 +28,6 @@ sections: - 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. - | - After registering a self-hosted runner with the `--ephemeral` parameter on more than one level (for example, both enterprise and organization), the runner may get stuck in an idle state and require re-registration. + After registering a self-hosted runner with the `--ephemeral` parameter on more than one level (for example, both enterprise and organization), the runner may get stuck in an idle state and require re-registration. [Updated: 2022-06-17] - After upgrading to {% data variables.product.prodname_ghe_server %} 3.4, releases may appear to be missing from repositories. This can occur when the required Elasticsearch index migrations have not successfully completed. + - '{% data reusables.release-notes.ghas-3.4-secret-scanning-known-issue %}' \ No newline at end of file diff --git a/data/release-notes/enterprise-server/3-5/0.yml b/data/release-notes/enterprise-server/3-5/0.yml index f30c3f056874..71952659d9af 100644 --- a/data/release-notes/enterprise-server/3-5/0.yml +++ b/data/release-notes/enterprise-server/3-5/0.yml @@ -434,3 +434,4 @@ sections: - Reopening of dismissed Dependabot alerts - Enabling the **Update branch** button for all pull requests in a repository - Light high contrast theme + - '{% data reusables.release-notes.ghas-3.4-secret-scanning-known-issue %}' \ No newline at end of file diff --git a/data/release-notes/enterprise-server/3-5/1.yml b/data/release-notes/enterprise-server/3-5/1.yml index 16ed88b60743..c19a2fce38ff 100644 --- a/data/release-notes/enterprise-server/3-5/1.yml +++ b/data/release-notes/enterprise-server/3-5/1.yml @@ -32,8 +32,9 @@ sections: - 'Management Console may appear stuck on the _Starting_ screen after upgrading an under-provisioned instance to GitHub Enterprise Server 3.5. [Updated: 2022-06-20]' - | The following features are unavailable for users in GitHub Enterprise Server 3.5.0, 3.5.1, 3.5.2, and 3.5.3. The features will be available in an upcoming patch release. [Updated: 2022-08-16] - + - Detection of GitHub Actions workflow files for the dependency graph - Reopening of dismissed Dependabot alerts - Enabling the **Update branch** button for all pull requests in a repository - Light high contrast theme + - '{% data reusables.release-notes.ghas-3.4-secret-scanning-known-issue %}' \ No newline at end of file diff --git a/data/release-notes/enterprise-server/3-5/2.yml b/data/release-notes/enterprise-server/3-5/2.yml index 1329dd91ad12..b76a16706ace 100644 --- a/data/release-notes/enterprise-server/3-5/2.yml +++ b/data/release-notes/enterprise-server/3-5/2.yml @@ -39,3 +39,4 @@ sections: - Reopening of dismissed Dependabot alerts - Enabling the **Update branch** button for all pull requests in a repository - Light high contrast theme + - '{% data reusables.release-notes.ghas-3.4-secret-scanning-known-issue %}' \ No newline at end of file diff --git a/data/release-notes/enterprise-server/3-5/3.yml b/data/release-notes/enterprise-server/3-5/3.yml index f6e3ad5a2f47..7916b213896b 100644 --- a/data/release-notes/enterprise-server/3-5/3.yml +++ b/data/release-notes/enterprise-server/3-5/3.yml @@ -23,18 +23,19 @@ sections: - Metrics for `aqueduct` background processes are gathered for Collectd forwarding and display in the Management Console. - The location of the database migration and configuration run log, `/data/user/common/ghe-config.log`, is now displayed on the page that details a migration in progress. known_issues: - - On a freshly set up {% data variables.product.prodname_ghe_server %} instance without any users, an attacker could create the first admin user. - - Custom firewall rules are removed during the upgrade process. - - Git LFS tracked files [uploaded through the web interface](https://github.com/blog/2105-upload-files-to-your-repositories) are incorrectly added directly to the repository. - - Issues cannot be closed if they contain a permalink to a blob in the same repository, where the blob's file path is longer than 255 characters. - - 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 need to be restarted after restoring an appliance from a backup taken on a different host. - - | - The following features are unavailable for users in GitHub Enterprise Server 3.5.0, 3.5.1, 3.5.2, and 3.5.3. The features will be available in an upcoming patch release. [Updated: 2022-08-16] + - On a freshly set up {% data variables.product.prodname_ghe_server %} instance without any users, an attacker could create the first admin user. + - Custom firewall rules are removed during the upgrade process. + - Git LFS tracked files [uploaded through the web interface](https://github.com/blog/2105-upload-files-to-your-repositories) are incorrectly added directly to the repository. + - Issues cannot be closed if they contain a permalink to a blob in the same repository, where the blob's file path is longer than 255 characters. + - 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 need to be restarted after restoring an appliance from a backup taken on a different host. + - | + The following features are unavailable for users in GitHub Enterprise Server 3.5.0, 3.5.1, 3.5.2, and 3.5.3. The features will be available in an upcoming patch release. [Updated: 2022-08-16] - - Detection of GitHub Actions workflow files for the dependency graph - - Reopening of dismissed Dependabot alerts - - Enabling the **Update branch** button for all pull requests in a repository - - Light high contrast theme + - Detection of GitHub Actions workflow files for the dependency graph + - Reopening of dismissed Dependabot alerts + - Enabling the **Update branch** button for all pull requests in a repository + - Light high contrast theme + - '{% data reusables.release-notes.ghas-3.4-secret-scanning-known-issue %}' \ No newline at end of file diff --git a/data/release-notes/enterprise-server/3-6/0-rc1.yml b/data/release-notes/enterprise-server/3-6/0-rc1.yml index 5a197a429704..104708fa496c 100644 --- a/data/release-notes/enterprise-server/3-6/0-rc1.yml +++ b/data/release-notes/enterprise-server/3-6/0-rc1.yml @@ -299,3 +299,4 @@ sections: - In a repository's settings, enabling the option to allow users with read access to create discussions does not enable this functionality. - In some cases, users cannot convert existing issues to discussions. - Custom patterns for secret scanning have `.*` as an end delimiter, specifically in the "After secret" field. This delimiter causes inconsistencies in scans for secrets across repositories, and you may notice gaps in a repository's history where no scans completed. Incremental scans may also be impacted. To prevent issues with scans, modify the end of the pattern to remove the `.*` delimiter. + - '{% data reusables.release-notes.ghas-3.4-secret-scanning-known-issue %}' \ No newline at end of file diff --git a/data/reusables/release-notes/ghas-3.4-secret-scanning-known-issue.md b/data/reusables/release-notes/ghas-3.4-secret-scanning-known-issue.md new file mode 100644 index 000000000000..67593664e735 --- /dev/null +++ b/data/reusables/release-notes/ghas-3.4-secret-scanning-known-issue.md @@ -0,0 +1,16 @@ +{% ifversion ghes > 3.1 or ghes < 3.5 %} + +In some cases, GitHub Advanced Security customers who upgrade to GitHub Enterprise Server 3.5 or later may notice that alerts from secret scanning are missing in the web UI and REST API. To ensure the alerts remain visible, do not skip 3.4 when you upgrade from an earlier release to 3.5 or later. A fix for 3.5 and later will be available in an upcoming patch release. + +To plan an upgrade through 3.4, see the [Upgrade assistant](https://support.github.com/enterprise/server-upgrade). [Updated: 2022-08-16] + +{% elsif ghes > 3.4 or ghes < 3.7 %} + +In some cases, GitHub Advanced Security customers who upgrade to GitHub Enterprise Server {{ currentVersion }} may notice that alerts from secret scanning are missing in the web UI and REST API. To ensure the alerts remain visible, do not skip 3.4 as you upgrade to the latest release. To plan an upgrade through 3.4, see the [Upgrade assistant](https://support.github.com/enterprise/server-upgrade). + +- To display the missing alerts for all repositories owned by an organization, organization owners can navigate to the organization's **Code security and analysis** settings, then click **Enable all** for secret scanning. For more information, see "[Managing security and analysis settings for your organization](/organizations/keeping-your-organization-secure/managing-security-settings-for-your-organization/managing-security-and-analysis-settings-for-your-organization#enabling-or-disabling-a-feature-for-all-existing-repositories)." +- To display the missing alerts for an individual repository, people with admin access to the repository can disable then enable secret scanning for the repository. For more information, see "[Managing security and analysis settings for your repository](/repositories/managing-your-repositorys-settings-and-features/enabling-features-for-your-repository/managing-security-and-analysis-settings-for-your-repository)." + +A fix will be available in an upcoming patch release. [Updated: 2022-08-16] + +{% endif %}