diff --git a/translations/zh-CN/data/release-notes/enterprise-server/2-20/0.yml b/translations/zh-CN/data/release-notes/enterprise-server/2-20/0.yml index 3fd77690d316..185a6af4232c 100644 --- a/translations/zh-CN/data/release-notes/enterprise-server/2-20/0.yml +++ b/translations/zh-CN/data/release-notes/enterprise-server/2-20/0.yml @@ -1,10 +1,10 @@ date: '2020-02-11' sections: features: - - '在存储库分支上，存储库管理员可以使用[分支保护规则](https://help.github.com/en/github/administering-a-repository/enabling-branch-restrictions)启用“需要线性历史记录”，从而拒绝包含合并提交的任何推送。{% comment %} https://github.blog/changelog/2019-12-04-expanded-branch-protection-rules/ {% endcomment %}' - - '存储库管理员可以使用[分支保护规则](https://help.github.com/en/github/administering-a-repository/enabling-branch-restrictions)启用“允许强制推送”，从而授予所有用户强制推送到受保护的分支的能力。{% comment %} https://github.blog/changelog/2019-12-04-expanded-branch-protection-rules/、https://github.com/github/ce-oss-happiness/issues/42、https://github.com/github/github/pull/125950 {% endcomment %}' - - '存储库管理员可以使用[分支保护规则](https://help.github.com/en/github/administering-a-repository/enabling-branch-restrictions)启用“允许删除”，从而授予所有具有推送权限的用户删除受保护分支的能力。{% comment %} https://github.blog/changelog/2019-12-04-expanded-branch-protection-rules/ {% endcomment %}' - - '管理员可以在存储库上设置 `maxobjectsize` 限制、对不在 [Git LFS](https://help.github.com/en/enterprise/admin/installation/configuring-git-large-file-storage-on-github-enterprise-server) 中的存储库[限制推送提交的大小](https://help.github.com/en/enterprise/admin/installation/setting-git-push-limits)。{% comment %} https://github.com/github/babeld/pull/864、https://team.githubapp.com/posts/33519、https://github.com/githubcustomers/Slack/issues/27 {% endcomment %}' + - '在存储库分支上，存储库管理员可以使用[分支保护规则](https://help.github.com/en/github/administering-a-repository/enabling-branch-restrictions) 启用“需要线性历史记录”，从而拒绝包含合并提交的任何推送。{% comment %} https://github.blog/changelog/2019-12-04-expanded-branch-protection-rules/ {% endcomment %}' + - '存储库管理员可以使用[分支保护规则](https://help.github.com/en/github/administering-a-repository/enabling-branch-restrictions) 启用“允许强制推送”，从而授予所有用户强制推送到受保护的分支的能力。{% comment %} https://github.blog/changelog/2019-12-04-expanded-branch-protection-rules/、https://github.com/github/ce-oss-happiness/issues/42、https://github.com/github/github/pull/125950 {% endcomment %}' + - '存储库管理员可以使用[分支保护规则](https://help.github.com/en/github/administering-a-repository/enabling-branch-restrictions) 启用“允许删除”，从而授予所有具有推送权限的用户删除受保护分支的能力。{% comment %} https://github.blog/changelog/2019-12-04-expanded-branch-protection-rules/ {% endcomment %}' + - '管理员可以在存储库上设置 `maxobjectsize` 限制、对不在 [Git LFS](https://help.github.com/en/enterprise/admin/installation/configuring-git-large-file-storage-on-github-enterprise-server) 中的存储库 [限制推送提交的大小](https://help.github.com/en/enterprise/admin/installation/setting-git-push-limits)。{% comment %} https://github.com/github/babeld/pull/864、https://team.githubapp.com/posts/33519、https://github.com/githubcustomers/Slack/issues/27 {% endcomment %}' - '组织所有者在创建新存储库时可以创建一组默认标签。{% comment %} https://github.com/github/issues-projects/issues/237、https://github.com/github/issues-projects/issues/179 {% endcomment %}' security_fixes: - 包已更新到最新的安全版本。 @@ -32,7 +32,7 @@ sections: known_issues: - '在新建的没有任何用户的 GitHub Enterprise Server 上，攻击者可以创建第一个管理员用户。{% comment %} https://github.com/github/enterprise2/issues/1889 {% endcomment %}' - '在升级期间不会维护自定义防火墙规则。{% comment %} https://github.com/github/enterprise2/issues/2823 {% endcomment %}' - - '[通过 Web 界面上传](https://github.com/blog/2105-upload-files-to-your-repositories)的 Git LFS 跟踪文件被错误地直接添加到存储库。{% comment %} https://github.com/github/github/issues/54684 {% endcomment %}' + - '[通过 Web 界面上传](https://github.com/blog/2105-upload-files-to-your-repositories) 的 Git LFS 跟踪文件被错误地直接添加到存储库。{% comment %} https://github.com/github/github/issues/54684 {% endcomment %}' - '如果问题包含同一存储库中文件路径长于 255 个字符的 blob 的永久链接，则问题无法关闭。{% comment %} https://github.com/github/github/issues/107731 {% endcomment %}' - '推送到 Gist 时，可能会在后接收挂钩期间触发异常。{% comment %} https://github.com/github/github/issues/129091 {% endcomment %}' - "数据库中重复的 Webhook 条目可能会导致从早期版本的升级失败。（更新时间：2020-02-26）" diff --git a/translations/zh-CN/data/release-notes/enterprise-server/2-20/1.yml b/translations/zh-CN/data/release-notes/enterprise-server/2-20/1.yml index 3a318e0188c0..78f477fb90c4 100644 --- a/translations/zh-CN/data/release-notes/enterprise-server/2-20/1.yml +++ b/translations/zh-CN/data/release-notes/enterprise-server/2-20/1.yml @@ -10,7 +10,7 @@ sections: known_issues: - '在没有任何用户的新建 GitHub Enterprise Server 上，攻击者可能创建第一个管理员用户。{% comment %} https://github.com/github/enterprise2/issues/1889 {% endcomment %}' - '自定义防火墙规则在升级期间没有维护。{% comment %} https://github.com/github/enterprise2/issues/2823 {% endcomment %}' - - '[通过 Web 界面上传](https://github.com/blog/2105-upload-files-to-your-repositories)的 Git LFS 跟踪文件被错误地直接添加到存储库。{% comment %} https://github.com/github/github/issues/54684 {% endcomment %}' + - '[通过 Web 界面上传](https://github.com/blog/2105-upload-files-to-your-repositories) 的 Git LFS 跟踪文件被错误地直接添加到存储库。{% comment %} https://github.com/github/github/issues/54684 {% endcomment %}' - '问题若是包含同一存储库中文件路径长于 255 个字符的 blob 的永久链接，则无法关闭。{% comment %} https://github.com/github/github/issues/107731 {% endcomment %}' - '推送到 Gist 时，可能会在后接收挂钩时触发异常。{% comment %} https://github.com/github/github/issues/129091 {% endcomment %}' - '如果自定义了后台工作进程配置，则升级和设置更新将失败。{% comment %} https://github.com/github/enterprise2/issues/19119 {% endcomment %}' diff --git a/translations/zh-CN/data/release-notes/enterprise-server/2-20/13.yml b/translations/zh-CN/data/release-notes/enterprise-server/2-20/13.yml index cf56d4e79fb8..78d43e8ad5fd 100644 --- a/translations/zh-CN/data/release-notes/enterprise-server/2-20/13.yml +++ b/translations/zh-CN/data/release-notes/enterprise-server/2-20/13.yml @@ -15,7 +15,7 @@ sections: known_issues: - '在没有任何用户的新建 GitHub Enterprise Server 上，攻击者可以创建第一个管理员用户。{% comment %} https://github.com/github/enterprise2/issues/1889 {% endcomment %}' - '在升级期间不会维护自定义防火墙规则。{% comment %} https://github.com/github/enterprise2/issues/2823 {% endcomment %}' - - 'Git LFS 跟踪的[通过 Web 界面上传的](https://github.com/blog/2105-upload-files-to-your-repositories)文件被错误地直接添加到存储库。{% comment %} https://github.com/github/github/issues/54684 {% endcomment %}' + - 'Git LFS 跟踪的[通过 Web 界面上传的](https://github.com/blog/2105-upload-files-to-your-repositories) 文件被错误地直接添加到存储库。{% comment %} https://github.com/github/github/issues/54684 {% endcomment %}' - '如果问题包含指向同一存储库中文件路径长于 255 个字符的 blob 的永久链接，则无法关闭。{% comment %} https://github.com/github/github/issues/107731 {% endcomment %}' - '在 GitHub Connect 中启用了“用户可以搜索 GitHub.com”时，专用和内部存储库中的问题不包括在 GitHub.com 搜索结果中。{% comment %} https://github.com/github/admin-experience/issues/571 {% endcomment %}' - '在命令行上推送到存储库时不会报告安全警报。{% comment %} https://github.com/github/github/issues/143190 {% endcomment %}' diff --git a/translations/zh-CN/data/release-notes/enterprise-server/2-20/14.yml b/translations/zh-CN/data/release-notes/enterprise-server/2-20/14.yml index 048b4bdd5c5a..c7fa16c2b1db 100644 --- a/translations/zh-CN/data/release-notes/enterprise-server/2-20/14.yml +++ b/translations/zh-CN/data/release-notes/enterprise-server/2-20/14.yml @@ -6,7 +6,7 @@ sections: known_issues: - '在新建的没有任何用户的 GitHub Enterprise Server 上，攻击者可以创建第一个管理员用户。{% comment %} https://github.com/github/enterprise2/issues/1889 {% endcomment %}' - '在升级期间不会维护自定义防火墙规则。{% comment %} https://github.com/github/enterprise2/issues/2823 {% endcomment %}' - - '[通过 Web 界面上传](https://github.com/blog/2105-upload-files-to-your-repositories)的 Git LFS 跟踪文件被错误地直接添加到存储库。{% comment %} https://github.com/github/github/issues/54684 {% endcomment %}' + - '[通过 Web 界面上传](https://github.com/blog/2105-upload-files-to-your-repositories) 的 Git LFS 跟踪文件被错误地直接添加到存储库。{% comment %} https://github.com/github/github/issues/54684 {% endcomment %}' - '如果问题包含同一存储库中文件路径长于 255 个字符的 blob 的永久链接，则问题无法关闭。{% comment %} https://github.com/github/github/issues/107731 {% endcomment %}' - '在 GitHub Connect 中启用了“用户可以搜索 GitHub.com”时，专用和内部存储库中的问题不包括在 GitHub.com 搜索结果中。{% comment %} https://github.com/github/admin-experience/issues/571 {% endcomment %}' - '在命令行上推送到存储库时不会报告安全警报。{% comment %} https://github.com/github/github/issues/143190 {% endcomment %}' diff --git a/translations/zh-CN/data/release-notes/enterprise-server/2-20/16.yml b/translations/zh-CN/data/release-notes/enterprise-server/2-20/16.yml index fa27d40c7b18..1e52de5edcde 100644 --- a/translations/zh-CN/data/release-notes/enterprise-server/2-20/16.yml +++ b/translations/zh-CN/data/release-notes/enterprise-server/2-20/16.yml @@ -6,7 +6,7 @@ sections: known_issues: - '在没有任何用户的新建 GitHub Enterprise Server 上，攻击者可以创建第一个管理员用户。{% comment %} https://github.com/github/enterprise2/issues/1889 {% endcomment %}' - '在升级期间不会维护自定义防火墙规则。{% comment %} https://github.com/github/enterprise2/issues/2823 {% endcomment %}' - - 'Git LFS 跟踪的[通过 Web 界面上传的](https://github.com/blog/2105-upload-files-to-your-repositories)文件被错误地直接添加到存储库。{% comment %} https://github.com/github/github/issues/54684 {% endcomment %}' + - 'Git LFS 跟踪的[通过 Web 界面上传的](https://github.com/blog/2105-upload-files-to-your-repositories) 文件被错误地直接添加到存储库。{% comment %} https://github.com/github/github/issues/54684 {% endcomment %}' - '如果问题包含指向同一存储库中文件路径长于 255 个字符的 blob 的永久链接，则无法关闭。{% comment %} https://github.com/github/github/issues/107731 {% endcomment %}' - '在 GitHub Connect 中启用了“用户可以搜索 GitHub.com”时，专用和内部存储库中的问题不包括在 GitHub.com 搜索结果中。{% comment %} https://github.com/github/admin-experience/issues/571 {% endcomment %}' - '在命令行上推送到存储库时不会报告安全警报。{% comment %} https://github.com/github/github/issues/143190 {% endcomment %}' diff --git a/translations/zh-CN/data/release-notes/enterprise-server/2-20/17.yml b/translations/zh-CN/data/release-notes/enterprise-server/2-20/17.yml index 39d615a7f259..9bf37de24bfd 100644 --- a/translations/zh-CN/data/release-notes/enterprise-server/2-20/17.yml +++ b/translations/zh-CN/data/release-notes/enterprise-server/2-20/17.yml @@ -6,7 +6,7 @@ sections: known_issues: - '在没有任何用户的新建 GitHub Enterprise Server 上，攻击者可以创建第一个管理员用户。{% comment %} https://github.com/github/enterprise2/issues/1889 {% endcomment %}' - '在升级期间不会维护自定义防火墙规则。{% comment %} https://github.com/github/enterprise2/issues/2823 {% endcomment %}' - - '[通过 Web 界面上传](https://github.com/blog/2105-upload-files-to-your-repositories)的 Git LFS 跟踪文件被错误地直接添加到存储库。{% comment %} https://github.com/github/github/issues/54684 {% endcomment %}' + - '[通过 Web 界面上传](https://github.com/blog/2105-upload-files-to-your-repositories) 的 Git LFS 跟踪文件被错误地直接添加到存储库。{% comment %} https://github.com/github/github/issues/54684 {% endcomment %}' - '如果问题包含同一存储库中文件路径长于 255 个字符的 blob 的永久链接，则无法关闭。{% comment %} https://github.com/github/github/issues/107731 {% endcomment %}' - '在 GitHub Connect 中启用了“用户可以搜索 GitHub.com”时，专用和内部存储库中的问题不包括在 GitHub.com 搜索结果中。{% comment %} https://github.com/github/admin-experience/issues/571 {% endcomment %}' - '在命令行上推送到存储库时不会报告安全警报。{% comment %} https://github.com/github/github/issues/143190 {% endcomment %}' diff --git a/translations/zh-CN/data/release-notes/enterprise-server/2-20/18.yml b/translations/zh-CN/data/release-notes/enterprise-server/2-20/18.yml index 9bdfe66a3791..1d03969a08f5 100644 --- a/translations/zh-CN/data/release-notes/enterprise-server/2-20/18.yml +++ b/translations/zh-CN/data/release-notes/enterprise-server/2-20/18.yml @@ -19,7 +19,7 @@ sections: known_issues: - '在新建的没有任何用户的 GitHub Enterprise Server 上，攻击者可以创建第一个管理员用户。{% comment %} https://github.com/github/enterprise2/issues/1889 {% endcomment %}' - '在升级期间不会维护自定义防火墙规则。{% comment %} https://github.com/github/enterprise2/issues/2823 {% endcomment %}' - - '[通过 Web 界面上传](https://github.com/blog/2105-upload-files-to-your-repositories)的 Git LFS 跟踪文件被错误地直接添加到存储库。{% comment %} https://github.com/github/github/issues/54684 {% endcomment %}' + - '[通过 Web 界面上传](https://github.com/blog/2105-upload-files-to-your-repositories) 的 Git LFS 跟踪文件被错误地直接添加到存储库。{% comment %} https://github.com/github/github/issues/54684 {% endcomment %}' - '如果问题包含同一存储库中文件路径长于 255 个字符的 blob 的永久链接，则问题无法关闭。{% comment %} https://github.com/github/github/issues/107731 {% endcomment %}' - '在 GitHub Connect 中启用了“用户可以搜索 GitHub.com”时，专用和内部存储库中的问题不包括在 GitHub.com 搜索结果中。{% comment %} https://github.com/github/admin-experience/issues/571 {% endcomment %}' - '在命令行上推送到存储库时不会报告安全警报。{% comment %} https://github.com/github/github/issues/143190 {% endcomment %}' diff --git a/translations/zh-CN/data/release-notes/enterprise-server/2-20/19.yml b/translations/zh-CN/data/release-notes/enterprise-server/2-20/19.yml index 848ad4fa39ec..795bdd4a6215 100644 --- a/translations/zh-CN/data/release-notes/enterprise-server/2-20/19.yml +++ b/translations/zh-CN/data/release-notes/enterprise-server/2-20/19.yml @@ -7,7 +7,7 @@ sections: known_issues: - '在没有任何用户的新建 GitHub Enterprise Server 上，攻击者可以创建第一个管理员用户。{% comment %} https://github.com/github/enterprise2/issues/1889 {% endcomment %}' - '在升级期间不会维护自定义防火墙规则。{% comment %} https://github.com/github/enterprise2/issues/2823 {% endcomment %}' - - 'Git LFS 跟踪的[通过 Web 界面上传的](https://github.com/blog/2105-upload-files-to-your-repositories)文件被错误地直接添加到存储库。{% comment %} https://github.com/github/github/issues/54684 {% endcomment %}' + - 'Git LFS 跟踪的[通过 Web 界面上传的](https://github.com/blog/2105-upload-files-to-your-repositories) 文件被错误地直接添加到存储库。{% comment %} https://github.com/github/github/issues/54684 {% endcomment %}' - '如果问题包含同一存储库中文件路径长于 255 个字符的 blob 的永久链接，则无法关闭。{% comment %} https://github.com/github/github/issues/107731 {% endcomment %}' - '在 GitHub Connect 中启用了“用户可以搜索 GitHub.com”时，专用和内部存储库中的问题不包括在 GitHub.com 搜索结果中。{% comment %} https://github.com/github/admin-experience/issues/571 {% endcomment %}' - '在命令行上推送到存储库时不会报告安全警报。{% comment %} https://github.com/github/github/issues/143190 {% endcomment %}' diff --git a/translations/zh-CN/data/release-notes/enterprise-server/2-20/2.yml b/translations/zh-CN/data/release-notes/enterprise-server/2-20/2.yml index 76e0513b0c21..3a59704de009 100644 --- a/translations/zh-CN/data/release-notes/enterprise-server/2-20/2.yml +++ b/translations/zh-CN/data/release-notes/enterprise-server/2-20/2.yml @@ -17,7 +17,7 @@ sections: known_issues: - '在新建的没有任何用户的 GitHub Enterprise Server 上，攻击者可以创建第一个管理员用户。{% comment %} https://github.com/github/enterprise2/issues/1889 {% endcomment %}' - '在升级期间不会维护自定义防火墙规则。{% comment %} https://github.com/github/enterprise2/issues/2823 {% endcomment %}' - - '[通过 Web 界面上传](https://github.com/blog/2105-upload-files-to-your-repositories)的 Git LFS 跟踪的文件被错误地直接添加到存储库。{% comment %} https://github.com/github/github/issues/54684 {% endcomment %}' + - '[通过 Web 界面上传](https://github.com/blog/2105-upload-files-to-your-repositories) 的 Git LFS 跟踪的文件被错误地直接添加到存储库。{% comment %} https://github.com/github/github/issues/54684 {% endcomment %}' - '问题若是包含同一存储库中文件路径长于 255 个字符的 blob 的永久链接，则无法关闭。{% comment %} https://github.com/github/github/issues/107731 {% endcomment %}' - '推送到 Gist 时，可能会在后接收挂钩时触发异常。{% comment %} https://github.com/github/github/issues/129091 {% endcomment %}' - '如果自定义了后台工作进程配置，则升级和设置更新将失败。{% comment %} https://github.com/github/enterprise2/issues/19119 {% endcomment %}' diff --git a/translations/zh-CN/data/release-notes/enterprise-server/2-20/20.yml b/translations/zh-CN/data/release-notes/enterprise-server/2-20/20.yml index dab45f31ddc8..3d820f946ec6 100644 --- a/translations/zh-CN/data/release-notes/enterprise-server/2-20/20.yml +++ b/translations/zh-CN/data/release-notes/enterprise-server/2-20/20.yml @@ -9,7 +9,7 @@ sections: known_issues: - '在没有任何用户的新建 GitHub Enterprise Server 上，攻击者可以创建第一个管理员用户。{% comment %} https://github.com/github/enterprise2/issues/1889 {% endcomment %}' - '在升级期间不会维护自定义防火墙规则。{% comment %} https://github.com/github/enterprise2/issues/2823 {% endcomment %}' - - 'Git LFS 跟踪的[通过 Web 界面上传的](https://github.com/blog/2105-upload-files-to-your-repositories)文件被错误地直接添加到存储库。{% comment %} https://github.com/github/github/issues/54684 {% endcomment %}' + - 'Git LFS 跟踪的[通过 Web 界面上传的](https://github.com/blog/2105-upload-files-to-your-repositories) 文件被错误地直接添加到存储库。{% comment %} https://github.com/github/github/issues/54684 {% endcomment %}' - '如果问题包含指向同一存储库中文件路径长于 255 个字符的 blob 的永久链接，则无法关闭。{% comment %} https://github.com/github/github/issues/107731 {% endcomment %}' - '在 GitHub Connect 中启用了“用户可以搜索 GitHub.com”时，专用和内部存储库中的问题不包括在 GitHub.com 搜索结果中。{% comment %} https://github.com/github/admin-experience/issues/571 {% endcomment %}' - '在命令行上推送到存储库时不会报告安全警报。{% comment %} https://github.com/github/github/issues/143190 {% endcomment %}' diff --git a/translations/zh-CN/data/release-notes/enterprise-server/2-20/21.yml b/translations/zh-CN/data/release-notes/enterprise-server/2-20/21.yml index fe9d3649d4bd..0fc6e11d13b3 100644 --- a/translations/zh-CN/data/release-notes/enterprise-server/2-20/21.yml +++ b/translations/zh-CN/data/release-notes/enterprise-server/2-20/21.yml @@ -8,7 +8,7 @@ sections: known_issues: - '在新建的没有任何用户的 GitHub Enterprise Server 上，攻击者可以创建第一个管理员用户。{% comment %} https://github.com/github/enterprise2/issues/1889 {% endcomment %}' - '在升级期间不会维护自定义防火墙规则。{% comment %} https://github.com/github/enterprise2/issues/2823 {% endcomment %}' - - '[通过 Web 界面上传](https://github.com/blog/2105-upload-files-to-your-repositories)的 Git LFS 跟踪文件被错误地直接添加到存储库。{% comment %} https://github.com/github/github/issues/54684 {% endcomment %}' + - '[通过 Web 界面上传](https://github.com/blog/2105-upload-files-to-your-repositories) 的 Git LFS 跟踪文件被错误地直接添加到存储库。{% comment %} https://github.com/github/github/issues/54684 {% endcomment %}' - '如果问题包含同一存储库中文件路径长于 255 个字符的 blob 的永久链接，则问题无法关闭。{% comment %} https://github.com/github/github/issues/107731 {% endcomment %}' - '在 GitHub Connect 中启用了“用户可以搜索 GitHub.com”时，专用和内部存储库中的问题不包括在 GitHub.com 搜索结果中。{% comment %} https://github.com/github/admin-experience/issues/571 {% endcomment %}' - '在命令行上推送到存储库时不会报告安全警报。{% comment %} https://github.com/github/github/issues/143190 {% endcomment %}' diff --git a/translations/zh-CN/data/release-notes/enterprise-server/2-20/22.yml b/translations/zh-CN/data/release-notes/enterprise-server/2-20/22.yml index da27dc46d11f..d54b3fa69d59 100644 --- a/translations/zh-CN/data/release-notes/enterprise-server/2-20/22.yml +++ b/translations/zh-CN/data/release-notes/enterprise-server/2-20/22.yml @@ -12,7 +12,7 @@ sections: known_issues: - '在没有任何用户的新建 GitHub Enterprise Server 上，攻击者可以创建第一个管理员用户。{% comment %} https://github.com/github/enterprise2/issues/1889 {% endcomment %}' - '在升级期间不会维护自定义防火墙规则。{% comment %} https://github.com/github/enterprise2/issues/2823 {% endcomment %}' - - 'Git LFS 跟踪的[通过 Web 界面上传的](https://github.com/blog/2105-upload-files-to-your-repositories)文件被错误地直接添加到存储库。{% comment %} https://github.com/github/github/issues/54684 {% endcomment %}' + - 'Git LFS 跟踪的[通过 Web 界面上传的](https://github.com/blog/2105-upload-files-to-your-repositories) 文件被错误地直接添加到存储库。{% comment %} https://github.com/github/github/issues/54684 {% endcomment %}' - '如果问题包含指向同一存储库中文件路径长于 255 个字符的 blob 的永久链接，则无法关闭。{% comment %} https://github.com/github/github/issues/107731 {% endcomment %}' - '在 GitHub Connect 中启用了“用户可以搜索 GitHub.com”时，专用和内部存储库中的问题不包括在 GitHub.com 搜索结果中。{% comment %} https://github.com/github/admin-experience/issues/571 {% endcomment %}' - '在命令行上推送到存储库时不会报告安全警报。{% comment %} https://github.com/github/github/issues/143190 {% endcomment %}' diff --git a/translations/zh-CN/data/release-notes/enterprise-server/2-20/23.yml b/translations/zh-CN/data/release-notes/enterprise-server/2-20/23.yml index cbf678035124..537d38a5763a 100644 --- a/translations/zh-CN/data/release-notes/enterprise-server/2-20/23.yml +++ b/translations/zh-CN/data/release-notes/enterprise-server/2-20/23.yml @@ -6,7 +6,7 @@ sections: known_issues: - '在新建的没有任何用户的 GitHub Enterprise Server 上，攻击者可以创建第一个管理员用户。{% comment %} https://github.com/github/enterprise2/issues/1889 {% endcomment %}' - '在升级期间不会维护自定义防火墙规则。{% comment %} https://github.com/github/enterprise2/issues/2823 {% endcomment %}' - - '[通过 Web 界面上传](https://github.com/blog/2105-upload-files-to-your-repositories)的 Git LFS 跟踪文件被错误地直接添加到存储库。{% comment %} https://github.com/github/github/issues/54684 {% endcomment %}' + - '[通过 Web 界面上传](https://github.com/blog/2105-upload-files-to-your-repositories) 的 Git LFS 跟踪文件被错误地直接添加到存储库。{% comment %} https://github.com/github/github/issues/54684 {% endcomment %}' - '如果问题包含同一存储库中文件路径长于 255 个字符的 blob 的永久链接，则问题无法关闭。{% comment %} https://github.com/github/github/issues/107731 {% endcomment %}' - '在 GitHub Connect 中启用了“用户可以搜索 GitHub.com”时，专用和内部存储库中的问题不包括在 GitHub.com 搜索结果中。{% comment %} https://github.com/github/admin-experience/issues/571 {% endcomment %}' - '在命令行上推送到存储库时不会报告安全警报。{% comment %} https://github.com/github/github/issues/143190 {% endcomment %}' diff --git a/translations/zh-CN/data/release-notes/enterprise-server/2-20/24.yml b/translations/zh-CN/data/release-notes/enterprise-server/2-20/24.yml index 5c62b29244a0..555c9a549cdc 100644 --- a/translations/zh-CN/data/release-notes/enterprise-server/2-20/24.yml +++ b/translations/zh-CN/data/release-notes/enterprise-server/2-20/24.yml @@ -1,9 +1,9 @@ date: '2021-03-02' sections: security_fixes: - - '**高：**在 GitHub Enterprise Server 中发现了一个不适当的访问控制漏洞，允许经过验证的实例用户通过特殊构建的拉取请求和 REST API 请求获得对未授权存储库的写入权限。攻击者需要能够创建目标存储库分支，该设置默认为组织拥有的私有存储库禁用。分支保护（如所需的拉取请求审查或状态检查）将防止未经进一步审查或验证的未授权提交被合并。此漏洞已分配 CVE-2021-22861。这个问题是通过 [GitHub Bug 赏金计划](https://bounty.github.com)报告的。' - - '**高：**在 GitHub Enterprise Server GraphQL API 中发现了一个不适当的访问控制漏洞，允许经过验证的实例用户在未经适当授权的情况下修改拉取请求的维护员协作权限。通过利用此漏洞，攻击者将能够访问在他们作为维护员的存储库上打开的拉取请求的头部分支。默认为组织拥有的私有存储库禁用分叉，并且可以防止此漏洞。此外，分支保护（如所需的拉取请求审查或状态检查）将防止未经进一步审查或验证的未授权提交被合并。此漏洞已分配 CVE-2021-22863。这个问题是通过 [GitHub Bug 赏金计划](https://bounty.github.com)报告的。' - - '**高：**在 GitHub Enterprise Server 中发现了一个在构建 GitHub Pages 站点时可以利用的远程代码执行漏洞。GitHub Pages 使用的基础分析器的用户控制配置没有受到足够的限制，因此可以在 GitHub Enterprise Server 实例上执行命令。要利用此漏洞，攻击者需要获得在 GitHub Enterprise Server 实例上创建和构建 GitHub Pages 站点的权限。该漏洞编号为 CVE-2020-10519，是通过 [GitHub Bug 赏金计划](https://bounty.github.com/)报告的。' + - '**高：**在 GitHub Enterprise Server 中发现了一个不适当的访问控制漏洞，允许经过验证的实例用户通过特殊构建的拉取请求和 REST API 请求获得对未授权存储库的写入权限。攻击者需要能够创建目标存储库分支，该设置默认为组织拥有的私有存储库禁用。分支保护（如所需的拉取请求审查或状态检查）将防止未经进一步审查或验证的未授权提交被合并。此漏洞已分配 CVE-2021-22861。这个问题是通过 [GitHub Bug 赏金计划](https://bounty.github.com) 报告的。' + - '**高：**在 GitHub Enterprise Server GraphQL API 中发现了一个不适当的访问控制漏洞，允许经过验证的实例用户在未经适当授权的情况下修改拉取请求的维护员协作权限。通过利用此漏洞，攻击者将能够访问在他们作为维护员的存储库上打开的拉取请求的头部分支。默认为组织拥有的私有存储库禁用分叉，并且可以防止此漏洞。此外，分支保护（如所需的拉取请求审查或状态检查）将防止未经进一步审查或验证的未授权提交被合并。此漏洞已分配 CVE-2021-22863。这个问题是通过 [GitHub Bug 赏金计划](https://bounty.github.com) 报告的。' + - '**高：**在 GitHub Enterprise Server 中发现了一个在构建 GitHub Pages 站点时可以利用的远程代码执行漏洞。GitHub Pages 使用的基础分析器的用户控制配置没有受到足够的限制，因此可以在 GitHub Enterprise Server 实例上执行命令。要利用此漏洞，攻击者需要获得在 GitHub Enterprise Server 实例上创建和构建 GitHub Pages 站点的权限。该漏洞编号为 CVE-2020-10519，是通过 [GitHub Bug 赏金计划](https://bounty.github.com/) 报告的。' - '**低：**对 SVN 桥的特别设计请求可能会触发长时间的等待，然后再导致拒绝服务 (DoS)。' - '包已更新到最新的安全版本。' bugs: @@ -16,12 +16,12 @@ sections: - '无法成功启用或禁用企业帐户设置中的“防止存储库管理员更改匿名 Git 读取访问权限”复选框。' - '在闰年，用户在尝试在星期一查看贡献活动时收到 404 响应。' changes: - - '添加了 [AWS EC2 r5b 实例类型](https://aws.amazon.com/about-aws/whats-new/2020/12/introducing-new-amazon-ec2-r5b-instances-feuring-60-gbps-of-ebbandwidth-260K-iops/)支持。' + - '添加了 [AWS EC2 r5b 实例类型](https://aws.amazon.com/about-aws/whats-new/2020/12/introducing-new-amazon-ec2-r5b-instances-feuring-60-gbps-of-ebbandwidth-260K-iops/) 支持。' - '调整的背景队列排列优先顺序，以更均匀地分配作业。' known_issues: - '在新建的没有任何用户的 GitHub Enterprise Server 上，攻击者可以创建第一个管理员用户。' - '在升级期间不会维护自定义防火墙规则。' - - '[通过 Web 界面上传](https://github.com/blog/2105-upload-files-to-your-repositories)的 Git LFS 跟踪文件被错误地直接添加到存储库。' + - '[通过 Web 界面上传](https://github.com/blog/2105-upload-files-to-your-repositories) 的 Git LFS 跟踪文件被错误地直接添加到存储库。' - '如果问题包含文件路径长于 255 个字符的同一存储库中 blob 的永久链接，则问题无法关闭。' - '对 GitHub Connect 启用“用户可以搜索 GitHub.com”后，专用和内部存储库中的问题不包括在 GitHub.com 搜索结果中。' - '推送到命令行上的存储库时不报告安全警报。' diff --git a/translations/zh-CN/data/release-notes/enterprise-server/2-20/3.yml b/translations/zh-CN/data/release-notes/enterprise-server/2-20/3.yml index c13bcaf40483..dcc8a64941ed 100644 --- a/translations/zh-CN/data/release-notes/enterprise-server/2-20/3.yml +++ b/translations/zh-CN/data/release-notes/enterprise-server/2-20/3.yml @@ -5,7 +5,7 @@ sections: known_issues: - '在没有任何用户的新建 GitHub Enterprise Server 上，攻击者可能创建第一个管理员用户。{% comment %} https://github.com/github/enterprise2/issues/1889 {% endcomment %}' - '自定义防火墙规则在升级期间没有维护。{% comment %} https://github.com/github/enterprise2/issues/2823 {% endcomment %}' - - '[通过 Web 界面上传](https://github.com/blog/2105-upload-files-to-your-repositories)的 Git LFS 跟踪文件被错误地直接添加到存储库。{% comment %} https://github.com/github/github/issues/54684 {% endcomment %}' + - '[通过 Web 界面上传](https://github.com/blog/2105-upload-files-to-your-repositories) 的 Git LFS 跟踪文件被错误地直接添加到存储库。{% comment %} https://github.com/github/github/issues/54684 {% endcomment %}' - '问题若是包含同一存储库中文件路径长于 255 个字符的 blob 的永久链接，则无法关闭。{% comment %} https://github.com/github/github/issues/107731 {% endcomment %}' - '推送到 Gist 时，可能会在后接收挂钩时触发异常。{% comment %} https://github.com/github/github/issues/129091 {% endcomment %}' - '在 GitHub Connect 中启用了“用户可以搜索 GitHub.com”时，专用和内部存储库中的问题不包括在 GitHub.com 搜索结果中。{% comment %} https://github.com/github/admin-experience/issues/571 {% endcomment %}' diff --git a/translations/zh-CN/data/release-notes/enterprise-server/2-20/4.yml b/translations/zh-CN/data/release-notes/enterprise-server/2-20/4.yml index 7322860bb3cb..33ff0ef6d063 100644 --- a/translations/zh-CN/data/release-notes/enterprise-server/2-20/4.yml +++ b/translations/zh-CN/data/release-notes/enterprise-server/2-20/4.yml @@ -8,7 +8,7 @@ sections: known_issues: - '在没有任何用户的新建 GitHub Enterprise Server 上，攻击者可能创建第一个管理员用户。{% comment %} https://github.com/github/enterprise2/issues/1889 {% endcomment %}' - '自定义防火墙规则在升级期间没有维护。{% comment %} https://github.com/github/enterprise2/issues/2823 {% endcomment %}' - - '[通过 Web 界面上传](https://github.com/blog/2105-upload-files-to-your-repositories)的 Git LFS 跟踪文件被错误地直接添加到存储库。{% comment %} https://github.com/github/github/issues/54684 {% endcomment %}' + - '[通过 Web 界面上传](https://github.com/blog/2105-upload-files-to-your-repositories) 的 Git LFS 跟踪文件被错误地直接添加到存储库。{% comment %} https://github.com/github/github/issues/54684 {% endcomment %}' - '问题若是包含同一存储库中文件路径长于 255 个字符的 blob 的永久链接，则无法关闭。{% comment %} https://github.com/github/github/issues/107731 {% endcomment %}' - '推送到 Gist 时，可能会在后接收挂钩时触发异常。{% comment %} https://github.com/github/github/issues/129091 {% endcomment %}' - '在 GitHub Connect 中启用了“用户可以搜索 GitHub.com”时，专用和内部存储库中的问题不包括在 GitHub.com 搜索结果中。{% comment %} https://github.com/github/admin-experience/issues/571 {% endcomment %}' diff --git a/translations/zh-CN/data/release-notes/enterprise-server/2-20/5.yml b/translations/zh-CN/data/release-notes/enterprise-server/2-20/5.yml index 79bb908419d7..54e0febee4e1 100644 --- a/translations/zh-CN/data/release-notes/enterprise-server/2-20/5.yml +++ b/translations/zh-CN/data/release-notes/enterprise-server/2-20/5.yml @@ -10,7 +10,7 @@ sections: known_issues: - '在没有任何用户的新设置的 GitHub Enterprise Server 上，，攻击者可以创建第一个管理员用户。{% comment %} https://github.com/github/enterprise2/issues/1889 {% endcomment %}' - '在升级期间不会维护自定义防火墙规则。{% comment %} https://github.com/github/enterprise2/issues/2823 {% endcomment %}' - - 'Git LFS 跟踪的[通过 Web 界面上传的](https://github.com/blog/2105-upload-files-to-your-repositories)文件被错误地直接添加到存储库。{% comment %} https://github.com/github/github/issues/54684 {% endcomment %}' + - 'Git LFS 跟踪的[通过 Web 界面上传的](https://github.com/blog/2105-upload-files-to-your-repositories) 文件被错误地直接添加到存储库。{% comment %} https://github.com/github/github/issues/54684 {% endcomment %}' - '如果问题包含指向同一存储库中文件路径长于 255 个字符的 blob 的永久链接，则问题无法关闭。{% comment %} https://github.com/github/github/issues/107731 {% endcomment %}' - '当推送到 Gist 时，可能会在后接收挂钩期间触发异常。{% comment %} https://github.com/github/github/issues/129091 {% endcomment %}' - '在 GitHub Connect 中启用了“用户可以搜索 GitHub.com”时，专用和内部存储库中的问题不包括在 GitHub.com 搜索结果中。{% comment %} https://github.com/github/admin-experience/issues/571 {% endcomment %}' diff --git a/translations/zh-CN/data/release-notes/enterprise-server/2-20/6.yml b/translations/zh-CN/data/release-notes/enterprise-server/2-20/6.yml index cef61a882af1..6ba4cc7bbf0e 100644 --- a/translations/zh-CN/data/release-notes/enterprise-server/2-20/6.yml +++ b/translations/zh-CN/data/release-notes/enterprise-server/2-20/6.yml @@ -18,7 +18,7 @@ sections: known_issues: - '在新建的没有任何用户的 GitHub Enterprise Server 上，攻击者可以创建第一个管理员用户。{% comment %} https://github.com/github/enterprise2/issues/1889 {% endcomment %}' - '在升级期间不会维护自定义防火墙规则。{% comment %} https://github.com/github/enterprise2/issues/2823 {% endcomment %}' - - '[通过 Web 界面上传](https://github.com/blog/2105-upload-files-to-your-repositories)的 Git LFS 跟踪文件被错误地直接添加到存储库。{% comment %} https://github.com/github/github/issues/54684 {% endcomment %}' + - '[通过 Web 界面上传](https://github.com/blog/2105-upload-files-to-your-repositories) 的 Git LFS 跟踪文件被错误地直接添加到存储库。{% comment %} https://github.com/github/github/issues/54684 {% endcomment %}' - '如果问题包含同一存储库中文件路径长于 255 个字符的 blob 的永久链接，则问题无法关闭。{% comment %} https://github.com/github/github/issues/107731 {% endcomment %}' - '推送到 Gist 时，可能会在后接收挂钩期间触发异常。{% comment %} https://github.com/github/github/issues/129091 {% endcomment %}' - '在 GitHub Connect 中启用了“用户可以搜索 GitHub.com”时，专用和内部存储库中的问题不包括在 GitHub.com 搜索结果中。{% comment %} https://github.com/github/admin-experience/issues/571 {% endcomment %}' diff --git a/translations/zh-CN/data/release-notes/enterprise-server/2-20/8.yml b/translations/zh-CN/data/release-notes/enterprise-server/2-20/8.yml index 3d89e875dbf7..9dca8a0876d2 100644 --- a/translations/zh-CN/data/release-notes/enterprise-server/2-20/8.yml +++ b/translations/zh-CN/data/release-notes/enterprise-server/2-20/8.yml @@ -11,7 +11,7 @@ sections: known_issues: - '在新建的没有任何用户的 GitHub Enterprise Server 上，攻击者可以创建第一个管理员用户。{% comment %} https://github.com/github/enterprise2/issues/1889 {% endcomment %}' - '在升级期间不会维护自定义防火墙规则。{% comment %} https://github.com/github/enterprise2/issues/2823 {% endcomment %}' - - '[通过 Web 界面上传](https://github.com/blog/2105-upload-files-to-your-repositories)的 Git LFS 跟踪的文件被错误地直接添加到存储库。{% comment %} https://github.com/github/github/issues/54684 {% endcomment %}' + - '[通过 Web 界面上传](https://github.com/blog/2105-upload-files-to-your-repositories) 的 Git LFS 跟踪的文件被错误地直接添加到存储库。{% comment %} https://github.com/github/github/issues/54684 {% endcomment %}' - '问题若是包含同一存储库中文件路径长于 255 个字符的 blob 的永久链接，则无法关闭。{% comment %} https://github.com/github/github/issues/107731 {% endcomment %}' - '推送到 Gist 时，可能会在后接收挂钩时触发异常。{% comment %} https://github.com/github/github/issues/129091 {% endcomment %}' - '对 GitHub Connect 启用“用户可以搜索 GitHub.com”后，专用和内部存储库中的问题不包括在 GitHub.com 搜索结果中。{% comment %} https://github.com/github/admin-experience/issues/571 {% endcomment %}' diff --git a/translations/zh-CN/data/release-notes/enterprise-server/2-20/9.yml b/translations/zh-CN/data/release-notes/enterprise-server/2-20/9.yml index 3e01f8fba29c..4d560203d54b 100644 --- a/translations/zh-CN/data/release-notes/enterprise-server/2-20/9.yml +++ b/translations/zh-CN/data/release-notes/enterprise-server/2-20/9.yml @@ -1,14 +1,14 @@ date: '2020-06-02' sections: security_fixes: - - '**高：**在 GitHub Enterprise Server API 中发现了一个不适当的访问控制漏洞，该漏洞允许组织成员升级权限，获得对组织内未经授权的存储库的访问权限。此漏洞影响 GitHub Enterprise Server 2.21 之前的所有版本。 为应对此问题，我们发布了 [CVE-2020-10516](https://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2020-10516)。此漏洞通过 [GitHub Bug 赏金计划](https://bounty.github.com)报告。{% comment %} https://github.com/github/github/pull/144454, https://github.com/github/github/pull/143444 {% endcomment %}' + - '**高：**在 GitHub Enterprise Server API 中发现了一个不适当的访问控制漏洞，该漏洞允许组织成员升级权限，获得对组织内未经授权的存储库的访问权限。此漏洞影响 GitHub Enterprise Server 2.21 之前的所有版本。 为应对此问题，我们发布了 [CVE-2020-10516](https://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2020-10516)。此漏洞通过 [GitHub Bug 赏金计划](https://bounty.github.com) 报告。{% comment %} https://github.com/github/github/pull/144454, https://github.com/github/github/pull/143444 {% endcomment %}' - '包已更新到最新的安全版本。{% comment %} https://github.com/github/enterprise2/pull/20421, https://github.com/github/enterprise2/pull/20315 {% endcomment %}' bugs: - '面向 Internet 的 GitHub Enterprise Server 实例可以通过搜索引擎编制索引。{% comment %} https://github.com/github/github/pull/145073, https://github.com/github/github/pull/144973 {% endcomment %}' known_issues: - '在新建的没有任何用户的 GitHub Enterprise Server 上，攻击者可以创建第一个管理员用户。{% comment %} https://github.com/github/enterprise2/issues/1889 {% endcomment %}' - '在升级期间不会维护自定义防火墙规则。{% comment %} https://github.com/github/enterprise2/issues/2823 {% endcomment %}' - - '[通过 Web 界面上传](https://github.com/blog/2105-upload-files-to-your-repositories)的 Git LFS 跟踪的文件被错误地直接添加到存储库。{% comment %} https://github.com/github/github/issues/54684 {% endcomment %}' + - '[通过 Web 界面上传](https://github.com/blog/2105-upload-files-to-your-repositories) 的 Git LFS 跟踪的文件被错误地直接添加到存储库。{% comment %} https://github.com/github/github/issues/54684 {% endcomment %}' - '问题若是包含同一存储库中文件路径长于 255 个字符的 blob 的永久链接，则无法关闭。{% comment %} https://github.com/github/github/issues/107731 {% endcomment %}' - '推送到 Gist 时，可能会在后接收挂钩时触发异常。{% comment %} https://github.com/github/github/issues/129091 {% endcomment %}' - '对 GitHub Connect 启用“用户可以搜索 GitHub.com”后，专用和内部存储库中的问题不包括在 GitHub.com 搜索结果中。{% comment %} https://github.com/github/admin-experience/issues/571 {% endcomment %}' diff --git a/translations/zh-CN/data/release-notes/enterprise-server/2-21/0.yml b/translations/zh-CN/data/release-notes/enterprise-server/2-21/0.yml index 7ff6239c4dee..75cbdf5940a8 100644 --- a/translations/zh-CN/data/release-notes/enterprise-server/2-21/0.yml +++ b/translations/zh-CN/data/release-notes/enterprise-server/2-21/0.yml @@ -3,9 +3,9 @@ sections: features: - '用户可以在从网页通知导航时可以就议题、拉请求及其他主题[管理通知](https://help.github.com/en/enterprise/2.21/user/github/managing-subscriptions-and-notifications-on-github/about-notifications)。{% comment %} https://github.com/github/enterprise-releases/issues/2135#issuecomment-633905096 {% endcomment %}' - '用户可以[将拉取请求转换回“草稿”](https://github.blog/changelog/2020-04-08-convert-pull-request-to-draft/) {% comment %} https://github.com/github/releases/issues/800 {% endcomment %}' - - '[多行建议](https://github.blog/changelog/2020-04-15-multi-line-code-sugutions-general-availability/)可让用户在审查拉取请求时建议对多行代码进行特定的更改。{% comment %} https://github.com/github/releases/issues/810 {% endcomment %}' + - '[多行建议](https://github.blog/changelog/2020-04-15-multi-line-code-sugutions-general-availability/) 可让用户在审查拉取请求时建议对多行代码进行特定的更改。{% comment %} https://github.com/github/releases/issues/810 {% endcomment %}' - '可以写入存储库的用户可以[隐藏作为“重复项”的议题评论或拉取请求](https://help.github.com/en/enterprise/2.21/user/github/building-a-strong-community/managing-disrutive-comments#hiding-a-comment)。{% comment %}https://github.com/github/github/pull/131746 {% endcomment %}' - - '当[从模板创建存储库](https://help.github.com/en/enterprise/2.21/user/github/creating-cloning-and-archiving-repositeries/creating-a-repository-from-a-template)时，用户可以选择性地选择包含所有分支，而不仅仅是默认分支。{% comment %} https://github.com/github/releases/issues/580 {% endcomment %}' + - '当[从模板创建存储库](https://help.github.com/en/enterprise/2.21/user/github/creating-cloning-and-archiving-repositeries/creating-a-repository-from-a-template) 时，用户可以选择性地选择包含所有分支，而不仅仅是默认分支。{% comment %} https://github.com/github/releases/issues/580 {% endcomment %}' - '[问题项目卡包含链接的拉取请求部分](https://github.blog/changelog/2020-02-04-project-issue-cards-include-linked-pull-requests/)，因此用户能够看到哪些开发工作与直接来源于项目板的问题有关。{% comment %} https://github.com/github/releases/issues/743 {% endcomment %}' - '反应 API 中有一组新的[“删除反应”终结点](https://developer.github.com/changes/2020-02-26-new-delete-reactions-endpoints/)。现有的“删除反应”终结点将在 2021 年初弃用。{% comment %} https://developer.github.com/changes/2020-02-26-new-delete-reactions-endpoints/ {% endcomment %}' - '有一组新的 [Teams API 终结点](https://developer.github.com/changes/2020-01-21-moving-the-team-api-endpoints/)，允许 GitHub 缩放并长期支持 Teams API。现有 API 终结点将在 2021 年初弃用。{% comment %} https://developer.github.com/changes/2020-01-21-moving-the-team-api-endpoints/ {% endcomment %}' @@ -37,7 +37,7 @@ sections: - '如果有超过 10 个令牌，“个人访问令牌”页面将超时。{% comment %} https://github.com/github/github/pull/132064 {% endcomment %}' - '计划的 LDAP 用户和团队同步任务可能会在先前计划的同步任务仍在进行中时开始。已经实施锁定机制来防止新的同步任务在运行时启动。{% comment %} https://github.com/github/github/pull/139205, https://github.com/github/support/issues/429, https://github.com/github/github/issues/54386, https://github.com/github/iam/issues/40 {% endcomment %}' changes: - - 'Web 通知界面，包括新的[状态](https://help.github.com/en/enterprise/2.21/user/github/managing-subscriptions-and-notifications-on-github/managing-notifications-from-your-inbox#triaging-options)、[筛选器](https://help.github.com/en/enterprise/2.21/user/github/managing-subscriptions-and-notifications-on-github/managing-notifications-from-your-inbox#supported-queries-for-custom-filters)和[快捷方式](https://help.github.com/en/enterprise/2.21/user/github/getting-started-with-github/keyboard-shortcuts#notifications)，已经更新。{% comment %} https://github.com/github/enterprise-releases/issues/2135#issuecomment-633905096 {% endcomment %}' + - 'Web 通知界面，包括新的[状态](https://help.github.com/en/enterprise/2.21/user/github/managing-subscriptions-and-notifications-on-github/managing-notifications-from-your-inbox#triaging-options)、[筛选器](https://help.github.com/en/enterprise/2.21/user/github/managing-subscriptions-and-notifications-on-github/managing-notifications-from-your-inbox#supported-queries-for-custom-filters) 和 [快捷方式](https://help.github.com/en/enterprise/2.21/user/github/getting-started-with-github/keyboard-shortcuts#notifications)，已经更新。{% comment %} https://github.com/github/enterprise-releases/issues/2135#issuecomment-633905096 {% endcomment %}' - '现在可以禁用在 LDAP 同步时重新激活 LDAP 用户。{% comment %} https://github.com/github/github/pull/139023 {% endcomment %}' - '已更新推送受保护分支措辞，以明确管理员总是可以推送，当状态检查通过时，具有维护角色的用户可以推送。{% comment %} https://github.com/github/github/pull/141555 {% endcomment %}' - '当建议与原始文本相同时，防止空白提交。{% comment %} https://github.com/github/github/pull/138587 {% endcomment %}' @@ -50,7 +50,7 @@ sections: - '管理员可以[启用安全警报](https://help.github.com/en/enterprise/2.21/admin/installation/enabling-security alerts-for-vulnerable-dependencies-on-github-enterprise-server#enabling-security-alerts-for-vulnerable-dependencies-for-vulnerable-dependencies-on-github-enterprise-server)，但禁用来自这些警报的所有通知。{% comment %} https://github.com/github/releases/issues/841 {% endcomment %}' - '页面日志显示访问 GitHub Pages 网站的用户登录。{% comment %} https://github.com/github/enterprise2/pull/19905 {% endcomment %}' - '企业成员可以导航到 `https://[ghes-hostname]/enterprises/[account-name]`，从一个视图查看他们作业企业帐户一部分所属的所有组织。{% comment %} https://github.com/github/releases/issues/832 {% endcomment %}' - - '[分类和维护角色的 REST API 支持](https://developer.github.com/changes/2020-04-07-explining-rest-api-support-for-the-triage-and-server-roles/)已扩展。{% comment %} https://github.com/github/releases/issues/748 {% endcomment %}' + - '[分类和维护角色的 REST API 支持](https://developer.github.com/changes/2020-04-07-explining-rest-api-support-for-the-triage-and-server-roles/) 已扩展。{% comment %} https://github.com/github/releases/issues/748 {% endcomment %}' - '用户可以使用 `@me` 搜索语法创建和分享解析到当前用户的搜索查询。{% comment %} https://github.com/github/github/pull/129624 {% endcomment %}' - '新发行模板配置选项已[添加](https://github.blog/changelog/2019-10-28-new-issue-template-configuration-options/)。{% comment %} https://github.com/github/releases/issues/660 {% endcomment %}' - 'MySQL 备份和恢复可靠性以及完成时间已得到改善。{% comment %} https://github.com/github/ghes-infrastructure/issues/162 {% endcomment %}' @@ -63,7 +63,7 @@ sections: known_issues: - '在新建的没有任何用户的 GitHub Enterprise Server 上，攻击者可以创建第一个管理员用户。{% comment %} https://github.com/github/enterprise2/issues/1889 {% endcomment %}' - '在升级期间不会维护自定义防火墙规则。{% comment %} https://github.com/github/enterprise2/issues/2823 {% endcomment %}' - - '[通过 Web 界面上传](https://github.com/blog/2105-upload-files-to-your-repositories)的 Git LFS 跟踪文件被错误地直接添加到存储库。{% comment %} https://github.com/github/github/issues/54684 {% endcomment %}' + - '[通过 Web 界面上传](https://github.com/blog/2105-upload-files-to-your-repositories) 的 Git LFS 跟踪文件被错误地直接添加到存储库。{% comment %} https://github.com/github/github/issues/54684 {% endcomment %}' - '如果问题包含同一存储库中文件路径长于 255 个字符的 blob 的永久链接，则问题无法关闭。{% comment %} https://github.com/github/github/issues/107731 {% endcomment %}' - '推送到 Gist 时，可能会在后接收挂钩期间触发异常。{% comment %} https://github.com/github/github/issues/129091 {% endcomment %}' - '在 GitHub Connect 中启用了“用户可以搜索 GitHub.com”时，专用和内部存储库中的问题不包括在 GitHub.com 搜索结果中。{% comment %} https://github.com/github/admin-experience/issues/571 {% endcomment %}' diff --git a/translations/zh-CN/data/release-notes/enterprise-server/2-21/1.yml b/translations/zh-CN/data/release-notes/enterprise-server/2-21/1.yml index 4550bee32a62..530bf9e5835f 100644 --- a/translations/zh-CN/data/release-notes/enterprise-server/2-21/1.yml +++ b/translations/zh-CN/data/release-notes/enterprise-server/2-21/1.yml @@ -12,7 +12,7 @@ sections: known_issues: - '在没有任何用户的新建 GitHub Enterprise Server 上，攻击者可能创建第一个管理员用户。{% comment %} https://github.com/github/enterprise2/issues/1889 {% endcomment %}' - '自定义防火墙规则在升级期间没有维护。{% comment %} https://github.com/github/enterprise2/issues/2823 {% endcomment %}' - - '[通过 Web 界面上传](https://github.com/blog/2105-upload-files-to-your-repositories)的 Git LFS 跟踪文件被错误地直接添加到存储库。{% comment %} https://github.com/github/github/issues/54684 {% endcomment %}' + - '[通过 Web 界面上传](https://github.com/blog/2105-upload-files-to-your-repositories) 的 Git LFS 跟踪文件被错误地直接添加到存储库。{% comment %} https://github.com/github/github/issues/54684 {% endcomment %}' - '问题若是包含同一存储库中文件路径长于 255 个字符的 blob 的永久链接，则无法关闭。{% comment %} https://github.com/github/github/issues/107731 {% endcomment %}' - '在 GitHub Connect 中启用了“用户可以搜索 GitHub.com”时，专用和内部存储库中的问题不包括在 GitHub.com 搜索结果中。{% comment %} https://github.com/github/admin-experience/issues/571 {% endcomment %}' - '在命令行上推送到存储库时不会报告安全警报。{% comment %} https://github.com/github/github/issues/143190 {% endcomment %}' diff --git a/translations/zh-CN/data/release-notes/enterprise-server/2-21/10.yml b/translations/zh-CN/data/release-notes/enterprise-server/2-21/10.yml index 9241ea8b92e4..a209d32b9e1a 100644 --- a/translations/zh-CN/data/release-notes/enterprise-server/2-21/10.yml +++ b/translations/zh-CN/data/release-notes/enterprise-server/2-21/10.yml @@ -7,7 +7,7 @@ sections: known_issues: - '在没有任何用户的新建 GitHub Enterprise Server 上，攻击者可能创建第一个管理员用户。{% comment %} https://github.com/github/enterprise2/issues/1889 {% endcomment %}' - '自定义防火墙规则在升级期间没有维护。{% comment %} https://github.com/github/enterprise2/issues/2823 {% endcomment %}' - - '[通过 Web 界面上传](https://github.com/blog/2105-upload-files-to-your-repositories)的 Git LFS 跟踪文件被错误地直接添加到存储库。{% comment %} https://github.com/github/github/issues/54684 {% endcomment %}' + - '[通过 Web 界面上传](https://github.com/blog/2105-upload-files-to-your-repositories) 的 Git LFS 跟踪文件被错误地直接添加到存储库。{% comment %} https://github.com/github/github/issues/54684 {% endcomment %}' - '问题若是包含同一存储库中文件路径长于 255 个字符的 blob 的永久链接，则无法关闭。{% comment %} https://github.com/github/github/issues/107731 {% endcomment %}' - '在 GitHub Connect 中启用了“用户可以搜索 GitHub.com”时，专用和内部存储库中的问题不包括在 GitHub.com 搜索结果中。{% comment %} https://github.com/github/admin-experience/issues/571 {% endcomment %}' - '在命令行上推送到存储库时不会报告安全警报。{% comment %} https://github.com/github/github/issues/143190 {% endcomment %}' diff --git a/translations/zh-CN/data/release-notes/enterprise-server/2-21/11.yml b/translations/zh-CN/data/release-notes/enterprise-server/2-21/11.yml index de748ef8f034..137e8f2e6683 100644 --- a/translations/zh-CN/data/release-notes/enterprise-server/2-21/11.yml +++ b/translations/zh-CN/data/release-notes/enterprise-server/2-21/11.yml @@ -10,7 +10,7 @@ sections: known_issues: - '在没有任何用户的新建 GitHub Enterprise Server 上，攻击者可能创建第一个管理员用户。{% comment %} https://github.com/github/enterprise2/issues/1889 {% endcomment %}' - '自定义防火墙规则在升级期间没有维护。{% comment %} https://github.com/github/enterprise2/issues/2823 {% endcomment %}' - - '[通过 Web 界面上传](https://github.com/blog/2105-upload-files-to-your-repositories)的 Git LFS 跟踪文件被错误地直接添加到存储库。{% comment %} https://github.com/github/github/issues/54684 {% endcomment %}' + - '[通过 Web 界面上传](https://github.com/blog/2105-upload-files-to-your-repositories) 的 Git LFS 跟踪文件被错误地直接添加到存储库。{% comment %} https://github.com/github/github/issues/54684 {% endcomment %}' - '问题若是包含同一存储库中文件路径长于 255 个字符的 blob 的永久链接，则无法关闭。{% comment %} https://github.com/github/github/issues/107731 {% endcomment %}' - '在 GitHub Connect 中启用了“用户可以搜索 GitHub.com”时，专用和内部存储库中的问题不包括在 GitHub.com 搜索结果中。{% comment %} https://github.com/github/admin-experience/issues/571 {% endcomment %}' - '在命令行上推送到存储库时不会报告安全警报。{% comment %} https://github.com/github/github/issues/143190 {% endcomment %}' diff --git a/translations/zh-CN/data/release-notes/enterprise-server/2-21/12.yml b/translations/zh-CN/data/release-notes/enterprise-server/2-21/12.yml index 7f68292a85ec..6e1c97938e36 100644 --- a/translations/zh-CN/data/release-notes/enterprise-server/2-21/12.yml +++ b/translations/zh-CN/data/release-notes/enterprise-server/2-21/12.yml @@ -9,7 +9,7 @@ sections: known_issues: - '在没有任何用户的新建 GitHub Enterprise Server 上，攻击者可以创建第一个管理员用户。{% comment %} https://github.com/github/enterprise2/issues/1889 {% endcomment %}' - '在升级期间不会维护自定义防火墙规则。{% comment %} https://github.com/github/enterprise2/issues/2823 {% endcomment %}' - - 'Git LFS 跟踪的[通过 Web 界面上传的](https://github.com/blog/2105-upload-files-to-your-repositories)文件被错误地直接添加到存储库。{% comment %} https://github.com/github/github/issues/54684 {% endcomment %}' + - 'Git LFS 跟踪的[通过 Web 界面上传的](https://github.com/blog/2105-upload-files-to-your-repositories) 文件被错误地直接添加到存储库。{% comment %} https://github.com/github/github/issues/54684 {% endcomment %}' - '如果问题包含指向同一存储库中文件路径长于 255 个字符的 blob 的永久链接，则无法关闭。{% comment %} https://github.com/github/github/issues/107731 {% endcomment %}' - '在 GitHub Connect 中启用了“用户可以搜索 GitHub.com”时，专用和内部存储库中的问题不包括在 GitHub.com 搜索结果中。{% comment %} https://github.com/github/admin-experience/issues/571 {% endcomment %}' - '在命令行上推送到存储库时不会报告安全警报。{% comment %} https://github.com/github/github/issues/143190 {% endcomment %}' diff --git a/translations/zh-CN/data/release-notes/enterprise-server/2-21/13.yml b/translations/zh-CN/data/release-notes/enterprise-server/2-21/13.yml index 23bb387e3be2..5075ebdd0e7c 100644 --- a/translations/zh-CN/data/release-notes/enterprise-server/2-21/13.yml +++ b/translations/zh-CN/data/release-notes/enterprise-server/2-21/13.yml @@ -12,7 +12,7 @@ sections: known_issues: - '在没有任何用户的新建 GitHub Enterprise Server 上，攻击者可能创建第一个管理员用户。{% comment %} https://github.com/github/enterprise2/issues/1889 {% endcomment %}' - '自定义防火墙规则在升级期间没有维护。{% comment %} https://github.com/github/enterprise2/issues/2823 {% endcomment %}' - - '[通过 Web 界面上传](https://github.com/blog/2105-upload-files-to-your-repositories)的 Git LFS 跟踪文件被错误地直接添加到存储库。{% comment %} https://github.com/github/github/issues/54684 {% endcomment %}' + - '[通过 Web 界面上传](https://github.com/blog/2105-upload-files-to-your-repositories) 的 Git LFS 跟踪文件被错误地直接添加到存储库。{% comment %} https://github.com/github/github/issues/54684 {% endcomment %}' - '问题若是包含同一存储库中文件路径长于 255 个字符的 blob 的永久链接，则无法关闭。{% comment %} https://github.com/github/github/issues/107731 {% endcomment %}' - '在 GitHub Connect 中启用了“用户可以搜索 GitHub.com”时，专用和内部存储库中的问题不包括在 GitHub.com 搜索结果中。{% comment %} https://github.com/github/admin-experience/issues/571 {% endcomment %}' - '在命令行上推送到存储库时不会报告安全警报。{% comment %} https://github.com/github/github/issues/143190 {% endcomment %}' diff --git a/translations/zh-CN/data/release-notes/enterprise-server/2-21/15.yml b/translations/zh-CN/data/release-notes/enterprise-server/2-21/15.yml index 20bd0c49a781..62516052e52f 100644 --- a/translations/zh-CN/data/release-notes/enterprise-server/2-21/15.yml +++ b/translations/zh-CN/data/release-notes/enterprise-server/2-21/15.yml @@ -21,12 +21,12 @@ sections: - '在闰年，用户在星期一尝试查看贡献活动时收到 404 响应。' - '无法访问浏览**部分，出现 500 内部服务器错误。' changes: - - '添加了对 [AWS EC2 r5b 实例类型](https://aws.amazon.com/about-aws/whats-new/2020/12/introducing-new-amazon-ec2-r5b-instances-feuring-60-gbps-of-ebbandwidth-260K-iops/)的支持。' + - '添加了对 [AWS EC2 r5b 实例类型](https://aws.amazon.com/about-aws/whats-new/2020/12/introducing-new-amazon-ec2-r5b-instances-feuring-60-gbps-of-ebbandwidth-260K-iops/) 的支持。' - '调整后台队列优先级，以更均匀地分配作业。' known_issues: - '在新建的没有任何用户的 GitHub Enterprise Server 上，攻击者可以创建第一个管理员用户。' - '在升级期间不会维护自定义防火墙规则。' - - '[通过 Web 界面上传](https://github.com/blog/2105-upload-files-to-your-repositories)的 Git LFS 跟踪文件被错误地直接添加到存储库。' + - '[通过 Web 界面上传](https://github.com/blog/2105-upload-files-to-your-repositories) 的 Git LFS 跟踪文件被错误地直接添加到存储库。' - '问题若是包含同一存储库中文件路径长于 255 个字符的 blob 的永久链接，则无法关闭。' - '对 GitHub Connect 启用“用户可以搜索 GitHub.com”后，专用和内部存储库中的问题不包括在 GitHub.com 搜索结果中。' - '推送到命令行上的仓库时，不会报告安全警报。' diff --git a/translations/zh-CN/data/release-notes/enterprise-server/2-21/16.yml b/translations/zh-CN/data/release-notes/enterprise-server/2-21/16.yml index a9364810d096..06206d549626 100644 --- a/translations/zh-CN/data/release-notes/enterprise-server/2-21/16.yml +++ b/translations/zh-CN/data/release-notes/enterprise-server/2-21/16.yml @@ -7,7 +7,7 @@ sections: known_issues: - 在没有任何用户的新设置的 GitHub Enterprise Server 上，攻击者可以创建第一个管理员用户。 - 在升级期间不会维护自定义防火墙规则。 - - "Git LFS 跟踪的[通过 Web 界面上传的](https://github.com/blog/2105-upload-files-to-your-repositories)文件被错误地直接添加到存储库。" + - "Git LFS 跟踪的[通过 Web 界面上传的](https://github.com/blog/2105-upload-files-to-your-repositories) 文件被错误地直接添加到存储库。" - 如果问题包含指向同一存储库中文件路径长于 255 个字符的 blob 的永久链接，则问题无法关闭。 - 在 GitHub Connect 中启用了“用户可以搜索 GitHub.com”时，专用和内部存储库中的问题不包括在 GitHub.com 搜索结果中。 - 在命令行上推送到存储库时不会报告安全警报。 diff --git a/translations/zh-CN/data/release-notes/enterprise-server/2-21/18.yml b/translations/zh-CN/data/release-notes/enterprise-server/2-21/18.yml index b6e86259eb87..f65df3fd2cbf 100644 --- a/translations/zh-CN/data/release-notes/enterprise-server/2-21/18.yml +++ b/translations/zh-CN/data/release-notes/enterprise-server/2-21/18.yml @@ -9,7 +9,7 @@ sections: known_issues: - 在没有任何用户的新设置的 GitHub Enterprise Server 上，攻击者可以创建第一个管理员用户。 - 在升级期间不会维护自定义防火墙规则。 - - "Git LFS 跟踪的[通过 Web 界面上传的](https://github.com/blog/2105-upload-files-to-your-repositories)文件被错误地直接添加到存储库。" + - "Git LFS 跟踪的[通过 Web 界面上传的](https://github.com/blog/2105-upload-files-to-your-repositories) 文件被错误地直接添加到存储库。" - 如果问题包含指向同一存储库中文件路径长于 255 个字符的 blob 的永久链接，则问题无法关闭。 - 在 GitHub Connect 中启用了“用户可以搜索 GitHub.com”时，专用和内部存储库中的问题不包括在 GitHub.com 搜索结果中。 - 在命令行上推送到存储库时不会报告安全警报。 diff --git a/translations/zh-CN/data/release-notes/enterprise-server/2-21/19.yml b/translations/zh-CN/data/release-notes/enterprise-server/2-21/19.yml index d9ccb888bb88..436dd85a410d 100644 --- a/translations/zh-CN/data/release-notes/enterprise-server/2-21/19.yml +++ b/translations/zh-CN/data/release-notes/enterprise-server/2-21/19.yml @@ -11,7 +11,7 @@ sections: known_issues: - 在没有任何用户的新建 GitHub Enterprise Server 上，攻击者可以创建第一个管理员用户。 - 在升级期间不会维护自定义防火墙规则。 - - "Git LFS 跟踪的[通过 Web 界面上传的](https://github.com/blog/2105-upload-files-to-your-repositories)文件被错误地直接添加到存储库。" + - "Git LFS 跟踪的[通过 Web 界面上传的](https://github.com/blog/2105-upload-files-to-your-repositories) 文件被错误地直接添加到存储库。" - 如果问题包含指向同一存储库中文件路径长于 255 个字符的 blob 的永久链接，则无法关闭。 - 在 GitHub Connect 中启用了“用户可以搜索 GitHub.com”时，专用和内部存储库中的问题不包括在 GitHub.com 搜索结果中。 - 在命令行上推送到存储库时不会报告安全警报。 diff --git a/translations/zh-CN/data/release-notes/enterprise-server/2-21/2.yml b/translations/zh-CN/data/release-notes/enterprise-server/2-21/2.yml index f3d8d4e4936e..3836c06a3f6c 100644 --- a/translations/zh-CN/data/release-notes/enterprise-server/2-21/2.yml +++ b/translations/zh-CN/data/release-notes/enterprise-server/2-21/2.yml @@ -12,7 +12,7 @@ sections: known_issues: - '在没有任何用户的新建 GitHub Enterprise Server 上，攻击者可以创建第一个管理员用户。{% comment %} https://github.com/github/enterprise2/issues/1889 {% endcomment %}' - '在升级期间不会维护自定义防火墙规则。{% comment %} https://github.com/github/enterprise2/issues/2823 {% endcomment %}' - - 'Git LFS 跟踪的[通过 Web 界面上传的](https://github.com/blog/2105-upload-files-to-your-repositories)文件被错误地直接添加到存储库。{% comment %} https://github.com/github/github/issues/54684 {% endcomment %}' + - 'Git LFS 跟踪的[通过 Web 界面上传的](https://github.com/blog/2105-upload-files-to-your-repositories) 文件被错误地直接添加到存储库。{% comment %} https://github.com/github/github/issues/54684 {% endcomment %}' - '如果问题包含指向同一存储库中文件路径长于 255 个字符的 blob 的永久链接，则无法关闭。{% comment %} https://github.com/github/github/issues/107731 {% endcomment %}' - '在 GitHub Connect 中启用了“用户可以搜索 GitHub.com”时，专用和内部存储库中的问题不包括在 GitHub.com 搜索结果中。{% comment %} https://github.com/github/admin-experience/issues/571 {% endcomment %}' - '在命令行上推送到存储库时不会报告安全警报。{% comment %} https://github.com/github/github/issues/143190 {% endcomment %}' diff --git a/translations/zh-CN/data/release-notes/enterprise-server/2-21/20.yml b/translations/zh-CN/data/release-notes/enterprise-server/2-21/20.yml index 35cf37ce02a1..625e12598b01 100644 --- a/translations/zh-CN/data/release-notes/enterprise-server/2-21/20.yml +++ b/translations/zh-CN/data/release-notes/enterprise-server/2-21/20.yml @@ -12,7 +12,7 @@ sections: known_issues: - 在新建的没有任何用户的 GitHub Enterprise Server 上，攻击者可以创建第一个管理员用户。 - 在升级期间不会维护自定义防火墙规则。 - - "[通过 Web 界面上传](https://github.com/blog/2105-upload-files-to-your-repositories)的 Git LFS 跟踪文件被错误地直接添加到存储库。" + - "[通过 Web 界面上传](https://github.com/blog/2105-upload-files-to-your-repositories) 的 Git LFS 跟踪文件被错误地直接添加到存储库。" - 如果问题包含文件路径长于 255 个字符的同一存储库中 blob 的永久链接，则问题无法关闭。 - 在 GitHub Connect 中启用了“用户可以搜索 GitHub.com”时，专用和内部存储库中的问题不包括在 GitHub.com 搜索结果中。 - 推送到命令行上的存储库时不报告安全警报。 diff --git a/translations/zh-CN/data/release-notes/enterprise-server/2-21/21.yml b/translations/zh-CN/data/release-notes/enterprise-server/2-21/21.yml index 6f3f8092e253..b3ff2396fe53 100644 --- a/translations/zh-CN/data/release-notes/enterprise-server/2-21/21.yml +++ b/translations/zh-CN/data/release-notes/enterprise-server/2-21/21.yml @@ -8,7 +8,7 @@ sections: known_issues: - 在新建的没有任何用户的 GitHub Enterprise Server 上，攻击者可以创建第一个管理员用户。 - 在升级期间不会维护自定义防火墙规则。 - - "[通过 Web 界面上传](https://github.com/blog/2105-upload-files-to-your-repositories)的 Git LFS 跟踪文件被错误地直接添加到存储库。" + - "[通过 Web 界面上传](https://github.com/blog/2105-upload-files-to-your-repositories) 的 Git LFS 跟踪文件被错误地直接添加到存储库。" - 问题若是包含同一存储库中文件路径长于 255 个字符的 blob 的永久链接，则无法关闭。 - 对 GitHub Connect 启用“用户可以搜索 GitHub.com”后，专用和内部存储库中的问题不包括在 GitHub.com 搜索结果中。 - 推送到命令行上的仓库时，不会报告安全警报。 diff --git a/translations/zh-CN/data/release-notes/enterprise-server/2-21/22.yml b/translations/zh-CN/data/release-notes/enterprise-server/2-21/22.yml index fd1d867027eb..984427aed346 100644 --- a/translations/zh-CN/data/release-notes/enterprise-server/2-21/22.yml +++ b/translations/zh-CN/data/release-notes/enterprise-server/2-21/22.yml @@ -9,7 +9,7 @@ sections: known_issues: - 在新建的没有任何用户的 GitHub Enterprise Server 上，攻击者可能创建第一个管理员用户。 - 在升级期间不会维护自定义防火墙规则。 - - "Git LFS 跟踪的[通过 Web 界面上传的](https://github.com/blog/2105-upload-files-to-your-repositories)文件被错误地直接添加到存储库。" + - "Git LFS 跟踪的[通过 Web 界面上传的](https://github.com/blog/2105-upload-files-to-your-repositories) 文件被错误地直接添加到存储库。" - 如果问题包含指向同一存储库中文件路径长于 255 个字符的 blob 的永久链接，则无法关闭。 - 在 GitHub Connect 中启用了“用户可以搜索 GitHub.com”时，专用和内部存储库中的问题不包括在 GitHub.com 搜索结果中。 - 推送到命令行上的存储库时，不会报告安全警报。 diff --git a/translations/zh-CN/data/release-notes/enterprise-server/2-21/3.yml b/translations/zh-CN/data/release-notes/enterprise-server/2-21/3.yml index 61e9cc25c1a3..33960c105d2c 100644 --- a/translations/zh-CN/data/release-notes/enterprise-server/2-21/3.yml +++ b/translations/zh-CN/data/release-notes/enterprise-server/2-21/3.yml @@ -9,7 +9,7 @@ sections: known_issues: - '在没有任何用户的新建 GitHub Enterprise Server 上，攻击者可能创建第一个管理员用户。{% comment %} https://github.com/github/enterprise2/issues/1889 {% endcomment %}' - '自定义防火墙规则在升级期间没有维护。{% comment %} https://github.com/github/enterprise2/issues/2823 {% endcomment %}' - - '[通过 Web 界面上传](https://github.com/blog/2105-upload-files-to-your-repositories)的 Git LFS 跟踪文件被错误地直接添加到存储库。{% comment %} https://github.com/github/github/issues/54684 {% endcomment %}' + - '[通过 Web 界面上传](https://github.com/blog/2105-upload-files-to-your-repositories) 的 Git LFS 跟踪文件被错误地直接添加到存储库。{% comment %} https://github.com/github/github/issues/54684 {% endcomment %}' - '问题若是包含同一存储库中文件路径长于 255 个字符的 blob 的永久链接，则无法关闭。{% comment %} https://github.com/github/github/issues/107731 {% endcomment %}' - '在 GitHub Connect 中启用了“用户可以搜索 GitHub.com”时，专用和内部存储库中的问题不包括在 GitHub.com 搜索结果中。{% comment %} https://github.com/github/admin-experience/issues/571 {% endcomment %}' - '在命令行上推送到存储库时不会报告安全警报。{% comment %} https://github.com/github/github/issues/143190 {% endcomment %}' diff --git a/translations/zh-CN/data/release-notes/enterprise-server/2-21/4.yml b/translations/zh-CN/data/release-notes/enterprise-server/2-21/4.yml index fe8a7af32a53..88503711fa74 100644 --- a/translations/zh-CN/data/release-notes/enterprise-server/2-21/4.yml +++ b/translations/zh-CN/data/release-notes/enterprise-server/2-21/4.yml @@ -19,7 +19,7 @@ sections: known_issues: - '在没有任何用户的新建 GitHub Enterprise Server 上，攻击者可能创建第一个管理员用户。{% comment %} https://github.com/github/enterprise2/issues/1889 {% endcomment %}' - '自定义防火墙规则在升级期间没有维护。{% comment %} https://github.com/github/enterprise2/issues/2823 {% endcomment %}' - - '[通过 Web 界面上传](https://github.com/blog/2105-upload-files-to-your-repositories)的 Git LFS 跟踪文件被错误地直接添加到存储库。{% comment %} https://github.com/github/github/issues/54684 {% endcomment %}' + - '[通过 Web 界面上传](https://github.com/blog/2105-upload-files-to-your-repositories) 的 Git LFS 跟踪文件被错误地直接添加到存储库。{% comment %} https://github.com/github/github/issues/54684 {% endcomment %}' - '问题若是包含同一存储库中文件路径长于 255 个字符的 blob 的永久链接，则无法关闭。{% comment %} https://github.com/github/github/issues/107731 {% endcomment %}' - '在 GitHub Connect 中启用了“用户可以搜索 GitHub.com”时，专用和内部存储库中的问题不包括在 GitHub.com 搜索结果中。{% comment %} https://github.com/github/admin-experience/issues/571 {% endcomment %}' - '在命令行上推送到存储库时不会报告安全警报。{% comment %} https://github.com/github/github/issues/143190 {% endcomment %}' diff --git a/translations/zh-CN/data/release-notes/enterprise-server/2-21/5.yml b/translations/zh-CN/data/release-notes/enterprise-server/2-21/5.yml index f80dee5edb4d..72818d403641 100644 --- a/translations/zh-CN/data/release-notes/enterprise-server/2-21/5.yml +++ b/translations/zh-CN/data/release-notes/enterprise-server/2-21/5.yml @@ -7,7 +7,7 @@ sections: known_issues: - '在没有任何用户的新建 GitHub Enterprise Server 上，攻击者可以创建第一个管理员用户。{% comment %} https://github.com/github/enterprise2/issues/1889 {% endcomment %}' - '在升级期间不会维护自定义防火墙规则。{% comment %} https://github.com/github/enterprise2/issues/2823 {% endcomment %}' - - 'Git LFS 跟踪的[通过 Web 界面上传的](https://github.com/blog/2105-upload-files-to-your-repositories)文件被错误地直接添加到存储库。{% comment %} https://github.com/github/github/issues/54684 {% endcomment %}' + - 'Git LFS 跟踪的[通过 Web 界面上传的](https://github.com/blog/2105-upload-files-to-your-repositories) 文件被错误地直接添加到存储库。{% comment %} https://github.com/github/github/issues/54684 {% endcomment %}' - '如果问题包含同一存储库中文件路径长于 255 个字符的 blob 的永久链接，则无法关闭。{% comment %} https://github.com/github/github/issues/107731 {% endcomment %}' - '在 GitHub Connect 中启用了“用户可以搜索 GitHub.com”时，专用和内部存储库中的问题不包括在 GitHub.com 搜索结果中。{% comment %} https://github.com/github/admin-experience/issues/571 {% endcomment %}' - '在命令行上推送到存储库时不会报告安全警报。{% comment %} https://github.com/github/github/issues/143190 {% endcomment %}' diff --git a/translations/zh-CN/data/release-notes/enterprise-server/2-21/7.yml b/translations/zh-CN/data/release-notes/enterprise-server/2-21/7.yml index b3467f5f1cbc..91ff25ca7a3c 100644 --- a/translations/zh-CN/data/release-notes/enterprise-server/2-21/7.yml +++ b/translations/zh-CN/data/release-notes/enterprise-server/2-21/7.yml @@ -7,7 +7,7 @@ sections: known_issues: - '在新建的没有任何用户的 GitHub Enterprise Server 上，攻击者可以创建第一个管理员用户。{% comment %} https://github.com/github/enterprise2/issues/1889 {% endcomment %}' - '在升级期间不会维护自定义防火墙规则。{% comment %} https://github.com/github/enterprise2/issues/2823 {% endcomment %}' - - '[通过 Web 界面上传](https://github.com/blog/2105-upload-files-to-your-repositories)的 Git LFS 跟踪的文件被错误地直接添加到存储库。{% comment %} https://github.com/github/github/issues/54684 {% endcomment %}' + - '[通过 Web 界面上传](https://github.com/blog/2105-upload-files-to-your-repositories) 的 Git LFS 跟踪的文件被错误地直接添加到存储库。{% comment %} https://github.com/github/github/issues/54684 {% endcomment %}' - '问题若是包含同一存储库中文件路径长于 255 个字符的 blob 的永久链接，则无法关闭。{% comment %} https://github.com/github/github/issues/107731 {% endcomment %}' - '对 GitHub Connect 启用“用户可以搜索 GitHub.com”后，专用和内部存储库中的问题不包括在 GitHub.com 搜索结果中。{% comment %} https://github.com/github/admin-experience/issues/571 {% endcomment %}' - '推送到命令行上的仓库时，不会报告安全警报。{% comment %} https://github.com/github/github/issues/143190 {% endcomment %}' diff --git a/translations/zh-CN/data/release-notes/enterprise-server/2-21/8.yml b/translations/zh-CN/data/release-notes/enterprise-server/2-21/8.yml index 2834cac6c712..8eff6b03a84e 100644 --- a/translations/zh-CN/data/release-notes/enterprise-server/2-21/8.yml +++ b/translations/zh-CN/data/release-notes/enterprise-server/2-21/8.yml @@ -8,7 +8,7 @@ sections: known_issues: - '在新建的没有任何用户的 GitHub Enterprise Server 上，攻击者可以创建第一个管理员用户。{% comment %} https://github.com/github/enterprise2/issues/1889 {% endcomment %}' - '在升级期间不会维护自定义防火墙规则。{% comment %} https://github.com/github/enterprise2/issues/2823 {% endcomment %}' - - '[通过 Web 界面上传](https://github.com/blog/2105-upload-files-to-your-repositories)的 Git LFS 跟踪的文件被错误地直接添加到存储库。{% comment %} https://github.com/github/github/issues/54684 {% endcomment %}' + - '[通过 Web 界面上传](https://github.com/blog/2105-upload-files-to-your-repositories) 的 Git LFS 跟踪的文件被错误地直接添加到存储库。{% comment %} https://github.com/github/github/issues/54684 {% endcomment %}' - '问题若是包含同一存储库中文件路径长于 255 个字符的 blob 的永久链接，则无法关闭。{% comment %} https://github.com/github/github/issues/107731 {% endcomment %}' - '对 GitHub Connect 启用“用户可以搜索 GitHub.com”后，专用和内部存储库中的问题不包括在 GitHub.com 搜索结果中。{% comment %} https://github.com/github/admin-experience/issues/571 {% endcomment %}' - '推送到命令行上的仓库时，不会报告安全警报。{% comment %} https://github.com/github/github/issues/143190 {% endcomment %}' diff --git a/translations/zh-CN/data/release-notes/enterprise-server/2-22/10.yml b/translations/zh-CN/data/release-notes/enterprise-server/2-22/10.yml index 4fbde7ebaa83..ff6775fba448 100644 --- a/translations/zh-CN/data/release-notes/enterprise-server/2-22/10.yml +++ b/translations/zh-CN/data/release-notes/enterprise-server/2-22/10.yml @@ -10,7 +10,7 @@ sections: known_issues: - 在没有任何用户的新建 GitHub Enterprise Server 上，攻击者可以创建第一个管理员用户。 - 在升级期间不会维护自定义防火墙规则。 - - "Git LFS 跟踪的[通过 Web 界面上传的](https://github.com/blog/2105-upload-files-to-your-repositories)文件被错误地直接添加到存储库。" + - "Git LFS 跟踪的[通过 Web 界面上传的](https://github.com/blog/2105-upload-files-to-your-repositories) 文件被错误地直接添加到存储库。" - 如果问题包含指向同一存储库中文件路径长于 255 个字符的 blob 的永久链接，则无法关闭。 - 在 GitHub Connect 中启用了“用户可以搜索 GitHub.com”时，专用和内部存储库中的问题不包括在 GitHub.com 搜索结果中。 - "当副本节点在高可用性配置中脱机时，{% data variables.product.product_name %} 仍可能将 {% data variables.product.prodname_pages %} 请求路由到脱机节点，从而减少用户的 {% data variables.product.prodname_pages %} 可用性。" diff --git a/translations/zh-CN/data/release-notes/enterprise-server/2-22/11.yml b/translations/zh-CN/data/release-notes/enterprise-server/2-22/11.yml index 5c160dca8ce2..18d2b0d53faf 100644 --- a/translations/zh-CN/data/release-notes/enterprise-server/2-22/11.yml +++ b/translations/zh-CN/data/release-notes/enterprise-server/2-22/11.yml @@ -13,7 +13,7 @@ sections: known_issues: - 在新建的没有任何用户的 GitHub Enterprise Server 上，攻击者可以创建第一个管理员用户。 - 在升级期间不会维护自定义防火墙规则。 - - "[通过 Web 界面上传](https://github.com/blog/2105-upload-files-to-your-repositories)的 Git LFS 跟踪文件被错误地直接添加到存储库。" + - "[通过 Web 界面上传](https://github.com/blog/2105-upload-files-to-your-repositories) 的 Git LFS 跟踪文件被错误地直接添加到存储库。" - 如果问题包含文件路径长于 255 个字符的同一存储库中 blob 的永久链接，则问题无法关闭。 - 在 GitHub Connect 中启用了“用户可以搜索 GitHub.com”时，专用和内部存储库中的问题不包括在 GitHub.com 搜索结果中。 - "当副本节点在高可用性配置下离线时，{% data variables.product.product_name %} 仍可能将 {% data variables.product.prodname_pages %} 请求路由到离线节点，从而减少用户的 {% data variables.product.prodname_pages %} 可用性。" diff --git a/translations/zh-CN/data/release-notes/enterprise-server/2-22/12.yml b/translations/zh-CN/data/release-notes/enterprise-server/2-22/12.yml index 5cc9632ff81c..47a2a7d55538 100644 --- a/translations/zh-CN/data/release-notes/enterprise-server/2-22/12.yml +++ b/translations/zh-CN/data/release-notes/enterprise-server/2-22/12.yml @@ -16,7 +16,7 @@ sections: known_issues: - 在没有任何用户的新建 GitHub Enterprise Server 上，攻击者可能创建第一个管理员用户。 - 在升级期间不会维护自定义防火墙规则。 - - "[通过 Web 界面上传](https://github.com/blog/2105-upload-files-to-your-repositories)的 Git LFS 跟踪文件被错误地直接添加到存储库。" + - "[通过 Web 界面上传](https://github.com/blog/2105-upload-files-to-your-repositories) 的 Git LFS 跟踪文件被错误地直接添加到存储库。" - 问题若是包含同一存储库中文件路径长于 255 个字符的 blob 的永久链接，则无法关闭。 - 对 GitHub Connect 启用“用户可以搜索 GitHub.com”后，专用和内部存储库中的问题不包括在 GitHub.com 搜索结果中。 - "当副本节点在高可用性配置下离线时，{% data variables.product.product_name %} 仍可能将 {% data variables.product.prodname_pages %} 请求路由到离线节点，从而减少用户的 {% data variables.product.prodname_pages %} 可用性。" diff --git a/translations/zh-CN/data/release-notes/enterprise-server/2-22/13.yml b/translations/zh-CN/data/release-notes/enterprise-server/2-22/13.yml index 6b86c7620b67..c89983a37e34 100644 --- a/translations/zh-CN/data/release-notes/enterprise-server/2-22/13.yml +++ b/translations/zh-CN/data/release-notes/enterprise-server/2-22/13.yml @@ -14,7 +14,7 @@ sections: known_issues: - 在新建的没有任何用户的 GitHub Enterprise Server 上，攻击者可以创建第一个管理员用户。 - 在升级期间不会维护自定义防火墙规则。 - - "[通过 Web 界面上传](https://github.com/blog/2105-upload-files-to-your-repositories)的 Git LFS 跟踪文件被错误地直接添加到存储库。" + - "[通过 Web 界面上传](https://github.com/blog/2105-upload-files-to-your-repositories) 的 Git LFS 跟踪文件被错误地直接添加到存储库。" - 问题若是包含同一存储库中文件路径长于 255 个字符的 blob 的永久链接，则无法关闭。 - 对 GitHub Connect 启用“用户可以搜索 GitHub.com”后，专用和内部存储库中的问题不包括在 GitHub.com 搜索结果中。 - "当副本节点在高可用性配置下离线时，{% data variables.product.product_name %} 仍可能将 {% data variables.product.prodname_pages %} 请求路由到离线节点，从而减少用户的 {% data variables.product.prodname_pages %} 可用性。" diff --git a/translations/zh-CN/data/release-notes/enterprise-server/2-22/14.yml b/translations/zh-CN/data/release-notes/enterprise-server/2-22/14.yml index bad192aca256..1de6e632c54c 100644 --- a/translations/zh-CN/data/release-notes/enterprise-server/2-22/14.yml +++ b/translations/zh-CN/data/release-notes/enterprise-server/2-22/14.yml @@ -12,7 +12,7 @@ sections: known_issues: - 在没有任何用户的新建 GitHub Enterprise Server 上，攻击者可能创建第一个管理员用户。 - 在升级期间不会维护自定义防火墙规则。 - - "[通过 Web 界面上传](https://github.com/blog/2105-upload-files-to-your-repositories)的 Git LFS 跟踪文件被错误地直接添加到存储库。" + - "[通过 Web 界面上传](https://github.com/blog/2105-upload-files-to-your-repositories) 的 Git LFS 跟踪文件被错误地直接添加到存储库。" - 问题若是包含同一存储库中文件路径长于 255 个字符的 blob 的永久链接，则无法关闭。 - 对 GitHub Connect 启用“用户可以搜索 GitHub.com”后，专用和内部存储库中的问题不包括在 GitHub.com 搜索结果中。 - "当副本节点在高可用性配置下离线时，{% data variables.product.product_name %} 仍可能将 {% data variables.product.prodname_pages %} 请求路由到离线节点，从而减少用户的 {% data variables.product.prodname_pages %} 可用性。" diff --git a/translations/zh-CN/data/release-notes/enterprise-server/2-22/15.yml b/translations/zh-CN/data/release-notes/enterprise-server/2-22/15.yml index a15bc73c4ad2..b2418e49acfd 100644 --- a/translations/zh-CN/data/release-notes/enterprise-server/2-22/15.yml +++ b/translations/zh-CN/data/release-notes/enterprise-server/2-22/15.yml @@ -10,7 +10,7 @@ sections: known_issues: - 在新建的没有任何用户的 GitHub Enterprise Server 上，攻击者可以创建第一个管理员用户。 - 自定义防火墙规则在升级过程中被删除。 - - "[通过 Web 界面上传](https://github.com/blog/2105-upload-files-to-your-repositories)的 Git LFS 跟踪文件被错误地直接添加到存储库。" + - "[通过 Web 界面上传](https://github.com/blog/2105-upload-files-to-your-repositories) 的 Git LFS 跟踪文件被错误地直接添加到存储库。" - 如果问题包含文件路径长于 255 个字符的同一存储库中 blob 的永久链接，则问题无法关闭。 - 在 GitHub Connect 中启用了“用户可以搜索 GitHub.com”时，专用和内部存储库中的问题不包括在 GitHub.com 搜索结果中。 - "当副本节点在高可用性配置下离线时，{% data variables.product.product_name %} 仍可能将 {% data variables.product.prodname_pages %} 请求路由到离线节点，从而减少用户的 {% data variables.product.prodname_pages %} 可用性。" diff --git a/translations/zh-CN/data/release-notes/enterprise-server/2-22/16.yml b/translations/zh-CN/data/release-notes/enterprise-server/2-22/16.yml index b3ef76089333..66c4f4b6803f 100644 --- a/translations/zh-CN/data/release-notes/enterprise-server/2-22/16.yml +++ b/translations/zh-CN/data/release-notes/enterprise-server/2-22/16.yml @@ -9,7 +9,7 @@ sections: known_issues: - 在没有任何用户的新建 GitHub Enterprise Server 上，攻击者可以创建第一个管理员用户。 - 将在升级过程中删除自定义防火墙规则。 - - "Git LFS 跟踪的[通过 Web 界面上传的](https://github.com/blog/2105-upload-files-to-your-repositories)文件被错误地直接添加到存储库。" + - "Git LFS 跟踪的[通过 Web 界面上传的](https://github.com/blog/2105-upload-files-to-your-repositories) 文件被错误地直接添加到存储库。" - 如果问题包含指向同一存储库中 blob 文件路径长于 255 个字符的 blob 的永久链接，则无法关闭。 - 在 GitHub Connect 中启用了“用户可以搜索 GitHub.com”时，专用和内部存储库中的问题不包括在 GitHub.com 搜索结果中。 - "当副本节点在高可用性配置中脱机时，{% data variables.product.product_name %} 仍可能将 {% data variables.product.prodname_pages %} 请求路由到脱机节点，从而减少用户的 {% data variables.product.prodname_pages %} 可用性。" diff --git a/translations/zh-CN/data/release-notes/enterprise-server/2-22/17.yml b/translations/zh-CN/data/release-notes/enterprise-server/2-22/17.yml index e344b6c696a2..c7fa8fcb2cdd 100644 --- a/translations/zh-CN/data/release-notes/enterprise-server/2-22/17.yml +++ b/translations/zh-CN/data/release-notes/enterprise-server/2-22/17.yml @@ -14,7 +14,7 @@ sections: known_issues: - 在新建的没有任何用户的 GitHub Enterprise Server 上，攻击者可能创建第一个管理员用户。 - 自定义防火墙规则在升级过程中被删除。 - - "Git LFS 跟踪的[通过 Web 界面上传的](https://github.com/blog/2105-upload-files-to-your-repositories)文件被错误地直接添加到存储库。" + - "Git LFS 跟踪的[通过 Web 界面上传的](https://github.com/blog/2105-upload-files-to-your-repositories) 文件被错误地直接添加到存储库。" - 如果问题包含指向同一存储库中文件路径长于 255 个字符的 blob 的永久链接，则无法关闭。 - 在 GitHub Connect 中启用了“用户可以搜索 GitHub.com”时，专用和内部存储库中的问题不包括在 GitHub.com 搜索结果中。 - "当副本节点在高可用性配置下脱机时，{% data variables.product.product_name %} 仍可能会将 {% data variables.product.prodname_pages %} 请求路由到脱机节点，从而减少用户的 {% data variables.product.prodname_pages %} 可用性。" diff --git a/translations/zh-CN/data/release-notes/enterprise-server/2-22/18.yml b/translations/zh-CN/data/release-notes/enterprise-server/2-22/18.yml index 84386623296e..ffb96a3509e7 100644 --- a/translations/zh-CN/data/release-notes/enterprise-server/2-22/18.yml +++ b/translations/zh-CN/data/release-notes/enterprise-server/2-22/18.yml @@ -10,7 +10,7 @@ sections: known_issues: - "在新建的没有任何用户的 {% data variables.product.prodname_ghe_server %} 上，攻击者可以创建第一个管理员用户。" - 自定义防火墙规则在升级过程中被删除。 - - "[通过 Web 界面上传](https://github.com/blog/2105-upload-files-to-your-repositories)的 Git LFS 跟踪文件被错误地直接添加到存储库。" + - "[通过 Web 界面上传](https://github.com/blog/2105-upload-files-to-your-repositories) 的 Git LFS 跟踪文件被错误地直接添加到存储库。" - 问题若是包含同一存储库中文件路径长于 255 个字符的 blob 的永久链接，则无法关闭。 - 对 GitHub Connect 启用“用户可以搜索 GitHub.com”后，专用和内部存储库中的问题不包括在 GitHub.com 搜索结果中。 - "当副本节点在高可用性配置下离线时，{% data variables.product.product_name %} 仍可能将 {% data variables.product.prodname_pages %} 请求路由到离线节点，从而减少用户的 {% data variables.product.prodname_pages %} 可用性。" diff --git a/translations/zh-CN/data/release-notes/enterprise-server/2-22/19.yml b/translations/zh-CN/data/release-notes/enterprise-server/2-22/19.yml index 9da19f2fd0f7..9fb7ef341698 100644 --- a/translations/zh-CN/data/release-notes/enterprise-server/2-22/19.yml +++ b/translations/zh-CN/data/release-notes/enterprise-server/2-22/19.yml @@ -7,7 +7,7 @@ sections: known_issues: - "在新建的没有任何用户的 {% data variables.product.prodname_ghe_server %} 上，攻击者可以创建第一个管理员用户。" - 自定义防火墙规则在升级过程中被删除。 - - "[通过 Web 界面上传](https://github.com/blog/2105-upload-files-to-your-repositories)的 Git LFS 跟踪文件被错误地直接添加到存储库。" + - "[通过 Web 界面上传](https://github.com/blog/2105-upload-files-to-your-repositories) 的 Git LFS 跟踪文件被错误地直接添加到存储库。" - 问题若是包含同一存储库中文件路径长于 255 个字符的 blob 的永久链接，则无法关闭。 - 对 GitHub Connect 启用“用户可以搜索 GitHub.com”后，专用和内部存储库中的问题不包括在 GitHub.com 搜索结果中。 - "当副本节点在高可用性配置下离线时，{% data variables.product.product_name %} 仍可能将 {% data variables.product.prodname_pages %} 请求路由到离线节点，从而减少用户的 {% data variables.product.prodname_pages %} 可用性。" diff --git a/translations/zh-CN/data/release-notes/enterprise-server/2-22/20.yml b/translations/zh-CN/data/release-notes/enterprise-server/2-22/20.yml index de294794b947..b0f45e8bb4a4 100644 --- a/translations/zh-CN/data/release-notes/enterprise-server/2-22/20.yml +++ b/translations/zh-CN/data/release-notes/enterprise-server/2-22/20.yml @@ -4,11 +4,11 @@ sections: - 包已更新到最新的安全版本。 bugs: - 与自动更新相关的日志消息（`添加 h/m/s 随机时间。`）被记录到系统日志中。 - - "导致请求失败的内部 API 的 Git 挂钩返回异常`未定义 \"success\":String 的方法主体(NoMethodError)`，而不是返回显式的 `nil`。" + - "导致请求失败的内部 API 的 Git 挂钩返回异常`未定义 \"success\":String 的方法主体 (NoMethodError)`，而不是返回显式的 `nil`。" known_issues: - "在没有任何用户的新建 {% data variables.product.prodname_ghe_server %} 上，攻击者可以创建第一个管理员用户。" - 自定义防火墙规则在升级过程中被移除。 - - "Git LFS 跟踪的[通过 Web 界面上传的](https://github.com/blog/2105-upload-files-to-your-repositories)文件被错误地直接添加到存储库。" + - "Git LFS 跟踪的[通过 Web 界面上传的](https://github.com/blog/2105-upload-files-to-your-repositories) 文件被错误地直接添加到存储库。" - 如果问题包含同一存储库中文件路径长于 255 个字符的 blob 的永久链接，则无法关闭。 - 在 GitHub Connect 中启用了“用户可以搜索 GitHub.com”时，专用和内部存储库中的问题不包括在 GitHub.com 搜索结果中。 - "当副本节点在高可用性配置下脱机时，{% data variables.product.product_name %} 仍可能将 {% data variables.product.prodname_pages %} 请求路由到脱机节点，从而减少用户的 {% data variables.product.prodname_pages %} 可用性。" diff --git a/translations/zh-CN/data/release-notes/enterprise-server/2-22/21.yml b/translations/zh-CN/data/release-notes/enterprise-server/2-22/21.yml index fb986a446563..63fa97294316 100644 --- a/translations/zh-CN/data/release-notes/enterprise-server/2-22/21.yml +++ b/translations/zh-CN/data/release-notes/enterprise-server/2-22/21.yml @@ -5,7 +5,7 @@ sections: known_issues: - "在新建的没有任何用户的 {% data variables.product.prodname_ghe_server %} 上，攻击者可能创建第一个管理员用户。" - 自定义防火墙规则在升级过程中被删除。 - - "Git LFS 跟踪的[通过 Web 界面上传的](https://github.com/blog/2105-upload-files-to-your-repositories)文件被错误地直接添加到存储库。" + - "Git LFS 跟踪的[通过 Web 界面上传的](https://github.com/blog/2105-upload-files-to-your-repositories) 文件被错误地直接添加到存储库。" - 如果问题包含指向同一存储库中文件路径长于 255 个字符的 blob 的永久链接，则无法关闭。 - 在 GitHub Connect 中启用了“用户可以搜索 GitHub.com”时，专用和内部存储库中的问题不包括在 GitHub.com 搜索结果中。 - "当副本节点在高可用性配置下脱机时，{% data variables.product.product_name %} 仍可能会将 {% data variables.product.prodname_pages %} 请求路由到脱机节点，从而减少用户的 {% data variables.product.prodname_pages %} 可用性。" diff --git a/translations/zh-CN/data/release-notes/enterprise-server/2-22/4.yml b/translations/zh-CN/data/release-notes/enterprise-server/2-22/4.yml index 89218b634dfe..c856ed8be6fd 100644 --- a/translations/zh-CN/data/release-notes/enterprise-server/2-22/4.yml +++ b/translations/zh-CN/data/release-notes/enterprise-server/2-22/4.yml @@ -12,7 +12,7 @@ sections: known_issues: - "在没有任何用户的新建 GitHub Enterprise Server 上，攻击者可能创建第一个管理员用户。{% comment %} https://github.com/github/enterprise2/issues/1889 {% endcomment %}" - "自定义防火墙规则在升级期间没有维护。{% comment %} https://github.com/github/enterprise2/issues/2823 {% endcomment %}" - - "[通过 Web 界面上传](https://github.com/blog/2105-upload-files-to-your-repositories)的 Git LFS 跟踪文件被错误地直接添加到存储库。{% comment %} https://github.com/github/github/issues/54684 {% endcomment %}" + - "[通过 Web 界面上传](https://github.com/blog/2105-upload-files-to-your-repositories) 的 Git LFS 跟踪文件被错误地直接添加到存储库。{% comment %} https://github.com/github/github/issues/54684 {% endcomment %}" - "问题若是包含同一存储库中文件路径长于 255 个字符的 blob 的永久链接，则无法关闭。{% comment %} https://github.com/github/github/issues/107731 {% endcomment %}" - "在 GitHub Connect 中启用了“用户可以搜索 GitHub.com”时，专用和内部存储库中的问题不包括在 GitHub.com 搜索结果中。{% comment %} https://github.com/github/admin-experience/issues/571 {% endcomment %}" - "当副本节点在高可用性配置下离线时，{% data variables.product.product_name %} 仍可能将 {% data variables.product.prodname_pages %} 请求路由到离线节点，从而减少用户的 {% data variables.product.prodname_pages %} 可用性。" diff --git a/translations/zh-CN/data/release-notes/enterprise-server/2-22/5.yml b/translations/zh-CN/data/release-notes/enterprise-server/2-22/5.yml index a4e0915993ca..45df00109879 100644 --- a/translations/zh-CN/data/release-notes/enterprise-server/2-22/5.yml +++ b/translations/zh-CN/data/release-notes/enterprise-server/2-22/5.yml @@ -16,7 +16,7 @@ sections: known_issues: - '在新建的没有任何用户的 GitHub Enterprise Server 上，攻击者可以创建第一个管理员用户。{% comment %} https://github.com/github/enterprise2/issues/1889 {% endcomment %}' - '在升级期间不会维护自定义防火墙规则。{% comment %} https://github.com/github/enterprise2/issues/2823 {% endcomment %}' - - '[通过 Web 界面上传](https://github.com/blog/2105-upload-files-to-your-repositories)的 Git LFS 跟踪的文件被错误地直接添加到存储库。{% comment %} https://github.com/github/github/issues/54684 {% endcomment %}' + - '[通过 Web 界面上传](https://github.com/blog/2105-upload-files-to-your-repositories) 的 Git LFS 跟踪的文件被错误地直接添加到存储库。{% comment %} https://github.com/github/github/issues/54684 {% endcomment %}' - '问题若是包含同一存储库中文件路径长于 255 个字符的 blob 的永久链接，则无法关闭。{% comment %} https://github.com/github/github/issues/107731 {% endcomment %}' - '对 GitHub Connect 启用“用户可以搜索 GitHub.com”后，专用和内部存储库中的问题不包括在 GitHub.com 搜索结果中。{% comment %} https://github.com/github/admin-experience/issues/571 {% endcomment %}' - '当副本节点在高可用性配置下离线时，{% data variables.product.product_name %} 仍可能将 {% data variables.product.prodname_pages %} 请求路由到离线节点，从而减少用户的 {% data variables.product.prodname_pages %} 可用性。' diff --git a/translations/zh-CN/data/release-notes/enterprise-server/2-22/6.yml b/translations/zh-CN/data/release-notes/enterprise-server/2-22/6.yml index 7a16711fe356..e31c9bf37ad3 100644 --- a/translations/zh-CN/data/release-notes/enterprise-server/2-22/6.yml +++ b/translations/zh-CN/data/release-notes/enterprise-server/2-22/6.yml @@ -12,7 +12,7 @@ sections: known_issues: - '在没有任何用户的新建 GitHub Enterprise Server 上，攻击者可能创建第一个管理员用户。{% comment %} https://github.com/github/enterprise2/issues/1889 {% endcomment %}' - '自定义防火墙规则在升级期间没有维护。{% comment %} https://github.com/github/enterprise2/issues/2823 {% endcomment %}' - - '[通过 Web 界面上传](https://github.com/blog/2105-upload-files-to-your-repositories)的 Git LFS 跟踪文件被错误地直接添加到存储库。{% comment %} https://github.com/github/github/issues/54684 {% endcomment %}' + - '[通过 Web 界面上传](https://github.com/blog/2105-upload-files-to-your-repositories) 的 Git LFS 跟踪文件被错误地直接添加到存储库。{% comment %} https://github.com/github/github/issues/54684 {% endcomment %}' - '问题若是包含同一存储库中文件路径长于 255 个字符的 blob 的永久链接，则无法关闭。{% comment %} https://github.com/github/github/issues/107731 {% endcomment %}' - '在 GitHub Connect 中启用了“用户可以搜索 GitHub.com”时，专用和内部存储库中的问题不包括在 GitHub.com 搜索结果中。{% comment %} https://github.com/github/admin-experience/issues/571 {% endcomment %}' - '当副本节点在高可用性配置下离线时，{% data variables.product.product_name %} 仍可能将 {% data variables.product.prodname_pages %} 请求路由到离线节点，从而减少用户的 {% data variables.product.prodname_pages %} 可用性。' diff --git a/translations/zh-CN/data/release-notes/enterprise-server/3-0/0-rc1.yml b/translations/zh-CN/data/release-notes/enterprise-server/3-0/0-rc1.yml index f6bc03f21e1c..56148f1df111 100644 --- a/translations/zh-CN/data/release-notes/enterprise-server/3-0/0-rc1.yml +++ b/translations/zh-CN/data/release-notes/enterprise-server/3-0/0-rc1.yml @@ -1,7 +1,7 @@ date: '2021-01-12' release_candidate: true deprecated: true -intro: "应在非生产环境中测试候选发布版。有关候选发布计划的更多信息，请参阅 [GitHub 博客](https://github.blog/2020-12-03-improving-the-ghes-release-process-release-candidates/)或“[关于升级到新版本](/admin/overview/about-upgrades-to-new-releases)”。" +intro: "应在非生产环境中测试候选发布版。有关候选发布计划的更多信息，请参阅 [GitHub 博客](https://github.blog/2020-12-03-improving-the-ghes-release-process-release-candidates/) 或“[关于升级到新版本](/admin/overview/about-upgrades-to-new-releases)”。" sections: bugs: - 已更改几个日志文件的格式，包括为不同的日志类型添加了一个 PID。此更改不会影响 GitHub Enterprise Support 使用支持包来解决问题的方法。 @@ -10,7 +10,7 @@ sections: - "在新建的没有任何用户的 {% data variables.product.prodname_ghe_server %} 上，攻击者可以创建第一个管理员用户。" - 候选发布版 1 不支持群集模式。 - 在升级期间不会维护自定义防火墙规则。 - - "Git LFS 跟踪的文件[通过 Web 界面上传](https://github.blog/2016-02-18-upload-files-to-your-repositories/)被错误地直接添加到存储库。" + - "Git LFS 跟踪的文件[通过 Web 界面上传](https://github.blog/2016-02-18-upload-files-to-your-repositories/) 被错误地直接添加到存储库。" - 对 GitHub Connect 启用“用户可以搜索 GitHub.com”后，专用和内部存储库中的问题不包括在 GitHub.com 搜索结果中。 - 在尝试设置 Actions 未成功后，如果禁用 Actions，你将无法创建第一个用户，也无法使用设备 - 未保存“必要消息已查看”审核日志事件 diff --git a/translations/zh-CN/data/release-notes/enterprise-server/3-0/0-rc2.yml b/translations/zh-CN/data/release-notes/enterprise-server/3-0/0-rc2.yml index d3e33bd45695..88b12c8c1232 100644 --- a/translations/zh-CN/data/release-notes/enterprise-server/3-0/0-rc2.yml +++ b/translations/zh-CN/data/release-notes/enterprise-server/3-0/0-rc2.yml @@ -1,7 +1,7 @@ date: '2021-01-29' release_candidate: true deprecated: true -intro: "应在非生产环境中测试候选发布版。有关候选发布计划的更多信息，请参阅 [GitHub 博客](https://github.blog/2020-12-03-improving-the-ghes-release-process-release-candidates/)或“[关于升级到新版本](/admin/overview/about-upgrades-to-new-releases)”。" +intro: "应在非生产环境中测试候选发布版。有关候选发布计划的更多信息，请参阅 [GitHub 博客](https://github.blog/2020-12-03-improving-the-ghes-release-process-release-candidates/) 或“[关于升级到新版本](/admin/overview/about-upgrades-to-new-releases)”。" sections: bugs: - heading: 修复候选发布 1 中的已知问题 diff --git a/translations/zh-CN/data/release-notes/enterprise-server/3-0/0.yml b/translations/zh-CN/data/release-notes/enterprise-server/3-0/0.yml index 36d3d58fab1a..3b972a783312 100644 --- a/translations/zh-CN/data/release-notes/enterprise-server/3-0/0.yml +++ b/translations/zh-CN/data/release-notes/enterprise-server/3-0/0.yml @@ -85,76 +85,4 @@ sections: - heading: Default branch renaming notes: - | - Enterprise and organization administrators can now set the default branch name for new repositories. Enterprise administrators can also enforce their choice of default branch name across all organizations or allow individual organizations to choose their own. - - Existing repositories are unaffected by these settings, and their default branch name will not be changed. - - {% note %} - - The default branch for newly-created repositories will be set to `main` in GHES 3.1, unless you opt out by setting the default branch setting at the enterprise level. - - {% endnote %} - - This change is one of many changes GitHub is making to support projects and maintainers that want to rename their default branch. To learn more about the changes we're making, see [github/renaming](https://github.com/github/renaming). - - bugs: - - heading: Fixes for known issues from Release Candidates - notes: - - All known issues from Release Candidate 1 and Release Candidate 2 have been fixed, except those listed in the Known Issues section below. - - heading: Fixes for other issues - notes: - - Issues with migrations and upgrades to 3.0.0 have been fixed. - - Backup Utilities versioning now works for release candidate versions. - - Generating a support bundle resulted in an error in the orchestrator logs. - - A large restore could result in Redis running out of memory. - - The checkbox to enable GitHub Actions in the Management Console is now visible with any authentication method. - - GitHub Actions could be enabled if the required storage was also configured. - - '`ghe-repl-status` could silently fail if MSSQL replication was not configured.' - - The format of several log files have changed, including the addition of a PID for different log types. This does not affect how GitHub Enterprise Support uses support bundles to troubleshoot issues. - - A PATCH request to the webhook configuration API no longer erases the webhook secret. - - Certain types of pre-receive hooks were failing. - - 'The Packages NuGet service now normalizes semantic versions on publish. An invalid semantic version (for example: v1.0.0.0.0.0) is not downloadable by NuGet clients and therefore a NuGet service is expected to normalize those versions (for example: v1.0.0.0.0.0 --> v1.0.0). Any original, non-normalized, version will be available in the `verbatimVersion` field. No changes to client configurations are required.' - - known_issues: - - On a freshly set up {% data variables.product.prodname_ghe_server %} without any users, an attacker could create the first admin user. - - Custom firewall rules are not maintained during an upgrade. - - Git LFS tracked files [uploaded through the web interface](https://github.blog/2016-02-18-upload-files-to-your-repositories/) are incorrectly added directly to the repository. - - 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. - - When maintenance mode is enabled, some services continue to be listed as "active processes". The services identified are expected to run during maintenance mode. If you experience this issue and are unsure, contact {% data variables.contact.contact_ent_support %}. - - When GitHub Actions is enabled, use '`ghe-maintenance -u`' to unset maintenance mode. - - 'Duplicated logging to `/var/log/messages`, `/var/log/syslog`, and `/var/log/user.log` results in increased root volume utilization.' - - Users can dismiss a mandatory message without checking all checkboxes. - - '[Pre-receive hook scripts](/admin/policies/enforcing-policy-with-pre-receive-hooks) cannot write temporary files, which may cause script execution to fail. Users who use pre-receive hooks should test in a staging environment to see if scripts require write access.' - - Repository [deploy keys](/developers/overview/managing-deploy-keys) are unable to be used with repositories containing LFS objects. - - Jupyter Notebook rendering in the web UI may fail if the notebook includes non-ASCII UTF-8 characters. - - reStructuredText (RST) rendering in the web UI may fail and instead display raw RST markup text. - - Dependency graph fails to parse `setup.py` Python manifest files, resulting in HTTP 500 errors in logs. This, combined with the duplicated logging issue, results in increased root volume utilization. - - A race condition can cause dependency graph database migrations to appear to fail. - - Instances with a custom timezone that were upgraded from an earlier release of GitHub Enterprise Server may have incorrect timestamps in the web UI. - - Old builds of Pages are not cleaned up, which could fill up the user disk (`/data/user/`). - - When deleting a branch after merging a pull request, an error message appears although the branch deletion succeeds. - - When a replica node is offline in a high availability configuration, {% data variables.product.product_name %} may still route {% data variables.product.prodname_pages %} requests to the offline node, reducing the availability of {% data variables.product.prodname_pages %} for users. - - Resource limits that are specific to processing pre-receive hooks may cause some pre-receive hooks to fail. - - deprecations: - - heading: Deprecation of GitHub Enterprise Server 2.19 - notes: - - '**{% data variables.product.prodname_ghe_server %} 2.19 is deprecated as of November 12, 2020**. That means that no patch releases will be made, even for critical security issues, after this date. For better performance, improved security, and new features, [upgrade to the newest version of {% data variables.product.prodname_ghe_server %}](https://help.github.com/enterprise/admin/guides/installation/upgrading-github-enterprise/) as soon as possible.' - - heading: Deprecation of Legacy GitHub App Webhook Events - notes: - - Starting with {% data variables.product.prodname_ghe_server %} 2.21.0 two legacy GitHub Apps-related webhook events have been deprecated and will be removed in {% data variables.product.prodname_ghe_server %} 3.2.0. The deprecated events `integration_installation` and `integration_installation_repositories` have equivalent events which will be supported. More information is available in the [deprecation announcement blog post](https://developer.github.com/changes/2020-04-15-replacing-the-installation-and-installation-repositories-events/). - - heading: Deprecation of Legacy GitHub Apps Endpoint - notes: - - Starting with {% data variables.product.prodname_ghe_server %} 2.21.0 the legacy GitHub Apps endpoint for creating installation access tokens was deprecated and will be removed in {% data variables.product.prodname_ghe_server %} 3.2.0. More information is available in the [deprecation announcement blog post](https://developer.github.com/changes/2020-04-15-replacing-create-installation-access-token-endpoint/). - - heading: Deprecation of OAuth Application API - notes: - - GitHub no longer supports the OAuth application endpoints that contain `access_token` as a path parameter. We have introduced new endpoints that allow you to securely manage tokens for OAuth Apps by moving `access_token` to the request body. While deprecated, the endpoints are still accessible in this version. We intend to remove these endpoints on {% data variables.product.prodname_ghe_server %} 3.4. For more information, see the [deprecation announcement blog post](https://developer.github.com/changes/2020-02-14-deprecating-oauth-app-endpoint/). - - heading: Deprecation of support for Semiotic - notes: - - The service supported a "Find by Symbol" experience in the pull request view that was not widely used. - - heading: Deprecation of workflow commands - notes: - - '{% data variables.product.prodname_actions %} `set-env` and `add-path` workflow commands have been deprecated. For more information, see the [changelog](https://github.blog/changelog/2020-10-01-github-actions-deprecating-set-env-and-add-path-commands/).' - - backups: - - '{% data variables.product.prodname_ghe_server %} 3.0 requires at least [GitHub Enterprise Backup Utilities 3.0.0](https://github.com/github/backup-utils) for [Backups and Disaster Recovery](/enterprise-server@3.0/admin/configuration/configuring-backups-on-your-appliance).' + Enterp \ No newline at end of file diff --git a/translations/zh-CN/data/release-notes/enterprise-server/3-0/10.yml b/translations/zh-CN/data/release-notes/enterprise-server/3-0/10.yml index 1d7b2535a633..12c50d1a3287 100644 --- a/translations/zh-CN/data/release-notes/enterprise-server/3-0/10.yml +++ b/translations/zh-CN/data/release-notes/enterprise-server/3-0/10.yml @@ -12,7 +12,7 @@ sections: known_issues: - 在新建的没有任何用户的 GitHub Enterprise Server 上，攻击者可以创建第一个管理员用户。 - 自定义防火墙规则在升级过程中被删除。 - - "[通过 Web 界面上传](https://github.com/blog/2105-upload-files-to-your-repositories)的 Git LFS 跟踪文件被错误地直接添加到存储库。" + - "[通过 Web 界面上传](https://github.com/blog/2105-upload-files-to-your-repositories) 的 Git LFS 跟踪文件被错误地直接添加到存储库。" - 问题若是包含同一存储库中文件路径长于 255 个字符的 blob 的永久链接，则无法关闭。 - 对 GitHub Connect 启用“用户可以搜索 GitHub.com”后，专用和内部存储库中的问题不包括在 GitHub.com 搜索结果中。 - "当副本节点在高可用性配置下离线时，{% data variables.product.product_name %} 仍可能将 {% data variables.product.prodname_pages %} 请求路由到离线节点，从而减少用户的 {% data variables.product.prodname_pages %} 可用性。" diff --git a/translations/zh-CN/data/release-notes/enterprise-server/3-0/11.yml b/translations/zh-CN/data/release-notes/enterprise-server/3-0/11.yml index 7abc22b1f880..b32d6600bf77 100644 --- a/translations/zh-CN/data/release-notes/enterprise-server/3-0/11.yml +++ b/translations/zh-CN/data/release-notes/enterprise-server/3-0/11.yml @@ -19,7 +19,7 @@ sections: known_issues: - 在没有任何用户的新建 GitHub Enterprise Server 上，攻击者可能创建第一个管理员用户。 - 自定义防火墙规则在升级过程中被删除。 - - "[通过 Web 界面上传](https://github.com/blog/2105-upload-files-to-your-repositories)的 Git LFS 跟踪文件被错误地直接添加到存储库。" + - "[通过 Web 界面上传](https://github.com/blog/2105-upload-files-to-your-repositories) 的 Git LFS 跟踪文件被错误地直接添加到存储库。" - 问题若是包含同一存储库中文件路径长于 255 个字符的 blob 的永久链接，则无法关闭。 - 对 GitHub Connect 启用“用户可以搜索 GitHub.com”后，专用和内部存储库中的问题不包括在 GitHub.com 搜索结果中。 - "当副本节点在高可用性配置下离线时，{% data variables.product.product_name %} 仍可能将 {% data variables.product.prodname_pages %} 请求路由到离线节点，从而减少用户的 {% data variables.product.prodname_pages %} 可用性。" diff --git a/translations/zh-CN/data/release-notes/enterprise-server/3-0/12.yml b/translations/zh-CN/data/release-notes/enterprise-server/3-0/12.yml index 83ed9e4d38a4..4beb227eef03 100644 --- a/translations/zh-CN/data/release-notes/enterprise-server/3-0/12.yml +++ b/translations/zh-CN/data/release-notes/enterprise-server/3-0/12.yml @@ -14,7 +14,7 @@ sections: known_issues: - "在新建的没有任何用户的 {% data variables.product.prodname_ghe_server %} 上，攻击者可以创建第一个管理员用户。" - 自定义防火墙规则在升级过程中被删除。 - - "[通过 Web 界面上传](https://github.com/blog/2105-upload-files-to-your-repositories)的 Git LFS 跟踪文件被错误地直接添加到存储库。" + - "[通过 Web 界面上传](https://github.com/blog/2105-upload-files-to-your-repositories) 的 Git LFS 跟踪文件被错误地直接添加到存储库。" - 问题若是包含同一存储库中文件路径长于 255 个字符的 blob 的永久链接，则无法关闭。 - 对 GitHub Connect 启用“用户可以搜索 GitHub.com”后，专用和内部存储库中的问题不包括在 GitHub.com 搜索结果中。 - "当副本节点在高可用性配置下离线时，{% data variables.product.product_name %} 仍可能将 {% data variables.product.prodname_pages %} 请求路由到离线节点，从而减少用户的 {% data variables.product.prodname_pages %} 可用性。" diff --git a/translations/zh-CN/data/release-notes/enterprise-server/3-0/13.yml b/translations/zh-CN/data/release-notes/enterprise-server/3-0/13.yml index dbc8a9831ce0..d5f69b52c697 100644 --- a/translations/zh-CN/data/release-notes/enterprise-server/3-0/13.yml +++ b/translations/zh-CN/data/release-notes/enterprise-server/3-0/13.yml @@ -10,7 +10,7 @@ sections: known_issues: - "在新建的没有任何用户的 {% data variables.product.prodname_ghe_server %} 上，攻击者可能创建第一个管理员用户。" - 自定义防火墙规则在升级过程中被删除。 - - "Git LFS 跟踪的[通过 Web 界面上传的](https://github.com/blog/2105-upload-files-to-your-repositories)文件被错误地直接添加到存储库。" + - "Git LFS 跟踪的[通过 Web 界面上传的](https://github.com/blog/2105-upload-files-to-your-repositories) 文件被错误地直接添加到存储库。" - 如果问题包含指向同一存储库中文件路径长于 255 个字符的 blob 的永久链接，则无法关闭。 - 在 GitHub Connect 中启用了“用户可以搜索 GitHub.com”时，专用和内部存储库中的问题不包括在 GitHub.com 搜索结果中。 - "当副本节点在高可用性配置下脱机时，{% data variables.product.product_name %} 仍可能会将 {% data variables.product.prodname_pages %} 请求路由到脱机节点，从而减少用户的 {% data variables.product.prodname_pages %} 可用性。" diff --git a/translations/zh-CN/data/release-notes/enterprise-server/3-0/14.yml b/translations/zh-CN/data/release-notes/enterprise-server/3-0/14.yml index 152449a873ca..3669c5a896ff 100644 --- a/translations/zh-CN/data/release-notes/enterprise-server/3-0/14.yml +++ b/translations/zh-CN/data/release-notes/enterprise-server/3-0/14.yml @@ -14,7 +14,7 @@ sections: known_issues: - "在新建的没有任何用户的 {% data variables.product.prodname_ghe_server %} 上，攻击者可以创建第一个管理员用户。" - 将在升级过程中删除自定义防火墙规则。 - - "Git LFS 跟踪的[通过 Web 界面上传的](https://github.com/blog/2105-upload-files-to-your-repositories)文件被错误地直接添加到存储库。" + - "Git LFS 跟踪的[通过 Web 界面上传的](https://github.com/blog/2105-upload-files-to-your-repositories) 文件被错误地直接添加到存储库。" - 如果问题包含指向同一存储库中 blob 文件路径长于 255 个字符的 blob 的永久链接，则无法关闭。 - 在 GitHub Connect 中启用了“用户可以搜索 GitHub.com”时，专用和内部存储库中的问题不包括在 GitHub.com 搜索结果中。 - "当副本节点在高可用性配置中脱机时，{% data variables.product.product_name %} 仍可能将 {% data variables.product.prodname_pages %} 请求路由到脱机节点，从而减少用户的 {% data variables.product.prodname_pages %} 可用性。" diff --git a/translations/zh-CN/data/release-notes/enterprise-server/3-0/15.yml b/translations/zh-CN/data/release-notes/enterprise-server/3-0/15.yml index 73505c64219d..3fbc1efb1817 100644 --- a/translations/zh-CN/data/release-notes/enterprise-server/3-0/15.yml +++ b/translations/zh-CN/data/release-notes/enterprise-server/3-0/15.yml @@ -10,7 +10,7 @@ sections: known_issues: - "在新建的没有任何用户的 {% data variables.product.prodname_ghe_server %} 上，攻击者可以创建第一个管理员用户。" - 自定义防火墙规则在升级过程中被删除。 - - "[通过 Web 界面上传](https://github.com/blog/2105-upload-files-to-your-repositories)的 Git LFS 跟踪文件被错误地直接添加到存储库。" + - "[通过 Web 界面上传](https://github.com/blog/2105-upload-files-to-your-repositories) 的 Git LFS 跟踪文件被错误地直接添加到存储库。" - 问题若是包含同一存储库中文件路径长于 255 个字符的 blob 的永久链接，则无法关闭。 - 对 GitHub Connect 启用“用户可以搜索 GitHub.com”后，专用和内部存储库中的问题不包括在 GitHub.com 搜索结果中。 - "当副本节点在高可用性配置下离线时，{% data variables.product.product_name %} 仍可能将 {% data variables.product.prodname_pages %} 请求路由到离线节点，从而减少用户的 {% data variables.product.prodname_pages %} 可用性。" diff --git a/translations/zh-CN/data/release-notes/enterprise-server/3-0/16.yml b/translations/zh-CN/data/release-notes/enterprise-server/3-0/16.yml index cf2c76bcb0c8..076f8c50bc9a 100644 --- a/translations/zh-CN/data/release-notes/enterprise-server/3-0/16.yml +++ b/translations/zh-CN/data/release-notes/enterprise-server/3-0/16.yml @@ -11,7 +11,7 @@ sections: known_issues: - "在新建的没有任何用户的 {% data variables.product.prodname_ghe_server %} 上，攻击者可以创建第一个管理员用户。" - 自定义防火墙规则在升级过程中被删除。 - - "[通过 Web 界面上传](https://github.com/blog/2105-upload-files-to-your-repositories)的 Git LFS 跟踪文件被错误地直接添加到存储库。" + - "[通过 Web 界面上传](https://github.com/blog/2105-upload-files-to-your-repositories) 的 Git LFS 跟踪文件被错误地直接添加到存储库。" - 问题若是包含同一存储库中文件路径长于 255 个字符的 blob 的永久链接，则无法关闭。 - 对 GitHub Connect 启用“用户可以搜索 GitHub.com”后，专用和内部存储库中的问题不包括在 GitHub.com 搜索结果中。 - "当副本节点在高可用性配置下离线时，{% data variables.product.product_name %} 仍可能将 {% data variables.product.prodname_pages %} 请求路由到离线节点，从而减少用户的 {% data variables.product.prodname_pages %} 可用性。" diff --git a/translations/zh-CN/data/release-notes/enterprise-server/3-0/17.yml b/translations/zh-CN/data/release-notes/enterprise-server/3-0/17.yml index ce84c24a9985..7fdbc4c67a71 100644 --- a/translations/zh-CN/data/release-notes/enterprise-server/3-0/17.yml +++ b/translations/zh-CN/data/release-notes/enterprise-server/3-0/17.yml @@ -18,7 +18,7 @@ sections: known_issues: - "在没有任何用户的新建 {% data variables.product.prodname_ghe_server %} 上，攻击者可以创建第一个管理员用户。" - 自定义防火墙规则在升级过程中被移除。 - - "Git LFS 跟踪的[通过 Web 界面上传的](https://github.com/blog/2105-upload-files-to-your-repositories)文件被错误地直接添加到存储库。" + - "Git LFS 跟踪的[通过 Web 界面上传的](https://github.com/blog/2105-upload-files-to-your-repositories) 文件被错误地直接添加到存储库。" - 如果问题包含同一存储库中文件路径长于 255 个字符的 blob 的永久链接，则无法关闭。 - 在 GitHub Connect 中启用了“用户可以搜索 GitHub.com”时，专用和内部存储库中的问题不包括在 GitHub.com 搜索结果中。 - "当副本节点在高可用性配置下脱机时，{% data variables.product.product_name %} 仍可能将 {% data variables.product.prodname_pages %} 请求路由到脱机节点，从而减少用户的 {% data variables.product.prodname_pages %} 可用性。" diff --git a/translations/zh-CN/data/release-notes/enterprise-server/3-0/18.yml b/translations/zh-CN/data/release-notes/enterprise-server/3-0/18.yml index 2eb40f01e6e4..1103417c6277 100644 --- a/translations/zh-CN/data/release-notes/enterprise-server/3-0/18.yml +++ b/translations/zh-CN/data/release-notes/enterprise-server/3-0/18.yml @@ -8,7 +8,7 @@ sections: known_issues: - "在新建的没有任何用户的 {% data variables.product.prodname_ghe_server %} 上，攻击者可以创建第一个管理员用户。" - 自定义防火墙规则在升级过程中被删除。 - - "[通过 Web 界面上传](https://github.com/blog/2105-upload-files-to-your-repositories)的 Git LFS 跟踪文件被错误地直接添加到存储库。" + - "[通过 Web 界面上传](https://github.com/blog/2105-upload-files-to-your-repositories) 的 Git LFS 跟踪文件被错误地直接添加到存储库。" - 问题若是包含同一存储库中文件路径长于 255 个字符的 blob 的永久链接，则无法关闭。 - 对 GitHub Connect 启用“用户可以搜索 GitHub.com”后，专用和内部存储库中的问题不包括在 GitHub.com 搜索结果中。 - "当副本节点在高可用性配置下离线时，{% data variables.product.product_name %} 仍可能将 {% data variables.product.prodname_pages %} 请求路由到离线节点，从而减少用户的 {% data variables.product.prodname_pages %} 可用性。" diff --git a/translations/zh-CN/data/release-notes/enterprise-server/3-0/19.yml b/translations/zh-CN/data/release-notes/enterprise-server/3-0/19.yml index c474915c0c0f..25ddf7941703 100644 --- a/translations/zh-CN/data/release-notes/enterprise-server/3-0/19.yml +++ b/translations/zh-CN/data/release-notes/enterprise-server/3-0/19.yml @@ -16,7 +16,7 @@ sections: known_issues: - "在新建的没有任何用户的 {% data variables.product.prodname_ghe_server %} 上，攻击者可以创建第一个管理员用户。" - 自定义防火墙规则在升级过程中被删除。 - - "[通过 Web 界面上传](https://github.com/blog/2105-upload-files-to-your-repositories)的 Git LFS 跟踪文件被错误地直接添加到存储库。" + - "[通过 Web 界面上传](https://github.com/blog/2105-upload-files-to-your-repositories) 的 Git LFS 跟踪文件被错误地直接添加到存储库。" - 问题若是包含同一存储库中文件路径长于 255 个字符的 blob 的永久链接，则无法关闭。 - 对 GitHub Connect 启用“用户可以搜索 GitHub.com”后，专用和内部存储库中的问题不包括在 GitHub.com 搜索结果中。 - "当副本节点在高可用性配置下离线时，{% data variables.product.product_name %} 仍可能将 {% data variables.product.prodname_pages %} 请求路由到离线节点，从而减少用户的 {% data variables.product.prodname_pages %} 可用性。" diff --git a/translations/zh-CN/data/release-notes/enterprise-server/3-0/20.yml b/translations/zh-CN/data/release-notes/enterprise-server/3-0/20.yml index 1cc77e86b169..9418c4fe542c 100644 --- a/translations/zh-CN/data/release-notes/enterprise-server/3-0/20.yml +++ b/translations/zh-CN/data/release-notes/enterprise-server/3-0/20.yml @@ -14,7 +14,7 @@ sections: known_issues: - "在新建的没有任何用户的 {% data variables.product.prodname_ghe_server %} 上，攻击者可以创建第一个管理员用户。" - 自定义防火墙规则在升级过程中被删除。 - - "[通过 Web 界面上传](https://github.com/blog/2105-upload-files-to-your-repositories)的 Git LFS 跟踪文件被错误地直接添加到存储库。" + - "[通过 Web 界面上传](https://github.com/blog/2105-upload-files-to-your-repositories) 的 Git LFS 跟踪文件被错误地直接添加到存储库。" - 问题若是包含同一存储库中文件路径长于 255 个字符的 blob 的永久链接，则无法关闭。 - 对 GitHub Connect 启用“用户可以搜索 GitHub.com”后，专用和内部存储库中的问题不包括在 GitHub.com 搜索结果中。 - "当副本节点在高可用性配置下离线时，{% data variables.product.product_name %} 仍可能将 {% data variables.product.prodname_pages %} 请求路由到离线节点，从而减少用户的 {% data variables.product.prodname_pages %} 可用性。" diff --git a/translations/zh-CN/data/release-notes/enterprise-server/3-0/22.yml b/translations/zh-CN/data/release-notes/enterprise-server/3-0/22.yml index c2407b0ed861..ad1f63619e0b 100644 --- a/translations/zh-CN/data/release-notes/enterprise-server/3-0/22.yml +++ b/translations/zh-CN/data/release-notes/enterprise-server/3-0/22.yml @@ -1,12 +1,12 @@ date: '2021-12-13' sections: security_fixes: - - '{% octicon "alert" aria-label="The alert icon" %} **严重：**在 Log4j 库中发现远程代码执行漏洞，该漏洞会影响 3.3.1 之前的所有 {% data variables.product.prodname_ghe_server %} 版本，漏洞编号为[CVE-2021-44228](https://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2021-44228)。Log4j 库用于在 {% data variables.product.prodname_ghe_server %} 实例上运行的开源服务。已在 {% data variables.product.prodname_ghe_server %} 3.0.22、3.1.14、3.2.6 和 3.3.1 中修复该漏洞。 有关详细信息，请参阅 GitHub 博客[文章](https://github.blog/2021-12-13-githubs-response-to-log4j-vulnerability-cve-2021-44228/)。' + - '{% octicon "alert" aria-label="The alert icon" %} **严重：**在 Log4j 库中发现远程代码执行漏洞，该漏洞会影响 3.3.1 之前的所有 {% data variables.product.prodname_ghe_server %} 版本，漏洞编号为[CVE-2021-44228](https://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2021-44228)。Log4j 库用于在 {% data variables.product.prodname_ghe_server %} 实例上运行的开源服务。已在 {% data variables.product.prodname_ghe_server %} 3.0.22、3.1.14、3.2.6 和 3.3.1 中修复该漏洞。有关详细信息，请参阅 GitHub 博客 [文章](https://github.blog/2021-12-13-githubs-response-to-log4j-vulnerability-cve-2021-44228/)。' - '**2021 年 12 月 17 日更新**：此版本中的修复也能缓解在该版本之后发布的 [CVE-2021-45046](https://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2021-45046)。无需再升级 {% data variables.product.prodname_ghe_server %}，即可缓解 CVE-2021-44228 和 CVE-2021-45046。' known_issues: - "在新建的没有任何用户的 {% data variables.product.prodname_ghe_server %} 上，攻击者可以创建第一个管理员用户。" - 自定义防火墙规则在升级过程中被删除。 - - "[通过 Web 界面上传](https://github.com/blog/2105-upload-files-to-your-repositories)的 Git LFS 跟踪文件被错误地直接添加到存储库。" + - "[通过 Web 界面上传](https://github.com/blog/2105-upload-files-to-your-repositories) 的 Git LFS 跟踪文件被错误地直接添加到存储库。" - 问题若是包含同一存储库中文件路径长于 255 个字符的 blob 的永久链接，则无法关闭。 - 对 GitHub Connect 启用“用户可以搜索 GitHub.com”后，专用和内部存储库中的问题不包括在 GitHub.com 搜索结果中。 - "当副本节点在高可用性配置下离线时，{% data variables.product.product_name %} 仍可能将 {% data variables.product.prodname_pages %} 请求路由到离线节点，从而减少用户的 {% data variables.product.prodname_pages %} 可用性。" diff --git a/translations/zh-CN/data/release-notes/enterprise-server/3-0/23.yml b/translations/zh-CN/data/release-notes/enterprise-server/3-0/23.yml index 0ea086a5a9f2..98897d783656 100644 --- a/translations/zh-CN/data/release-notes/enterprise-server/3-0/23.yml +++ b/translations/zh-CN/data/release-notes/enterprise-server/3-0/23.yml @@ -12,7 +12,7 @@ sections: known_issues: - "在新建的没有任何用户的 {% data variables.product.prodname_ghe_server %} 上，攻击者可以创建第一个管理员用户。" - 自定义防火墙规则在升级过程中被删除。 - - "[通过 Web 界面上传](https://github.com/blog/2105-upload-files-to-your-repositories)的 Git LFS 跟踪文件被错误地直接添加到存储库。" + - "[通过 Web 界面上传](https://github.com/blog/2105-upload-files-to-your-repositories) 的 Git LFS 跟踪文件被错误地直接添加到存储库。" - 问题若是包含同一存储库中文件路径长于 255 个字符的 blob 的永久链接，则无法关闭。 - 对 GitHub Connect 启用“用户可以搜索 GitHub.com”后，专用和内部存储库中的问题不包括在 GitHub.com 搜索结果中。 - "当副本节点在高可用性配置下离线时，{% data variables.product.product_name %} 仍可能将 {% data variables.product.prodname_pages %} 请求路由到离线节点，从而减少用户的 {% data variables.product.prodname_pages %} 可用性。" diff --git a/translations/zh-CN/data/release-notes/enterprise-server/3-0/24.yml b/translations/zh-CN/data/release-notes/enterprise-server/3-0/24.yml index 6023a57e4c83..afe43164e1e1 100644 --- a/translations/zh-CN/data/release-notes/enterprise-server/3-0/24.yml +++ b/translations/zh-CN/data/release-notes/enterprise-server/3-0/24.yml @@ -13,7 +13,7 @@ sections: known_issues: - "在新建的没有任何用户的 {% data variables.product.prodname_ghe_server %} 上，攻击者可以创建第一个管理员用户。" - 自定义防火墙规则在升级过程中被删除。 - - "[通过 Web 界面上传](https://github.com/blog/2105-upload-files-to-your-repositories)的 Git LFS 跟踪文件被错误地直接添加到存储库。" + - "[通过 Web 界面上传](https://github.com/blog/2105-upload-files-to-your-repositories) 的 Git LFS 跟踪文件被错误地直接添加到存储库。" - 问题若是包含同一存储库中文件路径长于 255 个字符的 blob 的永久链接，则无法关闭。 - 对 GitHub Connect 启用“用户可以搜索 GitHub.com”后，专用和内部存储库中的问题不包括在 GitHub.com 搜索结果中。 - "当副本节点在高可用性配置下离线时，{% data variables.product.product_name %} 仍可能将 {% data variables.product.prodname_pages %} 请求路由到离线节点，从而减少用户的 {% data variables.product.prodname_pages %} 可用性。" diff --git a/translations/zh-CN/data/release-notes/enterprise-server/3-0/4.yml b/translations/zh-CN/data/release-notes/enterprise-server/3-0/4.yml index 15a89606aa31..d77ba0baaebe 100644 --- a/translations/zh-CN/data/release-notes/enterprise-server/3-0/4.yml +++ b/translations/zh-CN/data/release-notes/enterprise-server/3-0/4.yml @@ -2,7 +2,7 @@ date: '2021-04-01' intro: "对于 {% data variables.product.prodname_ghe_server %} 3.0+，最低基础结构要求已经增加。有关详细信息，请参阅“[关于 GitHub Enterprise Server 3.0 及更高版本的最低要求](/admin/enterprise-management/upgrading-github-enterprise-server#about-minimum-requirements-for-github-enterprise-server-30-and-later)”。" sections: security_fixes: - - "**高：**在 GitHub Enterprise Server 中发现了一个不适当的访问控制漏洞，该漏洞允许根据 GitHub 应用的 [Web 身份验证流](https://docs.github.com/en/developers/apps/identifying-and-authorizing-users-for-github-apps#web-application-flow)生成的访问令牌通过 REST API 读取专用存储库元数据，而无需获取适当的权限。若要利用这个漏洞，攻击者需要在实例上创建 GitHub 应用，并让用户通过 Web 身份验证流对应用程序进行授权。返回的专用存储库元数据将仅限于令牌标识的用户拥有的存储库。此漏洞影响 GitHub Enterprise Server 3.0.4 之前的所有版本，并在 3.0.4、2.22.10 和 2.21.18 版本中得到了修复。此漏洞编号为 CVE-2021-22865，并通过 [GitHub Bug 赏金计划](https://bounty.github.com)报告。" + - "**高：**在 GitHub Enterprise Server 中发现了一个不适当的访问控制漏洞，该漏洞允许根据 GitHub 应用的 [Web 身份验证流](https://docs.github.com/en/developers/apps/identifying-and-authorizing-users-for-github-apps#web-application-flow) 生成的访问令牌通过 REST API 读取专用存储库元数据，而无需获取适当的权限。若要利用这个漏洞，攻击者需要在实例上创建 GitHub 应用，并让用户通过 Web 身份验证流对应用程序进行授权。返回的专用存储库元数据将仅限于令牌标识的用户拥有的存储库。此漏洞影响 GitHub Enterprise Server 3.0.4 之前的所有版本，并在 3.0.4、2.22.10 和 2.21.18 版本中得到了修复。此漏洞编号为 CVE-2021-22865，并通过 [GitHub Bug 赏金计划](https://bounty.github.com) 报告。" - 包已更新到最新的安全版本。 bugs: - 启用维护模式时，尽管某些服务应该运行但不应列出，它们仍被列为“活动进程”。 @@ -17,7 +17,7 @@ sections: known_issues: - 在没有任何用户的新建 GitHub Enterprise Server 上，攻击者可以创建第一个管理员用户。 - 在升级期间不会维护自定义防火墙规则。 - - "Git LFS 跟踪的[通过 Web 界面上传的](https://github.com/blog/2105-upload-files-to-your-repositories)文件被错误地直接添加到存储库。" + - "Git LFS 跟踪的[通过 Web 界面上传的](https://github.com/blog/2105-upload-files-to-your-repositories) 文件被错误地直接添加到存储库。" - 如果问题包含同一存储库中文件路径长于 255 个字符的 blob 的永久链接，则无法关闭。 - 在 GitHub Connect 中启用了“用户可以搜索 GitHub.com”时，专用和内部存储库中的问题不包括在 GitHub.com 搜索结果中。 - 如果笔记本包含非 ASCII UTF-8 字符，则 Web UI 中的 Jupyter Notebook 渲染可能会失败。 diff --git a/translations/zh-CN/data/release-notes/enterprise-server/3-0/5.yml b/translations/zh-CN/data/release-notes/enterprise-server/3-0/5.yml index e7537e5b7910..3dcb6edb680f 100644 --- a/translations/zh-CN/data/release-notes/enterprise-server/3-0/5.yml +++ b/translations/zh-CN/data/release-notes/enterprise-server/3-0/5.yml @@ -20,7 +20,7 @@ sections: known_issues: - 在新建的没有任何用户的 GitHub Enterprise Server 上，攻击者可以创建第一个管理员用户。 - 在升级期间不会维护自定义防火墙规则。 - - "[通过 Web 界面上传](https://github.com/blog/2105-upload-files-to-your-repositories)的 Git LFS 跟踪文件被错误地直接添加到存储库。" + - "[通过 Web 界面上传](https://github.com/blog/2105-upload-files-to-your-repositories) 的 Git LFS 跟踪文件被错误地直接添加到存储库。" - 如果问题包含文件路径长于 255 个字符的同一存储库中 blob 的永久链接，则问题无法关闭。 - 在 GitHub Connect 中启用了“用户可以搜索 GitHub.com”时，专用和内部存储库中的问题不包括在 GitHub.com 搜索结果中。 - 在合并拉取请求后删除分支时，即使分支删除成功也会出现错误消息。 diff --git a/translations/zh-CN/data/release-notes/enterprise-server/3-0/6.yml b/translations/zh-CN/data/release-notes/enterprise-server/3-0/6.yml index 32d81e475ca5..8abb94ecbddc 100644 --- a/translations/zh-CN/data/release-notes/enterprise-server/3-0/6.yml +++ b/translations/zh-CN/data/release-notes/enterprise-server/3-0/6.yml @@ -24,7 +24,7 @@ sections: known_issues: - 在新建的没有任何用户的 GitHub Enterprise Server 上，攻击者可以创建第一个管理员用户。 - 在升级期间不会维护自定义防火墙规则。 - - "[通过 Web 界面上传](https://github.com/blog/2105-upload-files-to-your-repositories)的 Git LFS 跟踪文件被错误地直接添加到存储库。" + - "[通过 Web 界面上传](https://github.com/blog/2105-upload-files-to-your-repositories) 的 Git LFS 跟踪文件被错误地直接添加到存储库。" - 问题若是包含同一存储库中文件路径长于 255 个字符的 blob 的永久链接，则无法关闭。 - 对 GitHub Connect 启用“用户可以搜索 GitHub.com”后，专用和内部存储库中的问题不包括在 GitHub.com 搜索结果中。 - "当副本节点在高可用性配置下离线时，{% data variables.product.product_name %} 仍可能将 {% data variables.product.prodname_pages %} 请求路由到离线节点，从而减少用户的 {% data variables.product.prodname_pages %} 可用性。" diff --git a/translations/zh-CN/data/release-notes/enterprise-server/3-0/8.yml b/translations/zh-CN/data/release-notes/enterprise-server/3-0/8.yml index 52ca8b7cacba..e7d404a70561 100644 --- a/translations/zh-CN/data/release-notes/enterprise-server/3-0/8.yml +++ b/translations/zh-CN/data/release-notes/enterprise-server/3-0/8.yml @@ -20,7 +20,7 @@ sections: - "使用 `ghe-repo /` 通过管理 shell 访问存储库时将被挂起。解决方法是使用 `ghe-repo / -c \"bash -i\"`，直到下一个版本提供修复为止。" - 在新建的没有任何用户的 GitHub Enterprise Server 上，攻击者可能创建第一个管理员用户。 - 在升级期间不会维护自定义防火墙规则。 - - "Git LFS 跟踪的[通过 Web 界面上传的](https://github.com/blog/2105-upload-files-to-your-repositories)文件被错误地直接添加到存储库。" + - "Git LFS 跟踪的[通过 Web 界面上传的](https://github.com/blog/2105-upload-files-to-your-repositories) 文件被错误地直接添加到存储库。" - 如果问题包含指向同一存储库中文件路径长于 255 个字符的 blob 的永久链接，则无法关闭。 - 在 GitHub Connect 中启用了“用户可以搜索 GitHub.com”时，专用和内部存储库中的问题不包括在 GitHub.com 搜索结果中。 - "当副本节点在高可用性配置下脱机时，{% data variables.product.product_name %} 仍可能会将 {% data variables.product.prodname_pages %} 请求路由到脱机节点，从而减少用户的 {% data variables.product.prodname_pages %} 可用性。" diff --git a/translations/zh-CN/data/release-notes/enterprise-server/3-0/9.yml b/translations/zh-CN/data/release-notes/enterprise-server/3-0/9.yml index 4a27a0b12c01..ef1eafe39230 100644 --- a/translations/zh-CN/data/release-notes/enterprise-server/3-0/9.yml +++ b/translations/zh-CN/data/release-notes/enterprise-server/3-0/9.yml @@ -17,7 +17,7 @@ sections: known_issues: - 在没有任何用户的新建 GitHub Enterprise Server 上，攻击者可能创建第一个管理员用户。 - 自定义防火墙规则在升级过程中被删除。 - - "[通过 Web 界面上传](https://github.com/blog/2105-upload-files-to-your-repositories)的 Git LFS 跟踪文件被错误地直接添加到存储库。" + - "[通过 Web 界面上传](https://github.com/blog/2105-upload-files-to-your-repositories) 的 Git LFS 跟踪文件被错误地直接添加到存储库。" - 问题若是包含同一存储库中文件路径长于 255 个字符的 blob 的永久链接，则无法关闭。 - 对 GitHub Connect 启用“用户可以搜索 GitHub.com”后，专用和内部存储库中的问题不包括在 GitHub.com 搜索结果中。 - "当副本节点在高可用性配置下离线时，{% data variables.product.product_name %} 仍可能将 {% data variables.product.prodname_pages %} 请求路由到离线节点，从而减少用户的 {% data variables.product.prodname_pages %} 可用性。" diff --git a/translations/zh-CN/data/release-notes/enterprise-server/3-1/0.yml b/translations/zh-CN/data/release-notes/enterprise-server/3-1/0.yml index 3b24968dd8f9..f0c907455142 100644 --- a/translations/zh-CN/data/release-notes/enterprise-server/3-1/0.yml +++ b/translations/zh-CN/data/release-notes/enterprise-server/3-1/0.yml @@ -96,78 +96,4 @@ sections: - heading: API Changes notes: - The code scanning API allows users to upload data about static analysis security testing results, or export data about alerts. For more information, see the [code scanning API reference](/rest/reference/code-scanning). - - The [GitHub Apps API](/rest/reference/apps) for managing installations has now graduated from an API preview to a generally available API. The [preview header](/rest/overview/api-previews) is no longer required to access these endpoints. - - security_fixes: - - '**MEDIUM** Under certain circumstances, users who were removed from a team or organization could retain write access to branches they had existing pull requests opened for.' - - Packages have been updated to the latest security versions. - - bugs: - - heading: Fixes for known issues from Release Candidate - notes: - - All known issues from Release Candidate 1 have been fixed, except those listed in the Known Issues section below. - - heading: Fixes for other issues - notes: - - On the "Configure Actions and Packages" page of the initial installation process, clicking on the "Test domain settings" button did not complete the test. - - 'Running `ghe-btop` failed with an error and cannot find a `babeld` container.' - - MySQL could reload and cause downtime if you change auto failover settings. - - After upgrading, a mismatch of internal and external timeout values created service unavailability. - - Expected replication delays in MSSQL generated warnings. - - 'Link to "[Configuring clustering](/admin/enterprise-management/configuring-clustering)" on the Management Console was incorrect.' - - When creating or editing a pre-receive hook, a race condition in the user interface meant that after selecting a repository, files within the repository were sometimes not populated in files dropdown. - - When an IP address is added to a whitelist using "Create Whitelist Entry" button, it could still be shown as locked out. - - References to the "Dependency graph" and "Dependabot alerts" features were not shown as disabled on some repositories. - - Setting an announcement in the enterprise account settings could result in a 500 Internal Server Error. - - HTTP POST requests to the `/hooks` endpoint could fail with a 401 response due to an incorrectly configured `hookID`. - - The `build-server` process failed to clean up processes, leaving them in the `defunct` state. - - '`spokesd` created excessive log entries, including the phrase "fixing placement skipped".' - - While upgrading Actions the upgrade could fail if the instance could not make self-requests via its configured hostname. - - Upgrading from 2.22.x to 3.1.0.rc1 could result in a database migration error relating to the `BackfillIntegrationApplicationCallbackUrlsTransition` data transition. - - known_issues: - - Access to a repository through the administrative shell using `ghe-repo /` will hang. As a workaround, use `ghe-repo / -c "bash -i"` until a fix is available in the next version. - - 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. - - On a freshly set up {% data variables.product.prodname_ghe_server %} without any users, an attacker could create the first admin user. - - Custom firewall rules are not maintained during an upgrade. - - 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 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. - - Upgrading an instance that has previously ran a 2.13 release, but not a 2.14 release, results in a database migration error relating to the `AddRepositoryIdToCheckRuns` data transition. - - | - After upgrading from 3.0.x to 3.1.x, in some cases GitHub Actions can fail with an error: `An unexpected error occurred when executing this workflow.` To workaround this problem, connect to the administrative shell (ssh) and run: - ``` - ghe-actions-console -s actions -c "Queue-ServiceJob -JobId 4DB1F4CF-19FD-40E0-A253-91288813DE8B" - ``` - - When a replica node is offline in a high availability configuration, {% data variables.product.product_name %} may still route {% data variables.product.prodname_pages %} requests to the offline node, reducing the availability of {% data variables.product.prodname_pages %} for users. - - Resource limits that are specific to processing pre-receive hooks may cause some pre-receive hooks to fail. - - deprecations: - - heading: Deprecation of GitHub Enterprise Server 2.20 - notes: - - '**{% data variables.product.prodname_ghe_server %} 2.20 was discontinued on March 2, 2021**. That means that no patch releases will be made, even for critical security issues, after this date. For better performance, improved security, and new features, [upgrade to the newest version of {% data variables.product.prodname_ghe_server %}](/enterprise-server@3.1/admin/enterprise-management/upgrading-github-enterprise-server) as soon as possible.' - - heading: Deprecation of GitHub Enterprise Server 2.21 - notes: - - '**{% data variables.product.prodname_ghe_server %} 2.21 will be discontinued on June 9, 2021**. That means that no patch releases will be made, even for critical security issues, after this date. For better performance, improved security, and new features, [upgrade to the newest version of {% data variables.product.prodname_ghe_server %}](/enterprise-server@3.1/admin/enterprise-management/upgrading-github-enterprise-server) as soon as possible.' - - heading: Deprecation of Legacy GitHub App Webhook Events - notes: - - 'Starting with {% data variables.product.prodname_ghe_server %} 2.21.0 two legacy GitHub Apps-related webhook events have been deprecated and will be removed in {% data variables.product.prodname_ghe_server %} 3.2.0. The deprecated events `integration_installation` and `integration_installation_repositories` have equivalent events which will be supported. More information is available in the [deprecation announcement blog post](https://developer.github.com/changes/2020-04-15-replacing-the-installation-and-installation-repositories-events/).' - - heading: Deprecation of Legacy GitHub Apps Endpoint - notes: - - Starting with {% data variables.product.prodname_ghe_server %} 2.21.0 the legacy GitHub Apps endpoint for creating installation access tokens was deprecated and will be removed in {% data variables.product.prodname_ghe_server %} 3.2.0. More information is available in the [deprecation announcement blog post](https://developer.github.com/changes/2020-04-15-replacing-create-installation-access-token-endpoint/). - - heading: Deprecation of OAuth Application API - notes: - - 'GitHub no longer supports the OAuth application endpoints that contain `access_token` as a path parameter. We have introduced new endpoints that allow you to securely manage tokens for OAuth Apps by moving `access_token` to the request body. While deprecated, the endpoints are still accessible in this version. We intend to remove these endpoints on {% data variables.product.prodname_ghe_server %} 3.4. For more information, see the [deprecation announcement blog post](https://developer.github.com/changes/2020-02-14-deprecating-oauth-app-endpoint/).' - - heading: Deprecation of GitHub Actions short SHA support - notes: - - '{% data variables.product.prodname_actions %} will remove support for referencing actions using the shortened version of a git commit SHA. This may cause some workflows in your repository to break. To fix these workflows, you will need to update the action reference to use the full commit SHA. For more information, see "[Security hardening for {% data variables.product.prodname_actions %}](/actions/learn-github-actions/security-hardening-for-github-actions#using-third-party-actions)."' - - heading: Deprecation of XenServer Hypervisor support - notes: - - Beginning in {% data variables.product.prodname_ghe_server %} 3.1, we will begin discontinuing support for Xen Hypervisor. The complete deprecation is scheduled for {% data variables.product.prodname_ghe_server %} 3.3, following the standard one year deprecation window. - - heading: Change to the format of authentication tokens affects GitHub Connect - notes: - # https://github.com/github/releases/issues/1235 - - | - GitHub Connect will no longer work after June 3rd for instances running GitHub Enterprise Server 3.1 or older, due to the format of GitHub authentication tokens changing. To continue using GitHub Connect, upgrade to GitHub Enterprise Server 3.2 or later. For more information, see the [GitHub Blog](https://github.blog/2022-05-20-action-needed-by-github-connect-customers-using-ghes-3-1-and-older-to-adopt-new-authentication-token-format-updates/). [Updated: 2022-06-14] - - backups: - - '{% data variables.product.prodname_ghe_server %} 3.1 requires at least [GitHub Enterprise Backup Utilities 3.1.0](https://github.com/github/backup-utils) for [Backups and Disaster Recovery](/enterprise-server@3.1/admin/configuration/configuring-backups-on-your-appliance).' + - The [GitHub Apps API](/rest/reference/apps) for managing installations has now graduated from an API preview to a \ No newline at end of file diff --git a/translations/zh-CN/data/release-notes/enterprise-server/3-1/10.yml b/translations/zh-CN/data/release-notes/enterprise-server/3-1/10.yml index 0856cb8115d3..d35296f1133f 100644 --- a/translations/zh-CN/data/release-notes/enterprise-server/3-1/10.yml +++ b/translations/zh-CN/data/release-notes/enterprise-server/3-1/10.yml @@ -14,7 +14,7 @@ sections: - "{% data variables.product.prodname_registry %} npm 注册表不再返回元数据响应的时间值。这样做是为了大幅提高性能。我们继续拥有将时间值作为元数据响应的一部分返回所需的所有数据，并将在解决现有性能问题后恢复返回该值。" - "在新建的没有任何用户的 {% data variables.product.prodname_ghe_server %} 上，攻击者可能创建第一个管理员用户。" - 自定义防火墙规则在升级过程中被删除。 - - "Git LFS 跟踪的[通过 Web 界面上传的](https://github.com/blog/2105-upload-files-to-your-repositories)文件被错误地直接添加到存储库。" + - "Git LFS 跟踪的[通过 Web 界面上传的](https://github.com/blog/2105-upload-files-to-your-repositories) 文件被错误地直接添加到存储库。" - 如果问题包含指向同一存储库中文件路径长于 255 个字符的 blob 的永久链接，则无法关闭。 - 在 GitHub Connect 中启用了“用户可以搜索 GitHub.com”时，专用和内部存储库中的问题不包括在 GitHub.com 搜索结果中。 - "如果为 {% data variables.product.prodname_ghe_server %} 启用 {% data variables.product.prodname_actions %}，将能使用 `ghe-repl-teardown` 成功拆解副本节点，但是可能会返回 `ERROR:Running migrations`。" diff --git a/translations/zh-CN/data/release-notes/enterprise-server/3-1/13.yml b/translations/zh-CN/data/release-notes/enterprise-server/3-1/13.yml index b6b479d82a29..e1caa93d1769 100644 --- a/translations/zh-CN/data/release-notes/enterprise-server/3-1/13.yml +++ b/translations/zh-CN/data/release-notes/enterprise-server/3-1/13.yml @@ -16,7 +16,7 @@ sections: - "{% data variables.product.prodname_registry %} npm 注册表不再在元数据响应中返回时间值。这样可以大幅改善性能。我们继续拥有将时间值作为元数据响应的一部分返回所需的所有数据，并将在以后解决现有性能问题后恢复返回该值。" - "在新建的没有任何用户的 {% data variables.product.prodname_ghe_server %} 上，攻击者可以创建第一个管理员用户。" - 自定义防火墙规则在升级过程中被删除。 - - "[通过 Web 界面上传](https://github.com/blog/2105-upload-files-to-your-repositories)的 Git LFS 跟踪文件被错误地直接添加到存储库。" + - "[通过 Web 界面上传](https://github.com/blog/2105-upload-files-to-your-repositories) 的 Git LFS 跟踪文件被错误地直接添加到存储库。" - 如果问题包含文件路径长于 255 个字符的同一存储库中 blob 的永久链接，则问题无法关闭。 - 在 GitHub Connect 中启用了“用户可以搜索 GitHub.com”时，专用和内部存储库中的问题不包括在 GitHub.com 搜索结果中。 - "如果为 {% data variables.product.prodname_ghe_server %} 启用 {% data variables.product.prodname_actions %}，将能使用 `ghe-repl-teardown` 成功拆解副本节点，但是可能会返回 `ERROR:Running migrations`。" diff --git a/translations/zh-CN/data/release-notes/enterprise-server/3-1/14.yml b/translations/zh-CN/data/release-notes/enterprise-server/3-1/14.yml index d820e279f031..b1024380777b 100644 --- a/translations/zh-CN/data/release-notes/enterprise-server/3-1/14.yml +++ b/translations/zh-CN/data/release-notes/enterprise-server/3-1/14.yml @@ -1,7 +1,7 @@ date: '2021-12-13' sections: security_fixes: - - '{% octicon "alert" aria-label="The alert icon" %} **严重：**在 Log4j 库中发现远程代码执行漏洞，该漏洞会影响 3.3.1 之前的所有 {% data variables.product.prodname_ghe_server %} 版本，漏洞编号为[CVE-2021-44228](https://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2021-44228)。Log4j 库用于在 {% data variables.product.prodname_ghe_server %} 实例上运行的开源服务。已在 {% data variables.product.prodname_ghe_server %} 3.0.22、3.1.14、3.2.6 和 3.3.1 中修复该漏洞。 有关详细信息，请参阅 GitHub 博客[文章](https://github.blog/2021-12-13-githubs-response-to-log4j-vulnerability-cve-2021-44228/)。' + - '{% octicon "alert" aria-label="The alert icon" %} **严重：**在 Log4j 库中发现远程代码执行漏洞，该漏洞会影响 3.3.1 之前的所有 {% data variables.product.prodname_ghe_server %} 版本，漏洞编号为[CVE-2021-44228](https://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2021-44228)。Log4j 库用于在 {% data variables.product.prodname_ghe_server %} 实例上运行的开源服务。已在 {% data variables.product.prodname_ghe_server %} 3.0.22、3.1.14、3.2.6 和 3.3.1 中修复该漏洞。有关详细信息，请参阅 GitHub 博客 [文章](https://github.blog/2021-12-13-githubs-response-to-log4j-vulnerability-cve-2021-44228/)。' - '**2021 年 12 月 17 日更新**：此版本中的修复也能缓解在该版本之后发布的 [CVE-2021-45046](https://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2021-45046)。无需再升级 {% data variables.product.prodname_ghe_server %}，即可缓解 CVE-2021-44228 和 CVE-2021-45046。' known_issues: - "{% data variables.product.prodname_registry %} npm 注册表不再返回元数据响应的时间值。这样做是为了大幅改善性能。作为元数据响应的一部分，我们继续拥有返回时间值所需的所有数据，并将在我们解决现有性能问题后恢复返回这个值。" diff --git a/translations/zh-CN/data/release-notes/enterprise-server/3-1/16.yml b/translations/zh-CN/data/release-notes/enterprise-server/3-1/16.yml index d69a0d05f4b8..6f74e7700d9f 100644 --- a/translations/zh-CN/data/release-notes/enterprise-server/3-1/16.yml +++ b/translations/zh-CN/data/release-notes/enterprise-server/3-1/16.yml @@ -17,7 +17,7 @@ sections: - "{% data variables.product.prodname_registry %} npm 注册表不再在元数据响应中返回时间值。这样做是为了大幅改善性能。作为元数据响应的一部分，我们继续拥有返回时间值所需的全部数据，并将在我们解决现有性能问题后恢复返回这个值。" - "在新建的没有任何用户的 {% data variables.product.prodname_ghe_server %} 上，攻击者可以创建第一个管理员用户。" - 自定义防火墙规则在升级过程中被删除。 - - "[通过 Web 界面上传](https://github.com/blog/2105-upload-files-to-your-repositories)的 Git LFS 跟踪文件被错误地直接添加到存储库。" + - "[通过 Web 界面上传](https://github.com/blog/2105-upload-files-to-your-repositories) 的 Git LFS 跟踪文件被错误地直接添加到存储库。" - 问题若是包含同一存储库中文件路径长于 255 个字符的 blob 的永久链接，则无法关闭。 - 对 GitHub Connect 启用“用户可以搜索 GitHub.com”后，专用和内部存储库中的问题不包括在 GitHub.com 搜索结果中。 - "如果为 {% data variables.product.prodname_ghe_server %} 启用 {% data variables.product.prodname_actions %}，将能使用 `ghe-repl-teardown` 成功拆解副本节点，但是可能会返回 `ERROR:Running migrations`。" diff --git a/translations/zh-CN/data/release-notes/enterprise-server/3-1/17.yml b/translations/zh-CN/data/release-notes/enterprise-server/3-1/17.yml index 5f85dbc002b3..1c5afc11dd2e 100644 --- a/translations/zh-CN/data/release-notes/enterprise-server/3-1/17.yml +++ b/translations/zh-CN/data/release-notes/enterprise-server/3-1/17.yml @@ -8,7 +8,7 @@ sections: - "{% data variables.product.prodname_registry %} npm 注册表不再在元数据响应中返回时间值。这样做是为了大幅改善性能。作为元数据响应的一部分，我们继续拥有返回时间值所需的所有数据，并将在我们解决现有性能问题后恢复返回这个值。" - "在新建的没有任何用户的 {% data variables.product.prodname_ghe_server %} 实例上，攻击者可以创建第一个管理员用户。" - 自定义防火墙规则在升级过程中被删除。 - - "[通过 Web 界面上传](https://github.com/blog/2105-upload-files-to-your-repositories)的 Git LFS 跟踪文件被错误地直接添加到存储库。" + - "[通过 Web 界面上传](https://github.com/blog/2105-upload-files-to-your-repositories) 的 Git LFS 跟踪文件被错误地直接添加到存储库。" - 问题若是包含同一存储库中文件路径长于 255 个字符的 blob 的永久链接，则无法关闭。 - 对 GitHub Connect 启用“用户可以搜索 GitHub.com”后，专用和内部存储库中的问题不包括在 GitHub.com 搜索结果中。 - "如果为 {% data variables.product.prodname_ghe_server %} 启用 {% data variables.product.prodname_actions %}，将能使用 `ghe-repl-teardown` 成功拆解副本节点，但是可能会返回 `ERROR:Running migrations`。" diff --git a/translations/zh-CN/data/release-notes/enterprise-server/3-1/19.yml b/translations/zh-CN/data/release-notes/enterprise-server/3-1/19.yml index cdd6e15a9eb2..f5efe9944a39 100644 --- a/translations/zh-CN/data/release-notes/enterprise-server/3-1/19.yml +++ b/translations/zh-CN/data/release-notes/enterprise-server/3-1/19.yml @@ -34,7 +34,7 @@ sections: - "{% data variables.product.prodname_registry %} npm 注册表在元数据响应中不再返回时间值。这样做是为了大幅改善性能。我们继续拥有将时间值作为元数据响应的一部分返回所需的所有数据，并将在以后解决现有性能问题后恢复返回该值。" - "在没有任何用户的新建 {% data variables.product.prodname_ghe_server %} 实例上，攻击者可以创建第一个管理员用户。" - 自定义防火墙规则在升级过程中被移除。 - - "Git LFS 跟踪的[通过 Web 界面上传的](https://github.com/blog/2105-upload-files-to-your-repositories)文件被错误地直接添加到存储库。" + - "Git LFS 跟踪的[通过 Web 界面上传的](https://github.com/blog/2105-upload-files-to-your-repositories) 文件被错误地直接添加到存储库。" - 如果问题包含同一存储库中文件路径长于 255 个字符的 blob 的永久链接，则无法关闭。 - "对 {% data variables.product.prodname_github_connect %} 启用“用户可以搜索 GitHub.com”后，专用和内部存储库中的问题不包括在 {% data variables.product.prodname_dotcom_the_website %} 搜索结果中。" - "如果为 {% data variables.product.prodname_ghe_server %} 启用 {% data variables.product.prodname_actions %}，就可以使用 `ghe-repl-teardown` 成功拆解副本节点，但是可能会返回 `ERROR:Running migrations`。" diff --git a/translations/zh-CN/data/release-notes/enterprise-server/3-1/20.yml b/translations/zh-CN/data/release-notes/enterprise-server/3-1/20.yml index 98df6f6beb42..c9909354e0b3 100644 --- a/translations/zh-CN/data/release-notes/enterprise-server/3-1/20.yml +++ b/translations/zh-CN/data/release-notes/enterprise-server/3-1/20.yml @@ -15,7 +15,7 @@ sections: - "{% data variables.product.prodname_registry %} npm 注册表不再在元数据响应中返回时间值。这样做是为了大幅改善性能。作为元数据响应的一部分，我们继续拥有返回时间值所需的所有数据，并将在我们解决现有性能问题后恢复返回这个值。" - "在新建的没有任何用户的 {% data variables.product.prodname_ghe_server %} 实例上，攻击者可以创建第一个管理员用户。" - 自定义防火墙规则在升级过程中被删除。 - - "[通过 Web 界面上传](https://github.com/blog/2105-upload-files-to-your-repositories)的 Git LFS 跟踪文件被错误地直接添加到存储库。" + - "[通过 Web 界面上传](https://github.com/blog/2105-upload-files-to-your-repositories) 的 Git LFS 跟踪文件被错误地直接添加到存储库。" - 问题若是包含同一存储库中文件路径长于 255 个字符的 blob 的永久链接，则无法关闭。 - "对 {% data variables.product.prodname_github_connect %} 启用“用户可以搜索 GitHub.com”后，专用和内部存储库中的问题不包括在 {% data variables.product.prodname_dotcom_the_website %} 搜索结果中。" - "如果为 {% data variables.product.prodname_ghe_server %} 启用 {% data variables.product.prodname_actions %}，将能使用 `ghe-repl-teardown` 成功拆解副本节点，但是可能会返回 `ERROR:Running migrations`。" diff --git a/translations/zh-CN/data/release-notes/enterprise-server/3-1/21.yml b/translations/zh-CN/data/release-notes/enterprise-server/3-1/21.yml index da3e9b4d5052..3a69a0d67354 100644 --- a/translations/zh-CN/data/release-notes/enterprise-server/3-1/21.yml +++ b/translations/zh-CN/data/release-notes/enterprise-server/3-1/21.yml @@ -2,7 +2,7 @@ date: '2022-05-17' sections: security_fixes: - '**中：**发现了 nginx 解析器中的一个安全问题，可以从 DNS 服务器伪造 UDP 数据包的攻击者可能导致 1 字节内存覆盖，从而导致工作进程崩溃或其他潜在的破坏性影响。该漏洞的编号为 [CVE-2021-23017](https://nvd.nist.gov/vuln/detail/CVE-2021-23017)。' - - "更新了 `actions/checkout@v2` 和 `actions/checkout@v3` 操作以解决 [Git 安全措施实施博客文章](https://github.blog/2022-04-12-git-security-vulnerability-announced/)中公布的新漏洞。" + - "更新了 `actions/checkout@v2` 和 `actions/checkout@v3` 操作以解决 [Git 安全措施实施博客文章](https://github.blog/2022-04-12-git-security-vulnerability-announced/) 中公布的新漏洞。" - 包已更新到最新的安全版本。 bugs: - 在某些群集拓扑中，`ghe-cluster-status` 命令会在 `/tmp` 中留下空目录。 @@ -18,7 +18,7 @@ sections: - "{% data variables.product.prodname_registry %} npm 注册表不再在元数据响应中返回时间值。这样可以大幅改善性能。我们继续拥有将时间值作为元数据响应的一部分返回所需的所有数据，并将在以后解决现有性能问题后恢复返回该值。" - "在新建的没有任何用户的 {% data variables.product.prodname_ghe_server %} 实例上，攻击者可以创建第一个管理员用户。" - 自定义防火墙规则在升级过程中被删除。 - - "[通过 Web 界面上传](https://github.com/blog/2105-upload-files-to-your-repositories)的 Git LFS 跟踪文件被错误地直接添加到存储库。" + - "[通过 Web 界面上传](https://github.com/blog/2105-upload-files-to-your-repositories) 的 Git LFS 跟踪文件被错误地直接添加到存储库。" - 如果问题包含文件路径长于 255 个字符的同一存储库中 blob 的永久链接，则问题无法关闭。 - "对 {% data variables.product.prodname_github_connect %} 启用“用户可以搜索 GitHub.com”后，专用和内部存储库中的问题不包括在 {% data variables.product.prodname_dotcom_the_website %} 搜索结果中。" - "如果为 {% data variables.product.prodname_ghe_server %} 启用 {% data variables.product.prodname_actions %}，将能使用 `ghe-repl-teardown` 成功拆解副本节点，但是可能会返回 `ERROR:Running migrations`。" diff --git a/translations/zh-CN/data/release-notes/enterprise-server/3-1/22.yml b/translations/zh-CN/data/release-notes/enterprise-server/3-1/22.yml index aa5edba89b3a..21f73d0617d8 100644 --- a/translations/zh-CN/data/release-notes/enterprise-server/3-1/22.yml +++ b/translations/zh-CN/data/release-notes/enterprise-server/3-1/22.yml @@ -13,7 +13,7 @@ sections: - "{% data variables.product.prodname_registry %} npm 注册表不再在元数据响应中返回时间值。这样可以大幅改善性能。我们继续拥有将时间值作为元数据响应的一部分返回所需的所有数据，并将在以后解决现有性能问题后恢复返回该值。" - "在新建的没有任何用户的 {% data variables.product.prodname_ghe_server %} 实例上，攻击者可以创建第一个管理员用户。" - 自定义防火墙规则在升级过程中被删除。 - - "[通过 Web 界面上传](https://github.com/blog/2105-upload-files-to-your-repositories)的 Git LFS 跟踪文件被错误地直接添加到存储库。" + - "[通过 Web 界面上传](https://github.com/blog/2105-upload-files-to-your-repositories) 的 Git LFS 跟踪文件被错误地直接添加到存储库。" - 如果问题包含文件路径长于 255 个字符的同一存储库中 Blob 的永久链接，则问题无法关闭。 - "对 {% data variables.product.prodname_github_connect %} 启用“用户可以搜索 GitHub.com”后，专用和内部存储库中的问题不包括在 {% data variables.product.prodname_dotcom_the_website %} 搜索结果中。" - "如果为 {% data variables.product.prodname_ghe_server %} 启用 {% data variables.product.prodname_actions %}，将能使用 `ghe-repl-teardown` 成功拆解副本节点，但是可能会返回 `ERROR:Running migrations`。" diff --git a/translations/zh-CN/data/release-notes/enterprise-server/3-1/5.yml b/translations/zh-CN/data/release-notes/enterprise-server/3-1/5.yml index db2fc553e822..36c0363cea23 100644 --- a/translations/zh-CN/data/release-notes/enterprise-server/3-1/5.yml +++ b/translations/zh-CN/data/release-notes/enterprise-server/3-1/5.yml @@ -13,7 +13,7 @@ sections: - "{% data variables.product.prodname_registry %} npm 注册表不再在元数据响应中返回时间值。这样可以大幅改善性能。我们继续拥有将时间值作为元数据响应的一部分返回所需的所有数据，并将在以后解决现有性能问题后恢复返回该值。" - "在新建的没有任何用户的 {% data variables.product.prodname_ghe_server %} 上，攻击者可以创建第一个管理员用户。" - 自定义防火墙规则在升级过程中被删除。 - - "[通过 Web 界面上传](https://github.com/blog/2105-upload-files-to-your-repositories)的 Git LFS 跟踪文件被错误地直接添加到存储库。" + - "[通过 Web 界面上传](https://github.com/blog/2105-upload-files-to-your-repositories) 的 Git LFS 跟踪文件被错误地直接添加到存储库。" - 如果问题包含文件路径长于 255 个字符的同一存储库中 blob 的永久链接，则问题无法关闭。 - 在 GitHub Connect 中启用了“用户可以搜索 GitHub.com”时，专用和内部存储库中的问题不包括在 GitHub.com 搜索结果中。 - "如果为 {% data variables.product.prodname_ghe_server %} 启用 {% data variables.product.prodname_actions %}，将能使用 `ghe-repl-teardown` 成功拆解副本节点，但是可能会返回 `ERROR:Running migrations`。" diff --git a/translations/zh-CN/data/release-notes/enterprise-server/3-1/6.yml b/translations/zh-CN/data/release-notes/enterprise-server/3-1/6.yml index 9890f3ea5873..c83709b3395e 100644 --- a/translations/zh-CN/data/release-notes/enterprise-server/3-1/6.yml +++ b/translations/zh-CN/data/release-notes/enterprise-server/3-1/6.yml @@ -16,7 +16,7 @@ sections: - "{% data variables.product.prodname_registry %} npm 注册表不再在元数据响应中返回时间值。这样做是为了大幅改善性能。作为元数据响应的一部分，我们继续拥有返回时间值所需的全部数据，并将在我们解决现有性能问题后恢复返回这个值。" - "在新建的没有任何用户的 {% data variables.product.prodname_ghe_server %} 上，攻击者可以创建第一个管理员用户。" - 自定义防火墙规则在升级过程中被删除。 - - "[通过 Web 界面上传](https://github.com/blog/2105-upload-files-to-your-repositories)的 Git LFS 跟踪文件被错误地直接添加到存储库。" + - "[通过 Web 界面上传](https://github.com/blog/2105-upload-files-to-your-repositories) 的 Git LFS 跟踪文件被错误地直接添加到存储库。" - 问题若是包含同一存储库中文件路径长于 255 个字符的 blob 的永久链接，则无法关闭。 - 对 GitHub Connect 启用“用户可以搜索 GitHub.com”后，专用和内部存储库中的问题不包括在 GitHub.com 搜索结果中。 - "如果为 {% data variables.product.prodname_ghe_server %} 启用 {% data variables.product.prodname_actions %}，将能使用 `ghe-repl-teardown` 成功拆解副本节点，但是可能会返回 `ERROR:Running migrations`。" diff --git a/translations/zh-CN/data/release-notes/enterprise-server/3-1/7.yml b/translations/zh-CN/data/release-notes/enterprise-server/3-1/7.yml index 452ff2faa720..6ce33d145e80 100644 --- a/translations/zh-CN/data/release-notes/enterprise-server/3-1/7.yml +++ b/translations/zh-CN/data/release-notes/enterprise-server/3-1/7.yml @@ -11,7 +11,7 @@ sections: - "{% data variables.product.prodname_registry %} npm 注册表不再在元数据响应中返回时间值。这样可以大幅改善性能。作为元数据响应的一部分，我们继续拥有返回时间值所需的所有数据，并将在我们解决现有性能问题后恢复返回这个值。" - "在新建的没有任何用户的 {% data variables.product.prodname_ghe_server %} 上，攻击者可以创建第一个管理员用户。" - 将在升级过程中删除自定义防火墙规则。 - - "Git LFS 跟踪的[通过 Web 界面上传的](https://github.com/blog/2105-upload-files-to-your-repositories)文件被错误地直接添加到存储库。" + - "Git LFS 跟踪的[通过 Web 界面上传的](https://github.com/blog/2105-upload-files-to-your-repositories) 文件被错误地直接添加到存储库。" - 如果问题包含指向同一存储库中 blob 文件路径长于 255 个字符的 blob 的永久链接，则无法关闭。 - 在 GitHub Connect 中启用了“用户可以搜索 GitHub.com”时，专用和内部存储库中的问题不包括在 GitHub.com 搜索结果中。 - "如果为 {% data variables.product.prodname_ghe_server %} 启用 {% data variables.product.prodname_actions %}，将会使用 `ghe-repl-teardown` 成功拆解副本节点，但是可能会返回 `ERROR:Running migrations`。" diff --git a/translations/zh-CN/data/release-notes/enterprise-server/3-1/8.yml b/translations/zh-CN/data/release-notes/enterprise-server/3-1/8.yml index a388d49cbee4..043d742a4816 100644 --- a/translations/zh-CN/data/release-notes/enterprise-server/3-1/8.yml +++ b/translations/zh-CN/data/release-notes/enterprise-server/3-1/8.yml @@ -13,7 +13,7 @@ sections: - "{% data variables.product.prodname_registry %} npm 注册表不再返回元数据响应的时间值。这样做是为了大幅提高性能。我们继续拥有将时间值作为元数据响应的一部分返回所需的所有数据，并将在解决现有性能问题后恢复返回该值。" - "在新建的没有任何用户的 {% data variables.product.prodname_ghe_server %} 上，攻击者可能创建第一个管理员用户。" - 自定义防火墙规则在升级过程中被删除。 - - "Git LFS 跟踪的[通过 Web 界面上传的](https://github.com/blog/2105-upload-files-to-your-repositories)文件被错误地直接添加到存储库。" + - "Git LFS 跟踪的[通过 Web 界面上传的](https://github.com/blog/2105-upload-files-to-your-repositories) 文件被错误地直接添加到存储库。" - 如果问题包含指向同一存储库中文件路径长于 255 个字符的 blob 的永久链接，则无法关闭。 - 在 GitHub Connect 中启用了“用户可以搜索 GitHub.com”时，专用和内部存储库中的问题不包括在 GitHub.com 搜索结果中。 - "如果为 {% data variables.product.prodname_ghe_server %} 启用 {% data variables.product.prodname_actions %}，将能使用 `ghe-repl-teardown` 成功拆解副本节点，但是可能会返回 `ERROR:Running migrations`。" diff --git a/translations/zh-CN/data/release-notes/enterprise-server/3-1/9.yml b/translations/zh-CN/data/release-notes/enterprise-server/3-1/9.yml index 9a68debc63ab..163dfacd56fd 100644 --- a/translations/zh-CN/data/release-notes/enterprise-server/3-1/9.yml +++ b/translations/zh-CN/data/release-notes/enterprise-server/3-1/9.yml @@ -21,7 +21,7 @@ sections: - "{% data variables.product.prodname_registry %} npm 注册表不再在元数据响应中返回时间值。这样做是为了大幅改善性能。作为元数据响应的一部分，我们继续拥有返回时间值所需的所有数据，并将在我们解决现有性能问题后恢复返回这个值。" - "在新建的没有任何用户的 {% data variables.product.prodname_ghe_server %} 上，攻击者可以创建第一个管理员用户。" - 自定义防火墙规则在升级过程中被删除。 - - "Git LFS 跟踪的文件[通过 Web 界面上传](https://github.com/blog/2105-upload-files-to-your-repositories)被错误地直接添加到存储库。" + - "Git LFS 跟踪的文件[通过 Web 界面上传](https://github.com/blog/2105-upload-files-to-your-repositories) 被错误地直接添加到存储库。" - 如果问题包含文件路径长于 255 个字符的同一存储库中 blob 的永久链接，则问题无法关闭。 - 对 GitHub Connect 启用“用户可以搜索 GitHub.com”后，专用和内部存储库中的问题不包括在 GitHub.com 搜索结果中。 - "如果为 {% data variables.product.prodname_ghe_server %} 启用 {% data variables.product.prodname_actions %}，将能使用 `ghe-repl-teardown` 成功拆解副本节点，但是可能会返回 `ERROR:Running migrations`。" diff --git a/translations/zh-CN/data/release-notes/enterprise-server/3-2/0-rc1.yml b/translations/zh-CN/data/release-notes/enterprise-server/3-2/0-rc1.yml index 0213319af567..da8971f9c37e 100644 --- a/translations/zh-CN/data/release-notes/enterprise-server/3-2/0-rc1.yml +++ b/translations/zh-CN/data/release-notes/enterprise-server/3-2/0-rc1.yml @@ -103,207 +103,4 @@ sections: - The markdown editor used when creating or editing a release in a repository now has a text-editing toolbar. For more information, see "[Managing releases in a repository](/github/administering-a-repository/releasing-projects-on-github/managing-releases-in-a-repository#creating-a-release)." # https://github.com/github/releases/issues/1169 - - Uploading video files is now supported everywhere you write Markdown on {% data variables.product.product_name %}. Share demos, reproduction steps, and more in your issue and pull request comments, as well as in Markdown files within repositories, such as READMEs. For more information, see "[Attaching files](/github/writing-on-github/working-with-advanced-formatting/attaching-files)." - - # https://github.com/github/releases/issues/1269 - - Markdown files will now automatically generate a table of contents in the header when there are 2 or more headings. The table of contents is interactive and links to the selected section. All 6 Markdown heading levels are supported. - - # https://github.com/github/releases/issues/1294 - - 'There is a new keyboard shortcut, `cmd+e` on macOS or `ctrl+e` on Windows, to insert codeblocks in Markdown files, issues, pull requests, and comments.' - - # https://github.com/github/releases/issues/1474 - - Appending `?plain=1` to the URL for any Markdown file will now display the file without rendering and with line numbers. The plain view can be used to link other users to specific lines. For example, appending `?plain=1#L52` will highlight line 52 of a plain text Markdown file. For more information, "[Creating a permanent link to a code snippet](/github/writing-on-github/working-with-advanced-formatting/creating-a-permanent-link-to-a-code-snippet#linking-to-markdown)." - - - heading: 'Issues and pull requests changes' - notes: - # https://github.com/github/releases/issues/1413 - - With the [latest version of Octicons](https://github.com/primer/octicons/releases), the states of issues and pull requests are now more visually distinct so you can scan their status more easily. For more information, see [{% data variables.product.prodname_blog %}](https://github.blog/changelog/2021-06-08-new-issue-and-pull-request-state-icons/). - - # https://github.com/github/releases/issues/1419 - - A new "Require conversation resolution before merging" branch protection rule and "Conversations" menu is now available. Easily discover your pull request comments from the "Files changed" tab, and require that all your pull request conversations are resolved before merging. For more information, see "[About pull request reviews](/github/collaborating-with-pull-requests/reviewing-changes-in-pull-requests/about-pull-request-reviews#discovering-and-navigating-conversations)" and "[About protected branches](/github/administering-a-repository/defining-the-mergeability-of-pull-requests/about-protected-branches#require-conversation-resolution-before-merging)." - - # https://github.com/github/releases/issues/1279 - - To prevent the merge of unexpected changes after auto-merge is enabled for a pull request, auto-merge is now disabled automatically when new changes are pushed by a user without write access to the repository. Users without write access can still update the pull request with changes from the base branch when auto-merge is enabled. To prevent a malicious user from using a merge conflict to introduce unexpected changes to the pull request, auto-merge for the pull request is disabled if the update causes a merge conflict. For more information about auto-merge, see "[Automatically merging a pull request](/github/collaborating-with-pull-requests/incorporating-changes-from-a-pull-request/automatically-merging-a-pull-request)." - - # https://github.com/github/releases/issues/1550 - - People with maintain permissions can now manage the repository-level "Allow auto-merge" setting. This setting, which is off by default, controls whether auto-merge is available on pull requests in the repository. Previously, only people with admin permissions could manage this setting. Additionally, this setting can now by controlled using the "[Create a repository](/rest/reference/repos#create-an-organization-repository)" and "[Update a repository](/rest/reference/repos#update-a-repository)" REST APIs. For more information, see "[Managing auto-merge for pull requests in your repository](/github/administering-a-repository/configuring-pull-request-merges/managing-auto-merge-for-pull-requests-in-your-repository)." - - # https://github.com/github/releases/issues/1201 - - The assignees selection for issues and pull requests now supports type ahead searching so you can find users in your organization faster. Additionally, search result rankings have been updated to prefer matches at the start of a person's username or profile name. - - # https://github.com/github/releases/issues/1430 - - When a review is requested from a team of more than 100 people, developers are now shown a confirmation dialog box in order to prevent unnecessary notifications for large teams. - - # https://github.com/github/releases/issues/1293 - - Back-tick `code blocks` are now supported in issue titles, pull request titles, and in any place issue and pull request titles are referenced in {% data variables.product.prodname_ghe_server %}. - - # https://github.com/github/releases/issues/1300 - - Events for pull requests and pull request reviews are now included in the audit log for both [enterprises](/admin/user-management/managing-users-in-your-enterprise/auditing-users-across-your-enterprise) and [organizations](/organizations/keeping-your-organization-secure/reviewing-the-audit-log-for-your-organization). These events help admins better monitor pull request activity and help ensure security and compliance requirements are being met. Events can be viewed from the web UI, exported as CSV or JSON, or accessed via REST API. You can also search the audit log for specific pull request events. For more information, see "[Reviewing the audit log for your organization](/organizations/keeping-your-organization-secure/reviewing-the-audit-log-for-your-organization#pull_request-category-actions)." - - - heading: 'Branches changes' - notes: - # https://github.com/github/releases/issues/885 - - | - The default branch name for new repositories is now `main`. Existing repositories are not impacted by this change. If users, organization owners, or enterprise owners have previously specified a default branch for new repositories, they are also not impacted. - - If you want to set a different default branch name, you can do so in the [user](/account-and-profile/setting-up-and-managing-your-github-user-account/managing-user-account-settings/managing-the-default-branch-name-for-your-repositories), [organization](/organizations/managing-organization-settings/managing-the-default-branch-name-for-repositories-in-your-organization), or [enterprise](/admin/policies/enforcing-policies-for-your-enterprise/enforcing-repository-management-policies-in-your-enterprise#enforcing-a-policy-on-the-default-branch-name) settings. - - # https://github.com/github/releases/issues/981 - - | - Branches, including the default branch, can now be renamed using the the {% data variables.product.product_name %} web UI. When a branch is renamed, any open pull requests and draft releases targeting the renamed branch will be retargeted automatically, and branch protection rules that explicitly reference the renamed branch will be updated. - - Admin permissions are required to rename the default branch, but write permissions are sufficient to rename other branches. - - To help make the change as seamless as possible for users: - - * A notice is shown to contributors, maintainers, and admins on the repository homepage with instructions for updating their local repository. - * Web requests to the old branch will be redirected. - * A "moved permanently" HTTP response will be returned to REST API calls. - * An informational message is displayed to Git command line users that push to the old branch. - - For more information, see "[Renaming a branch](/github/administering-a-repository/managing-branches-in-your-repository/renaming-a-branch)." - - - heading: 'GitHub Actions changes' - notes: - # https://github.com/github/releases/issues/1227 - - '{% data variables.product.prodname_actions %} now lets you control the permissions granted to the `GITHUB_TOKEN` secret. The `GITHUB_TOKEN` is an automatically-generated secret that lets you make authenticated calls to the API for {% data variables.product.product_name %} in your workflow runs. {% data variables.product.prodname_actions %} generates a new token for each job and expires the token when a job completes. The token usually has `write` permissions to a number of [API endpoints](/actions/reference/authentication-in-a-workflow#permissions-for-the-github_token), except in the case of pull requests from forks, which are always `read`. These new settings allow you to follow a principle of least privilege in your workflows. For more information, see "[Authentication in a workflow](/actions/reference/authentication-in-a-workflow#modifying-the-permissions-for-the-github_token)."' - - # https://github.com/github/releases/issues/1280 - - '{% data variables.product.prodname_cli %} 1.9 and later allows you to work with {% data variables.product.prodname_actions %} in your terminal. For more information, see the [{% data variables.product.prodname_dotcom %} changelog](https://github.blog/changelog/2021-04-15-github-cli-1-9-enables-you-to-work-with-github-actions-from-your-terminal/).' - - # https://github.com/github/releases/issues/1157 - - The audit log now includes events associated with {% data variables.product.prodname_actions %} workflow runs. This data provides administrators with a greatly expanded data set for security and compliance audits. For more information, see "[Reviewing the audit log for your organization](/organizations/keeping-your-organization-secure/reviewing-the-audit-log-for-your-organization#workflows-category-actions)." - - # https://github.com/github/releases/issues/1587 - - Performance improvements have been made to {% data variables.product.prodname_actions %}, which may result in higher maximum job throughput. For more information on job throughput with internally-tested CPU and memory configurations, see "[Getting started with {% data variables.product.prodname_actions %} for {% data variables.product.prodname_ghe_server %}](/admin/github-actions/enabling-github-actions-for-github-enterprise-server/getting-started-with-github-actions-for-github-enterprise-server#review-hardware-considerations)." - - - heading: 'GitHub Packages changes' - notes: - # https://github.com/github/releases/issues/1088 - - Any package or package version for {% data variables.product.prodname_registry %} can now be deleted from {% data variables.product.product_name %}'s web UI. You can also undo the deletion of any package or package version within 30 days. For more information, see "[Deleting and restoring a package](/packages/learn-github-packages/deleting-and-restoring-a-package)". - - - heading: 'Dependabot and Dependency graph changes' - notes: - # https://github.com/github/releases/issues/1537 - - The dependency graph can now be enabled using the Management Console, rather than needing to run a command in the administrative shell. For more information, see "[Enabling alerts for vulnerable dependencies {% data variables.product.prodname_ghe_server %}](/admin/configuration/managing-connections-between-github-enterprise-server-and-github-enterprise-cloud/enabling-alerts-for-vulnerable-dependencies-on-github-enterprise-server#enabling-the-dependency-graph-and-dependabot-alerts-for-vulnerable-dependencies-on-github-enterprise-server)." - - # https://github.com/github/releases/issues/1153 - - Notifications for multiple {% data variables.product.prodname_dependabot_alerts %} are now grouped together if they're discovered at the same time. This significantly reduces the volume of {% data variables.product.prodname_dependabot %} alert notifications that users receive. For more information, see the [{% data variables.product.prodname_dotcom %} changelog](https://github.blog/changelog/2021-03-18-grouped-dependabot-alert-notifications/). - - # https://github.com/github/releases/issues/1371 - - Dependency graph and {% data variables.product.prodname_dependabot_alerts %} now support Go modules. {% data variables.product.prodname_ghe_server %} analyzes a repository's `go.mod` files to understand the repository’s dependencies. Along with security advisories, the dependency graph provides the information needed to alert developers to vulnerable dependencies. For more information about enabling the dependency graph on private repositories, see "[Securing your repository](/code-security/getting-started/securing-your-repository#managing-the-dependency-graph)." - - # https://github.com/github/releases/issues/1538 - - The default notification settings for security alerts have changed. Previously, if you had permission to view security alerts in a repository, you would receive notifications for that repository as long as your settings allowed for security alert notifications. Now, you must opt in to security alert notifications by watching the repository. You will be notified if you select `All Activity` or configure `Custom` to include `Security alerts`. All existing repositories will be automatically migrated to these new settings and you will continue to receive notifications; however, any new repositories will require opting-in by watching the repository. For more information see "[Configuring notifications for {% data variables.product.prodname_dependabot_alerts %}](/code-security/dependabot/dependabot-alerts/configuring-notifications-for-dependabot-alerts)" and "[Managing alerts from secret scanning](/code-security/secret-security/managing-alerts-from-secret-scanning)." - - - heading: 'Code scanning and secret scanning changes' - notes: - # https://github.com/github/releases/issues/1352 - - '{% data variables.product.prodname_code_scanning_capc %} with {% data variables.product.prodname_codeql %} now generates diagnostic information for all supported languages. This helps check the state of the created database to understand the status and quality of performed analysis. The diagnostic information is available starting in [version 2.5.6](https://github.com/github/codeql-cli-binaries/releases) of the [{% data variables.product.prodname_codeql_cli %}](https://codeql.github.com/docs/codeql-cli/). You can see the detailed diagnostic information in the {% data variables.product.prodname_actions %} logs for {% data variables.product.prodname_codeql %}. For more information, see "[Viewing code scanning logs](/code-security/code-scanning/automatically-scanning-your-code-for-vulnerabilities-and-errors/viewing-code-scanning-logs)."' - - # https://github.com/github/releases/issues/1360 - - '{% data variables.product.prodname_code_scanning_capc %} with {% data variables.product.prodname_codeql_cli %} now supports analyzing several languages during a single build. This makes it easier to run code analysis to use CI/CD systems other than {% data variables.product.prodname_actions %}. The new mode of the `codeql database create` command is available starting [version 2.5.6](https://github.com/github/codeql-cli-binaries/releases) of the [{% data variables.product.prodname_codeql_cli %}](https://codeql.github.com/docs/codeql-cli/). For more information about setting this up, see "[Installing {% data variables.product.prodname_codeql_cli %} in your CI system](/code-security/secure-coding/using-codeql-code-scanning-with-your-existing-ci-system/running-codeql-cli-in-your-ci-system)."' - - # https://github.com/github/releases/issues/1160 - - '{% data variables.product.prodname_code_scanning_capc %} alerts from all enabled tools are now shown in one consolidated list, so that you can easily prioritize across all alerts. You can view alerts from a specific tool by using the "Tool" filter, and the "Rule" and "Tag" filters will dynamically update based on your "Tool" selection.' - - # https://github.com/github/releases/issues/1454 - - '{% data variables.product.prodname_code_scanning_capc %} with {% data variables.product.prodname_codeql %} now includes beta support for analyzing C++20 code. This is only available when building codebases with GCC on Linux. C++20 modules are not supported yet.' - - # https://github.com/github/releases/issues/1375 - - The depth of {% data variables.product.prodname_codeql %}'s analysis has been improved by adding support for more [libraries and frameworks](https://codeql.github.com/docs/codeql-overview/supported-languages-and-frameworks/) and increasing the coverage of our existing library and framework models for several languages ([C++](https://github.com/github/codeql/tree/main/cpp), [JavaScript](https://github.com/github/codeql/tree/main/javascript), [Python](https://github.com/github/codeql/tree/main/python), and [Java](https://github.com/github/codeql/tree/main/java)). As a result, {% data variables.product.prodname_codeql %} can now detect even more potential sources of untrusted user data, review the steps through which that data flows, and identify potentially dangerous sinks in which this data could end up. This results in an overall improvement of the quality of the {% data variables.product.prodname_code_scanning %} alerts. For more information, see the [{% data variables.product.prodname_dotcom %} changelog](https://github.blog/changelog/2021-07-01-codeql-code-scanning-now-recognizes-more-sources-and-uses-of-untrusted-user-data/). - - # https://github.com/github/releases/issues/1335 - # https://github.com/github/releases/issues/1314 - - | - {% data variables.product.prodname_code_scanning_capc %} now shows `security-severity` levels for CodeQL security alerts. You can configure which `security-severity` levels will cause a check failure for a pull request. The severity level of security alerts can be `critical`, `high`, `medium`, or `low`. By default, any {% data variables.product.prodname_code_scanning %} alerts with a `security-severity` of `critical` or `high` will cause a pull request check failure. - - Additionally, you can now also configure which severity levels will cause a pull request check to fail for non-security alerts. You can configure this behavior at the repository level, and define whether alerts with the severity `error`, `warning`, or `note` will cause a pull request check to fail. By default, non-security {% data variables.product.prodname_code_scanning %} alerts with a severity of `error` will cause a pull request check failure. - - For more information see "[Defining which alert severity levels cause pull request check failure](/code-security/code-scanning/automatically-scanning-your-code-for-vulnerabilities-and-errors/configuring-code-scanning#defining-the-severities-causing-pull-request-check-failure)." - - ![List of code scanning alerts with security levels](/assets/images/enterprise/3.2/release-notes/code-scanning-alerts.png) - - # https://github.com/github/releases/issues/1324 - - | - Improvements to the branch filter for {% data variables.product.prodname_code_scanning %} alerts make it clearer which {% data variables.product.prodname_code_scanning %} alerts are being displayed on the alerts page. By default, {% data variables.product.prodname_code_scanning %} alerts are filtered to show alerts for the default branch of the repository only. You can use the branch filter to display the alerts on any of the non-default branches. Any branch filter that has been applied is shown in the search bar. - - The search syntax has also been simplified to `branch:`. This syntax can be used multiple times in the search bar to filter on multiple branches. The previous syntax, `ref:refs/heads/`, is still supported, so any saved URLs will continue to work. - - # https://github.com/github/releases/issues/1313 - - | - Free text search is now available for code scanning alerts. You can search code scanning results to quickly find specific alerts without having to know exact search terms. The search is applied across the alert's name, description, and help text. The syntax is: - - - A single word returns all matches. - - Multiple search words returns matches to either word. - - Words in double quotes returns exact matches. - - The keyword 'AND' returns matches to multiple words. - - - '{% data variables.product.prodname_secret_scanning_caps %} added patterns for 23 new service providers. For the updated list of supported secrets, see "[About secret scanning](/code-security/secret-scanning/about-secret-scanning)."' - - - heading: API Changes - notes: - # https://github.com/github/releases/issues/1253 - - Pagination support has been added to the Repositories REST API's "compare two commits" endpoint, which returns a list of commits reachable from one commit or branch, but unreachable from another. The API can also now return the results for comparisons over 250 commits. For more information, see the "[Commits](/rest/reference/commits#compare-two-commits)" REST API documentation and "[Traversing with pagination](/rest/guides/traversing-with-pagination)." - - # https://github.com/github/releases/issues/969 - - The REST API can now be used to programmatically resend or check the status of webhooks. For more information, see "[Webhooks](/rest/reference/webhooks)," "[Organizations](/rest/reference/orgs#webhooks)," and "[Apps](/rest/reference/apps#webhooks)" in the REST API documentation. - - # https://github.com/github/releases/issues/1349 - - | - Improvements have been made to the code scanning and {% data variables.product.prodname_GH_advanced_security %} APIs: - - - The code scanning API now returns the CodeQL query version used for an analysis. This can be used to reproduce results or confirm that an analysis used the latest query. For more information, see "[Code scanning](/rest/reference/code-scanning#list-code-scanning-alerts-for-a-repository)" in the REST API documentation. - - Admin users can now use the REST API to enable or disable {% data variables.product.prodname_GH_advanced_security %} for repositories, using the `security_and_analysis` object on `repos/{org}/{repo}`. In addition, admin users can check whether {% data variables.product.prodname_advanced_security %} is currently enabled for a repository by using a `GET /repos/{owner}/{repo}` request. These changes help you manage {% data variables.product.prodname_advanced_security %} repository access at scale. For more information, see "[Repositories](/rest/reference/repos#update-a-repository)" in the REST API documentation. - - # No security/bug fixes for the RC release - # security_fixes: - # - PLACEHOLDER - - # bugs: - # - PLACEHOLDER - - known_issues: - - On a freshly set up {% data variables.product.prodname_ghe_server %} 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. - - deprecations: - - heading: Deprecation of GitHub Enterprise Server 2.21 - notes: - - '**{% data variables.product.prodname_ghe_server %} 2.21 was discontinued on June 6, 2021**. That means that no patch releases will be made, even for critical security issues, after this date. For better performance, improved security, and new features, [upgrade to the newest version of {% data variables.product.prodname_ghe_server %}](/enterprise-server@3.2/admin/enterprise-management/upgrading-github-enterprise-server) as soon as possible.' - - heading: Deprecation of GitHub Enterprise Server 2.22 - notes: - - '**{% data variables.product.prodname_ghe_server %} 2.22 will be discontinued on September 23, 2021**. That means that no patch releases will be made, even for critical security issues, after this date. For better performance, improved security, and new features, [upgrade to the newest version of {% data variables.product.prodname_ghe_server %}](/enterprise-server@3.2/admin/enterprise-management/upgrading-github-enterprise-server) as soon as possible.' - - heading: Deprecation of XenServer Hypervisor support - notes: - # https://github.com/github/docs-content/issues/4439 - - Beginning in {% data variables.product.prodname_ghe_server %} 3.1, we will begin discontinuing support for Xen Hypervisor. The complete deprecation is scheduled for {% data variables.product.prodname_ghe_server %} 3.3, following the standard one year deprecation window. Please contact [GitHub Support](https://support.github.com/contact) with questions or concerns. - - heading: Removal of Legacy GitHub Services - notes: - # https://github.com/github/releases/issues/1506 - - '{% data variables.product.prodname_ghe_server %} 3.2 removes unused GitHub Service database records. More information is available in the [deprecation announcement post](https://developer.github.com/changes/2018-04-25-github-services-deprecation/).' - - heading: Deprecation of OAuth Application API endpoints and API authentication via query parameters - notes: - # https://github.com/github/releases/issues/1316 - - | - To prevent accidental logging or exposure of `access_tokens`, we discourage the use of OAuth Application API endpoints and the use of API auth via query params. Visit the following posts to see the proposed replacements: - - * [Replacement OAuth Application API endpoints](https://developer.github.com/changes/2020-02-14-deprecating-oauth-app-endpoint/#changes-to-make) - * [Replacement auth via headers instead of query param](https://developer.github.com/changes/2020-02-10-deprecating-auth-through-query-param/#changes-to-make) - - These endpoints and auth route are planned to be removed from {% data variables.product.prodname_ghe_server %} in {% data variables.product.prodname_ghe_server %} 3.4. - - heading: Removal of legacy GitHub App webhook events and endpoints - notes: - # https://github.com/github/releases/issues/965 - - | - Two legacy GitHub Apps-related webhook events have been removed: `integration_installation` and `integration_installation_repositories`. You should instead be listening to the `installation` and `installation_repositories` events. - - | - The following REST API endpoint has been removed: `POST /installations/{installation_id}/access_tokens`. You should instead be using the namespaced equivalent `POST /app/installations/{installation_id}/access_tokens`. - - backups: - - '{% data variables.product.prodname_ghe_server %} 3.2 requires at least [GitHub Enterprise Backup Utilities 3.2.0](https://github.com/github/backup-utils) for [Backups and Disaster Recovery](/enterprise-server@3.2/admin/configuration/configuring-backups-on-your-appliance).' + - Uploading video files is now supported everywhere you write Markdown on {% data variables.product.pro \ No newline at end of file diff --git a/translations/zh-CN/data/release-notes/enterprise-server/3-2/0.yml b/translations/zh-CN/data/release-notes/enterprise-server/3-2/0.yml index ba34f7a61d3e..aed77c126fc8 100644 --- a/translations/zh-CN/data/release-notes/enterprise-server/3-2/0.yml +++ b/translations/zh-CN/data/release-notes/enterprise-server/3-2/0.yml @@ -101,217 +101,4 @@ sections: - The markdown editor used when creating or editing a release in a repository now has a text-editing toolbar. For more information, see "[Managing releases in a repository](/github/administering-a-repository/releasing-projects-on-github/managing-releases-in-a-repository#creating-a-release)." # https://github.com/github/releases/issues/1169 - - Uploading video files is now supported everywhere you write Markdown on {% data variables.product.product_name %}. Share demos, reproduction steps, and more in your issue and pull request comments, as well as in Markdown files within repositories, such as READMEs. For more information, see "[Attaching files](/github/writing-on-github/working-with-advanced-formatting/attaching-files)." - - # https://github.com/github/releases/issues/1269 - - Markdown files will now automatically generate a table of contents in the header when there are 2 or more headings. The table of contents is interactive and links to the selected section. All 6 Markdown heading levels are supported. - - # https://github.com/github/releases/issues/1294 - - 'There is a new keyboard shortcut, `cmd+e` on macOS or `ctrl+e` on Windows, to insert codeblocks in Markdown files, issues, pull requests, and comments.' - - # https://github.com/github/releases/issues/1474 - - Appending `?plain=1` to the URL for any Markdown file will now display the file without rendering and with line numbers. The plain view can be used to link other users to specific lines. For example, appending `?plain=1#L52` will highlight line 52 of a plain text Markdown file. For more information, "[Creating a permanent link to a code snippet](/github/writing-on-github/working-with-advanced-formatting/creating-a-permanent-link-to-a-code-snippet#linking-to-markdown)." - - - heading: 'Issues and pull requests changes' - notes: - # https://github.com/github/releases/issues/1413 - - With the [latest version of Octicons](https://github.com/primer/octicons/releases), the states of issues and pull requests are now more visually distinct so you can scan their status more easily. For more information, see [{% data variables.product.prodname_blog %}](https://github.blog/changelog/2021-06-08-new-issue-and-pull-request-state-icons/). - - # https://github.com/github/releases/issues/1419 - - A new "Require conversation resolution before merging" branch protection rule and "Conversations" menu is now available. Easily discover your pull request comments from the "Files changed" tab, and require that all your pull request conversations are resolved before merging. For more information, see "[About pull request reviews](/github/collaborating-with-pull-requests/reviewing-changes-in-pull-requests/about-pull-request-reviews#discovering-and-navigating-conversations)" and "[About protected branches](/github/administering-a-repository/defining-the-mergeability-of-pull-requests/about-protected-branches#require-conversation-resolution-before-merging)." - - # https://github.com/github/releases/issues/1279 - - To prevent the merge of unexpected changes after auto-merge is enabled for a pull request, auto-merge is now disabled automatically when new changes are pushed by a user without write access to the repository. Users without write access can still update the pull request with changes from the base branch when auto-merge is enabled. To prevent a malicious user from using a merge conflict to introduce unexpected changes to the pull request, auto-merge for the pull request is disabled if the update causes a merge conflict. For more information about auto-merge, see "[Automatically merging a pull request](/github/collaborating-with-pull-requests/incorporating-changes-from-a-pull-request/automatically-merging-a-pull-request)." - - # https://github.com/github/releases/issues/1550 - - People with maintain permissions can now manage the repository-level "Allow auto-merge" setting. This setting, which is off by default, controls whether auto-merge is available on pull requests in the repository. Previously, only people with admin permissions could manage this setting. Additionally, this setting can now by controlled using the "[Create a repository](/rest/reference/repos#create-an-organization-repository)" and "[Update a repository](/rest/reference/repos#update-a-repository)" REST APIs. For more information, see "[Managing auto-merge for pull requests in your repository](/github/administering-a-repository/configuring-pull-request-merges/managing-auto-merge-for-pull-requests-in-your-repository)." - - # https://github.com/github/releases/issues/1201 - - The assignees selection for issues and pull requests now supports type ahead searching so you can find users in your organization faster. Additionally, search result rankings have been updated to prefer matches at the start of a person's username or profile name. - - # https://github.com/github/releases/issues/1430 - - When a review is requested from a team of more than 100 people, developers are now shown a confirmation dialog box in order to prevent unnecessary notifications for large teams. - - # https://github.com/github/releases/issues/1293 - - Back-tick `code blocks` are now supported in issue titles, pull request titles, and in any place issue and pull request titles are referenced in {% data variables.product.prodname_ghe_server %}. - - # https://github.com/github/releases/issues/1300 - - Events for pull requests and pull request reviews are now included in the audit log for both [enterprises](/admin/user-management/managing-users-in-your-enterprise/auditing-users-across-your-enterprise) and [organizations](/organizations/keeping-your-organization-secure/reviewing-the-audit-log-for-your-organization). These events help admins better monitor pull request activity and help ensure security and compliance requirements are being met. Events can be viewed from the web UI, exported as CSV or JSON, or accessed via REST API. You can also search the audit log for specific pull request events. For more information, see "[Reviewing the audit log for your organization](/organizations/keeping-your-organization-secure/reviewing-the-audit-log-for-your-organization#pull_request-category-actions)." - - - heading: 'Branches changes' - notes: - # https://github.com/github/releases/issues/885 - - | - The default branch name for new repositories is now `main`. Existing repositories are not impacted by this change. If users, organization owners, or enterprise owners have previously specified a default branch for new repositories, they are also not impacted. - - If you want to set a different default branch name, you can do so in the [user](/account-and-profile/setting-up-and-managing-your-github-user-account/managing-user-account-settings/managing-the-default-branch-name-for-your-repositories), [organization](/organizations/managing-organization-settings/managing-the-default-branch-name-for-repositories-in-your-organization), or [enterprise](/admin/policies/enforcing-policies-for-your-enterprise/enforcing-repository-management-policies-in-your-enterprise#enforcing-a-policy-on-the-default-branch-name) settings. - - # https://github.com/github/releases/issues/981 - - | - Branches, including the default branch, can now be renamed using the the {% data variables.product.product_name %} web UI. When a branch is renamed, any open pull requests and draft releases targeting the renamed branch will be retargeted automatically, and branch protection rules that explicitly reference the renamed branch will be updated. - - Admin permissions are required to rename the default branch, but write permissions are sufficient to rename other branches. - - To help make the change as seamless as possible for users: - - * A notice is shown to contributors, maintainers, and admins on the repository homepage with instructions for updating their local repository. - * Web requests to the old branch will be redirected. - * A "moved permanently" HTTP response will be returned to REST API calls. - * An informational message is displayed to Git command line users that push to the old branch. - - For more information, see "[Renaming a branch](/github/administering-a-repository/managing-branches-in-your-repository/renaming-a-branch)." - - - heading: 'GitHub Actions changes' - notes: - # https://github.com/github/releases/issues/1227 - - '{% data variables.product.prodname_actions %} now lets you control the permissions granted to the `GITHUB_TOKEN` secret. The `GITHUB_TOKEN` is an automatically-generated secret that lets you make authenticated calls to the API for {% data variables.product.product_name %} in your workflow runs. {% data variables.product.prodname_actions %} generates a new token for each job and expires the token when a job completes. The token usually has `write` permissions to a number of [API endpoints](/actions/reference/authentication-in-a-workflow#permissions-for-the-github_token), except in the case of pull requests from forks, which are always `read`. These new settings allow you to follow a principle of least privilege in your workflows. For more information, see "[Authentication in a workflow](/actions/reference/authentication-in-a-workflow#modifying-the-permissions-for-the-github_token)."' - - # https://github.com/github/releases/issues/1280 - - '{% data variables.product.prodname_cli %} 1.9 and later allows you to work with {% data variables.product.prodname_actions %} in your terminal. For more information, see the [{% data variables.product.prodname_dotcom %} changelog](https://github.blog/changelog/2021-04-15-github-cli-1-9-enables-you-to-work-with-github-actions-from-your-terminal/).' - - # https://github.com/github/releases/issues/1157 - - The audit log now includes events associated with {% data variables.product.prodname_actions %} workflow runs. This data provides administrators with a greatly expanded data set for security and compliance audits. For more information, see "[Reviewing the audit log for your organization](/organizations/keeping-your-organization-secure/reviewing-the-audit-log-for-your-organization#workflows-category-actions)." - - # https://github.com/github/releases/issues/1587 - - | - {% data variables.product.prodname_ghe_server %} 3.2 contains performance improvements for job concurrency with {% data variables.product.prodname_actions %}. For more information about the new performance targets for a range of CPU and memory configurations, see "[Getting started with {% data variables.product.prodname_actions %} for {% data variables.product.prodname_ghe_server %}](/admin/github-actions/enabling-github-actions-for-github-enterprise-server/getting-started-with-github-actions-for-github-enterprise-server#review-hardware-considerations)." - * The "Maximum Concurrency" values were modified to reflect our most up to date performance testing. [Updated: 2021-12-07] - - - The [{% data variables.product.prodname_actions %} Runner](https://github.com/actions/runner) application in {% data variables.product.prodname_ghe_server %} 3.2 has been updated to [v2.279.0](https://github.com/actions/runner/releases/tag/v2.279.0). - - - heading: 'GitHub Packages changes' - notes: - # https://github.com/github/releases/issues/1088 - - Any package or package version for {% data variables.product.prodname_registry %} can now be deleted from {% data variables.product.product_name %}'s web UI. You can also undo the deletion of any package or package version within 30 days. For more information, see "[Deleting and restoring a package](/packages/learn-github-packages/deleting-and-restoring-a-package)". - - - heading: 'Dependabot and Dependency graph changes' - notes: - # https://github.com/github/releases/issues/1537 - - The dependency graph can now be enabled using the Management Console, rather than needing to run a command in the administrative shell. For more information, see "[Enabling alerts for vulnerable dependencies {% data variables.product.prodname_ghe_server %}](/admin/configuration/managing-connections-between-github-enterprise-server-and-github-enterprise-cloud/enabling-alerts-for-vulnerable-dependencies-on-github-enterprise-server#enabling-the-dependency-graph-and-dependabot-alerts-for-vulnerable-dependencies-on-github-enterprise-server)." - - # https://github.com/github/releases/issues/1153 - - Notifications for multiple {% data variables.product.prodname_dependabot_alerts %} are now grouped together if they're discovered at the same time. This significantly reduces the volume of {% data variables.product.prodname_dependabot %} alert notifications that users receive. For more information, see the [{% data variables.product.prodname_dotcom %} changelog](https://github.blog/changelog/2021-03-18-grouped-dependabot-alert-notifications/). - - # https://github.com/github/releases/issues/1371 - - Dependency graph and {% data variables.product.prodname_dependabot_alerts %} now support Go modules. {% data variables.product.prodname_ghe_server %} analyzes a repository's `go.mod` files to understand the repository’s dependencies. Along with security advisories, the dependency graph provides the information needed to alert developers to vulnerable dependencies. For more information about enabling the dependency graph on private repositories, see "[Securing your repository](/code-security/getting-started/securing-your-repository#managing-the-dependency-graph)." - - # https://github.com/github/releases/issues/1538 - - The default notification settings for security alerts have changed. Previously, if you had permission to view security alerts in a repository, you would receive notifications for that repository as long as your settings allowed for security alert notifications. Now, you must opt in to security alert notifications by watching the repository. You will be notified if you select `All Activity` or configure `Custom` to include `Security alerts`. All existing repositories will be automatically migrated to these new settings and you will continue to receive notifications; however, any new repositories will require opting-in by watching the repository. For more information see "[Configuring notifications for {% data variables.product.prodname_dependabot_alerts %}](/code-security/dependabot/dependabot-alerts/configuring-notifications-for-dependabot-alerts)" and "[Managing alerts from secret scanning](/code-security/secret-security/managing-alerts-from-secret-scanning)." - - - heading: 'Code scanning and secret scanning changes' - notes: - # https://github.com/github/releases/issues/1352 - - '{% data variables.product.prodname_code_scanning_capc %} with {% data variables.product.prodname_codeql %} now generates diagnostic information for all supported languages. This helps check the state of the created database to understand the status and quality of performed analysis. The diagnostic information is available starting in [version 2.5.6](https://github.com/github/codeql-cli-binaries/releases) of the [{% data variables.product.prodname_codeql_cli %}](https://codeql.github.com/docs/codeql-cli/). You can see the detailed diagnostic information in the {% data variables.product.prodname_actions %} logs for {% data variables.product.prodname_codeql %}. For more information, see "[Viewing code scanning logs](/code-security/code-scanning/automatically-scanning-your-code-for-vulnerabilities-and-errors/viewing-code-scanning-logs)."' - - # https://github.com/github/releases/issues/1360 - - '{% data variables.product.prodname_code_scanning_capc %} with {% data variables.product.prodname_codeql_cli %} now supports analyzing several languages during a single build. This makes it easier to run code analysis to use CI/CD systems other than {% data variables.product.prodname_actions %}. The new mode of the `codeql database create` command is available starting [version 2.5.6](https://github.com/github/codeql-cli-binaries/releases) of the [{% data variables.product.prodname_codeql_cli %}](https://codeql.github.com/docs/codeql-cli/). For more information about setting this up, see "[Installing {% data variables.product.prodname_codeql_cli %} in your CI system](/code-security/secure-coding/using-codeql-code-scanning-with-your-existing-ci-system/running-codeql-cli-in-your-ci-system)."' - - # https://github.com/github/releases/issues/1160 - - '{% data variables.product.prodname_code_scanning_capc %} alerts from all enabled tools are now shown in one consolidated list, so that you can easily prioritize across all alerts. You can view alerts from a specific tool by using the "Tool" filter, and the "Rule" and "Tag" filters will dynamically update based on your "Tool" selection.' - - # https://github.com/github/releases/issues/1454 - - '{% data variables.product.prodname_code_scanning_capc %} with {% data variables.product.prodname_codeql %} now includes beta support for analyzing C++20 code. This is only available when building codebases with GCC on Linux. C++20 modules are not supported yet.' - - # https://github.com/github/releases/issues/1375 - - The depth of {% data variables.product.prodname_codeql %}'s analysis has been improved by adding support for more [libraries and frameworks](https://codeql.github.com/docs/codeql-overview/supported-languages-and-frameworks/) and increasing the coverage of our existing library and framework models for several languages ([C++](https://github.com/github/codeql/tree/main/cpp), [JavaScript](https://github.com/github/codeql/tree/main/javascript), [Python](https://github.com/github/codeql/tree/main/python), and [Java](https://github.com/github/codeql/tree/main/java)). As a result, {% data variables.product.prodname_codeql %} can now detect even more potential sources of untrusted user data, review the steps through which that data flows, and identify potentially dangerous sinks in which this data could end up. This results in an overall improvement of the quality of the {% data variables.product.prodname_code_scanning %} alerts. For more information, see the [{% data variables.product.prodname_dotcom %} changelog](https://github.blog/changelog/2021-07-01-codeql-code-scanning-now-recognizes-more-sources-and-uses-of-untrusted-user-data/). - - # https://github.com/github/releases/issues/1335 - # https://github.com/github/releases/issues/1314 - - | - {% data variables.product.prodname_code_scanning_capc %} now shows `security-severity` levels for CodeQL security alerts. You can configure which `security-severity` levels will cause a check failure for a pull request. The severity level of security alerts can be `critical`, `high`, `medium`, or `low`. By default, any {% data variables.product.prodname_code_scanning %} alerts with a `security-severity` of `critical` or `high` will cause a pull request check failure. - - Additionally, you can now also configure which severity levels will cause a pull request check to fail for non-security alerts. You can configure this behavior at the repository level, and define whether alerts with the severity `error`, `warning`, or `note` will cause a pull request check to fail. By default, non-security {% data variables.product.prodname_code_scanning %} alerts with a severity of `error` will cause a pull request check failure. - - For more information see "[Defining which alert severity levels cause pull request check failure](/code-security/code-scanning/automatically-scanning-your-code-for-vulnerabilities-and-errors/configuring-code-scanning#defining-the-severities-causing-pull-request-check-failure)." - - ![List of code scanning alerts with security levels](/assets/images/enterprise/3.2/release-notes/code-scanning-alerts.png) - - # https://github.com/github/releases/issues/1324 - - | - Improvements to the branch filter for {% data variables.product.prodname_code_scanning %} alerts make it clearer which {% data variables.product.prodname_code_scanning %} alerts are being displayed on the alerts page. By default, {% data variables.product.prodname_code_scanning %} alerts are filtered to show alerts for the default branch of the repository only. You can use the branch filter to display the alerts on any of the non-default branches. Any branch filter that has been applied is shown in the search bar. - - The search syntax has also been simplified to `branch:`. This syntax can be used multiple times in the search bar to filter on multiple branches. The previous syntax, `ref:refs/heads/`, is still supported, so any saved URLs will continue to work. - - # https://github.com/github/releases/issues/1313 - - | - Free text search is now available for code scanning alerts. You can search code scanning results to quickly find specific alerts without having to know exact search terms. The search is applied across the alert's name, description, and help text. The syntax is: - - - A single word returns all matches. - - Multiple search words returns matches to either word. - - Words in double quotes returns exact matches. - - The keyword 'AND' returns matches to multiple words. - - - '{% data variables.product.prodname_secret_scanning_caps %} added patterns for 23 new service providers. For the updated list of supported secrets, see "[About secret scanning](/code-security/secret-scanning/about-secret-scanning)."' - - - heading: API Changes - notes: - # https://github.com/github/releases/issues/1253 - - Pagination support has been added to the Repositories REST API's "compare two commits" endpoint, which returns a list of commits reachable from one commit or branch, but unreachable from another. The API can also now return the results for comparisons over 250 commits. For more information, see the "[Commits](/rest/reference/commits#compare-two-commits)" REST API documentation and "[Traversing with pagination](/rest/guides/traversing-with-pagination)." - - # https://github.com/github/releases/issues/969 - - The REST API can now be used to programmatically resend or check the status of webhooks. For more information, see "[Repositories](/rest/reference/repos#webhooks)," "[Organizations](/rest/reference/orgs#webhooks)," and "[Apps](/rest/reference/apps#webhooks)" in the REST API documentation. - - # https://github.com/github/releases/issues/1349 - - | - Improvements have been made to the code scanning and {% data variables.product.prodname_GH_advanced_security %} APIs: - - - The code scanning API now returns the CodeQL query version used for an analysis. This can be used to reproduce results or confirm that an analysis used the latest query. For more information, see "[Code scanning](/rest/reference/code-scanning#list-code-scanning-alerts-for-a-repository)" in the REST API documentation. - - Admin users can now use the REST API to enable or disable {% data variables.product.prodname_GH_advanced_security %} for repositories, using the `security_and_analysis` object on `repos/{org}/{repo}`. In addition, admin users can check whether {% data variables.product.prodname_advanced_security %} is currently enabled for a repository by using a `GET /repos/{owner}/{repo}` request. These changes help you manage {% data variables.product.prodname_advanced_security %} repository access at scale. For more information, see "[Repositories](/rest/reference/repos#update-a-repository)" in the REST API documentation. - - # No security/bug fixes for the RC release - # security_fixes: - # - PLACEHOLDER - - # bugs: - # - PLACEHOLDER - - known_issues: - - On a freshly set up {% data variables.product.prodname_ghe_server %} 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. - - '{% data reusables.release-notes.ghas-3.4-secret-scanning-known-issue %}' - - deprecations: - - heading: Deprecation of GitHub Enterprise Server 2.21 - notes: - - '**{% data variables.product.prodname_ghe_server %} 2.21 was discontinued on June 6, 2021**. That means that no patch releases will be made, even for critical security issues, after this date. For better performance, improved security, and new features, [upgrade to the newest version of {% data variables.product.prodname_ghe_server %}](/enterprise-server@3.2/admin/enterprise-management/upgrading-github-enterprise-server) as soon as possible.' - - heading: Deprecation of GitHub Enterprise Server 2.22 - notes: - - '**{% data variables.product.prodname_ghe_server %} 2.22 will be discontinued on September 23, 2021**. That means that no patch releases will be made, even for critical security issues, after this date. For better performance, improved security, and new features, [upgrade to the newest version of {% data variables.product.prodname_ghe_server %}](/enterprise-server@3.2/admin/enterprise-management/upgrading-github-enterprise-server) as soon as possible.' - - heading: Deprecation of XenServer Hypervisor support - notes: - # https://github.com/github/docs-content/issues/4439 - - Beginning in {% data variables.product.prodname_ghe_server %} 3.1, we will begin discontinuing support for Xen Hypervisor. The complete deprecation is scheduled for {% data variables.product.prodname_ghe_server %} 3.3, following the standard one year deprecation window. Please contact [GitHub Support](https://support.github.com/contact) with questions or concerns. - - heading: Removal of Legacy GitHub Services - notes: - # https://github.com/github/releases/issues/1506 - - '{% data variables.product.prodname_ghe_server %} 3.2 removes unused GitHub Service database records. More information is available in the [deprecation announcement post](https://developer.github.com/changes/2018-04-25-github-services-deprecation/).' - - heading: Deprecation of OAuth Application API endpoints and API authentication via query parameters - notes: - # https://github.com/github/releases/issues/1316 - - | - To prevent accidental logging or exposure of `access_tokens`, we discourage the use of OAuth Application API endpoints and the use of API auth via query params. Visit the following posts to see the proposed replacements: - - * [Replacement OAuth Application API endpoints](https://developer.github.com/changes/2020-02-14-deprecating-oauth-app-endpoint/#changes-to-make) - * [Replacement auth via headers instead of query param](https://developer.github.com/changes/2020-02-10-deprecating-auth-through-query-param/#changes-to-make) - - These endpoints and auth route are planned to be removed from {% data variables.product.prodname_ghe_server %} in {% data variables.product.prodname_ghe_server %} 3.4. - - heading: Removal of legacy GitHub App webhook events and endpoints - notes: - # https://github.com/github/releases/issues/965 - - | - Two legacy GitHub Apps-related webhook events have been removed: `integration_installation` and `integration_installation_repositories`. You should instead be listening to the `installation` and `installation_repositories` events. - - | - The following REST API endpoint has been removed: `POST /installations/{installation_id}/access_tokens`. You should instead be using the namespaced equivalent `POST /app/installations/{installation_id}/access_tokens`. - - heading: Change to the format of authentication tokens affects GitHub Connect - notes: - # https://github.com/github/releases/issues/1235 - - | - GitHub Connect will no longer work after June 3rd for instances running GitHub Enterprise Server 3.1 or older, due to the format of GitHub authentication tokens changing. To continue using GitHub Connect, upgrade to GitHub Enterprise Server 3.2 or later. For more information, see the [GitHub Blog](https://github.blog/2022-05-20-action-needed-by-github-connect-customers-using-ghes-3-1-and-older-to-adopt-new-authentication-token-format-updates/). [Updated: 2022-06-14] - - backups: - - '{% data variables.product.prodname_ghe_server %} 3.2 requires at least [GitHub Enterprise Backup Utilities 3.2.0](https://github.com/github/backup-utils) for [Backups and Disaster Recovery](/enterprise-server@3.2/admin/configuration/configuring-backups-on-your-appliance).' + - Uploading video files is now supported everywhe \ No newline at end of file diff --git a/translations/zh-CN/data/release-notes/enterprise-server/3-2/1.yml b/translations/zh-CN/data/release-notes/enterprise-server/3-2/1.yml index 09c7e2745f50..68d9c3b4a292 100644 --- a/translations/zh-CN/data/release-notes/enterprise-server/3-2/1.yml +++ b/translations/zh-CN/data/release-notes/enterprise-server/3-2/1.yml @@ -20,7 +20,7 @@ sections: known_issues: - "在新建的没有任何用户的 {% data variables.product.prodname_ghe_server %} 上，攻击者可以创建第一个管理员用户。" - 自定义防火墙规则在升级过程中被删除。 - - "[通过 Web 界面上传](https://github.com/blog/2105-upload-files-to-your-repositories)的 Git LFS 跟踪文件被错误地直接添加到存储库。" + - "[通过 Web 界面上传](https://github.com/blog/2105-upload-files-to-your-repositories) 的 Git LFS 跟踪文件被错误地直接添加到存储库。" - 如果问题包含文件路径长于 255 个字符的同一存储库中 blob 的永久链接，则问题无法关闭。 - 在 GitHub Connect 中启用了“用户可以搜索 GitHub.com”时，专用和内部存储库中的问题不包括在 GitHub.com 搜索结果中。 - "{% data variables.product.prodname_registry %} npm 注册表不再在元数据响应中返回时间值。这样做是为了大幅改善性能。作为元数据响应的一部分，我们继续拥有返回时间值所需的所有数据，并将在我们解决现有性能问题后恢复返回这个值。" diff --git a/translations/zh-CN/data/release-notes/enterprise-server/3-2/10.yml b/translations/zh-CN/data/release-notes/enterprise-server/3-2/10.yml index 654001252d7a..991db42fde06 100644 --- a/translations/zh-CN/data/release-notes/enterprise-server/3-2/10.yml +++ b/translations/zh-CN/data/release-notes/enterprise-server/3-2/10.yml @@ -8,7 +8,7 @@ sections: known_issues: - "在新建的没有任何用户的 {% data variables.product.prodname_ghe_server %} 实例上，攻击者可以创建第一个管理员用户。" - 自定义防火墙规则在升级过程中被删除。 - - "[通过 Web 界面上传](https://github.com/blog/2105-upload-files-to-your-repositories)的 Git LFS 跟踪文件被错误地直接添加到存储库。" + - "[通过 Web 界面上传](https://github.com/blog/2105-upload-files-to-your-repositories) 的 Git LFS 跟踪文件被错误地直接添加到存储库。" - 如果问题包含同一存储库中文件路径长于 255 个字符的 blob 的永久链接，则无法关闭。 - 在 GitHub Connect 中启用了“用户可以搜索 GitHub.com”时，专用和内部存储库中的问题不包括在 GitHub.com 搜索结果中。 - "{% data variables.product.prodname_registry %} npm 注册表不再在元数据响应中返回时间值。这样可以大幅改善性能。我们继续拥有将时间值作为元数据响应的一部分返回所需的所有数据，并将在以后解决现有性能问题后恢复返回该值。" diff --git a/translations/zh-CN/data/release-notes/enterprise-server/3-2/11.yml b/translations/zh-CN/data/release-notes/enterprise-server/3-2/11.yml index bafb1315de2b..75846bcc129f 100644 --- a/translations/zh-CN/data/release-notes/enterprise-server/3-2/11.yml +++ b/translations/zh-CN/data/release-notes/enterprise-server/3-2/11.yml @@ -36,7 +36,7 @@ sections: known_issues: - "在新建的没有任何用户的 {% data variables.product.prodname_ghe_server %} 实例上，攻击者可以创建第一个管理员用户。" - 自定义防火墙规则在升级过程中被移除。 - - "[通过 Web 界面上传](https://github.com/blog/2105-upload-files-to-your-repositories)的 Git LFS 跟踪文件被错误地直接添加到存储库。" + - "[通过 Web 界面上传](https://github.com/blog/2105-upload-files-to-your-repositories) 的 Git LFS 跟踪文件被错误地直接添加到存储库。" - 如果问题包含同一存储库中 blob 的永久链接并且该 blob de 文件路径长于 255 个字符，则问题无法关闭。 - "对 {% data variables.product.prodname_github_connect %} 启用“用户可以搜索 GitHub.com”后，专用和内部存储库中的问题不包括在 {% data variables.product.prodname_dotcom_the_website %} 搜索结果中。" - "{% data variables.product.prodname_registry %} npm 注册表不再在元数据响应中返回时间值。这样做是为了大幅改善性能。我们继续拥有将时间值作为元数据响应的一部分返回所需的所有数据，并将在以后解决现有性能问题后恢复返回该值。" diff --git a/translations/zh-CN/data/release-notes/enterprise-server/3-2/12.yml b/translations/zh-CN/data/release-notes/enterprise-server/3-2/12.yml index 5543b2fb4181..70bc34bb4630 100644 --- a/translations/zh-CN/data/release-notes/enterprise-server/3-2/12.yml +++ b/translations/zh-CN/data/release-notes/enterprise-server/3-2/12.yml @@ -16,7 +16,7 @@ sections: known_issues: - "在新建的没有任何用户的 {% data variables.product.prodname_ghe_server %} 实例上，攻击者可以创建第一个管理员用户。" - 自定义防火墙规则在升级过程中被删除。 - - "[通过 Web 界面上传](https://github.com/blog/2105-upload-files-to-your-repositories)的 Git LFS 跟踪文件被错误地直接添加到存储库。" + - "[通过 Web 界面上传](https://github.com/blog/2105-upload-files-to-your-repositories) 的 Git LFS 跟踪文件被错误地直接添加到存储库。" - 如果问题包含文件路径长于 255 个字符的同一存储库中 blob 的永久链接，则问题无法关闭。 - "对 {% data variables.product.prodname_github_connect %} 启用“用户可以搜索 GitHub.com”后，专用和内部存储库中的问题不包括在 {% data variables.product.prodname_dotcom_the_website %} 搜索结果中。" - "{% data variables.product.prodname_registry %} npm 注册表不再在元数据响应中返回时间值。这样可以大幅改善性能。我们继续拥有将时间值作为元数据响应的一部分返回所需的所有数据，并将在以后解决现有性能问题后恢复返回该值。" diff --git a/translations/zh-CN/data/release-notes/enterprise-server/3-2/13.yml b/translations/zh-CN/data/release-notes/enterprise-server/3-2/13.yml index 68abc622b70e..ce9471be0c27 100644 --- a/translations/zh-CN/data/release-notes/enterprise-server/3-2/13.yml +++ b/translations/zh-CN/data/release-notes/enterprise-server/3-2/13.yml @@ -2,7 +2,7 @@ date: '2022-05-17' sections: security_fixes: - '**中：**发现了 nginx 解析器中的一个安全问题，可以从 DNS 服务器伪造 UDP 数据包的攻击者可能导致 1 字节内存覆盖，从而导致工作进程崩溃或其他潜在的破坏性影响。该漏洞的编号为 [CVE-2021-23017](https://nvd.nist.gov/vuln/detail/CVE-2021-23017)。' - - "更新了 `actions/checkout@v2` 和 `actions/checkout@v3` 操作以解决 [Git 安全措施实施博客文章](https://github.blog/2022-04-12-git-security-vulnerability-announced/)中公布的新漏洞。" + - "更新了 `actions/checkout@v2` 和 `actions/checkout@v3` 操作以解决 [Git 安全措施实施博客文章](https://github.blog/2022-04-12-git-security-vulnerability-announced/) 中公布的新漏洞。" - 包已更新到最新的安全版本。 bugs: - 在某些群集拓扑中，`ghe-cluster-status` 命令会在 `/tmp` 中留下空目录。 @@ -20,7 +20,7 @@ sections: known_issues: - "在新建的没有任何用户的 {% data variables.product.prodname_ghe_server %} 实例上，攻击者可以创建第一个管理员用户。" - 自定义防火墙规则在升级过程中被移除。 - - "[通过 Web 界面上传](https://github.com/blog/2105-upload-files-to-your-repositories)的 Git LFS 跟踪文件被错误地直接添加到存储库。" + - "[通过 Web 界面上传](https://github.com/blog/2105-upload-files-to-your-repositories) 的 Git LFS 跟踪文件被错误地直接添加到存储库。" - 如果问题包含同一存储库中文件路径长于 255 个字符的 blob 的永久链接，则无法关闭。 - "对 {% data variables.product.prodname_github_connect %} 启用“用户可以搜索 GitHub.com”后，专用和内部存储库中的问题不包括在 {% data variables.product.prodname_dotcom_the_website %} 搜索结果中。" - "{% data variables.product.prodname_registry %} npm 注册表不再在元数据响应中返回时间值。这样做是为了大幅改善性能。我们继续拥有将时间值作为元数据响应的一部分返回所需的所有数据，并将在以后解决现有性能问题后恢复返回该值。" diff --git a/translations/zh-CN/data/release-notes/enterprise-server/3-2/14.yml b/translations/zh-CN/data/release-notes/enterprise-server/3-2/14.yml index 360c7618fc8a..9a81c4956e2c 100644 --- a/translations/zh-CN/data/release-notes/enterprise-server/3-2/14.yml +++ b/translations/zh-CN/data/release-notes/enterprise-server/3-2/14.yml @@ -15,7 +15,7 @@ sections: known_issues: - "在新建的没有任何用户的 {% data variables.product.prodname_ghe_server %} 实例上，攻击者可以创建第一个管理员用户。" - 自定义防火墙规则在升级过程中被删除。 - - "[通过 Web 界面上传](https://github.com/blog/2105-upload-files-to-your-repositories)的 Git LFS 跟踪文件被错误地直接添加到存储库。" + - "[通过 Web 界面上传](https://github.com/blog/2105-upload-files-to-your-repositories) 的 Git LFS 跟踪文件被错误地直接添加到存储库。" - 如果问题包含文件路径长于 255 个字符的同一存储库中 Blob 的永久链接，则问题无法关闭。 - "对 {% data variables.product.prodname_github_connect %} 启用“用户可以搜索 GitHub.com”后，专用和内部存储库中的问题不包括在 {% data variables.product.prodname_dotcom_the_website %} 搜索结果中。" - "{% data variables.product.prodname_registry %} npm 注册表不再在元数据响应中返回时间值。这样可以大幅改善性能。我们继续拥有将时间值作为元数据响应的一部分返回所需的所有数据，并将在以后解决现有性能问题后恢复返回该值。" diff --git a/translations/zh-CN/data/release-notes/enterprise-server/3-2/15.yml b/translations/zh-CN/data/release-notes/enterprise-server/3-2/15.yml index 84169dfb9942..1f07dcf1f739 100644 --- a/translations/zh-CN/data/release-notes/enterprise-server/3-2/15.yml +++ b/translations/zh-CN/data/release-notes/enterprise-server/3-2/15.yml @@ -12,7 +12,7 @@ sections: known_issues: - "在新建的没有任何用户的 {% data variables.product.prodname_ghe_server %} 实例上，攻击者可以创建第一个管理员用户。" - 自定义防火墙规则在升级过程中被删除。 - - "[通过 Web 界面上传](https://github.com/blog/2105-upload-files-to-your-repositories)的 Git LFS 跟踪文件被错误地直接添加到存储库。" + - "[通过 Web 界面上传](https://github.com/blog/2105-upload-files-to-your-repositories) 的 Git LFS 跟踪文件被错误地直接添加到存储库。" - 如果问题包含文件路径长于 255 个字符的同一存储库中 Blob 的永久链接，则问题无法关闭。 - "对 {% data variables.product.prodname_github_connect %} 启用“用户可以搜索 GitHub.com”后，专用和内部存储库中的问题不包括在 {% data variables.product.prodname_dotcom_the_website %} 搜索结果中。" - "{% data variables.product.prodname_registry %} npm 注册表不再在元数据响应中返回时间值。这样可以大幅改善性能。我们继续拥有将时间值作为元数据响应的一部分返回所需的所有数据，并将在以后解决现有性能问题后恢复返回该值。" diff --git a/translations/zh-CN/data/release-notes/enterprise-server/3-2/16.yml b/translations/zh-CN/data/release-notes/enterprise-server/3-2/16.yml index 8112ab2044bf..dacf7c132660 100644 --- a/translations/zh-CN/data/release-notes/enterprise-server/3-2/16.yml +++ b/translations/zh-CN/data/release-notes/enterprise-server/3-2/16.yml @@ -18,7 +18,7 @@ sections: known_issues: - "在新建的没有任何用户的 {% data variables.product.prodname_ghe_server %} 实例上，攻击者可以创建第一个管理员用户。" - 自定义防火墙规则在升级过程中被删除。 - - "[通过 Web 界面上传](https://github.com/blog/2105-upload-files-to-your-repositories)的 Git LFS 跟踪文件被错误地直接添加到存储库。" + - "[通过 Web 界面上传](https://github.com/blog/2105-upload-files-to-your-repositories) 的 Git LFS 跟踪文件被错误地直接添加到存储库。" - 如果问题包含文件路径长于 255 个字符的同一存储库中 blob 的永久链接，则问题无法关闭。 - "对 {% data variables.product.prodname_github_connect %} 启用“用户可以搜索 GitHub.com”后，专用和内部存储库中的问题不包括在 {% data variables.product.prodname_dotcom_the_website %} 搜索结果中。" - "{% data variables.product.prodname_registry %} npm 注册表不再在元数据响应中返回时间值。这样可以大幅改善性能。作为元数据响应的一部分，我们继续拥有返回时间值所需的所有数据，并将在以后解决现有性能问题后恢复返回这个值。" diff --git a/translations/zh-CN/data/release-notes/enterprise-server/3-2/18.yml b/translations/zh-CN/data/release-notes/enterprise-server/3-2/18.yml index f14a33838fdb..146ad3ce5609 100644 --- a/translations/zh-CN/data/release-notes/enterprise-server/3-2/18.yml +++ b/translations/zh-CN/data/release-notes/enterprise-server/3-2/18.yml @@ -8,7 +8,7 @@ sections: known_issues: - "在新建的没有任何用户的 {% data variables.product.prodname_ghe_server %} 实例上，攻击者可以创建第一个管理员用户。" - 自定义防火墙规则在升级过程中被删除。 - - "[通过 Web 界面上传](https://github.com/blog/2105-upload-files-to-your-repositories)的 Git LFS 跟踪文件被错误地直接添加到存储库。" + - "[通过 Web 界面上传](https://github.com/blog/2105-upload-files-to-your-repositories) 的 Git LFS 跟踪文件被错误地直接添加到存储库。" - 如果问题包含文件路径长于 255 个字符的同一存储库中 blob 的永久链接，则问题无法关闭。 - "对 {% data variables.product.prodname_github_connect %} 启用“用户可以搜索 GitHub.com”后，专用和内部存储库中的问题不包括在 {% data variables.product.prodname_dotcom_the_website %} 搜索结果中。" - "{% data variables.product.prodname_registry %} npm 注册表不再在元数据响应中返回时间值。这样可以大幅改善性能。作为元数据响应的一部分，我们继续拥有返回时间值所需的所有数据，并将在以后解决现有性能问题后恢复返回这个值。" diff --git a/translations/zh-CN/data/release-notes/enterprise-server/3-2/2.yml b/translations/zh-CN/data/release-notes/enterprise-server/3-2/2.yml index ca97d641728d..42dbd6c7e3b3 100644 --- a/translations/zh-CN/data/release-notes/enterprise-server/3-2/2.yml +++ b/translations/zh-CN/data/release-notes/enterprise-server/3-2/2.yml @@ -15,7 +15,7 @@ sections: - 在存储库中保存新版本后，`/releases` 页面显示 500 错误。此问题的修复程序预计将在 3.2.3 中发布。 - "在新建的没有任何用户的 {% data variables.product.prodname_ghe_server %} 上，攻击者可以创建第一个管理员用户。" - 自定义防火墙规则在升级过程中被删除。 - - "[通过 Web 界面上传](https://github.com/blog/2105-upload-files-to-your-repositories)的 Git LFS 跟踪文件被错误地直接添加到存储库。" + - "[通过 Web 界面上传](https://github.com/blog/2105-upload-files-to-your-repositories) 的 Git LFS 跟踪文件被错误地直接添加到存储库。" - 如果问题包含同一存储库中 blob 的永久链接并且该 blob 的文件路径长于 255 个字符，则问题无法关闭。 - 在 GitHub Connect 中启用了“用户可以搜索 GitHub.com”时，专用和内部存储库中的问题不包括在 GitHub.com 搜索结果中。 - "{% data variables.product.prodname_registry %} npm 注册表不再在元数据响应中返回时间值。这样做是为了大幅改善性能。我们继续拥有将时间值作为元数据响应的一部分返回所需的所有数据，并将在以后解决现有性能问题后恢复返回该值。" diff --git a/translations/zh-CN/data/release-notes/enterprise-server/3-2/3.yml b/translations/zh-CN/data/release-notes/enterprise-server/3-2/3.yml index cf4f2569ed2c..78b170108acc 100644 --- a/translations/zh-CN/data/release-notes/enterprise-server/3-2/3.yml +++ b/translations/zh-CN/data/release-notes/enterprise-server/3-2/3.yml @@ -23,7 +23,7 @@ sections: known_issues: - "在新建的没有任何用户的 {% data variables.product.prodname_ghe_server %} 上，攻击者可以创建第一个管理员用户。" - 自定义防火墙规则在升级过程中被删除。 - - "[通过 Web 界面上传](https://github.com/blog/2105-upload-files-to-your-repositories)的 Git LFS 跟踪文件被错误地直接添加到存储库。" + - "[通过 Web 界面上传](https://github.com/blog/2105-upload-files-to-your-repositories) 的 Git LFS 跟踪文件被错误地直接添加到存储库。" - 如果问题包含文件路径长于 255 个字符的同一存储库中 blob 的永久链接，则问题无法关闭。 - 对 GitHub Connect 启用“用户可以搜索 GitHub.com”后，专用和内部存储库中的问题不包括在 GitHub.com 搜索结果中。 - "{% data variables.product.prodname_registry %} npm 注册表不再在元数据响应中返回时间值。这样做是为了大幅改善性能。作为元数据响应的一部分，我们继续拥有返回时间值所需的所有数据，并将在我们解决现有性能问题后恢复返回这个值。" diff --git a/translations/zh-CN/data/release-notes/enterprise-server/3-2/4.yml b/translations/zh-CN/data/release-notes/enterprise-server/3-2/4.yml index 72cbad67f65e..fcd8a4d860ce 100644 --- a/translations/zh-CN/data/release-notes/enterprise-server/3-2/4.yml +++ b/translations/zh-CN/data/release-notes/enterprise-server/3-2/4.yml @@ -22,7 +22,7 @@ sections: known_issues: - "在新建的没有任何用户的 {% data variables.product.prodname_ghe_server %} 上，攻击者可以创建第一个管理员用户。" - 自定义防火墙规则在升级过程中被删除。 - - "[通过 Web 界面上传](https://github.com/blog/2105-upload-files-to-your-repositories)的 Git LFS 跟踪文件被错误地直接添加到存储库。" + - "[通过 Web 界面上传](https://github.com/blog/2105-upload-files-to-your-repositories) 的 Git LFS 跟踪文件被错误地直接添加到存储库。" - 如果问题包含同一存储库中 blob 的永久链接并且该 blob de 文件路径长于 255 个字符，则问题无法关闭。 - 在 GitHub Connect 中启用了“用户可以搜索 GitHub.com”时，专用和内部存储库中的问题不包括在 GitHub.com 搜索结果中。 - "{% data variables.product.prodname_registry %} npm 注册表不再在元数据响应中返回时间值。这样做是为了大幅改善性能。我们继续拥有将时间值作为元数据响应的一部分返回所需的所有数据，并将在以后解决现有性能问题后恢复返回该值。" diff --git a/translations/zh-CN/data/release-notes/enterprise-server/3-2/5.yml b/translations/zh-CN/data/release-notes/enterprise-server/3-2/5.yml index e3b6aef0653a..2edbe5ca6644 100644 --- a/translations/zh-CN/data/release-notes/enterprise-server/3-2/5.yml +++ b/translations/zh-CN/data/release-notes/enterprise-server/3-2/5.yml @@ -20,7 +20,7 @@ sections: known_issues: - "在新建的没有任何用户的 {% data variables.product.prodname_ghe_server %} 上，攻击者可以创建第一个管理员用户。" - 自定义防火墙规则在升级过程中被删除。 - - "[通过 Web 界面上传](https://github.com/blog/2105-upload-files-to-your-repositories)的 Git LFS 跟踪文件被错误地直接添加到存储库。" + - "[通过 Web 界面上传](https://github.com/blog/2105-upload-files-to-your-repositories) 的 Git LFS 跟踪文件被错误地直接添加到存储库。" - 如果问题包含同一存储库中 blob 的永久链接并且该 blob 的文件路径长于 255 个字符，则问题无法关闭。 - 在 GitHub Connect 中启用了“用户可以搜索 GitHub.com”时，专用和内部存储库中的问题不包括在 GitHub.com 搜索结果中。 - "{% data variables.product.prodname_registry %} npm 注册表不再在元数据响应中返回时间值。这样做是为了大幅改善性能。我们继续拥有将时间值作为元数据响应的一部分返回所需的所有数据，并将在以后解决现有性能问题后恢复返回该值。" diff --git a/translations/zh-CN/data/release-notes/enterprise-server/3-2/6.yml b/translations/zh-CN/data/release-notes/enterprise-server/3-2/6.yml index 239c0e710b2a..b197bc359063 100644 --- a/translations/zh-CN/data/release-notes/enterprise-server/3-2/6.yml +++ b/translations/zh-CN/data/release-notes/enterprise-server/3-2/6.yml @@ -1,12 +1,12 @@ date: '2021-12-13' sections: security_fixes: - - '{% octicon "alert" aria-label="The alert icon" %} 严重：****在 Log4j 库中发现远程代码执行漏洞，该漏洞会影响 3.3.1 之前的所有 {% data variables.product.prodname_ghe_server %} 版本，漏洞编号为 [CVE-2021-44228](https://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2021-44228)。Log4j 库用于在 {% data variables.product.prodname_ghe_server %} 实例上运行的开源服务。已在 {% data variables.product.prodname_ghe_server %} 3.0.22、3.1.14、3.2.6 和 3.3.1 中修复该漏洞。 有关详细信息，请参阅 GitHub 博客[文章](https://github.blog/2021-12-13-githubs-response-to-log4j-vulnerability-cve-2021-44228/)。' + - '{% octicon "alert" aria-label="The alert icon" %} 严重：****在 Log4j 库中发现远程代码执行漏洞，该漏洞会影响 3.3.1 之前的所有 {% data variables.product.prodname_ghe_server %} 版本，漏洞编号为 [CVE-2021-44228](https://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2021-44228)。Log4j 库用于在 {% data variables.product.prodname_ghe_server %} 实例上运行的开源服务。已在 {% data variables.product.prodname_ghe_server %} 3.0.22、3.1.14、3.2.6 和 3.3.1 中修复该漏洞。有关详细信息，请参阅 GitHub 博客 [文章](https://github.blog/2021-12-13-githubs-response-to-log4j-vulnerability-cve-2021-44228/)。' - '2021 年 12 月 17 日更新****：此版本中的修复也能缓解在该版本之后发布的 [CVE-2021-45046](https://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2021-45046)。无需再升级 {% data variables.product.prodname_ghe_server %}，即可缓解 CVE-2021-44228 和 CVE-2021-45046。' known_issues: - "在新建的没有任何用户的 {% data variables.product.prodname_ghe_server %} 上，攻击者可以创建第一个管理员用户。" - 自定义防火墙规则在升级过程中被删除。 - - "[通过 Web 界面上传](https://github.com/blog/2105-upload-files-to-your-repositories)的 Git LFS 跟踪文件被错误地直接添加到存储库。" + - "[通过 Web 界面上传](https://github.com/blog/2105-upload-files-to-your-repositories) 的 Git LFS 跟踪文件被错误地直接添加到存储库。" - 如果问题包含文件路径长于 255 个字符的同一存储库中 Blob 的永久链接，则问题无法关闭。 - 在 GitHub Connect 中启用了“用户可以搜索 GitHub.com”时，专用和内部存储库中的问题不包括在 GitHub.com 搜索结果中。 - "{% data variables.product.prodname_registry %} npm 注册表不再在元数据响应中返回时间值。这样可以大幅改善性能。我们继续拥有将时间值作为元数据响应的一部分返回所需的所有数据，并将在以后解决现有性能问题后恢复返回该值。" diff --git a/translations/zh-CN/data/release-notes/enterprise-server/3-2/7.yml b/translations/zh-CN/data/release-notes/enterprise-server/3-2/7.yml index fdb9db199db5..e4156f97251b 100644 --- a/translations/zh-CN/data/release-notes/enterprise-server/3-2/7.yml +++ b/translations/zh-CN/data/release-notes/enterprise-server/3-2/7.yml @@ -15,7 +15,7 @@ sections: known_issues: - "在新建的没有任何用户的 {% data variables.product.prodname_ghe_server %} 上，攻击者可以创建第一个管理员用户。" - 自定义防火墙规则在升级过程中被删除。 - - "[通过 Web 界面上传](https://github.com/blog/2105-upload-files-to-your-repositories)的 Git LFS 跟踪文件被错误地直接添加到存储库。" + - "[通过 Web 界面上传](https://github.com/blog/2105-upload-files-to-your-repositories) 的 Git LFS 跟踪文件被错误地直接添加到存储库。" - 如果问题包含同一存储库中 blob 的永久链接并且该 blob 的文件路径长于 255 个字符，则问题无法关闭。 - 在 GitHub Connect 中启用了“用户可以搜索 GitHub.com”时，专用和内部存储库中的问题不包括在 GitHub.com 搜索结果中。 - "{% data variables.product.prodname_registry %} npm 注册表不再在元数据响应中返回时间值。这样做是为了大幅改善性能。我们继续拥有将时间值作为元数据响应的一部分返回所需的所有数据，并将在以后解决现有性能问题后恢复返回该值。" diff --git a/translations/zh-CN/data/release-notes/enterprise-server/3-2/8.yml b/translations/zh-CN/data/release-notes/enterprise-server/3-2/8.yml index 5f00f51c99d4..416d30aa0c07 100644 --- a/translations/zh-CN/data/release-notes/enterprise-server/3-2/8.yml +++ b/translations/zh-CN/data/release-notes/enterprise-server/3-2/8.yml @@ -18,7 +18,7 @@ sections: known_issues: - "在新建的没有任何用户的 {% data variables.product.prodname_ghe_server %} 上，攻击者可以创建第一个管理员用户。" - 自定义防火墙规则在升级过程中被删除。 - - "[通过 Web 界面上传](https://github.com/blog/2105-upload-files-to-your-repositories)的 Git LFS 跟踪文件被错误地直接添加到存储库。" + - "[通过 Web 界面上传](https://github.com/blog/2105-upload-files-to-your-repositories) 的 Git LFS 跟踪文件被错误地直接添加到存储库。" - 如果问题包含同一存储库中文件路径长于 255 个字符的 blob 的永久链接，则无法关闭。 - 在 GitHub Connect 中启用了“用户可以搜索 GitHub.com”时，专用和内部存储库中的问题不包括在 GitHub.com 搜索结果中。 - "{% data variables.product.prodname_registry %} npm 注册表不再在元数据响应中返回时间值。这样可以大幅改善性能。我们继续拥有将时间值作为元数据响应的一部分返回所需的所有数据，并将在以后解决现有性能问题后恢复返回该值。" diff --git a/translations/zh-CN/data/release-notes/enterprise-server/3-2/9.yml b/translations/zh-CN/data/release-notes/enterprise-server/3-2/9.yml index 3230434c37de..8a0f8420da22 100644 --- a/translations/zh-CN/data/release-notes/enterprise-server/3-2/9.yml +++ b/translations/zh-CN/data/release-notes/enterprise-server/3-2/9.yml @@ -12,7 +12,7 @@ sections: known_issues: - "在新建的没有任何用户的 {% data variables.product.prodname_ghe_server %} 实例上，攻击者可以创建第一个管理员用户。" - 自定义防火墙规则在升级过程中被删除。 - - "[通过 Web 界面上传](https://github.com/blog/2105-upload-files-to-your-repositories)的 Git LFS 跟踪文件被错误地直接添加到存储库。" + - "[通过 Web 界面上传](https://github.com/blog/2105-upload-files-to-your-repositories) 的 Git LFS 跟踪文件被错误地直接添加到存储库。" - 如果问题包含同一存储库中文件路径长于 255 个字符的 blob 的永久链接，则无法关闭。 - 在 GitHub Connect 中启用了“用户可以搜索 GitHub.com”时，专用和内部存储库中的问题不包括在 GitHub.com 搜索结果中。 - "{% data variables.product.prodname_registry %} npm 注册表不再在元数据响应中返回时间值。这样可以大幅改善性能。我们继续拥有将时间值作为元数据响应的一部分返回所需的所有数据，并将在以后解决现有性能问题后恢复返回该值。" diff --git a/translations/zh-CN/data/release-notes/enterprise-server/3-3/0-rc1.yml b/translations/zh-CN/data/release-notes/enterprise-server/3-3/0-rc1.yml index eaa5046942a7..3f8f09148aaf 100644 --- a/translations/zh-CN/data/release-notes/enterprise-server/3-3/0-rc1.yml +++ b/translations/zh-CN/data/release-notes/enterprise-server/3-3/0-rc1.yml @@ -143,157 +143,4 @@ sections: For more information, see the [{% data variables.product.prodname_dotcom %} changelog](https://github.blog/changelog/2021-09-29-new-code-review-assignment-settings-and-team-filtering-improvements/). - You can now filter pull request searches to only include pull requests you are directly requested to review. # https://github.com/github/releases/issues/1683 - - Filtered files in pull requests are now completely hidden from view, and are no longer shown as collapsed in the "Files Changed" tab. The "File Filter" menu has also been simplified. For more information, see "[Filtering files in a pull request](/github/collaborating-with-pull-requests/reviewing-changes-in-pull-requests/filtering-files-in-a-pull-request)." - - - heading: 'GitHub Actions changes' - notes: - # https://github.com/github/releases/issues/1593 - - You can now create "composite actions" which combine multiple workflow steps into one action, and includes the ability to reference other actions. This makes it easier to reduce duplication in workflows. Previously, an action could only use scripts in its YAML definition. For more information, see "[Creating a composite action](/actions/creating-actions/creating-a-composite-action)." - - # https://github.com/github/releases/issues/1694 - - Managing self-hosted runners at the enterprise level no longer requires using personal access tokens with the `admin:enterprise` scope. You can instead use the new `manage_runners:enterprise` scope to restrict the permissions on your tokens. Tokens with this scope can authenticate to [many REST API endpoints](/rest/reference/enterprise-admin#list-self-hosted-runner-groups-for-an-enterprise) to manage your enterprise's self-hosted runners. - - # https://github.com/github/releases/issues/1157 - - | - The audit log now includes additional events for {% data variables.product.prodname_actions %}. Audit log entries are now recorded for the following events: - - * A self-hosted runner is registered or removed. - * A self-hosted runner is added to a runner group, or removed from a runner group. - * A runner group is created or removed. - * A workflow run is created or completed. - * A workflow job is prepared. Importantly, this log includes the list of secrets that were provided to the runner. - - For more information, see "[Security hardening for {% data variables.product.prodname_actions %}](/actions/security-guides/security-hardening-for-github-actions#auditing-github-actions-events)." - - # https://github.com/github/releases/issues/1588 - - Performance improvements have been made to {% data variables.product.prodname_actions %}, which may result in higher maximum job concurrency. - - - heading: 'GitHub Packages changes' - notes: - # https://github.com/github/docs-content/issues/5554 - - When a repository is deleted, any associated package files are now immediately deleted from your {% data variables.product.prodname_registry %} external storage. - - - heading: 'Dependabot and Dependency graph changes' - notes: - # https://github.com/github/releases/issues/1141 - - Dependency review is out of beta and is now generally available for {% data variables.product.prodname_GH_advanced_security %} customers. Dependency review provides an easy-to-understand view of dependency changes and their security impact in the "Files changed" tab of pull requests. It informs you of which dependencies were added, removed, or updated, along with vulnerability information. For more information, see "[Reviewing dependency changes in a pull request](/github/collaborating-with-pull-requests/reviewing-changes-in-pull-requests/reviewing-dependency-changes-in-a-pull-request)." - - # https://github.com/github/releases/issues/1630 - - '{% data variables.product.prodname_dependabot %} is now available as a private beta, offering both version updates and security updates for several popular ecosystems. {% data variables.product.prodname_dependabot %} on {% data variables.product.prodname_ghe_server %} requires {% data variables.product.prodname_actions %} and a pool of self-hosted runners configured for {% data variables.product.prodname_dependabot %} use. {% data variables.product.prodname_dependabot %} on {% data variables.product.prodname_ghe_server %} also requires {% data variables.product.prodname_github_connect %} to be enabled. To learn more and sign up for the beta, contact the GitHub Sales team.' - - - heading: 'Code scanning and secret scanning changes' - notes: - # https://github.com/github/releases/issues/1724 - - The depth of {% data variables.product.prodname_codeql %}'s analysis has been improved by adding support for more [libraries and frameworks](https://codeql.github.com/docs/codeql-overview/supported-languages-and-frameworks/) and increasing the coverage of our existing library and framework models. [JavaScript](https://github.com/github/codeql/tree/main/javascript) analysis now supports most common templating languages, and [Java](https://github.com/github/codeql/tree/main/java) now covers more than three times the endpoints of previous {% data variables.product.prodname_codeql %} versions. As a result, {% data variables.product.prodname_codeql %} can now detect even more potential sources of untrusted user data, steps through which that data flows, and potentially dangerous sinks where the data could end up. This results in an overall improvement of the quality of {% data variables.product.prodname_code_scanning %} alerts. - - # https://github.com/github/releases/issues/1639 - - '{% data variables.product.prodname_codeql %} now supports scanning standard language features in Java 16, such as records and pattern matching. {% data variables.product.prodname_codeql %} is able to analyze code written in Java version 7 through 16. For more information about supported languages and frameworks, see the [{% data variables.product.prodname_codeql %} documentation](https://codeql.github.com/docs/codeql-overview/supported-languages-and-frameworks/#id5).' - - # https://github.com/github/releases/issues/1655 - - | - Improvements have been made to the {% data variables.product.prodname_code_scanning %} `on:push` trigger when code is pushed to a pull request. If an `on:push` scan returns results that are associated with a pull request, {% data variables.product.prodname_code_scanning %} will now show these alerts on the pull request. - - Some other CI/CD systems can be exclusively configured to trigger a pipeline when code is pushed to a branch, or even exclusively for every commit. Whenever such an analysis pipeline is triggered and results are uploaded to the SARIF API, {% data variables.product.prodname_code_scanning %} will also try to match the analysis results to an open pull request. If an open pull request is found, the results will be published as described above. For more information, see the [{% data variables.product.prodname_dotcom %} changelog](https://github.blog/changelog/2021-09-27-showing-code-scanning-alerts-on-pull-requests/). - - # https://github.com/github/releases/issues/1546 - - You can now use the new pull request filter on the {% data variables.product.prodname_code_scanning %} alerts page to find all the {% data variables.product.prodname_code_scanning %} alerts associated with a pull request. A new "View all branch alerts" link on the pull request "Checks" tab allows you to directly view {% data variables.product.prodname_code_scanning %} alerts with the specific pull request filter already applied. For more information, see the [{% data variables.product.prodname_dotcom %} changelog](https://github.blog/changelog/2021-08-23-pull-request-filter-for-code-scanning-alerts/). - - # https://github.com/github/releases/issues/1562 - - User defined patterns for {% data variables.product.prodname_secret_scanning %} is out of beta and is now generally available for {% data variables.product.prodname_GH_advanced_security %} customers. Also new in this release is the ability to edit custom patterns defined at the repository, organization, and enterprise levels. After editing and saving a pattern, {% data variables.product.prodname_secret_scanning %} searches for matches both in a repository's entire Git history and in any new commits. Editing a pattern will close alerts previously associated with the pattern if they no longer match the updated version. Other improvements, such as dry-runs, are planned in future releases. For more information, see "[Defining custom patterns for secret scanning](/code-security/secret-scanning/defining-custom-patterns-for-secret-scanning)." - - - heading: API and webhook changes - notes: - # https://github.com/github/releases/issues/1744 - - Most REST API previews have graduated and are now an official part of the API. Preview headers are no longer required for most REST API endpoints, but will still function as expected if you specify a graduated preview in the `Accept` header of a request. For previews that still require specifying the preview in the `Accept` header of a request, see "[API previews](/rest/overview/api-previews)." - - # https://github.com/github/releases/issues/1513 - - You can now use the REST API to configure custom autolinks to external resources. The REST API now provides beta `GET`/`POST`/`DELETE` endpoints which you can use to view, add, or delete custom autolinks associated with a repository. For more information, see "[Autolinks](/rest/reference/repos#autolinks)." - - # https://github.com/github/releases/issues/1578 - - You can now use the REST API to sync a forked repository with its upstream repository. For more information, see "[Branches](/rest/reference/branches#sync-a-fork-branch-with-the-upstream-repository)" in the REST API documentation. - - # https://github.com/github/releases/issues/1527 - - Enterprise administrators on GitHub Enterprise Server can now use the REST API to enable or disable Git LFS for a repository. For more information, see "[Repositories](/rest/reference/repos#git-lfs)." - - # https://github.com/github/releases/issues/1476 - - You can now use the REST API to query the audit log for an enterprise. While audit log forwarding provides the ability to retain and analyze data with your own toolkit and determine patterns over time, the new endpoint can help you perform limited analysis on recent events. For more information, see "[{% data variables.product.prodname_enterprise %} administration](/rest/reference/enterprise-admin#get-the-audit-log-for-an-enterprise)" in the REST API documentation. - - # https://github.com/github/releases/issues/1485 - - GitHub App user-to-server API requests can now read public resources using the REST API. This includes, for example, the ability to list a public repository's issues and pull requests, and to access a public repository's comments and content. - - # https://github.com/github/releases/issues/1734 - - When creating or updating a repository, you can now configure whether forking is allowed using the REST and GraphQL APIs. Previously, APIs for creating and updating repositories didn't include the fields `allow_forking` (REST) or `forkingAllowed` (GraphQL). For more information, see "[Repositories](/rest/reference/repos)" in the REST API documentation and "[Repositories](/graphql/reference/objects#repository)" in the GraphQL API documentation. - - # https://github.com/github/releases/issues/1637 - - | - A new GraphQL mutation [`createCommitOnBranch`](/graphql/reference/mutations#createcommitonbranch) makes it easier to add, update, and delete files in a branch of a repository. Compared to the REST API, you do not need to manually create blobs and trees before creating the commit. This allows you to add, update, or delete multiple files in a single API call. - - Commits authored using the new API are automatically GPG signed and are [marked as verified](/github/authenticating-to-github/managing-commit-signature-verification/about-commit-signature-verification) in the {% data variables.product.prodname_ghe_server %} UI. GitHub Apps can use the mutation to author commits directly or [on behalf of users](/developers/apps/building-github-apps/identifying-and-authorizing-users-for-github-apps#user-to-server-requests). - - # https://github.com/github/releases/issues/1665 - - When a new tag is created, the [push](/developers/webhooks-and-events/webhooks/webhook-events-and-payloads#push) webhook payload now always includes a `head_commit` object that contains the data of the commit that the new tag points to. As a result, the `head_commit` object will always contain the commit data of the payload's `after` commit. - - - heading: 'Performance Changes' - notes: - # https://github.com/github/releases/issues/1823 - - Page loads and jobs are now significantly faster for repositories with many Git refs. - - # No security/bug fixes for the RC release - # security_fixes: - # - PLACEHOLDER - - # bugs: - # - PLACEHOLDER - - 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. - - deprecations: - - heading: Deprecation of GitHub Enterprise Server 2.22 - notes: - - '**{% data variables.product.prodname_ghe_server %} 2.22 was discontinued on September 23, 2021**. This means that no patch releases will be made, even for critical security issues, after this date. For better performance, improved security, and new features, [upgrade to the newest version of {% data variables.product.prodname_ghe_server %}](/enterprise-server@3.3/admin/enterprise-management/upgrading-github-enterprise-server) as soon as possible.' - - heading: Deprecation of GitHub Enterprise Server 3.0 - notes: - - '**{% data variables.product.prodname_ghe_server %} 3.0 will be discontinued on February 16, 2022**. This means that no patch releases will be made, even for critical security issues, after this date. For better performance, improved security, and new features, [upgrade to the newest version of {% data variables.product.prodname_ghe_server %}](/enterprise-server@3.3/admin/enterprise-management/upgrading-github-enterprise-server) as soon as possible.' - - - heading: Deprecation of XenServer Hypervisor support - notes: - # https://github.com/github/docs-content/issues/4439 - - Starting with {% data variables.product.prodname_ghe_server %} 3.3, {% data variables.product.prodname_ghe_server %} on XenServer is deprecated and is no longer supported. Please contact [GitHub Support](https://support.github.com) with questions or concerns. - - - heading: Deprecation of OAuth Application API endpoints and API authentication using query parameters - notes: - # https://github.com/github/releases/issues/1316 - - | - To prevent accidental logging or exposure of `access_tokens`, we discourage the use of OAuth Application API endpoints and the use of API authentication using query parameters. View the following posts to see the proposed replacements: - - * [Replacement OAuth Application API endpoints](https://developer.github.com/changes/2020-02-14-deprecating-oauth-app-endpoint/#changes-to-make) - * [Replacement authentication using headers instead of query param](https://developer.github.com/changes/2020-02-10-deprecating-auth-through-query-param/#changes-to-make) - - These endpoints and authentication route are planned to be removed from {% data variables.product.prodname_ghe_server %} in {% data variables.product.prodname_ghe_server %} 3.4. - - - heading: Deprecation of the CodeQL runner - notes: - # https://github.com/github/releases/issues/1632 - - The {% data variables.product.prodname_codeql %} runner is being deprecated. {% data variables.product.prodname_ghe_server %} 3.3 will be the final release series that supports the {% data variables.product.prodname_codeql %} runner. Starting with {% data variables.product.prodname_ghe_server %} 3.4, the {% data variables.product.prodname_codeql %} runner will be removed and no longer supported. The {% data variables.product.prodname_codeql %} CLI version 2.6.2 or greater is a feature-complete replacement for the {% data variables.product.prodname_codeql %} runner. For more information, see the [{% data variables.product.prodname_dotcom %} changelog](https://github.blog/changelog/2021-09-21-codeql-runner-deprecation/). - - - heading: Deprecation of custom bit-cache extensions - notes: - # https://github.com/github/releases/issues/1415 - - | - Starting in {% data variables.product.prodname_ghe_server %} 3.1, support for {% data variables.product.company_short %}'s proprietary bit-cache extensions began to be phased out. These extensions are now deprecated in {% data variables.product.prodname_ghe_server %} 3.3. - - Any repositories that were already present and active on {% data variables.product.product_location %} running version 3.1 or 3.2 will have been automatically updated. - - Repositories which were not present and active before upgrading to {% data variables.product.prodname_ghe_server %} 3.3 may not perform optimally until a repository maintenance task is run and has successfully completed. - - To start a repository maintenance task manually, browse to `https:///stafftools/repositories///network` for each affected repository and click the **Schedule** button. - - backups: - - '{% data variables.product.prodname_ghe_server %} 3.3 requires at least [GitHub Enterprise Backup Utilities 3.3.0](https://github.com/github/backup-utils) for [Backups and Disaster Recovery](/admin/configuration/configuring-your-enterprise/configuring-backups-on-your-appliance).' + - Filtered files in pull requests are now completely hidden from view, and are no longer shown as collapsed in the "Files Changed" tab. The "File Filter" menu has also been simplified. For more information, see "[Filtering files in a pull request](/github/collaborating-with-pull-requests/reviewing-changes-in-pull-requests/filterin \ No newline at end of file diff --git a/translations/zh-CN/data/release-notes/enterprise-server/3-3/0.yml b/translations/zh-CN/data/release-notes/enterprise-server/3-3/0.yml index f321bb7caa44..b73c706bade9 100644 --- a/translations/zh-CN/data/release-notes/enterprise-server/3-3/0.yml +++ b/translations/zh-CN/data/release-notes/enterprise-server/3-3/0.yml @@ -135,171 +135,4 @@ sections: The timeline and reviewers sidebar on the pull request page now indicate if a review request was automatically assigned to one or more team members. For more information, see the [{% data variables.product.prodname_dotcom %} changelog](https://github.blog/changelog/2021-09-29-new-code-review-assignment-settings-and-team-filtering-improvements/). - - You can now filter pull request searches to only include pull requests you are directly requested to review. - # https://github.com/github/releases/issues/1683 - - Filtered files in pull requests are now completely hidden from view, and are no longer shown as collapsed in the "Files Changed" tab. The "File Filter" menu has also been simplified. For more information, see "[Filtering files in a pull request](/github/collaborating-with-pull-requests/reviewing-changes-in-pull-requests/filtering-files-in-a-pull-request)." - - - heading: 'GitHub Actions changes' - notes: - # https://github.com/github/releases/issues/1593 - - You can now create "composite actions" which combine multiple workflow steps into one action, and includes the ability to reference other actions. This makes it easier to reduce duplication in workflows. Previously, an action could only use scripts in its YAML definition. For more information, see "[Creating a composite action](/actions/creating-actions/creating-a-composite-action)." - - # https://github.com/github/releases/issues/1694 - - Managing self-hosted runners at the enterprise level no longer requires using personal access tokens with the `admin:enterprise` scope. You can instead use the new `manage_runners:enterprise` scope to restrict the permissions on your tokens. Tokens with this scope can authenticate to [many REST API endpoints](/rest/reference/enterprise-admin#list-self-hosted-runner-groups-for-an-enterprise) to manage your enterprise's self-hosted runners. - - # https://github.com/github/releases/issues/1157 - - | - The audit log now includes additional events for {% data variables.product.prodname_actions %}. Audit log entries are now recorded for the following events: - - * A self-hosted runner is registered or removed. - * A self-hosted runner is added to a runner group, or removed from a runner group. - * A runner group is created or removed. - * A workflow run is created or completed. - * A workflow job is prepared. Importantly, this log includes the list of secrets that were provided to the runner. - - For more information, see "[Security hardening for {% data variables.product.prodname_actions %}](/actions/security-guides/security-hardening-for-github-actions#auditing-github-actions-events)." - - # https://github.com/github/releases/issues/1588 - - '{% data variables.product.prodname_ghe_server %} 3.3 contains performance improvements for job concurrency with {% data variables.product.prodname_actions %}. For more information about the new performance targets for a range of CPU and memory configurations, see "[Getting started with {% data variables.product.prodname_actions %} for {% data variables.product.prodname_ghe_server %}](/admin/github-actions/enabling-github-actions-for-github-enterprise-server/getting-started-with-github-actions-for-github-enterprise-server#review-hardware-considerations)."' - - # https://github.com/github/releases/issues/1556 - - To mitigate insider man in the middle attacks when using actions resolved through {% data variables.product.prodname_github_connect %} to {% data variables.product.prodname_dotcom_the_website %} from {% data variables.product.prodname_ghe_server %}, the actions namespace (`owner/name`) is retired on use. Retiring the namespace prevents that namespace from being created on your {% data variables.product.prodname_ghe_server %} instance, and ensures all workflows referencing the action will download it from {% data variables.product.prodname_dotcom_the_website %}. - - - heading: 'GitHub Packages changes' - notes: - # https://github.com/github/docs-content/issues/5554 - - When a repository is deleted, any associated package files are now immediately deleted from your {% data variables.product.prodname_registry %} external storage. - - - heading: 'Dependabot and Dependency graph changes' - notes: - # https://github.com/github/releases/issues/1141 - - Dependency review is out of beta and is now generally available for {% data variables.product.prodname_GH_advanced_security %} customers. Dependency review provides an easy-to-understand view of dependency changes and their security impact in the "Files changed" tab of pull requests. It informs you of which dependencies were added, removed, or updated, along with vulnerability information. For more information, see "[Reviewing dependency changes in a pull request](/github/collaborating-with-pull-requests/reviewing-changes-in-pull-requests/reviewing-dependency-changes-in-a-pull-request)." - - # https://github.com/github/releases/issues/1630 - - '{% data variables.product.prodname_dependabot %} is now available as a private beta, offering both version updates and security updates for several popular ecosystems. {% data variables.product.prodname_dependabot %} on {% data variables.product.prodname_ghe_server %} requires {% data variables.product.prodname_actions %} and a pool of self-hosted runners configured for {% data variables.product.prodname_dependabot %} use. {% data variables.product.prodname_dependabot %} on {% data variables.product.prodname_ghe_server %} also requires {% data variables.product.prodname_github_connect %} to be enabled. To learn more and sign up for the beta, contact the GitHub Sales team.' - - - heading: 'Code scanning and secret scanning changes' - notes: - # https://github.com/github/releases/issues/1724 - - The depth of {% data variables.product.prodname_codeql %}'s analysis has been improved by adding support for more [libraries and frameworks](https://codeql.github.com/docs/codeql-overview/supported-languages-and-frameworks/) and increasing the coverage of our existing library and framework models. [JavaScript](https://github.com/github/codeql/tree/main/javascript) analysis now supports most common templating languages, and [Java](https://github.com/github/codeql/tree/main/java) now covers more than three times the endpoints of previous {% data variables.product.prodname_codeql %} versions. As a result, {% data variables.product.prodname_codeql %} can now detect even more potential sources of untrusted user data, steps through which that data flows, and potentially dangerous sinks where the data could end up. This results in an overall improvement of the quality of {% data variables.product.prodname_code_scanning %} alerts. - - # https://github.com/github/releases/issues/1639 - - '{% data variables.product.prodname_codeql %} now supports scanning standard language features in Java 16, such as records and pattern matching. {% data variables.product.prodname_codeql %} is able to analyze code written in Java version 7 through 16. For more information about supported languages and frameworks, see the [{% data variables.product.prodname_codeql %} documentation](https://codeql.github.com/docs/codeql-overview/supported-languages-and-frameworks/#id5).' - - # https://github.com/github/releases/issues/1655 - - | - Improvements have been made to the {% data variables.product.prodname_code_scanning %} `on:push` trigger when code is pushed to a pull request. If an `on:push` scan returns results that are associated with a pull request, {% data variables.product.prodname_code_scanning %} will now show these alerts on the pull request. - - Some other CI/CD systems can be exclusively configured to trigger a pipeline when code is pushed to a branch, or even exclusively for every commit. Whenever such an analysis pipeline is triggered and results are uploaded to the SARIF API, {% data variables.product.prodname_code_scanning %} will also try to match the analysis results to an open pull request. If an open pull request is found, the results will be published as described above. For more information, see the [{% data variables.product.prodname_dotcom %} changelog](https://github.blog/changelog/2021-09-27-showing-code-scanning-alerts-on-pull-requests/). - - # https://github.com/github/releases/issues/1546 - - You can now use the new pull request filter on the {% data variables.product.prodname_code_scanning %} alerts page to find all the {% data variables.product.prodname_code_scanning %} alerts associated with a pull request. A new "View all branch alerts" link on the pull request "Checks" tab allows you to directly view {% data variables.product.prodname_code_scanning %} alerts with the specific pull request filter already applied. For more information, see the [{% data variables.product.prodname_dotcom %} changelog](https://github.blog/changelog/2021-08-23-pull-request-filter-for-code-scanning-alerts/). - - # https://github.com/github/releases/issues/1562 - - User defined patterns for {% data variables.product.prodname_secret_scanning %} is out of beta and is now generally available for {% data variables.product.prodname_GH_advanced_security %} customers. Also new in this release is the ability to edit custom patterns defined at the repository, organization, and enterprise levels. After editing and saving a pattern, {% data variables.product.prodname_secret_scanning %} searches for matches both in a repository's entire Git history and in any new commits. Editing a pattern will close alerts previously associated with the pattern if they no longer match the updated version. Other improvements, such as dry-runs, are planned in future releases. For more information, see "[Defining custom patterns for secret scanning](/code-security/secret-scanning/defining-custom-patterns-for-secret-scanning)." - - - heading: API and webhook changes - notes: - # https://github.com/github/releases/issues/1744 - - Most REST API previews have graduated and are now an official part of the API. Preview headers are no longer required for most REST API endpoints, but will still function as expected if you specify a graduated preview in the `Accept` header of a request. For previews that still require specifying the preview in the `Accept` header of a request, see "[API previews](/rest/overview/api-previews)." - - # https://github.com/github/releases/issues/1513 - - You can now use the REST API to configure custom autolinks to external resources. The REST API now provides beta `GET`/`POST`/`DELETE` endpoints which you can use to view, add, or delete custom autolinks associated with a repository. For more information, see "[Autolinks](/rest/reference/repos#autolinks)." - - # https://github.com/github/releases/issues/1578 - - You can now use the REST API to sync a forked repository with its upstream repository. For more information, see "[Branches](/rest/reference/branches#sync-a-fork-branch-with-the-upstream-repository)" in the REST API documentation. - - # https://github.com/github/releases/issues/1527 - - Enterprise administrators on GitHub Enterprise Server can now use the REST API to enable or disable Git LFS for a repository. For more information, see "[Repositories](/rest/reference/repos#git-lfs)." - - # https://github.com/github/releases/issues/1476 - - You can now use the REST API to query the audit log for an enterprise. While audit log forwarding provides the ability to retain and analyze data with your own toolkit and determine patterns over time, the new endpoint can help you perform limited analysis on recent events. For more information, see "[{% data variables.product.prodname_enterprise %} administration](/rest/reference/enterprise-admin#get-the-audit-log-for-an-enterprise)" in the REST API documentation. - - # https://github.com/github/releases/issues/1485 - - GitHub App user-to-server API requests can now read public resources using the REST API. This includes, for example, the ability to list a public repository's issues and pull requests, and to access a public repository's comments and content. - - # https://github.com/github/releases/issues/1734 - - When creating or updating a repository, you can now configure whether forking is allowed using the REST and GraphQL APIs. Previously, APIs for creating and updating repositories didn't include the fields `allow_forking` (REST) or `forkingAllowed` (GraphQL). For more information, see "[Repositories](/rest/reference/repos)" in the REST API documentation and "[Repositories](/graphql/reference/objects#repository)" in the GraphQL API documentation. - - # https://github.com/github/releases/issues/1637 - - | - A new GraphQL mutation [`createCommitOnBranch`](/graphql/reference/mutations#createcommitonbranch) makes it easier to add, update, and delete files in a branch of a repository. Compared to the REST API, you do not need to manually create blobs and trees before creating the commit. This allows you to add, update, or delete multiple files in a single API call. - - Commits authored using the new API are automatically GPG signed and are [marked as verified](/github/authenticating-to-github/managing-commit-signature-verification/about-commit-signature-verification) in the {% data variables.product.prodname_ghe_server %} UI. GitHub Apps can use the mutation to author commits directly or [on behalf of users](/developers/apps/building-github-apps/identifying-and-authorizing-users-for-github-apps#user-to-server-requests). - - # https://github.com/github/releases/issues/1665 - - When a new tag is created, the [push](/developers/webhooks-and-events/webhooks/webhook-events-and-payloads#push) webhook payload now always includes a `head_commit` object that contains the data of the commit that the new tag points to. As a result, the `head_commit` object will always contain the commit data of the payload's `after` commit. - - - heading: 'Performance Changes' - notes: - # https://github.com/github/releases/issues/1823 - - Page loads and jobs are now significantly faster for repositories with many Git refs. - - # No security/bug fixes for the RC release - # security_fixes: - # - PLACEHOLDER - - # bugs: - # - PLACEHOLDER - - 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 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 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: - - '**{% data variables.product.prodname_ghe_server %} 2.22 was discontinued on September 23, 2021**. This means that no patch releases will be made, even for critical security issues, after this date. For better performance, improved security, and new features, [upgrade to the newest version of {% data variables.product.prodname_ghe_server %}](/enterprise-server@3.3/admin/enterprise-management/upgrading-github-enterprise-server) as soon as possible.' - - heading: Deprecation of GitHub Enterprise Server 3.0 - notes: - - '**{% data variables.product.prodname_ghe_server %} 3.0 will be discontinued on February 16, 2022**. This means that no patch releases will be made, even for critical security issues, after this date. For better performance, improved security, and new features, [upgrade to the newest version of {% data variables.product.prodname_ghe_server %}](/enterprise-server@3.3/admin/enterprise-management/upgrading-github-enterprise-server) as soon as possible.' - - - heading: Deprecation of XenServer Hypervisor support - notes: - # https://github.com/github/docs-content/issues/4439 - - Starting with {% data variables.product.prodname_ghe_server %} 3.3, {% data variables.product.prodname_ghe_server %} on XenServer is deprecated and is no longer supported. Please contact [GitHub Support](https://support.github.com) with questions or concerns. - - - heading: Deprecation of OAuth Application API endpoints and API authentication using query parameters - notes: - # https://github.com/github/releases/issues/1316 - - | - To prevent accidental logging or exposure of `access_tokens`, we discourage the use of OAuth Application API endpoints and the use of API authentication using query parameters. View the following posts to see the proposed replacements: - - * [Replacement OAuth Application API endpoints](https://developer.github.com/changes/2020-02-14-deprecating-oauth-app-endpoint/#changes-to-make) - * [Replacement authentication using headers instead of query param](https://developer.github.com/changes/2020-02-10-deprecating-auth-through-query-param/#changes-to-make) - - These endpoints and authentication route are planned to be removed from {% data variables.product.prodname_ghe_server %} in {% data variables.product.prodname_ghe_server %} 3.4. - - - heading: Deprecation of the CodeQL runner - notes: - # https://github.com/github/releases/issues/1632 - - The {% data variables.product.prodname_codeql %} runner is being deprecated. {% data variables.product.prodname_ghe_server %} 3.3 will be the final release series that supports the {% data variables.product.prodname_codeql %} runner. Starting with {% data variables.product.prodname_ghe_server %} 3.4, the {% data variables.product.prodname_codeql %} runner will be removed and no longer supported. The {% data variables.product.prodname_codeql %} CLI version 2.6.2 or greater is a feature-complete replacement for the {% data variables.product.prodname_codeql %} runner. For more information, see the [{% data variables.product.prodname_dotcom %} changelog](https://github.blog/changelog/2021-09-21-codeql-runner-deprecation/). - - - heading: Deprecation of custom bit-cache extensions - notes: - # https://github.com/github/releases/issues/1415 - - | - Starting in {% data variables.product.prodname_ghe_server %} 3.1, support for {% data variables.product.company_short %}'s proprietary bit-cache extensions began to be phased out. These extensions are now deprecated in {% data variables.product.prodname_ghe_server %} 3.3. - - Any repositories that were already present and active on {% data variables.product.product_location %} running version 3.1 or 3.2 will have been automatically updated. - - Repositories which were not present and active before upgrading to {% data variables.product.prodname_ghe_server %} 3.3 may not perform optimally until a repository maintenance task is run and has successfully completed. - - To start a repository maintenance task manually, browse to `https:///stafftools/repositories///network` for each affected repository and click the **Schedule** button. - - - heading: Change to the format of authentication tokens affects GitHub Connect - notes: - # https://github.com/github/releases/issues/1235 - - | - GitHub Connect will no longer work after June 3rd for instances running GitHub Enterprise Server 3.1 or older, due to the format of GitHub authentication tokens changing. To continue using GitHub Connect, upgrade to GitHub Enterprise Server 3.2 or later. For more information, see the [GitHub Blog](https://github.blog/2022-05-20-action-needed-by-github-connect-customers-using-ghes-3-1-and-older-to-adopt-new-authentication-token-format-updates/). [Updated: 2022-06-14] - - backups: - - '{% data variables.product.prodname_ghe_server %} 3.3 requires at least [GitHub Enterprise Backup Utilities 3.3.0](https://github.com/github/backup-utils) for [Backups and Disaster Recovery](/admin/configuration/configuring-your-enterprise/configuring-backups-on-your-appliance).' + - You can now filter pull request searches to only include pull requests you \ No newline at end of file diff --git a/translations/zh-CN/data/release-notes/enterprise-server/3-3/1.yml b/translations/zh-CN/data/release-notes/enterprise-server/3-3/1.yml index f1a151b0f5bc..8a1c6e91dc3a 100644 --- a/translations/zh-CN/data/release-notes/enterprise-server/3-3/1.yml +++ b/translations/zh-CN/data/release-notes/enterprise-server/3-3/1.yml @@ -1,13 +1,13 @@ date: '2021-12-13' sections: security_fixes: - - '{% octicon "alert" aria-label="The alert icon" %} 严重：****在 Log4j 库中发现远程代码执行漏洞，该漏洞会影响 3.3.1 之前的所有 {% data variables.product.prodname_ghe_server %} 版本，漏洞编号为 [CVE-2021-44228](https://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2021-44228)。Log4j 库用于在 {% data variables.product.prodname_ghe_server %} 实例上运行的开源服务。已在 {% data variables.product.prodname_ghe_server %} 3.0.22、3.1.14、3.2.6 和 3.3.1 中修复该漏洞。 有关详细信息，请参阅 GitHub 博客[文章](https://github.blog/2021-12-13-githubs-response-to-log4j-vulnerability-cve-2021-44228/)。' + - '{% octicon "alert" aria-label="The alert icon" %} 严重：****在 Log4j 库中发现远程代码执行漏洞，该漏洞会影响 3.3.1 之前的所有 {% data variables.product.prodname_ghe_server %} 版本，漏洞编号为 [CVE-2021-44228](https://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2021-44228)。Log4j 库用于在 {% data variables.product.prodname_ghe_server %} 实例上运行的开源服务。已在 {% data variables.product.prodname_ghe_server %} 3.0.22、3.1.14、3.2.6 和 3.3.1 中修复该漏洞。有关详细信息，请参阅 GitHub 博客 [文章](https://github.blog/2021-12-13-githubs-response-to-log4j-vulnerability-cve-2021-44228/)。' - '2021 年 12 月 17 日更新****：此版本中的修复也能缓解在该版本之后发布的 [CVE-2021-45046](https://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2021-45046)。无需再升级 {% data variables.product.prodname_ghe_server %}，即可缓解 CVE-2021-44228 和 CVE-2021-45046。' known_issues: - "升级到 {% data variables.product.prodname_ghe_server %} 3.3 后，{% data variables.product.prodname_actions %} 可能无法自动启动。若要解决此问题，请通过 SSH 连接到设备并运行 `ghe-actions-start` 命令。" - "在没有任何用户的新建 {% data variables.product.prodname_ghe_server %} 实例上，攻击者可以创建第一个管理员用户。" - 自定义防火墙规则在升级过程中被移除。 - - "[通过 Web 界面上传](https://github.com/blog/2105-upload-files-to-your-repositories)的 Git LFS 跟踪文件被错误地直接添加到存储库。" + - "[通过 Web 界面上传](https://github.com/blog/2105-upload-files-to-your-repositories) 的 Git LFS 跟踪文件被错误地直接添加到存储库。" - 如果问题包含同一存储库中 blob 的永久链接并且该 blob de 文件路径长于 255 个字符，则问题无法关闭。 - 在 GitHub Connect 中启用了“用户可以搜索 GitHub.com”时，专用和内部存储库中的问题不包括在 GitHub.com 搜索结果中。 - "{% data variables.product.prodname_registry %} npm 注册表不再在元数据响应中返回时间值。这样做是为了大幅改善性能。我们继续拥有将时间值作为元数据响应的一部分返回所需的所有数据，并将在以后解决现有性能问题后恢复返回该值。" diff --git a/translations/zh-CN/data/release-notes/enterprise-server/3-3/10.yml b/translations/zh-CN/data/release-notes/enterprise-server/3-3/10.yml index 5dd515f1ceda..93cc0f490ca4 100644 --- a/translations/zh-CN/data/release-notes/enterprise-server/3-3/10.yml +++ b/translations/zh-CN/data/release-notes/enterprise-server/3-3/10.yml @@ -13,7 +13,7 @@ sections: - "升级到 {% data variables.product.prodname_ghe_server %} 3.3 后，{% data variables.product.prodname_actions %} 可能无法自动启动。若要解决此问题，请通过 SSH 连接到设备并运行 `ghe-actions-start` 命令。" - "在新建的没有任何用户的 {% data variables.product.prodname_ghe_server %} 实例上，攻击者可以创建第一个管理员用户。" - 自定义防火墙规则在升级过程中被删除。 - - "[通过 Web 界面上传](https://github.com/blog/2105-upload-files-to-your-repositories)的 Git LFS 跟踪文件被错误地直接添加到存储库。" + - "[通过 Web 界面上传](https://github.com/blog/2105-upload-files-to-your-repositories) 的 Git LFS 跟踪文件被错误地直接添加到存储库。" - 如果问题包含文件路径长于 255 个字符的同一存储库中 blob 的永久链接，则问题无法关闭。 - "对 {% data variables.product.prodname_github_connect %} 启用“用户可以搜索 GitHub.com”后，专用和内部存储库中的问题不包括在 {% data variables.product.prodname_dotcom_the_website %} 搜索结果中。" - "{% data variables.product.prodname_registry %} npm 注册表不再在元数据响应中返回时间值。这样可以大幅改善性能。作为元数据响应的一部分，我们继续拥有返回时间值所需的所有数据，并将在以后解决现有性能问题后恢复返回这个值。" diff --git a/translations/zh-CN/data/release-notes/enterprise-server/3-3/11.yml b/translations/zh-CN/data/release-notes/enterprise-server/3-3/11.yml index af05faae671e..6e6dee098242 100644 --- a/translations/zh-CN/data/release-notes/enterprise-server/3-3/11.yml +++ b/translations/zh-CN/data/release-notes/enterprise-server/3-3/11.yml @@ -23,7 +23,7 @@ sections: - "升级到 {% data variables.product.prodname_ghe_server %} 3.3 后，{% data variables.product.prodname_actions %} 可能无法自动启动。若要解决此问题，请通过 SSH 连接到设备并运行 `ghe-actions-start` 命令。" - "在新建的没有任何用户的 {% data variables.product.prodname_ghe_server %} 实例上，攻击者可以创建第一个管理员用户。" - 自定义防火墙规则在升级过程中被删除。 - - "[通过 Web 界面上传](https://github.com/blog/2105-upload-files-to-your-repositories)的 Git LFS 跟踪文件被错误地直接添加到存储库。" + - "[通过 Web 界面上传](https://github.com/blog/2105-upload-files-to-your-repositories) 的 Git LFS 跟踪文件被错误地直接添加到存储库。" - 如果问题包含文件路径长于 255 个字符的同一存储库中 Blob 的永久链接，则问题无法关闭。 - "对 {% data variables.product.prodname_github_connect %} 启用“用户可以搜索 GitHub.com”后，专用和内部存储库中的问题不包括在 {% data variables.product.prodname_dotcom_the_website %} 搜索结果中。" - "{% data variables.product.prodname_registry %} npm 注册表不再在元数据响应中返回时间值。这样可以大幅改善性能。我们继续拥有将时间值作为元数据响应的一部分返回所需的所有数据，并将在以后解决现有性能问题后恢复返回该值。" diff --git a/translations/zh-CN/data/release-notes/enterprise-server/3-3/13.yml b/translations/zh-CN/data/release-notes/enterprise-server/3-3/13.yml index fc0b9b4e750c..aaf581f8d307 100644 --- a/translations/zh-CN/data/release-notes/enterprise-server/3-3/13.yml +++ b/translations/zh-CN/data/release-notes/enterprise-server/3-3/13.yml @@ -14,7 +14,7 @@ sections: - "升级到 {% data variables.product.prodname_ghe_server %} 3.3 后，{% data variables.product.prodname_actions %} 可能无法自动启动。若要解决此问题，请通过 SSH 连接到设备并运行 `ghe-actions-start` 命令。" - "在新建的没有任何用户的 {% data variables.product.prodname_ghe_server %} 实例上，攻击者可以创建第一个管理员用户。" - 自定义防火墙规则在升级过程中被删除。 - - "[通过 Web 界面上传](https://github.com/blog/2105-upload-files-to-your-repositories)的 Git LFS 跟踪文件被错误地直接添加到存储库。" + - "[通过 Web 界面上传](https://github.com/blog/2105-upload-files-to-your-repositories) 的 Git LFS 跟踪文件被错误地直接添加到存储库。" - 如果问题包含文件路径长于 255 个字符的同一存储库中 blob 的永久链接，则问题无法关闭。 - "对 {% data variables.product.prodname_github_connect %} 启用“用户可以搜索 GitHub.com”后，专用和内部存储库中的问题不包括在 {% data variables.product.prodname_dotcom_the_website %} 搜索结果中。" - "{% data variables.product.prodname_registry %} npm 注册表不再在元数据响应中返回时间值。这样可以大幅改善性能。作为元数据响应的一部分，我们继续拥有返回时间值所需的所有数据，并将在以后解决现有性能问题后恢复返回这个值。" diff --git a/translations/zh-CN/data/release-notes/enterprise-server/3-3/2.yml b/translations/zh-CN/data/release-notes/enterprise-server/3-3/2.yml index 7987ea5ef992..8c2319e683b4 100644 --- a/translations/zh-CN/data/release-notes/enterprise-server/3-3/2.yml +++ b/translations/zh-CN/data/release-notes/enterprise-server/3-3/2.yml @@ -22,7 +22,7 @@ sections: - "升级到 {% data variables.product.prodname_ghe_server %} 3.3 后，{% data variables.product.prodname_actions %} 可能无法自动启动。若要解决此问题，请通过 SSH 连接到设备并运行 `ghe-actions-start` 命令。" - "在新建的没有任何用户的 {% data variables.product.prodname_ghe_server %} 实例上，攻击者可以创建第一个管理员用户。" - 自定义防火墙规则在升级过程中被删除。 - - "[通过 Web 界面上传](https://github.com/blog/2105-upload-files-to-your-repositories)的 Git LFS 跟踪文件被错误地直接添加到存储库。" + - "[通过 Web 界面上传](https://github.com/blog/2105-upload-files-to-your-repositories) 的 Git LFS 跟踪文件被错误地直接添加到存储库。" - 如果问题包含文件路径长于 255 个字符的同一存储库中 blob 的永久链接，则问题无法关闭。 - 在 GitHub Connect 中启用了“用户可以搜索 GitHub.com”时，专用和内部存储库中的问题不包括在 GitHub.com 搜索结果中。 - "{% data variables.product.prodname_registry %} npm 注册表不再在元数据响应中返回时间值。这样可以大幅改善性能。我们继续拥有将时间值作为元数据响应的一部分返回所需的所有数据，并将在以后解决现有性能问题后恢复返回该值。" diff --git a/translations/zh-CN/data/release-notes/enterprise-server/3-3/3.yml b/translations/zh-CN/data/release-notes/enterprise-server/3-3/3.yml index 03a43eed09f5..cd38054c1b8d 100644 --- a/translations/zh-CN/data/release-notes/enterprise-server/3-3/3.yml +++ b/translations/zh-CN/data/release-notes/enterprise-server/3-3/3.yml @@ -20,7 +20,7 @@ sections: - "升级到 {% data variables.product.prodname_ghe_server %} 3.3 后，{% data variables.product.prodname_actions %} 可能无法自动启动。若要解决此问题，请通过 SSH 连接到设备并运行 `ghe-actions-start` 命令。" - "在新建的没有任何用户的 {% data variables.product.prodname_ghe_server %} 实例上，攻击者可以创建第一个管理员用户。" - 自定义防火墙规则在升级过程中被删除。 - - "[通过 Web 界面上传](https://github.com/blog/2105-upload-files-to-your-repositories)的 Git LFS 跟踪文件被错误地直接添加到存储库。" + - "[通过 Web 界面上传](https://github.com/blog/2105-upload-files-to-your-repositories) 的 Git LFS 跟踪文件被错误地直接添加到存储库。" - 如果问题包含文件路径长于 255 个字符的同一存储库中 blob 的永久链接，则问题无法关闭。 - 在 GitHub Connect 中启用了“用户可以搜索 GitHub.com”时，专用和内部存储库中的问题不包括在 GitHub.com 搜索结果中。 - "{% data variables.product.prodname_registry %} npm 注册表在元数据响应中不再返回时间值。这样可以大幅改善性能。我们继续拥有将时间值作为元数据响应的一部分返回所需的所有数据，并将在以后解决现有性能问题后恢复返回该值。" diff --git a/translations/zh-CN/data/release-notes/enterprise-server/3-3/4.yml b/translations/zh-CN/data/release-notes/enterprise-server/3-3/4.yml index 554a8318c1ae..da6ba74dc1bb 100644 --- a/translations/zh-CN/data/release-notes/enterprise-server/3-3/4.yml +++ b/translations/zh-CN/data/release-notes/enterprise-server/3-3/4.yml @@ -15,7 +15,7 @@ sections: - "升级到 {% data variables.product.prodname_ghe_server %} 3.3 后，{% data variables.product.prodname_actions %} 可能无法自动启动。若要解决此问题，请通过 SSH 连接到设备并运行 `ghe-actions-start` 命令。" - "在新建的没有任何用户的 {% data variables.product.prodname_ghe_server %} 实例上，攻击者可以创建第一个管理员用户。" - 自定义防火墙规则在升级过程中被删除。 - - "[通过 Web 界面上传](https://github.com/blog/2105-upload-files-to-your-repositories)的 Git LFS 跟踪文件被错误地直接添加到存储库。" + - "[通过 Web 界面上传](https://github.com/blog/2105-upload-files-to-your-repositories) 的 Git LFS 跟踪文件被错误地直接添加到存储库。" - 如果问题包含文件路径长于 255 个字符的同一存储库中 blob 的永久链接，则问题无法关闭。 - 在 GitHub Connect 中启用了“用户可以搜索 GitHub.com”时，专用和内部存储库中的问题不包括在 GitHub.com 搜索结果中。 - "{% data variables.product.prodname_registry %} npm 注册表不再在元数据响应中返回时间值。这样可以大幅改善性能。作为元数据响应的一部分，我们继续拥有返回时间值所需的所有数据，并将在以后解决现有性能问题后恢复返回这个值。" diff --git a/translations/zh-CN/data/release-notes/enterprise-server/3-3/5.yml b/translations/zh-CN/data/release-notes/enterprise-server/3-3/5.yml index 786a23168f83..9796b669bb46 100644 --- a/translations/zh-CN/data/release-notes/enterprise-server/3-3/5.yml +++ b/translations/zh-CN/data/release-notes/enterprise-server/3-3/5.yml @@ -9,7 +9,7 @@ sections: - "升级到 {% data variables.product.prodname_ghe_server %} 3.3 后，{% data variables.product.prodname_actions %} 可能无法自动启动。若要解决此问题，请通过 SSH 连接到设备并运行 `ghe-actions-start` 命令。" - "在新建的没有任何用户的 {% data variables.product.prodname_ghe_server %} 实例上，攻击者可以创建第一个管理员用户。" - 自定义防火墙规则在升级过程中被删除。 - - "[通过 Web 界面上传](https://github.com/blog/2105-upload-files-to-your-repositories)的 Git LFS 跟踪文件被错误地直接添加到存储库。" + - "[通过 Web 界面上传](https://github.com/blog/2105-upload-files-to-your-repositories) 的 Git LFS 跟踪文件被错误地直接添加到存储库。" - 如果问题包含文件路径长于 255 个字符的同一存储库中 blob 的永久链接，则问题无法关闭。 - 在 GitHub Connect 中启用了“用户可以搜索 GitHub.com”时，专用和内部存储库中的问题不包括在 GitHub.com 搜索结果中。 - "{% data variables.product.prodname_registry %} npm 注册表不再在元数据响应中返回时间值。这样可以大幅改善性能。作为元数据响应的一部分，我们继续拥有返回时间值所需的所有数据，并将在以后解决现有性能问题后恢复返回这个值。" diff --git a/translations/zh-CN/data/release-notes/enterprise-server/3-3/6.yml b/translations/zh-CN/data/release-notes/enterprise-server/3-3/6.yml index 00812d469b8c..971b0fb02c76 100644 --- a/translations/zh-CN/data/release-notes/enterprise-server/3-3/6.yml +++ b/translations/zh-CN/data/release-notes/enterprise-server/3-3/6.yml @@ -40,7 +40,7 @@ sections: - "升级到 {% data variables.product.prodname_ghe_server %} 3.3 后，{% data variables.product.prodname_actions %} 可能无法自动启动。若要解决此问题，请通过 SSH 连接到设备并运行 `ghe-actions-start` 命令。" - "在新建的没有任何用户的 {% data variables.product.prodname_ghe_server %} 实例上，攻击者可以创建第一个管理员用户。" - 自定义防火墙规则在升级过程中被删除。 - - "[通过 Web 界面上传](https://github.com/blog/2105-upload-files-to-your-repositories)的 Git LFS 跟踪文件被错误地直接添加到存储库。" + - "[通过 Web 界面上传](https://github.com/blog/2105-upload-files-to-your-repositories) 的 Git LFS 跟踪文件被错误地直接添加到存储库。" - 如果问题包含文件路径长于 255 个字符的同一存储库中 blob 的永久链接，则问题无法关闭。 - "对 {% data variables.product.prodname_github_connect %} 启用“用户可以搜索 GitHub.com”后，专用和内部存储库中的问题不包括在 {% data variables.product.prodname_dotcom_the_website %} 搜索结果中。" - "{% data variables.product.prodname_registry %} npm 注册表不再在元数据响应中返回时间值。这样可以大幅改善性能。我们继续拥有将时间值作为元数据响应的一部分返回所需的所有数据，并将在以后解决现有性能问题后恢复返回该值。" diff --git a/translations/zh-CN/data/release-notes/enterprise-server/3-3/7.yml b/translations/zh-CN/data/release-notes/enterprise-server/3-3/7.yml index 4bacfb9b5bfe..381e547e04e2 100644 --- a/translations/zh-CN/data/release-notes/enterprise-server/3-3/7.yml +++ b/translations/zh-CN/data/release-notes/enterprise-server/3-3/7.yml @@ -22,7 +22,7 @@ sections: - "升级到 {% data variables.product.prodname_ghe_server %} 3.3 后，{% data variables.product.prodname_actions %} 可能无法自动启动。若要解决此问题，请通过 SSH 连接到设备并运行 `ghe-actions-start` 命令。" - "在新建的没有任何用户的 {% data variables.product.prodname_ghe_server %} 实例上，攻击者可以创建第一个管理员用户。" - 自定义防火墙规则在升级过程中被删除。 - - "[通过 Web 界面上传](https://github.com/blog/2105-upload-files-to-your-repositories)的 Git LFS 跟踪文件被错误地直接添加到存储库。" + - "[通过 Web 界面上传](https://github.com/blog/2105-upload-files-to-your-repositories) 的 Git LFS 跟踪文件被错误地直接添加到存储库。" - 如果问题包含文件路径长于 255 个字符的同一存储库中 blob 的永久链接，则问题无法关闭。 - "对 {% data variables.product.prodname_github_connect %} 启用“用户可以搜索 GitHub.com”后，专用和内部存储库中的问题不包括在 {% data variables.product.prodname_dotcom_the_website %} 搜索结果中。" - "{% data variables.product.prodname_registry %} npm 注册表不再在元数据响应中返回时间值。这样做是为了大幅改善性能。作为元数据响应的一部分，我们继续拥有返回时间值所需的所有数据，并将在我们解决现有性能问题后恢复返回这个值。" diff --git a/translations/zh-CN/data/release-notes/enterprise-server/3-3/8.yml b/translations/zh-CN/data/release-notes/enterprise-server/3-3/8.yml index 952d8f1a3ada..7578a7aee7a4 100644 --- a/translations/zh-CN/data/release-notes/enterprise-server/3-3/8.yml +++ b/translations/zh-CN/data/release-notes/enterprise-server/3-3/8.yml @@ -2,7 +2,7 @@ date: '2022-05-17' sections: security_fixes: - '**中：**发现了 nginx 解析器中的一个安全问题，可以从 DNS 服务器伪造 UDP 数据包的攻击者可能导致 1 字节内存覆盖，从而导致工作进程崩溃或其他潜在的破坏性影响。该漏洞的编号为 [CVE-2021-23017](https://nvd.nist.gov/vuln/detail/CVE-2021-23017)。' - - "更新了 `actions/checkout@v2` 和 `actions/checkout@v3` 操作以解决 [Git 安全措施实施博客文章](https://github.blog/2022-04-12-git-security-vulnerability-announced/)中公布的新漏洞。" + - "更新了 `actions/checkout@v2` 和 `actions/checkout@v3` 操作以解决 [Git 安全措施实施博客文章](https://github.blog/2022-04-12-git-security-vulnerability-announced/) 中公布的新漏洞。" - 包已更新到最新的安全版本。 bugs: - 在某些群集拓扑中，`ghe-cluster-status` 命令会在 `/tmp` 中留下空目录。 diff --git a/translations/zh-CN/data/release-notes/enterprise-server/3-3/9.yml b/translations/zh-CN/data/release-notes/enterprise-server/3-3/9.yml index 5c427b58aeb6..48a15f0d68ba 100644 --- a/translations/zh-CN/data/release-notes/enterprise-server/3-3/9.yml +++ b/translations/zh-CN/data/release-notes/enterprise-server/3-3/9.yml @@ -17,7 +17,7 @@ sections: - "升级到 {% data variables.product.prodname_ghe_server %} 3.3 后，{% data variables.product.prodname_actions %} 可能无法自动启动。若要解决此问题，请通过 SSH 连接到设备并运行 `ghe-actions-start` 命令。" - "在新建的没有任何用户的 {% data variables.product.prodname_ghe_server %} 实例上，攻击者可以创建第一个管理员用户。" - 自定义防火墙规则在升级过程中被删除。 - - "[通过 Web 界面上传](https://github.com/blog/2105-upload-files-to-your-repositories)的 Git LFS 跟踪文件被错误地直接添加到存储库。" + - "[通过 Web 界面上传](https://github.com/blog/2105-upload-files-to-your-repositories) 的 Git LFS 跟踪文件被错误地直接添加到存储库。" - 如果问题包含文件路径长于 255 个字符的同一存储库中 blob 的永久链接，则问题无法关闭。 - "对 {% data variables.product.prodname_github_connect %} 启用“用户可以搜索 GitHub.com”后，专用和内部存储库中的问题不包括在 {% data variables.product.prodname_dotcom_the_website %} 搜索结果中。" - "{% data variables.product.prodname_registry %} npm 注册表不再在元数据响应中返回时间值。这样可以大幅改善性能。作为元数据响应的一部分，我们继续拥有返回时间值所需的所有数据，并将在以后解决现有性能问题后恢复返回这个值。" diff --git a/translations/zh-CN/data/release-notes/enterprise-server/3-4/0-rc1.yml b/translations/zh-CN/data/release-notes/enterprise-server/3-4/0-rc1.yml index f49bb7d8e3ef..e5667b2c09a5 100644 --- a/translations/zh-CN/data/release-notes/enterprise-server/3-4/0-rc1.yml +++ b/translations/zh-CN/data/release-notes/enterprise-server/3-4/0-rc1.yml @@ -151,136 +151,4 @@ sections: - heading: 'GitHub Actions changes' notes: # https://github.com/github/releases/issues/1906 - - '{% data variables.product.prodname_actions %} workflows triggered by {% data variables.product.prodname_dependabot %} for the `create`, `deployment`, and `deployment_status` events now always receive a read-only token and no secrets. Similarly, workflows triggered by {% data variables.product.prodname_dependabot %} for the `pull_request_target` event on pull requests where the base ref was created by {% data variables.product.prodname_dependabot %}, now always receive a read-only token and no secrets. These changes are designed to prevent potentially malicious code from executing in a privileged workflow. For more information, see "[Automating {% data variables.product.prodname_dependabot %} with {% data variables.product.prodname_actions %}](/code-security/supply-chain-security/keeping-your-dependencies-updated-automatically/automating-dependabot-with-github-actions)."' - - # https://github.com/github/releases/issues/1667 - - Workflow runs on `push` and `pull_request` events triggered by {% data variables.product.prodname_dependabot %} will now respect the permissions specified in your workflows, allowing you to control how you manage automatic dependency updates. The default token permissions will remain read-only. For more information, see the "[{% data variables.product.prodname_dotcom %} changelog](https://github.blog/changelog/2021-10-06-github-actions-workflows-triggered-by-dependabot-prs-will-respect-permissions-key-in-workflows/)." - - # https://github.com/github/releases/issues/1668 - - '{% data variables.product.prodname_actions %} workflows triggered by {% data variables.product.prodname_dependabot %} will now be sent the {% data variables.product.prodname_dependabot %} secrets. You can now pull from private package registries in your CI using the same secrets you have configured for {% data variables.product.prodname_dependabot %} to use, improving how {% data variables.product.prodname_actions %} and {% data variables.product.prodname_dependabot %} work together. For more information, see "[Automating {% data variables.product.prodname_dependabot %} with {% data variables.product.prodname_actions %}](/code-security/supply-chain-security/keeping-your-dependencies-updated-automatically/automating-dependabot-with-github-actions)."' - - # https://github.com/github/releases/issues/1615 - - You can now manage runner groups and see the status of your self-hosted runners using new Runners and Runner Groups pages in the UI. The Actions settings page for your repository or organization now shows a summary view of your runners, and allows you to deep dive into a specific runner to edit it or see what job it may be currently running. For more information, see the "[{% data variables.product.prodname_dotcom %} changelog](https://github.blog/changelog/2021-09-20-github-actions-experience-refresh-for-the-management-of-self-hosted-runners/)." - - # https://github.com/github/releases/issues/1785 - - 'Actions authors can now have their action run in Node.js 16 by specifying [`runs.using` as `node16` in the action''s `action.yml`](/actions/creating-actions/metadata-syntax-for-github-actions#runs-for-javascript-actions). This is in addition to the existing Node.js 12 support; actions can continue to specify `runs.using: node12` to use the Node.js 12 runtime.' - - # https://github.com/github/releases/issues/1799 - - 'For manually triggered workflows, {% data variables.product.prodname_actions %} now supports the `choice`, `boolean`, and `environment` input types in addition to the default `string` type. For more information, see "[`on.workflow_dispatch.inputs`](/actions/using-workflows/workflow-syntax-for-github-actions#onworkflow_dispatchinputs)."' - - # https://github.com/github/releases/issues/1782 - - Actions written in YAML, also known as composite actions, now support `if` conditionals. This lets you prevent specific steps from executing unless a condition has been met. Like steps defined in workflows, you can use any supported context and expression to create a conditional. - - # https://github.com/github/releases/issues/1919 - - The search order behavior for self-hosted runners has now changed, so that the first available matching runner at any level will run the job in all cases. This allows jobs to be sent to self-hosted runners much faster, especially for organizations and enterprises with lots of self-hosted runners. Previously, when running a job that required a self-hosted runner, {% data variables.product.prodname_actions %} would look for self-hosted runners in the repository, organization, and enterprise, in that order. - - # https://github.com/github/releases/issues/1753 - - Runner labels for {% data variables.product.prodname_actions %} self-hosted runners can now be listed, added and removed using the REST API. For more information about using the new APIs at a repository, organization, or enterprise level, see "[Repositories](/rest/reference/actions#list-labels-for-a-self-hosted-runner-for-a-repository)", "[Organizations](/rest/reference/actions#add-custom-labels-to-a-self-hosted-runner-for-an-organization)", and "[Enterprises](/rest/reference/enterprise-admin#list-labels-for-a-self-hosted-runner-for-an-enterprise)" in the REST API documentation. - - - heading: 'Dependabot and Dependency graph changes' - notes: - # https://github.com/github/releases/issues/1520 - - Dependency graph now supports detecting Python dependencies in repositories that use the Poetry package manager. Dependencies will be detected from both `pyproject.toml` and `poetry.lock` manifest files. - - # https://github.com/github/releases/issues/1921 - - When configuring {% data variables.product.prodname_dependabot %} security and version updates on GitHub Enterprise Server, we recommend you also enable {% data variables.product.prodname_dependabot %} in {% data variables.product.prodname_github_connect %}. This will allow {% data variables.product.prodname_dependabot %} to retrieve an updated list of dependencies and vulnerabilities from {% data variables.product.prodname_dotcom_the_website %}, by querying for information such as the changelogs of the public releases of open source code that you depend upon. For more information, see "[Enabling the dependency graph and Dependabot alerts for your enterprise](/admin/configuration/configuring-github-connect/enabling-the-dependency-graph-and-dependabot-alerts-for-your-enterprise)." - - # https://github.com/github/releases/issues/1717 - - '{% data variables.product.prodname_dependabot_alerts %} alerts can now be dismissed using the GraphQL API. For more information, see the "[dismissRepositoryVulnerabilityAlert](/graphql/reference/mutations#dismissrepositoryvulnerabilityalert)" mutation in the GraphQL API documentation.' - - - heading: 'Code scanning and secret scanning changes' - notes: - # https://github.com/github/releases/issues/1802 - - The {% data variables.product.prodname_codeql %} CLI now supports including markdown-rendered query help in SARIF files, so that the help text can be viewed in the {% data variables.product.prodname_code_scanning %} UI when the query generates an alert. For more information, see the "[{% data variables.product.prodname_dotcom %} changelog](https://github.blog/changelog/2021-11-23-display-help-text-for-your-custom-codeql-queries-in-code-scanning/)." - - # https://github.com/github/releases/issues/1790 - - The {% data variables.product.prodname_codeql %} CLI and {% data variables.product.prodname_vscode %} extension now support building databases and analyzing code on machines powered by Apple Silicon, such as Apple M1. For more information, see the "[{% data variables.product.prodname_dotcom %} changelog](https://github.blog/changelog/2021-11-10-codeql-now-supports-apple-silicon-m1/)." - - # https://github.com/github/releases/issues/1732 - - | - The depth of {% data variables.product.prodname_codeql %}'s analysis has been improved by adding support for more [libraries and frameworks](https://codeql.github.com/docs/codeql-overview/supported-languages-and-frameworks/) from the Python ecosystem. As a result, {% data variables.product.prodname_codeql %} can now detect even more potential sources of untrusted user data, steps through which that data flows, and potentially dangerous sinks where the data could end up. This results in an overall improvement of the quality of {% data variables.product.prodname_code_scanning %} alerts. For more information, see the "[{% data variables.product.prodname_dotcom %} changelog](https://github.blog/changelog/2021-11-24-codeql-code-scanning-now-recognizes-more-python-libraries-and-frameworks/)." - - # https://github.com/github/releases/issues/1567 - - Code scanning with {% data variables.product.prodname_codeql %} now includes beta support for analyzing code in all common Ruby versions, up to and including 3.02. For more information, see the "[{% data variables.product.prodname_dotcom %} changelog](https://github.blog/changelog/2021-10-27-codeql-code-scanning-adds-beta-support-for-ruby/)." - - # https://github.com/github/releases/issues/1764 - - | - Several improvements have been made to the {% data variables.product.prodname_code_scanning %} API: - - * The `fixed_at` timestamp has been added to alerts. This timestamp is the first time that the alert was not detected in an analysis. - * Alert results can now be sorted using `sort` and `direction` on either `created`, `updated` or `number`. For more information, see "[List code scanning alerts for a repository](/rest/reference/code-scanning#list-code-scanning-alerts-for-a-repository)." - * A `Last-Modified` header has been added to the alerts and alert endpoint response. For more information, see [`Last-Modified`](https://developer.mozilla.org/en-US/docs/Web/HTTP/Headers/Last-Modified) in the Mozilla documentation. - * The `relatedLocations` field has been added to the SARIF response when you request a code scanning analysis. The field may contain locations which are not the primary location of the alert. See an example in the [SARIF spec](https://docs.oasis-open.org/sarif/sarif/v2.1.0/cs01/sarif-v2.1.0-cs01.html#_Toc16012616) and for more information see "[Get a code scanning analysis for a repository](/rest/reference/code-scanning#get-a-code-scanning-analysis-for-a-repository)." - * Both `help` and `tags` data have been added to the webhook response alert rule object. For more information, see "[Code scanning alert webhooks events and payloads](/developers/webhooks-and-events/webhooks/webhook-events-and-payloads#code_scanning_alert)." - * Personal access tokens with the `public_repo` scope now have write access for code scanning endpoints on public repos, if the user has permission. - - For more information, see "[Code scanning](/rest/reference/code-scanning)" in the REST API documentation. - - # https://github.com/github/releases/issues/1943 - - '{% data variables.product.prodname_GH_advanced_security %} customers can now use the REST API to retrieve private repository secret scanning results at the enterprise level. The new endpoint supplements the existing repository-level and organization-level endpoints. For more information, see "[Secret scanning](/rest/reference/secret-scanning)" in the REST API documentation.' - - # No security/bug fixes for the RC release - # security_fixes: - # - PLACEHOLDER - - # bugs: - # - PLACEHOLDER - - 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 needs to be restarted after restoring appliance from backup taken on a different host. - - deprecations: - - heading: Deprecation of GitHub Enterprise Server 3.0 - notes: - - '**{% data variables.product.prodname_ghe_server %} 3.0 was discontinued on February 16, 2022**. This means that no patch releases will be made, even for critical security issues, after this date. For better performance, improved security, and new features, [upgrade to the newest version of {% data variables.product.prodname_ghe_server %}](/enterprise-server@3.4/admin/enterprise-management/upgrading-github-enterprise-server) as soon as possible.' - - heading: Deprecation of GitHub Enterprise Server 3.1 - notes: - - '**{% data variables.product.prodname_ghe_server %} 3.1 will be discontinued on June 3, 2022**. This means that no patch releases will be made, even for critical security issues, after this date. For better performance, improved security, and new features, [upgrade to the newest version of {% data variables.product.prodname_ghe_server %}](/enterprise-server@3.4/admin/enterprise-management/upgrading-github-enterprise-server) as soon as possible.' - - - heading: Deprecation of XenServer Hypervisor support - notes: - # https://github.com/github/docs-content/issues/4439 - - Starting in {% data variables.product.prodname_ghe_server %} 3.3, {% data variables.product.prodname_ghe_server %} on XenServer was deprecated and is no longer supported. Please contact [GitHub Support](https://support.github.com) with questions or concerns. - - - heading: Deprecation of the Content Attachments API preview - notes: - # - - Due to low usage, we have deprecated the Content References API preview in {% data variables.product.prodname_ghe_server %} 3.4. The API was previously accessible with the `corsair-preview` header. Users can continue to navigate to external URLs without this API. Any registered usages of the Content References API will no longer receive a webhook notification for URLs from your registered domain(s) and we no longer return valid response codes for attempted updates to existing content attachments. - - - heading: Deprecation of the Codes of Conduct API preview - notes: - # https://github.com/github/releases/issues/1708 - - 'The Codes of Conduct API preview, which was accessible with the `scarlet-witch-preview` header, is deprecated and no longer accessible in {% data variables.product.prodname_ghe_server %} 3.4. We instead recommend using the "[Get community profile metrics](/rest/reference/repos#get-community-profile-metrics)" endpoint to retrieve information about a repository''s code of conduct. For more information, see the "[Deprecation Notice: Codes of Conduct API preview](https://github.blog/changelog/2021-10-06-deprecation-notice-codes-of-conduct-api-preview/)" in the {% data variables.product.prodname_dotcom %} changelog.' - - - heading: Deprecation of OAuth Application API endpoints and API authentication using query parameters - notes: - # https://github.com/github/releases/issues/1316 - - | - Starting with {% data variables.product.prodname_ghe_server %} 3.4, the [deprecated version of the OAuth Application API endpoints](https://developer.github.com/changes/2020-02-14-deprecating-oauth-app-endpoint/#endpoints-affected) have been removed. If you encounter 404 error messages on these endpoints, convert your code to the versions of the OAuth Application API that do not have `access_tokens` in the URL. We've also disabled the use of API authentication using query parameters. We instead recommend using [API authentication in the request header](https://developer.github.com/changes/2020-02-10-deprecating-auth-through-query-param/#changes-to-make). - - - heading: Deprecation of the CodeQL runner - notes: - # https://github.com/github/releases/issues/1632 - - The {% data variables.product.prodname_codeql %} runner is deprecated in {% data variables.product.prodname_ghe_server %} 3.4 and is no longer supported. The deprecation only affects users who use {% data variables.product.prodname_codeql %} code scanning in third party CI/CD systems; {% data variables.product.prodname_actions %} users are not affected. We strongly recommend that customers migrate to the {% data variables.product.prodname_codeql %} CLI, which is a feature-complete replacement for the {% data variables.product.prodname_codeql %} runner. For more information, see the [{% data variables.product.prodname_dotcom %} changelog](https://github.blog/changelog/2021-09-21-codeql-runner-deprecation/). - - - heading: Deprecation of custom bit-cache extensions - notes: - # https://github.com/github/releases/issues/1415 - - | - Starting in {% data variables.product.prodname_ghe_server %} 3.1, support for {% data variables.product.company_short %}'s proprietary bit-cache extensions began to be phased out. These extensions are deprecated in {% data variables.product.prodname_ghe_server %} 3.3 onwards. - - Any repositories that were already present and active on {% data variables.product.product_location %} running version 3.1 or 3.2 will have been automatically updated. - - Repositories which were not present and active before upgrading to {% data variables.product.prodname_ghe_server %} 3.3 may not perform optimally until a repository maintenance task is run and has successfully completed. - - To start a repository maintenance task manually, browse to `https:///stafftools/repositories///network` for each affected repository and click the Schedule button. - - backups: - - '{% data variables.product.prodname_ghe_server %} 3.4 requires at least [GitHub Enterprise Backup Utilities 3.4.0](https://github.com/github/backup-utils) for [Backups and Disaster Recovery](/admin/configuration/configuring-your-enterprise/configuring-backups-on-your-appliance).' + - '{% data variables.product.prodname_actions %} workflows triggered by {% data variables.product.prodname_dependabot %} f \ No newline at end of file diff --git a/translations/zh-CN/data/release-notes/enterprise-server/3-4/0.yml b/translations/zh-CN/data/release-notes/enterprise-server/3-4/0.yml index 0ff37f40589e..17ea09b1e008 100644 --- a/translations/zh-CN/data/release-notes/enterprise-server/3-4/0.yml +++ b/translations/zh-CN/data/release-notes/enterprise-server/3-4/0.yml @@ -151,164 +151,4 @@ sections: - Administrators can now allow only specific users and teams to bypass pull request requirements. For more information, see the "[{% data variables.product.prodname_dotcom %} changelog](https://github.blog/changelog/2021-11-19-allow-bypassing-required-pull-requests/)." # https://github.com/github/releases/issues/1850 - - Administrators can now allow only specific users and teams to force push to a repository. For more information, see the "[{% data variables.product.prodname_dotcom %} changelog](https://github.blog/changelog/2021-12-21-specify-who-can-force-push-to-a-repository/)." - - # https://github.com/github/releases/issues/1796 - - When requiring pull requests for all changes to a protected branch, administrators can now choose if approved reviews are also a requirement. For more information, see the "[{% data variables.product.prodname_dotcom %} changelog](https://github.blog/changelog/2021-11-10-require-pull-requests-without-requiring-reviews/)." - - - heading: 'GitHub Actions changes' - notes: - # https://github.com/github/releases/issues/1906 - - '{% data variables.product.prodname_actions %} workflows triggered by {% data variables.product.prodname_dependabot %} for the `create`, `deployment`, and `deployment_status` events now always receive a read-only token and no secrets. Similarly, workflows triggered by {% data variables.product.prodname_dependabot %} for the `pull_request_target` event on pull requests where the base ref was created by {% data variables.product.prodname_dependabot %}, now always receive a read-only token and no secrets. These changes are designed to prevent potentially malicious code from executing in a privileged workflow. For more information, see "[Automating {% data variables.product.prodname_dependabot %} with {% data variables.product.prodname_actions %}](/code-security/supply-chain-security/keeping-your-dependencies-updated-automatically/automating-dependabot-with-github-actions)."' - - # https://github.com/github/releases/issues/1667 - - Workflow runs on `push` and `pull_request` events triggered by {% data variables.product.prodname_dependabot %} will now respect the permissions specified in your workflows, allowing you to control how you manage automatic dependency updates. The default token permissions will remain read-only. For more information, see the "[{% data variables.product.prodname_dotcom %} changelog](https://github.blog/changelog/2021-10-06-github-actions-workflows-triggered-by-dependabot-prs-will-respect-permissions-key-in-workflows/)." - - # https://github.com/github/releases/issues/1668 - - '{% data variables.product.prodname_actions %} workflows triggered by {% data variables.product.prodname_dependabot %} will now be sent the {% data variables.product.prodname_dependabot %} secrets. You can now pull from private package registries in your CI using the same secrets you have configured for {% data variables.product.prodname_dependabot %} to use, improving how {% data variables.product.prodname_actions %} and {% data variables.product.prodname_dependabot %} work together. For more information, see "[Automating {% data variables.product.prodname_dependabot %} with {% data variables.product.prodname_actions %}](/code-security/supply-chain-security/keeping-your-dependencies-updated-automatically/automating-dependabot-with-github-actions)."' - - # https://github.com/github/releases/issues/1615 - - You can now manage runner groups and see the status of your self-hosted runners using new Runners and Runner Groups pages in the UI. The Actions settings page for your repository or organization now shows a summary view of your runners, and allows you to deep dive into a specific runner to edit it or see what job it may be currently running. For more information, see the "[{% data variables.product.prodname_dotcom %} changelog](https://github.blog/changelog/2021-09-20-github-actions-experience-refresh-for-the-management-of-self-hosted-runners/)." - - # https://github.com/github/releases/issues/1785 - - 'Actions authors can now have their action run in Node.js 16 by specifying [`runs.using` as `node16` in the action''s `action.yml`](/actions/creating-actions/metadata-syntax-for-github-actions#runs-for-javascript-actions). This is in addition to the existing Node.js 12 support; actions can continue to specify `runs.using: node12` to use the Node.js 12 runtime.' - - # https://github.com/github/releases/issues/1799 - - 'For manually triggered workflows, {% data variables.product.prodname_actions %} now supports the `choice`, `boolean`, and `environment` input types in addition to the default `string` type. For more information, see "[`on.workflow_dispatch.inputs`](/actions/using-workflows/workflow-syntax-for-github-actions#onworkflow_dispatchinputs)."' - - # https://github.com/github/releases/issues/1782 - - Actions written in YAML, also known as composite actions, now support `if` conditionals. This lets you prevent specific steps from executing unless a condition has been met. Like steps defined in workflows, you can use any supported context and expression to create a conditional. - - # https://github.com/github/releases/issues/1919 - - The search order behavior for self-hosted runners has now changed, so that the first available matching runner at any level will run the job in all cases. This allows jobs to be sent to self-hosted runners much faster, especially for organizations and enterprises with lots of self-hosted runners. Previously, when running a job that required a self-hosted runner, {% data variables.product.prodname_actions %} would look for self-hosted runners in the repository, organization, and enterprise, in that order. - - # https://github.com/github/releases/issues/1753 - - Runner labels for {% data variables.product.prodname_actions %} self-hosted runners can now be listed, added and removed using the REST API. For more information about using the new APIs at a repository, organization, or enterprise level, see "[Repositories](/rest/reference/actions#list-labels-for-a-self-hosted-runner-for-a-repository)", "[Organizations](/rest/reference/actions#add-custom-labels-to-a-self-hosted-runner-for-an-organization)", and "[Enterprises](/rest/reference/enterprise-admin#list-labels-for-a-self-hosted-runner-for-an-enterprise)" in the REST API documentation. - - - heading: 'Dependabot and Dependency graph changes' - notes: - # https://github.com/github/releases/issues/1520 - - Dependency graph now supports detecting Python dependencies in repositories that use the Poetry package manager. Dependencies will be detected from both `pyproject.toml` and `poetry.lock` manifest files. - - # https://github.com/github/releases/issues/1921 - - When configuring {% data variables.product.prodname_dependabot %} security and version updates on GitHub Enterprise Server, we recommend you also enable {% data variables.product.prodname_dependabot %} in {% data variables.product.prodname_github_connect %}. This will allow {% data variables.product.prodname_dependabot %} to retrieve an updated list of dependencies and vulnerabilities from {% data variables.product.prodname_dotcom_the_website %}, by querying for information such as the changelogs of the public releases of open source code that you depend upon. For more information, see "[Enabling the dependency graph and Dependabot alerts for your enterprise](/admin/configuration/configuring-github-connect/enabling-the-dependency-graph-and-dependabot-alerts-for-your-enterprise)." - - # https://github.com/github/releases/issues/1717 - - '{% data variables.product.prodname_dependabot_alerts %} alerts can now be dismissed using the GraphQL API. For more information, see the "[dismissRepositoryVulnerabilityAlert](/graphql/reference/mutations#dismissrepositoryvulnerabilityalert)" mutation in the GraphQL API documentation.' - - - heading: 'Code scanning and secret scanning changes' - notes: - # https://github.com/github/releases/issues/1802 - - The {% data variables.product.prodname_codeql %} CLI now supports including markdown-rendered query help in SARIF files, so that the help text can be viewed in the {% data variables.product.prodname_code_scanning %} UI when the query generates an alert. For more information, see the "[{% data variables.product.prodname_dotcom %} changelog](https://github.blog/changelog/2021-11-23-display-help-text-for-your-custom-codeql-queries-in-code-scanning/)." - - # https://github.com/github/releases/issues/1790 - - The {% data variables.product.prodname_codeql %} CLI and {% data variables.product.prodname_vscode %} extension now support building databases and analyzing code on machines powered by Apple Silicon, such as Apple M1. For more information, see the "[{% data variables.product.prodname_dotcom %} changelog](https://github.blog/changelog/2021-11-10-codeql-now-supports-apple-silicon-m1/)." - - # https://github.com/github/releases/issues/1732 - - | - The depth of {% data variables.product.prodname_codeql %}'s analysis has been improved by adding support for more [libraries and frameworks](https://codeql.github.com/docs/codeql-overview/supported-languages-and-frameworks/) from the Python ecosystem. As a result, {% data variables.product.prodname_codeql %} can now detect even more potential sources of untrusted user data, steps through which that data flows, and potentially dangerous sinks where the data could end up. This results in an overall improvement of the quality of {% data variables.product.prodname_code_scanning %} alerts. For more information, see the "[{% data variables.product.prodname_dotcom %} changelog](https://github.blog/changelog/2021-11-24-codeql-code-scanning-now-recognizes-more-python-libraries-and-frameworks/)." - - # https://github.com/github/releases/issues/1567 - - Code scanning with {% data variables.product.prodname_codeql %} now includes beta support for analyzing code in all common Ruby versions, up to and including 3.02. For more information, see the "[{% data variables.product.prodname_dotcom %} changelog](https://github.blog/changelog/2021-10-27-codeql-code-scanning-adds-beta-support-for-ruby/)." - - # https://github.com/github/releases/issues/1764 - - | - Several improvements have been made to the {% data variables.product.prodname_code_scanning %} API: - - * The `fixed_at` timestamp has been added to alerts. This timestamp is the first time that the alert was not detected in an analysis. - * Alert results can now be sorted using `sort` and `direction` on either `created`, `updated` or `number`. For more information, see "[List code scanning alerts for a repository](/rest/reference/code-scanning#list-code-scanning-alerts-for-a-repository)." - * A `Last-Modified` header has been added to the alerts and alert endpoint response. For more information, see [`Last-Modified`](https://developer.mozilla.org/en-US/docs/Web/HTTP/Headers/Last-Modified) in the Mozilla documentation. - * The `relatedLocations` field has been added to the SARIF response when you request a code scanning analysis. The field may contain locations which are not the primary location of the alert. See an example in the [SARIF spec](https://docs.oasis-open.org/sarif/sarif/v2.1.0/cs01/sarif-v2.1.0-cs01.html#_Toc16012616) and for more information see "[Get a code scanning analysis for a repository](/rest/reference/code-scanning#get-a-code-scanning-analysis-for-a-repository)." - * Both `help` and `tags` data have been added to the webhook response alert rule object. For more information, see "[Code scanning alert webhooks events and payloads](/developers/webhooks-and-events/webhooks/webhook-events-and-payloads#code_scanning_alert)." - * Personal access tokens with the `public_repo` scope now have write access for code scanning endpoints on public repos, if the user has permission. - - For more information, see "[Code scanning](/rest/reference/code-scanning)" in the REST API documentation. - - # https://github.com/github/releases/issues/1943 - - '{% data variables.product.prodname_GH_advanced_security %} customers can now use the REST API to retrieve private repository secret scanning results at the enterprise level. The new endpoint supplements the existing repository-level and organization-level endpoints. For more information, see "[Secret scanning](/rest/reference/secret-scanning)" in the REST API documentation.' - - - heading: Mobile changes - notes: - # https://github.com/github/mobile/issues/2440 - # https://github.com/github/enterprise2/pull/28057 - - Support for {% data variables.product.prodname_mobile %} is now enabled by default for new {% data variables.product.prodname_ghe_server %} instances. If you have not explicitly disabled or enabled {% data variables.product.prodname_mobile %}, {% data variables.product.prodname_mobile %} will be enabled when you upgrade to {% data variables.product.prodname_ghe_server %} 3.4.0 or later. If you previously disabled or enabled {% data variables.product.prodname_mobile %} for your instance, your preference will be preserved upon upgrade. For more information, see "[Managing {% data variables.product.prodname_mobile %} for your enterprise](/admin/configuration/configuring-your-enterprise/managing-github-mobile-for-your-enterprise)." - - # No security/bug fixes for the GA release - # security_fixes: - # - PLACEHOLDER - - # bugs: - # - PLACEHOLDER - - 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 needs to be restarted after restoring appliance from backup taken on a different host. - - | - 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] - - | - 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] - - 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: - - '**{% data variables.product.prodname_ghe_server %} 3.0 was discontinued on February 16, 2022**. This means that no patch releases will be made, even for critical security issues, after this date. For better performance, improved security, and new features, [upgrade to the newest version of {% data variables.product.prodname_ghe_server %}](/enterprise-server@3.4/admin/enterprise-management/upgrading-github-enterprise-server) as soon as possible.' - - heading: Deprecation of GitHub Enterprise Server 3.1 - notes: - - '**{% data variables.product.prodname_ghe_server %} 3.1 will be discontinued on June 3, 2022**. This means that no patch releases will be made, even for critical security issues, after this date. For better performance, improved security, and new features, [upgrade to the newest version of {% data variables.product.prodname_ghe_server %}](/enterprise-server@3.4/admin/enterprise-management/upgrading-github-enterprise-server) as soon as possible.' - - - heading: Deprecation of XenServer Hypervisor support - notes: - # https://github.com/github/docs-content/issues/4439 - - Starting in {% data variables.product.prodname_ghe_server %} 3.3, {% data variables.product.prodname_ghe_server %} on XenServer was deprecated and is no longer supported. Please contact [GitHub Support](https://support.github.com) with questions or concerns. - - - heading: Deprecation of the Content Attachments API preview - notes: - # - - Due to low usage, we have deprecated the Content References API preview in {% data variables.product.prodname_ghe_server %} 3.4. The API was previously accessible with the `corsair-preview` header. Users can continue to navigate to external URLs without this API. Any registered usages of the Content References API will no longer receive a webhook notification for URLs from your registered domain(s) and we no longer return valid response codes for attempted updates to existing content attachments. - - - heading: Deprecation of the Codes of Conduct API preview - notes: - # https://github.com/github/releases/issues/1708 - - 'The Codes of Conduct API preview, which was accessible with the `scarlet-witch-preview` header, is deprecated and no longer accessible in {% data variables.product.prodname_ghe_server %} 3.4. We instead recommend using the "[Get community profile metrics](/rest/reference/repos#get-community-profile-metrics)" endpoint to retrieve information about a repository''s code of conduct. For more information, see the "[Deprecation Notice: Codes of Conduct API preview](https://github.blog/changelog/2021-10-06-deprecation-notice-codes-of-conduct-api-preview/)" in the {% data variables.product.prodname_dotcom %} changelog.' - - - heading: Deprecation of OAuth Application API endpoints and API authentication using query parameters - notes: - # https://github.com/github/releases/issues/1316 - - | - Starting with {% data variables.product.prodname_ghe_server %} 3.4, the [deprecated version of the OAuth Application API endpoints](https://developer.github.com/changes/2020-02-14-deprecating-oauth-app-endpoint/#endpoints-affected) have been removed. If you encounter 404 error messages on these endpoints, convert your code to the versions of the OAuth Application API that do not have `access_tokens` in the URL. We've also disabled the use of API authentication using query parameters. We instead recommend using [API authentication in the request header](https://developer.github.com/changes/2020-02-10-deprecating-auth-through-query-param/#changes-to-make). - - - heading: Deprecation of the CodeQL runner - notes: - # https://github.com/github/releases/issues/1632 - - The {% data variables.product.prodname_codeql %} runner is deprecated in {% data variables.product.prodname_ghe_server %} 3.4 and is no longer supported. The deprecation only affects users who use {% data variables.product.prodname_codeql %} code scanning in third party CI/CD systems; {% data variables.product.prodname_actions %} users are not affected. We strongly recommend that customers migrate to the {% data variables.product.prodname_codeql %} CLI, which is a feature-complete replacement for the {% data variables.product.prodname_codeql %} runner. For more information, see the [{% data variables.product.prodname_dotcom %} changelog](https://github.blog/changelog/2021-09-21-codeql-runner-deprecation/). - - - heading: Deprecation of custom bit-cache extensions - notes: - # https://github.com/github/releases/issues/1415 - - | - Starting in {% data variables.product.prodname_ghe_server %} 3.1, support for {% data variables.product.company_short %}'s proprietary bit-cache extensions began to be phased out. These extensions are deprecated in {% data variables.product.prodname_ghe_server %} 3.3 onwards. - - Any repositories that were already present and active on {% data variables.product.product_location %} running version 3.1 or 3.2 will have been automatically updated. - - Repositories which were not present and active before upgrading to {% data variables.product.prodname_ghe_server %} 3.3 may not perform optimally until a repository maintenance task is run and has successfully completed. - - To start a repository maintenance task manually, browse to `https:///stafftools/repositories///network` for each affected repository and click the Schedule button. - - - heading: Change to the format of authentication tokens affects GitHub Connect - notes: - # https://github.com/github/releases/issues/1235 - - | - GitHub Connect will no longer work after June 3rd for instances running GitHub Enterprise Server 3.1 or older, due to the format of GitHub authentication tokens changing. For more information, see the [GitHub changelog](https://github.blog/2022-05-20-action-needed-by-github-connect-customers-using-ghes-3-1-and-older-to-adopt-new-authentication-token-format-updates/). [Updated: 2022-06-14] - - backups: - - '{% data variables.product.prodname_ghe_server %} 3.4 requires at least [GitHub Enterprise Backup Utilities 3.4.0](https://github.com/github/backup-utils) for [Backups and Disaster Recovery](/admin/configuration/configuring-your-enterprise/configuring-backups-on-your-appliance).' + \ No newline at end of file diff --git a/translations/zh-CN/data/release-notes/enterprise-server/3-5/0-rc1.yml b/translations/zh-CN/data/release-notes/enterprise-server/3-5/0-rc1.yml index 378a8b6706f4..7933601f7eb9 100644 --- a/translations/zh-CN/data/release-notes/enterprise-server/3-5/0-rc1.yml +++ b/translations/zh-CN/data/release-notes/enterprise-server/3-5/0-rc1.yml @@ -92,330 +92,4 @@ sections: notes: # https://github.com/github/releases/issues/1963 - | - You can now configure GitHub Enterprise Server to automatically sign commits made in the web interface, such as from editing a file or merging a pull request. Signed commits increase confidence that changes come from trusted sources. This feature allows the [Require signed commits](/repositories/configuring-branches-and-merges-in-your-repository/defining-the-mergeability-of-pull-requests/about-protected-branches#require-signed-commits) branch protection setting to block unsigned commits from entering a repository, while allowing entry of signed commits – even those made in the web interface. For more information, see "[Configuring web commit signing](/admin/configuration/configuring-your-enterprise/configuring-web-commit-signing)." - - - heading: Sync license usage any time - notes: - # https://github.com/github/releases/issues/2201 - - | - For customers that sync license usage between GitHub Enterprise Server and GitHub Enterprise Cloud automatically using GitHub Connect, you now have the ability to sync your license usage independently of the automatic weekly sync. This feature also reports the status of sync job. For more information, see "[Syncing license usage between GitHub Enterprise Server and GitHub Enterprise Cloud](/billing/managing-your-license-for-github-enterprise/syncing-license-usage-between-github-enterprise-server-and-github-enterprise-cloud#manually-syncing-license-usage)." - - - heading: Reusable workflows for GitHub Actions are generally available - notes: - # https://github.com/github/releases/issues/1767 - # https://github.com/github/releases/issues/1950 - # https://github.com/github/releases/issues/2114 - - | - Reusable workflows are now generally available. Reusable workflows help you reduce duplication by enabling you to reuse an entire workflow as if it were an action. With the general availability release, a number of improvements are now available for GitHub Enterprise Server. For more information, see "[Reusing workflows](/actions/using-workflows/reusing-workflows)." - - - You can utilize outputs to pass data from reusable workflows to other jobs in the caller workflow. - - You can pass environment secrets to reusable workflows. - - The audit log includes information about which reusable workflows are used. - - Reusable workflows in the same repository as the calling repository can be referenced with just the path and filename (`PATH/FILENAME`). The called workflow will be from the same commit as the caller workflow. - - - heading: Self-hosted runners for GitHub Actions can now disable automatic updates - notes: - # https://github.com/github/releases/issues/2014 - - | - You now have more control over when your self-hosted runners perform software updates. If you specify the `--disableupdate` flag to the runner then it will not try to perform an automatic software update if a newer version of the runner is available. This allows you to update the self-hosted runner on your own schedule, and is especially convenient if your self-hosted runner is in a container. - - For compatibility with the GitHub Actions service, you will need to manually update your runner within 30 days of a new runner version being available. For instructions on how to install the latest runner version, please see the installation instructions for [the latest release in the runner repo](https://github.com/actions/runner/releases). - - - heading: Secure self-hosted runners for GitHub Actions by limiting workflows - notes: - # https://github.com/github/releases/issues/2013 - - | - Organization owners can now increase the security of CI/CD workflows on self-hosted runners by choosing which workflows can access a runner group. Previously, any workflow in a repository, such as an issue labeler, could access the self-hosted runners available to an organization. For more information, see "[Managing access to self-hosted runners using groups](/actions/hosting-your-own-runners/managing-access-to-self-hosted-runners-using-groups#changing-what-workflows-can-access-a-runner-group)" and the [GitHub Blog](https://github.blog/2022-03-23-github-actions-secure-self-hosted-runners-specific-workflows/). - - - heading: Prevent GitHub Actions from approving pull requests - notes: - # https://github.com/github/releases/issues/1959 - - | - You can now control whether GitHub Actions can approve pull requests. This feature protects against a user using GitHub Actions to satisfy the "Required approvals" branch protection requirement and merging a change that was not reviewed by another user. To prevent breaking existing workflows, **Allow GitHub Actions reviews to count towards required approval** is enabled by default. Organization owners can disable the feature in the organization's GitHub Actions settings. For more information, see "[Disabling or limiting GitHub Actions for your organization](/organizations/managing-organization-settings/disabling-or-limiting-github-actions-for-your-organization#preventing-github-actions-from-approving-pull-requests)." - - - heading: Re-run failed or individual GitHub Actions jobs - notes: - # https://github.com/github/releases/issues/1503 - - | - You can now re-run only failed jobs or an individual job in a GitHub Actions workflow run. For more information, see "[Re-running workflows and jobs](/actions/managing-workflow-runs/re-running-workflows-and-jobs)." - - - heading: Dependency graph supports GitHub Actions - notes: - # https://github.com/github/releases/issues/1913 - - | - The dependency graph now detects YAML files for GitHub Actions workflows. GitHub Enterprise Server will display the workflow files within the **Insights** tab's dependency graph section. Repositories that publish actions will also be able to see the number of repositories that depend on that action from the "Used By" control on the repository homepage. For more information, see "[About the dependency graph](/code-security/supply-chain-security/understanding-your-software-supply-chain/about-the-dependency-graph)." - - - heading: Security overview for enterprises in public beta - notes: - # https://github.com/github/releases/issues/2040 - - | - GitHub Advanced Security customers can now view an overview of security alerts at the enterprise level. The new **Security** tab at the enterprise level provides a repository-centric view of application security risks, as well as an alert-centric view of all secret scanning alerts. For more information, see "[About the security overview](/code-security/security-overview/about-the-security-overview)." - - - heading: Security view for organizations is generally available - notes: - # https://github.com/github/releases/issues/2096 - - | - The overview of security alerts at the organization level is now generally available. GitHub Advanced Security customers can use the security overview to view a repository-centric view of application security risks, or an alert-centric view of all code scanning, Dependabot, and secret scanning alerts for all repositories in an organization. For more information, see "[About the security overview](/code-security/security-overview/about-the-security-overview)." - - - heading: Code scanning detects more security issues, supports new language versions - notes: - # https://github.com/github/releases/issues/2097 - - | - Code scanning now detects a larger number of CWEs, and CodeQL code scanning fully supports the standard language features in the following language releases. - - - C# 10 / .NET 6 - - Python 3.10 - - Java 17 - - TypeScript 4.5 - - For more information, see the [GitHub Blog](https://github.blog/changelog/2022-02-25-code-scanning-detects-more-security-issues-supports-new-language-versions/). - - - heading: View code scanning alerts across an organization - notes: - # https://github.com/github/releases/issues/1792 - - | - GitHub Advanced Security customers can now view code scanning alerts in an organization's **Security** tab. This view is available to organization owners and members of teams with the [security manager role](/organizations/managing-peoples-access-to-your-organization-with-roles/managing-security-managers-in-your-organization). For more information, see "[About the security overview](/code-security/security-overview/about-the-security-overview)." - - # https://github.com/github/releases/issues/1763 - - | - Users can now retrieve code scanning alerts for an organization on your GitHub Enterprise Server instance via the REST API. This new API endpoint supplements the existing [endpoint for repositories](/rest/reference/code-scanning#list-code-scanning-alerts-for-a-repository). For more information, see [Code Scanning](/rest/code-scanning) in the REST API documentation. - - - heading: Secret scanning available as a push protection - notes: - # - - | - GitHub Enterprise Server can now block any pushes where a token is detected with high confidence. Developers can bypass the block by providing details of why the secret needs to be committed via a web UI. For more information, see "[Protecting pushes with secret scanning](/code-security/secret-scanning/protecting-pushes-with-secret-scanning)." - - - heading: Dry runs for custom patterns with secret scanning - notes: - # https://github.com/github/releases/issues/1703 - # https://github.com/github/releases/issues/2084 - - | - GitHub Advanced Security customers can now dry run custom secret scanning patterns at the organization or repository level. Dry runs allow people with owner or admin access to review and hone their patterns before publishing them and generating alerts. You can compose a pattern, then use **Save and dry run** to retrieve results. The scans typically take just a few seconds, but GitHub Enterprise Server will also notify organization owners or repository admins via email when dry run results are ready. For more information, see "[About secret scanning](/code-security/secret-scanning/about-secret-scanning#about-secret-scanning-for-private-repositories)" and "[Defining custom patterns for secret scanning](/code-security/secret-scanning/defining-custom-patterns-for-secret-scanning)." - - - heading: Secret scanning custom pattern events now in the audit log - notes: - # https://github.com/github/releases/issues/2154 - - | - The audit log now includes events associated with secret scanning custom patterns. This data helps GitHub Advanced Security customers understand actions taken on their [repository](/organizations/keeping-your-organization-secure/managing-security-settings-for-your-organization/reviewing-the-audit-log-for-your-organization#repository_secret_scanning_custom_pattern-category-actions)-, [organization](/organizations/keeping-your-organization-secure/managing-security-settings-for-your-organization/reviewing-the-audit-log-for-your-organization#org_secret_scanning_custom_pattern-category-actions)-, or [enterprise](/admin/monitoring-activity-in-your-enterprise/reviewing-audit-logs-for-your-enterprise/audit-log-events-for-your-enterprise#business_secret_scanning_custom_pattern-category-actions)-level custom patterns for security and compliance audits. For more information, see "[Reviewing the audit log for your organization](/organizations/keeping-your-organization-secure/managing-security-settings-for-your-organization/reviewing-the-audit-log-for-your-organization)" or "[Reviewing audit logs for your enterprise](/admin/monitoring-activity-in-your-enterprise/reviewing-audit-logs-for-your-enterprise)." - - - heading: Configure permissions for secret scanning with custom repository roles - notes: - # https://github.com/github/releases/issues/1909 - - | - You can now configure two new permissions for secret scanning when managing custom repository roles. - - - View secret scanning results - - Dismiss or reopen secret scanning results - - For more information, see "[Managing custom repository roles for an organization](/organizations/managing-peoples-access-to-your-organization-with-roles/managing-custom-repository-roles-for-an-organization)." - - - heading: Secret scanning now supports archived repositories - notes: - # https://github.com/github/releases/issues/2076 - - | - GitHub Advanced Security customers can now enable secret scanning for archived repositories via the UI and API. For more information, see "[About secret scanning](/code-security/secret-scanning/about-secret-scanning#about-secret-scanning-for-private-repositories)," "[About archived repositories](/repositories/archiving-a-github-repository/archiving-repositories)," and "[Repositories](/rest/repos/repos#update-a-repository)" in the REST API documentation. - - - heading: Secret scanning webhooks for alert locations - notes: - # https://github.com/github/releases/issues/2149 - - | - GitHub Advanced Security customers using secret scanning can now opt to receive a webhook each time a secret is detected in a new location. The `secret_scanning_alert_location` webhook event includes location details, like the commit SHA, and the associated alert for the detection. A location is created for every new file path containing the detected secret. For more information, see "[Webhook events and payloads](/developers/webhooks-and-events/webhooks/webhook-events-and-payloads#secret_scanning_alert_location)." - - - heading: View Dependabot alerts across an organization - notes: - # https://github.com/github/releases/issues/1992 - - | - GitHub Advanced Security customers can now view Dependabot alerts in in an organization's **Security** tab. This view is available to organization owners and members of teams with the [security manager role](/organizations/managing-peoples-access-to-your-organization-with-roles/managing-security-managers-in-your-organization). For more information, see "[About the security overview](/code-security/security-overview/about-the-security-overview)." - - - heading: Configure permissions for Dependabot alerts with custom repository roles - notes: - # https://github.com/github/releases/issues/1958 - - | - You can now configure two new permissions for Dependabot alerts when managing custom repository roles. - - - View Dependabot alerts - - Dismiss or reopen Dependabot alerts - - For more information, see "[Managing custom repository roles for an organization](/organizations/managing-peoples-access-to-your-organization-with-roles/managing-custom-repository-roles-for-an-organization)." - - - heading: Reopen dismissed Dependabot alerts - notes: - # https://github.com/github/releases/issues/1923 - - | - You can now reopen dismissed Dependabot alerts through the UI page for a closed alert. This does not affect Dependabot pull requests or the GraphQL API. For more information, see "[About Dependabot alerts](/code-security/dependabot/dependabot-alerts/about-dependabot-alerts)." - - - heading: Pub support for Dependabot version updates is in public beta - notes: - # https://github.com/github/releases/issues/2086 - - | - Users of Dependabot version updates can now proactively update dependencies for Flutter or Dart projects that use the Pub package manager. - - To test [version updates](/code-security/dependabot/dependabot-version-updates/about-dependabot-version-updates) on your own Dart or Flutter repository, add the following configuration file in [.github/dependabot.yaml](/code-security/dependabot/dependabot-version-updates/configuring-dependabot-version-updates#enabling-dependabot-version-updates). Note the `package-ecosystem: "pub"` and `enable-beta-ecosystems: true` flags. - ```yaml - version: 2 - enable-beta-ecosystems: true - updates: - - package-ecosystem: "pub" - directory: "/" - schedule: - interval: "weekly" - ``` - - - heading: See pull request associated with a repository's Dependabot alerts via GraphQL API - notes: - # https://github.com/github/releases/issues/2088 - - | - The new `DependabotUpdate` GraphQL object lets you view information about what happens to your repository's security updates. When GitHub Enterprise Server detects that a dependency in your repository is vulnerable, Dependabot will attempt to open a pull request to update that dependency to a non-vulnerable version. You can now see the pull request that fixes the vulnerability. In some cases, Dependabot fails to open a pull request. Previously, the error message that Dependabot generated was only visible in the "Dependabot Alerts" section of the **Security** tab. Now, if Dependabot runs into an error when trying to open a pull request for a security alert, you can determine the reason using the GraphQL API. For more information, see "[Objects](/graphql/reference/objects#dependabotupdate)" in the GraphQL API documentation. - - - heading: Access more information about Dependabot alerts via GraphQL API - notes: - # https://github.com/github/releases/issues/1922 - - | - You can now view fixed alerts from Dependabot with the GraphQL API. You can also access and filter by state, as well as by unique numeric identifier, and you can filter by state on the vulnerability alert object. The following fields now exist for a `RepositoryVulnerabilityAlert`. - - - `number` - - `fixed_at` - - `fix_reason` - - `state` - - For more information, see "[Objects](/graphql/reference/objects#repositoryvulnerabilityalert)" in the GraphQL API documentation. - - - heading: Git events in the enterprise audit log - notes: - # https://github.com/github/releases/issues/2205 - - | - The following Git-related events can now appear in the enterprise audit log. If you enable the feature and set an audit log retention period, the new events will be available for search via the UI and API, or export via JSON or CSV. - - - `git.clone` - - `git.fetch` - - `git.push` - - Due to the large number of Git events logged, we recommend you monitor your instance's file storage and review your related alert configurations. For more information, see "[Configuring the audit log for your enterprise](/admin/monitoring-activity-in-your-enterprise/reviewing-audit-logs-for-your-enterprise/configuring-the-audit-log-for-your-enterprise#managing-git-events-in-the-audit-log)." - - - heading: Improvements to CODEOWNERS - notes: - # https://github.com/github/releases/issues/1994 - - | - This release includes improvements to CODEOWNERS. - - - Syntax errors are now surfaced when viewing a CODEOWNERS file from the web. Previously, when a line in a CODEOWNERS file had a syntax error, the error would be ignored or in some cases cause the entire CODEOWNERS file to not load. GitHub Apps and Actions can access the same list of errors using new REST and GraphQL APIs. For more information, see "[Repositories](/rest/repos/repos#list-codeowners-errors)" in the REST API documentation or "[Objects](/graphql/reference/objects#repositorycodeowners)" in the GraphQL API documentation. - - After someone creates a new pull request or pushes new changes to a draft pull request, any code owners that will be requested for review are now listed in the pull request under "Reviewers". This feature gives you an early look at who will be requested to review once the pull request is marked ready for review. - - Comments in CODEOWNERS files can now appear at the end of a line, not just on dedicated lines. - - For more information, see "[About code owners](/repositories/managing-your-repositorys-settings-and-features/customizing-your-repository/about-code-owners)." - - - heading: More ways to keep a pull request's topic branch up to date - notes: - # https://github.com/github/releases/issues/1566 - - | - The **Update branch** button on the pull request page lets you update your pull request's branch with the latest changes from the base branch. This is useful for verifying your changes are compatible with the current version of the base branch before you merge. Two enhancements now give you more ways to keep your branch up-to-date. - - - When your pull request's topic branch is out of date with the base branch, you now have the option to update it by rebasing on the latest version of the base branch. Rebasing applies the changes from your branch onto the latest version of the base branch, resulting in a branch with a linear history since no merge commit is created. To update by rebasing, click the drop down menu next to the **Update Branch** button, click **Update with rebase**, and then click **Rebase branch**. Previously, **Update branch** performed a traditional merge that always resulted in a merge commit in your pull request branch. This option is still available, but now you have the choice. For more information, see "[Keeping your pull request in sync with the base branch](/pull-requests/collaborating-with-pull-requests/proposing-changes-to-your-work-with-pull-requests/keeping-your-pull-request-in-sync-with-the-base-branch)." - - - A new repository setting allows the **Update branch** button to always be available when a pull request's topic branch is not up to date with the base branch. Previously, this button was only available when the **Require branches to be up to date before merging** branch protection setting was enabled. People with admin or maintainer access can manage the **Always suggest updating pull request branches** setting from the **Pull Requests** section in repository settings. For more information, see "[Managing suggestions to update pull request branches](/repositories/configuring-branches-and-merges-in-your-repository/configuring-pull-request-merges/managing-suggestions-to-update-pull-request-branches)." - - - heading: Configure custom HTTP headers for GitHub Pages sites - notes: - # https://github.com/github/releases/issues/2124 - - | - You can now configure custom HTTP headers that apply to all GitHub Pages sites served from your GitHub Enterprise Server instance. For more information, see "[Configuring GitHub Pages for your enterprise](/admin/configuration/configuring-your-enterprise/configuring-github-pages-for-your-enterprise#configuring-github-pages-response-headers-for-your-enterprise)." - - - heading: Ignore commits in blame view - notes: - # https://github.com/github/releases/issues/2090 - - | - It's now possible to ignore revisions in the blame view by creating a _.git-blame-ignore-revs_ file in the root of your repository. For more information, see "[Viewing a file](/repositories/working-with-files/using-files/viewing-a-file#ignore-commits-in-the-blame-view)." - - - heading: Light high contrast theme is generally available - notes: - # https://github.com/github/releases/issues/2011 - - | - A light high contrast theme, with greater contrast between foreground and background elements, is now generally available. For more information, see "[Managing your theme settings](/account-and-profile/setting-up-and-managing-your-github-user-account/managing-user-account-settings/managing-your-theme-settings)." - - - heading: Tag protection rules - notes: - # https://github.com/github/releases/issues/1793 - - | - Repository owners can now configure tag protection rules to protect a repository's tags. Once protected by a tag protection rule, tags matching a specified name pattern can only be created and deleted by users with the Maintain or Admin role in the repository. For more information, see "[Configuring tag protection rules](/repositories/managing-your-repositorys-settings-and-features/managing-repository-settings/configuring-tag-protection-rules)." - - bugs: - # https://github.com/github/releases/issues/1934 - - | - It is now possible for GitHub Apps to upload release assets. - - changes: - # https://github.com/github/releases/issues/2063 - - | - To use the device authorization flow for OAuth and GitHub Apps, you must manually enable the feature. This change reduces the likelihood of apps being used in phishing attacks against GitHub Enterprise Server users by ensuring integrators are aware of the risks and make a conscious choice to support this form of authentication. If you own or manage an OAuth App or GitHub App and you want to use the device flow, you can enable it for your app via the app's settings page. The device flow API endpoints will respond with status code `400` to apps that have not enabled this feature. For more information, see "[Authorizing OAuth Apps](/developers/apps/building-oauth-apps/authorizing-oauth-apps#device-flow)." - - # https://github.com/github/releases/issues/2049 - - | - The code scanning alert page now always shows the alert status and information for the default branch. There is a new "Affected branches" panel in the sidebar where you can see the status of the alert in other branches. If the alert does not exist in your default branch, the alert page will show the status as "In branch" or "In pull request" for the location where the alert was last seen. This improvement makes it easier to understand the status of alerts which have been introduced into your code base. For more information, see "[About code scanning alerts](/code-security/code-scanning/automatically-scanning-your-code-for-vulnerabilities-and-errors/about-code-scanning-alerts#about-alert-details)." - - The alert list page is not changed and can be filtered by `branch`. You can use the code scanning API to retrieve more detailed branch information for alerts. For more information, see "[Code Scanning](/rest/code-scanning)" in the REST API documentation. - - # https://github.com/github/releases/issues/2050 - - | - Code scanning now shows the details of the analysis origin of an alert. If an alert has more than one analysis origin, it is shown in the "Affected branches" sidebar and in the alert timeline. You can hover over the analysis origin icon in the "Affected branches" sidebar to see the alert status in each analysis origin. If an alert only has a single analysis origin, no information about analysis origins is displayed on the alert page. These improvements will make it easier to understand your alerts. In particular, it will help you understand those that have multiple analysis origins. This is especially useful for setups with multiple analysis configurations, such as monorepos. For more information, see "[About code scanning alerts](/code-security/code-scanning/automatically-scanning-your-code-for-vulnerabilities-and-errors/about-code-scanning-alerts#about-analysis-origins)." - - # https://github.com/github/releases/issues/2071 - - | - Lists of repositories owned by a user or organization now have an additional filter option, "Templates", making it easier to find template repositories. - - # https://github.com/github/releases/issues/1947 - - | - GitHub Enterprise Server can display several common image formats, including PNG, JPG, GIF, PSD, and SVG, and provides several ways to compare differences between versions. Now when reviewing added or changed images in a pull request, previews of those images are shown by default. Previously, you would see a message indicating that binary files could not be shown and you would need to toggle the "Display rich diff" option. For more information, see "[Working with non-code files](/repositories/working-with-files/using-files/working-with-non-code-files)." - - # https://github.com/github/releases/issues/2054 - - | - New gists are now created with a default branch name of either `main` or the alternative default branch name defined in your user settings. This matches how other repositories are created on GitHub Enterprise Server. For more information, see "[About branches](/pull-requests/collaborating-with-pull-requests/proposing-changes-to-your-work-with-pull-requests/about-branches#about-the-default-branch)" and "[Managing the default branch name for your repositories](/account-and-profile/setting-up-and-managing-your-personal-account-on-github/managing-personal-account-settings/managing-the-default-branch-name-for-your-repositories)." - - # https://github.com/github/releases/issues/2028 - - | - Gists now only show the 30 most recent comments when first displayed. You can click **Load earlier comments...** to view more. This allows gists that have many comments to appear more quickly. For more information, see "[Editing and sharing content with gists](/get-started/writing-on-github/editing-and-sharing-content-with-gists)." - - # https://github.com/github/releases/issues/2036 - - | - Settings pages for users, organizations, repositories, and teams have been redesigned, grouping similar settings pages into sections for improved information architecture and discoverability. For more information, see the [GitHub changelog](https://github.blog/changelog/2022-02-02-redesign-of-githubs-settings-pages/). - - # https://github.com/github/releases/issues/2129 - - | - Focusing or hovering over a label now displays the label description in a tooltip. - - # https://github.com/github/releases/issues/1983 - - | - Creating and removing repository invitations, whether done through the API or web interface, are now subject to rate limits that may be enabled on your GitHub Enterprise Server instance. For more information about rate limits, see "[Configuring rate limits](/admin/configuration/configuring-your-enterprise/configuring-rate-limits)." - - # https://github.com/github/releases/issues/2291 - - | - MinIO has announced the removal of the MinIO Gateways starting June 1st, 2022. While MinIO Gateway for NAS continues to be one of the supported storage providers for Github Actions and Github Packages, we recommend moving to MinIO LTS support to avail support and bug fixes from MinIO. For more information about rate limits, see "[Scheduled removal of MinIO Gateway for GCS, Azure, HDFS in the minio/minio repository](https://github.com/minio/minio/issues/14331)." - - - deprecations: - - heading: Change to the format of authentication tokens - notes: - # https://github.com/github/releases/issues/1235 - - | - GitHub Connect will no longer work after June 3rd for instances running GitHub Enterprise Server 3.1 or older, due to the format of GitHub authentication tokens changing. For more information, see the [GitHub changelog](https://github.blog/changelog/2021-03-31-authentication-token-format-updates-are-generally-available/). - - - heading: CodeQL runner deprecated in favor of CodeQL CLI - notes: - # https://github.com/github/releases/issues/1632 - - | - The CodeQL runner is deprecated in favor of the CodeQL CLI. GitHub Enterprise Server 3.4 and later no longer include the CodeQL runner. This deprecation only affects users who use CodeQL code scanning in 3rd party CI/CD systems. GitHub Actions users are not affected. GitHub strongly recommends that customers migrate to the CodeQL CLI, which is a feature-complete replacement for the CodeQL runner and has many additional features. For more information, see "[Migrating from the CodeQL runner to CodeQL CLI](/code-security/code-scanning/using-codeql-code-scanning-with-your-existing-ci-system/migrating-from-the-codeql-runner-to-codeql-cli)." - - - heading: Theme picker for GitHub Pages has been removed - notes: - - | - The theme picker for GitHub Pages has been removed from the Pages settings. For more information about configuration of themes for GitHub Pages, see "[Adding a theme to your GitHub Pages site using Jekyll](/pages/setting-up-a-github-pages-site-with-jekyll/adding-a-theme-to-your-github-pages-site-using-jekyll)." - - 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. + \ No newline at end of file diff --git a/translations/zh-CN/data/release-notes/enterprise-server/3-5/5.yml b/translations/zh-CN/data/release-notes/enterprise-server/3-5/5.yml index b7f41bbb96d1..574ca6eccab2 100644 --- a/translations/zh-CN/data/release-notes/enterprise-server/3-5/5.yml +++ b/translations/zh-CN/data/release-notes/enterprise-server/3-5/5.yml @@ -19,7 +19,7 @@ sections: known_issues: - "在新建的没有任何用户的 {% data variables.product.prodname_ghe_server %} 实例上，攻击者可以创建第一个管理员用户。" - 自定义防火墙规则在升级过程中被删除。 - - "[通过 Web 界面上传](https://github.com/blog/2105-upload-files-to-your-repositories)的 Git LFS 跟踪文件被错误地直接添加到存储库。" + - "[通过 Web 界面上传](https://github.com/blog/2105-upload-files-to-your-repositories) 的 Git LFS 跟踪文件被错误地直接添加到存储库。" - 如果问题包含指向同一存储库中 Blob 的永久链接，且 Blob 的文件路径长度超过 255 个字符，则无法关闭问题。 - 在 GitHub Connect 中启用了“用户可以搜索 GitHub.com”时，专用和内部存储库中的问题不包括在 GitHub.com 搜索结果中。 - "{% data variables.product.prodname_registry %} npm 注册表不再在元数据响应中返回时间值。这样可以大幅改善性能。作为元数据响应的一部分，我们继续拥有返回时间值所需的所有数据，并将在我们解决现有性能问题后恢复返回这个值。" diff --git a/translations/zh-CN/data/release-notes/enterprise-server/3-6/0-rc1.yml b/translations/zh-CN/data/release-notes/enterprise-server/3-6/0-rc1.yml index fc7707911bf8..48a383dff8a7 100644 --- a/translations/zh-CN/data/release-notes/enterprise-server/3-6/0-rc1.yml +++ b/translations/zh-CN/data/release-notes/enterprise-server/3-6/0-rc1.yml @@ -107,192 +107,4 @@ sections: # https://github.com/github/releases/issues/2160 - | - Users can select multiple Dependabot alerts, then dismiss or reopen or dismiss the alerts. For example, from the **Closed alerts** tab, you can select multiple alerts that have been previously dismissed, and then reopen them all at once. For more information, see "[About Dependabot alerts](/code-security/supply-chain-security/managing-vulnerabilities-in-your-projects-dependencies/about-alerts-for-vulnerable-dependencies)." - - # https://github.com/github/releases/issues/2232 - - | - Dependabot updates `@types` dependencies alongside corresponding packages in TypeScript projects. Before this change, users would see separate pull requests for a package and the corresponding `@types` package. This feature is automatically enabled for repositories containing `@types` packages in the project's `devDependencies` within the _package.json_ file. You can disable this behavior by setting the [`ignore`](/code-security/dependabot/dependabot-version-updates/configuration-options-for-the-dependabot.yml-file#ignore) field in your `dependabot.yml` file to `@types/*`. For more information, see "[About Dependabot version updates](/code-security/dependabot/dependabot-version-updates/about-dependabot-version-updates)" and "[Configuration options for the _dependabot.yml_ file](/code-security/dependabot/dependabot-version-updates/configuration-options-for-the-dependabot.yml-file)." - - - heading: Code security - notes: - # https://github.com/github/releases/issues/2098 - # https://github.com/github/releases/issues/2282 - - | - GitHub Actions can enforce dependency reviews on users' pull requests by scanning for dependencies, and will warn users about associated security vulnerabilities. The `dependency-review-action` action is supported by a new API endpoint that diffs the dependencies between any two revisions. For more information, see "[About dependency review](/code-security/supply-chain-security/understanding-your-software-supply-chain/about-dependency-review#dependency-review-enforcement)." - - # https://github.com/github/releases/issues/2243 - - | - The dependency graph detects _Cargo.toml_ and _Cargo.lock_ files for Rust. These files will be displayed in the **Dependency graph** section of the **Insights** tab. Users will receive Dependabot alerts and updates for vulnerabilities associated with their Rust dependencies. Package metadata, including mapping packages to repositories, will be added at a later date. For more information, see "[About the dependency graph](/code-security/supply-chain-security/understanding-your-software-supply-chain/about-the-dependency-graph)." - - # https://github.com/github/releases/issues/1766 - - | - If GitHub Connect is enabled for your instance, users can contribute an improvement to a security advisory in the [GitHub Advisory Database](https://github.com/advisories). To contribute, click **Suggest improvements for this vulnerability** while viewing an advisory's details. For more information, see the following articles. - - - "[Managing GitHub Connect](/admin/configuration/configuring-github-connect/managing-github-connect)" - - "[Browsing security vulnerabilities in the GitHub Advisory Database](/enterprise-cloud@latest/code-security/supply-chain-security/managing-vulnerabilities-in-your-projects-dependencies/browsing-security-vulnerabilities-in-the-github-advisory-database)" in the GitHub Enterprise Cloud documentation - - "[About GitHub Security Advisories for repositories](/enterprise-cloud@latest/code-security/repository-security-advisories/about-github-security-advisories-for-repositories)" in the GitHub Enterprise Cloud documentation - - "[Editing security advisories in the GitHub Advisory Database](/enterprise-cloud@latest/code-security/supply-chain-security/managing-vulnerabilities-in-your-projects-dependencies/editing-security-advisories-in-the-github-advisory-database)" in the GitHub Enterprise Cloud documentation - - - heading: GitHub Actions - notes: - # https://github.com/github/releases/issues/2159 - - | - Within a workflow that calls a reusable workflow, users can pass the secrets to the reusable workflow with `secrets: inherit`. For more information, see "[Reusing workflows](/actions/using-workflows/reusing-workflows#using-inputs-and-secrets-in-a-reusable-workflow)." - - # https://github.com/github/releases/issues/2102 - - | - When using GitHub Actions, to reduce the risk of merging a change that was not reviewed by another person into a protected branch, enterprise owners and repository administrators can prevent Actions from creating pull requests. Organization owners could previously enable this restriction. For more information, see the following articles. - - - "[Enforcing policies for GitHub Actions in your enterprise](/admin/policies/enforcing-policies-for-your-enterprise/enforcing-policies-for-github-actions-in-your-enterprise#preventing-github-actions-from-creating-or-approving-pull-requests)" - - "[Disabling or limiting GitHub Actions for your organization](/organizations/managing-organization-settings/disabling-or-limiting-github-actions-for-your-organization#preventing-github-actions-from-creating-or-approving-pull-requests)" - - "[Managing GitHub Actions settings for a repository](/repositories/managing-your-repositorys-settings-and-features/enabling-features-for-your-repository/managing-github-actions-settings-for-a-repository#preventing-github-actions-from-creating-or-approving-pull-requests)" - - # https://github.com/github/releases/issues/2155 - - | - Users can write a single workflow triggered by `workflow_dispatch` and `workflow_call`, and use the `inputs` context to access input values. Previously, `workflow_dispatch` inputs were in the event payload, which increased difficulty for workflow authors who wanted to write one workflow that was both reusable and manually triggered. For workflows triggered by `workflow_dispatch`, inputs are still available in the `github.event.inputs` context to maintain compatibility. For more information, see "[Contexts](/actions/learn-github-actions/contexts#inputs-context)." - - # https://github.com/github/releases/issues/2103 - - | - To summarize the result of a job, users can generate Markdown and publish the contents as a job summary. For example, after running tests with GitHub Actions, a summary can provide an overview of passed, failed, or skipped tests, potentially reducing the need to review the full log output. For more information, see "[Workflow commands for GitHub Actions](/actions/using-workflows/workflow-commands-for-github-actions#adding-a-job-summary)." - - # https://github.com/github/releases/issues/2161 - - | - To more easily diagnose job execution failures during a workflow re-run, users can enable debug logging, which outputs information about a job's execution and environment. For more information, see "[Re-running workflows and jobs](/actions/managing-workflow-runs/re-running-workflows-and-jobs)" and "[Using workflow run logs](/actions/monitoring-and-troubleshooting-workflows/using-workflow-run-logs#viewing-logs-to-diagnose-failures)." - - # https://github.com/github/releases/issues/2140 - - | - If you manage self-hosted runners for GitHub Actions, you can ensure a consistent state on the runner itself before and after a workflow run by defining scripts to execute. By using scripts, you no longer need to require that users manually incorporate these steps into workflows. Pre- and post-job scripts are in beta and subject to change. For more information, see "[Running scripts before or after a job](/actions/hosting-your-own-runners/running-scripts-before-or-after-a-job)." - - - heading: GitHub Packages - notes: - # https://github.com/github/releases/issues/2334 - - | - Enterprise owners can migrate container images from the GitHub Docker registry to the GitHub Container registry. The Container registry provides the following benefits. - - - Improves the sharing of containers within an organization - - Allows the application of granular access permissions - - Permits the anonymous sharing of public container images - - Implements OCI standards for hosting Docker images - - The Container registry is in beta and subject to change. For more information, see "[Migrating your enterprise to the Container registry from the Docker registry](/admin/packages/migrating-your-enterprise-to-the-container-registry-from-the-docker-registry)." - - - heading: Community experience - notes: - # https://github.com/github/releases/issues/2113 - - | - GitHub Discussions is available for GitHub Enterprise Server. GitHub Discussions provides a central gathering space to ask questions, share ideas, and build connections. For more information, see "[GitHub Discussions](/discussions)." - - # https://github.com/github/releases/issues/2259 - - | - Enterprise owners can configure a policy to control whether people's usernames or full names are displayed within internal or public repositories. For more information, see "[Enforcing repository management policies in your enterprise](/admin/policies/enforcing-policies-for-your-enterprise/enforcing-repository-management-policies-in-your-enterprise#enforcing-a-policy-for-the-display-of-member-names-in-your-repositories)." - - - heading: Organizations - notes: - # https://github.com/github/releases/issues/2019 - - | - Users can create member-only READMEs for an organization. For more information, see "[Customizing your organization's profile](/organizations/collaborating-with-groups-in-organizations/customizing-your-organizations-profile)." - - # https://github.com/github/releases/issues/2234 - - | - Organization owners can pin a repository to an organization's profile directly from the repository via the new **Pin repository** dropdown. Pinned public repositories appear to all users of your instance, while public, private, and internal repositories are only visible to organization members. - - - heading: Repositories - notes: - # https://github.com/github/releases/issues/2214 - - | - While creating a fork, users can customize the fork's name. For more information, see "[Fork a repo](/get-started/quickstart/fork-a-repo)." - - # https://github.com/github/releases/issues/1973 - - | - Users can block creation of branches that match a configured name pattern with the **Restrict pushes that create matching branches** branch protection rule. For example, if a repository's default branch changes from `master` to `main`, a repository administrator can prevent any subsequent creation or push of the `master` branch. For more information, see - "[About protected branches](/repositories/configuring-branches-and-merges-in-your-repository/defining-the-mergeability-of-pull-requests/about-protected-branches#restrict-who-can-push-to-matching-branches)" and "[Managing a branch protection rule](/repositories/configuring-branches-and-merges-in-your-repository/defining-the-mergeability-of-pull-requests/managing-a-branch-protection-rule#creating-a-branch-protection-rule)." - - # https://github.com/github/releases/issues/2179 - - | - Users can create a branch directly from a repository's **Branches** page by clicking the **New branch**. For more information, see "[Creating and deleting branches within your repository](/pull-requests/collaborating-with-pull-requests/proposing-changes-to-your-work-with-pull-requests/creating-and-deleting-branches-within-your-repository)." - - # https://github.com/github/releases/issues/2220 - - | - Users can delete a branch that's associated with an open pull request. For more information, see "[Creating and deleting branches within your repository](/pull-requests/collaborating-with-pull-requests/proposing-changes-to-your-work-with-pull-requests/creating-and-deleting-branches-within-your-repository)." - - # https://github.com/github/releases/issues/2118 - - | - Repositories with multiple licenses display all of the licenses in the "About" sidebar on the {% octicon "code" aria-label="The code icon" %} **Code** tab. For more information, see "[Licensing a repository](/repositories/managing-your-repositorys-settings-and-features/customizing-your-repository/licensing-a-repository)." - - # https://github.com/github/releases/issues/2233 - - When a user renames or moves a file to a new directory, if at least half of the file's contents are identical, the commit history indicates that the file was renamed, similar to `git log --follow`. For more information, see the [GitHub Blog](https://github.blog/changelog/2022-06-06-view-commit-history-across-file-renames-and-moves/). - - # https://github.com/github/releases/issues/2093 - - | - Users can require a successful deployment of a branch before anyone can merge the pull request associated with the branch. For more information, see "[About protected branches](/repositories/configuring-branches-and-merges-in-your-repository/defining-the-mergeability-of-pull-requests/about-protected-branches#require-deployments-to-succeed-before-merging)" and "[Managing a branch protection rule](/repositories/configuring-branches-and-merges-in-your-repository/defining-the-mergeability-of-pull-requests/managing-a-branch-protection-rule)." - - # https://github.com/github/releases/issues/2073 - - | - Enterprise owners can prevent organization owners from inviting collaborators to repositories on the instance. For more information, see "[Enforcing a policy for inviting collaborators to repositories](/admin/policies/enforcing-policies-for-your-enterprise/enforcing-repository-management-policies-in-your-enterprise#enforcing-a-policy-for-inviting-collaborators-to-repositories)." - - # https://github.com/github/releases/issues/2173 - - | - Users can grant exceptions to GitHub Apps for any branch protection rule that supports exceptions. For more information, see "[About apps](/developers/apps/getting-started-with-apps/about-apps)" and "[Managing a branch protection rule](/repositories/configuring-branches-and-merges-in-your-repository/defining-the-mergeability-of-pull-requests/managing-a-branch-protection-rule)." - - - heading: Commits - notes: - # https://github.com/github/releases/issues/2306 - - | - For public GPG signing keys that are expired or revoked, GitHub Enterprise Server verifies Git commit signatures and show commits as verified if the user made the commit while the key was still valid. Users can also upload expired or revoked GPG keys. For more information, see "[About commit signature verification](/authentication/managing-commit-signature-verification/about-commit-signature-verification)." - - # https://github.com/github/releases/issues/1977 - - | - To affirm that a commit complies with the rules and licensing governing a repository, organization owners and repository administrators can now require developers to sign off on commits made through the web interface. For more information, see "[Managing the commit signoff policy for your organization](/organizations/managing-organization-settings/managing-the-commit-signoff-policy-for-your-organization)" and "[Managing the commit signoff policy for your repository](/repositories/managing-your-repositorys-settings-and-features/managing-repository-settings/managing-the-commit-signoff-policy-for-your-repository)." - - - heading: Pull requests - notes: - # https://github.com/github/releases/issues/2261 - - | - Using the file tree located in the **Files changed** tab of a pull request, users can navigate modified files, understand the size and scope of changes, and focus reviews. The file tree appears if a pull request modifies at least two files, and the browser window is sufficiently wide. For more information, see "[Reviewing proposed changes in a pull request](/pull-requests/collaborating-with-pull-requests/reviewing-changes-in-pull-requests/reviewing-proposed-changes-in-a-pull-request)" and "[Filtering files in a pull request](/pull-requests/collaborating-with-pull-requests/reviewing-changes-in-pull-requests/filtering-files-in-a-pull-request)." - - # https://github.com/github/releases/issues/2167 - - | - Users can default to using pull requests titles as the commit message for all squash merges. For more information, see "[Configuring commit squashing for pull requests](/repositories/configuring-branches-and-merges-in-your-repository/configuring-pull-request-merges/configuring-commit-squashing-for-pull-requests)." - - - heading: Releases - notes: - # https://github.com/github/releases/issues/2281 - - | - When viewing the details for a particular release, users can see the creation date for each release asset. For more information, see "[Viewing your repository's releases and tags](/repositories/releasing-projects-on-github/viewing-your-repositorys-releases-and-tags)." - - # https://github.com/github/releases/issues/2279 - - While creating a release with automatically generated release notes, users can see the tag identified as the previous release, then choose to select a different tag to specify as the previous release. For more information, see "[Automatically generated release notes](/repositories/releasing-projects-on-github/automatically-generated-release-notes)." - - - heading: Markdown - notes: - # https://github.com/github/releases/issues/2260 - - | - Editing Markdown in the web interface has been improved. - - - After a user selects text and pastes a URL, the selected text will become a Markdown link to the pasted URL. - - When a user pastes spreadsheet cells or HTML tables, the resulting text will render as a table. - - When a user copies text containing links, the pasted text will include the link as a Markdown link. - - For more information, see "[Basic writing and formatting syntax](/get-started/writing-on-github/getting-started-with-writing-and-formatting-on-github/basic-writing-and-formatting-syntax#links)." - - # https://github.com/github/releases/issues/2258 - - | - When editing a Markdown file in the web interface, clicking the **Preview** tab will automatically scroll to the place in the preview that you were editing. The scroll location is based on the position of your cursor before you clicked the **Preview** tab. - - changes: - - Interactive elements in the web interface such as links and buttons show a visible outline when focused with a keyboard, to help users find the current position on a page. In addition, when focused, form fields have a higher contrast outline. - - If a user refreshes the page while creating a new issue or pull request, the assignees, reviewers, labels and projects will all be preserved. - - 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 instance from a backup taken on a different host. - - 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 + Users can select multiple Dependabot alerts, then dismiss or reopen or dismiss the alerts. For example, from the **Closed alerts** tab, you can select multiple alerts that have been previously dismissed, and then reopen them all at once. For more information, see "[About Dependabot alerts](/code-security/supply-chain-security/managing-vulnerabilities-in-your-projects-dependencies/about-alerts-for-vulnerable-depen \ No newline at end of file diff --git a/translations/zh-CN/data/release-notes/enterprise-server/3-6/1.yml b/translations/zh-CN/data/release-notes/enterprise-server/3-6/1.yml index 8ec4162b8792..ae2b80b8ccf5 100644 --- a/translations/zh-CN/data/release-notes/enterprise-server/3-6/1.yml +++ b/translations/zh-CN/data/release-notes/enterprise-server/3-6/1.yml @@ -22,7 +22,7 @@ sections: known_issues: - "在新建的没有任何用户的 {% data variables.product.prodname_ghe_server %} 实例上，攻击者可以创建第一个管理员用户。" - 自定义防火墙规则在升级过程中被删除。 - - "[通过 Web 界面上传](https://github.com/blog/2105-upload-files-to-your-repositories)的 Git LFS 跟踪文件被错误地直接添加到存储库。" + - "[通过 Web 界面上传](https://github.com/blog/2105-upload-files-to-your-repositories) 的 Git LFS 跟踪文件被错误地直接添加到存储库。" - 如果问题包含指向同一存储库中 Blob 的永久链接，且 Blob 的文件路径长度超过 255 个字符，则无法关闭问题。 - 在 GitHub Connect 中启用了“用户可以搜索 GitHub.com”时，专用和内部存储库中的问题不包括在 GitHub.com 搜索结果中。 - "{% data variables.product.prodname_registry %} npm 注册表不再在元数据响应中返回时间值。这样可以大幅改善性能。作为元数据响应的一部分，我们继续拥有返回时间值所需的所有数据，并将在我们解决现有性能问题后恢复返回这个值。" diff --git a/translations/zh-CN/data/release-notes/enterprise-server/README.md b/translations/zh-CN/data/release-notes/enterprise-server/README.md index 9c71ddaabb25..716586639068 100644 --- a/translations/zh-CN/data/release-notes/enterprise-server/README.md +++ b/translations/zh-CN/data/release-notes/enterprise-server/README.md @@ -8,13 +8,13 @@ ms.locfileid: "145098647" --- # GitHub Enterprise Server 发行说明 -已呈现在此处： https://docs.github.com/en/enterprise-server@latest/admin/release-notes +已呈现在此处：https://docs.github.com/en/enterprise-server@latest/admin/release-notes ## 工作原理 ### 占位符内容文件 -内容文件存在于 `content/admin/release-notes.md` 中。 它有一个特殊的前辅文属性 `layout: release-notes`，无 Markdown 内容。 发行说明的来源来自 YAML 数据。 +内容文件存在于 `content/admin/release-notes.md` 中。它有一个特殊的前辅文属性 `layout: release-notes`，无 Markdown 内容。发行说明的来源来自 YAML 数据。 ### YAML 来源 @@ -22,7 +22,7 @@ ms.locfileid: "145098647" 目录按 GHES 版本编号命名（带有连字符而不是句点）。 -每个目录中的 YAML 文件按补丁编号命名。 某些修补程序文件名可能以 `-rc.yml` 结尾，这表示它是候选发布。 候选发布文件还需要 YAML 数据中的 `release_candidate: true`。 +每个目录中的 YAML 文件按补丁编号命名。某些修补程序文件名可能以 `-rc.yml` 结尾，这表示它是候选发布。候选发布文件还需要 YAML 数据中的 `release_candidate: true`。 已弃用的 GHES 版本的发行说明（参见 `lib/enterprise-server-releases.js`）不会从网站删除，并且将始终与当前支持的版本一起显示。 @@ -40,6 +40,6 @@ YAML 数据由 `middleware/contextualizers/release-notes.js` 处理和排序， ### 架构 -验证 YAML 数据的架构存在于 `tests/helpers/schemas/ghes-release-notes-schema.js` 中。 查看架构文件来了解必需和可选的属性。 +验证 YAML 数据的架构存在于 `tests/helpers/schemas/ghes-release-notes-schema.js` 中。查看架构文件来了解必需和可选的属性。 -架构在 `tests/linting/lint-files.js` 中执行测试。 如果数据未通过验证，测试将失败。 +架构在 `tests/linting/lint-files.js` 中执行测试。如果数据未通过验证，测试将失败。 diff --git a/translations/zh-CN/data/release-notes/github-ae/README.md b/translations/zh-CN/data/release-notes/github-ae/README.md index 64680ee2283f..76c8620a0f44 100644 --- a/translations/zh-CN/data/release-notes/github-ae/README.md +++ b/translations/zh-CN/data/release-notes/github-ae/README.md @@ -8,21 +8,21 @@ ms.locfileid: "145098643" --- # GitHub AE 版本说明 -已呈现在此处： https://docs.github.com/en/github-ae@latest/admin/release-notes +已呈现在此处：https://docs.github.com/en/github-ae@latest/admin/release-notes ## 工作原理 ### 占位符内容文件 -内容文件存在于 `content/admin/release-notes.md` 中。 它有一个特殊的前辅文属性 `layout: release-notes`，无 Markdown 内容。 发行说明的来源来自 YAML 数据。 +内容文件存在于 `content/admin/release-notes.md` 中。它有一个特殊的前辅文属性 `layout: release-notes`，无 Markdown 内容。发行说明的来源来自 YAML 数据。 ### YAML 来源 发行说明的源数据位于此目录 (`data/release-notes/github-ae`) 中。 -目录按月命名。 YAML 文件由每周发布的数据命名。 +目录按月命名。YAML 文件由每周发布的数据命名。 -必须在每个 YAML 文件中设置一个名为 `currentWeek` 的布尔属性。 每次不超过一个文件可将此属性设置为真。 +必须在每个 YAML 文件中设置一个名为 `currentWeek` 的布尔属性。每次不超过一个文件可将此属性设置为真。 请注意，补丁文件可由可选的 `deprecated: true` 属性单独废弃（即在文档网站上隐藏）。 @@ -38,6 +38,6 @@ YAML 数据由 `middleware/contextualizers/release-notes.js` 处理和排序， ### 架构 -验证 YAML 数据的架构存在于 `tests/helpers/schemas/ghae-release-notes-schema.js` 中。 查看架构文件来了解必需和可选的属性。 +验证 YAML 数据的架构存在于 `tests/helpers/schemas/ghae-release-notes-schema.js` 中。查看架构文件来了解必需和可选的属性。 -架构在 `tests/linting/lint-files.js` 中执行测试。 如果数据未通过验证，测试将失败。 +架构在 `tests/linting/lint-files.js` 中执行测试。如果数据未通过验证，测试将失败。