jprdonnelly/docs
1
0
Fork 0
mirror of synced 2025-12-23 03:44:00 -05:00
Code Issues Projects Releases Wiki Activity

fixing quotes and release date

Browse Source
This commit is contained in:
Chris Queitzsch
2022-01-18 23:26:53 -08:00
parent 403ec56315
commit 9370ccb901
4 changed files with 45 additions and 46 deletions
Download Patch File Download Diff File Expand all files Collapse all files

4
data/release-notes/enterprise-server/3-0/23.yml
View File

@@ -1,7 +1,7 @@
date: '2022-01-12' date: '2022-01-18'
sections: sections:
security_fixes: security_fixes:
- Packages have been updated to the latest security versions. In these updates, Log4j has been updated to version 2.17.1. Note: previous mitigations released in 3.3.1, 3.2.6, 3.1.14, and 3.0.22 are sufficient to address the impact of CVE-2021-44228, CVE-2021-45046, CVE-2021-45105, and CVE-2021-44832 in these versions of GitHub Enterprise Server. - 'Packages have been updated to the latest security versions. In these updates, Log4j has been updated to version 2.17.1. Note: previous mitigations released in 3.3.1, 3.2.6, 3.1.14, and 3.0.22 are sufficient to address the impact of CVE-2021-44228, CVE-2021-45046, CVE-2021-45105, and CVE-2021-44832 in these versions of GitHub Enterprise Server.'
- Sanitize more secrets in the generated support bundles - Sanitize more secrets in the generated support bundles
- Packages have been updated to the latest security versions. - Packages have been updated to the latest security versions.
bugs: bugs:

4
data/release-notes/enterprise-server/3-1/15.yml
View File

@@ -1,7 +1,7 @@
date: '2022-01-12' date: '2022-01-18'
sections: sections:
security_fixes: security_fixes:
- Packages have been updated to the latest security versions. In these updates, Log4j has been updated to version 2.17.1. Note: previous mitigations released in 3.3.1, 3.2.6, 3.1.14, and 3.0.22 are sufficient to address the impact of CVE-2021-44228, CVE-2021-45046, CVE-2021-45105, and CVE-2021-44832 in these versions of GitHub Enterprise Server. - 'Packages have been updated to the latest security versions. In these updates, Log4j has been updated to version 2.17.1. Note: previous mitigations released in 3.3.1, 3.2.6, 3.1.14, and 3.0.22 are sufficient to address the impact of CVE-2021-44228, CVE-2021-45046, CVE-2021-45105, and CVE-2021-44832 in these versions of GitHub Enterprise Server.'
- Sanitize more secrets in the generated support bundles - Sanitize more secrets in the generated support bundles
- Packages have been updated to the latest security versions. - Packages have been updated to the latest security versions.
bugs: bugs:

4
data/release-notes/enterprise-server/3-2/7.yml
View File

@@ -1,7 +1,7 @@
date: '2022-01-12' date: '2022-01-18'
sections: sections:
security_fixes: security_fixes:
- Packages have been updated to the latest security versions. In these updates, Log4j has been updated to version 2.17.1. Note: previous mitigations released in 3.3.1, 3.2.6, 3.1.14, and 3.0.22 are sufficient to address the impact of CVE-2021-44228, CVE-2021-45046, CVE-2021-45105, and CVE-2021-44832 in these versions of GitHub Enterprise Server. - 'Packages have been updated to the latest security versions. In these updates, Log4j has been updated to version 2.17.1. Note: previous mitigations released in 3.3.1, 3.2.6, 3.1.14, and 3.0.22 are sufficient to address the impact of CVE-2021-44228, CVE-2021-45046, CVE-2021-45105, and CVE-2021-44832 in these versions of GitHub Enterprise Server.'
- Sanitize more secrets in the generated support bundles - Sanitize more secrets in the generated support bundles
- Packages have been updated to the latest security versions. - Packages have been updated to the latest security versions.
bugs: bugs:

5
data/release-notes/enterprise-server/3-3/2.yml
View File

@@ -1,7 +1,7 @@
date: '2022-01-12' date: '2022-01-18'
sections: sections:
security_fixes: security_fixes:
- Packages have been updated to the latest security versions. In these updates, Log4j has been updated to version 2.17.1. Note: previous mitigations released in 3.3.1, 3.2.6, 3.1.14, and 3.0.22 are sufficient to address the impact of CVE-2021-44228, CVE-2021-45046, CVE-2021-45105, and CVE-2021-44832 in these versions of GitHub Enterprise Server. - 'Packages have been updated to the latest security versions. In these updates, Log4j has been updated to version 2.17.1. Note: previous mitigations released in 3.3.1, 3.2.6, 3.1.14, and 3.0.22 are sufficient to address the impact of CVE-2021-44228, CVE-2021-45046, CVE-2021-45105, and CVE-2021-44832 in these versions of GitHub Enterprise Server.'
- Sanitize more secrets in the generated support bundles - Sanitize more secrets in the generated support bundles
- Users on teams with the Security Manger role will now be notified about security alerts for repositories they are watching. - Users on teams with the Security Manger role will now be notified about security alerts for repositories they are watching.
- The security managers component will show a less-aggressive warning once the maximum number of teams has been reached. - The security managers component will show a less-aggressive warning once the maximum number of teams has been reached.
@@ -28,4 +28,3 @@ 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. - 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. - 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_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.'