Merge pull request #5397 from github/repo-sync

repo sync

Author: Octomerger

data/release-notes/2-21/19.yml

@@ -4,8 +4,8 @@ sections:
     - Packages have been updated to the latest security versions.
   bugs:
     - 'A warning message `jq: error (at <stdin>:0): Cannot index number with string "settings"` could occur during replica promotion.'
-    - Visiting the `/settings/emails page` would store state that could cause improper redirects when logging out and logging back in.
-    - Dependency graph alerts weren''t shown for some components whose advisories have upper case package names in `vulnerable_version_ranges`.
+    - Visiting the `/settings/emails` page would store state that could cause improper redirects when logging out and logging back in.
+    - Dependency graph alerts weren't shown for some components whose advisories have upper case package names in `vulnerable_version_ranges`.
     - User saw 500 error when executing git operations on an instance configured with LDAP authentication.
     - When ghe-migrator encountered import errors, it would sometimes abort the entire process, and the logs did not include enough context.
   known_issues:

data/release-notes/2-22/11.yml

@@ -6,8 +6,8 @@ sections:
     - 'A warning message `jq: error (at <stdin>:0): Cannot index number with string "settings"` could occur during replica promotion.'
     - Continuously restoring backups to a cluster could fail due to MySQL replicas failing to connect to the primary.
     - Syntax highlighting could fail due to the Treelights container running out of memory.
-    - Visiting the `/settings/emails page` would store state that could cause improper redirects when logging out and logging back in.
-    - Dependency graph alerts weren''t shown for some components whose advisories have upper case package names in `vulnerable_version_ranges`.
+    - Visiting the `/settings/emails` page would store state that could cause improper redirects when logging out and logging back in.
+    - Dependency graph alerts weren't shown for some components whose advisories have upper case package names in `vulnerable_version_ranges`.
     - GitHub integration apps were not able to notify teams when mentioned directly via an at-mention in an issue comment.
     - When ghe-migrator encountered import errors, it would sometimes abort the entire process, and the logs did not include enough context.
   known_issues:

data/release-notes/3-0/5.yml

@@ -10,7 +10,7 @@ sections:
     - Packages related subdomains were not showing up in the "Test domain settings" prompt for subdomain isolation.
     - The `X-GitHub-Enterprise-Host` header sent with webhooks included a random string, rather than the hostname of the GitHub Enterprise Server instance that sent the HTTP POST payload.
     - Upgrading from 2.22.x to 3.0.x would fail if GitHub Actions had previously been enabled, but disabled before the upgrade.
-    - Visiting the `/settings/emails page` would store state that could cause improper redirects when logging out and logging back in.
+    - Visiting the `/settings/emails` page would store state that could cause improper redirects when logging out and logging back in.
     - GitHub integration apps were not able to notify teams when mentioned directly via an at-mention in an issue comment.
     - reStructuredText (RST) rendering in the web UI would fail and instead displayed raw RST markup text.
     - Email notifications for Secret Scanning alerts were not sent to authorized users when the Dependency Graph was not fully enabled.