diff --git a/assets/images/help/classroom/student-codespaces-readme-link.png b/assets/images/help/classroom/student-codespaces-readme-link.png index c0b4a6897a..5737208956 100644 Binary files a/assets/images/help/classroom/student-codespaces-readme-link.png and b/assets/images/help/classroom/student-codespaces-readme-link.png differ diff --git a/assets/images/help/classroom/student-launch-new-codespace.png b/assets/images/help/classroom/student-launch-new-codespace.png index 991475bd80..4405cee983 100644 Binary files a/assets/images/help/classroom/student-launch-new-codespace.png and b/assets/images/help/classroom/student-launch-new-codespace.png differ diff --git a/content/education/manage-coursework-with-github-classroom/integrate-github-classroom-with-an-ide/using-github-codespaces-with-github-classroom.md b/content/education/manage-coursework-with-github-classroom/integrate-github-classroom-with-an-ide/using-github-codespaces-with-github-classroom.md index 5485268315..d2d9a09f01 100644 --- a/content/education/manage-coursework-with-github-classroom/integrate-github-classroom-with-an-ide/using-github-codespaces-with-github-classroom.md +++ b/content/education/manage-coursework-with-github-classroom/integrate-github-classroom-with-an-ide/using-github-codespaces-with-github-classroom.md @@ -81,7 +81,7 @@ When a student opens an assignment, the repository's README file includes their ![Screenshot of the Codespaces note in the README for a student assignment repository](/assets/images/help/classroom/student-codespaces-readme-link.png) -Students can launch a new or existing codespace by clicking the **{% octicon "code" aria-label="The code icon" %} Code** button on the main page of the assignment repository, then selecting the **Codespaces** tab. For more information, see "[Creating a codespace](/codespaces/developing-in-codespaces/creating-a-codespace#creating-a-codespace)." +Students can launch a new or existing codespace by clicking the **Open in GitHub Codespace** button in the README, or by clicking the **{% octicon "code" aria-label="The code icon" %} Code** button on the main page of the assignment repository, then selecting the **Codespaces** tab. From the **Codespaces** tab you can select an existing codespace or create a new one. For more information, see "[Creating a codespace](/codespaces/developing-in-codespaces/creating-a-codespace#creating-a-codespace)." ![Launch new codespace in assignment repository](/assets/images/help/classroom/student-launch-new-codespace.png) diff --git a/content/organizations/managing-peoples-access-to-your-organization-with-roles/about-custom-repository-roles.md b/content/organizations/managing-peoples-access-to-your-organization-with-roles/about-custom-repository-roles.md new file mode 100644 index 0000000000..a51c6527c1 --- /dev/null +++ b/content/organizations/managing-peoples-access-to-your-organization-with-roles/about-custom-repository-roles.md @@ -0,0 +1,130 @@ +--- +title: About custom repository roles +intro: You can more granularly control access to your organization's repositories with custom repository roles. +versions: + feature: custom-repository-roles +topics: + - Organizations + - Teams +shortTitle: About custom roles +--- + +{% data reusables.organizations.custom-repo-roles-ghec-only %} + +## About custom repository roles + +To perform any actions on {% data variables.product.product_name %}, such as creating a pull request in a repository or changing an organization's billing settings, a person must have sufficient access to the relevant account or resource. This access is controlled by permissions. A permission is the ability to perform a specific action. For example, the ability to delete an issue is a permission. A role is a set of permissions you can assign to individuals or teams. + +Within an organization, you can assign roles at the organization, team, and repository level. For more information about the different levels of roles, see "[Roles in an organization](/organizations/managing-peoples-access-to-your-organization-with-roles/roles-in-an-organization)." + +You can have more granular control over the permissions you grant at the repository level by creating up to three custom repository roles. {% data reusables.organizations.about-custom-repo-roles %} 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). + +After you create a custom role, anyone with admin access to a repository can assign the role to an individual or team. For more information, see "[Managing an individual's access to an organization repository](/organizations/managing-access-to-your-organizations-repositories/managing-an-individuals-access-to-an-organization-repository)" and "[Managing team access to an organization repository](/organizations/managing-access-to-your-organizations-repositories/managing-team-access-to-an-organization-repository)." + +{% ifversion custom-repo-role-api %} + +You can also use the REST API to create and manage custom repository roles. For more information, see "[Custom Repository Roles](/rest/orgs/custom-roles)." + +{% else %} + +You can also use the REST API to list the custom repository roles available in your organization. For more information, see "[Custom Repository Roles API](/rest/orgs/custom-roles)." + +{% endif %} + +## About the inherited role + +When you create a custom repository role, you start by choosing an inherited role from a set of pre-defined options. The inherited role determines the initial set of permissions included in the custom role. Then, you can further customize the role by choosing additional permissions to give the role. For the full list of available permissions, see "[Additional permissions for custom roles](#additional-permissions-for-custom-roles)." + +Your options for the inherited role are standardized for different types of contributors in your repository. + +| Inherited role | Designed for | +|----|----| +| **Read** | Non-code contributors who want to view or discuss your project | +| **Triage** | Contributors who need to proactively manage issues and pull requests without write access | +| **Write** | Organization members and collaborators who actively push to your project | +| **Maintain** | Project managers who need to manage the repository without access to sensitive or destructive actions | + +## Custom role examples + +Here are some examples of custom repository roles you can configure. + +| Custom repository role | Summary | Inherited role | Additional permissions | +|----|----|----|----| +| Security engineer | Able to contribute code and maintain the security pipeline | **Maintain** | Delete code scanning results | +| Contractor | Able to develop webhooks integrations | **Write** | Manage webhooks | +| Community manager | Able to handle all the community interactions without being able to contribute code | **Read** | - Mark an issue as duplicate
- Manage GitHub Page settings
- Manage wiki settings
- Set the social preview
- Edit repository metadata
- Triage discussions | + +## Additional permissions for custom roles + +After choosing an inherited role, you can select additional permissions for your custom role. + +You can only choose an additional permission if it's not already included in the inherited role. For example, if the inherited role offers **Write** access to a repository, then the "Close a pull request" permission will already be included in the inherited role. + +{% ifversion discussions %} +### Discussions + +- **Create a discussion category**: Ability to create a new discussion category. For more information, see "[Creating a new discussion category](/discussions/managing-discussions-for-your-community/managing-categories-for-discussions#creating-a-category)." +- **Edit a discussion category**: Ability to edit a discussion category. For more information, see "[Editing a discussion category](/discussions/managing-discussions-for-your-community/managing-categories-for-discussions#editing-a-category)." +- **Delete a discussion category**: Ability to delete a discussion category. For more information, see "[Deleting a discussion category](/discussions/managing-discussions-for-your-community/managing-categories-for-discussions#deleting-a-category)." +- **Mark or unmark discussion answers**: Ability to mark answers to a discussion, if the category for the discussion accepts answers. For more information, see "[Mark or unmark comments in a discussion as the answer](/discussions/managing-discussions-for-your-community/moderating-discussions#marking-a-comment-as-an-answer)." +- **Hide or unhide discussion comments**: Ability to hide and unhide comments in a discussion. For more information, see "[Moderating discussions](/communities/moderating-comments-and-conversations/managing-disruptive-comments#hiding-a-comment)." +- **Convert issues to discussions**: Ability to convert an issue into a discussion. For more information, see "[Converting issues to discussions](/discussions/managing-discussions-for-your-community/moderating-discussions#converting-an-issue-to-a-discussion)." +{% endif %} + +### Issue and Pull Requests + +- **Assign or remove a user**: Assign a user to an issue or pull request, or remove a user from an issue or pull request. +- **Add or remove a label**: Add a label to an issue or a pull request, or remove a label from an issue or pull request. + +### Issue + +- **Close an issue** +- **Reopen a closed issue** +- **Delete an issue** +- **Mark an issue as a duplicate** + +### Pull Request + +- **Close a pull request** +- **Reopen a closed pull request** +- **Request a pull request review**: Request a review from a user or team. + +### Repository + +- **Set milestones**: Add milestones to an issue or pull request. +- **Manage wiki settings**: Turn on wikis for a repository. +- **Manage project settings**: Turning on projects for a repository. +- **Manage pull request merging settings**: Choose the type of merge commits that are allowed in your repository, such as merge, squash, or rebase. +- **Manage {% data variables.product.prodname_pages %} settings**: Enable {% data variables.product.prodname_pages %} for the repository, and select the branch you want to publish. For more information, see "[Configuring a publishing source for your {% data variables.product.prodname_pages %} site](/pages/getting-started-with-github-pages/configuring-a-publishing-source-for-your-github-pages-site)." +- **Manage webhooks**: Add webhooks to the repository. +- **Manage deploy keys**: Add deploy keys to the repository. +- **Edit repository metadata**: Update the repository description as well as the repository topics. +{%- ifversion ghec %} +- **Set interaction limits**: Temporarily restrict certain users from commenting, opening issues, or creating pull requests in your public repository to enforce a period of limited activity. For more information, see "[Limiting interactions in your repository](/communities/moderating-comments-and-conversations/limiting-interactions-in-your-repository)." +{%- endif %} +- **Set the social preview**: Add an identifying image to your repository that appears on social media platforms when your repository is linked. For more information, see "[Customizing your repository's social media preview](/repositories/managing-your-repositorys-settings-and-features/customizing-your-repository/customizing-your-repositorys-social-media-preview)." +- **Push commits to protected branches**: Push to a branch that is marked as a protected branch. Branch protection rules will still apply and could result in a push being rejected. +- **Create protected tags**: Create tags that match a tag protection rule. For more information, see "[Configuring tag protection rules](/repositories/managing-your-repositorys-settings-and-features/managing-repository-settings/configuring-tag-protection-rules)." +- **Delete protected tags**: Delete tags that match a tag protection rule. For more information, see "[Configuring tag protection rules](/repositories/managing-your-repositorys-settings-and-features/managing-repository-settings/configuring-tag-protection-rules)."{% ifversion bypass-branch-protections %} +- **Bypass branch protections**: Push to a protected branch without needing to comply with branch protection rules.{% endif %} + +### Security + +- **View {% data variables.product.prodname_code_scanning %} results**: Ability to view {% data variables.product.prodname_code_scanning %} alerts. +- **Dismiss or reopen {% data variables.product.prodname_code_scanning %} results**: Ability to dismiss or reopen {% data variables.product.prodname_code_scanning %} alerts. +- **Delete {% data variables.product.prodname_code_scanning %} results**: Ability to delete {% data variables.product.prodname_code_scanning %} alerts. +- **View {% data variables.product.prodname_dependabot_alerts %}**: Ability to view {% data variables.product.prodname_dependabot_alerts %}. +- **Dismiss or reopen {% data variables.product.prodname_dependabot_alerts %}**: Ability to dismiss or reopen {% data variables.product.prodname_dependabot_alerts %}. +- **View {% data variables.product.prodname_secret_scanning %} results**: Ability to view {% data variables.product.prodname_secret_scanning %} alerts. +- **Dismiss or reopen {% data variables.product.prodname_secret_scanning %} results**: Ability to dismiss or reopen {% data variables.product.prodname_secret_scanning %} alerts. + +## Precedence for different levels of access + +If a person is given different levels of access through different avenues, such as team membership and the base permissions for an organization, the highest access overrides the others. For example, if an organization owner gives an organization member a custom role that uses the "Read" inherited role, and then an organization owner sets the organization's base permission to "Write", then this custom role will have write access, along with any additional permissions included in the custom role. + +{% data reusables.organizations.mixed-roles-warning %} + +To resolve conflicting access, you can adjust your organization's base permissions or the team's access, or edit the custom role. For more information, see: + - "[Setting base permissions for an organization](/github/setting-up-and-managing-organizations-and-teams/setting-base-permissions-for-an-organization)" + - "[Managing team access to an organization repository](/organizations/managing-access-to-your-organizations-repositories/managing-team-access-to-an-organization-repository)" + - "[Editing a repository role](#editing-a-repository-role)" \ No newline at end of file diff --git a/content/organizations/managing-peoples-access-to-your-organization-with-roles/index.md b/content/organizations/managing-peoples-access-to-your-organization-with-roles/index.md index edc22f9496..3816a9cf3f 100644 --- a/content/organizations/managing-peoples-access-to-your-organization-with-roles/index.md +++ b/content/organizations/managing-peoples-access-to-your-organization-with-roles/index.md @@ -15,8 +15,9 @@ topics: - Teams children: - /roles-in-an-organization - - /maintaining-ownership-continuity-for-your-organization + - /about-custom-repository-roles - /managing-custom-repository-roles-for-an-organization + - /maintaining-ownership-continuity-for-your-organization - /adding-a-billing-manager-to-your-organization - /removing-a-billing-manager-from-your-organization - /managing-security-managers-in-your-organization diff --git a/content/organizations/managing-peoples-access-to-your-organization-with-roles/managing-custom-repository-roles-for-an-organization.md b/content/organizations/managing-peoples-access-to-your-organization-with-roles/managing-custom-repository-roles-for-an-organization.md index cc6ec18ba9..0cb62007f0 100644 --- a/content/organizations/managing-peoples-access-to-your-organization-with-roles/managing-custom-repository-roles-for-an-organization.md +++ b/content/organizations/managing-peoples-access-to-your-organization-with-roles/managing-custom-repository-roles-for-an-organization.md @@ -1,145 +1,27 @@ --- title: Managing custom repository roles for an organization -intro: You can more granularly control access to your organization's repositories by creating custom repository roles. +intro: You can create, edit, or delete custom repository roles for your organization. permissions: Organization owners can manage custom repository roles. versions: feature: custom-repository-roles topics: - Organizations - Teams -shortTitle: Custom repository roles +shortTitle: Manage custom roles redirect_from: - /early-access/github/articles/managing-custom-repository-roles-for-an-organization --- +{% data reusables.organizations.custom-repo-roles-ghec-only %} + ## About custom repository roles -To perform any actions on {% data variables.product.product_name %}, such as creating a pull request in a repository or changing an organization's billing settings, a person must have sufficient access to the relevant account or resource. This access is controlled by permissions. A permission is the ability to perform a specific action. For example, the ability to delete an issue is a permission. A role is a set of permissions you can assign to individuals or teams. - -Within an organization, you can assign roles at the organization, team, and repository level. For more information about the different levels of roles, see "[Roles in an organization](/organizations/managing-peoples-access-to-your-organization-with-roles/roles-in-an-organization)." - -You can have more granular control over the permissions you grant at the repository level by creating up to three custom repository roles. A custom repository role is a configurable set of permissions with a custom name you choose. After you create a custom role, anyone with admin access to a repository can assign the role to an individual or team. For more information, see "[Managing an individual's access to an organization repository](/organizations/managing-access-to-your-organizations-repositories/managing-an-individuals-access-to-an-organization-repository)" and "[Managing team access to an organization repository](/organizations/managing-access-to-your-organizations-repositories/managing-team-access-to-an-organization-repository)." - -{% ifversion custom-repo-role-api %} - -You can also use the REST API to create and manage custom repository roles. For more information, see "[Custom Repository Roles](/rest/orgs/custom-roles)." - -{% else %} - -You can also use the REST API to list the custom repository roles available in your organization. For more information, see "[Custom Repository Roles API](/rest/orgs/custom-roles)." - -{% endif %} - -## About the inherited role - -When you create a custom repository role, you start by choosing an inherited role from a set of pre-defined options. The inherited role determines the initial set of permissions included in the custom role. Then, you can further customize the role by choosing additional permissions to give the role. For the full list of available permissions, see "[Additional permissions for custom roles](#additional-permissions-for-custom-roles)." - -Your options for the inherited role are standardized for different types of contributors in your repository. - -| Inherited role | Designed for | -|----|----| -| **Read** | Non-code contributors who want to view or discuss your project. | -| **Triage** | Contributors who need to proactively manage issues and pull requests without write access. | -| **Write** | Organization members and collaborators who actively push to your project. | -| **Maintain** | Project managers who need to manage the repository without access to sensitive or destructive actions. - -## Custom role examples - -Here are some examples of custom repository roles you can configure. - -| Custom repository role | Summary | Inherited role | Additional permissions | -|----|----|----|----| -| Security engineer | Able to contribute code and maintain the security pipeline | **Maintain** | Delete code scanning results | -| Contractor | Able to develop webhooks integrations | **Write** | Manage webhooks | -| Community manager | Able to handle all the community interactions without being able to contribute code | **Read** | - Mark an issue as duplicate
- Manage GitHub Page settings
- Manage wiki settings
- Set the social preview
- Edit repository metadata
- Triage discussions | - -## Additional permissions for custom roles - -After choosing an inherited role, you can select additional permissions for your custom role. - -You can only choose an additional permission if it's not already included in the inherited role. For example, if the inherited role offers **Write** access to a repository, then the "Close a pull request" permission will already be included in the inherited role. - -{% ifversion discussions %} -### Discussions - -- **Create a discussion category**: Ability to create a new discussion category. For more information, see "[Creating a new discussion category](/discussions/managing-discussions-for-your-community/managing-categories-for-discussions#creating-a-category)". -- **Edit a discussion category**: Ability to edit a discussion category. For more information, see "[Editing a discussion category](/discussions/managing-discussions-for-your-community/managing-categories-for-discussions#editing-a-category)." -- **Delete a discussion category**: Ability to delete a discussion category. For more information, see "[Deleting a discussion category](/discussions/managing-discussions-for-your-community/managing-categories-for-discussions#deleting-a-category)." -- **Mark or unmark discussion answers**: Ability to mark answers to a discussion, if the category for the discussion accepts answers. For more information, see "[Mark or unmark comments in a discussion as the answer](/discussions/managing-discussions-for-your-community/moderating-discussions#marking-a-comment-as-an-answer)". -- **Hide or unhide discussion comments**: Ability to hide and unhide comments in a discussion. For more information, see "[Moderating discussions](/communities/moderating-comments-and-conversations/managing-disruptive-comments#hiding-a-comment)." -- **Convert issues to discussions**: Ability to convert an issue into a discussion. For more information, see "[Converting issues to discussions](/discussions/managing-discussions-for-your-community/moderating-discussions#converting-an-issue-to-a-discussion)." -{% endif %} - -### Issue and Pull Requests - -- **Assign or remove a user**: Assign a user to an issue or pull request, or remove a user from an issue or pull request. -- **Add or remove a label**: Add a label to an issue or a pull request, or remove a label from an issue or pull request. - -### Issue - -- **Close an issue** -- **Reopen a closed issue** -- **Delete an issue** -- **Mark an issue as a duplicate** - -### Pull Request - -- **Close a pull request** -- **Reopen a closed pull request** -- **Request a pull request review**: Request a review from a user or team. - -### Repository - -- **Set milestones**: Add milestones to an issue or pull request. -- **Manage wiki settings**: Turn on wikis for a repository. -- **Manage project settings**: Turning on projects for a repository. -- **Manage pull request merging settings**: Choose the type of merge commits that are allowed in your repository, such as merge, squash, or rebase. -- **Manage {% data variables.product.prodname_pages %} settings**: Enable {% data variables.product.prodname_pages %} for the repository, and select the branch you want to publish. For more information, see "[Configuring a publishing source for your {% data variables.product.prodname_pages %} site](/pages/getting-started-with-github-pages/configuring-a-publishing-source-for-your-github-pages-site)." -- **Manage webhooks**: Add webhooks to the repository. -- **Manage deploy keys**: Add deploy keys to the repository. -- **Edit repository metadata**: Update the repository description as well as the repository topics. -{%- ifversion ghec %} -- **Set interaction limits**: Temporarily restrict certain users from commenting, opening issues, or creating pull requests in your public repository to enforce a period of limited activity. For more information, see "[Limiting interactions in your repository](/communities/moderating-comments-and-conversations/limiting-interactions-in-your-repository)." -{%- endif %} -- **Set the social preview**: Add an identifying image to your repository that appears on social media platforms when your repository is linked. For more information, see "[Customizing your repository's social media preview](/repositories/managing-your-repositorys-settings-and-features/customizing-your-repository/customizing-your-repositorys-social-media-preview)." -- **Push commits to protected branches**: Push to a branch that is marked as a protected branch. Branch protection rules will still apply and could result in a push being rejected. -- **Create protected tags**: Create tags that match a tag protection rule. For more information, see "[Configuring tag protection rules](/repositories/managing-your-repositorys-settings-and-features/managing-repository-settings/configuring-tag-protection-rules)." -- **Delete protected tags**: Delete tags that match a tag protection rule. For more information, see "[Configuring tag protection rules](/repositories/managing-your-repositorys-settings-and-features/managing-repository-settings/configuring-tag-protection-rules)."{% ifversion bypass-branch-protections %} -- **Bypass branch protections**: Push to a protected branch without needing to comply with branch protection rules.{% endif %} - -### Security - -- **View {% data variables.product.prodname_code_scanning %} results**: Ability to view {% data variables.product.prodname_code_scanning %} alerts. -- **Dismiss or reopen {% data variables.product.prodname_code_scanning %} results**: Ability to dismiss or reopen {% data variables.product.prodname_code_scanning %} alerts. -- **Delete {% data variables.product.prodname_code_scanning %} results**: Ability to delete {% data variables.product.prodname_code_scanning %} alerts. -- **View {% data variables.product.prodname_dependabot_alerts %}**: Ability to view {% data variables.product.prodname_dependabot_alerts %}. -- **Dismiss or reopen {% data variables.product.prodname_dependabot_alerts %}**: Ability to dismiss or reopen {% data variables.product.prodname_dependabot_alerts %}. -- **View {% data variables.product.prodname_secret_scanning %} results**: Ability to view {% data variables.product.prodname_secret_scanning %} alerts. -- **Dismiss or reopen {% data variables.product.prodname_secret_scanning %} results**: Ability to dismiss or reopen {% data variables.product.prodname_secret_scanning %} alerts. - -## Precedence for different levels of access - -If a person is given different levels of access through different avenues, such as team membership and the base permissions for an organization, the highest access overrides the others. For example, if an organization owner gives an organization member a custom role that uses the "Read" inherited role, and then an organization owner sets the organization's base permission to "Write", then this custom role will have write access, along with any additional permissions included in the custom role. - -{% data reusables.organizations.mixed-roles-warning %} - -To resolve conflicting access, you can adjust your organization's base permissions or the team's access, or edit the custom role. For more information, see: - - "[Setting base permissions for an organization](/github/setting-up-and-managing-organizations-and-teams/setting-base-permissions-for-an-organization)" - - "[Managing team access to an organization repository](/organizations/managing-access-to-your-organizations-repositories/managing-team-access-to-an-organization-repository)" - - "[Editing a repository role](#editing-a-repository-role)" +{% data reusables.organizations.about-custom-repo-roles %} For more information, see "[About custom repository roles](/organizations/managing-peoples-access-to-your-organization-with-roles/about-custom-repository-roles)." ## Creating a repository role To create a new repository role, you add permissions to an inherited role and give the custom role a name. -{% ifversion ghec %} -{% note %} - -**Note:** Only organizations that use {% data variables.product.prodname_ghe_cloud %} can create custom repository roles. {% data reusables.enterprise.link-to-ghec-trial %} - -{% endnote %} -{% endif %} - {% data reusables.profile.access_profile %} {% data reusables.profile.access_org %} {% data reusables.organizations.org_settings %} diff --git a/content/organizations/managing-programmatic-access-to-your-organization/managing-requests-for-personal-access-tokens-in-your-organization.md b/content/organizations/managing-programmatic-access-to-your-organization/managing-requests-for-personal-access-tokens-in-your-organization.md index 6a77074017..fb45074fba 100644 --- a/content/organizations/managing-programmatic-access-to-your-organization/managing-requests-for-personal-access-tokens-in-your-organization.md +++ b/content/organizations/managing-programmatic-access-to-your-organization/managing-requests-for-personal-access-tokens-in-your-organization.md @@ -35,6 +35,6 @@ Alternatively, you can approve or deny multiple tokens at once: {% data reusables.profile.access_org %} {% data reusables.profile.org_settings %} 1. In the left sidebar, under **{% octicon "key" aria-label="The key icon" %} {% data variables.product.pat_generic_caps %}s**, click **Pending requests**. If any tokens are pending approval for your organization, they will be displayed. -1. Optionally, use the **Owner** and **Repository** dropdown menus to filter the requests by the member making the request. +{% data reusables.user-settings.patv2-filters %} 1. Select each token that you want to approve or reject. 1. Select the **request selected...** dropdown menu and click **Approve...** or **Deny...**. diff --git a/content/organizations/managing-programmatic-access-to-your-organization/reviewing-and-revoking-personal-access-tokens-in-your-organization.md b/content/organizations/managing-programmatic-access-to-your-organization/reviewing-and-revoking-personal-access-tokens-in-your-organization.md index 5bdce996ef..40b6825eff 100644 --- a/content/organizations/managing-programmatic-access-to-your-organization/reviewing-and-revoking-personal-access-tokens-in-your-organization.md +++ b/content/organizations/managing-programmatic-access-to-your-organization/reviewing-and-revoking-personal-access-tokens-in-your-organization.md @@ -32,6 +32,6 @@ Alternatively, you can revoke multiple tokens at once: {% data reusables.profile.access_org %} {% data reusables.profile.org_settings %} 1. In the left sidebar, under **{% octicon "key" aria-label="The key icon" %} {% data variables.product.pat_generic_caps %}s**, click **Active tokens**. Any {% data variables.product.pat_v2 %}s that can access your organization will be displayed. -1. Optionally, use the **Owner** dropdown to filter the tokens by the member who created the token. +{% data reusables.user-settings.patv2-filters %} 1. Select each token that you want to revoke. 1. Select the **tokens selected...** dropdown menu and click **Revoke...**. diff --git a/data/graphql/ghae/graphql_upcoming_changes.public-ghae.yml b/data/graphql/ghae/graphql_upcoming_changes.public-ghae.yml index 859f0f2ef8..3fddac6539 100644 --- a/data/graphql/ghae/graphql_upcoming_changes.public-ghae.yml +++ b/data/graphql/ghae/graphql_upcoming_changes.public-ghae.yml @@ -211,6 +211,16 @@ upcoming_changes: date: '2023-01-01T00:00:00+00:00' criticality: breaking owner: lukewar + - location: ProjectNextFieldType.TRACKED_BY + description: + '`TRACKED_BY` will be removed. Follow the ProjectV2 guide at https://github.blog/changelog/2022-06-23-the-new-github-issues-june-23rd-update/, + to find a suitable replacement.' + reason: + The `ProjectNext` API is deprecated in favour of the more capable `ProjectV2` + API. + date: '2023-01-01T00:00:00+00:00' + criticality: breaking + owner: lukewar - location: ProjectNextFieldType.TRACKS description: '`TRACKS` will be removed. Follow the ProjectV2 guide at https://github.blog/changelog/2022-06-23-the-new-github-issues-june-23rd-update/, diff --git a/data/graphql/ghae/schema.docs-ghae.graphql b/data/graphql/ghae/schema.docs-ghae.graphql index 343387fba6..35638f140e 100644 --- a/data/graphql/ghae/schema.docs-ghae.graphql +++ b/data/graphql/ghae/schema.docs-ghae.graphql @@ -1664,6 +1664,17 @@ type BranchProtectionRule implements Node { """ isAdminEnforced: Boolean! + """ + Whether users can pull changes from upstream when the branch is locked. Set to + `true` to allow fork syncing. Set to `false` to prevent fork syncing. + """ + lockAllowsFetchAndMerge: Boolean! + + """ + Whether to set the branch as read-only. If this is true, users will not be able to push to the branch. + """ + lockBranch: Boolean! + """ Repository refs that are protected by this rule """ @@ -1729,6 +1740,11 @@ type BranchProtectionRule implements Node { """ repository: Repository + """ + Whether someone other than the person who last pushed to the branch must approve this pull request + """ + requireLastPushApproval: Boolean! + """ Number of approving reviews required to update matching branches. """ @@ -5601,6 +5617,17 @@ input CreateBranchProtectionRuleInput { """ isAdminEnforced: Boolean + """ + Whether users can pull changes from upstream when the branch is locked. Set to + `true` to allow fork syncing. Set to `false` to prevent fork syncing. + """ + lockAllowsFetchAndMerge: Boolean + + """ + Whether to set the branch as read-only. If this is true, users will not be able to push to the branch. + """ + lockBranch: Boolean + """ The glob-like pattern used to determine matching branches. """ @@ -5616,6 +5643,11 @@ input CreateBranchProtectionRuleInput { """ repositoryId: ID! @possibleTypes(concreteTypes: ["Repository"]) + """ + Whether someone other than the person who last pushed to the branch must approve this pull request + """ + requireLastPushApproval: Boolean + """ Number of approving reviews required to update matching branches. """ @@ -32712,6 +32744,11 @@ type Repository implements Node & ProjectOwner & RepositoryInfo & Starrable & Su """ hasAnonymousAccessEnabled: Boolean! + """ + Are discussions available on this repository? + """ + hasDiscussionsEnabled: Boolean! + """ Indicates if the repository has issues feature enabled. """ @@ -40223,6 +40260,17 @@ input UpdateBranchProtectionRuleInput { """ isAdminEnforced: Boolean + """ + Whether users can pull changes from upstream when the branch is locked. Set to + `true` to allow fork syncing. Set to `false` to prevent fork syncing. + """ + lockAllowsFetchAndMerge: Boolean + + """ + Whether to set the branch as read-only. If this is true, users will not be able to push to the branch. + """ + lockBranch: Boolean + """ The glob-like pattern used to determine matching branches. """ @@ -40233,6 +40281,11 @@ input UpdateBranchProtectionRuleInput { """ pushActorIds: [ID!] + """ + Whether someone other than the person who last pushed to the branch must approve this pull request + """ + requireLastPushApproval: Boolean + """ Number of approving reviews required to update matching branches. """ @@ -41965,6 +42018,11 @@ input UpdateRepositoryInput { """ description: String + """ + Indicates if the repository should have the discussions feature enabled. + """ + hasDiscussionsEnabled: Boolean + """ Indicates if the repository should have the issues feature enabled. """ diff --git a/data/graphql/ghec/graphql_upcoming_changes.public.yml b/data/graphql/ghec/graphql_upcoming_changes.public.yml index 10bc243aee..3223f72fd8 100644 --- a/data/graphql/ghec/graphql_upcoming_changes.public.yml +++ b/data/graphql/ghec/graphql_upcoming_changes.public.yml @@ -814,6 +814,16 @@ upcoming_changes: date: '2023-01-01T00:00:00+00:00' criticality: breaking owner: lukewar + - location: ProjectNextFieldType.TRACKED_BY + description: + '`TRACKED_BY` will be removed. Follow the ProjectV2 guide at https://github.blog/changelog/2022-06-23-the-new-github-issues-june-23rd-update/, + to find a suitable replacement.' + reason: + The `ProjectNext` API is deprecated in favour of the more capable `ProjectV2` + API. + date: '2023-01-01T00:00:00+00:00' + criticality: breaking + owner: lukewar - location: ProjectNextFieldType.TRACKS description: '`TRACKS` will be removed. Follow the ProjectV2 guide at https://github.blog/changelog/2022-06-23-the-new-github-issues-june-23rd-update/, diff --git a/data/graphql/ghec/schema.docs.graphql b/data/graphql/ghec/schema.docs.graphql index 07aea8e81e..1393406154 100644 --- a/data/graphql/ghec/schema.docs.graphql +++ b/data/graphql/ghec/schema.docs.graphql @@ -1238,6 +1238,41 @@ type ApproveVerifiableDomainPayload { domain: VerifiableDomain } +""" +Autogenerated input type of ArchiveProjectV2Item +""" +input ArchiveProjectV2ItemInput { + """ + A unique identifier for the client performing the mutation. + """ + clientMutationId: String + + """ + The ID of the ProjectV2Item to archive. + """ + itemId: ID! @possibleTypes(concreteTypes: ["ProjectV2Item"]) + + """ + The ID of the Project to archive the item from. + """ + projectId: ID! @possibleTypes(concreteTypes: ["ProjectV2"]) +} + +""" +Autogenerated return type of ArchiveProjectV2Item +""" +type ArchiveProjectV2ItemPayload { + """ + A unique identifier for the client performing the mutation. + """ + clientMutationId: String + + """ + The item archived from the project. + """ + item: ProjectV2Item +} + """ Autogenerated input type of ArchiveRepository """ @@ -2012,6 +2047,17 @@ type BranchProtectionRule implements Node { """ isAdminEnforced: Boolean! + """ + Whether users can pull changes from upstream when the branch is locked. Set to + `true` to allow fork syncing. Set to `false` to prevent fork syncing. + """ + lockAllowsFetchAndMerge: Boolean! + + """ + Whether to set the branch as read-only. If this is true, users will not be able to push to the branch. + """ + lockBranch: Boolean! + """ Repository refs that are protected by this rule """ @@ -2077,6 +2123,11 @@ type BranchProtectionRule implements Node { """ repository: Repository + """ + Whether someone other than the person who last pushed to the branch must approve this pull request + """ + requireLastPushApproval: Boolean! + """ Number of approving reviews required to update matching branches. """ @@ -6075,6 +6126,17 @@ input CreateBranchProtectionRuleInput { """ isAdminEnforced: Boolean + """ + Whether users can pull changes from upstream when the branch is locked. Set to + `true` to allow fork syncing. Set to `false` to prevent fork syncing. + """ + lockAllowsFetchAndMerge: Boolean + + """ + Whether to set the branch as read-only. If this is true, users will not be able to push to the branch. + """ + lockBranch: Boolean + """ The glob-like pattern used to determine matching branches. """ @@ -6090,6 +6152,11 @@ input CreateBranchProtectionRuleInput { """ repositoryId: ID! @possibleTypes(concreteTypes: ["Repository"]) + """ + Whether someone other than the person who last pushed to the branch must approve this pull request + """ + requireLastPushApproval: Boolean + """ Number of approving reviews required to update matching branches. """ @@ -17602,6 +17669,41 @@ type LicenseRule { label: String! } +""" +Autogenerated input type of LinkProjectV2ToRepository +""" +input LinkProjectV2ToRepositoryInput { + """ + A unique identifier for the client performing the mutation. + """ + clientMutationId: String + + """ + The ID of the project to link to the repository. + """ + projectId: ID! @possibleTypes(concreteTypes: ["ProjectV2"]) + + """ + The ID of the repository to link to the project. + """ + repositoryId: ID! @possibleTypes(concreteTypes: ["Repository"]) +} + +""" +Autogenerated return type of LinkProjectV2ToRepository +""" +type LinkProjectV2ToRepositoryPayload { + """ + A unique identifier for the client performing the mutation. + """ + clientMutationId: String + + """ + The repository the project is linked to. + """ + repository: Repository +} + """ Autogenerated input type of LinkRepositoryToProject """ @@ -19851,6 +19953,16 @@ type Mutation { input: ApproveVerifiableDomainInput! ): ApproveVerifiableDomainPayload + """ + Archives a ProjectV2Item + """ + archiveProjectV2Item( + """ + Parameters for ArchiveProjectV2Item + """ + input: ArchiveProjectV2ItemInput! + ): ArchiveProjectV2ItemPayload + """ Marks a repository as archived. """ @@ -20577,6 +20689,16 @@ type Mutation { input: InviteEnterpriseAdminInput! ): InviteEnterpriseAdminPayload + """ + Links a project to a repository. + """ + linkProjectV2ToRepository( + """ + Parameters for LinkProjectV2ToRepository + """ + input: LinkProjectV2ToRepositoryInput! + ): LinkProjectV2ToRepositoryPayload + """ Creates a repository link for a project. """ @@ -20957,6 +21079,16 @@ type Mutation { input: TransferIssueInput! ): TransferIssuePayload + """ + Unarchives a ProjectV2Item + """ + unarchiveProjectV2Item( + """ + Parameters for UnarchiveProjectV2Item + """ + input: UnarchiveProjectV2ItemInput! + ): UnarchiveProjectV2ItemPayload + """ Unarchives a repository. """ @@ -20987,6 +21119,16 @@ type Mutation { input: UnfollowUserInput! ): UnfollowUserPayload + """ + Unlinks a project from a repository. + """ + unlinkProjectV2FromRepository( + """ + Parameters for UnlinkProjectV2FromRepository + """ + input: UnlinkProjectV2FromRepositoryInput! + ): UnlinkProjectV2FromRepositoryPayload + """ Deletes a repository link from a project. """ @@ -29307,6 +29449,14 @@ enum ProjectNextFieldType { reason: "The `ProjectNext` API is deprecated in favour of the more capable `ProjectV2` API. Follow the ProjectV2 guide at https://github.blog/changelog/2022-06-23-the-new-github-issues-june-23rd-update/, to find a suitable replacement. Removal on 2023-01-01 UTC." ) + """ + Tracked by + """ + TRACKED_BY + @deprecated( + reason: "The `ProjectNext` API is deprecated in favour of the more capable `ProjectV2` API. Follow the ProjectV2 guide at https://github.blog/changelog/2022-06-23-the-new-github-issues-june-23rd-update/, to find a suitable replacement. Removal on 2023-01-01 UTC." + ) + """ Tracks """ @@ -30398,6 +30548,11 @@ enum ProjectV2FieldType { """ TITLE + """ + Tracked by + """ + TRACKED_BY + """ Tracks """ @@ -40238,6 +40393,11 @@ type Repository implements Node & PackageOwner & ProjectOwner & ProjectV2Recent """ fundingLinks: [FundingLink!]! + """ + Are discussions available on this repository? + """ + hasDiscussionsEnabled: Boolean! + """ Indicates if the repository has issues feature enabled. """ @@ -48939,6 +49099,41 @@ An RFC 3986, RFC 3987, and RFC 6570 (level 4) compliant URI string. """ scalar URI +""" +Autogenerated input type of UnarchiveProjectV2Item +""" +input UnarchiveProjectV2ItemInput { + """ + A unique identifier for the client performing the mutation. + """ + clientMutationId: String + + """ + The ID of the ProjectV2Item to unarchive. + """ + itemId: ID! @possibleTypes(concreteTypes: ["ProjectV2Item"]) + + """ + The ID of the Project to archive the item from. + """ + projectId: ID! @possibleTypes(concreteTypes: ["ProjectV2"]) +} + +""" +Autogenerated return type of UnarchiveProjectV2Item +""" +type UnarchiveProjectV2ItemPayload { + """ + A unique identifier for the client performing the mutation. + """ + clientMutationId: String + + """ + The item unarchived from the project. + """ + item: ProjectV2Item +} + """ Autogenerated input type of UnarchiveRepository """ @@ -49143,6 +49338,41 @@ type UnlabeledEvent implements Node { labelable: Labelable! } +""" +Autogenerated input type of UnlinkProjectV2FromRepository +""" +input UnlinkProjectV2FromRepositoryInput { + """ + A unique identifier for the client performing the mutation. + """ + clientMutationId: String + + """ + The ID of the project to unlink from the repository. + """ + projectId: ID! @possibleTypes(concreteTypes: ["ProjectV2"]) + + """ + The ID of the repository to unlink from the project. + """ + repositoryId: ID! @possibleTypes(concreteTypes: ["Repository"]) +} + +""" +Autogenerated return type of UnlinkProjectV2FromRepository +""" +type UnlinkProjectV2FromRepositoryPayload { + """ + A unique identifier for the client performing the mutation. + """ + clientMutationId: String + + """ + The repository the project is no longer linked to. + """ + repository: Repository +} + """ Autogenerated input type of UnlinkRepositoryFromProject """ @@ -49575,6 +49805,17 @@ input UpdateBranchProtectionRuleInput { """ isAdminEnforced: Boolean + """ + Whether users can pull changes from upstream when the branch is locked. Set to + `true` to allow fork syncing. Set to `false` to prevent fork syncing. + """ + lockAllowsFetchAndMerge: Boolean + + """ + Whether to set the branch as read-only. If this is true, users will not be able to push to the branch. + """ + lockBranch: Boolean + """ The glob-like pattern used to determine matching branches. """ @@ -49585,6 +49826,11 @@ input UpdateBranchProtectionRuleInput { """ pushActorIds: [ID!] + """ + Whether someone other than the person who last pushed to the branch must approve this pull request + """ + requireLastPushApproval: Boolean + """ Number of approving reviews required to update matching branches. """ @@ -51797,6 +52043,11 @@ input UpdateRepositoryInput { """ description: String + """ + Indicates if the repository should have the discussions feature enabled. + """ + hasDiscussionsEnabled: Boolean + """ Indicates if the repository should have the issues feature enabled. """ diff --git a/data/graphql/ghes-3.7/graphql_upcoming_changes.public-enterprise.yml b/data/graphql/ghes-3.7/graphql_upcoming_changes.public-enterprise.yml index cd47c93ed3..b76ac857e9 100644 --- a/data/graphql/ghes-3.7/graphql_upcoming_changes.public-enterprise.yml +++ b/data/graphql/ghes-3.7/graphql_upcoming_changes.public-enterprise.yml @@ -68,14 +68,153 @@ upcoming_changes: date: '2022-07-01T00:00:00+00:00' criticality: breaking owner: jhunschejones - - location: Enterprise.userAccounts - description: - '`userAccounts` will be removed. Use the `Enterprise.members` field - instead.' - reason: The `Enterprise.userAccounts` field is being removed. - date: '2022-07-01T00:00:00+00:00' + - location: LockMergeQueueInput.branch + description: '`branch` will be removed.' + reason: + The merge queue is locked for the repository's default branch, the `branch` + argument is now a no-op + date: '2022-10-01T00:00:00+00:00' criticality: breaking - owner: jdennes + owner: jhunschejones + - location: MergeLockedMergeGroupInput.branch + description: '`branch` will be removed.' + reason: + Changes are merged into the repository's default branch, the `branch` argument + is now a no-op + date: '2022-10-01T00:00:00+00:00' + criticality: breaking + owner: jhunschejones + - location: ProjectNextFieldType.ASSIGNEES + description: + '`ASSIGNEES` will be removed. Follow the ProjectV2 guide at https://github.blog/changelog/2022-06-23-the-new-github-issues-june-23rd-update/, + to find a suitable replacement.' + reason: + The `ProjectNext` API is deprecated in favour of the more capable `ProjectV2` + API. + date: '2022-10-01T00:00:00+00:00' + criticality: breaking + owner: lukewar + - location: ProjectNextFieldType.DATE + description: + '`DATE` will be removed. Follow the ProjectV2 guide at https://github.blog/changelog/2022-06-23-the-new-github-issues-june-23rd-update/, + to find a suitable replacement.' + reason: + The `ProjectNext` API is deprecated in favour of the more capable `ProjectV2` + API. + date: '2022-10-01T00:00:00+00:00' + criticality: breaking + owner: lukewar + - location: ProjectNextFieldType.ITERATION + description: + '`ITERATION` will be removed. Follow the ProjectV2 guide at https://github.blog/changelog/2022-06-23-the-new-github-issues-june-23rd-update/, + to find a suitable replacement.' + reason: + The `ProjectNext` API is deprecated in favour of the more capable `ProjectV2` + API. + date: '2022-10-01T00:00:00+00:00' + criticality: breaking + owner: lukewar + - location: ProjectNextFieldType.LABELS + description: + '`LABELS` will be removed. Follow the ProjectV2 guide at https://github.blog/changelog/2022-06-23-the-new-github-issues-june-23rd-update/, + to find a suitable replacement.' + reason: + The `ProjectNext` API is deprecated in favour of the more capable `ProjectV2` + API. + date: '2022-10-01T00:00:00+00:00' + criticality: breaking + owner: lukewar + - location: ProjectNextFieldType.LINKED_PULL_REQUESTS + description: + '`LINKED_PULL_REQUESTS` will be removed. Follow the ProjectV2 guide + at https://github.blog/changelog/2022-06-23-the-new-github-issues-june-23rd-update/, + to find a suitable replacement.' + reason: + The `ProjectNext` API is deprecated in favour of the more capable `ProjectV2` + API. + date: '2022-10-01T00:00:00+00:00' + criticality: breaking + owner: lukewar + - location: ProjectNextFieldType.MILESTONE + description: + '`MILESTONE` will be removed. Follow the ProjectV2 guide at https://github.blog/changelog/2022-06-23-the-new-github-issues-june-23rd-update/, + to find a suitable replacement.' + reason: + The `ProjectNext` API is deprecated in favour of the more capable `ProjectV2` + API. + date: '2022-10-01T00:00:00+00:00' + criticality: breaking + owner: lukewar + - location: ProjectNextFieldType.NUMBER + description: + '`NUMBER` will be removed. Follow the ProjectV2 guide at https://github.blog/changelog/2022-06-23-the-new-github-issues-june-23rd-update/, + to find a suitable replacement.' + reason: + The `ProjectNext` API is deprecated in favour of the more capable `ProjectV2` + API. + date: '2022-10-01T00:00:00+00:00' + criticality: breaking + owner: lukewar + - location: ProjectNextFieldType.REPOSITORY + description: + '`REPOSITORY` will be removed. Follow the ProjectV2 guide at https://github.blog/changelog/2022-06-23-the-new-github-issues-june-23rd-update/, + to find a suitable replacement.' + reason: + The `ProjectNext` API is deprecated in favour of the more capable `ProjectV2` + API. + date: '2022-10-01T00:00:00+00:00' + criticality: breaking + owner: lukewar + - location: ProjectNextFieldType.REVIEWERS + description: + '`REVIEWERS` will be removed. Follow the ProjectV2 guide at https://github.blog/changelog/2022-06-23-the-new-github-issues-june-23rd-update/, + to find a suitable replacement.' + reason: + The `ProjectNext` API is deprecated in favour of the more capable `ProjectV2` + API. + date: '2022-10-01T00:00:00+00:00' + criticality: breaking + owner: lukewar + - location: ProjectNextFieldType.SINGLE_SELECT + description: + '`SINGLE_SELECT` will be removed. Follow the ProjectV2 guide at https://github.blog/changelog/2022-06-23-the-new-github-issues-june-23rd-update/, + to find a suitable replacement.' + reason: + The `ProjectNext` API is deprecated in favour of the more capable `ProjectV2` + API. + date: '2022-10-01T00:00:00+00:00' + criticality: breaking + owner: lukewar + - location: ProjectNextFieldType.TEXT + description: + '`TEXT` will be removed. Follow the ProjectV2 guide at https://github.blog/changelog/2022-06-23-the-new-github-issues-june-23rd-update/, + to find a suitable replacement.' + reason: + The `ProjectNext` API is deprecated in favour of the more capable `ProjectV2` + API. + date: '2022-10-01T00:00:00+00:00' + criticality: breaking + owner: lukewar + - location: ProjectNextFieldType.TITLE + description: + '`TITLE` will be removed. Follow the ProjectV2 guide at https://github.blog/changelog/2022-06-23-the-new-github-issues-june-23rd-update/, + to find a suitable replacement.' + reason: + The `ProjectNext` API is deprecated in favour of the more capable `ProjectV2` + API. + date: '2022-10-01T00:00:00+00:00' + criticality: breaking + owner: lukewar + - location: ProjectNextFieldType.TRACKS + description: + '`TRACKS` will be removed. Follow the ProjectV2 guide at https://github.blog/changelog/2022-06-23-the-new-github-issues-june-23rd-update/, + to find a suitable replacement.' + reason: + The `ProjectNext` API is deprecated in favour of the more capable `ProjectV2` + API. + date: '2022-10-01T00:00:00+00:00' + criticality: breaking + owner: lukewar - location: RemovePullRequestFromMergeQueueInput.branch description: '`branch` will be removed.' reason: @@ -84,3 +223,19 @@ upcoming_changes: date: '2022-10-01T00:00:00+00:00' criticality: breaking owner: jhunschejones + - location: RepositoryVulnerabilityAlert.fixReason + description: '`fixReason` will be removed.' + reason: + The `fixReason` field is being removed. You can still use `fixedAt` and + `dismissReason`. + date: '2022-10-01T00:00:00+00:00' + criticality: breaking + owner: jamestran201 + - location: UnlockAndResetMergeGroupInput.branch + description: '`branch` will be removed.' + reason: + The current merge group for the repository's default branch, the `branch` + argument is now a no-op + date: '2022-10-01T00:00:00+00:00' + criticality: breaking + owner: jhunschejones diff --git a/data/graphql/ghes-3.7/schema.docs-enterprise.graphql b/data/graphql/ghes-3.7/schema.docs-enterprise.graphql index 91a1111082..4169c22047 100644 --- a/data/graphql/ghes-3.7/schema.docs-enterprise.graphql +++ b/data/graphql/ghes-3.7/schema.docs-enterprise.graphql @@ -252,6 +252,36 @@ type AddDiscussionCommentPayload { comment: DiscussionComment } +""" +Autogenerated input type of AddDiscussionPollVote +""" +input AddDiscussionPollVoteInput { + """ + A unique identifier for the client performing the mutation. + """ + clientMutationId: String + + """ + The Node ID of the discussion poll option to vote for. + """ + pollOptionId: ID! @possibleTypes(concreteTypes: ["DiscussionPollOption"]) +} + +""" +Autogenerated return type of AddDiscussionPollVote +""" +type AddDiscussionPollVotePayload { + """ + A unique identifier for the client performing the mutation. + """ + clientMutationId: String + + """ + The poll option that a vote was added to. + """ + pollOption: DiscussionPollOption +} + """ Autogenerated input type of AddEnterpriseAdmin """ @@ -422,6 +452,87 @@ type AddProjectColumnPayload { project: Project } +""" +Autogenerated input type of AddProjectV2DraftIssue +""" +input AddProjectV2DraftIssueInput { + """ + The IDs of the assignees of the draft issue. + """ + assigneeIds: [ID!] @possibleTypes(concreteTypes: ["User"]) + + """ + The body of the draft issue. + """ + body: String + + """ + A unique identifier for the client performing the mutation. + """ + clientMutationId: String + + """ + The ID of the Project to add the draft issue to. + """ + projectId: ID! @possibleTypes(concreteTypes: ["ProjectV2"]) + + """ + The title of the draft issue. + """ + title: String! +} + +""" +Autogenerated return type of AddProjectV2DraftIssue +""" +type AddProjectV2DraftIssuePayload { + """ + A unique identifier for the client performing the mutation. + """ + clientMutationId: String + + """ + The draft issue added to the project. + """ + projectItem: ProjectV2Item +} + +""" +Autogenerated input type of AddProjectV2ItemById +""" +input AddProjectV2ItemByIdInput { + """ + A unique identifier for the client performing the mutation. + """ + clientMutationId: String + + """ + The id of the Issue or Pull Request to add. + """ + contentId: ID! + @possibleTypes(concreteTypes: ["DraftIssue", "Issue", "PullRequest"], abstractType: "ProjectV2ItemContent") + + """ + The ID of the Project to add the item to. + """ + projectId: ID! @possibleTypes(concreteTypes: ["ProjectV2"]) +} + +""" +Autogenerated return type of AddProjectV2ItemById +""" +type AddProjectV2ItemByIdPayload { + """ + A unique identifier for the client performing the mutation. + """ + clientMutationId: String + + """ + The item added to the project. + """ + item: ProjectV2Item +} + """ Autogenerated input type of AddPullRequestReviewComment """ @@ -2710,9 +2821,19 @@ input CheckRunFilter { checkType: CheckRunType """ - Filters the check runs by this status. + Filters the check runs by these conclusions. + """ + conclusions: [CheckConclusionState!] + + """ + Filters the check runs by this status. Superceded by statuses. """ status: CheckStatusState + + """ + Filters the check runs by this status. Overrides status. + """ + statuses: [CheckStatusState!] } """ @@ -4179,7 +4300,9 @@ type CommitComment implements Comment & Deletable & Minimizable & Node & Reactab lastEditedAt: DateTime """ - Returns why the comment was minimized. + Returns why the comment was minimized. One of `abuse`, `off-topic`, + `outdated`, `resolved`, `duplicate` and `spam`. Note that the case and + formatting of these values differs from the inputs to the `MinimizeComment` mutation. """ minimizedReason: String @@ -4573,7 +4696,7 @@ with `refs/heads/` (although the input is not required to be fully qualified). The Ref may be specified by its global node ID or by the -repository nameWithOwner and branch name. +`repositoryNameWithOwner` and `branchName`. ### Examples @@ -4581,10 +4704,10 @@ Specify a branch using a global node ID: { "id": "MDM6UmVmMTpyZWZzL2hlYWRzL21haW4=" } -Specify a branch using nameWithOwner and branch name: +Specify a branch using `repositoryNameWithOwner` and `branchName`: { - "nameWithOwner": "github/graphql-client", + "repositoryNameWithOwner": "github/graphql-client", "branchName": "main" } """ @@ -5052,7 +5175,8 @@ type ContributionsCollection { ): [PullRequestContributionsByRepository!]! """ - Pull request review contributions made by the user. + Pull request review contributions made by the user. Returns the most recently + submitted review for each PR reviewed by the user. """ pullRequestReviewContributions( """ @@ -6231,6 +6355,41 @@ type CreateProjectPayload { project: Project } +""" +Autogenerated input type of CreateProjectV2 +""" +input CreateProjectV2Input { + """ + A unique identifier for the client performing the mutation. + """ + clientMutationId: String + + """ + The owner ID to create the project under. + """ + ownerId: ID! @possibleTypes(concreteTypes: ["Organization", "User"], abstractType: "OrganizationOrUser") + + """ + The title of the project. + """ + title: String! +} + +""" +Autogenerated return type of CreateProjectV2 +""" +type CreateProjectV2Payload { + """ + A unique identifier for the client performing the mutation. + """ + clientMutationId: String + + """ + The new project. + """ + projectV2: ProjectV2 +} + """ Autogenerated input type of CreatePullRequest """ @@ -7374,6 +7533,41 @@ type DeleteProjectPayload { owner: ProjectOwner } +""" +Autogenerated input type of DeleteProjectV2Item +""" +input DeleteProjectV2ItemInput { + """ + A unique identifier for the client performing the mutation. + """ + clientMutationId: String + + """ + The ID of the item to be removed. + """ + itemId: ID! @possibleTypes(concreteTypes: ["ProjectV2Item"]) + + """ + The ID of the Project from which the item should be removed. + """ + projectId: ID! @possibleTypes(concreteTypes: ["ProjectV2"]) +} + +""" +Autogenerated return type of DeleteProjectV2Item +""" +type DeleteProjectV2ItemPayload { + """ + A unique identifier for the client performing the mutation. + """ + clientMutationId: String + + """ + The ID of the deleted item. + """ + deletedItemId: ID +} + """ Autogenerated input type of DeletePullRequestReviewComment """ @@ -8677,6 +8871,11 @@ type Discussion implements Comment & Deletable & Labelable & Lockable & Node & R """ number: Int! + """ + The poll associated with this discussion, if one exists. + """ + poll: DiscussionPoll + """ Identifies when the comment was published at. """ @@ -8858,6 +9057,11 @@ type DiscussionCategory implements Node & RepositoryNode { """ repository: Repository! + """ + The slug of this category. + """ + slug: String! + """ Identifies the date and time when the object was last updated. """ @@ -8985,7 +9189,9 @@ type DiscussionComment implements Comment & Deletable & Minimizable & Node & Rea lastEditedAt: DateTime """ - Returns why the comment was minimized. + Returns why the comment was minimized. One of `abuse`, `off-topic`, + `outdated`, `resolved`, `duplicate` and `spam`. Note that the case and + formatting of these values differs from the inputs to the `MinimizeComment` mutation. """ minimizedReason: String @@ -9303,6 +9509,11 @@ type DiscussionPoll implements Node { Returns the last _n_ elements from the list. """ last: Int + + """ + How to order the options for the discussion poll. + """ + orderBy: DiscussionPollOptionOrder = {field: AUTHORED_ORDER, direction: ASC} ): DiscussionPollOptionConnection """ @@ -9393,6 +9604,36 @@ type DiscussionPollOptionEdge { node: DiscussionPollOption } +""" +Ordering options for discussion poll option connections. +""" +input DiscussionPollOptionOrder { + """ + The ordering direction. + """ + direction: OrderDirection! + + """ + The field to order poll options by. + """ + field: DiscussionPollOptionOrderField! +} + +""" +Properties by which discussion poll option connections can be ordered. +""" +enum DiscussionPollOptionOrderField { + """ + Order poll options by the order that the poll author specified when creating the poll. + """ + AUTHORED_ORDER + + """ + Order poll options by the number of votes it has. + """ + VOTE_COUNT +} + """ Autogenerated input type of DismissPullRequestReview """ @@ -9493,6 +9734,122 @@ type DismissRepositoryVulnerabilityAlertPayload { repositoryVulnerabilityAlert: RepositoryVulnerabilityAlert } +""" +A draft issue within a project. +""" +type DraftIssue implements Node { + """ + A list of users to assigned to this draft issue. + """ + assignees( + """ + Returns the elements in the list that come after the specified cursor. + """ + after: String + + """ + Returns the elements in the list that come before the specified cursor. + """ + before: String + + """ + Returns the first _n_ elements from the list. + """ + first: Int + + """ + Returns the last _n_ elements from the list. + """ + last: Int + ): UserConnection! + + """ + The body of the draft issue. + """ + body: String! + + """ + The body of the draft issue rendered to HTML. + """ + bodyHTML: HTML! + + """ + The body of the draft issue rendered to text. + """ + bodyText: String! + + """ + Identifies the date and time when the object was created. + """ + createdAt: DateTime! + + """ + The actor who created this draft issue. + """ + creator: Actor + id: ID! + + """ + List of items linked with the draft issue (currently draft issue can be linked to only one item). + """ + projectV2Items( + """ + Returns the elements in the list that come after the specified cursor. + """ + after: String + + """ + Returns the elements in the list that come before the specified cursor. + """ + before: String + + """ + Returns the first _n_ elements from the list. + """ + first: Int + + """ + Returns the last _n_ elements from the list. + """ + last: Int + ): ProjectV2ItemConnection! + + """ + Projects that link to this draft issue (currently draft issue can be linked to only one project). + """ + projectsV2( + """ + Returns the elements in the list that come after the specified cursor. + """ + after: String + + """ + Returns the elements in the list that come before the specified cursor. + """ + before: String + + """ + Returns the first _n_ elements from the list. + """ + first: Int + + """ + Returns the last _n_ elements from the list. + """ + last: Int + ): ProjectV2Connection! + + """ + The title of the draft issue + """ + title: String! + + """ + Identifies the date and time when the object was last updated. + """ + updatedAt: DateTime! +} + """ Specifies a review comment to be left with a Pull Request Review. """ @@ -9573,7 +9930,7 @@ input EnablePullRequestAutoMergeInput { commitHeadline: String """ - The merge method to use. If omitted, defaults to 'MERGE' + The merge method to use. If omitted, defaults to `MERGE` """ mergeMethod: PullRequestMergeMethod = MERGE @@ -9763,34 +10120,6 @@ type Enterprise implements Node { """ url: URI! - """ - A list of user accounts on this enterprise. - """ - userAccounts( - """ - Returns the elements in the list that come after the specified cursor. - """ - after: String - - """ - Returns the elements in the list that come before the specified cursor. - """ - before: String - - """ - Returns the first _n_ elements from the list. - """ - first: Int - - """ - Returns the last _n_ elements from the list. - """ - last: Int - ): EnterpriseUserAccountConnection! - @deprecated( - reason: "The `Enterprise.userAccounts` field is being removed. Use the `Enterprise.members` field instead. Removal on 2022-07-01 UTC." - ) - """ Is the current viewer an admin of this enterprise? """ @@ -11998,46 +12327,6 @@ type EnterpriseUserAccount implements Actor & Node { user: User } -""" -The connection type for EnterpriseUserAccount. -""" -type EnterpriseUserAccountConnection { - """ - A list of edges. - """ - edges: [EnterpriseUserAccountEdge] - - """ - A list of nodes. - """ - nodes: [EnterpriseUserAccount] - - """ - Information to aid in pagination. - """ - pageInfo: PageInfo! - - """ - Identifies the total count of items in the connection. - """ - totalCount: Int! -} - -""" -An edge in a connection. -""" -type EnterpriseUserAccountEdge { - """ - A cursor for use in pagination. - """ - cursor: String! - - """ - The item at the end of the edge. - """ - node: EnterpriseUserAccount -} - """ The possible roles for enterprise membership. """ @@ -12845,7 +13134,9 @@ type GistComment implements Comment & Deletable & Minimizable & Node & Updatable lastEditedAt: DateTime """ - Returns why the comment was minimized. + Returns why the comment was minimized. One of `abuse`, `off-topic`, + `outdated`, `resolved`, `duplicate` and `spam`. Note that the case and + formatting of these values differs from the inputs to the `MinimizeComment` mutation. """ minimizedReason: String @@ -13845,7 +14136,7 @@ union IpAllowListOwner = App | Enterprise | Organization """ An Issue is a place to discuss ideas, enhancements, tasks, and bugs for a project. """ -type Issue implements Assignable & Closable & Comment & Labelable & Lockable & Node & Reactable & RepositoryNode & Subscribable & UniformResourceLocatable & Updatable & UpdatableComment { +type Issue implements Assignable & Closable & Comment & Labelable & Lockable & Node & ProjectV2Owner & Reactable & RepositoryNode & Subscribable & UniformResourceLocatable & Updatable & UpdatableComment { """ Reason that the conversation was locked. """ @@ -14102,6 +14393,51 @@ type Issue implements Assignable & Closable & Comment & Labelable & Lockable & N last: Int ): ProjectCardConnection! + """ + Find a project by number. + """ + projectV2( + """ + The project number. + """ + number: Int! + ): ProjectV2 + + """ + A list of projects under the owner. + """ + projectsV2( + """ + Returns the elements in the list that come after the specified cursor. + """ + after: String + + """ + Returns the elements in the list that come before the specified cursor. + """ + before: String + + """ + Returns the first _n_ elements from the list. + """ + first: Int + + """ + Returns the last _n_ elements from the list. + """ + last: Int + + """ + How to order the returned projects. + """ + orderBy: ProjectV2Order = {field: NUMBER, direction: DESC} + + """ + A project to search for under the the owner. + """ + query: String + ): ProjectV2Connection! + """ Identifies when the comment was published at. """ @@ -14400,7 +14736,9 @@ type IssueComment implements Comment & Deletable & Minimizable & Node & Reactabl lastEditedAt: DateTime """ - Returns why the comment was minimized. + Returns why the comment was minimized. One of `abuse`, `off-topic`, + `outdated`, `resolved`, `duplicate` and `spam`. Note that the case and + formatting of these values differs from the inputs to the `MinimizeComment` mutation. """ minimizedReason: String @@ -16382,6 +16720,41 @@ type MergeBranchPayload { mergeCommit: Commit } +""" +The possible default commit messages for merges. +""" +enum MergeCommitMessage { + """ + Default to a blank commit message. + """ + BLANK + + """ + Default to the pull request's body. + """ + PR_BODY + + """ + Default to the pull request's title. + """ + PR_TITLE +} + +""" +The possible default commit titles for merges. +""" +enum MergeCommitTitle { + """ + Default to the classic title for a merge message (e.g., Merge pull request #123 from branch-name). + """ + MERGE_MESSAGE + + """ + Default to the pull request's title. + """ + PR_TITLE +} + """ Autogenerated input type of MergePullRequest """ @@ -16638,20 +17011,10 @@ enum MigrationSourceType { """ BITBUCKET_SERVER - """ - A GitHub migration source. - """ - GITHUB - """ A GitHub Migration API source. """ GITHUB_ARCHIVE - - """ - A GitLab migration source. - """ - GITLAB } """ @@ -17001,7 +17364,9 @@ interface Minimizable { isMinimized: Boolean! """ - Returns why the comment was minimized. + Returns why the comment was minimized. One of `abuse`, `off-topic`, + `outdated`, `resolved`, `duplicate` and `spam`. Note that the case and + formatting of these values differs from the inputs to the `MinimizeComment` mutation. """ minimizedReason: String @@ -17210,6 +17575,16 @@ type Mutation { input: AddDiscussionCommentInput! ): AddDiscussionCommentPayload + """ + Vote for an option in a discussion poll. + """ + addDiscussionPollVote( + """ + Parameters for AddDiscussionPollVote + """ + input: AddDiscussionPollVoteInput! + ): AddDiscussionPollVotePayload + """ Adds an administrator to the global enterprise account. """ @@ -17250,6 +17625,26 @@ type Mutation { input: AddProjectColumnInput! ): AddProjectColumnPayload + """ + Creates a new draft issue and add it to a Project. + """ + addProjectV2DraftIssue( + """ + Parameters for AddProjectV2DraftIssue + """ + input: AddProjectV2DraftIssueInput! + ): AddProjectV2DraftIssuePayload + + """ + Links an existing content instance to a Project. + """ + addProjectV2ItemById( + """ + Parameters for AddProjectV2ItemById + """ + input: AddProjectV2ItemByIdInput! + ): AddProjectV2ItemByIdPayload + """ Adds a review to a Pull Request. """ @@ -17611,6 +18006,16 @@ type Mutation { input: CreateProjectInput! ): CreateProjectPayload + """ + Creates a new project. + """ + createProjectV2( + """ + Parameters for CreateProjectV2 + """ + input: CreateProjectV2Input! + ): CreateProjectV2Payload + """ Create a new pull request """ @@ -17791,6 +18196,16 @@ type Mutation { input: DeleteProjectColumnInput! ): DeleteProjectColumnPayload + """ + Deletes an item from a Project. + """ + deleteProjectV2Item( + """ + Parameters for DeleteProjectV2Item + """ + input: DeleteProjectV2ItemInput! + ): DeleteProjectV2ItemPayload + """ Deletes a pull request review. """ @@ -18352,7 +18767,7 @@ type Mutation { ): UnresolveReviewThreadPayload """ - Create a new branch protection rule + Update a branch protection rule """ updateBranchProtectionRule( """ @@ -18651,6 +19066,16 @@ type Mutation { input: UpdateOrganizationAllowPrivateRepositoryForkingSettingInput! ): UpdateOrganizationAllowPrivateRepositoryForkingSettingPayload + """ + Sets whether contributors are required to sign off on web-based commits for repositories in an organization. + """ + updateOrganizationWebCommitSignoffSetting( + """ + Parameters for UpdateOrganizationWebCommitSignoffSetting + """ + input: UpdateOrganizationWebCommitSignoffSettingInput! + ): UpdateOrganizationWebCommitSignoffSettingPayload + """ Updates an existing project. """ @@ -18681,6 +19106,47 @@ type Mutation { input: UpdateProjectColumnInput! ): UpdateProjectColumnPayload + """ + Updates an existing project (beta). + """ + updateProjectV2( + """ + Parameters for UpdateProjectV2 + """ + input: UpdateProjectV2Input! + ): UpdateProjectV2Payload + + """ + Updates a draft issue within a Project. + """ + updateProjectV2DraftIssue( + """ + Parameters for UpdateProjectV2DraftIssue + """ + input: UpdateProjectV2DraftIssueInput! + ): UpdateProjectV2DraftIssuePayload + + """ + This mutation updates the value of a field for an item in a Project. Currently + only single-select, text, number, date, and iteration fields are supported. + """ + updateProjectV2ItemFieldValue( + """ + Parameters for UpdateProjectV2ItemFieldValue + """ + input: UpdateProjectV2ItemFieldValueInput! + ): UpdateProjectV2ItemFieldValuePayload + + """ + This mutation updates the position of the item in the project, where the position represents the priority of an item. + """ + updateProjectV2ItemPosition( + """ + Parameters for UpdateProjectV2ItemPosition + """ + input: UpdateProjectV2ItemPositionInput! + ): UpdateProjectV2ItemPositionPayload + """ Update a pull request """ @@ -18768,6 +19234,16 @@ type Mutation { input: UpdateRepositoryInput! ): UpdateRepositoryPayload + """ + Sets whether contributors are required to sign off on web-based commits for a repository. + """ + updateRepositoryWebCommitSignoffSetting( + """ + Parameters for UpdateRepositoryWebCommitSignoffSetting + """ + input: UpdateRepositoryWebCommitSignoffSettingInput! + ): UpdateRepositoryWebCommitSignoffSettingPayload + """ Updates the state for subscribable subjects. """ @@ -21093,6 +21569,11 @@ enum OrgRemoveMemberAuditEntryMembershipType { """ OUTSIDE_COLLABORATOR + """ + A suspended member. + """ + SUSPENDED + """ An unaffiliated collaborator is a person who is not a member of the Organization and does not have access to any repositories in the Organization. @@ -22076,7 +22557,7 @@ type OrgUpdateMemberRepositoryInvitationPermissionAuditEntry implements AuditEnt """ An account on GitHub, with one or more owners, that has repositories, members and teams. """ -type Organization implements Actor & MemberStatusable & Node & PackageOwner & ProfileOwner & ProjectOwner & RepositoryDiscussionAuthor & RepositoryDiscussionCommentAuthor & RepositoryOwner & UniformResourceLocatable { +type Organization implements Actor & MemberStatusable & Node & PackageOwner & ProfileOwner & ProjectOwner & ProjectV2Owner & ProjectV2Recent & RepositoryDiscussionAuthor & RepositoryDiscussionCommentAuthor & RepositoryOwner & UniformResourceLocatable { """ Determine if this repository owner has any items that can be pinned to their profile. """ @@ -22529,6 +23010,16 @@ type Organization implements Actor & MemberStatusable & Node & PackageOwner & Pr number: Int! ): Project + """ + Find a project by number. + """ + projectV2( + """ + The project number. + """ + number: Int! + ): ProjectV2 + """ A list of projects under the owner. """ @@ -22579,6 +23070,66 @@ type Organization implements Actor & MemberStatusable & Node & PackageOwner & Pr """ projectsUrl: URI! + """ + A list of projects under the owner. + """ + projectsV2( + """ + Returns the elements in the list that come after the specified cursor. + """ + after: String + + """ + Returns the elements in the list that come before the specified cursor. + """ + before: String + + """ + Returns the first _n_ elements from the list. + """ + first: Int + + """ + Returns the last _n_ elements from the list. + """ + last: Int + + """ + How to order the returned projects. + """ + orderBy: ProjectV2Order = {field: NUMBER, direction: DESC} + + """ + A project to search for under the the owner. + """ + query: String + ): ProjectV2Connection! + + """ + Recent projects that this user has modified in the context of the owner. + """ + recentProjects( + """ + Returns the elements in the list that come after the specified cursor. + """ + after: String + + """ + Returns the elements in the list that come before the specified cursor. + """ + before: String + + """ + Returns the first _n_ elements from the list. + """ + first: Int + + """ + Returns the last _n_ elements from the list. + """ + last: Int + ): ProjectV2Connection! + """ A list of repositories that the user owns. """ @@ -22915,6 +23466,11 @@ type Organization implements Actor & MemberStatusable & Node & PackageOwner & Pr """ viewerIsFollowing: Boolean! + """ + Whether contributors are required to sign off on web-based commits for repositories in this organization. + """ + webCommitSignoffRequired: Boolean! + """ The organization's public profile URL. """ @@ -23421,6 +23977,11 @@ enum OrganizationMembersCanCreateRepositoriesSettingValue { PRIVATE } +""" +Used for argument of CreateProjectV2 mutation. +""" +union OrganizationOrUser = Organization | User + """ Ordering options for organization connections. """ @@ -25621,6 +26182,1842 @@ enum ProjectTemplate { BUG_TRIAGE } +""" +New projects that manage issues, pull requests and drafts using tables and boards. +""" +type ProjectV2 implements Closable & Node & Updatable { + """ + Returns true if the project is closed. + """ + closed: Boolean! + + """ + Identifies the date and time when the object was closed. + """ + closedAt: DateTime + + """ + Identifies the date and time when the object was created. + """ + createdAt: DateTime! + + """ + The actor who originally created the project. + """ + creator: Actor + + """ + Identifies the primary key from the database. + """ + databaseId: Int + + """ + A field of the project + """ + field( + """ + The name of the field + """ + name: String! + ): ProjectV2FieldConfiguration + + """ + List of fields and their constraints in the project + """ + fields( + """ + Returns the elements in the list that come after the specified cursor. + """ + after: String + + """ + Returns the elements in the list that come before the specified cursor. + """ + before: String + + """ + Returns the first _n_ elements from the list. + """ + first: Int + + """ + Returns the last _n_ elements from the list. + """ + last: Int + + """ + Ordering options for project v2 fields returned from the connection + """ + orderBy: ProjectV2FieldOrder = {field: POSITION, direction: ASC} + ): ProjectV2FieldConfigurationConnection! + id: ID! + + """ + List of items in the project + """ + items( + """ + Returns the elements in the list that come after the specified cursor. + """ + after: String + + """ + Returns the elements in the list that come before the specified cursor. + """ + before: String + + """ + Returns the first _n_ elements from the list. + """ + first: Int + + """ + Returns the last _n_ elements from the list. + """ + last: Int + + """ + Ordering options for project v2 items returned from the connection + """ + orderBy: ProjectV2ItemOrder = {field: POSITION, direction: ASC} + ): ProjectV2ItemConnection! + + """ + The project's number. + """ + number: Int! + + """ + The project's owner. Currently limited to organizations and users. + """ + owner: ProjectV2Owner! + + """ + Returns true if the project is public. + """ + public: Boolean! + + """ + The project's readme. + """ + readme: String + + """ + The repositories the project is linked to. + """ + repositories( + """ + Returns the elements in the list that come after the specified cursor. + """ + after: String + + """ + Returns the elements in the list that come before the specified cursor. + """ + before: String + + """ + Returns the first _n_ elements from the list. + """ + first: Int + + """ + Returns the last _n_ elements from the list. + """ + last: Int + + """ + Ordering options for repositories returned from the connection + """ + orderBy: RepositoryOrder = {field: CREATED_AT, direction: DESC} + ): RepositoryConnection! + + """ + The HTTP path for this project + """ + resourcePath: URI! + + """ + The project's short description. + """ + shortDescription: String + + """ + The project's name. + """ + title: String! + + """ + Identifies the date and time when the object was last updated. + """ + updatedAt: DateTime! + + """ + The HTTP URL for this project + """ + url: URI! + + """ + Check if the current viewer can update this object. + """ + viewerCanUpdate: Boolean! + + """ + List of views in the project + """ + views( + """ + Returns the elements in the list that come after the specified cursor. + """ + after: String + + """ + Returns the elements in the list that come before the specified cursor. + """ + before: String + + """ + Returns the first _n_ elements from the list. + """ + first: Int + + """ + Returns the last _n_ elements from the list. + """ + last: Int + + """ + Ordering options for project v2 views returned from the connection + """ + orderBy: ProjectV2ViewOrder = {field: POSITION, direction: ASC} + ): ProjectV2ViewConnection! +} + +""" +The connection type for ProjectV2. +""" +type ProjectV2Connection { + """ + A list of edges. + """ + edges: [ProjectV2Edge] + + """ + A list of nodes. + """ + nodes: [ProjectV2] + + """ + Information to aid in pagination. + """ + pageInfo: PageInfo! + + """ + Identifies the total count of items in the connection. + """ + totalCount: Int! +} + +""" +An edge in a connection. +""" +type ProjectV2Edge { + """ + A cursor for use in pagination. + """ + cursor: String! + + """ + The item at the end of the edge. + """ + node: ProjectV2 +} + +""" +A field inside a project. +""" +type ProjectV2Field implements Node & ProjectV2FieldCommon { + """ + Identifies the date and time when the object was created. + """ + createdAt: DateTime! + + """ + The field's type. + """ + dataType: ProjectV2FieldType! + + """ + Identifies the primary key from the database. + """ + databaseId: Int + id: ID! + + """ + The project field's name. + """ + name: String! + + """ + The project that contains this field. + """ + project: ProjectV2! + + """ + Identifies the date and time when the object was last updated. + """ + updatedAt: DateTime! +} + +""" +Common fields across different project field types +""" +interface ProjectV2FieldCommon { + """ + Identifies the date and time when the object was created. + """ + createdAt: DateTime! + + """ + The field's type. + """ + dataType: ProjectV2FieldType! + + """ + Identifies the primary key from the database. + """ + databaseId: Int + id: ID! + + """ + The project field's name. + """ + name: String! + + """ + The project that contains this field. + """ + project: ProjectV2! + + """ + Identifies the date and time when the object was last updated. + """ + updatedAt: DateTime! +} + +""" +Configurations for project fields. +""" +union ProjectV2FieldConfiguration = ProjectV2Field | ProjectV2IterationField | ProjectV2SingleSelectField + +""" +The connection type for ProjectV2FieldConfiguration. +""" +type ProjectV2FieldConfigurationConnection { + """ + A list of edges. + """ + edges: [ProjectV2FieldConfigurationEdge] + + """ + A list of nodes. + """ + nodes: [ProjectV2FieldConfiguration] + + """ + Information to aid in pagination. + """ + pageInfo: PageInfo! + + """ + Identifies the total count of items in the connection. + """ + totalCount: Int! +} + +""" +An edge in a connection. +""" +type ProjectV2FieldConfigurationEdge { + """ + A cursor for use in pagination. + """ + cursor: String! + + """ + The item at the end of the edge. + """ + node: ProjectV2FieldConfiguration +} + +""" +The connection type for ProjectV2Field. +""" +type ProjectV2FieldConnection { + """ + A list of edges. + """ + edges: [ProjectV2FieldEdge] + + """ + A list of nodes. + """ + nodes: [ProjectV2Field] + + """ + Information to aid in pagination. + """ + pageInfo: PageInfo! + + """ + Identifies the total count of items in the connection. + """ + totalCount: Int! +} + +""" +An edge in a connection. +""" +type ProjectV2FieldEdge { + """ + A cursor for use in pagination. + """ + cursor: String! + + """ + The item at the end of the edge. + """ + node: ProjectV2Field +} + +""" +Ordering options for project v2 field connections +""" +input ProjectV2FieldOrder { + """ + The ordering direction. + """ + direction: OrderDirection! + + """ + The field to order the project v2 fields by. + """ + field: ProjectV2FieldOrderField! +} + +""" +Properties by which project v2 field connections can be ordered. +""" +enum ProjectV2FieldOrderField { + """ + Order project v2 fields by creation time + """ + CREATED_AT + + """ + Order project v2 fields by name + """ + NAME + + """ + Order project v2 fields by position + """ + POSITION +} + +""" +The type of a project field. +""" +enum ProjectV2FieldType { + """ + Assignees + """ + ASSIGNEES + + """ + Date + """ + DATE + + """ + Iteration + """ + ITERATION + + """ + Labels + """ + LABELS + + """ + Linked Pull Requests + """ + LINKED_PULL_REQUESTS + + """ + Milestone + """ + MILESTONE + + """ + Number + """ + NUMBER + + """ + Repository + """ + REPOSITORY + + """ + Reviewers + """ + REVIEWERS + + """ + Single Select + """ + SINGLE_SELECT + + """ + Text + """ + TEXT + + """ + Title + """ + TITLE + + """ + Tracks + """ + TRACKS +} + +""" +The values that can be used to update a field of an item inside a Project. Only 1 value can be updated at a time. +""" +input ProjectV2FieldValue { + """ + The ISO 8601 date to set on the field. + """ + date: Date + + """ + The id of the iteration to set on the field. + """ + iterationId: String + + """ + The number to set on the field. + """ + number: Float + + """ + The id of the single select option to set on the field. + """ + singleSelectOptionId: String + + """ + The text to set on the field. + """ + text: String +} + +""" +An item within a Project. +""" +type ProjectV2Item implements Node { + """ + The content of the referenced draft issue, issue, or pull request + """ + content: ProjectV2ItemContent + + """ + Identifies the date and time when the object was created. + """ + createdAt: DateTime! + + """ + The actor who created the item. + """ + creator: Actor + + """ + Identifies the primary key from the database. + """ + databaseId: Int + + """ + A specific field value given a field name + """ + fieldValueByName( + """ + The name of the field to return the field value of + """ + name: String! + ): ProjectV2ItemFieldValue + + """ + List of field values + """ + fieldValues( + """ + Returns the elements in the list that come after the specified cursor. + """ + after: String + + """ + Returns the elements in the list that come before the specified cursor. + """ + before: String + + """ + Returns the first _n_ elements from the list. + """ + first: Int + + """ + Returns the last _n_ elements from the list. + """ + last: Int + + """ + Ordering options for project v2 item field values returned from the connection + """ + orderBy: ProjectV2ItemFieldValueOrder = {field: POSITION, direction: ASC} + ): ProjectV2ItemFieldValueConnection! + id: ID! + + """ + Whether the item is archived. + """ + isArchived: Boolean! + + """ + The project that contains this item. + """ + project: ProjectV2! + + """ + The type of the item. + """ + type: ProjectV2ItemType! + + """ + Identifies the date and time when the object was last updated. + """ + updatedAt: DateTime! +} + +""" +The connection type for ProjectV2Item. +""" +type ProjectV2ItemConnection { + """ + A list of edges. + """ + edges: [ProjectV2ItemEdge] + + """ + A list of nodes. + """ + nodes: [ProjectV2Item] + + """ + Information to aid in pagination. + """ + pageInfo: PageInfo! + + """ + Identifies the total count of items in the connection. + """ + totalCount: Int! +} + +""" +Types that can be inside Project Items. +""" +union ProjectV2ItemContent = DraftIssue | Issue | PullRequest + +""" +An edge in a connection. +""" +type ProjectV2ItemEdge { + """ + A cursor for use in pagination. + """ + cursor: String! + + """ + The item at the end of the edge. + """ + node: ProjectV2Item +} + +""" +The value of a date field in a Project item. +""" +type ProjectV2ItemFieldDateValue implements Node & ProjectV2ItemFieldValueCommon { + """ + Identifies the date and time when the object was created. + """ + createdAt: DateTime! + + """ + The actor who created the item. + """ + creator: Actor + + """ + Identifies the primary key from the database. + """ + databaseId: Int + + """ + Date value for the field + """ + date: Date + + """ + The project field that contains this value. + """ + field: ProjectV2FieldConfiguration! + id: ID! + + """ + The project item that contains this value. + """ + item: ProjectV2Item! + + """ + Identifies the date and time when the object was last updated. + """ + updatedAt: DateTime! +} + +""" +The value of an iteration field in a Project item. +""" +type ProjectV2ItemFieldIterationValue implements Node & ProjectV2ItemFieldValueCommon { + """ + Identifies the date and time when the object was created. + """ + createdAt: DateTime! + + """ + The actor who created the item. + """ + creator: Actor + + """ + Identifies the primary key from the database. + """ + databaseId: Int + + """ + The duration of the iteration in days. + """ + duration: Int! + + """ + The project field that contains this value. + """ + field: ProjectV2FieldConfiguration! + id: ID! + + """ + The project item that contains this value. + """ + item: ProjectV2Item! + + """ + The ID of the iteration. + """ + iterationId: String! + + """ + The start date of the iteration. + """ + startDate: Date! + + """ + The title of the iteration. + """ + title: String! + + """ + The title of the iteration, with HTML. + """ + titleHTML: String! + + """ + Identifies the date and time when the object was last updated. + """ + updatedAt: DateTime! +} + +""" +The value of the labels field in a Project item. +""" +type ProjectV2ItemFieldLabelValue { + """ + The field that contains this value. + """ + field: ProjectV2FieldConfiguration! + + """ + Labels value of a field + """ + labels( + """ + Returns the elements in the list that come after the specified cursor. + """ + after: String + + """ + Returns the elements in the list that come before the specified cursor. + """ + before: String + + """ + Returns the first _n_ elements from the list. + """ + first: Int + + """ + Returns the last _n_ elements from the list. + """ + last: Int + ): LabelConnection +} + +""" +The value of a milestone field in a Project item. +""" +type ProjectV2ItemFieldMilestoneValue { + """ + The field that contains this value. + """ + field: ProjectV2FieldConfiguration! + + """ + Milestone value of a field + """ + milestone: Milestone +} + +""" +The value of a number field in a Project item. +""" +type ProjectV2ItemFieldNumberValue implements Node & ProjectV2ItemFieldValueCommon { + """ + Identifies the date and time when the object was created. + """ + createdAt: DateTime! + + """ + The actor who created the item. + """ + creator: Actor + + """ + Identifies the primary key from the database. + """ + databaseId: Int + + """ + The project field that contains this value. + """ + field: ProjectV2FieldConfiguration! + id: ID! + + """ + The project item that contains this value. + """ + item: ProjectV2Item! + + """ + Number as a float(8) + """ + number: Float + + """ + Identifies the date and time when the object was last updated. + """ + updatedAt: DateTime! +} + +""" +The value of a pull request field in a Project item. +""" +type ProjectV2ItemFieldPullRequestValue { + """ + The field that contains this value. + """ + field: ProjectV2FieldConfiguration! + + """ + The pull requests for this field + """ + pullRequests( + """ + Returns the elements in the list that come after the specified cursor. + """ + after: String + + """ + Returns the elements in the list that come before the specified cursor. + """ + before: String + + """ + Returns the first _n_ elements from the list. + """ + first: Int + + """ + Returns the last _n_ elements from the list. + """ + last: Int + + """ + Ordering options for pull requests. + """ + orderBy: PullRequestOrder = {field: CREATED_AT, direction: ASC} + ): PullRequestConnection +} + +""" +The value of a repository field in a Project item. +""" +type ProjectV2ItemFieldRepositoryValue { + """ + The field that contains this value. + """ + field: ProjectV2FieldConfiguration! + + """ + The repository for this field. + """ + repository: Repository +} + +""" +The value of a reviewers field in a Project item. +""" +type ProjectV2ItemFieldReviewerValue { + """ + The field that contains this value. + """ + field: ProjectV2FieldConfiguration! + + """ + The reviewers for this field. + """ + reviewers( + """ + Returns the elements in the list that come after the specified cursor. + """ + after: String + + """ + Returns the elements in the list that come before the specified cursor. + """ + before: String + + """ + Returns the first _n_ elements from the list. + """ + first: Int + + """ + Returns the last _n_ elements from the list. + """ + last: Int + ): RequestedReviewerConnection +} + +""" +The value of a single select field in a Project item. +""" +type ProjectV2ItemFieldSingleSelectValue implements Node & ProjectV2ItemFieldValueCommon { + """ + Identifies the date and time when the object was created. + """ + createdAt: DateTime! + + """ + The actor who created the item. + """ + creator: Actor + + """ + Identifies the primary key from the database. + """ + databaseId: Int + + """ + The project field that contains this value. + """ + field: ProjectV2FieldConfiguration! + id: ID! + + """ + The project item that contains this value. + """ + item: ProjectV2Item! + + """ + The name of the selected single select option. + """ + name: String + + """ + The html name of the selected single select option. + """ + nameHTML: String + + """ + The id of the selected single select option. + """ + optionId: String + + """ + Identifies the date and time when the object was last updated. + """ + updatedAt: DateTime! +} + +""" +The value of a text field in a Project item. +""" +type ProjectV2ItemFieldTextValue implements Node & ProjectV2ItemFieldValueCommon { + """ + Identifies the date and time when the object was created. + """ + createdAt: DateTime! + + """ + The actor who created the item. + """ + creator: Actor + + """ + Identifies the primary key from the database. + """ + databaseId: Int + + """ + The project field that contains this value. + """ + field: ProjectV2FieldConfiguration! + id: ID! + + """ + The project item that contains this value. + """ + item: ProjectV2Item! + + """ + Text value of a field + """ + text: String + + """ + Identifies the date and time when the object was last updated. + """ + updatedAt: DateTime! +} + +""" +The value of a user field in a Project item. +""" +type ProjectV2ItemFieldUserValue { + """ + The field that contains this value. + """ + field: ProjectV2FieldConfiguration! + + """ + The users for this field + """ + users( + """ + Returns the elements in the list that come after the specified cursor. + """ + after: String + + """ + Returns the elements in the list that come before the specified cursor. + """ + before: String + + """ + Returns the first _n_ elements from the list. + """ + first: Int + + """ + Returns the last _n_ elements from the list. + """ + last: Int + ): UserConnection +} + +""" +Project field values +""" +union ProjectV2ItemFieldValue = + ProjectV2ItemFieldDateValue + | ProjectV2ItemFieldIterationValue + | ProjectV2ItemFieldLabelValue + | ProjectV2ItemFieldMilestoneValue + | ProjectV2ItemFieldNumberValue + | ProjectV2ItemFieldPullRequestValue + | ProjectV2ItemFieldRepositoryValue + | ProjectV2ItemFieldReviewerValue + | ProjectV2ItemFieldSingleSelectValue + | ProjectV2ItemFieldTextValue + | ProjectV2ItemFieldUserValue + +""" +Common fields across different project field value types +""" +interface ProjectV2ItemFieldValueCommon { + """ + Identifies the date and time when the object was created. + """ + createdAt: DateTime! + + """ + The actor who created the item. + """ + creator: Actor + + """ + Identifies the primary key from the database. + """ + databaseId: Int + + """ + The project field that contains this value. + """ + field: ProjectV2FieldConfiguration! + id: ID! + + """ + The project item that contains this value. + """ + item: ProjectV2Item! + + """ + Identifies the date and time when the object was last updated. + """ + updatedAt: DateTime! +} + +""" +The connection type for ProjectV2ItemFieldValue. +""" +type ProjectV2ItemFieldValueConnection { + """ + A list of edges. + """ + edges: [ProjectV2ItemFieldValueEdge] + + """ + A list of nodes. + """ + nodes: [ProjectV2ItemFieldValue] + + """ + Information to aid in pagination. + """ + pageInfo: PageInfo! + + """ + Identifies the total count of items in the connection. + """ + totalCount: Int! +} + +""" +An edge in a connection. +""" +type ProjectV2ItemFieldValueEdge { + """ + A cursor for use in pagination. + """ + cursor: String! + + """ + The item at the end of the edge. + """ + node: ProjectV2ItemFieldValue +} + +""" +Ordering options for project v2 item field value connections +""" +input ProjectV2ItemFieldValueOrder { + """ + The ordering direction. + """ + direction: OrderDirection! + + """ + The field to order the project v2 item field values by. + """ + field: ProjectV2ItemFieldValueOrderField! +} + +""" +Properties by which project v2 item field value connections can be ordered. +""" +enum ProjectV2ItemFieldValueOrderField { + """ + Order project v2 item field values by the their position in the project + """ + POSITION +} + +""" +Ordering options for project v2 item connections +""" +input ProjectV2ItemOrder { + """ + The ordering direction. + """ + direction: OrderDirection! + + """ + The field to order the project v2 items by. + """ + field: ProjectV2ItemOrderField! +} + +""" +Properties by which project v2 item connections can be ordered. +""" +enum ProjectV2ItemOrderField { + """ + Order project v2 items by the their position in the project + """ + POSITION +} + +""" +The type of a project item. +""" +enum ProjectV2ItemType { + """ + Draft Issue + """ + DRAFT_ISSUE + + """ + Issue + """ + ISSUE + + """ + Pull Request + """ + PULL_REQUEST + + """ + Redacted Item + """ + REDACTED +} + +""" +An iteration field inside a project. +""" +type ProjectV2IterationField implements Node & ProjectV2FieldCommon { + """ + Iteration configuration settings + """ + configuration: ProjectV2IterationFieldConfiguration! + + """ + Identifies the date and time when the object was created. + """ + createdAt: DateTime! + + """ + The field's type. + """ + dataType: ProjectV2FieldType! + + """ + Identifies the primary key from the database. + """ + databaseId: Int + id: ID! + + """ + The project field's name. + """ + name: String! + + """ + The project that contains this field. + """ + project: ProjectV2! + + """ + Identifies the date and time when the object was last updated. + """ + updatedAt: DateTime! +} + +""" +Iteration field configuration for a project. +""" +type ProjectV2IterationFieldConfiguration { + """ + The iteration's completed iterations + """ + completedIterations: [ProjectV2IterationFieldIteration!]! + + """ + The iteration's duration in days + """ + duration: Int! + + """ + The iteration's iterations + """ + iterations: [ProjectV2IterationFieldIteration!]! + + """ + The iteration's start day of the week + """ + startDay: Int! +} + +""" +Iteration field iteration settings for a project. +""" +type ProjectV2IterationFieldIteration { + """ + The iteration's duration in days + """ + duration: Int! + + """ + The iteration's ID. + """ + id: String! + + """ + The iteration's start date + """ + startDate: Date! + + """ + The iteration's title. + """ + title: String! + + """ + The iteration's html title. + """ + titleHTML: String! +} + +""" +Ways in which lists of projects can be ordered upon return. +""" +input ProjectV2Order { + """ + The direction in which to order projects by the specified field. + """ + direction: OrderDirection! + + """ + The field in which to order projects by. + """ + field: ProjectV2OrderField! +} + +""" +Properties by which projects can be ordered. +""" +enum ProjectV2OrderField { + """ + The project's date and time of creation + """ + CREATED_AT + + """ + The project's number + """ + NUMBER + + """ + The project's title + """ + TITLE + + """ + The project's date and time of update + """ + UPDATED_AT +} + +""" +Represents an owner of a project (beta). +""" +interface ProjectV2Owner { + id: ID! + + """ + Find a project by number. + """ + projectV2( + """ + The project number. + """ + number: Int! + ): ProjectV2 + + """ + A list of projects under the owner. + """ + projectsV2( + """ + Returns the elements in the list that come after the specified cursor. + """ + after: String + + """ + Returns the elements in the list that come before the specified cursor. + """ + before: String + + """ + Returns the first _n_ elements from the list. + """ + first: Int + + """ + Returns the last _n_ elements from the list. + """ + last: Int + + """ + How to order the returned projects. + """ + orderBy: ProjectV2Order = {field: NUMBER, direction: DESC} + + """ + A project to search for under the the owner. + """ + query: String + ): ProjectV2Connection! +} + +""" +Recent projects for the owner. +""" +interface ProjectV2Recent { + """ + Recent projects that this user has modified in the context of the owner. + """ + recentProjects( + """ + Returns the elements in the list that come after the specified cursor. + """ + after: String + + """ + Returns the elements in the list that come before the specified cursor. + """ + before: String + + """ + Returns the first _n_ elements from the list. + """ + first: Int + + """ + Returns the last _n_ elements from the list. + """ + last: Int + ): ProjectV2Connection! +} + +""" +A single select field inside a project. +""" +type ProjectV2SingleSelectField implements Node & ProjectV2FieldCommon { + """ + Identifies the date and time when the object was created. + """ + createdAt: DateTime! + + """ + The field's type. + """ + dataType: ProjectV2FieldType! + + """ + Identifies the primary key from the database. + """ + databaseId: Int + id: ID! + + """ + The project field's name. + """ + name: String! + + """ + Options for the single select field + """ + options: [ProjectV2SingleSelectFieldOption!]! + + """ + The project that contains this field. + """ + project: ProjectV2! + + """ + Identifies the date and time when the object was last updated. + """ + updatedAt: DateTime! +} + +""" +Single select field option for a configuration for a project. +""" +type ProjectV2SingleSelectFieldOption { + """ + The option's ID. + """ + id: String! + + """ + The option's name. + """ + name: String! + + """ + The option's html name. + """ + nameHTML: String! +} + +""" +Represents a sort by field and direction. +""" +type ProjectV2SortBy { + """ + The direction of the sorting. Possible values are ASC and DESC. + """ + direction: OrderDirection! + + """ + The field by which items are sorted. + """ + field: ProjectV2Field! +} + +""" +The connection type for ProjectV2SortBy. +""" +type ProjectV2SortByConnection { + """ + A list of edges. + """ + edges: [ProjectV2SortByEdge] + + """ + A list of nodes. + """ + nodes: [ProjectV2SortBy] + + """ + Information to aid in pagination. + """ + pageInfo: PageInfo! + + """ + Identifies the total count of items in the connection. + """ + totalCount: Int! +} + +""" +An edge in a connection. +""" +type ProjectV2SortByEdge { + """ + A cursor for use in pagination. + """ + cursor: String! + + """ + The item at the end of the edge. + """ + node: ProjectV2SortBy +} + +""" +A view within a ProjectV2. +""" +type ProjectV2View implements Node { + """ + Identifies the date and time when the object was created. + """ + createdAt: DateTime! + + """ + Identifies the primary key from the database. + """ + databaseId: Int + + """ + The project view's filter. + """ + filter: String + + """ + The view's group-by field. + """ + groupBy( + """ + Returns the elements in the list that come after the specified cursor. + """ + after: String + + """ + Returns the elements in the list that come before the specified cursor. + """ + before: String + + """ + Returns the first _n_ elements from the list. + """ + first: Int + + """ + Returns the last _n_ elements from the list. + """ + last: Int + + """ + Ordering options for the project v2 fields returned from the connection. + """ + orderBy: ProjectV2FieldOrder = {field: POSITION, direction: ASC} + ): ProjectV2FieldConnection + id: ID! + + """ + The project view's layout. + """ + layout: ProjectV2ViewLayout! + + """ + The project view's name. + """ + name: String! + + """ + The project view's number. + """ + number: Int! + + """ + The project that contains this view. + """ + project: ProjectV2! + + """ + The view's sort-by config. + """ + sortBy( + """ + Returns the elements in the list that come after the specified cursor. + """ + after: String + + """ + Returns the elements in the list that come before the specified cursor. + """ + before: String + + """ + Returns the first _n_ elements from the list. + """ + first: Int + + """ + Returns the last _n_ elements from the list. + """ + last: Int + ): ProjectV2SortByConnection + + """ + Identifies the date and time when the object was last updated. + """ + updatedAt: DateTime! + + """ + The view's vertical-group-by field. + """ + verticalGroupBy( + """ + Returns the elements in the list that come after the specified cursor. + """ + after: String + + """ + Returns the elements in the list that come before the specified cursor. + """ + before: String + + """ + Returns the first _n_ elements from the list. + """ + first: Int + + """ + Returns the last _n_ elements from the list. + """ + last: Int + + """ + Ordering options for the project v2 fields returned from the connection. + """ + orderBy: ProjectV2FieldOrder = {field: POSITION, direction: ASC} + ): ProjectV2FieldConnection + + """ + The view's visible fields. + """ + visibleFields( + """ + Returns the elements in the list that come after the specified cursor. + """ + after: String + + """ + Returns the elements in the list that come before the specified cursor. + """ + before: String + + """ + Returns the first _n_ elements from the list. + """ + first: Int + + """ + Returns the last _n_ elements from the list. + """ + last: Int + + """ + Ordering options for the project v2 fields returned from the connection. + """ + orderBy: ProjectV2FieldOrder = {field: POSITION, direction: ASC} + ): ProjectV2FieldConnection +} + +""" +The connection type for ProjectV2View. +""" +type ProjectV2ViewConnection { + """ + A list of edges. + """ + edges: [ProjectV2ViewEdge] + + """ + A list of nodes. + """ + nodes: [ProjectV2View] + + """ + Information to aid in pagination. + """ + pageInfo: PageInfo! + + """ + Identifies the total count of items in the connection. + """ + totalCount: Int! +} + +""" +An edge in a connection. +""" +type ProjectV2ViewEdge { + """ + A cursor for use in pagination. + """ + cursor: String! + + """ + The item at the end of the edge. + """ + node: ProjectV2View +} + +""" +The layout of a project v2 view. +""" +enum ProjectV2ViewLayout { + """ + Board layout + """ + BOARD_LAYOUT + + """ + Table layout + """ + TABLE_LAYOUT +} + +""" +Ordering options for project v2 view connections +""" +input ProjectV2ViewOrder { + """ + The ordering direction. + """ + direction: OrderDirection! + + """ + The field to order the project v2 views by. + """ + field: ProjectV2ViewOrderField! +} + +""" +Properties by which project v2 view connections can be ordered. +""" +enum ProjectV2ViewOrderField { + """ + Order project v2 views by creation time + """ + CREATED_AT + + """ + Order project v2 views by name + """ + NAME + + """ + Order project v2 views by position + """ + POSITION +} + """ A user's public key. """ @@ -25703,7 +28100,7 @@ type PublicKeyEdge { """ A repository pull request. """ -type PullRequest implements Assignable & Closable & Comment & Labelable & Lockable & Node & Reactable & RepositoryNode & Subscribable & UniformResourceLocatable & Updatable & UpdatableComment { +type PullRequest implements Assignable & Closable & Comment & Labelable & Lockable & Node & ProjectV2Owner & Reactable & RepositoryNode & Subscribable & UniformResourceLocatable & Updatable & UpdatableComment { """ Reason that the conversation was locked. """ @@ -26223,6 +28620,51 @@ type PullRequest implements Assignable & Closable & Comment & Labelable & Lockab last: Int ): ProjectCardConnection! + """ + Find a project by number. + """ + projectV2( + """ + The project number. + """ + number: Int! + ): ProjectV2 + + """ + A list of projects under the owner. + """ + projectsV2( + """ + Returns the elements in the list that come after the specified cursor. + """ + after: String + + """ + Returns the elements in the list that come before the specified cursor. + """ + before: String + + """ + Returns the first _n_ elements from the list. + """ + first: Int + + """ + Returns the last _n_ elements from the list. + """ + last: Int + + """ + How to order the returned projects. + """ + orderBy: ProjectV2Order = {field: NUMBER, direction: DESC} + + """ + A project to search for under the the owner. + """ + query: String + ): ProjectV2Connection! + """ Identifies when the comment was published at. """ @@ -26519,6 +28961,11 @@ type PullRequest implements Assignable & Closable & Comment & Labelable & Lockab """ viewerCanDisableAutoMerge: Boolean! + """ + Can the viewer edit files within this pull request. + """ + viewerCanEditFiles: Boolean! + """ Whether or not the viewer can enable auto-merge """ @@ -27244,7 +29691,9 @@ type PullRequestReviewComment implements Comment & Deletable & Minimizable & Nod lastEditedAt: DateTime """ - Returns why the comment was minimized. + Returns why the comment was minimized. One of `abuse`, `off-topic`, + `outdated`, `resolved`, `duplicate` and `spam`. Note that the case and + formatting of these values differs from the inputs to the `MinimizeComment` mutation. """ minimizedReason: String @@ -27840,6 +30289,87 @@ type PullRequestTemplate { repository: Repository! } +""" +A threaded list of comments for a given pull request. +""" +type PullRequestThread implements Node { + """ + A list of pull request comments associated with the thread. + """ + comments( + """ + Returns the elements in the list that come after the specified cursor. + """ + after: String + + """ + Returns the elements in the list that come before the specified cursor. + """ + before: String + + """ + Returns the first _n_ elements from the list. + """ + first: Int + + """ + Returns the last _n_ elements from the list. + """ + last: Int + + """ + Skips the first _n_ elements in the list. + """ + skip: Int + ): PullRequestReviewCommentConnection! + id: ID! + + """ + Whether or not the thread has been collapsed (resolved) + """ + isCollapsed: Boolean! + + """ + Indicates whether this thread was outdated by newer changes. + """ + isOutdated: Boolean! + + """ + Whether this thread has been resolved + """ + isResolved: Boolean! + + """ + Identifies the pull request associated with this thread. + """ + pullRequest: PullRequest! + + """ + Identifies the repository associated with this thread. + """ + repository: Repository! + + """ + The user who resolved this thread + """ + resolvedBy: User + + """ + Indicates whether the current viewer can reply to this thread. + """ + viewerCanReply: Boolean! + + """ + Whether or not the viewer can resolve this thread + """ + viewerCanResolve: Boolean! + + """ + Whether or not the viewer can unresolve this thread + """ + viewerCanUnresolve: Boolean! +} + """ The connection type for PullRequestTimelineItem. """ @@ -32719,7 +35249,7 @@ enum ReportedContentClassifiers { """ A repository contains the content for a project. """ -type Repository implements Node & PackageOwner & ProjectOwner & RepositoryInfo & Starrable & Subscribable & UniformResourceLocatable { +type Repository implements Node & PackageOwner & ProjectOwner & ProjectV2Recent & RepositoryInfo & Starrable & Subscribable & UniformResourceLocatable { """ Whether or not a pull request head branch that is behind its base branch can always be updated even if it is not required to be up to date before merging. @@ -32996,6 +35526,16 @@ type Repository implements Node & PackageOwner & ProjectOwner & RepositoryInfo & last: Int ): DiscussionCategoryConnection! + """ + A discussion category by slug. + """ + discussionCategory( + """ + The slug of the discussion category to be returned. + """ + slug: String! + ): DiscussionCategory + """ A list of discussions that have been opened in the repository. """ @@ -33416,6 +35956,16 @@ type Repository implements Node & PackageOwner & ProjectOwner & RepositoryInfo & """ mergeCommitAllowed: Boolean! + """ + How the default commit message will be generated when merging a pull request. + """ + mergeCommitMessage: MergeCommitMessage! + + """ + How the default commit title will be generated when merging a pull request. + """ + mergeCommitTitle: MergeCommitTitle! + """ Returns a single milestone from the current repository by number. """ @@ -33746,6 +36296,31 @@ type Repository implements Node & PackageOwner & ProjectOwner & RepositoryInfo & """ rebaseMergeAllowed: Boolean! + """ + Recent projects that this user has modified in the context of the owner. + """ + recentProjects( + """ + Returns the elements in the list that come after the specified cursor. + """ + after: String + + """ + Returns the elements in the list that come before the specified cursor. + """ + before: String + + """ + Returns the first _n_ elements from the list. + """ + first: Int + + """ + Returns the last _n_ elements from the list. + """ + last: Int + ): ProjectV2Connection! + """ Fetch a given ref from the repository """ @@ -33892,6 +36467,16 @@ type Repository implements Node & PackageOwner & ProjectOwner & RepositoryInfo & """ squashMergeAllowed: Boolean! + """ + How the default commit message will be generated when squash merging a pull request. + """ + squashMergeCommitMessage: SquashMergeCommitMessage! + + """ + How the default commit title will be generated when squash merging a pull request. + """ + squashMergeCommitTitle: SquashMergeCommitTitle! + """ Whether a squash merge commit can use the pull request title as default. """ @@ -34057,6 +36642,11 @@ type Repository implements Node & PackageOwner & ProjectOwner & RepositoryInfo & """ before: String + """ + Filter by the scope of the alert's dependency + """ + dependencyScopes: [RepositoryVulnerabilityAlertDependencyScope!] + """ Returns the first _n_ elements from the list. """ @@ -34097,6 +36687,11 @@ type Repository implements Node & PackageOwner & ProjectOwner & RepositoryInfo & """ last: Int ): UserConnection! + + """ + Whether contributors are required to sign off on web-based commits in this repository. + """ + webCommitSignoffRequired: Boolean! } """ @@ -35348,6 +37943,16 @@ type RepositoryVulnerabilityAlert implements Node & RepositoryNode { """ dependabotUpdate: DependabotUpdate + """ + The scope of an alert's dependency + """ + dependencyScope: RepositoryVulnerabilityAlertDependencyScope + + """ + Comment explaining the reason the alert was dismissed + """ + dismissComment: String + """ The reason the alert was dismissed """ @@ -35367,6 +37972,9 @@ type RepositoryVulnerabilityAlert implements Node & RepositoryNode { The reason the alert was marked as fixed. """ fixReason: String + @deprecated( + reason: "The `fixReason` field is being removed. You can still use `fixedAt` and `dismissReason`. Removal on 2022-10-01 UTC." + ) """ When was the alert fixed? @@ -35440,6 +38048,21 @@ type RepositoryVulnerabilityAlertConnection { totalCount: Int! } +""" +The possible scopes of an alert's dependency. +""" +enum RepositoryVulnerabilityAlertDependencyScope { + """ + A dependency that is only used in development + """ + DEVELOPMENT + + """ + A dependency that is leveraged during application runtime + """ + RUNTIME +} + """ An edge in a connection. """ @@ -35565,6 +38188,46 @@ Types that can be requested reviewers. """ union RequestedReviewer = Mannequin | Team | User +""" +The connection type for RequestedReviewer. +""" +type RequestedReviewerConnection { + """ + A list of edges. + """ + edges: [RequestedReviewerEdge] + + """ + A list of nodes. + """ + nodes: [RequestedReviewer] + + """ + Information to aid in pagination. + """ + pageInfo: PageInfo! + + """ + Identifies the total count of items in the connection. + """ + totalCount: Int! +} + +""" +An edge in a connection. +""" +type RequestedReviewerEdge { + """ + A cursor for use in pagination. + """ + cursor: String! + + """ + The item at the end of the edge. + """ + node: RequestedReviewer +} + """ Represents a type that can be required by a pull request for merging. """ @@ -36531,11 +39194,21 @@ type SecurityAdvisoryConnection { The possible ecosystems of a security vulnerability's package. """ enum SecurityAdvisoryEcosystem { + """ + GitHub Actions + """ + ACTIONS + """ PHP packages hosted at packagist.org """ COMPOSER + """ + Erlang/Elixir packages hosted at hex.pm + """ + ERLANG + """ Go modules """ @@ -36784,6 +39457,87 @@ type SmimeSignature implements GitSignature { wasSignedByGitHub: Boolean! } +""" +The possible default commit messages for squash merges. +""" +enum SquashMergeCommitMessage { + """ + Default to a blank commit message. + """ + BLANK + + """ + Default to the branch's commit messages. + """ + COMMIT_MESSAGES + + """ + Default to the pull request's body. + """ + PR_BODY +} + +""" +The possible default commit titles for squash merges. +""" +enum SquashMergeCommitTitle { + """ + Default to the commit's title (if only one commit) or the pull request's title (when more than one commit). + """ + COMMIT_OR_PR_TITLE + + """ + Default to the pull request's title. + """ + PR_TITLE +} + +""" +Represents an SSH signature on a Commit or Tag. +""" +type SshSignature implements GitSignature { + """ + Email used to sign this object. + """ + email: String! + + """ + True if the signature is valid and verified by GitHub. + """ + isValid: Boolean! + + """ + Hex-encoded fingerprint of the key that signed this object. + """ + keyFingerprint: String + + """ + Payload for GPG signing object. Raw ODB object without the signature header. + """ + payload: String! + + """ + ASCII-armored signature header from object. + """ + signature: String! + + """ + GitHub user corresponding to the email signing this commit. + """ + signer: User + + """ + The state of this signature. `VALID` if signature is valid and verified by + GitHub, otherwise represents reason why signature is considered invalid. + """ + state: GitSignatureState! + + """ + True if the signature was made with GitHub's signing key. + """ + wasSignedByGitHub: Boolean! +} + """ Ways in which star connections can be ordered. """ @@ -36972,6 +39726,11 @@ input StartRepositoryMigrationInput { """ githubPat: String + """ + Whether to lock the source repository. + """ + lockSource: Boolean + """ The signed URL to access the user-uploaded metadata archive """ @@ -37001,6 +39760,11 @@ input StartRepositoryMigrationInput { The Octoshift migration source repository URL. """ sourceRepositoryUrl: URI! + + """ + The visibility of the imported repository. + """ + targetRepoVisibility: String } """ @@ -37835,7 +40599,7 @@ type Team implements MemberStatusable & Node & Subscribable { orderBy: TeamRepositoryOrder """ - The search string to look for. + The search string to look for. Repositories will be returned where the name contains your search string. """ query: String ): TeamRepositoryConnection! @@ -39676,6 +42440,11 @@ input TransferIssueInput { """ clientMutationId: String + """ + Whether to create labels if they don't exist in the target repository (matched by name) + """ + createLabelsIfMissing: Boolean = false + """ The Node ID of the issue to be transferred """ @@ -39813,6 +42582,11 @@ type TreeEntry { """ repository: Repository! + """ + Entry byte size + """ + size: Int! + """ If the TreeEntry is for a directory occupied by a submodule project, this returns the corresponding submodule """ @@ -41802,6 +44576,46 @@ type UpdateOrganizationAllowPrivateRepositoryForkingSettingPayload { organization: Organization } +""" +Autogenerated input type of UpdateOrganizationWebCommitSignoffSetting +""" +input UpdateOrganizationWebCommitSignoffSettingInput { + """ + A unique identifier for the client performing the mutation. + """ + clientMutationId: String + + """ + The ID of the organization on which to set the web commit signoff setting. + """ + organizationId: ID! @possibleTypes(concreteTypes: ["Organization"]) + + """ + Enable signoff on web-based commits for repositories in the organization? + """ + webCommitSignoffRequired: Boolean! +} + +""" +Autogenerated return type of UpdateOrganizationWebCommitSignoffSetting +""" +type UpdateOrganizationWebCommitSignoffSettingPayload { + """ + A unique identifier for the client performing the mutation. + """ + clientMutationId: String + + """ + A message confirming the result of updating the web commit signoff setting. + """ + message: String + + """ + The organization with the updated web commit signoff setting. + """ + organization: Organization +} + """ Autogenerated input type of UpdateProjectCard """ @@ -41927,6 +44741,215 @@ type UpdateProjectPayload { project: Project } +""" +Autogenerated input type of UpdateProjectV2DraftIssue +""" +input UpdateProjectV2DraftIssueInput { + """ + The IDs of the assignees of the draft issue. + """ + assigneeIds: [ID!] @possibleTypes(concreteTypes: ["User"]) + + """ + The body of the draft issue. + """ + body: String + + """ + A unique identifier for the client performing the mutation. + """ + clientMutationId: String + + """ + The ID of the draft issue to update. + """ + draftIssueId: ID! @possibleTypes(concreteTypes: ["DraftIssue"]) + + """ + The title of the draft issue. + """ + title: String +} + +""" +Autogenerated return type of UpdateProjectV2DraftIssue +""" +type UpdateProjectV2DraftIssuePayload { + """ + A unique identifier for the client performing the mutation. + """ + clientMutationId: String + + """ + The draft issue updated in the project. + """ + draftIssue: DraftIssue +} + +""" +Autogenerated input type of UpdateProjectV2 +""" +input UpdateProjectV2Input { + """ + A unique identifier for the client performing the mutation. + """ + clientMutationId: String + + """ + Set the project to closed or open. + """ + closed: Boolean + + """ + The ID of the Project to update. + """ + projectId: ID! @possibleTypes(concreteTypes: ["ProjectV2"]) + + """ + Set the project to public or private. + """ + public: Boolean + + """ + Set the readme description of the project. + """ + readme: String + + """ + Set the short description of the project. + """ + shortDescription: String + + """ + Set the title of the project. + """ + title: String +} + +""" +Autogenerated input type of UpdateProjectV2ItemFieldValue +""" +input UpdateProjectV2ItemFieldValueInput { + """ + A unique identifier for the client performing the mutation. + """ + clientMutationId: String + + """ + The ID of the field to be updated. + """ + fieldId: ID! + @possibleTypes( + concreteTypes: ["ProjectV2Field", "ProjectV2IterationField", "ProjectV2SingleSelectField"] + abstractType: "ProjectV2FieldConfiguration" + ) + + """ + The ID of the item to be updated. + """ + itemId: ID! @possibleTypes(concreteTypes: ["ProjectV2Item"]) + + """ + The ID of the Project. + """ + projectId: ID! @possibleTypes(concreteTypes: ["ProjectV2"]) + + """ + The value which will be set on the field. + """ + value: ProjectV2FieldValue! +} + +""" +Autogenerated return type of UpdateProjectV2ItemFieldValue +""" +type UpdateProjectV2ItemFieldValuePayload { + """ + A unique identifier for the client performing the mutation. + """ + clientMutationId: String + + """ + The updated item. + """ + projectV2Item: ProjectV2Item +} + +""" +Autogenerated input type of UpdateProjectV2ItemPosition +""" +input UpdateProjectV2ItemPositionInput { + """ + The ID of the item to position this item after. If omitted or set to null the item will be moved to top. + """ + afterId: ID @possibleTypes(concreteTypes: ["ProjectV2Item"]) + + """ + A unique identifier for the client performing the mutation. + """ + clientMutationId: String + + """ + The ID of the item to be moved. + """ + itemId: ID! @possibleTypes(concreteTypes: ["ProjectV2Item"]) + + """ + The ID of the Project. + """ + projectId: ID! @possibleTypes(concreteTypes: ["ProjectV2"]) +} + +""" +Autogenerated return type of UpdateProjectV2ItemPosition +""" +type UpdateProjectV2ItemPositionPayload { + """ + A unique identifier for the client performing the mutation. + """ + clientMutationId: String + + """ + The items in the new order + """ + items( + """ + Returns the elements in the list that come after the specified cursor. + """ + after: String + + """ + Returns the elements in the list that come before the specified cursor. + """ + before: String + + """ + Returns the first _n_ elements from the list. + """ + first: Int + + """ + Returns the last _n_ elements from the list. + """ + last: Int + ): ProjectV2ItemConnection +} + +""" +Autogenerated return type of UpdateProjectV2 +""" +type UpdateProjectV2Payload { + """ + A unique identifier for the client performing the mutation. + """ + clientMutationId: String + + """ + The updated Project. + """ + projectV2: ProjectV2 +} + """ Autogenerated input type of UpdatePullRequestBranch """ @@ -42249,6 +45272,46 @@ type UpdateRepositoryPayload { repository: Repository } +""" +Autogenerated input type of UpdateRepositoryWebCommitSignoffSetting +""" +input UpdateRepositoryWebCommitSignoffSettingInput { + """ + A unique identifier for the client performing the mutation. + """ + clientMutationId: String + + """ + The ID of the repository to update. + """ + repositoryId: ID! @possibleTypes(concreteTypes: ["Repository"]) + + """ + Indicates if the repository should require signoff on web-based commits. + """ + webCommitSignoffRequired: Boolean! +} + +""" +Autogenerated return type of UpdateRepositoryWebCommitSignoffSetting +""" +type UpdateRepositoryWebCommitSignoffSettingPayload { + """ + A unique identifier for the client performing the mutation. + """ + clientMutationId: String + + """ + A message confirming the result of updating the web commit signoff setting. + """ + message: String + + """ + The updated repository. + """ + repository: Repository +} + """ Autogenerated input type of UpdateSubscription """ @@ -42522,7 +45585,7 @@ type UpdateTopicsPayload { """ A user is an individual's account on GitHub that owns repositories and can make new content. """ -type User implements Actor & Node & PackageOwner & ProfileOwner & ProjectOwner & RepositoryDiscussionAuthor & RepositoryDiscussionCommentAuthor & RepositoryOwner & UniformResourceLocatable { +type User implements Actor & Node & PackageOwner & ProfileOwner & ProjectOwner & ProjectV2Owner & ProjectV2Recent & RepositoryDiscussionAuthor & RepositoryDiscussionCommentAuthor & RepositoryOwner & UniformResourceLocatable { """ Determine if this repository owner has any items that can be pinned to their profile. """ @@ -43072,6 +46135,16 @@ type User implements Actor & Node & PackageOwner & ProfileOwner & ProjectOwner & number: Int! ): Project + """ + Find a project by number. + """ + projectV2( + """ + The project number. + """ + number: Int! + ): ProjectV2 + """ A list of projects under the owner. """ @@ -43122,6 +46195,41 @@ type User implements Actor & Node & PackageOwner & ProfileOwner & ProjectOwner & """ projectsUrl: URI! + """ + A list of projects under the owner. + """ + projectsV2( + """ + Returns the elements in the list that come after the specified cursor. + """ + after: String + + """ + Returns the elements in the list that come before the specified cursor. + """ + before: String + + """ + Returns the first _n_ elements from the list. + """ + first: Int + + """ + Returns the last _n_ elements from the list. + """ + last: Int + + """ + How to order the returned projects. + """ + orderBy: ProjectV2Order = {field: NUMBER, direction: DESC} + + """ + A project to search for under the the owner. + """ + query: String + ): ProjectV2Connection! + """ A list of public keys associated with this user. """ @@ -43197,6 +46305,31 @@ type User implements Actor & Node & PackageOwner & ProfileOwner & ProjectOwner & states: [PullRequestState!] ): PullRequestConnection! + """ + Recent projects that this user has modified in the context of the owner. + """ + recentProjects( + """ + Returns the elements in the list that come after the specified cursor. + """ + after: String + + """ + Returns the elements in the list that come before the specified cursor. + """ + before: String + + """ + Returns the first _n_ elements from the list. + """ + first: Int + + """ + Returns the last _n_ elements from the list. + """ + last: Int + ): ProjectV2Connection! + """ A list of repositories that the user owns. """ @@ -44162,6 +47295,36 @@ type Workflow implements Node { """ name: String! + """ + The runs of the workflow. + """ + runs( + """ + Returns the elements in the list that come after the specified cursor. + """ + after: String + + """ + Returns the elements in the list that come before the specified cursor. + """ + before: String + + """ + Returns the first _n_ elements from the list. + """ + first: Int + + """ + Returns the last _n_ elements from the list. + """ + last: Int + + """ + Ordering options for the connection + """ + orderBy: WorkflowRunOrder = {field: CREATED_AT, direction: DESC} + ): WorkflowRunConnection! + """ Identifies the date and time when the object was last updated. """ @@ -44264,6 +47427,71 @@ type WorkflowRun implements Node { workflow: Workflow! } +""" +The connection type for WorkflowRun. +""" +type WorkflowRunConnection { + """ + A list of edges. + """ + edges: [WorkflowRunEdge] + + """ + A list of nodes. + """ + nodes: [WorkflowRun] + + """ + Information to aid in pagination. + """ + pageInfo: PageInfo! + + """ + Identifies the total count of items in the connection. + """ + totalCount: Int! +} + +""" +An edge in a connection. +""" +type WorkflowRunEdge { + """ + A cursor for use in pagination. + """ + cursor: String! + + """ + The item at the end of the edge. + """ + node: WorkflowRun +} + +""" +Ways in which lists of workflow runs can be ordered upon return. +""" +input WorkflowRunOrder { + """ + The direction in which to order workflow runs by the specified field. + """ + direction: OrderDirection! + + """ + The field by which to order workflows. + """ + field: WorkflowRunOrderField! +} + +""" +Properties by which workflow run connections can be ordered. +""" +enum WorkflowRunOrderField { + """ + Order workflow runs by most recently created + """ + CREATED_AT +} + """ A valid x509 certificate string """ diff --git a/data/graphql/graphql_upcoming_changes.public.yml b/data/graphql/graphql_upcoming_changes.public.yml index 10bc243aee..3223f72fd8 100644 --- a/data/graphql/graphql_upcoming_changes.public.yml +++ b/data/graphql/graphql_upcoming_changes.public.yml @@ -814,6 +814,16 @@ upcoming_changes: date: '2023-01-01T00:00:00+00:00' criticality: breaking owner: lukewar + - location: ProjectNextFieldType.TRACKED_BY + description: + '`TRACKED_BY` will be removed. Follow the ProjectV2 guide at https://github.blog/changelog/2022-06-23-the-new-github-issues-june-23rd-update/, + to find a suitable replacement.' + reason: + The `ProjectNext` API is deprecated in favour of the more capable `ProjectV2` + API. + date: '2023-01-01T00:00:00+00:00' + criticality: breaking + owner: lukewar - location: ProjectNextFieldType.TRACKS description: '`TRACKS` will be removed. Follow the ProjectV2 guide at https://github.blog/changelog/2022-06-23-the-new-github-issues-june-23rd-update/, diff --git a/data/graphql/schema.docs.graphql b/data/graphql/schema.docs.graphql index 07aea8e81e..1393406154 100644 --- a/data/graphql/schema.docs.graphql +++ b/data/graphql/schema.docs.graphql @@ -1238,6 +1238,41 @@ type ApproveVerifiableDomainPayload { domain: VerifiableDomain } +""" +Autogenerated input type of ArchiveProjectV2Item +""" +input ArchiveProjectV2ItemInput { + """ + A unique identifier for the client performing the mutation. + """ + clientMutationId: String + + """ + The ID of the ProjectV2Item to archive. + """ + itemId: ID! @possibleTypes(concreteTypes: ["ProjectV2Item"]) + + """ + The ID of the Project to archive the item from. + """ + projectId: ID! @possibleTypes(concreteTypes: ["ProjectV2"]) +} + +""" +Autogenerated return type of ArchiveProjectV2Item +""" +type ArchiveProjectV2ItemPayload { + """ + A unique identifier for the client performing the mutation. + """ + clientMutationId: String + + """ + The item archived from the project. + """ + item: ProjectV2Item +} + """ Autogenerated input type of ArchiveRepository """ @@ -2012,6 +2047,17 @@ type BranchProtectionRule implements Node { """ isAdminEnforced: Boolean! + """ + Whether users can pull changes from upstream when the branch is locked. Set to + `true` to allow fork syncing. Set to `false` to prevent fork syncing. + """ + lockAllowsFetchAndMerge: Boolean! + + """ + Whether to set the branch as read-only. If this is true, users will not be able to push to the branch. + """ + lockBranch: Boolean! + """ Repository refs that are protected by this rule """ @@ -2077,6 +2123,11 @@ type BranchProtectionRule implements Node { """ repository: Repository + """ + Whether someone other than the person who last pushed to the branch must approve this pull request + """ + requireLastPushApproval: Boolean! + """ Number of approving reviews required to update matching branches. """ @@ -6075,6 +6126,17 @@ input CreateBranchProtectionRuleInput { """ isAdminEnforced: Boolean + """ + Whether users can pull changes from upstream when the branch is locked. Set to + `true` to allow fork syncing. Set to `false` to prevent fork syncing. + """ + lockAllowsFetchAndMerge: Boolean + + """ + Whether to set the branch as read-only. If this is true, users will not be able to push to the branch. + """ + lockBranch: Boolean + """ The glob-like pattern used to determine matching branches. """ @@ -6090,6 +6152,11 @@ input CreateBranchProtectionRuleInput { """ repositoryId: ID! @possibleTypes(concreteTypes: ["Repository"]) + """ + Whether someone other than the person who last pushed to the branch must approve this pull request + """ + requireLastPushApproval: Boolean + """ Number of approving reviews required to update matching branches. """ @@ -17602,6 +17669,41 @@ type LicenseRule { label: String! } +""" +Autogenerated input type of LinkProjectV2ToRepository +""" +input LinkProjectV2ToRepositoryInput { + """ + A unique identifier for the client performing the mutation. + """ + clientMutationId: String + + """ + The ID of the project to link to the repository. + """ + projectId: ID! @possibleTypes(concreteTypes: ["ProjectV2"]) + + """ + The ID of the repository to link to the project. + """ + repositoryId: ID! @possibleTypes(concreteTypes: ["Repository"]) +} + +""" +Autogenerated return type of LinkProjectV2ToRepository +""" +type LinkProjectV2ToRepositoryPayload { + """ + A unique identifier for the client performing the mutation. + """ + clientMutationId: String + + """ + The repository the project is linked to. + """ + repository: Repository +} + """ Autogenerated input type of LinkRepositoryToProject """ @@ -19851,6 +19953,16 @@ type Mutation { input: ApproveVerifiableDomainInput! ): ApproveVerifiableDomainPayload + """ + Archives a ProjectV2Item + """ + archiveProjectV2Item( + """ + Parameters for ArchiveProjectV2Item + """ + input: ArchiveProjectV2ItemInput! + ): ArchiveProjectV2ItemPayload + """ Marks a repository as archived. """ @@ -20577,6 +20689,16 @@ type Mutation { input: InviteEnterpriseAdminInput! ): InviteEnterpriseAdminPayload + """ + Links a project to a repository. + """ + linkProjectV2ToRepository( + """ + Parameters for LinkProjectV2ToRepository + """ + input: LinkProjectV2ToRepositoryInput! + ): LinkProjectV2ToRepositoryPayload + """ Creates a repository link for a project. """ @@ -20957,6 +21079,16 @@ type Mutation { input: TransferIssueInput! ): TransferIssuePayload + """ + Unarchives a ProjectV2Item + """ + unarchiveProjectV2Item( + """ + Parameters for UnarchiveProjectV2Item + """ + input: UnarchiveProjectV2ItemInput! + ): UnarchiveProjectV2ItemPayload + """ Unarchives a repository. """ @@ -20987,6 +21119,16 @@ type Mutation { input: UnfollowUserInput! ): UnfollowUserPayload + """ + Unlinks a project from a repository. + """ + unlinkProjectV2FromRepository( + """ + Parameters for UnlinkProjectV2FromRepository + """ + input: UnlinkProjectV2FromRepositoryInput! + ): UnlinkProjectV2FromRepositoryPayload + """ Deletes a repository link from a project. """ @@ -29307,6 +29449,14 @@ enum ProjectNextFieldType { reason: "The `ProjectNext` API is deprecated in favour of the more capable `ProjectV2` API. Follow the ProjectV2 guide at https://github.blog/changelog/2022-06-23-the-new-github-issues-june-23rd-update/, to find a suitable replacement. Removal on 2023-01-01 UTC." ) + """ + Tracked by + """ + TRACKED_BY + @deprecated( + reason: "The `ProjectNext` API is deprecated in favour of the more capable `ProjectV2` API. Follow the ProjectV2 guide at https://github.blog/changelog/2022-06-23-the-new-github-issues-june-23rd-update/, to find a suitable replacement. Removal on 2023-01-01 UTC." + ) + """ Tracks """ @@ -30398,6 +30548,11 @@ enum ProjectV2FieldType { """ TITLE + """ + Tracked by + """ + TRACKED_BY + """ Tracks """ @@ -40238,6 +40393,11 @@ type Repository implements Node & PackageOwner & ProjectOwner & ProjectV2Recent """ fundingLinks: [FundingLink!]! + """ + Are discussions available on this repository? + """ + hasDiscussionsEnabled: Boolean! + """ Indicates if the repository has issues feature enabled. """ @@ -48939,6 +49099,41 @@ An RFC 3986, RFC 3987, and RFC 6570 (level 4) compliant URI string. """ scalar URI +""" +Autogenerated input type of UnarchiveProjectV2Item +""" +input UnarchiveProjectV2ItemInput { + """ + A unique identifier for the client performing the mutation. + """ + clientMutationId: String + + """ + The ID of the ProjectV2Item to unarchive. + """ + itemId: ID! @possibleTypes(concreteTypes: ["ProjectV2Item"]) + + """ + The ID of the Project to archive the item from. + """ + projectId: ID! @possibleTypes(concreteTypes: ["ProjectV2"]) +} + +""" +Autogenerated return type of UnarchiveProjectV2Item +""" +type UnarchiveProjectV2ItemPayload { + """ + A unique identifier for the client performing the mutation. + """ + clientMutationId: String + + """ + The item unarchived from the project. + """ + item: ProjectV2Item +} + """ Autogenerated input type of UnarchiveRepository """ @@ -49143,6 +49338,41 @@ type UnlabeledEvent implements Node { labelable: Labelable! } +""" +Autogenerated input type of UnlinkProjectV2FromRepository +""" +input UnlinkProjectV2FromRepositoryInput { + """ + A unique identifier for the client performing the mutation. + """ + clientMutationId: String + + """ + The ID of the project to unlink from the repository. + """ + projectId: ID! @possibleTypes(concreteTypes: ["ProjectV2"]) + + """ + The ID of the repository to unlink from the project. + """ + repositoryId: ID! @possibleTypes(concreteTypes: ["Repository"]) +} + +""" +Autogenerated return type of UnlinkProjectV2FromRepository +""" +type UnlinkProjectV2FromRepositoryPayload { + """ + A unique identifier for the client performing the mutation. + """ + clientMutationId: String + + """ + The repository the project is no longer linked to. + """ + repository: Repository +} + """ Autogenerated input type of UnlinkRepositoryFromProject """ @@ -49575,6 +49805,17 @@ input UpdateBranchProtectionRuleInput { """ isAdminEnforced: Boolean + """ + Whether users can pull changes from upstream when the branch is locked. Set to + `true` to allow fork syncing. Set to `false` to prevent fork syncing. + """ + lockAllowsFetchAndMerge: Boolean + + """ + Whether to set the branch as read-only. If this is true, users will not be able to push to the branch. + """ + lockBranch: Boolean + """ The glob-like pattern used to determine matching branches. """ @@ -49585,6 +49826,11 @@ input UpdateBranchProtectionRuleInput { """ pushActorIds: [ID!] + """ + Whether someone other than the person who last pushed to the branch must approve this pull request + """ + requireLastPushApproval: Boolean + """ Number of approving reviews required to update matching branches. """ @@ -51797,6 +52043,11 @@ input UpdateRepositoryInput { """ description: String + """ + Indicates if the repository should have the discussions feature enabled. + """ + hasDiscussionsEnabled: Boolean + """ Indicates if the repository should have the issues feature enabled. """ diff --git a/data/release-notes/enterprise-server/2-20/0.yml b/data/release-notes/enterprise-server/2-20/0.yml deleted file mode 100644 index a013951fd4..0000000000 --- a/data/release-notes/enterprise-server/2-20/0.yml +++ /dev/null @@ -1,44 +0,0 @@ -date: '2020-02-11' -sections: - features: - - 'On a repository branch, repository administrators can reject any push that contains a merge commit by enabling `Require linear history` using [branch protection rules](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 %}' - - 'Repository administrators can grant all users with push access the ability to force-push to a protected branch by enabling `Allow force pushes` using [branch protection rules](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 %}' - - 'Repository administrators can grant all users with push access the ability to delete a protected branch by enabling `Allow deletions` using [branch protection rules](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 %}' - - 'Administrators can set a `maxobjectsize` limit on repositories, [limiting the size of push commits](https://help.github.com/en/enterprise/admin/installation/setting-git-push-limits) to a repository that are not in [Git LFS](https://help.github.com/en/enterprise/admin/installation/configuring-git-large-file-storage-on-github-enterprise-server). {% comment %} https://github.com/github/babeld/pull/864, https://team.githubapp.com/posts/33519, https://github.com/githubcustomers/Slack/issues/27 {% endcomment %}' - - 'Organization owners can create a set of default labels when creating a new repository.{% comment %} https://github.com/github/issues-projects/issues/237, https://github.com/github/issues-projects/issues/179 {% endcomment %}' - security_fixes: - - Packages have been updated to the latest security versions. - bugs: - - 'When a member of an organization tried to view a public repository in that organization, an SSO prompt could break the page display. {% comment %} https://github.com/github/github/issues/126677, https://github.com/github/github/pull/127501 {% endcomment %}' - - "When viewing a users' profile, the links to that users' teams could be broken. {% comment %} https://github.com/github/github/issues/131771, https://github.com/github/github/pull/131865 {% endcomment %}" - - 'Users with the `maintain` role were unable to edit repository topics. {% comment %} https://github.com/github/github/pull/129503, https://github.com/github/github/issues/119456 {% endcomment %}' - - "A user who isn't an administrator for an organization would receive a 500 error when attempting to access the sign up page. {% comment %} https://github.com/github/github/pull/129213, https://github.com/github/github/issues/129210, https://github.com/github/github/issues/129212 {% endcomment %}" - - 'The edit history popup would not display on gist comments. {% comment %} https://github.com/github/github/pull/129134, https://github.com/github/github/issues/128496 {% endcomment %}' - - 'A new account could be registered with an email that was already registered. {% comment %} https://github.com/github/github/pull/127905, https://github.com/github/github/issues/127858 {% endcomment %}' - - 'A storage service was hitting a file descriptor limit and causing kernel hanging and other services to log errors. {% comment %} https://github.com/github/enterprise2/pull/18775 {% endcomment %}' - - 'When an autolink reference was part of a url, the hyperlink could be removed. {% comment %} https://github.com/github/github/pull/126776 {% endcomment %}' - - 'When adding a comment to a pull request, the `Linked Issues` section from the sidebar could disappear. {% comment %} https://github.com/github/issues-projects/issues/384, https://github.com/github/github/pull/130514 {% endcomment %}' - - 'When editing an existing organization invitation for a user, a duplicate header could be appear on the `Teams` table. {% comment %} https://github.com/github/github/issues/120381, https://github.com/github/github/pull/128939 {% endcomment %}' - - 'The `resqued` service could stop logging events when the queues became too large. {% comment %} https://github.com/github/github/pull/130087, https://github.com/github/business-support/issues/2696 {% endcomment %}' - - 'Self-signed certificates are not automatically generated when running the `ghe-config-apply` command for cluster and high-availability configurations. {% comment %} https://github.com/github/enterprise2/pull/18773 {% endcomment %}' - changes: - - 'No logo will be displayed for a topic if one has not been uploaded. {% comment %} https://github.com/github/github/issues/130513, https://github.com/github/github/pull/130515 {% endcomment %}' - - 'When viewing an issue on a mobile browser, the issue metadata is listed at the top of the page. {% comment %} https://github.com/github/github/pull/127560 {% endcomment %}' - - 'Consul''s top-level domain has changed from ".consul" to ".ghe.local". {% comment %} https://github.com/github/enterprise2/pull/17443, https://github.com/github/enterprise2/issues/17701 {% endcomment %}' - - 'The hookshot service no longer relies on ElasticSearch and only uses MySQL as a database store. {% comment %} https://github.com/github/enterprise2/pull/18158, https://github.com/github/hookshot/pull/1128, https://github.com/github/enterprise2/pull/15898 {% endcomment %}' - - 'Improved visual distinction between issue, project and discussion has been implemented on project note cards. {% comment %} https://github.com/github/github/pull/132038 {% endcomment %}' - - 'On a pull request review, a notice is displayed if a multi-line comment is truncated. {% comment %} https://github.com/github/github/issues/125948, https://github.com/github/github/pull/128677 {% endcomment %}' - - 'Users can view their audit log on the `Security Log` tab of their personal settings page. {% comment %} https://github.com/github/github/pull/123041{% endcomment %}' - known_issues: - - 'On a freshly set up GitHub Enterprise Server without any users, an attacker could create the first admin user. {% comment %} https://github.com/github/enterprise2/issues/1889 {% endcomment %}' - - 'Custom firewall rules are not maintained during an upgrade. {% comment %} https://github.com/github/enterprise2/issues/2823 {% endcomment %}' - - '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. {% comment %} https://github.com/github/github/issues/54684 {% endcomment %}' - - '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. {% comment %} https://github.com/github/github/issues/107731 {% endcomment %}' - - 'When pushing to a gist, an exception could be triggered during the post-receive hook. {% comment %} https://github.com/github/github/issues/129091 {% endcomment %}' - - Duplicate webhook entries in the database can cause upgrades from previous versions to fail. (updated 2020-02-26) - - 'Upgrades and settings updates will fail if background worker configurations have been customised. {% comment %} https://github.com/github/enterprise2/issues/19119 {% endcomment %}' - - '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. {% comment %} https://github.com/github/admin-experience/issues/571 {% endcomment %}' - - 'When upgrading from previous versions, background job workers may not be spawned, preventing essential features such as merging pull requests. (updated 2020-04-07) {% comment %} https://github.com/github/enterprise2/issues/19232 {% endcomment %}' - - 'Security alerts are not reported when pushing to a repository on the command line. (updated 2020-06-23) {% comment %} https://github.com/github/github/issues/143190 {% endcomment %}' - - 'Dependency graph is not detecting dependencies when deployed in a cluster configuration with multiple Redis nodes. (updated 2020-06-30) {% comment %} https://github.com/github/dependency-graph/issues/81 {% endcomment %}' - - '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.' diff --git a/data/release-notes/enterprise-server/2-20/1.yml b/data/release-notes/enterprise-server/2-20/1.yml deleted file mode 100644 index 1edc6f0037..0000000000 --- a/data/release-notes/enterprise-server/2-20/1.yml +++ /dev/null @@ -1,21 +0,0 @@ -date: '2020-02-27' -sections: - security_fixes: - - 'Packages have been updated to the latest security versions. {% comment %} https://github.com/github/enterprise2/pull/19116, https://github.com/github/enterprise2/pull/19110, https://github.com/github/enterprise2/pull/19154, https://github.com/github/enterprise2/pull/19142 {% endcomment %}' - bugs: - - 'Restore from backups would fail with an `Invalid RDB version number` error. {% comment %} https://github.com/github/enterprise2/pull/19117, https://github.com/github/enterprise2/pull/19109 {% endcomment %}' - - 'Upgrading an HA replica would stall indefinitely waiting for MySQL to start. {% comment %} https://github.com/github/enterprise2/pull/19168, https://github.com/github/enterprise2/pull/19101 {% endcomment %}' - - 'PR review comments with unexpected values for "position" or "original_position" caused imports to fail. {% comment %} https://github.com/github/github/pull/135439, https://github.com/github/github/pull/135374 {% endcomment %}' - - 'Duplicate webhook entries in the database could cause upgrades from previous versions to fail. {% comment %} https://github.com/github/hookshot/pull/1541, https://github.com/github/hookshot/pull/1426, https://github.com/github/hookshot/pull/1540 {% endcomment %}' - known_issues: - - 'On a freshly set up GitHub Enterprise Server without any users, an attacker could create the first admin user. {% comment %} https://github.com/github/enterprise2/issues/1889 {% endcomment %}' - - 'Custom firewall rules are not maintained during an upgrade. {% comment %} https://github.com/github/enterprise2/issues/2823 {% endcomment %}' - - '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. {% comment %} https://github.com/github/github/issues/54684 {% endcomment %}' - - '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. {% comment %} https://github.com/github/github/issues/107731 {% endcomment %}' - - 'When pushing to a gist, an exception could be triggered during the post-receive hook. {% comment %} https://github.com/github/github/issues/129091 {% endcomment %}' - - 'Upgrades and settings updates will fail if background worker configurations have been customised. {% comment %} https://github.com/github/enterprise2/issues/19119 {% endcomment %}' - - '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. {% comment %} https://github.com/github/admin-experience/issues/571 {% endcomment %}' - - 'When upgrading from previous versions, background job workers may not be spawned, preventing essential features such as merging pull requests. (updated 2020-04-07) {% comment %} https://github.com/github/enterprise2/issues/19232 {% endcomment %}' - - 'Security alerts are not reported when pushing to a repository on the command line. (updated 2020-06-23) {% comment %} https://github.com/github/github/issues/143190 {% endcomment %}' - - 'Dependency graph is not detecting dependencies when deployed in a cluster configuration with multiple Redis nodes. (updated 2020-06-30) {% comment %} https://github.com/github/dependency-graph/issues/81 {% endcomment %}' - - '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.' diff --git a/data/release-notes/enterprise-server/2-20/10.yml b/data/release-notes/enterprise-server/2-20/10.yml deleted file mode 100644 index dd032d2c05..0000000000 --- a/data/release-notes/enterprise-server/2-20/10.yml +++ /dev/null @@ -1,21 +0,0 @@ -date: '2020-06-23' -sections: - security_fixes: - - 'Packages have been updated to the latest security versions. {% comment %} https://github.com/github/enterprise2/pull/20746, https://github.com/github/enterprise2/pull/20727 {% endcomment %}' - bugs: - - 'Excessively large log events could lead to log forwarding instability when UDP was used as the transport mechanism. {% comment %} https://github.com/github/enterprise2/pull/20457, https://github.com/github/enterprise2/pull/20445 {% endcomment %}' - - "Automatic unsuspension of a user through SSO did not complete if the SSH keys attribute had keys already associated with the user's account. {% comment %} https://github.com/github/github/pull/143474, https://github.com/github/github/pull/142927 {% endcomment %}" - - 'The repository permission hash from the REST API indicated no access for business members who have pull access to internal repositories. {% comment %} https://github.com/github/github/pull/144755, https://github.com/github/github/pull/144292 {% endcomment %}' - - 'Previewing a GitHub App description written in markdown was not properly rendered. {% comment %} https://github.com/github/github/pull/145038, https://github.com/github/github/pull/133360 {% endcomment %}' - - 'The audit log did not include branch protection changes events. {% comment %} https://github.com/github/github/pull/145995, https://github.com/github/github/pull/145014 {% endcomment %}' - - "Trying to assign code review to a member of an empty team would result in a '500 Internal Server Error'. {% comment %} https://github.com/github/github/pull/146328, https://github.com/github/github/pull/139330 {% endcomment %}" - - 'Code review assignment using the load balancing algorithm could repeatedly assign to the same team member. {% comment %} https://github.com/github/github/pull/146329, https://github.com/github/github/pull/136504 {% endcomment %}' - known_issues: - - 'On a freshly set up GitHub Enterprise Server without any users, an attacker could create the first admin user. {% comment %} https://github.com/github/enterprise2/issues/1889 {% endcomment %}' - - 'Custom firewall rules are not maintained during an upgrade. {% comment %} https://github.com/github/enterprise2/issues/2823 {% endcomment %}' - - '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. {% comment %} https://github.com/github/github/issues/54684 {% endcomment %}' - - '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. {% comment %} https://github.com/github/github/issues/107731 {% endcomment %}' - - '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. {% comment %} https://github.com/github/admin-experience/issues/571 {% endcomment %}' - - 'Security alerts are not reported when pushing to a repository on the command line. {% comment %} https://github.com/github/github/issues/143190 {% endcomment %}' - - 'Dependency graph is not detecting dependencies when deployed in a cluster configuration with multiple Redis nodes. (updated 2020-06-30) {% comment %} https://github.com/github/dependency-graph/issues/81 {% endcomment %}' - - '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.' diff --git a/data/release-notes/enterprise-server/2-20/11.yml b/data/release-notes/enterprise-server/2-20/11.yml deleted file mode 100644 index 46e5c7329e..0000000000 --- a/data/release-notes/enterprise-server/2-20/11.yml +++ /dev/null @@ -1,19 +0,0 @@ -date: '2020-07-09' -sections: - security_fixes: - - '**MEDIUM:** Updated nginx to 1.16.1 and addressed CVE-2019-20372. (updated 2020-07-22) {% comment %} https://github.com/github/enterprise2/pull/21251 {% endcomment %}' - - 'Packages have been updated to the latest security versions. {% comment %} https://github.com/github/enterprise2/pull/21088, https://github.com/github/enterprise2/pull/21036 {% endcomment %}' - bugs: - - 'Dependency graph was not detecting dependencies when deployed in a cluster configuration with multiple Redis nodes. {% comment %} https://github.com/github/enterprise2/pull/21260, https://github.com/github/enterprise2/pull/21102 {% endcomment %}' - - 'Certain log files did not rotate every 7 days. {% comment %} https://github.com/github/enterprise2/pull/21278, https://github.com/github/enterprise2/pull/21264 {% endcomment %}' - - 'Rapid reuse of webhook source ports resulted in rejected connections. {% comment %} https://github.com/github/enterprise2/pull/21289 {% endcomment %}' - - 'Incorrect background jobs could attempt to run on instances configured as passive replicas. {% comment %} https://github.com/github/enterprise2/pull/21318, https://github.com/github/enterprise2/pull/21212, https://github.com/github/enterprise2/issues/21167 {% endcomment %}' - - 'Internal repositories were not correctly included in search results for SAML-enabled orgs. {% comment %} https://github.com/github/github/pull/147503, https://github.com/github/github/pull/145692 {% endcomment %}' - known_issues: - - 'On a freshly set up GitHub Enterprise Server without any users, an attacker could create the first admin user. {% comment %} https://github.com/github/enterprise2/issues/1889 {% endcomment %}' - - 'Custom firewall rules are not maintained during an upgrade. {% comment %} https://github.com/github/enterprise2/issues/2823 {% endcomment %}' - - '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. {% comment %} https://github.com/github/github/issues/54684 {% endcomment %}' - - '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. {% comment %} https://github.com/github/github/issues/107731 {% endcomment %}' - - '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. {% comment %} https://github.com/github/admin-experience/issues/571 {% endcomment %}' - - 'Security alerts are not reported when pushing to a repository on the command line. {% comment %} https://github.com/github/github/issues/143190 {% endcomment %}' - - '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.' diff --git a/data/release-notes/enterprise-server/2-20/12.yml b/data/release-notes/enterprise-server/2-20/12.yml deleted file mode 100644 index edf6e7559f..0000000000 --- a/data/release-notes/enterprise-server/2-20/12.yml +++ /dev/null @@ -1,17 +0,0 @@ -date: '2020-07-21' -sections: - security_fixes: - - 'Packages have been updated to the latest security versions. {% comment %} https://github.com/github/enterprise2/pull/21437, https://github.com/github/enterprise2/pull/21402, https://github.com/github/enterprise2/pull/21495, https://github.com/github/enterprise2/pull/21479 {% endcomment %}' - bugs: - - 'The Management Console monitor graphs would sometimes not display correctly on larger screens. {% comment %} https://github.com/github/enterprise2/pull/21397, https://github.com/github/enterprise2/pull/21381 {% endcomment %}' - - 'GitHub App Manifest creation flow was unusable in some scenarios when a SameSite Cookie policy was applied. {% comment %} https://github.com/github/github/pull/147826, https://github.com/github/github/pull/144121 {% endcomment %}' - changes: - - 'Improvements to HAProxy scaling. {% comment %} https://github.com/github/enterprise2/pull/21383 {% endcomment %}' - known_issues: - - 'On a freshly set up GitHub Enterprise Server without any users, an attacker could create the first admin user. {% comment %} https://github.com/github/enterprise2/issues/1889 {% endcomment %}' - - 'Custom firewall rules are not maintained during an upgrade. {% comment %} https://github.com/github/enterprise2/issues/2823 {% endcomment %}' - - '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. {% comment %} https://github.com/github/github/issues/54684 {% endcomment %}' - - '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. {% comment %} https://github.com/github/github/issues/107731 {% endcomment %}' - - '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. {% comment %} https://github.com/github/admin-experience/issues/571 {% endcomment %}' - - 'Security alerts are not reported when pushing to a repository on the command line. {% comment %} https://github.com/github/github/issues/143190 {% endcomment %}' - - '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.' diff --git a/data/release-notes/enterprise-server/2-20/13.yml b/data/release-notes/enterprise-server/2-20/13.yml deleted file mode 100644 index ed91a8f4b3..0000000000 --- a/data/release-notes/enterprise-server/2-20/13.yml +++ /dev/null @@ -1,22 +0,0 @@ -date: '2020-08-11' -sections: - security_fixes: - - '{% octicon "alert" aria-label="The alert icon" %} **Critical:** A remote code execution vulnerability was identified in GitHub Pages that could allow an attacker to execute commands as part building a GitHub Pages site. This issue was due to an outdated and vulnerable dependency used in the Pages build process. To exploit this vulnerability, an attacker would need permission to create and build a GitHub Pages site on the GitHub Enterprise Server instance. This vulnerability affected all versions of GitHub Enterprise Server. To mitigate this vulnerability, Kramdown has been updated to address CVE-2020-14001. {% comment %} https://github.com/github/pages/pull/2836, https://github.com/github/pages/pull/2827 {% endcomment %}' - - '**High:** An attacker could inject a malicious argument into a Git sub-command when executed on GitHub Enterprise Server. This could allow an attacker to overwrite arbitrary files with partially user-controlled content and potentially execute arbitrary commands on the GitHub Enterprise Server instance. To exploit this vulnerability, an attacker would need permission to access repositories within the GitHub Enterprise Server instance. However, due to other protections in place, we could not identify a way to actively exploit this vulnerability. This vulnerability was reported through the GitHub Security Bug Bounty program. {% comment %} https://github.com/github/github/pull/151097 {% endcomment %}' - - 'Packages have been updated to the latest security versions. {% comment %} https://github.com/github/enterprise2/pull/21811, https://github.com/github/enterprise2/pull/21700 {% endcomment %}' - bugs: - - 'A Consul configuration error prevented some background jobs from being processed on standalone instances. {% comment %} https://github.com/github/enterprise2/pull/21464 {% endcomment %}' - - 'The service memory allocation calculation could allocate an incorrect or unbounded memory allocation to a service resulting in poor system performance. {% comment %} https://github.com/github/enterprise2/pull/21716 {% endcomment %}' - - 'The virtualization platform for oVirt KVM systems was not properly detected, causing problems during upgrades. {% comment %} https://github.com/github/enterprise2/pull/21730, https://github.com/github/enterprise2/pull/21669 {% endcomment %}' - - "The error message for invalid authentication with a password via Git command line didn't populate the URL linking to adding the appropriate token or SSH key. {% comment %} https://github.com/github/github/pull/149714 {% endcomment %}" - - 'GitHub Connect was using a deprecated GitHub.com API endpoint. {% comment %} https://github.com/github/github/pull/150828, https://github.com/github/github/pull/150545 {% endcomment %}' - - 'Issues could not be sorted by *Recently updated* on repositories migrated to a new instance. {% comment %} https://github.com/github/github/pull/150843, https://github.com/github/github/pull/149330 {% endcomment %}' - - 'The 404 page contained GitHub.com contact and status links in the footer. {% comment %} https://github.com/github/github/pull/151316 {% endcomment %}' - known_issues: - - 'On a freshly set up GitHub Enterprise Server without any users, an attacker could create the first admin user. {% comment %} https://github.com/github/enterprise2/issues/1889 {% endcomment %}' - - 'Custom firewall rules are not maintained during an upgrade. {% comment %} https://github.com/github/enterprise2/issues/2823 {% endcomment %}' - - '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. {% comment %} https://github.com/github/github/issues/54684 {% endcomment %}' - - '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. {% comment %} https://github.com/github/github/issues/107731 {% endcomment %}' - - '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. {% comment %} https://github.com/github/admin-experience/issues/571 {% endcomment %}' - - 'Security alerts are not reported when pushing to a repository on the command line. {% comment %} https://github.com/github/github/issues/143190 {% endcomment %}' - - '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.' diff --git a/data/release-notes/enterprise-server/2-20/14.yml b/data/release-notes/enterprise-server/2-20/14.yml deleted file mode 100644 index 822fc9d0f4..0000000000 --- a/data/release-notes/enterprise-server/2-20/14.yml +++ /dev/null @@ -1,13 +0,0 @@ -date: '2020-08-12' -sections: - bugs: - - 'Resolved an issue that could lead to high CPU usage while generating system configuration templates. {% comment %} https://github.com/github/enterprise2/pull/21784, https://github.com/github/enterprise2/pull/21741 {% endcomment %}' - - 'Recent changes to memory allocations could lead to a degradation in system performance {% comment %} https://github.com/github/enterprise2/pull/22067 {% endcomment %}' - known_issues: - - 'On a freshly set up GitHub Enterprise Server without any users, an attacker could create the first admin user. {% comment %} https://github.com/github/enterprise2/issues/1889 {% endcomment %}' - - 'Custom firewall rules are not maintained during an upgrade. {% comment %} https://github.com/github/enterprise2/issues/2823 {% endcomment %}' - - '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. {% comment %} https://github.com/github/github/issues/54684 {% endcomment %}' - - '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. {% comment %} https://github.com/github/github/issues/107731 {% endcomment %}' - - '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. {% comment %} https://github.com/github/admin-experience/issues/571 {% endcomment %}' - - 'Security alerts are not reported when pushing to a repository on the command line. {% comment %} https://github.com/github/github/issues/143190 {% endcomment %}' - - '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.' diff --git a/data/release-notes/enterprise-server/2-20/15.yml b/data/release-notes/enterprise-server/2-20/15.yml deleted file mode 100644 index 01f9c1eed7..0000000000 --- a/data/release-notes/enterprise-server/2-20/15.yml +++ /dev/null @@ -1,25 +0,0 @@ -date: '2020-08-26' -sections: - security_fixes: - - >- - {% octicon "alert" aria-label="The alert icon" %} **Critical:** A remote code execution vulnerability was identified in GitHub Pages that could be exploited when building a GitHub Pages site. User-controlled configuration of the underlying parsers used by GitHub Pages were not sufficiently restricted and made it possible to execute commands on the GitHub Enterprise Server instance. To exploit this vulnerability, an attacker would need permission to create and build a GitHub Pages site on the GitHub Enterprise Server instance. This vulnerability affected all versions of GitHub Enterprise Server. The underlying issues contributing to this vulnerability were identified both internally and through the GitHub Security Bug Bounty program. We have issued CVE-2020-10518. {% comment %} https://github.com/github/pages/pull/2883, https://github.com/github/pages/pull/2902, https://github.com/github/pages/pull/2894, https://github.com/github/pages/pull/2877, https://github.com/github/pages-gem/pull/700, - https://github.com/github/pages/pull/2890, https://github.com/github/pages/pull/2898, https://github.com/github/pages/pull/2909, https://github.com/github/pages/pull/2891, https://github.com/github/pages/pull/2884, https://github.com/github/pages/pull/2889 {% endcomment %} - - '**MEDIUM:** An improper access control vulnerability was identified that allowed authenticated users of the instance to determine the names of unauthorized private repositories given their numerical IDs. This vulnerability did not allow unauthorized access to any repository content besides the name. This vulnerability affected all versions of GitHub Enterprise Server prior to 2.22 and has been assigned [CVE-2020-10517](https://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2020-10517). The vulnerability was reported via the [GitHub Bug Bounty program](https://bounty.github.com). {% comment %} https://github.com/github/github/pull/151987, https://github.com/github/github/pull/151713 {% endcomment %}' - - 'Packages have been updated to the latest security versions. {% comment %} https://github.com/github/enterprise2/pull/21852, https://github.com/github/enterprise2/pull/21828, https://github.com/github/enterprise2/pull/22153, https://github.com/github/enterprise2/pull/21920, https://github.com/github/enterprise2/pull/22215, https://github.com/github/enterprise2/pull/22190 {% endcomment %}' - bugs: - - 'A message was not logged when the ghe-config-apply process had finished running ghe-es-auto-expand. {% comment %} https://github.com/github/enterprise2/pull/22177, https://github.com/github/enterprise2/pull/22171 {% endcomment %}' - - 'Excessive logging to the `syslog` file could occur on high-availability replicas if the primary appliance is unavailable. {% comment %} https://github.com/github/enterprise2/pull/22267, https://github.com/github/enterprise2/pull/22124 {% endcomment %}' - - "Database re-seeding on a replica could fail with an error: `Got packet bigger than 'max_allowed_packet'` {% comment %} https://github.com/github/enterprise2/pull/22321, https://github.com/github/enterprise2/pull/20063 {% endcomment %}" - - 'In some cases duplicate user data could cause a 500 error while running the ghe-license-usage script. {% comment %} https://github.com/github/github/pull/152638 {% endcomment %}' - changes: - - 'In a high availability or geo-replication configuration, replica instances would exit maintenance mode when ghe-config-apply ran. {% comment %} https://github.com/github/enterprise2/pull/21776, https://github.com/github/enterprise2/pull/21440 {% endcomment %}' - - "We've added support for the R5a and R5n AWS instance types. {% comment %} https://github.com/github/enterprise2/pull/21902, https://github.com/github/enterprise2/pull/21173 {% endcomment %}" - - 'Removed the license seat count information on the administrative SSH MOTD due to a performance issue impacting GitHub Enterprise Server clusters. {% comment %} https://github.com/github/enterprise2/pull/21993, https://github.com/github/enterprise2/pull/21870 {% endcomment %}' - known_issues: - - 'On a freshly set up GitHub Enterprise Server without any users, an attacker could create the first admin user. {% comment %} https://github.com/github/enterprise2/issues/1889 {% endcomment %}' - - 'Custom firewall rules are not maintained during an upgrade. {% comment %} https://github.com/github/enterprise2/issues/2823 {% endcomment %}' - - '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. {% comment %} https://github.com/github/github/issues/54684 {% endcomment %}' - - '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. {% comment %} https://github.com/github/github/issues/107731 {% endcomment %}' - - '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. {% comment %} https://github.com/github/admin-experience/issues/571 {% endcomment %}' - - 'Security alerts are not reported when pushing to a repository on the command line. {% comment %} https://github.com/github/github/issues/143190 {% endcomment %}' - - '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.' diff --git a/data/release-notes/enterprise-server/2-20/16.yml b/data/release-notes/enterprise-server/2-20/16.yml deleted file mode 100644 index 5aa4be9795..0000000000 --- a/data/release-notes/enterprise-server/2-20/16.yml +++ /dev/null @@ -1,13 +0,0 @@ -date: '2020-09-08' -sections: - bugs: - - 'A service health check caused session growth resulting in filesystem inode exhaustion. {% comment %} https://github.com/github/enterprise2/pull/22480, https://github.com/github/enterprise2/pull/22475 {% endcomment %}' - - "Upgrading using a hotpatch could fail with an error: `'libdbi1' was not found` {% comment %} https://github.com/github/enterprise2/pull/22558, https://github.com/github/enterprise2/pull/22552 {% endcomment %}" - known_issues: - - 'On a freshly set up GitHub Enterprise Server without any users, an attacker could create the first admin user. {% comment %} https://github.com/github/enterprise2/issues/1889 {% endcomment %}' - - 'Custom firewall rules are not maintained during an upgrade. {% comment %} https://github.com/github/enterprise2/issues/2823 {% endcomment %}' - - '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. {% comment %} https://github.com/github/github/issues/54684 {% endcomment %}' - - '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. {% comment %} https://github.com/github/github/issues/107731 {% endcomment %}' - - '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. {% comment %} https://github.com/github/admin-experience/issues/571 {% endcomment %}' - - 'Security alerts are not reported when pushing to a repository on the command line. {% comment %} https://github.com/github/github/issues/143190 {% endcomment %}' - - '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.' diff --git a/data/release-notes/enterprise-server/2-20/17.yml b/data/release-notes/enterprise-server/2-20/17.yml deleted file mode 100644 index f5d1c0decc..0000000000 --- a/data/release-notes/enterprise-server/2-20/17.yml +++ /dev/null @@ -1,13 +0,0 @@ -date: '2020-09-23' -sections: - security_fixes: - - '**MEDIUM**: ImageMagick has been updated to address [DSA-4715-1](https://www.debian.org/security/2020/dsa-4715). {% comment %} https://github.com/github/enterprise2/pull/22625, https://github.com/github/enterprise2/pull/22610 {% endcomment %}' - - 'Packages have been updated to the latest security versions. {% comment %} https://github.com/github/enterprise2/pull/22601, https://github.com/github/enterprise2/pull/22592, https://github.com/github/enterprise2/pull/22605, https://github.com/github/enterprise2/pull/22426, https://github.com/github/enterprise2/pull/22718, https://github.com/github/enterprise2/pull/22699 {% endcomment %}' - known_issues: - - 'On a freshly set up GitHub Enterprise Server without any users, an attacker could create the first admin user. {% comment %} https://github.com/github/enterprise2/issues/1889 {% endcomment %}' - - 'Custom firewall rules are not maintained during an upgrade. {% comment %} https://github.com/github/enterprise2/issues/2823 {% endcomment %}' - - '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. {% comment %} https://github.com/github/github/issues/54684 {% endcomment %}' - - '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. {% comment %} https://github.com/github/github/issues/107731 {% endcomment %}' - - '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. {% comment %} https://github.com/github/admin-experience/issues/571 {% endcomment %}' - - 'Security alerts are not reported when pushing to a repository on the command line. {% comment %} https://github.com/github/github/issues/143190 {% endcomment %}' - - '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.' diff --git a/data/release-notes/enterprise-server/2-20/18.yml b/data/release-notes/enterprise-server/2-20/18.yml deleted file mode 100644 index 8cda7e436e..0000000000 --- a/data/release-notes/enterprise-server/2-20/18.yml +++ /dev/null @@ -1,26 +0,0 @@ -date: '2020-10-09' -sections: - security_fixes: - - 'A user whose LDAP directory username standardizes to an existing GHES account login could authenticate into the existing account. {% comment %} https://github.com/github/github/pull/156518, https://github.com/github/github/pull/155512 {% endcomment %}' - - 'Packages have been updated to the latest security versions. {% comment %} https://github.com/github/enterprise2/pull/22910, https://github.com/github/enterprise2/pull/22878 {% endcomment %}' - bugs: - - 'The NameID Format dropdown in the Management Console would be reset to "unspecified" after setting it to "persistent". {% comment %} https://github.com/github/enterprise2/pull/22403, https://github.com/github/enterprise2/pull/22331, https://github.com/github/enterprise2/issues/13446 {% endcomment %}' - - 'Saving settings via the [management console](/admin/configuration/accessing-the-management-console) would append a newline to the [TLS/SSL certificate and key](/admin/configuration/configuring-tls) files which triggered unnecessary reloading of some services. {% comment %} https://github.com/github/enterprise2/pull/22607, https://github.com/github/enterprise2/pull/22540 {% endcomment %}' - - 'System logs for Dependency Graph were not rotating, allowing unbounded storage growth. {% comment %} https://github.com/github/enterprise2/pull/22765, https://github.com/github/enterprise2/pull/22733 {% endcomment %}' - - 'Links to GitHub Security Advisories would use a URL with the hostname of the GitHub Enterprise Server instance instead of GitHub.com, directing the user to a nonexistent URL. {% comment %} https://github.com/github/github/pull/153444, https://github.com/github/github/pull/151301 {% endcomment %}' - - 'When importing a repository with `ghe-migrator`, an unexpected exception could occur when inconsistent data is present. {% comment %} https://github.com/github/github/pull/153848, https://github.com/github/github/pull/151552 {% endcomment %}' - - 'When using `ghe-migrator` to import PR review requests, records associated with deleted users would result in extraneous database records. {% comment %} https://github.com/github/github/pull/154958, https://github.com/github/github/pull/153169 {% endcomment %}' - - 'When importing users with `ghe-migrator`, an error of "Emails is invalid" would occur if the system-generated email address were longer than 100 characters. {% comment %} https://github.com/github/github/pull/155112, https://github.com/github/github/pull/152418 {% endcomment %}' - - 'Logging webhook activity could use large amounts of disk space and cause the root disk to become full. {% comment %} https://github.com/github/github/pull/155655, https://github.com/github/github/pull/154100 {% endcomment %}' - changes: - - 'Support is added for the AWS EC2 instance type `m5.16xlarge`. {% comment %} https://github.com/github/enterprise2/pull/22500, https://github.com/github/enterprise2/pull/22473 {% endcomment %}' - - 'Remove the requirement for SSH fingerprints in `ghe-migrator` archives as it can always be computed. {% comment %} https://github.com/github/github/pull/156944, https://github.com/github/github/pull/155387 {% endcomment %}' - - 'GitHub App Manifests now include the `request_oauth_on_install` field. {% comment %} https://github.com/github/github/pull/156996, https://github.com/github/github/pull/155010, https://github.com/github/ecosystem-apps/issues/1055 {% endcomment %}' - known_issues: - - 'On a freshly set up GitHub Enterprise Server without any users, an attacker could create the first admin user. {% comment %} https://github.com/github/enterprise2/issues/1889 {% endcomment %}' - - 'Custom firewall rules are not maintained during an upgrade. {% comment %} https://github.com/github/enterprise2/issues/2823 {% endcomment %}' - - '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. {% comment %} https://github.com/github/github/issues/54684 {% endcomment %}' - - '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. {% comment %} https://github.com/github/github/issues/107731 {% endcomment %}' - - '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. {% comment %} https://github.com/github/admin-experience/issues/571 {% endcomment %}' - - 'Security alerts are not reported when pushing to a repository on the command line. {% comment %} https://github.com/github/github/issues/143190 {% endcomment %}' - - '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.' diff --git a/data/release-notes/enterprise-server/2-20/19.yml b/data/release-notes/enterprise-server/2-20/19.yml deleted file mode 100644 index 888ccc6eea..0000000000 --- a/data/release-notes/enterprise-server/2-20/19.yml +++ /dev/null @@ -1,14 +0,0 @@ -date: '2020-10-20' -sections: - security_fixes: - - 'Packages have been updated to the latest security versions. {% comment %} https://github.com/github/enterprise2/pull/23095, https://github.com/github/enterprise2/pull/23081 {% endcomment %}' - bugs: - - 'The enterprise account "Confirm two-factor requirement policy" messaging was incorrect. {% comment %} https://github.com/github/github/pull/158737 {% endcomment %}' - known_issues: - - 'On a freshly set up GitHub Enterprise Server without any users, an attacker could create the first admin user. {% comment %} https://github.com/github/enterprise2/issues/1889 {% endcomment %}' - - 'Custom firewall rules are not maintained during an upgrade. {% comment %} https://github.com/github/enterprise2/issues/2823 {% endcomment %}' - - '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. {% comment %} https://github.com/github/github/issues/54684 {% endcomment %}' - - '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. {% comment %} https://github.com/github/github/issues/107731 {% endcomment %}' - - '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. {% comment %} https://github.com/github/admin-experience/issues/571 {% endcomment %}' - - 'Security alerts are not reported when pushing to a repository on the command line. {% comment %} https://github.com/github/github/issues/143190 {% endcomment %}' - - '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.' diff --git a/data/release-notes/enterprise-server/2-20/2.yml b/data/release-notes/enterprise-server/2-20/2.yml deleted file mode 100644 index 9bafa389ed..0000000000 --- a/data/release-notes/enterprise-server/2-20/2.yml +++ /dev/null @@ -1,28 +0,0 @@ -date: '2020-03-10' -sections: - security_fixes: - - 'Packages have been updated to the latest security versions. {% comment %} https://github.com/github/enterprise2/pull/19204, https://github.com/github/enterprise2/pull/19187 {% endcomment %}' - bugs: - - 'In some cases the forwarded log entries, mainly for audit.log were getting truncated. {% comment %} https://github.com/github/enterprise2/pull/19244, https://github.com/github/enterprise2/pull/19192, https://github.com/github/enterprise2/issues/16655 {% endcomment %}' - - 'The `ghe-license-check` command-line utility returned an "Invalid license file" error for some valid licenses, causing configuration changes to fail. {% comment %} https://github.com/github/enterprise2/pull/19249, https://github.com/github/enterprise2/pull/19185, https://github.zendesk.com/agent/tickets/549903 {% endcomment %}' - - 'Alambic exception logs were not forwarded by syslog. {% comment %} https://github.com/github/enterprise2/pull/19263, https://github.com/github/enterprise2/pull/19123, https://github.com/github/enterprise2/issues/18734 {% endcomment %}' - - 'The [`org_block event`](https://developer.github.com/v3/activity/events/types/#orgblockevent) is not unavailable but was appearing for GitHub Apps on GitHub Enterprise Server. {% comment %} https://github.com/github/github/pull/136227, https://github.com/github/github/pull/135640, https://github.com/github/ecosystem-apps/issues/693 {% endcomment %}' - - 'GraphQL query responses sometimes returned unmatched node identifiers for `ProtectedBranch` objects. {% comment %} https://github.com/github/github/pull/136376, https://github.com/github/github/pull/136214, https://github.com/github/github/issues/135407 {% endcomment %}' - - 'The GitHub App credential used by GitHub Connect failed to refresh immediately after expiry. {% comment %} https://github.com/github/github/pull/136384, https://github.com/github/github/pull/136259 {% endcomment %}' - - 'Leaving a comment in reply to a pull request comment was intermittently creating a pending pull request review. {% comment %} https://github.com/github/github/pull/136454, https://github.com/github/github/pull/133697, https://github.com/github/github/issues/127401 {% endcomment %}' - - 'Using ghe-migrator or exporting from GitHub.com, an export would silently fail to export non-image attachments. {% comment %} https://github.com/github/github/pull/136487, https://github.com/github/github/pull/134524, https://github.com/github/github/issues/134358 {% endcomment %}' - - 'Pre-receive hook returned 500 error on web UI when UTF-8 characters were encountered. {% comment %} https://github.com/github/github/pull/136699, https://github.com/github/github/pull/136014, https://github.com/github/github/issues/133501 {% endcomment %}' - changes: - - 'The ` ghe-license-usage ` command-line utility includes a new `--unencrypted` option to provide visibility into the exported license usage file. {% comment %} https://github.com/github/github/pull/136134, https://github.com/github/github/pull/136000 {% endcomment %}' - known_issues: - - 'On a freshly set up GitHub Enterprise Server without any users, an attacker could create the first admin user. {% comment %} https://github.com/github/enterprise2/issues/1889 {% endcomment %}' - - 'Custom firewall rules are not maintained during an upgrade. {% comment %} https://github.com/github/enterprise2/issues/2823 {% endcomment %}' - - '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. {% comment %} https://github.com/github/github/issues/54684 {% endcomment %}' - - '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. {% comment %} https://github.com/github/github/issues/107731 {% endcomment %}' - - 'When pushing to a gist, an exception could be triggered during the post-receive hook. {% comment %} https://github.com/github/github/issues/129091 {% endcomment %}' - - 'Upgrades and settings updates will fail if background worker configurations have been customised. {% comment %} https://github.com/github/enterprise2/issues/19119 {% endcomment %}' - - '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. {% comment %} https://github.com/github/admin-experience/issues/571 {% endcomment %}' - - 'When upgrading from previous versions, background job workers may not be spawned, preventing essential features such as merging pull requests. (updated 2020-04-07) {% comment %} https://github.com/github/enterprise2/issues/19232 {% endcomment %}' - - 'Security alerts are not reported when pushing to a repository on the command line. (updated 2020-06-23) {% comment %} https://github.com/github/github/issues/143190 {% endcomment %}' - - 'Dependency graph is not detecting dependencies when deployed in a cluster configuration with multiple Redis nodes. (updated 2020-06-30) {% comment %} https://github.com/github/dependency-graph/issues/81 {% endcomment %}' - - '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.' diff --git a/data/release-notes/enterprise-server/2-20/20.yml b/data/release-notes/enterprise-server/2-20/20.yml deleted file mode 100644 index f73670d87f..0000000000 --- a/data/release-notes/enterprise-server/2-20/20.yml +++ /dev/null @@ -1,16 +0,0 @@ -date: '2020-11-03' -sections: - security_fixes: - - '**MEDIUM:** High CPU usage could be triggered by a specially crafted request to the SVN bridge resulting in Denial of Service (DoS). {% comment %} https://github.com/github/slumlord/pull/1003, https://github.com/github/slumlord/pull/1000 {% endcomment %}' - - "**LOW:** Incorrect token validation resulted in a reduced entropy for matching tokens during authentication. Analysis shows that in practice there's no significant security risk here. {% comment %} https://github.com/github/github/pull/159453, https://github.com/github/github/pull/159193 {% endcomment %}" - - 'Packages have been updated to the latest security versions. {% comment %} https://github.com/github/enterprise2/pull/23538, https://github.com/github/enterprise2/pull/23171, https://github.com/github/enterprise2/pull/23691, https://github.com/github/enterprise2/pull/23677 {% endcomment %}' - bugs: - - 'Suspended users were included in the list of suggested users, potentially hiding unsuspended users. {% comment %} https://github.com/github/github/pull/159809, https://github.com/github/github/pull/140563, https://github.com/github/github/pull/142146 {% endcomment %}' - known_issues: - - 'On a freshly set up GitHub Enterprise Server without any users, an attacker could create the first admin user. {% comment %} https://github.com/github/enterprise2/issues/1889 {% endcomment %}' - - 'Custom firewall rules are not maintained during an upgrade. {% comment %} https://github.com/github/enterprise2/issues/2823 {% endcomment %}' - - '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. {% comment %} https://github.com/github/github/issues/54684 {% endcomment %}' - - '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. {% comment %} https://github.com/github/github/issues/107731 {% endcomment %}' - - '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. {% comment %} https://github.com/github/admin-experience/issues/571 {% endcomment %}' - - 'Security alerts are not reported when pushing to a repository on the command line. {% comment %} https://github.com/github/github/issues/143190 {% endcomment %}' - - '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.' diff --git a/data/release-notes/enterprise-server/2-20/21.yml b/data/release-notes/enterprise-server/2-20/21.yml deleted file mode 100644 index d3b280cc4f..0000000000 --- a/data/release-notes/enterprise-server/2-20/21.yml +++ /dev/null @@ -1,15 +0,0 @@ -date: '2020-11-17' -sections: - security_fixes: - - 'Packages have been updated to the latest security versions. {% comment %} https://github.com/github/enterprise2/pull/23843, https://github.com/github/enterprise2/pull/23712 {% endcomment %}' - bugs: - - 'The babeld logs were missing a separator between seconds and microseconds. {% comment %} https://github.com/github/babeld/pull/1004, https://github.com/github/babeld/pull/1002 {% endcomment %}' - - 'When the enterprise account "Repository visibility change" policy was set to "Enabled", organization owners could not change the visibility of repositories within the organization. {% comment %} https://github.com/github/github/pull/160922, https://github.com/github/github/pull/160773 {% endcomment %}' - known_issues: - - 'On a freshly set up GitHub Enterprise Server without any users, an attacker could create the first admin user. {% comment %} https://github.com/github/enterprise2/issues/1889 {% endcomment %}' - - 'Custom firewall rules are not maintained during an upgrade. {% comment %} https://github.com/github/enterprise2/issues/2823 {% endcomment %}' - - '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. {% comment %} https://github.com/github/github/issues/54684 {% endcomment %}' - - '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. {% comment %} https://github.com/github/github/issues/107731 {% endcomment %}' - - '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. {% comment %} https://github.com/github/admin-experience/issues/571 {% endcomment %}' - - 'Security alerts are not reported when pushing to a repository on the command line. {% comment %} https://github.com/github/github/issues/143190 {% endcomment %}' - - '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.' diff --git a/data/release-notes/enterprise-server/2-20/22.yml b/data/release-notes/enterprise-server/2-20/22.yml deleted file mode 100644 index 2bfe078443..0000000000 --- a/data/release-notes/enterprise-server/2-20/22.yml +++ /dev/null @@ -1,19 +0,0 @@ -date: '2020-12-03' -sections: - bugs: - - 'Authorization service was being detected as unhealthy due to a race condition in the bootstrap which led to restart of the service. {% comment %} https://github.com/github/authzd/pull/1279 {% endcomment %}' - - 'An underlying behavior was causing a service to become unavailable during the hotpatch upgrade process. {% comment %} https://github.com/github/enterprise2/pull/24053, https://github.com/github/enterprise2/issues/23947 {% endcomment %}' - - 'A subset of log forwarding SSL certificates was not being applied correctly. {% comment %} https://github.com/github/enterprise2/pull/24112, https://github.com/github/enterprise2/pull/23981 {% endcomment %}' - - 'Email notifications sent to suspended users when they were removed from a Team or an Organization. {% comment %} https://github.com/github/github/pull/163107, https://github.com/github/github/pull/162742 {% endcomment %}' - - 'The way SSH certificates were applied between Organizations and Businesses was inconsistent. {% comment %} https://github.com/github/github/pull/163429, https://github.com/github/github/pull/159538, https://github.com/github/authentication/issues/115 {% endcomment %}' - - 'When an account was rate limited due to using incorrect passwords, it could be locked out for up to 24 hours. {% comment %} https://github.com/github/github/pull/163456, https://github.com/github/github/pull/162938, https://github.com/github/github-ds/pull/51 {% endcomment %}' - - 'Pull request synchronization on repositories with many references could cause worker queues to fall behind. {% comment %} https://github.com/github/github/pull/163576, https://github.com/github/github/pull/163142 {% endcomment %}' - - 'When signing in after attempting to visit a specific page, people were sent to the home page instead of their intended destination. {% comment %} https://github.com/github/github/pull/163785, https://github.com/github/github/pull/163579, https://github.com/github/github/pull/154117, https://github.com/github/ecosystem-apps/issues/1076 {% endcomment %}' - known_issues: - - 'On a freshly set up GitHub Enterprise Server without any users, an attacker could create the first admin user. {% comment %} https://github.com/github/enterprise2/issues/1889 {% endcomment %}' - - 'Custom firewall rules are not maintained during an upgrade. {% comment %} https://github.com/github/enterprise2/issues/2823 {% endcomment %}' - - '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. {% comment %} https://github.com/github/github/issues/54684 {% endcomment %}' - - '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. {% comment %} https://github.com/github/github/issues/107731 {% endcomment %}' - - '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. {% comment %} https://github.com/github/admin-experience/issues/571 {% endcomment %}' - - 'Security alerts are not reported when pushing to a repository on the command line. {% comment %} https://github.com/github/github/issues/143190 {% endcomment %}' - - '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.' diff --git a/data/release-notes/enterprise-server/2-20/23.yml b/data/release-notes/enterprise-server/2-20/23.yml deleted file mode 100644 index 284578b32a..0000000000 --- a/data/release-notes/enterprise-server/2-20/23.yml +++ /dev/null @@ -1,13 +0,0 @@ -date: '2020-12-17' -sections: - security_fixes: - - '**LOW:** High CPU usage could be triggered by a specially crafted request to the SVN bridge resulting in Denial of Service (DoS). {% comment %} https://github.com/github/slumlord/pull/1020, https://github.com/github/slumlord/pull/1017 {% endcomment %}' - - 'Packages have been updated to the latest security versions. {% comment %} https://github.com/github/enterprise2/pull/24351, https://github.com/github/enterprise2/pull/23866 {% endcomment %}' - known_issues: - - 'On a freshly set up GitHub Enterprise Server without any users, an attacker could create the first admin user. {% comment %} https://github.com/github/enterprise2/issues/1889 {% endcomment %}' - - 'Custom firewall rules are not maintained during an upgrade. {% comment %} https://github.com/github/enterprise2/issues/2823 {% endcomment %}' - - '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. {% comment %} https://github.com/github/github/issues/54684 {% endcomment %}' - - '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. {% comment %} https://github.com/github/github/issues/107731 {% endcomment %}' - - '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. {% comment %} https://github.com/github/admin-experience/issues/571 {% endcomment %}' - - 'Security alerts are not reported when pushing to a repository on the command line. {% comment %} https://github.com/github/github/issues/143190 {% endcomment %}' - - '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.' diff --git a/data/release-notes/enterprise-server/2-20/24.yml b/data/release-notes/enterprise-server/2-20/24.yml deleted file mode 100644 index dce5ec62ad..0000000000 --- a/data/release-notes/enterprise-server/2-20/24.yml +++ /dev/null @@ -1,28 +0,0 @@ -date: '2021-03-02' -sections: - security_fixes: - - '**HIGH:** An improper access control vulnerability was identified in GitHub Enterprise Server that allowed authenticated users of the instance to gain write access to unauthorized repositories via specifically crafted pull requests and REST API requests. An attacker would need to be able to fork the targeted repository, a setting that is disabled by default for organization owned private repositories. Branch protections such as required pull request reviews or status checks would prevent unauthorized commits from being merged without further review or validation. This vulnerability has been assigned CVE-2021-22861. This issue was reported via the [GitHub Bug Bounty Program](https://bounty.github.com).' - - '**HIGH:** An improper access control vulnerability was identified in the GitHub Enterprise Server GraphQL API that allowed authenticated users of the instance to modify the maintainer collaboration permission of a pull request without proper authorization. By exploiting this vulnerability, an attacker would be able to gain access to head branches of pull requests opened on repositories of which they are a maintainer. Forking is disabled by default for organization owned private repositories and would prevent this vulnerability. Additionally, branch protections such as required pull request reviews or status checks would prevent unauthorized commits from being merged without further review or validation. This vulnerability has been assigned CVE-2021-22863. This issue was reported via the [GitHub Bug Bounty Program](https://bounty.github.com).' - - '**HIGH:** A remote code execution vulnerability was identified in GitHub Enterprise Server that could be exploited when building a GitHub Pages site. User-controlled configuration of the underlying parsers used by GitHub Pages were not sufficiently restricted and made it possible to execute commands on the GitHub Enterprise Server instance. To exploit this vulnerability, an attacker would need permission to create and build a GitHub Pages site on the GitHub Enterprise Server instance. This vulnerability has been assigned CVE-2020-10519 and was reported via the [GitHub Bug Bounty Program](https://bounty.github.com).' - - '**LOW:** A specially crafted request to the SVN bridge could trigger a long wait before failure resulting in Denial of Service (DoS).' - - 'Packages have been updated to the latest security versions.' - bugs: - - 'An informational message was unintentionally logged as an error during GitHub Enterprise Backup Utilities snapshots, which resulted in unnecessary emails being sent when backups were scheduled by cron jobs that listen for output to stderr.' - - 'While restoring a large backup, exception logging related to Redis memory exhaustion could cause the restore to fail due to a full disk.' - - 'When editing a wiki page a user could experience a 500 error when clicking the Save button.' - - 'An S/MIME signed commit using a certificate with multiple names in the subject alternative name would incorrectly show as "Unverified" in the commit badge.' - - 'Suspended user was sent emails when added to a team.' - - 'When uploading a new license file with a different number of seats from the previous license file, the seat difference was not correctly represented in the enterprise account Settings -> License page.' - - 'The "Prevent repository admins from changing anonymous Git read access" checkbox available in the enterprise account settings could not be successfully enabled or disabled.' - - 'During a leap year, the user was getting a 404 response when trying to view Contribution activity on a Monday.' - changes: - - 'Added support for [AWS EC2 r5b instance types](https://aws.amazon.com/about-aws/whats-new/2020/12/introducing-new-amazon-ec2-r5b-instances-featuring-60-gbps-of-ebs-bandwidth-and-260K-iops/).' - - 'Adjusted background queue prioritization to more evenly distribute jobs.' - known_issues: - - 'On a freshly set up GitHub Enterprise 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.' - - 'Security alerts are not reported when pushing to a repository on the command line.' - - '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.' diff --git a/data/release-notes/enterprise-server/2-20/3.yml b/data/release-notes/enterprise-server/2-20/3.yml deleted file mode 100644 index 022221e2f3..0000000000 --- a/data/release-notes/enterprise-server/2-20/3.yml +++ /dev/null @@ -1,15 +0,0 @@ -date: '2020-03-12' -sections: - bugs: - - 'Upgrades and settings updates would fail if background worker configurations had been customised. {% comment %} https://github.com/github/enterprise2/pull/19321, https://github.com/github/enterprise2/pull/19299 {% endcomment %}' - known_issues: - - 'On a freshly set up GitHub Enterprise Server without any users, an attacker could create the first admin user. {% comment %} https://github.com/github/enterprise2/issues/1889 {% endcomment %}' - - 'Custom firewall rules are not maintained during an upgrade. {% comment %} https://github.com/github/enterprise2/issues/2823 {% endcomment %}' - - '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. {% comment %} https://github.com/github/github/issues/54684 {% endcomment %}' - - '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. {% comment %} https://github.com/github/github/issues/107731 {% endcomment %}' - - 'When pushing to a gist, an exception could be triggered during the post-receive hook. {% comment %} https://github.com/github/github/issues/129091 {% endcomment %}' - - '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. {% comment %} https://github.com/github/admin-experience/issues/571 {% endcomment %}' - - 'When upgrading from previous versions, background job workers may not be spawned, preventing essential features such as merging pull requests. (updated 2020-04-07) {% comment %} https://github.com/github/enterprise2/issues/19232 {% endcomment %}' - - 'Security alerts are not reported when pushing to a repository on the command line. (updated 2020-06-23) {% comment %} https://github.com/github/github/issues/143190 {% endcomment %}' - - 'Dependency graph is not detecting dependencies when deployed in a cluster configuration with multiple Redis nodes. (updated 2020-06-30) {% comment %} https://github.com/github/dependency-graph/issues/81 {% endcomment %}' - - '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.' diff --git a/data/release-notes/enterprise-server/2-20/4.yml b/data/release-notes/enterprise-server/2-20/4.yml deleted file mode 100644 index a20b1808ba..0000000000 --- a/data/release-notes/enterprise-server/2-20/4.yml +++ /dev/null @@ -1,18 +0,0 @@ -date: '2020-03-25' -sections: - bugs: - - 'SAML Authentication requests and Metadata were not strictly encoded, causing some Identity Providers to not correctly process Service Provider initiated Authentication requests. {% comment %} https://github.com/github/github/pull/137150, https://github.com/github/github/pull/136770, https://github.com/github/github/issues/136766 {% endcomment %}' - - '`ghe-migrator` exports did not contain milestone users, which could break import operations. {% comment %} https://github.com/github/github/pull/138100, https://github.com/github/github/pull/137987, https://github.com/github/github/issues/137779 {% endcomment %}' - - 'When pushing to a Gist, an exception could be triggered during the post-receive hook. {% comment %} https://github.com/github/github/pull/138460, https://github.com/github/github/pull/138313 {% endcomment %}' - - '`ghe-repl-status` could fail when trying to display repositories that were not fully replicated. {% comment %} https://github.com/github/github/pull/138463, https://github.com/github/github/pull/138388 {% endcomment %}' - known_issues: - - 'On a freshly set up GitHub Enterprise Server without any users, an attacker could create the first admin user. {% comment %} https://github.com/github/enterprise2/issues/1889 {% endcomment %}' - - 'Custom firewall rules are not maintained during an upgrade. {% comment %} https://github.com/github/enterprise2/issues/2823 {% endcomment %}' - - '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. {% comment %} https://github.com/github/github/issues/54684 {% endcomment %}' - - '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. {% comment %} https://github.com/github/github/issues/107731 {% endcomment %}' - - 'When pushing to a gist, an exception could be triggered during the post-receive hook. {% comment %} https://github.com/github/github/issues/129091 {% endcomment %}' - - '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. {% comment %} https://github.com/github/admin-experience/issues/571 {% endcomment %}' - - 'When upgrading from previous versions, background job workers may not be spawned, preventing essential features such as merging pull requests. (updated 2020-04-07) {% comment %} https://github.com/github/enterprise2/issues/19232 {% endcomment %}' - - 'Security alerts are not reported when pushing to a repository on the command line. (updated 2020-06-23) {% comment %} https://github.com/github/github/issues/143190 {% endcomment %}' - - 'Dependency graph is not detecting dependencies when deployed in a cluster configuration with multiple Redis nodes. (updated 2020-06-30) {% comment %} https://github.com/github/dependency-graph/issues/81 {% endcomment %}' - - '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.' diff --git a/data/release-notes/enterprise-server/2-20/5.yml b/data/release-notes/enterprise-server/2-20/5.yml deleted file mode 100644 index fe0368387b..0000000000 --- a/data/release-notes/enterprise-server/2-20/5.yml +++ /dev/null @@ -1,20 +0,0 @@ -date: '2020-04-07' -sections: - security_fixes: - - 'Packages have been updated to the latest security versions. {% comment %} https://github.com/github/enterprise2/pull/19536, https://github.com/github/enterprise2/pull/19494 {% endcomment %}' - bugs: - - 'A maximum Git object size of 100MB option could not be selected for a repository when the global enterprise account had a Git object size option other than 100MB set. {% comment %} https://github.com/github/github/pull/138805, https://github.com/github/github/pull/138683 {% endcomment %}' - - 'Results from the the Issues and Pull Requests API could have inconsistent behaviour when ordering by the `updated_at` field. {% comment %} https://github.com/github/github/pull/139247, https://github.com/github/github/pull/138486 {% endcomment %}' - - 'The SecurityVulnerability `package` field could not be queried via the GraphQL API. {% comment %} https://github.com/github/github/pull/139418, https://github.com/github/github/pull/138245 {% endcomment %}' - - 'Changing a repository from *public* to *internal* displayed an irrelevant billing message. {% comment %} https://github.com/github/github/pull/139531, https://github.com/github/github/pull/139492 {% endcomment %}' - known_issues: - - 'On a freshly set up GitHub Enterprise Server without any users, an attacker could create the first admin user. {% comment %} https://github.com/github/enterprise2/issues/1889 {% endcomment %}' - - 'Custom firewall rules are not maintained during an upgrade. {% comment %} https://github.com/github/enterprise2/issues/2823 {% endcomment %}' - - '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. {% comment %} https://github.com/github/github/issues/54684 {% endcomment %}' - - '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. {% comment %} https://github.com/github/github/issues/107731 {% endcomment %}' - - 'When pushing to a gist, an exception could be triggered during the post-receive hook. {% comment %} https://github.com/github/github/issues/129091 {% endcomment %}' - - '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. {% comment %} https://github.com/github/admin-experience/issues/571 {% endcomment %}' - - 'When upgrading from previous versions, background job workers may not be spawned, preventing essential features such as merging pull requests. {% comment %} https://github.com/github/enterprise2/issues/19232 {% endcomment %}' - - 'Security alerts are not reported when pushing to a repository on the command line. (updated 2020-06-23) {% comment %} https://github.com/github/github/issues/143190 {% endcomment %}' - - 'Dependency graph is not detecting dependencies when deployed in a cluster configuration with multiple Redis nodes. (updated 2020-06-30) {% comment %} https://github.com/github/dependency-graph/issues/81 {% endcomment %}' - - '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.' diff --git a/data/release-notes/enterprise-server/2-20/6.yml b/data/release-notes/enterprise-server/2-20/6.yml deleted file mode 100644 index 9e4ee142e6..0000000000 --- a/data/release-notes/enterprise-server/2-20/6.yml +++ /dev/null @@ -1,27 +0,0 @@ -date: '2020-04-23' -sections: - security_fixes: - - '**HIGH**: OpenSSL has been updated to address [CVE-2020-1967](https://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2020-1967). {% comment %} https://github.com/github/enterprise2/pull/19889, https://github.com/github/enterprise2/pull/19885 {% endcomment %}' - - '**HIGH**: Git has been updated to address [CVE-2020-5260](https://github.com/git/git/security/advisories/GHSA-qm7j-c969-7j4q) and [CVE-2020-11008](https://github.com/git/git/security/advisories/GHSA-hjc9-x69f-jqj7). New restrictions prevent malicious repositories from being pushed to the server instance, protecting clients which have not yet been patched. {% comment %} https://github.com/github/git/pull/990 {% endcomment %}' - - '**LOW**: ImageMagick has been updated to address [CVE-2019-10131](https://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2019-10131). {% comment %} https://github.com/github/enterprise2/pull/19655, https://github.com/github/enterprise2/pull/19617 {% endcomment %}' - - 'Packages have been updated to the latest security versions. {% comment %} https://github.com/github/enterprise2/pull/19809, https://github.com/github/enterprise2/pull/19792, https://github.com/github/enterprise2/pull/19899, https://github.com/github/enterprise2/pull/19882 {% endcomment %}' - bugs: - - 'The git user lacked permissions to invoke the processes required to convert existing repositories using Subversion, from the v4 format to v3 LRS. {% comment %} https://github.com/github/enterprise2/pull/19465, https://github.com/github/enterprise2/pull/19150 {% endcomment %}' - - 'A mismatch in MySQL configurations could cause backups to fail in large installations. {% comment %} https://github.com/github/enterprise2/pull/19688, https://github.com/github/enterprise2/pull/19409, https://github.com/github/enterprise2/issues/19055 {% endcomment %}' - - 'When upgrading from previous versions, background job workers would sometimes not spawn, preventing essential features such as merging pull requests. {% comment %} https://github.com/github/enterprise2/pull/19771, https://github.com/github/enterprise2/pull/19712 {% endcomment %}' - - "When a GitHub Enterprise Server license contained non-ASCII characters, a `GET` request to the Management Console's API `/setup/api/settings` endpoint would result in an Internal Server Error. {% comment %} https://github.com/github/enterprise2/pull/19790 {% endcomment %}" - - 'The recovery console would prompt for a root password, even if the root account was locked. {% comment %} https://github.com/github/enterprise2/pull/19810, https://github.com/github/enterprise2/pull/19788, https://github.com/github/enterprise2/issues/18425 {% endcomment %}' - - 'A CODEOWNERS file with a leading UTF-8 Byte Order Mark would cause all codeowner rules to be ignored. {% comment %} https://github.com/github/github/pull/140974, https://github.com/github/github/pull/140729 {% endcomment %}' - changes: - - 'When the orchestrator-client cron job failed, multiple emails would be sent to the root account. {% comment %} https://github.com/github/enterprise2/pull/19761, https://github.com/github/enterprise2/pull/19748 {% endcomment %}' - - "When an external identity provider controlled user's site administrator status, users could not be demoted via the command line utility. {% comment %} https://github.com/github/github/pull/140522, https://github.com/github/github/pull/137807, https://github.com/github/github/issues/42727 {% endcomment %}" - known_issues: - - 'On a freshly set up GitHub Enterprise Server without any users, an attacker could create the first admin user. {% comment %} https://github.com/github/enterprise2/issues/1889 {% endcomment %}' - - 'Custom firewall rules are not maintained during an upgrade. {% comment %} https://github.com/github/enterprise2/issues/2823 {% endcomment %}' - - '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. {% comment %} https://github.com/github/github/issues/54684 {% endcomment %}' - - '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. {% comment %} https://github.com/github/github/issues/107731 {% endcomment %}' - - 'When pushing to a gist, an exception could be triggered during the post-receive hook. {% comment %} https://github.com/github/github/issues/129091 {% endcomment %}' - - '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. {% comment %} https://github.com/github/admin-experience/issues/571 {% endcomment %}' - - 'Security alerts are not reported when pushing to a repository on the command line. (updated 2020-06-23) {% comment %} https://github.com/github/github/issues/143190 {% endcomment %}' - - 'Dependency graph is not detecting dependencies when deployed in a cluster configuration with multiple Redis nodes. (updated 2020-06-30) {% comment %} https://github.com/github/dependency-graph/issues/81 {% endcomment %}' - - '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.' diff --git a/data/release-notes/enterprise-server/2-20/7.yml b/data/release-notes/enterprise-server/2-20/7.yml deleted file mode 100644 index 8604e4f45f..0000000000 --- a/data/release-notes/enterprise-server/2-20/7.yml +++ /dev/null @@ -1,21 +0,0 @@ -date: '2020-05-05' -sections: - security_fixes: - - 'Packages have been updated to the latest security versions. {% comment %} https://github.com/github/enterprise2/pull/20027, https://github.com/github/enterprise2/pull/19997 {% endcomment %}' - bugs: - - '`ghe-repl-start` and `ghe-repl-status` displayed syntax errors. {% comment %} https://github.com/github/enterprise2/pull/19954, https://github.com/github/enterprise2/pull/19927 {% endcomment %}' - - 'If a repository has the "automatically delete head branches" setting enabled, the head branch wasn''t automatically deleted, when a pull request was merged by a GitHub App installation. {% comment %} https://github.com/github/github/pull/141588, https://github.com/github/github/pull/133698, https://github.com/github/github/pull/133871, https://github.com/github/github/issues/132588 {% endcomment %}' - - 'When an organization member was reinstated, the webhook payload reported the `ghost` user as the sender and not the actual user performing the reinstatement. {% comment %} https://github.com/github/github/pull/141731, https://github.com/github/github/pull/140609 {% endcomment %}' - - 'If a repository has the "automatically delete head branches" setting enabled, the head branch wasn''t automatically deleted where the head repository was different from the base repository. {% comment %} https://github.com/github/github/pull/142096, https://github.com/github/github/pull/133871 {% endcomment %}' - - 'The garbage collection of temporary files could lead to a license validation error. {% comment %} https://github.com/github/github/pull/142209, https://github.com/github/github/pull/142189 {% endcomment %}' - - 'In some situations, including when a repository is first created, the pre-receive hook would be run without a value populated for the GITHUB_REPO_PUBLIC environment variable. {% comment %} https://github.com/github/github/pull/139419, https://github.com/github/github/pull/136228, https://github.com/github/github/pull/134363 {% endcomment %}' - known_issues: - - 'On a freshly set up GitHub Enterprise Server without any users, an attacker could create the first admin user. {% comment %} https://github.com/github/enterprise2/issues/1889 {% endcomment %}' - - 'Custom firewall rules are not maintained during an upgrade. {% comment %} https://github.com/github/enterprise2/issues/2823 {% endcomment %}' - - '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. {% comment %} https://github.com/github/github/issues/54684 {% endcomment %}' - - '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. {% comment %} https://github.com/github/github/issues/107731 {% endcomment %}' - - 'When pushing to a gist, an exception could be triggered during the post-receive hook. {% comment %} https://github.com/github/github/issues/129091 {% endcomment %}' - - '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. {% comment %} https://github.com/github/admin-experience/issues/571 {% endcomment %}' - - 'Security alerts are not reported when pushing to a repository on the command line. (updated 2020-06-23) {% comment %} https://github.com/github/github/issues/143190 {% endcomment %}' - - 'Dependency graph is not detecting dependencies when deployed in a cluster configuration with multiple Redis nodes. (updated 2020-06-30) {% comment %} https://github.com/github/dependency-graph/issues/81 {% endcomment %}' - - '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.' diff --git a/data/release-notes/enterprise-server/2-20/8.yml b/data/release-notes/enterprise-server/2-20/8.yml deleted file mode 100644 index 4ed9daf124..0000000000 --- a/data/release-notes/enterprise-server/2-20/8.yml +++ /dev/null @@ -1,20 +0,0 @@ -date: '2020-05-19' -sections: - security_fixes: - - 'Packages have been updated to the latest security versions. {% comment %} https://github.com/github/enterprise2/pull/20108, https://github.com/github/enterprise2/pull/20086 {% endcomment %}' - bugs: - - 'After the license file was updated, services were not properly reloaded causing functionality loss. {% comment %} https://github.com/github/enterprise2/pull/20072, https://github.com/github/enterprise2/pull/19989 {% endcomment %}' - - 'Internal API requests updating Dependency Graph information could fail if the response body was too large. {% comment %} https://github.com/github/enterprise2/pull/20231, https://github.com/github/enterprise2/pull/20208 {% endcomment %}' - - 'The `affiliations` argument to some GraphQL repository connections was not respected. {% comment %} https://github.com/github/github/pull/142036, https://github.com/github/github/pull/140658 {% endcomment %}' - - 'Automatic unsuspension of a user through SSO did not complete if the SAML email attribute had different casing than the GitHub user email. {% comment %} https://github.com/github/github/pull/143321, https://github.com/github/github/pull/142915 {% endcomment %}' - - 'Restoring the membership of a user to an organization did not instrument the actor in webhook and audit log payloads. {% comment %} https://github.com/github/github/pull/143231, https://github.com/github/github/pull/140849 {% endcomment %}' - known_issues: - - 'On a freshly set up GitHub Enterprise Server without any users, an attacker could create the first admin user. {% comment %} https://github.com/github/enterprise2/issues/1889 {% endcomment %}' - - 'Custom firewall rules are not maintained during an upgrade. {% comment %} https://github.com/github/enterprise2/issues/2823 {% endcomment %}' - - '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. {% comment %} https://github.com/github/github/issues/54684 {% endcomment %}' - - '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. {% comment %} https://github.com/github/github/issues/107731 {% endcomment %}' - - 'When pushing to a gist, an exception could be triggered during the post-receive hook. {% comment %} https://github.com/github/github/issues/129091 {% endcomment %}' - - '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. {% comment %} https://github.com/github/admin-experience/issues/571 {% endcomment %}' - - 'Security alerts are not reported when pushing to a repository on the command line. (updated 2020-06-23) {% comment %} https://github.com/github/github/issues/143190 {% endcomment %}' - - 'Dependency graph is not detecting dependencies when deployed in a cluster configuration with multiple Redis nodes. (updated 2020-06-30) {% comment %} https://github.com/github/dependency-graph/issues/81 {% endcomment %}' - - '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.' diff --git a/data/release-notes/enterprise-server/2-20/9.yml b/data/release-notes/enterprise-server/2-20/9.yml deleted file mode 100644 index df804d9c24..0000000000 --- a/data/release-notes/enterprise-server/2-20/9.yml +++ /dev/null @@ -1,17 +0,0 @@ -date: '2020-06-02' -sections: - security_fixes: - - '**HIGH:** An improper access control vulnerability was identified in the GitHub Enterprise Server API that allowed an organization member to escalate permissions and gain access to unauthorized repositories within an organization. This vulnerability affected all versions of GitHub Enterprise Server prior to 2.21. We have issued [CVE-2020-10516](https://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2020-10516) in response to this issue. The vulnerability was reported via the [GitHub Bug Bounty program](https://bounty.github.com). {% comment %} https://github.com/github/github/pull/144454, https://github.com/github/github/pull/143444 {% endcomment %}' - - 'Packages have been updated to the latest security versions. {% comment %} https://github.com/github/enterprise2/pull/20421, https://github.com/github/enterprise2/pull/20315 {% endcomment %}' - bugs: - - 'Internet-facing GitHub Enterprise Server instances could be indexed by search engines. {% comment %} https://github.com/github/github/pull/145073, https://github.com/github/github/pull/144973 {% endcomment %}' - known_issues: - - 'On a freshly set up GitHub Enterprise Server without any users, an attacker could create the first admin user. {% comment %} https://github.com/github/enterprise2/issues/1889 {% endcomment %}' - - 'Custom firewall rules are not maintained during an upgrade. {% comment %} https://github.com/github/enterprise2/issues/2823 {% endcomment %}' - - '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. {% comment %} https://github.com/github/github/issues/54684 {% endcomment %}' - - '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. {% comment %} https://github.com/github/github/issues/107731 {% endcomment %}' - - 'When pushing to a gist, an exception could be triggered during the post-receive hook. {% comment %} https://github.com/github/github/issues/129091 {% endcomment %}' - - '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. {% comment %} https://github.com/github/admin-experience/issues/571 {% endcomment %}' - - 'Security alerts are not reported when pushing to a repository on the command line. (updated 2020-06-23) {% comment %} https://github.com/github/github/issues/143190 {% endcomment %}' - - 'Dependency graph is not detecting dependencies when deployed in a cluster configuration with multiple Redis nodes. (updated 2020-06-30) {% comment %} https://github.com/github/dependency-graph/issues/81 {% endcomment %}' - - '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.' diff --git a/data/release-notes/enterprise-server/2-21/0.yml b/data/release-notes/enterprise-server/2-21/0.yml deleted file mode 100644 index 6ca5525e98..0000000000 --- a/data/release-notes/enterprise-server/2-21/0.yml +++ /dev/null @@ -1,73 +0,0 @@ -date: '2020-06-09' -sections: - features: - - 'Users can [manage notifications](https://help.github.com/en/enterprise/2.21/user/github/managing-subscriptions-and-notifications-on-github/about-notifications) on issues, pull requests and other subjects when navigating from a web notification. {% comment %} https://github.com/github/enterprise-releases/issues/2135#issuecomment-633905096 {% endcomment %}' - - 'Users can [convert a pull request back to a "Draft"](https://github.blog/changelog/2020-04-08-convert-pull-request-to-draft/). {% comment %} https://github.com/github/releases/issues/800 {% endcomment %}' - - '[Multi-line suggestions](https://github.blog/changelog/2020-04-15-multi-line-code-suggestions-general-availability/) let a user suggest a specific change to multiple lines of code when reviewing a pull request. {% comment %} https://github.com/github/releases/issues/810 {% endcomment %}' - - 'Users with write access to a repository can [hide a comment in an issue or pull request as a "Duplicate" ](https://help.github.com/en/enterprise/2.21/user/github/building-a-strong-community/managing-disruptive-comments#hiding-a-comment). {% comment %}https://github.com/github/github/pull/131746 {% endcomment %}' - - 'When [creating a repository from a template](https://help.github.com/en/enterprise/2.21/user/github/creating-cloning-and-archiving-repositories/creating-a-repository-from-a-template) a user can optionally select to include all branches, rather than just the default branch. {% comment %} https://github.com/github/releases/issues/580 {% endcomment %}' - - '[Issue project cards include a linked pull requests section](https://github.blog/changelog/2020-02-04-project-issue-cards-include-linked-pull-requests/) so a user can see what development work is related to the issue directly from the project board. {% comment %} https://github.com/github/releases/issues/743 {% endcomment %}' - - 'There are a new set of ["Deleting reactions" endpoints](https://developer.github.com/changes/2020-02-26-new-delete-reactions-endpoints/) in the Reactions API. The existing "Delete reactions" endpoints will be deprecated in early 2021. {% comment %} https://developer.github.com/changes/2020-02-26-new-delete-reactions-endpoints/ {% endcomment %}' - - 'There are a new set of [Teams API endpoints](https://developer.github.com/changes/2020-01-21-moving-the-team-api-endpoints/) which will allow GitHub to scale and support the Teams API long-term. The existing API endpoints will be deprecated in early 2021. {% comment %} https://developer.github.com/changes/2020-01-21-moving-the-team-api-endpoints/ {% endcomment %}' - - 'Users can [create links between issues and pull requests](https://help.github.com/en/enterprise/2.21/user/github/managing-your-work-on-github/linking-a-pull-request-to-an-issue#manually-linking-a-pull-request-to-an-issue) without needing to use closing keywords in the pull request description. {% comment %} https://github.com/github/releases/issues/704 {% endcomment %}' - security_fixes: - - 'An improper access control vulnerability was identified in the GitHub Enterprise Server API that allowed an organization member to escalate permissions and gain access to unauthorized repositories within an organization. This vulnerability affected all versions of GitHub Enterprise Server prior to 2.21. We have issued [CVE-2020-10516](https://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2020-10516) in response to this issue. The vulnerability was reported via the [GitHub Bug Bounty program](https://bounty.github.com/). {% comment %} https://developer.github.com/changes/2020-02-26-new-delete-reactions-endpoints/ {% endcomment %}' - bugs: - - "If a user with push access minimized another user's comment, the author of the comment could unminimize it even if they had insufficient privileges. {% comment %} https://github.com/github/github/pull/141237 {% endcomment %}" - - 'Users could accidentally merge to master from the issue template editor and blob editor. {% comment %} https://github.com/github/github/pull/134483, https://github.com/github/github/pull/134323 {% endcomment %}' - - 'When a user deleted an account from GitHub, the audit log records did not correctly show organization removal records. {% comment %} https://github.com/github/github/pull/140940 {% endcomment %}' - - 'The gist avatar for the current user would link to a non-existent URL. {% comment %} https://github.com/github/github/pull/140925 {% endcomment %}' - - 'The organization repositories tab count did not include internal repositories. {% comment %} https://github.com/github/github/pull/136323 {% endcomment %}' - - 'Clicking the "Show All Teams" button when transferring a repository caused a 500 error. {% comment %} https://github.com/github/github/pull/134455 {% endcomment %}' - - "Long filenames could cause overflow issues when showing the 'Changed since last view' label or the 'Show rich' diff toggle on the diff file view. {% comment %} https://github.com/github/github/pull/134453 {% endcomment %}" - - 'Hovercards for organization teams misreported their member size. {% comment %} https://github.com/github/github/pull/133879 {% endcomment %}' - - 'The pull request review comment popup window had a scrolling issue. {% comment %} https://github.com/github/github/pull/141157 {% endcomment %}' - - 'Haproxy could become saturated causing a slowdown in git operations. {% comment %} https://github.com/github/enterprise2/issues/19322 {% endcomment %}' - - 'The Dependency Graph feature was not automatically enabled after HA replica promotion. {% comment %} https://github.com/github/enterprise2/issues/18698 {% endcomment %}' - - 'A timeout could be triggered on the releases index page for repositories with thousands of draft pull requests. {% comment %} https://github.com/github/github/pull/131802 {% endcomment %}' - - 'It was not possible to filter pull requests by both state and draft at the same time. {% comment %} https://github.com/github/github/pull/132567 {% endcomment %}' - - 'If a pull request changed a submodule pointer, then clicking "Edit file" on that submodule file from the "Files changed" tab of the pull request page caused a 404 error. {% comment %} https://github.com/github/github/pull/132448 {% endcomment %}' - - 'It was not possible to add users to an organization, or delete the organization, following the bulk removal of all users and admins from that organization. {% comment %} https://github.com/github/github/pull/132238 {% endcomment %}' - - 'Review comments against files containing diacritics and non-Latin characters in the filename on the "Files changed" page would disappear when the page is reloaded. {% comment %} https://github.com/github/github/pull/131836 {% endcomment %}' - - 'The state of the "Viewed" checkbox was not retained for files containing diacritics and non-Latin characters in the filename on the "Files changed" page. {% comment %} https://github.com/github/github/pull/131836 {% endcomment %}' - - 'Pull requests showed the "Approved" badge when not all required reviews were in place. {% comment %} https://github.com/github/github/pull/131823 {% endcomment %}' - - 'The tag dropdown was empty when searching for a tag in repositories with more than 100 tags. {% comment %} https://github.com/github/github/pull/131914 {% endcomment %}' - - 'Pull request pages showing annotations with non UTF-8 titles could encounter encoding errors in view rendering. {% comment %} https://github.com/github/github/pull/138534 {% endcomment %}' - - 'A race condition for refresh on the OAuth page could cause a redirect to be executed twice. {% comment %} https://github.com/github/github/pull/131964 {% endcomment %}' - - 'The "Personal Access Tokens" page would timeout if there are more than 10 tokens. {% comment %} https://github.com/github/github/pull/132064 {% endcomment %}' - - 'Scheduled LDAP User and Team Sync jobs could be started while previously scheduled Sync jobs were still in process. A locking mechanism has been implemented to prevent new Sync jobs from starting if one is still running. {% 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: - - 'The web notifications interface, including new [states](https://help.github.com/en/enterprise/2.21/user/github/managing-subscriptions-and-notifications-on-github/managing-notifications-from-your-inbox#triaging-options) , [filters](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) and [shortcuts](https://help.github.com/en/enterprise/2.21/user/github/getting-started-with-github/keyboard-shortcuts#notifications) have been updated. {% comment %} https://github.com/github/enterprise-releases/issues/2135#issuecomment-633905096 {% endcomment %}' - - 'It is now possible to disable reactivation of LDAP users on LDAP sync. {% comment %} https://github.com/github/github/pull/139023 {% endcomment %}' - - 'The push protected branch wording has been updated to clarify that admins can always push and that users with the Maintain role can push when status checks pass. {% comment %} https://github.com/github/github/pull/141555 {% endcomment %}' - - 'Prevent blank commit when suggestion is identical to original text. {% comment %} https://github.com/github/github/pull/138587 {% endcomment %}' - - 'Pagination is supported as a way to get more files in the diff associated with a commit via the REST API. {% comment %} https://github.com/github/github/pull/134341 {% endcomment %}' - - 'Admins can enable, disable, delete, and search for webhooks using the webhook ID from the command line using `ghe-webhook-manage`. {% comment %} https://github.com/github/enterprise2/pull/19027 {% endcomment %}' - - 'Automatic base retargeting will happen after manual head reference cleanup for a merged pull request. {% comment %} https://github.com/github/github/pull/142133 {% endcomment %}' - - 'SVG files are handled as text and as images in the diff viewer. {% comment %} https://github.com/github/render/pull/1129 {% endcomment %}' - - 'The "auto delete branches on merge" setting can be set when creating and updating repositories using the REST API. {% comment %} https://github.com/github/github/pull/131728 {% endcomment %}' - - 'A new endpoint has been added to delete a deployment through the REST API. {% comment %} https://github.com/github/github/pull/128733 {% endcomment %}' - - 'Admins can [enable security alerts](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-on-github-enterprise-server) but disable all notifications from those alerts. {% comment %} https://github.com/github/releases/issues/841 {% endcomment %}' - - 'The Pages log shows the user login accessing the GitHub Pages site. {% comment %} https://github.com/github/enterprise2/pull/19905 {% endcomment %}' - - 'Enterprise members can see all of the organizations they belong to as part of their Enterprise account from one view by navigating to `https://[ghes-hostname]/enterprises/[account-name]`. {% comment %} https://github.com/github/releases/issues/832 {% endcomment %}' - - '[REST API support for triage and maintain roles](https://developer.github.com/changes/2020-04-07-expanding-rest-api-support-for-the-triage-and-maintain-roles/) has been expanded. {% comment %} https://github.com/github/releases/issues/748 {% endcomment %}' - - 'A user can create and share search queries that resolve to the current user by using the `@me` search syntax. {% comment %} https://github.com/github/github/pull/129624 {% endcomment %}' - - 'New issue template configuration options have been [added](https://github.blog/changelog/2019-10-28-new-issue-template-configuration-options/). {% comment %} https://github.com/github/releases/issues/660 {% endcomment %}' - - 'MySQL backup and restore reliability and time to completion has been improved. {% comment %} https://github.com/github/ghes-infrastructure/issues/162 {% endcomment %}' - - '[Improved visibility](https://github.blog/2020-02-06-get-more-information-at-a-glance-with-issue-and-pull-request-linking/) of pull requests and issue references in the issue sidebar, issue cards and issue list. {% comment %} https://github.com/github/releases/issues/704 {% endcomment %}' - - 'Users can filter and search by `linked:pr` or `linked:issue`. {% comment %} https://github.com/github/releases/issues/744 {% endcomment %}' - - 'Automatic failover of MySQL within a single region for Cluster deployments is now possible. {% comment %} https://github.com/github/ghes-infrastructure/issues/136 {% endcomment %}' - - 'A user can compare tags between two releases to determine what changes have been made on the releases page. {% comment %} https://github.com/github/github/issues/107054 {% endcomment %}' - - 'Outdated comments are no longer collapsed by default on the Pull Request timeline. They can be collapsed by resolving the thread. {% comment %} https://github.com/github/enterprise-web/pull/6389#issuecomment-634201583 {% endcomment %}' - - 'Admins can view a list of logins reserved for internal use by navigating to the "Reserved logins" stafftools tab. {% comment %} https://github.com/github/enterprise-web/pull/6389#issuecomment-637846206 {% endcomment %}' - known_issues: - - 'On a freshly set up GitHub Enterprise Server without any users, an attacker could create the first admin user. {% comment %} https://github.com/github/enterprise2/issues/1889 {% endcomment %}' - - 'Custom firewall rules are not maintained during an upgrade. {% comment %} https://github.com/github/enterprise2/issues/2823 {% endcomment %}' - - '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. {% comment %} https://github.com/github/github/issues/54684 {% endcomment %}' - - '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. {% comment %} https://github.com/github/github/issues/107731 {% endcomment %}' - - 'When pushing to a gist, an exception could be triggered during the post-receive hook. {% comment %} https://github.com/github/github/issues/129091 {% endcomment %}' - - '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. {% comment %} https://github.com/github/admin-experience/issues/571 {% endcomment %}' - - 'Security alerts are not reported when pushing to a repository on the command line. (updated 2020-06-23) {% comment %} https://github.com/github/github/issues/143190 {% endcomment %}' - - 'Audit logs may be attributed to 127.0.0.1 instead of the actual source IP address. (updated 2020-11-02) {% comment %} https://github.com/github/enterprise2/issues/21514 {% endcomment %}' - - "Configuring a repository's permission to `Triage` or `Maintain` fails with an error message." - - '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.' diff --git a/data/release-notes/enterprise-server/2-21/1.yml b/data/release-notes/enterprise-server/2-21/1.yml deleted file mode 100644 index d5c0d4cb97..0000000000 --- a/data/release-notes/enterprise-server/2-21/1.yml +++ /dev/null @@ -1,21 +0,0 @@ -date: '2020-06-23' -sections: - security_fixes: - - 'Packages have been updated to the latest security versions. {% comment %} https://github.com/github/enterprise2/pull/20747, https://github.com/github/enterprise2/pull/20727 {% endcomment %}' - bugs: - - 'Excessively large log events could lead to log forwarding instability when UDP was used as the transport mechanism. {% comment %} https://github.com/github/enterprise2/pull/20458, https://github.com/github/enterprise2/pull/20445 {% endcomment %}' - - 'The internal communication service used to access MySQL could restart more often than required, including part way through the upgrade process, which could cause the upgrade to partially fail. We have reduced the rate of restarts and made the code more robust. {% comment %} https://github.com/github/enterprise2/pull/20957, https://github.com/github/enterprise2/pull/20972, https://github.com/github/github/pull/146974 {% endcomment %}' - - "Automatic unsuspension of a user through SSO did not complete if the SSH keys attribute had keys already associated with the user's account. {% comment %} https://github.com/github/github/pull/143475, https://github.com/github/github/pull/142927 {% endcomment %}" - - 'The repository permission hash from the REST API indicated no access for business members who have pull access to internal repositories. {% comment %} https://github.com/github/github/pull/144756, https://github.com/github/github/pull/144292 {% endcomment %}' - - 'The "Repository issue deletion" Enterprise account policy did not reflect the currently saved setting. {% comment %} https://github.com/github/github/pull/145218, https://github.com/github/github/pull/145067 {% endcomment %}' - - 'The audit log did not include branch protection changes events. {% comment %} https://github.com/github/github/pull/145998, https://github.com/github/github/pull/145014 {% endcomment %}' - known_issues: - - 'On a freshly set up GitHub Enterprise Server without any users, an attacker could create the first admin user. {% comment %} https://github.com/github/enterprise2/issues/1889 {% endcomment %}' - - 'Custom firewall rules are not maintained during an upgrade. {% comment %} https://github.com/github/enterprise2/issues/2823 {% endcomment %}' - - '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. {% comment %} https://github.com/github/github/issues/54684 {% endcomment %}' - - '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. {% comment %} https://github.com/github/github/issues/107731 {% endcomment %}' - - '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. {% comment %} https://github.com/github/admin-experience/issues/571 {% endcomment %}' - - 'Security alerts are not reported when pushing to a repository on the command line. {% comment %} https://github.com/github/github/issues/143190 {% endcomment %}' - - 'Audit logs may be attributed to 127.0.0.1 instead of the actual source IP address. (updated 2020-11-02) {% comment %} https://github.com/github/enterprise2/issues/21514 {% endcomment %}' - - "Configuring a repository's permission to `Triage` or `Maintain` fails with an error message." - - '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.' diff --git a/data/release-notes/enterprise-server/2-21/10.yml b/data/release-notes/enterprise-server/2-21/10.yml deleted file mode 100644 index 2c9912398f..0000000000 --- a/data/release-notes/enterprise-server/2-21/10.yml +++ /dev/null @@ -1,15 +0,0 @@ -date: '2020-10-20' -sections: - security_fixes: - - 'Packages have been updated to the latest security versions. {% comment %} https://github.com/github/enterprise2/pull/23096, https://github.com/github/enterprise2/pull/23081 {% endcomment %}' - bugs: - - 'The enterprise account "Confirm two-factor requirement policy" messaging was incorrect. {% comment %} https://github.com/github/github/pull/158736 {% endcomment %}' - known_issues: - - 'On a freshly set up GitHub Enterprise Server without any users, an attacker could create the first admin user. {% comment %} https://github.com/github/enterprise2/issues/1889 {% endcomment %}' - - 'Custom firewall rules are not maintained during an upgrade. {% comment %} https://github.com/github/enterprise2/issues/2823 {% endcomment %}' - - '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. {% comment %} https://github.com/github/github/issues/54684 {% endcomment %}' - - '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. {% comment %} https://github.com/github/github/issues/107731 {% endcomment %}' - - '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. {% comment %} https://github.com/github/admin-experience/issues/571 {% endcomment %}' - - 'Security alerts are not reported when pushing to a repository on the command line. {% comment %} https://github.com/github/github/issues/143190 {% endcomment %}' - - 'Audit logs may be attributed to 127.0.0.1 instead of the actual source IP address. (updated 2020-11-02) {% comment %} https://github.com/github/enterprise2/issues/21514 {% endcomment %}' - - '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.' diff --git a/data/release-notes/enterprise-server/2-21/11.yml b/data/release-notes/enterprise-server/2-21/11.yml deleted file mode 100644 index 606bf949c7..0000000000 --- a/data/release-notes/enterprise-server/2-21/11.yml +++ /dev/null @@ -1,18 +0,0 @@ -date: '2020-11-03' -sections: - security_fixes: - - '**MEDIUM:** High CPU usage could be triggered by a specially crafted request to the SVN bridge resulting in Denial of Service (DoS). {% comment %} https://github.com/github/slumlord/pull/1004, https://github.com/github/slumlord/pull/1000 {% endcomment %}' - - "**LOW:** Incorrect token validation resulted in a reduced entropy for matching tokens during authentication. Analysis shows that in practice there's no significant security risk here. {% comment %} https://github.com/github/github/pull/159455, https://github.com/github/github/pull/159193 {% endcomment %}" - - 'Packages have been updated to the latest security versions. {% comment %} https://github.com/github/enterprise2/pull/23539, https://github.com/github/enterprise2/pull/23171, https://github.com/github/enterprise2/pull/23692, https://github.com/github/enterprise2/pull/23677 {% endcomment %}' - bugs: - - 'Editing issues templates with filenames containing non-ASCII characters would fail with a "500 Internal Server Error". {% comment %} https://github.com/github/github/pull/160589, https://github.com/github/github/pull/159747 {% endcomment %}' - - 'A metric gathering method for background jobs increased CPU utilization. (updated 2020-11-03) {% comment %} https://github.com/github/github/pull/160109 {% endcomment %}' - known_issues: - - 'On a freshly set up GitHub Enterprise Server without any users, an attacker could create the first admin user. {% comment %} https://github.com/github/enterprise2/issues/1889 {% endcomment %}' - - 'Custom firewall rules are not maintained during an upgrade. {% comment %} https://github.com/github/enterprise2/issues/2823 {% endcomment %}' - - '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. {% comment %} https://github.com/github/github/issues/54684 {% endcomment %}' - - '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. {% comment %} https://github.com/github/github/issues/107731 {% endcomment %}' - - '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. {% comment %} https://github.com/github/admin-experience/issues/571 {% endcomment %}' - - 'Security alerts are not reported when pushing to a repository on the command line. {% comment %} https://github.com/github/github/issues/143190 {% endcomment %}' - - 'Audit logs may be attributed to 127.0.0.1 instead of the actual source IP address. {% comment %} https://github.com/github/enterprise2/issues/21514 {% endcomment %}' - - '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.' diff --git a/data/release-notes/enterprise-server/2-21/12.yml b/data/release-notes/enterprise-server/2-21/12.yml deleted file mode 100644 index 5420d17a97..0000000000 --- a/data/release-notes/enterprise-server/2-21/12.yml +++ /dev/null @@ -1,16 +0,0 @@ -date: '2020-11-17' -sections: - security_fixes: - - 'Packages have been updated to the latest security versions. {% comment %} https://github.com/github/enterprise2/pull/23844, https://github.com/github/enterprise2/pull/23712 {% endcomment %}' - bugs: - - 'The babeld logs were missing a separator between seconds and microseconds. {% comment %} https://github.com/github/babeld/pull/1005, https://github.com/github/babeld/pull/1002 {% endcomment %}' - - 'When the enterprise account "Repository visibility change" policy was set to "Enabled", organization owners could not change the visibility of repositories within the organization. {% comment %} https://github.com/github/github/pull/160921, https://github.com/github/github/pull/160773 {% endcomment %}' - - 'Audit logs could be attributed to 127.0.0.1 instead of the actual source IP address. {% comment %} https://github.com/github/github/pull/162436, https://github.com/github/github/pull/161215 {% endcomment %}' - known_issues: - - 'On a freshly set up GitHub Enterprise Server without any users, an attacker could create the first admin user. {% comment %} https://github.com/github/enterprise2/issues/1889 {% endcomment %}' - - 'Custom firewall rules are not maintained during an upgrade. {% comment %} https://github.com/github/enterprise2/issues/2823 {% endcomment %}' - - '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. {% comment %} https://github.com/github/github/issues/54684 {% endcomment %}' - - '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. {% comment %} https://github.com/github/github/issues/107731 {% endcomment %}' - - '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. {% comment %} https://github.com/github/admin-experience/issues/571 {% endcomment %}' - - 'Security alerts are not reported when pushing to a repository on the command line. {% comment %} https://github.com/github/github/issues/143190 {% endcomment %}' - - '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.' diff --git a/data/release-notes/enterprise-server/2-21/13.yml b/data/release-notes/enterprise-server/2-21/13.yml deleted file mode 100644 index 82e4631890..0000000000 --- a/data/release-notes/enterprise-server/2-21/13.yml +++ /dev/null @@ -1,19 +0,0 @@ -date: '2020-12-03' -sections: - bugs: - - 'Authorization service was being detected as unhealthy due to a race condition in the bootstrap which led to restart of the service. {% comment %} https://github.com/github/authzd/pull/1278 {% endcomment %}' - - 'An underlying behavior was causing a service to become unavailable during the hotpatch upgrade process. {% comment %} https://github.com/github/enterprise2/pull/24054, https://github.com/github/enterprise2/issues/23947 {% endcomment %}' - - 'A subset of log forwarding SSL certificates was not being applied correctly. {% comment %} https://github.com/github/enterprise2/pull/24113, https://github.com/github/enterprise2/pull/23981 {% endcomment %}' - - 'Email notifications sent to suspended users when they were removed from a Team or an Organization. {% comment %} https://github.com/github/github/pull/162971, https://github.com/github/github/pull/162742 {% endcomment %}' - - 'The way SSH certificates were applied between Organizations and Businesses was inconsistent. {% comment %} https://github.com/github/github/pull/163426, https://github.com/github/github/pull/159538, https://github.com/github/authentication/issues/115 {% endcomment %}' - - 'When an account was rate limited due to using incorrect passwords, it could be locked out for up to 24 hours. {% comment %} https://github.com/github/github/pull/163436, https://github.com/github/github/pull/162938, https://github.com/github/github-ds/pull/51 {% endcomment %}' - - 'Pull request synchronization on repositories with many references could cause worker queues to fall behind. {% comment %} https://github.com/github/github/pull/163575, https://github.com/github/github/pull/163142 {% endcomment %}' - - 'When signing in after attempting to visit a specific page, people were sent to the home page instead of their intended destination. {% comment %} https://github.com/github/github/pull/163784, https://github.com/github/github/pull/163579, https://github.com/github/github/pull/154117, https://github.com/github/ecosystem-apps/issues/1076 {% endcomment %}' - known_issues: - - 'On a freshly set up GitHub Enterprise Server without any users, an attacker could create the first admin user. {% comment %} https://github.com/github/enterprise2/issues/1889 {% endcomment %}' - - 'Custom firewall rules are not maintained during an upgrade. {% comment %} https://github.com/github/enterprise2/issues/2823 {% endcomment %}' - - '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. {% comment %} https://github.com/github/github/issues/54684 {% endcomment %}' - - '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. {% comment %} https://github.com/github/github/issues/107731 {% endcomment %}' - - '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. {% comment %} https://github.com/github/admin-experience/issues/571 {% endcomment %}' - - 'Security alerts are not reported when pushing to a repository on the command line. {% comment %} https://github.com/github/github/issues/143190 {% endcomment %}' - - '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.' diff --git a/data/release-notes/enterprise-server/2-21/14.yml b/data/release-notes/enterprise-server/2-21/14.yml deleted file mode 100644 index 9b3797670d..0000000000 --- a/data/release-notes/enterprise-server/2-21/14.yml +++ /dev/null @@ -1,13 +0,0 @@ -date: '2020-12-17' -sections: - security_fixes: - - '**LOW:** High CPU usage could be triggered by a specially crafted request to the SVN bridge resulting in Denial of Service (DoS). {% comment %} https://github.com/github/slumlord/pull/1021, https://github.com/github/slumlord/pull/1017 {% endcomment %}' - - 'Packages have been updated to the latest security versions. {% comment %} https://github.com/github/enterprise2/pull/24352, https://github.com/github/enterprise2/pull/23866 {% endcomment %}' - known_issues: - - 'On a freshly set up GitHub Enterprise Server without any users, an attacker could create the first admin user. {% comment %} https://github.com/github/enterprise2/issues/1889 {% endcomment %}' - - 'Custom firewall rules are not maintained during an upgrade. {% comment %} https://github.com/github/enterprise2/issues/2823 {% endcomment %}' - - '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. {% comment %} https://github.com/github/github/issues/54684 {% endcomment %}' - - '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. {% comment %} https://github.com/github/github/issues/107731 {% endcomment %}' - - '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. {% comment %} https://github.com/github/admin-experience/issues/571 {% endcomment %}' - - 'Security alerts are not reported when pushing to a repository on the command line. {% comment %} https://github.com/github/github/issues/143190 {% endcomment %}' - - '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.' diff --git a/data/release-notes/enterprise-server/2-21/15.yml b/data/release-notes/enterprise-server/2-21/15.yml deleted file mode 100644 index 1d96fee086..0000000000 --- a/data/release-notes/enterprise-server/2-21/15.yml +++ /dev/null @@ -1,33 +0,0 @@ -date: '2021-03-02' -sections: - security_fixes: - - '**HIGH:** An improper access control vulnerability was identified in GitHub Enterprise Server that allowed authenticated users of the instance to gain write access to unauthorized repositories via specifically crafted pull requests and REST API requests. An attacker would need to be able to fork the targeted repository, a setting that is disabled by default for organization owned private repositories. Branch protections such as required pull request reviews or status checks would prevent unauthorized commits from being merged without further review or validation. This vulnerability has been assigned CVE-2021-22861. This issue was reported via the [GitHub Bug Bounty Program](https://bounty.github.com).' - - '**HIGH:** An improper access control vulnerability was identified in the GitHub Enterprise Server GraphQL API that allowed authenticated users of the instance to modify the maintainer collaboration permission of a pull request without proper authorization. By exploiting this vulnerability, an attacker would be able to gain access to head branches of pull requests opened on repositories of which they are a maintainer. Forking is disabled by default for organization owned private repositories and would prevent this vulnerability. Additionally, branch protections such as required pull request reviews or status checks would prevent unauthorized commits from being merged without further review or validation. This vulnerability has been assigned CVE-2021-22863. This issue was reported via the [GitHub Bug Bounty Program](https://bounty.github.com).' - - '**HIGH:** A remote code execution vulnerability was identified in GitHub Enterprise Server that could be exploited when building a GitHub Pages site. User-controlled configuration of the underlying parsers used by GitHub Pages were not sufficiently restricted and made it possible to execute commands on the GitHub Enterprise Server instance. To exploit this vulnerability, an attacker would need permission to create and build a GitHub Pages site on the GitHub Enterprise Server instance. This vulnerability has been assigned CVE-2020-10519 and was reported via the [GitHub Bug Bounty Program](https://bounty.github.com).' - - '**MEDIUM:** GitHub Tokens from GitHub Pages builds could end up in logs.' - - '**LOW:** A specially crafted request to the SVN bridge could trigger a long wait before failure resulting in Denial of Service (DoS).' - - 'Packages have been updated to the latest security versions.' - bugs: - - 'The load-balancer health checks in some cases could cause the babeld logs to fill up with errors about the PROXY protocol.' - - 'An informational message was unintentionally logged as an error during GitHub Enterprise Backup Utilities snapshots, which resulted in unnecessary emails being sent when backups were scheduled by cron jobs that listen for output to stderr.' - - 'While restoring a large backup, exception logging related to Redis memory exhaustion could cause the restore to fail due to a full disk.' - - 'When editing a wiki page a user could experience a 500 error when clicking the Save button.' - - 'An S/MIME signed commit using a certificate with multiple names in the subject alternative name would incorrectly show as "Unverified" in the commit badge.' - - 'Suspended user was sent emails when added to a team.' - - 'When a repository had a large number of manifests an error `You have reached the maximum number of allowed manifest files (20) for this repository.` was shown on the Insights -> Dependency graph tab. For more information, see [Visualization limits](https://docs.github.com/en/github/managing-security-vulnerabilities/troubleshooting-the-detection-of-vulnerable-dependencies#are-there-limits-which-affect-the-dependency-graph-data).' - - 'When uploading a new license file with a different number of seats from the previous license file, the seat difference was not correctly represented in the enterprise account Settings -> License page.' - - 'The "Prevent repository admins from changing anonymous Git read access" checkbox available in the enterprise account settings could not be successfully enabled or disabled.' - - 'When a GitHub Pages build failed, the email notification contained an incorrect link for support location.' - - 'During a leap year, the user was getting a 404 response when trying to view Contribution activity on a Monday.' - - 'Visiting the *Explore* section failed with a 500 Internal Server error.' - changes: - - 'Added support for [AWS EC2 r5b instance types](https://aws.amazon.com/about-aws/whats-new/2020/12/introducing-new-amazon-ec2-r5b-instances-featuring-60-gbps-of-ebs-bandwidth-and-260K-iops/).' - - 'Adjusted background queue prioritization to more evenly distribute jobs.' - known_issues: - - 'On a freshly set up GitHub Enterprise 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.' - - 'Security alerts are not reported when pushing to a repository on the command line.' - - '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.' diff --git a/data/release-notes/enterprise-server/2-21/16.yml b/data/release-notes/enterprise-server/2-21/16.yml deleted file mode 100644 index 4736838b30..0000000000 --- a/data/release-notes/enterprise-server/2-21/16.yml +++ /dev/null @@ -1,14 +0,0 @@ -date: '2021-03-16' -sections: - security_fixes: - - Packages have been updated to the latest security versions. - bugs: - - Importing of repository archives from GitHub Enterprise Server that are missing repository files would fail with an error. - known_issues: - - On a freshly set up GitHub Enterprise 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. - - Security alerts are not reported when pushing to a repository on the command line. - - 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. diff --git a/data/release-notes/enterprise-server/2-21/17.yml b/data/release-notes/enterprise-server/2-21/17.yml deleted file mode 100644 index 9c2b33be60..0000000000 --- a/data/release-notes/enterprise-server/2-21/17.yml +++ /dev/null @@ -1,27 +0,0 @@ -date: '2021-03-23' -intro: Downloads have been disabled due to a major bug affecting multiple customers. A fix will be available in the next patch. -sections: - security_fixes: - - '**HIGH:** A remote code execution vulnerability was identified in GitHub Enterprise Server that could be exploited when building a GitHub Pages site. User-controlled configuration options used by GitHub Pages were not sufficiently restricted and made it possible to override environment variables leading to code execution on the GitHub Enterprise Server instance. To exploit this vulnerability, an attacker would need permission to create and build a GitHub Pages site on the GitHub Enterprise Server instance. This vulnerability affected all versions of GitHub Enterprise Server prior to 3.0.3 and was fixed in 3.0.3, 2.22.9, and 2.21.17. This vulnerability was reported via the GitHub Bug Bounty program and has been assigned CVE-2021-22864.' - - Packages have been updated to the latest security versions. - bugs: - - The `ghe-cluster-config-init` run was not fully accounting for the exit code of background jobs leading to improper handling of preflight checks. - changes: - - Logs will rotate based on size in addition to time. - - Use a relative number for consul and nomad `bootstrap_expect` allowing for a cluster to bootstrap even if a handful of nodes are down. - known_issues: - - On a freshly set up GitHub Enterprise 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. - - Security alerts are not reported when pushing to a repository on the command line. - - | - Log rotation may fail to signal services to transition to new log files, leading to older log files continuing to be used, and eventual root disk space exhaustion. - To remedy and/or prevent this issue, run the following commands in the [administrative shell](https://docs.github.com/en/enterprise-server/admin/configuration/accessing-the-administrative-shell-ssh) (SSH), or contact [GitHub Enterprise Support](https://support.github.com/contact) for assistance: - - ``` - printf "PATH=/usr/local/sbin:/usr/local/bin:/usr/local/share/enterprise:/usr/sbin:/usr/bin:/sbin:/bin\n29,59 * * * * root /usr/sbin/logrotate /etc/logrotate.conf\n" | sudo sponge /etc/cron.d/logrotate - sudo /usr/sbin/logrotate -f /etc/logrotate.conf - ``` - - 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. diff --git a/data/release-notes/enterprise-server/2-21/18.yml b/data/release-notes/enterprise-server/2-21/18.yml deleted file mode 100644 index 1efe66af7f..0000000000 --- a/data/release-notes/enterprise-server/2-21/18.yml +++ /dev/null @@ -1,16 +0,0 @@ -date: '2021-04-01' -sections: - security_fixes: - - "**HIGH:** An improper access control vulnerability was identified in GitHub Enterprise Server that allowed access tokens generated from a GitHub App's [web authentication flow](https://docs.github.com/en/developers/apps/identifying-and-authorizing-users-for-github-apps#web-application-flow) to read private repository metadata via the REST API without having been granted the appropriate permissions. To exploit this vulnerability, an attacker would need to create a GitHub App on the instance and have a user authorize the application through the web authentication flow. The private repository metadata returned would be limited to repositories owned by the user the token identifies. This vulnerability affected all versions of GitHub Enterprise Server prior to 3.0.4 and was fixed in versions 3.0.4, 2.22.10, 2.21.18. This vulnerability has been assigned CVE-2021-22865 and was reported via the [GitHub Bug Bounty Program](https://bounty.github.com)." - - Packages have been updated to the latest security versions. - bugs: - - Services were not transitioning to new log files as part of log rotation, resulting in increased disk usage. - - The label on search results for internal repositories was shown as "Private" instead of "Internal". - known_issues: - - On a freshly set up GitHub Enterprise 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. - - Security alerts are not reported when pushing to a repository on the command line. - - '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.' diff --git a/data/release-notes/enterprise-server/2-21/19.yml b/data/release-notes/enterprise-server/2-21/19.yml deleted file mode 100644 index 6be34a199a..0000000000 --- a/data/release-notes/enterprise-server/2-21/19.yml +++ /dev/null @@ -1,18 +0,0 @@ -date: '2021-04-14' -sections: - security_fixes: - - Packages have been updated to the latest security versions. - bugs: - - 'A warning message `jq: error (at :0): Cannot index number with string "settings"` could occur during replica promotion.' - - Visiting the `/settings/emails` page would store state that could cause improper redirects when logging out and logging back in. - - Dependency graph alerts weren't shown for some components whose advisories have upper case package names in `vulnerable_version_ranges`. - - User saw 500 error when executing git operations on an instance configured with LDAP authentication. - - When ghe-migrator encountered import errors, it would sometimes abort the entire process, and the logs did not include enough context. - known_issues: - - On a freshly set up GitHub Enterprise 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. - - Security alerts are not reported when pushing to a repository on the command line. - - '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.' diff --git a/data/release-notes/enterprise-server/2-21/2.yml b/data/release-notes/enterprise-server/2-21/2.yml deleted file mode 100644 index ecf4b02c46..0000000000 --- a/data/release-notes/enterprise-server/2-21/2.yml +++ /dev/null @@ -1,21 +0,0 @@ -date: '2020-07-09' -sections: - security_fixes: - - '**MEDIUM:** Updated nginx to 1.16.1 and addressed CVE-2019-20372. (updated 2020-07-22) {% comment %} https://github.com/github/enterprise2/pull/21252 {% endcomment %}' - - 'Packages have been updated to the latest security versions. {% comment %} https://github.com/github/enterprise2/pull/21089, https://github.com/github/enterprise2/pull/21036 {% endcomment %}' - bugs: - - 'Certain log files did not rotate every 7 days. {% comment %} https://github.com/github/enterprise2/pull/21279, https://github.com/github/enterprise2/pull/21264 {% endcomment %}' - - 'Rapid reuse of webhook source ports resulted in rejected connections. {% comment %} https://github.com/github/enterprise2/pull/21286, https://github.com/github/enterprise2/pull/21280 {% endcomment %}' - - 'Incorrect background jobs could attempt to run on instances configured as passive replicas. {% comment %} https://github.com/github/enterprise2/pull/21317, https://github.com/github/enterprise2/pull/21212, https://github.com/github/enterprise2/issues/21167 {% endcomment %}' - - 'The VPN between nodes could become unstable causing errors to be logged and free space on the root volume to be exhausted. {% comment %} https://github.com/github/enterprise2/pull/21360, https://github.com/github/enterprise2/pull/21357 {% endcomment %}' - - 'Internal repositories were not correctly included in search results for SAML-enabled orgs. {% comment %} https://github.com/github/github/pull/147505, https://github.com/github/github/pull/145692 {% endcomment %}' - known_issues: - - 'On a freshly set up GitHub Enterprise Server without any users, an attacker could create the first admin user. {% comment %} https://github.com/github/enterprise2/issues/1889 {% endcomment %}' - - 'Custom firewall rules are not maintained during an upgrade. {% comment %} https://github.com/github/enterprise2/issues/2823 {% endcomment %}' - - '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. {% comment %} https://github.com/github/github/issues/54684 {% endcomment %}' - - '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. {% comment %} https://github.com/github/github/issues/107731 {% endcomment %}' - - '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. {% comment %} https://github.com/github/admin-experience/issues/571 {% endcomment %}' - - 'Security alerts are not reported when pushing to a repository on the command line. {% comment %} https://github.com/github/github/issues/143190 {% endcomment %}' - - 'Audit logs may be attributed to 127.0.0.1 instead of the actual source IP address. (updated 2020-11-02) {% comment %} https://github.com/github/enterprise2/issues/21514 {% endcomment %}' - - "Configuring a repository's permission to `Triage` or `Maintain` fails with an error message." - - '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.' diff --git a/data/release-notes/enterprise-server/2-21/20.yml b/data/release-notes/enterprise-server/2-21/20.yml deleted file mode 100644 index da65139d80..0000000000 --- a/data/release-notes/enterprise-server/2-21/20.yml +++ /dev/null @@ -1,19 +0,0 @@ -date: '2021-04-28' -sections: - security_fixes: - - Packages have been updated to the latest security versions. - bugs: - - Setup script running on MySQL replication may have caused unnecessary database reseeding during database failover. - - '`config-apply` could take longer than necessary due to `rake db:migrate` being called unnecessarily.' - - Orchestrator could have failed over to a MySQL replica which was not replicating from primary during seeding phase when primary could not be connected. - - Organizations or projects with errors blocked migration and could not be excluded. - changes: - - Preflight checks allow all AWS instance types by default. - known_issues: - - On a freshly set up GitHub Enterprise 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. - - Security alerts are not reported when pushing to a repository on the command line. - - '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.' diff --git a/data/release-notes/enterprise-server/2-21/21.yml b/data/release-notes/enterprise-server/2-21/21.yml deleted file mode 100644 index c5de73a768..0000000000 --- a/data/release-notes/enterprise-server/2-21/21.yml +++ /dev/null @@ -1,15 +0,0 @@ -date: '2021-05-13' -sections: - security_fixes: - - Packages have been updated to the latest security versions. - bugs: - - Orchestrator auto failover could be enabled during the phase of config apply. - - Users with maintainer permissions to a repository were shown an e-mail verification warning instead of a successful page build on the repository Pages settings page. - known_issues: - - On a freshly set up GitHub Enterprise 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. - - Security alerts are not reported when pushing to a repository on the command line. - - '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.' diff --git a/data/release-notes/enterprise-server/2-21/22.yml b/data/release-notes/enterprise-server/2-21/22.yml deleted file mode 100644 index 790fbe4e39..0000000000 --- a/data/release-notes/enterprise-server/2-21/22.yml +++ /dev/null @@ -1,16 +0,0 @@ -date: '2021-05-25' -sections: - 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: - - An IP address added by an admin using the "Create Whitelist Entry" button could still be locked out. - - In a cluster or HA environment, GitHub Pages builds could be triggered on secondary nodes where they would fail. - known_issues: - - On a freshly set up GitHub Enterprise 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. - - Security alerts are not reported when pushing to a repository on the command line. - - '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.' diff --git a/data/release-notes/enterprise-server/2-21/23.yml b/data/release-notes/enterprise-server/2-21/23.yml deleted file mode 100644 index 3716c433b7..0000000000 --- a/data/release-notes/enterprise-server/2-21/23.yml +++ /dev/null @@ -1,16 +0,0 @@ -date: '2021-06-10' -sections: - security_fixes: - - Packages have been updated to the latest security versions. - bugs: - - Import failures of organizations or repositories from non-GitHub sources could produce an `undefined method '[]' for nil:NilClass` error. - changes: - - Users of the GraphQL API can query the public field `closingIssuesReferences` on the `PullRequest` object. This field retrieves issues that will be automatically closed when the related pull request is merged. This approach will also allow this data to be migrated in future, as part of a higher fidelity migration process. - known_issues: - - On a freshly set up GitHub Enterprise 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. - - Security alerts are not reported when pushing to a repository on the command line. - - '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.' diff --git a/data/release-notes/enterprise-server/2-21/3.yml b/data/release-notes/enterprise-server/2-21/3.yml deleted file mode 100644 index 8a3fd7d4cc..0000000000 --- a/data/release-notes/enterprise-server/2-21/3.yml +++ /dev/null @@ -1,18 +0,0 @@ -date: '2020-07-21' -sections: - security_fixes: - - 'Packages have been updated to the latest security versions. {% comment %} https://github.com/github/enterprise2/pull/21438, https://github.com/github/enterprise2/pull/21402, https://github.com/github/enterprise2/pull/21496, https://github.com/github/enterprise2/pull/21479 {% endcomment %}' - bugs: - - 'The Management Console monitor graphs would sometimes not display correctly on larger screens. {% comment %} https://github.com/github/enterprise2/pull/21398, https://github.com/github/enterprise2/pull/21381 {% endcomment %}' - - 'GitHub App Manifest creation flow was unusable in some scenarios when a SameSite Cookie policy was applied. {% comment %} https://github.com/github/github/pull/147829, https://github.com/github/github/pull/144121 {% endcomment %}' - - "In some circumstances, accessing the 'Explore' page would throw an application error. {% comment %} https://github.com/github/github/pull/149605, https://github.com/github/github/pull/148949 {% endcomment %}" - known_issues: - - 'On a freshly set up GitHub Enterprise Server without any users, an attacker could create the first admin user. {% comment %} https://github.com/github/enterprise2/issues/1889 {% endcomment %}' - - 'Custom firewall rules are not maintained during an upgrade. {% comment %} https://github.com/github/enterprise2/issues/2823 {% endcomment %}' - - '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. {% comment %} https://github.com/github/github/issues/54684 {% endcomment %}' - - '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. {% comment %} https://github.com/github/github/issues/107731 {% endcomment %}' - - '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. {% comment %} https://github.com/github/admin-experience/issues/571 {% endcomment %}' - - 'Security alerts are not reported when pushing to a repository on the command line. {% comment %} https://github.com/github/github/issues/143190 {% endcomment %}' - - 'Audit logs may be attributed to 127.0.0.1 instead of the actual source IP address. (updated 2020-11-02) {% comment %} https://github.com/github/enterprise2/issues/21514 {% endcomment %}' - - "Configuring a repository's permission to `Triage` or `Maintain` fails with an error message." - - '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.' diff --git a/data/release-notes/enterprise-server/2-21/4.yml b/data/release-notes/enterprise-server/2-21/4.yml deleted file mode 100644 index a02e4b938e..0000000000 --- a/data/release-notes/enterprise-server/2-21/4.yml +++ /dev/null @@ -1,28 +0,0 @@ -date: '2020-08-11' -sections: - security_fixes: - - '{% octicon "alert" aria-label="The alert icon" %} **Critical:** A remote code execution vulnerability was identified in GitHub Pages that could allow an attacker to execute commands as part building a GitHub Pages site. This issue was due to an outdated and vulnerable dependency used in the Pages build process. To exploit this vulnerability, an attacker would need permission to create and build a GitHub Pages site on the GitHub Enterprise Server instance. This vulnerability affected all versions of GitHub Enterprise Server. To mitigate this vulnerability, Kramdown has been updated to address CVE-2020-14001. {% comment %} https://github.com/github/pages/pull/2835, https://github.com/github/pages/pull/2827 {% endcomment %}' - - '**High:** High: An attacker could inject a malicious argument into a Git sub-command when executed on GitHub Enterprise Server. This could allow an attacker to overwrite arbitrary files with partially user-controlled content and potentially execute arbitrary commands on the GitHub Enterprise Server instance. To exploit this vulnerability, an attacker would need permission to access repositories within the GHES instance. However, due to other protections in place, we could not identify a way to actively exploit this vulnerability. This vulnerability was reported through the GitHub Security Bug Bounty program. {% comment %} https://github.com/github/github/pull/150936, https://github.com/github/github/pull/150634 {% endcomment %}' - - 'Packages have been updated to the latest security versions. {% comment %} https://github.com/github/enterprise2/pull/21679, https://github.com/github/enterprise2/pull/21542, https://github.com/github/enterprise2/pull/21812, https://github.com/github/enterprise2/pull/21700 {% endcomment %}' - bugs: - - 'A Consul configuration error prevented some background jobs from being processed on standalone instances. {% comment %} https://github.com/github/enterprise2/pull/21463 {% endcomment %}' - - 'The service memory allocation calculation could allocate an incorrect or unbounded memory allocation to a service resulting in poor system performance. {% comment %} https://github.com/github/enterprise2/pull/21689 {% endcomment %}' - - 'The virtualization platform for oVirt KVM systems was not properly detected, causing problems during upgrades. {% comment %} https://github.com/github/enterprise2/pull/21731, https://github.com/github/enterprise2/pull/21669 {% endcomment %}' - - "The error message for invalid authentication with a password via Git command line didn't populate the URL linking to adding the appropriate token or SSH key. {% comment %} https://github.com/github/github/pull/149607, https://github.com/github/github/pull/149351 {% endcomment %}" - - 'Creating an issue on a user repository using the Issue Template feature could fail with an Internal Server Error. {% comment %} https://github.com/github/github/pull/150173, https://github.com/github/github/pull/149445 {% endcomment %}' - - 'Visiting the *Explore* section failed with a 500 Internal Server error. {% comment %} https://github.com/github/github/pull/150512, https://github.com/github/github/pull/150504 {% endcomment %}' - - 'Issues could not be sorted by *Recently updated* on repositories migrated to a new instance. {% comment %} https://github.com/github/github/pull/150688, https://github.com/github/github/pull/149330 {% endcomment %}' - - 'GitHub Connect was using a deprecated GitHub.com API endpoint. {% comment %} https://github.com/github/github/pull/150827, https://github.com/github/github/pull/150545 {% endcomment %}' - - 'Internal metrics gathering for background jobs contributed to CPU and memory use unnecessarily. {% comment %} https://github.com/github/github/pull/151182, https://github.com/github/github/pull/147695 {% endcomment %}' - - 'The 404 page contained GitHub.com contact and status links in the footer. {% comment %} https://github.com/github/github/pull/151315 {% endcomment %}' - - 'Background jobs for an unreleased feature were queued and left unprocessed. {% comment %} https://github.com/github/github/pull/151395, https://github.com/github/github/pull/146248 {% endcomment %}' - known_issues: - - 'On a freshly set up GitHub Enterprise Server without any users, an attacker could create the first admin user. {% comment %} https://github.com/github/enterprise2/issues/1889 {% endcomment %}' - - 'Custom firewall rules are not maintained during an upgrade. {% comment %} https://github.com/github/enterprise2/issues/2823 {% endcomment %}' - - '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. {% comment %} https://github.com/github/github/issues/54684 {% endcomment %}' - - '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. {% comment %} https://github.com/github/github/issues/107731 {% endcomment %}' - - '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. {% comment %} https://github.com/github/admin-experience/issues/571 {% endcomment %}' - - 'Security alerts are not reported when pushing to a repository on the command line. {% comment %} https://github.com/github/github/issues/143190 {% endcomment %}' - - 'Audit logs may be attributed to 127.0.0.1 instead of the actual source IP address. (updated 2020-11-02) {% comment %} https://github.com/github/enterprise2/issues/21514 {% endcomment %}' - - "Configuring a repository's permission to `Triage` or `Maintain` fails with an error message." - - '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.' diff --git a/data/release-notes/enterprise-server/2-21/5.yml b/data/release-notes/enterprise-server/2-21/5.yml deleted file mode 100644 index fa46636234..0000000000 --- a/data/release-notes/enterprise-server/2-21/5.yml +++ /dev/null @@ -1,16 +0,0 @@ -date: '2020-08-12' -sections: - bugs: - - 'Resolved an issue that could lead to high CPU usage while generating system configuration templates. {% comment %} https://github.com/github/enterprise2/pull/21786, https://github.com/github/enterprise2/pull/21741 {% endcomment %}' - - 'Recent changes to memory allocations could lead to a degradation in system performance {% comment %} https://github.com/github/enterprise2/pull/22066 {% endcomment %}' - - 'Temporary connectivity issues while running database migrations could cause data loss. {% comment %} https://github.com/github/enterprise2/pull/22128, https://github.com/github/enterprise2/pull/22100 {% endcomment %}' - known_issues: - - 'On a freshly set up GitHub Enterprise Server without any users, an attacker could create the first admin user. {% comment %} https://github.com/github/enterprise2/issues/1889 {% endcomment %}' - - 'Custom firewall rules are not maintained during an upgrade. {% comment %} https://github.com/github/enterprise2/issues/2823 {% endcomment %}' - - '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. {% comment %} https://github.com/github/github/issues/54684 {% endcomment %}' - - '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. {% comment %} https://github.com/github/github/issues/107731 {% endcomment %}' - - '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. {% comment %} https://github.com/github/admin-experience/issues/571 {% endcomment %}' - - 'Security alerts are not reported when pushing to a repository on the command line. {% comment %} https://github.com/github/github/issues/143190 {% endcomment %}' - - 'Audit logs may be attributed to 127.0.0.1 instead of the actual source IP address. (updated 2020-11-02) {% comment %} https://github.com/github/enterprise2/issues/21514 {% endcomment %}' - - "Configuring a repository's permission to `Triage` or `Maintain` fails with an error message." - - '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.' diff --git a/data/release-notes/enterprise-server/2-21/6.yml b/data/release-notes/enterprise-server/2-21/6.yml deleted file mode 100644 index c9ef772868..0000000000 --- a/data/release-notes/enterprise-server/2-21/6.yml +++ /dev/null @@ -1,28 +0,0 @@ -date: '2020-08-26' -sections: - security_fixes: - - >- - {% octicon "alert" aria-label="The alert icon" %} **Critical:** A remote code execution vulnerability was identified in GitHub Pages that could be exploited when building a GitHub Pages site. User-controlled configuration of the underlying parsers used by GitHub Pages were not sufficiently restricted and made it possible to execute commands on the GitHub Enterprise Server instance. To exploit this vulnerability, an attacker would need permission to create and build a GitHub Pages site on the GitHub Enterprise Server instance. This vulnerability affected all versions of GitHub Enterprise Server. The underlying issues contributing to this vulnerability were identified both internally and through the GitHub Security Bug Bounty program. We have issued CVE-2020-10518. {% comment %} https://github.com/github/pages/pull/2882, https://github.com/github/pages/pull/2902, https://github.com/github/pages/pull/2894, https://github.com/github/pages/pull/2877, https://github.com/github/pages-gem/pull/700, - https://github.com/github/pages/pull/2889, https://github.com/github/pages/pull/2899, https://github.com/github/pages/pull/2903, https://github.com/github/pages/pull/2890, https://github.com/github/pages/pull/2891, https://github.com/github/pages/pull/2884 {% endcomment %} - - '**Medium:** An improper access control vulnerability was identified that allowed authenticated users of the instance to determine the names of unauthorized private repositories given their numerical IDs. This vulnerability did not allow unauthorized access to any repository content besides the name. This vulnerability affected all versions of GitHub Enterprise Server prior to 2.22 and has been assigned [CVE-2020-10517](https://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2020-10517). The vulnerability was reported via the [GitHub Bug Bounty program](https://bounty.github.com). {% comment %} https://github.com/github/github/pull/151986, https://github.com/github/github/pull/151713 {% endcomment %}' - - 'Packages have been updated to the latest security versions. {% comment %} https://github.com/github/enterprise2/pull/21853, https://github.com/github/enterprise2/pull/21828, https://github.com/github/enterprise2/pull/22154, https://github.com/github/enterprise2/pull/21920, https://github.com/github/enterprise2/pull/22216, https://github.com/github/enterprise2/pull/22190 {% endcomment %}' - bugs: - - 'A message was not logged when the ghe-config-apply process had finished running ghe-es-auto-expand. {% comment %} https://github.com/github/enterprise2/pull/22178, https://github.com/github/enterprise2/pull/22171 {% endcomment %}' - - 'Excessive logging to the `syslog` file could occur on high-availability replicas if the primary appliance is unavailable. {% comment %} https://github.com/github/enterprise2/pull/22268, https://github.com/github/enterprise2/pull/22124 {% endcomment %}' - - "Database re-seeding on a replica could fail with an error: `Got packet bigger than 'max_allowed_packet'` {% comment %} https://github.com/github/enterprise2/pull/22322, https://github.com/github/enterprise2/pull/20063 {% endcomment %}" - - 'In some cases duplicate user data could cause a 500 error while running the ghe-license-usage script. {% comment %} https://github.com/github/github/pull/152637 {% endcomment %}' - - 'Using `ghe-migrator`, the `add` command would fail to lock a repository when using the `--lock` flag. {% comment %} https://github.com/github/github/pull/152780, https://github.com/github/github/pull/152588 {% endcomment %}' - changes: - - 'In a high availability or geo-replication configuration, replica instances would exit maintenance mode when ghe-config-apply ran. {% comment %} https://github.com/github/enterprise2/pull/21777, https://github.com/github/enterprise2/pull/21440 {% endcomment %}' - - "We've added support for the R5a and R5n AWS instance types. {% comment %} https://github.com/github/enterprise2/pull/21903, https://github.com/github/enterprise2/pull/21173 {% endcomment %}" - - 'Removed the license seat count information on the administrative SSH MOTD due to a performance issue impacting GitHub Enterprise Server clusters. {% comment %} https://github.com/github/enterprise2/pull/21994, https://github.com/github/enterprise2/pull/21870 {% endcomment %}' - known_issues: - - 'On a freshly set up GitHub Enterprise Server without any users, an attacker could create the first admin user. {% comment %} https://github.com/github/enterprise2/issues/1889 {% endcomment %}' - - 'Custom firewall rules are not maintained during an upgrade. {% comment %} https://github.com/github/enterprise2/issues/2823 {% endcomment %}' - - '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. {% comment %} https://github.com/github/github/issues/54684 {% endcomment %}' - - '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. {% comment %} https://github.com/github/github/issues/107731 {% endcomment %}' - - '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. {% comment %} https://github.com/github/admin-experience/issues/571 {% endcomment %}' - - 'Security alerts are not reported when pushing to a repository on the command line. {% comment %} https://github.com/github/github/issues/143190 {% endcomment %}' - - 'Audit logs may be attributed to 127.0.0.1 instead of the actual source IP address. (updated 2020-11-02) {% comment %} https://github.com/github/enterprise2/issues/21514 {% endcomment %}' - - "Configuring a repository's permission to `Triage` or `Maintain` fails with an error message." - - '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.' diff --git a/data/release-notes/enterprise-server/2-21/7.yml b/data/release-notes/enterprise-server/2-21/7.yml deleted file mode 100644 index 7f2ec280c2..0000000000 --- a/data/release-notes/enterprise-server/2-21/7.yml +++ /dev/null @@ -1,15 +0,0 @@ -date: '2020-09-08' -sections: - bugs: - - 'A service health check caused session growth resulting in filesystem inode exhaustion. {% comment %} https://github.com/github/enterprise2/pull/22481, https://github.com/github/enterprise2/pull/22475 {% endcomment %}' - - "Upgrading using a hotpatch could fail with an error: `'libdbi1' was not found` {% comment %} https://github.com/github/enterprise2/pull/22556, https://github.com/github/enterprise2/pull/22552 {% endcomment %}" - - "Configuring a repository's permission to `Triage` or `Maintain` no longer fails." - known_issues: - - 'On a freshly set up GitHub Enterprise Server without any users, an attacker could create the first admin user. {% comment %} https://github.com/github/enterprise2/issues/1889 {% endcomment %}' - - 'Custom firewall rules are not maintained during an upgrade. {% comment %} https://github.com/github/enterprise2/issues/2823 {% endcomment %}' - - '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. {% comment %} https://github.com/github/github/issues/54684 {% endcomment %}' - - '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. {% comment %} https://github.com/github/github/issues/107731 {% endcomment %}' - - '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. {% comment %} https://github.com/github/admin-experience/issues/571 {% endcomment %}' - - 'Security alerts are not reported when pushing to a repository on the command line. {% comment %} https://github.com/github/github/issues/143190 {% endcomment %}' - - 'Audit logs may be attributed to 127.0.0.1 instead of the actual source IP address. (updated 2020-11-02) {% comment %} https://github.com/github/enterprise2/issues/21514 {% endcomment %}' - - '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.' diff --git a/data/release-notes/enterprise-server/2-21/8.yml b/data/release-notes/enterprise-server/2-21/8.yml deleted file mode 100644 index 0bada09136..0000000000 --- a/data/release-notes/enterprise-server/2-21/8.yml +++ /dev/null @@ -1,16 +0,0 @@ -date: '2020-09-23' -sections: - security_fixes: - - '**MEDIUM**: ImageMagick has been updated to address [DSA-4715-1](https://www.debian.org/security/2020/dsa-4715). {% comment %} https://github.com/github/enterprise2/pull/22621, https://github.com/github/enterprise2/pull/22610 {% endcomment %}' - - 'Packages have been updated to the latest security versions. {% comment %} https://github.com/github/enterprise2/pull/22571, https://github.com/github/enterprise2/pull/22426, https://github.com/github/enterprise2/pull/22602, https://github.com/github/enterprise2/pull/22592, https://github.com/github/enterprise2/pull/22719, https://github.com/github/enterprise2/pull/22699 {% endcomment %}' - bugs: - - 'Admins were unable to see delivered repository webhooks and instead saw "Sorry, something went wrong and we weren''t able to fetch the deliveries for this hook". {% comment %} https://github.com/github/authzd/pull/1181, https://github.com/github/authzd/pull/980 {% endcomment %}' - known_issues: - - 'On a freshly set up GitHub Enterprise Server without any users, an attacker could create the first admin user. {% comment %} https://github.com/github/enterprise2/issues/1889 {% endcomment %}' - - 'Custom firewall rules are not maintained during an upgrade. {% comment %} https://github.com/github/enterprise2/issues/2823 {% endcomment %}' - - '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. {% comment %} https://github.com/github/github/issues/54684 {% endcomment %}' - - '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. {% comment %} https://github.com/github/github/issues/107731 {% endcomment %}' - - '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. {% comment %} https://github.com/github/admin-experience/issues/571 {% endcomment %}' - - 'Security alerts are not reported when pushing to a repository on the command line. {% comment %} https://github.com/github/github/issues/143190 {% endcomment %}' - - 'Audit logs may be attributed to 127.0.0.1 instead of the actual source IP address. (updated 2020-11-02) {% comment %} https://github.com/github/enterprise2/issues/21514 {% endcomment %}' - - '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.' diff --git a/data/release-notes/enterprise-server/2-21/9.yml b/data/release-notes/enterprise-server/2-21/9.yml deleted file mode 100644 index 8be05dfa05..0000000000 --- a/data/release-notes/enterprise-server/2-21/9.yml +++ /dev/null @@ -1,29 +0,0 @@ -date: '2020-10-09' -sections: - security_fixes: - - 'A user whose **LDAP** directory username standardizes to an existing GHES account login could authenticate into the existing account. {% comment %} https://github.com/github/github/pull/156517, https://github.com/github/github/pull/155512 {% endcomment %}' - - 'Packages have been updated to the latest security versions. {% comment %} https://github.com/github/enterprise2/pull/22911, https://github.com/github/enterprise2/pull/22878 {% endcomment %}' - bugs: - - 'The NameID Format dropdown in the Management Console would be reset to "unspecified" after setting it to "persistent". {% comment %} https://github.com/github/enterprise2/pull/22402, https://github.com/github/enterprise2/pull/22331, https://github.com/github/enterprise2/issues/13446 {% endcomment %}' - - 'Saving settings via the [management console](/admin/configuration/accessing-the-management-console) would append a newline to the [TLS/SSL certificate and key](/admin/configuration/configuring-tls) files which triggered unnecessary reloading of some services. {% comment %} https://github.com/github/enterprise2/pull/22608, https://github.com/github/enterprise2/pull/22540 {% endcomment %}' - - 'System logs for Dependency Graph were not rotating, allowing unbounded storage growth. {% comment %} https://github.com/github/enterprise2/pull/22766, https://github.com/github/enterprise2/pull/22733 {% endcomment %}' - - 'Upgrade could fail if the resqued workers override setting is in use. {% comment %} https://github.com/github/enterprise2/pull/22838, https://github.com/github/enterprise2/pull/22814 {% endcomment %}' - - 'When importing a repository with `ghe-migrator`, an unexpected exception could occur when inconsistent data is present. {% comment %} https://github.com/github/github/pull/153849, https://github.com/github/github/pull/151552 {% endcomment %}' - - 'Links to GitHub Security Advisories would use a URL with the hostname of the GitHub Enterprise Server instance instead of GitHub.com, directing the user to a nonexistent URL. {% comment %} https://github.com/github/github/pull/153853, https://github.com/github/github/pull/151301 {% endcomment %}' - - 'The enterprise account security settings page showed a "View your organizations'' current configurations" link for the "Two-factor authentication" setting when the authentication mode in use does not support built in two-factor authentication. {% comment %} https://github.com/github/github/pull/153861 {% endcomment %}' - - 'When using `ghe-migrator` to import PR review requests, records associated with deleted users would result in extraneous database records. {% comment %} https://github.com/github/github/pull/154959, https://github.com/github/github/pull/153169 {% endcomment %}' - - 'When importing users with `ghe-migrator`, an error of "Emails is invalid" would occur if the system-generated email address were longer than 100 characters. {% comment %} https://github.com/github/github/pull/155110, https://github.com/github/github/pull/152418 {% endcomment %}' - - 'Logging webhook activity could use large amounts of disk space and cause the root disk to become full. {% comment %} https://github.com/github/github/pull/155656, https://github.com/github/github/pull/154100 {% endcomment %}' - changes: - - 'Support is added for the AWS EC2 instance type `m5.16xlarge`. {% comment %} https://github.com/github/enterprise2/pull/22501, https://github.com/github/enterprise2/pull/22473 {% endcomment %}' - - 'Remove the requirement for SSH fingerprints in `ghe-migrator` archives as it can always be computed. {% comment %} https://github.com/github/github/pull/156945, https://github.com/github/github/pull/155387 {% endcomment %}' - - 'GitHub App Manifests now include the `request_oauth_on_install` field. {% comment %} https://github.com/github/github/pull/156994, https://github.com/github/github/pull/155010, https://github.com/github/ecosystem-apps/issues/1055 {% endcomment %}' - known_issues: - - 'On a freshly set up GitHub Enterprise Server without any users, an attacker could create the first admin user. {% comment %} https://github.com/github/enterprise2/issues/1889 {% endcomment %}' - - 'Custom firewall rules are not maintained during an upgrade. {% comment %} https://github.com/github/enterprise2/issues/2823 {% endcomment %}' - - '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. {% comment %} https://github.com/github/github/issues/54684 {% endcomment %}' - - '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. {% comment %} https://github.com/github/github/issues/107731 {% endcomment %}' - - '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. {% comment %} https://github.com/github/admin-experience/issues/571 {% endcomment %}' - - 'Security alerts are not reported when pushing to a repository on the command line. {% comment %} https://github.com/github/github/issues/143190 {% endcomment %}' - - 'Audit logs may be attributed to 127.0.0.1 instead of the actual source IP address. (updated 2020-11-02) {% comment %} https://github.com/github/enterprise2/issues/21514 {% endcomment %}' - - '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.' diff --git a/data/release-notes/enterprise-server/2-22/0.yml b/data/release-notes/enterprise-server/2-22/0.yml deleted file mode 100644 index 8525a93483..0000000000 --- a/data/release-notes/enterprise-server/2-22/0.yml +++ /dev/null @@ -1,143 +0,0 @@ -intro: GitHub is excited to present GitHub Enterprise Server 2.22.0. -date: '2020-09-23' -sections: - features: - - heading: GitHub Actions Beta - notes: - - | - [GitHub Actions](https://github.com/features/actions) is a powerful, flexible solution for CI/CD and workflow automation. GitHub Actions on Enterprise Server includes tools to help you manage the service, including key metrics in the Management Console, audit logs and access controls to help you control the roll out. - - You will need to provide your own [storage](https://docs.github.com/en/enterprise/2.22/admin/github-actions/enabling-github-actions-and-configuring-storage) and runners for GitHub Actions. AWS S3, Azure Blob Storage and MinIO are supported. Please review the [updated minimum requirements for your platform](https://docs.github.com/en/enterprise/2.22/admin/installation/setting-up-a-github-enterprise-server-instance) before you turn on GitHub Actions. To learn more, contact the GitHub Sales team or [sign up for the beta](https://resources.github.com/beta-signup/). {% comment %} https://github.com/github/releases/issues/775 {% endcomment %} - - - heading: GitHub Packages Beta - notes: - - | - [GitHub Packages](https://github.com/features/packages) is a package hosting service, natively integrated with GitHub APIs, Actions, and webhooks. Create an [end-to-end DevOps workflow](https://docs.github.com/en/enterprise/2.22/admin/packages/configuring-packages-support-for-your-enterprise) that includes your code, continuous integration, and deployment solutions. - - Supported storage back ends include AWS S3 and MinIO with support for Azure blob coming in a future release. Please note that the current Docker support will be replaced by a beta of the new GitHub Container Registry in the next release. Please review the [updated minimum requirements for your platform](https://docs.github.com/en/enterprise/2.22/admin/installation/setting-up-a-github-enterprise-server-instance) before you turn on GitHub Packages. To learn more, contact the GitHub Sales team or [sign up for the beta](https://resources.github.com/beta-signup/). {% comment %} https://github.com/github/releases/issues/773 {% endcomment %} - - - heading: Advanced Security Code Scanning Beta - notes: - - | - [GitHub Advanced Security code scanning](https://github.com/features/security) is a developer-first, GitHub-native static application security testing (SAST). Easily find security vulnerabilities before they reach production, all powered by the world’s most powerful code analysis engine: CodeQL. - - Administrators using GitHub Advanced Security can [sign up for](https://resources.github.com/beta-signup/) and [enable](https://docs.github.com/en/enterprise/2.22/admin/configuration/configuring-code-scanning-for-your-appliance) GitHub Advanced Security code scanning beta. Please review the [updated minimum requirements for your platform](https://docs.github.com/en/enterprise/2.22/admin/installation/setting-up-a-github-enterprise-server-instance) before you turn on GitHub Advanced Security code scanning. {% comment %} https://github.com/github/releases/issues/768 {% endcomment %} - - - heading: Pull Request Retargeting - notes: - - | - When a [pull request's head branch](https://docs.github.com/en/enterprise/2.22/user/github/collaborating-with-issues-and-pull-requests/about-branches#working-with-branches) is merged and deleted, all other open pull requests in the same repository that target this branch are now retargeted to the merged pull request's base branch. Previously these pull requests were closed. {% comment %} https://github.com/github/releases/issues/801 {% endcomment %} - - - heading: Suspend and Unsuspend an App Installation - notes: - - | - Administrators and users can [suspend any GitHub App’s access](https://docs.github.com/enterprise/2.22/user/rest/reference/apps#suspend-an-app-installation) for as long as needed, and [unsuspend the app](https://docs.github.com/enterprise/2.22/user/rest/reference/apps#unsuspend-an-app-installation) on command through Settings and the API. Suspended apps cannot access the GitHub API or webhook events. You can use this instead of uninstalling an application, which deauthorises every user. {% comment %} https://github.com/github/github/pull/138316 https://github.com/github/github/pull/150869 {% endcomment %}'' - - - heading: Improved Large Scale Performance - notes: - - | - We have revised the approach we take to scheduling network maintenance for repositories, ensuring large monorepos are able to avoid failure states. {% comment %} https://github.com/github/github/pull/146789, https://github.com/github/github/pull/147931, https://github.com/github/github/pull/146724, https://github.com/github/git-protocols/issues/94 {% endcomment %}'' - - Passive replicas are now [supported and configurable on GitHub Enterprise Server cluster deployments](https://docs.github.com/en/enterprise/2.22/admin/enterprise-management/configuring-high-availability-replication-for-a-cluster). These changes will enable faster failover, reducing RTO and RPO. {% comment %} https://github.com/github/releases/issues/905 {% endcomment %} - - - heading: View All of Your Users - notes: - - | - For exceptionally large teams, administrators can [adjust the 1,500 default maximum for user lists](https://docs.github.com/en/enterprise/2.22/admin/configuration/command-line-utilities#ghe-config). {% comment %} https://github.com/github/github/pull/146508 {% endcomment %}'' - - changes: - - heading: Administration Changes - notes: - - Shared workers have been enabled to make live updates more resilient by sharing connections across tabs. {% comment %} https://github.com/github/releases/issues/914 {% endcomment %} - - The "Contact Support" link on `50x` error pages now links to the support email or link configured in the Management Console. {% comment %} https://github.com/github/github/pull/142123 {% endcomment %} - - It's now possible to [manage global announcements and expiration dates through the enterprise account settings](https://docs.github.com/en/enterprise/2.22/admin/installation/command-line-utilities#ghe-announce). {% comment %} https://github.com/github/releases/issues/945, https://github.com/github/github/pull/148475, https://github.com/github/github/pull/148494 {% endcomment %} - - You can now [exempt certain users from the default API rate limits configured in the management console](https://docs.github.com/en/enterprise/2.22/admin/configuration/configuring-rate-limits), if necessary. {% comment %} https://github.com/github/github/pull/148673 {% endcomment %} - - Repository administrators can now [set their repository to any available visibility option](https://docs.github.com/en/enterprise/2.22/user/github/administering-a-repository/setting-repository-visibility) from a single dialog in the repository's settings. Previously, you had to navigate separate sections, buttons, and dialog boxes for changing between public and private and between private and internal. {% comment %} https://github.com/github/releases/issues/882 {% endcomment %} - - A new Enterprise settings link on the user dropdown menu makes it easier to navigate to Enterprise Account Settings. {% comment %} https://github.com/github/releases/issues/946, https://github.com/github/github/pull/150595, https://github.com/github/github/pull/150520, https://github.com/github/github/pull/151121, https://github.com/github/hydro-schemas/pull/1244 {% endcomment %} - - The legacy "Admin Center" link on the /stafftools page has been removed. The "Enterprise" link is now the best way to navigate to the Enterprise Account from the /stafftools page. {% comment %} https://github.com/github/github/pull/147633 {% endcomment %} - - The Options sub-menu item in the Enterprise Account settings has been moved from the Settings section to the Policies section. {% comment %} https://github.com/github/releases/issues/944, https://github.com/github/github/pull/148477 {% endcomment %} - - '[Accessing resources by using a personal access token or SSH key now counts as user activity](https://docs.github.com/en/enterprise/2.22/admin/user-management/managing-dormant-users). This relieves administrators from the burden of filtering out certain users from the user dormancy reports and makes it safer to use the "Suspend all" button without accidentally suspending users who only accessed GitHub in a read-only way over the APIs with a Personal Access Token (PAT) or SSH key. {% comment %} https://github.com/github/github/pull/140433, https://github.com/github/help-docs/pull/14853, https://github.com/github/customer-feedback/issues/174, https://github.com/github/supportability/issues/14 {% endcomment %}' - - - heading: Security Changes - notes: - - Two-factor recovery codes can no longer be used during the two-factor sign in process. One-Time-Passwords are the only acceptable values. {% comment %} https://github.com/github/github/pull/145016, https://github.com/github/github/pull/140208 {% endcomment %} - - When a user is signed into GitHub Enterprise Server through single sign-on, the [default repository visibility selection is Private](https://docs.github.com/en/enterprise/2.22/user/github/administering-a-repository/setting-repository-visibility). {% comment %} https://github.com/github/releases/issues/872 {% endcomment %} - - Owners of GitHub Apps can now choose to have their [user-to-server access tokens expire after 8 hours](https://developer.github.com/changes/2020-04-30-expiring-user-to-server-access-tokens-for-github-apps/), to help enforce regular token rotation and reduce the impact of a compromised token. {% comment %} https://github.com/github/releases/issues/966 {% endcomment %} - - - heading: Developer Changes - notes: - - '[The GitHub UI has undergone a design refresh](https://github.blog/changelog/2020-06-23-design-updates-to-repositories-and-github-ui/), and the repositories homepage has been redesigned, including a responsive layout and improved mobile web experience. {% comment %} https://github.com/github/releases/issues/886 {% endcomment %}' - - In the "Clone with SSH" repository dropdown menu, users will now be notified if they do not have any keys setup. {% comment %} https://github.com/github/github/pull/149098 {% endcomment %} - - Commits are now ordered chronologically in the pull request timeline and commits tab. This new ordering is also reflected in the ["List commits on a pull request"](https://docs.github.com/en/enterprise/2.22/user/rest/reference/pulls#list-commits-on-a-pull-request) REST API and GraphQL ["PullRequest object"](https://docs.github.com/en/enterprise/2.22/user/graphql/reference/objects#pullrequest) timeline connection. {% comment %} https://github.com/github/releases/issues/867 {% endcomment %} - - Users can now [set a skin tone default for emoji autocomplete results](https://github.blog/changelog/2020-07-17-customizable-skin-tones-in-emoji-autocomplete/) in comment text areas. {% comment %} https://github.com/github/releases/issues/916 {% endcomment %} - - '[Tree-sitter](https://github.com/tree-sitter/tree-sitter) improves syntax highlighting and is now the default library used for language parsing. {% comment %} https://github.com/github/releases/issues/918, https://github.com/github/windrose/issues/44 {% endcomment %}' - - - heading: Users and organizations can add Twitter usernames to their GitHub profiles - notes: - - '[Developers and organizations can now add their Twitter username to their profile](https://github.blog/changelog/2020-07-22-users-and-organizations-can-now-add-twitter-usernames-to-their-github-profiles/) {% comment %} https://github.com/github/github/pull/145127 {% endcomment %}' - - - heading: API Changes - notes: - - | - #### Graduated Previews - - The following previews are now an official part of the API: - * The GitHub Apps API and endpoints that returned the `performed_via_github_app` property no longer require the [`machine-man`](https://developer.github.com/changes/2020-08-20-graduate-machine-man-and-sailor-v-previews/) preview header. {% comment %} https://github.com/github/releases/issues/965 {% endcomment %} - * To add and view a lock reason to an issue, you no longer need to use the [`sailor-v`](https://developer.github.com/changes/2020-08-20-graduate-machine-man-and-sailor-v-previews/) preview header. {% comment %} https://github.com/github/github/pull/143676 {% endcomment %} - - - | - #### GraphQL Schema Changes - - * [The GraphQL schema changes](https://docs.github.com/enterprise/2.22/user/graphql/overview/changelog) include backwards-compatible changes, schema previews, and upcoming breaking changes. - - - heading: VMware Network Driver Changes - notes: - - | - The GitHub Enterprise Server default network adapter type for VMware customers has been changed from E1000 to VMXNET3, starting with release 2.22.0. When upgrading from an earlier release to 2.22.0 or newer, if an E1000 network adapter is detected during the pre-upgrade check, the following message will be displayed at the command line: - - ``` - WARNING: Your virtual appliance is currently using an emulated Intel E1000 network adapter. - For optimal performance, please update the virtual machine configuration on your VMware host to use the VMXNET3 driver. - Proceed with installation? [y/N] - ``` - - The administrator can choose to update the network adapter type to VMXNET3 either before or after the GitHub Enterprise Server upgrade. The virtual appliance will need to be shutdown for this change. Customers should follow the VMware recommended steps for [changing the virtual machine network adapter configuration](https://docs.vmware.com/en/VMware-vSphere/7.0/com.vmware.vsphere.vm_admin.doc/GUID-3719A0BE-4B4A-44FF-8A21-290950918FBD.html) to VMXNET3. Please note that `VMXNET3` will not be an option if the OS version for the virtual appliance is set to `Other Linux (64-bit)`. In that case, the OS version would first need to be changed from `Other Linux (64-bit)` to `Other 2.6.x Linux (64-bit)` or if available, `Debian GNU/Linux 9` . We recommend testing these changes on a [staging instance](https://docs.github.com/en/enterprise-server@2.22/admin/installation/setting-up-a-staging-instance) before it is performed on a production GitHub Enterprise Server. {% comment %} https://github.com/github/ghes-infrastructure/issues/781 {% endcomment %} - - bugs: - - The stafftools page for viewing pending collaborator showed a `500 Internal Server Error` when there was a pending email invite. {% comment %} https://github.com/github/github/pull/150836 {% endcomment %} - - The Repository Health Check in stafftools could give incorrect results on busy repositories. {% comment %} https://github.com/github/github/pull/151160 {% endcomment %} - - A logged in user trying to accept an email invitation could get a `404 Not Found` error. {% comment %} https://github.com/github/github/pull/150848 {% endcomment %} - - If a user navigated to a repository whose name started with "repositories.", they were redirected to the owner's "Repositories" tab instead of landing on the repository overview page. {% comment %} https://github.com/github/github/pull/149704 {% endcomment %} - - Labels in the dashboard timeline did not have enough contrast. {% comment %} https://github.com/github/github/pull/146749 {% endcomment %} - - deprecations: - - heading: Upcoming Deprecation of GitHub Enterprise Server 2.19 - notes: - - '**GitHub Enterprise Server 2.19 will be 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 GitHub Enterprise 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 GitHub Enterprise Server 2.21.0 two legacy GitHub Apps-related webhook events have been deprecated and will be removed in GitHub Enterprise Server 2.25.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/). {% comment %} https://github.com/github/enterprise-web/pull/6419#issuecomment-668303461 {% endcomment %} - - heading: Deprecation of Legacy GitHub Apps Endpoint - notes: - - Starting with GitHub Enterprise Server 2.21.0 the legacy GitHub Apps endpoint for creating installation access tokens was deprecated and will be removed in GitHub Enterprise Server 2.25.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/). {% comment %} https://github.com/github/enterprise-web/pull/6419#issuecomment-668303461 {% endcomment %} - - 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 GitHub Enterprise Server 3.4. For more information, see the [deprecation announcement blog post](https://developer.github.com/changes/2020-02-14-deprecating-oauth-app-endpoint/). - - backups: - - GitHub Enterprise Server 2.22 requires at least [GitHub Enterprise Backup Utilities](https://github.com/github/backup-utils) 2.22.0 for [Backups and Disaster Recovery](https://help.github.com/enterprise/2.22/admin/guides/installation/backups-and-disaster-recovery/). - - known_issues: - - On a freshly set up GitHub Enterprise Server without any users, an attacker could create the first admin user. {% comment %} https://github.com/github/enterprise2/issues/1889 {% endcomment %} - - Custom firewall rules are not maintained during an upgrade. {% comment %} https://github.com/github/enterprise2/issues/2823 {% endcomment %} - - 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. {% comment %} https://github.com/github/github/issues/54684 {% endcomment %} - - 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. {% comment %} https://github.com/github/github/issues/107731 {% endcomment %} - - 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. {% comment %} https://github.com/github/admin-experience/issues/571 {% endcomment %} - - The Name ID Format dropdown in the Management Console resets to "unspecified" after setting instance to "persistent". {% comment %} https://github.com/github/enterprise2/issues/13446 {% endcomment %} - - The repository Settings page of a repository for a user or organization GitHub Pages sites will fail with a "500 Internal Server Error". {% comment %} https://github.com/github/github/issues/156183 {% endcomment %} - - Users may experience slower Git clone and fetch performance on an instance with high availability replicas due to reads being forwarded to a different node. {% comment %} https://github.com/github/spokesd/issues/746 {% endcomment %} - - '[Creating a GitHub App from a manifest](https://docs.github.com/en/enterprise/2.22/user/developers/apps/creating-a-github-app-from-a-manifest) fails. To work around this issue, users can follow the manual instructions for [creating a GitHub App](https://docs.github.com/en/enterprise/2.22/user/developers/apps/creating-a-github-app). {% comment %} https://github.com/github/enterprise2/issues/22849 {% endcomment %}' - - GitHub usernames may change unintentionally when using SAML authentication, if the GitHub username does not match the value of the attribute mapped to the `username` field in the Management Console. (updated 2020-10-08) {% comment %} https://github.com/github/external-identities/issues/335 {% endcomment %} - - On a freshly set up 2.22.0 instance or after upgrading to 2.22.0, the activity feed on an organization's dashboard will no longer update. (updated 2020-10-27) {% comment %}https://github.com/github/enterprise2/issues/23050{% endcomment %} - - Audit logs may be attributed to 127.0.0.1 instead of the actual source IP address. (updated 2020-11-02) {% comment %} https://github.com/github/enterprise2/issues/21514 {% endcomment %} - - 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. diff --git a/data/release-notes/enterprise-server/2-22/1.yml b/data/release-notes/enterprise-server/2-22/1.yml deleted file mode 100644 index 928b7fa41c..0000000000 --- a/data/release-notes/enterprise-server/2-22/1.yml +++ /dev/null @@ -1,74 +0,0 @@ -date: '2020-10-09' -sections: - security_fixes: - - '**MEDIUM**: ImageMagick has been updated to address [DSA-4715-1](https://www.debian.org/security/2020/dsa-4715). {% comment %} https://github.com/github/enterprise2/pull/22623, https://github.com/github/enterprise2/pull/22610 {% endcomment %}' - - 'Requests from a GitHub App integration to refresh an OAuth access token would be accepted if sent with a different, valid OAuth client ID and client secret than was used to create the refresh token. {% comment %} https://github.com/github/github/pull/154921, https://github.com/github/github/pull/154423, https://github.com/github/ecosystem-apps/issues/1066 {% endcomment %}' - - 'A user whose LDAP directory username standardizes to an existing GHES account login could authenticate into the existing account. {% comment %} https://github.com/github/github/pull/156513, https://github.com/github/github/pull/155512 {% endcomment %}' - - 'Packages have been updated to the latest security versions. {% comment %} https://github.com/github/enterprise2/pull/22912, https://github.com/github/enterprise2/pull/22878 {% endcomment %}' - - bugs: - - | - The NameID Format dropdown in the Management Console would be reset to "unspecified" after setting it to "persistent". {% comment %} https://github.com/github/enterprise2/pull/22376, https://github.com/github/enterprise2/pull/22331, https://github.com/github/enterprise2/issues/13446 {% endcomment %} - - | - Upgrading using a hotpatch could fail with an error: `'libdbi1' was not found` {% comment %} https://github.com/github/enterprise2/pull/22557, https://github.com/github/enterprise2/pull/22552 {% endcomment %} - - | - Saving settings via the [management console](/admin/configuration/accessing-the-management-console) would append a newline to the [TLS/SSL certificate and key](/admin/configuration/configuring-tls) files which triggered unnecessary reloading of some services. {% comment %} https://github.com/github/enterprise2/pull/22570, https://github.com/github/enterprise2/pull/22540 {% endcomment %} - - | - System logs for Dependency Graph were not rotating, allowing unbounded storage growth. {% comment %} https://github.com/github/enterprise2/pull/22767, https://github.com/github/enterprise2/pull/22733 {% endcomment %} - - | - The MS SQL Server performance graph showed statistics from the primary instance even when a replica was selected. {% comment %} https://github.com/github/enterprise2/pull/22778, https://github.com/github/enterprise2/pull/22750 {% endcomment %} - - | - `ghe-actions-precheck` would silently exit without running the storage checks if Actions was not enabled. {% comment %} https://github.com/github/enterprise2/pull/22787, https://github.com/github/enterprise2/pull/22742 {% endcomment %} - - | - Upgrade could fail if the resqued workers override setting is in use. {% comment %} https://github.com/github/enterprise2/pull/22836, https://github.com/github/enterprise2/pull/22814 {% endcomment %} - - | - Some services running in containers were not sending logs to the journal. {% comment %} https://github.com/github/enterprise2/pull/22994, https://github.com/github/enterprise2/pull/22518 {% endcomment %} - - | - Links to GitHub Security Advisories would use a URL with the hostname of the GitHub Enterprise Server instance instead of GitHub.com, directing the user to a nonexistent URL. {% comment %} https://github.com/github/github/pull/153316, https://github.com/github/github/pull/151301 {% endcomment %} - - | - When importing a repository with `ghe-migrator`, an unexpected exception could occur when inconsistent data is present. {% comment %} https://github.com/github/github/pull/153850, https://github.com/github/github/pull/151552 {% endcomment %} - - | - The enterprise account security settings page showed a "View your organizations' current configurations" link for the "Two-factor authentication" setting when the authentication mode in use does not support built in two-factor authentication. {% comment %} https://github.com/github/github/pull/153860 {% endcomment %} - - | - OAuth refresh tokens would be removed prematurely. {% comment %} https://github.com/github/github/pull/154271, https://github.com/github/github/pull/153694 {% endcomment %} - - | - Search repair tasks would generate exceptions during the migration phase of configuration. {% comment %} https://github.com/github/github/pull/154573, https://github.com/github/github/pull/153392 {% endcomment %} - - | - On the settings page for GitHub Apps, the "Beta Features" tab was not visible in some circumstances. {% comment %} https://github.com/github/github/pull/154612, https://github.com/github/github/pull/154417 {% endcomment %} - - | - When using `ghe-migrator` to import PR review requests, records associated with deleted users would result in extraneous database records. {% comment %} https://github.com/github/github/pull/154960, https://github.com/github/github/pull/153169 {% endcomment %} - - | - When importing users with `ghe-migrator`, an error of "Emails is invalid" would occur if the system-generated email address were longer than 100 characters. {% comment %} https://github.com/github/github/pull/155109, https://github.com/github/github/pull/152418 {% endcomment %} - - | - Logging webhook activity could use large amounts of disk space and cause the root disk to become full. {% comment %} https://github.com/github/github/pull/155657, https://github.com/github/github/pull/154100 {% endcomment %} - - | - Users experienced slower Git clone and fetch performance on an instance with high availability replicas due to reads being forwarded to a different node. {% comment %} https://github.com/github/github/pull/156195, https://github.com/github/github/pull/156016, https://github.com/github/spokesd/issues/746 {% endcomment %} - - | - The repository Settings page of a repository for a user or organization GitHub Pages sites would fail with a "500 Internal Server Error". {% comment %} https://github.com/github/github/pull/156439, https://github.com/github/github/issues/156183 {% endcomment %} - - | - Repository network maintenance operations could become stuck in a `running` state. {% comment %} https://github.com/github/github/pull/156669, https://github.com/github/github/pull/156036 {% endcomment %} - - | - A repository being deleted immediately after uploading a code scanning result could cause a stall in the processing of code scanning results for all repositories. {% comment %} https://github.com/github/github/pull/157063, https://github.com/github/github/pull/156437 {% endcomment %} - - | - When a large number of code scanning results were submitted at the same time, processing of batches could time out resulting in a stall in processing of code scanning results. {% comment %} https://github.com/github/github/pull/157065, https://github.com/github/github/pull/156462 {% endcomment %} - - | - [Creating a GitHub App from a manifest](https://docs.github.com/en/enterprise/2.22/user/developers/apps/creating-a-github-app-from-a-manifest) would fail. {% comment %} https://github.com/github/github/pull/157133, https://github.com/github/github/pull/156904, https://github.com/github/enterprise2/issues/22849 {% endcomment %} - - | - GitHub usernames were changed unintentionally when using SAML authentication, when the GitHub username did not match the value of the attribute mapped to the `username` field in the Management Console. {% comment %} https://github.com/github/github/pull/158131, https://github.com/github/github/pull/157936, https://github.com/github/external-identities/issues/335 {% endcomment %} - - changes: - - Support is added for the AWS EC2 instance type `m5.16xlarge`. {% comment %} https://github.com/github/enterprise2/pull/22502, https://github.com/github/enterprise2/pull/22473 {% endcomment %} - - Remove the requirement for SSH fingerprints in `ghe-migrator` archives as it can always be computed. {% comment %} https://github.com/github/github/pull/156946, https://github.com/github/github/pull/155387 {% endcomment %} - - GitHub App Manifests now include the `request_oauth_on_install` field. {% comment %} https://github.com/github/github/pull/156991, https://github.com/github/github/pull/155010, https://github.com/github/ecosystem-apps/issues/1055 {% endcomment %} - - known_issues: - - On a freshly set up GitHub Enterprise Server without any users, an attacker could create the first admin user. {% comment %} https://github.com/github/enterprise2/issues/1889 {% endcomment %} - - Custom firewall rules are not maintained during an upgrade. {% comment %} https://github.com/github/enterprise2/issues/2823 {% endcomment %} - - 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. {% comment %} https://github.com/github/github/issues/54684 {% endcomment %} - - 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. {% comment %} https://github.com/github/github/issues/107731 {% endcomment %} - - 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. {% comment %} https://github.com/github/admin-experience/issues/571 {% endcomment %} - - Configuration updates will fail when restoring data to a GitHub Actions-enabled instance if the original backup source did not have the feature enabled. {% comment %} https://github.com/github/c2c-actions-runtime/issues/915 {% endcomment %} - - GitHub Actions can fail to start up successfully if it was previously enabled on an instance running 2.22.0 and is upgraded to 2.22.1. (updated 2020-10-23) {% comment %} https://github.com/github/c2c-actions/issues/1680 {% endcomment %} - - On a freshly set up 2.22.1 instance or after upgrading to 2.22.1, the activity feed on an organization's dashboard will no longer update. (updated 2020-10-27) {% comment %}https://github.com/github/enterprise2/issues/23050{% endcomment %} - - Audit logs may be attributed to 127.0.0.1 instead of the actual source IP address. (updated 2020-11-02) {% comment %} https://github.com/github/enterprise2/issues/21514 {% endcomment %} - - 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. diff --git a/data/release-notes/enterprise-server/2-22/10.yml b/data/release-notes/enterprise-server/2-22/10.yml deleted file mode 100644 index 4f40bbb01a..0000000000 --- a/data/release-notes/enterprise-server/2-22/10.yml +++ /dev/null @@ -1,16 +0,0 @@ -date: '2021-04-01' -sections: - security_fixes: - - "**HIGH:** An improper access control vulnerability was identified in GitHub Enterprise Server that allowed access tokens generated from a GitHub App's [web authentication flow](https://docs.github.com/en/developers/apps/identifying-and-authorizing-users-for-github-apps#web-application-flow) to read private repository metadata via the REST API without having been granted the appropriate permissions. To exploit this vulnerability, an attacker would need to create a GitHub App on the instance and have a user authorize the application through the web authentication flow. The private repository metadata returned would be limited to repositories owned by the user the token identifies. This vulnerability affected all versions of GitHub Enterprise Server prior to 3.0.4 and was fixed in versions 3.0.4, 2.22.10, 2.21.18. This vulnerability has been assigned CVE-2021-22865 and was reported via the [GitHub Bug Bounty Program](https://bounty.github.com)." - - Packages have been updated to the latest security versions. - bugs: - - A timezone set on GitHub Enterprise 11.10.x or earlier was not being used by some services which were defaulting to UTC time. - - Services were not transitioning to new log files as part of log rotation, resulting in increased disk usage. - - The label on search results for internal repositories was shown as "Private" instead of "Internal". - known_issues: - - On a freshly set up GitHub Enterprise 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. - - 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. diff --git a/data/release-notes/enterprise-server/2-22/11.yml b/data/release-notes/enterprise-server/2-22/11.yml deleted file mode 100644 index 65ea42d038..0000000000 --- a/data/release-notes/enterprise-server/2-22/11.yml +++ /dev/null @@ -1,19 +0,0 @@ -date: '2021-04-14' -sections: - security_fixes: - - Packages have been updated to the latest security versions. - bugs: - - 'A warning message `jq: error (at :0): Cannot index number with string "settings"` could occur during replica promotion.' - - Continuously restoring backups to a cluster could fail due to MySQL replicas failing to connect to the primary. - - Syntax highlighting could fail due to the Treelights container running out of memory. - - Visiting the `/settings/emails` page would store state that could cause improper redirects when logging out and logging back in. - - Dependency graph alerts weren't shown for some components whose advisories have upper case package names in `vulnerable_version_ranges`. - - GitHub integration apps were not able to notify teams when mentioned directly via an at-mention in an issue comment. - - When ghe-migrator encountered import errors, it would sometimes abort the entire process, and the logs did not include enough context. - known_issues: - - On a freshly set up GitHub Enterprise 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. - - 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. diff --git a/data/release-notes/enterprise-server/2-22/12.yml b/data/release-notes/enterprise-server/2-22/12.yml deleted file mode 100644 index 14248f149c..0000000000 --- a/data/release-notes/enterprise-server/2-22/12.yml +++ /dev/null @@ -1,22 +0,0 @@ -date: '2021-04-28' -sections: - security_fixes: - - Packages have been updated to the latest security versions. - bugs: - - During upgrades, the process would pause indefinitely after `cleanup nomad job`. - - 'Failing `ghe-cluster-failover` with the error message `Trilogy::Error: trilogy_connect`.' - - '`ghe-cluster-status-mysql` showed warnings about failovers as errors.' - - Setup script running on MySQL replication may have caused unnecessary database reseeding during database failover. - - '`config-apply` could take longer than necessary due to `rake db:migrate` being called unnecessarily.' - - Orchestrator could have failed over to a MySQL replica which was not replicating from primary during seeding phase when primary could not be connected. - - Organizations or projects with errors blocked migration and could not be excluded. - - Customers with more than three storage hosts were unable to restore to their disaster-recovery cluster due to the fullest disks being selected instead of empty nodes. - changes: - - Preflight checks allow all AWS instance types by default. - known_issues: - - On a freshly set up GitHub Enterprise 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. - - 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. diff --git a/data/release-notes/enterprise-server/2-22/13.yml b/data/release-notes/enterprise-server/2-22/13.yml deleted file mode 100644 index 027fc8ba41..0000000000 --- a/data/release-notes/enterprise-server/2-22/13.yml +++ /dev/null @@ -1,20 +0,0 @@ -date: '2021-05-13' -sections: - security_fixes: - - "**HIGH:** A UI misrepresentation vulnerability was identified in GitHub Enterprise Server that allowed more permissions to be granted during a GitHub App's user-authorization web flow than was displayed to the user during approval. To exploit this vulnerability, an attacker would need to create a GitHub App on the instance and have a user authorize the application through the web authentication flow. All permissions being granted would properly be shown during the first authorization, but in certain circumstances, if the user revisits the authorization flow after the GitHub App has configured additional user-level permissions, those additional permissions may not be shown, leading to more permissions being granted than the user potentially intended. This vulnerability affected GitHub Enterprise Server 3.0.x prior to 3.0.7 and 2.22.x prior to 2.22.13. It was fixed in versions 3.0.7 and 2.22.13. This vulnerability has been assigned CVE-2021-22866 and was reported via the [GitHub Bug Bounty Program](https://bounty.github.com/)." - - Packages have been updated to the latest security versions. - bugs: - - Orchestrator auto failover could be enabled during the phase of config apply. - - Users with maintainer permissions to a repository were shown an e-mail verification warning instead of a successful page build on the repository Pages settings page. - - The code owner of a wildcard rule would be incorrectly added to the list of owners for the code owners badge even if a later rule took precedence for that path. - - OpenAPI documentation referred to an invalid header. - changes: - - Added logging for config change on HAProxy reload. - - Added logging for repository creation. - known_issues: - - On a freshly set up GitHub Enterprise 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. - - 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. diff --git a/data/release-notes/enterprise-server/2-22/14.yml b/data/release-notes/enterprise-server/2-22/14.yml deleted file mode 100644 index 025475faf0..0000000000 --- a/data/release-notes/enterprise-server/2-22/14.yml +++ /dev/null @@ -1,18 +0,0 @@ -date: '2021-05-25' -sections: - 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: - - Normal replication delays in MSSQL generated warnings. - - An IP address added by an admin using the "Create Whitelist Entry" button could still be locked out. - - '`spokesd` created excessive log entries including the phrase "fixing placement skipped".' - changes: - - Check annotations older than 4 months will be archived. - known_issues: - - On a freshly set up GitHub Enterprise 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. - - 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. diff --git a/data/release-notes/enterprise-server/2-22/15.yml b/data/release-notes/enterprise-server/2-22/15.yml deleted file mode 100644 index ea41c4c259..0000000000 --- a/data/release-notes/enterprise-server/2-22/15.yml +++ /dev/null @@ -1,16 +0,0 @@ -date: '2021-06-10' -sections: - security_fixes: - - Packages have been updated to the latest security versions. - bugs: - - Import failures of organizations or repositories from non-GitHub sources could produce an `undefined method '[]' for nil:NilClass` error. - - GitHub profile names might have changed unintentionally when using SAML authentication, if the GitHub profile name did not match the value of the attribute mapped to the `Full name` field in the Management Console. - changes: - - Users of the GraphQL API can query the public field `closingIssuesReferences` on the `PullRequest` object. This field retrieves issues that will be automatically closed when the related pull request is merged. This approach will also allow this data to be migrated in future, as part of a higher fidelity migration process. - known_issues: - - On a freshly set up GitHub Enterprise 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. - - 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. diff --git a/data/release-notes/enterprise-server/2-22/16.yml b/data/release-notes/enterprise-server/2-22/16.yml deleted file mode 100644 index d38c2f24b2..0000000000 --- a/data/release-notes/enterprise-server/2-22/16.yml +++ /dev/null @@ -1,15 +0,0 @@ -date: '2021-06-24' -sections: - security_fixes: - - Packages have been updated to the latest security versions. - bugs: - - The sshd service would sometimes fail to start on instances running on Google Cloud Platform. - - Old upgrade files would persist on the user disk, sometimes resulting in out of space conditions. - - An export archive would silently fail to import pull requests if they contained review requests from teams not present in the archive. - known_issues: - - On a freshly set up GitHub Enterprise 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. - - 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. diff --git a/data/release-notes/enterprise-server/2-22/17.yml b/data/release-notes/enterprise-server/2-22/17.yml deleted file mode 100644 index 7f9b37ef4b..0000000000 --- a/data/release-notes/enterprise-server/2-22/17.yml +++ /dev/null @@ -1,20 +0,0 @@ -date: '2021-07-14' -sections: - security_fixes: - - '**HIGH:** A path traversal vulnerability was identified in GitHub Enterprise Server that could be exploited when building a GitHub Pages site. User-controlled configuration options used by GitHub Pages were not sufficiently restricted and made it possible to read files on the GitHub Enterprise Server instance. To exploit this vulnerability, an attacker would need permission to create and build a GitHub Pages site on the GitHub Enterprise Server instance. This vulnerability affected all versions of GitHub Enterprise Server prior to 3.1.3 and has been assigned CVE-2021-22867. This vulnerability was reported via the GitHub Bug Bounty program.' - - Packages have been updated to the latest security versions. - bugs: - - '`ghe-cluster-config-node-init` would fail during cluster setup if HTTP proxy is enabled.' - - Collectd would not resolve the forwarding destination hostname after the initial startup. - - The job that purged stale deleted repositories could fail to make progress if some of those repositories were protected from deletion by legal holds. - - Git pushes could result in a 500 Internal Server Error during the user reconciliation process on instances using LDAP authentication mode. - - A significant number of 503 errors were logged every time a user visited a repository's `/settings` page if the dependency graph was not enabled. - changes: - - Improved the efficiency of config apply by skipping IP allow firewall rules that had not changed, which saved significant time on large clusters. - known_issues: - - On a freshly set up GitHub Enterprise 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. - - 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. diff --git a/data/release-notes/enterprise-server/2-22/18.yml b/data/release-notes/enterprise-server/2-22/18.yml deleted file mode 100644 index 640a2252d5..0000000000 --- a/data/release-notes/enterprise-server/2-22/18.yml +++ /dev/null @@ -1,16 +0,0 @@ -date: '2021-07-27' -sections: - security_fixes: - - Packages have been updated to the latest security versions. - bugs: - - A significant number of 503 errors were being created if the scheduled job to sync vulnerabilities with GitHub.com attempted to run when dependency graph was not enabled and content analysis was enabled. - - Unauthenticated HTTP proxy for the pages containers build was not supported for any users that use HTTP proxies. - changes: - - The logs for `babeld` now include a `cmd` field for HTTP ref advertisement requests instead of only including it during the negotiation requests. - 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. - - 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. diff --git a/data/release-notes/enterprise-server/2-22/19.yml b/data/release-notes/enterprise-server/2-22/19.yml deleted file mode 100644 index 85159a0056..0000000000 --- a/data/release-notes/enterprise-server/2-22/19.yml +++ /dev/null @@ -1,13 +0,0 @@ -date: '2021-08-10' -sections: - bugs: - - Audit log entries for changes made to "Repository creation" organization settings were inaccurate. - changes: - - Abuse rate limits are now called Secondary rate limits, since the behavior they limit is not always abusive. - 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. - - 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. diff --git a/data/release-notes/enterprise-server/2-22/2.yml b/data/release-notes/enterprise-server/2-22/2.yml deleted file mode 100644 index 42e92d228d..0000000000 --- a/data/release-notes/enterprise-server/2-22/2.yml +++ /dev/null @@ -1,31 +0,0 @@ -date: '2020-10-20' -sections: - security_fixes: - - Packages have been updated to the latest security versions. {% comment %} https://github.com/github/enterprise2/pull/23097, https://github.com/github/enterprise2/pull/23081 {% endcomment %} - - bugs: - - | - If the storage account settings failed to validate while configuring GitHub Actions, running `ghe-actions-teardown` was required before making a new attempt. {% comment %} https://github.com/github/enterprise2/pull/23057, https://github.com/github/enterprise2/pull/22981 {% endcomment %} - - | - A custom proxy configuration could adversely affect the GitHub Actions environment. {% comment %} https://github.com/github/enterprise2/pull/23121, https://github.com/github/enterprise2/pull/23092, https://github.com/github/c2c-actions-platform/issues/2254 {% endcomment %} - - | - On a change of an address on eth0, Nomad and Consul could get unresponsive. {% comment %} https://github.com/github/enterprise2/pull/23227, https://github.com/github/enterprise2/pull/23153 {% endcomment %} - - | - When using self-signed certificates, GHES could have SSL validation exceptions upon configuring GitHub Actions. {% comment %} https://github.com/github/enterprise2/pull/23381 {% endcomment %} - - | - Using a GitHub Action from a branch name with a `+` or `/` character resulted in an error: `Unable to resolve action`. {% comment %} https://github.com/github/github/pull/157942, https://github.com/github/github/pull/157819, https://github.com/github/launch/pull/3463 {% endcomment %} - - | - The enterprise account "Confirm two-factor requirement policy" messaging was incorrect. {% comment %} https://github.com/github/github/pull/158735 {% endcomment %} - - | - On certain requests above 100MB, Kafka's buffer could be over-allocated. {% comment %} https://github.com/github/kafka-lite/pull/286, https://github.com/github/kafka-lite/pull/285 {% endcomment %} - - known_issues: - - On a freshly set up GitHub Enterprise Server without any users, an attacker could create the first admin user. {% comment %} https://github.com/github/enterprise2/issues/1889 {% endcomment %} - - Custom firewall rules are not maintained during an upgrade. {% comment %} https://github.com/github/enterprise2/issues/2823 {% endcomment %} - - 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. {% comment %} https://github.com/github/github/issues/54684 {% endcomment %} - - 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. {% comment %} https://github.com/github/github/issues/107731 {% endcomment %} - - 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. {% comment %} https://github.com/github/admin-experience/issues/571 {% endcomment %} - - GitHub Actions can fail to start up successfully if it was previously enabled on an instance running 2.22.0 and is upgraded to 2.22.2. (updated 2020-10-23) {% comment %} https://github.com/github/c2c-actions/issues/1680 {% endcomment %} - - On a freshly set up 2.22.2 instance or after upgrading to 2.22.2, the activity feed on an organization's dashboard will no longer update. (updated 2020-10-27) {% comment %}https://github.com/github/enterprise2/issues/23050{% endcomment %} - - Audit logs may be attributed to 127.0.0.1 instead of the actual source IP address. (updated 2020-11-02) {% comment %} https://github.com/github/enterprise2/issues/21514 {% endcomment %} - - 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. diff --git a/data/release-notes/enterprise-server/2-22/20.yml b/data/release-notes/enterprise-server/2-22/20.yml deleted file mode 100644 index e400819ffa..0000000000 --- a/data/release-notes/enterprise-server/2-22/20.yml +++ /dev/null @@ -1,14 +0,0 @@ -date: '2021-08-24' -sections: - security_fixes: - - Packages have been updated to the latest security versions. - bugs: - - Journald messages related to automatic updates (`Adding h/m/s random time.`) were logged to syslog. - - Git hooks to the internal API that result in failing requests returned the exception `undefined method body for "success":String (NoMethodError)` instead of returning an explicit `nil`. - 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. - - 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. diff --git a/data/release-notes/enterprise-server/2-22/21.yml b/data/release-notes/enterprise-server/2-22/21.yml deleted file mode 100644 index 08b210ba47..0000000000 --- a/data/release-notes/enterprise-server/2-22/21.yml +++ /dev/null @@ -1,11 +0,0 @@ -date: '2021-09-07' -sections: - security_fixes: - - Packages have been updated to the latest security versions. - 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. - - 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. diff --git a/data/release-notes/enterprise-server/2-22/22.yml b/data/release-notes/enterprise-server/2-22/22.yml deleted file mode 100644 index 8132ad054a..0000000000 --- a/data/release-notes/enterprise-server/2-22/22.yml +++ /dev/null @@ -1,14 +0,0 @@ -date: '2021-09-24' -sections: - security_fixes: - - '**HIGH:** A path traversal vulnerability was identified in {% data variables.product.prodname_ghe_server %} that could be exploited when building a {% data variables.product.prodname_pages %} site. User-controlled configuration options used by {% data variables.product.prodname_pages %} were not sufficiently restricted and made it possible to read files on the {% data variables.product.prodname_ghe_server %} instance. To exploit this vulnerability, an attacker would need permission to create and build a {% data variables.product.prodname_pages %} site on the {% data variables.product.prodname_ghe_server %} instance. This vulnerability affected all versions of {% data variables.product.prodname_ghe_server %} prior to 3.1.8 and was fixed in 3.1.8, 3.0.16, and 2.22.22. This is the result of an incomplete fix for CVE-2021-22867. This vulnerability was reported via the GitHub Bug Bounty program and has been assigned CVE-2021-22868. {% comment %} https://github.com/github/pages/pull/3359, https://github.com/github/pages/pull/3357 {% endcomment %}' - bugs: - - 'The {% data variables.product.prodname_github_connect %} configuration of the source instance was always restored to new instances even when the `--config` option for `ghe-restore` was not used. This would lead to a conflict with the {% data variables.product.prodname_github_connect %} connection and license synchronization if both the source and destination instances were online at the same time. {% comment %} https://github.com/github/github/pull/192247, https://github.com/github/github/pull/191951, https://github.com/github/enterprise2/pull/26870, https://github.com/github/backup-utils/pull/770, https://github.com/github/connected-enterprise/issues/208 {% endcomment %}' - - 'Fixes {% data variables.product.prodname_pages %} builds so they take into account the NO_PROXY setting of the appliance. This is relevant to appliances configured with an HTTP proxy only. {% comment %} https://github.com/github/github/pull/192380 {% endcomment %}' - 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 {% data variables.product.prodname_github_connect %}, issues in private and internal repositories are not included in GitHub.com search results. - - 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. diff --git a/data/release-notes/enterprise-server/2-22/3.yml b/data/release-notes/enterprise-server/2-22/3.yml deleted file mode 100644 index 83b8ebfa6a..0000000000 --- a/data/release-notes/enterprise-server/2-22/3.yml +++ /dev/null @@ -1,25 +0,0 @@ -date: '2020-11-03' -sections: - security_fixes: - - | - **LOW:** High CPU usage could be triggered by a specially crafted request to the SVN bridge resulting in Denial of Service (DoS) on the SVN bridge service. (updated 2020-11-16) {% comment %} https://github.com/github/slumlord/pull/1005, https://github.com/github/slumlord/pull/1000 {% endcomment %} - - | - **LOW:** Incorrect token validation resulted in a reduced entropy for matching tokens during authentication. Analysis shows that in practice there's no significant security risk here. {% comment %} https://github.com/github/github/pull/159457, https://github.com/github/github/pull/159193 {% endcomment %} - - | - Packages have been updated to the latest security versions. {% comment %} https://github.com/github/enterprise2/pull/23540, https://github.com/github/enterprise2/pull/23171, https://github.com/github/enterprise2/pull/23693, https://github.com/github/enterprise2/pull/23677 {% endcomment %} - - bugs: - - GitHub Actions could fail to start up successfully if it was previously enabled on an instance running 2.22.0 and was upgraded to 2.22.1 or 2.22.2. {% comment %} https://github.com/github/enterprise2/pull/23622, https://github.com/github/enterprise2/pull/23490, https://github.com/github/c2c-actions/issues/1680 {% endcomment %} - - Configuration files for GitHub Actions were not copied to the replica when setting up high availability replicas potentially leading to errors during `ghe-repl-promote`. {% comment %} https://github.com/github/enterprise2/pull/23703, https://github.com/github/enterprise2/pull/23683 {% endcomment %} - - On a freshly set up 2.22.1 or 2.22.2 instance or after upgrading to 2.22.1 or 2.22.2, the activity feed on an organization's dashboard would not update. {% comment %} https://github.com/github/github/pull/159376, https://github.com/github/github/pull/159235, https://github.com/github/enterprise2/issues/23050 {% endcomment %} - - Editing issues templates with filenames containing non-ASCII characters would fail with a "500 Internal Server Error". {% comment %} https://github.com/github/github/pull/160588, https://github.com/github/github/pull/159747 {% endcomment %} - - A metric gathering method for background jobs increased CPU utilization. (updated 2020-11-03) {% comment %} https://github.com/github/github/pull/160109 {% endcomment %} - - known_issues: - - On a freshly set up GitHub Enterprise Server without any users, an attacker could create the first admin user. {% comment %} https://github.com/github/enterprise2/issues/1889 {% endcomment %} - - Custom firewall rules are not maintained during an upgrade. {% comment %} https://github.com/github/enterprise2/issues/2823 {% endcomment %} - - 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. {% comment %} https://github.com/github/github/issues/54684 {% endcomment %} - - 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. {% comment %} https://github.com/github/github/issues/107731 {% endcomment %} - - 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. {% comment %} https://github.com/github/admin-experience/issues/571 {% endcomment %} - - Audit logs may be attributed to 127.0.0.1 instead of the actual source IP address. {% comment %} https://github.com/github/enterprise2/issues/21514 {% endcomment %} - - 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. diff --git a/data/release-notes/enterprise-server/2-22/4.yml b/data/release-notes/enterprise-server/2-22/4.yml deleted file mode 100644 index cccadef9a1..0000000000 --- a/data/release-notes/enterprise-server/2-22/4.yml +++ /dev/null @@ -1,18 +0,0 @@ -date: '2020-11-17' -sections: - security_fixes: - - Packages have been updated to the latest security versions. {% comment %} https://github.com/github/enterprise2/pull/23845, https://github.com/github/enterprise2/pull/23712 {% endcomment %} - - bugs: - - The babeld logs were missing a separator between seconds and microseconds. {% comment %} https://github.com/github/babeld/pull/1006, https://github.com/github/babeld/pull/1002 {% endcomment %} - - After upgrading GHES with a hotpatch, the `ghe-actions-precheck` and `ghe-packages-precheck` commands would fail with the error `"docker load" accepts no arguments`. {% comment %} https://github.com/github/enterprise2/pull/23760, https://github.com/github/enterprise2/pull/23745 {% endcomment %} - - When the enterprise account "Repository visibility change" policy was set to "Enabled", organization owners could not change the visibility of repositories within the organization. {% comment %} https://github.com/github/github/pull/160920, https://github.com/github/github/pull/160773 {% endcomment %} - - Audit logs could be attributed to 127.0.0.1 instead of the actual source IP address. {% comment %} https://github.com/github/github/pull/162438, https://github.com/github/github/pull/161215 {% endcomment %} - - known_issues: - - On a freshly set up GitHub Enterprise Server without any users, an attacker could create the first admin user. {% comment %} https://github.com/github/enterprise2/issues/1889 {% endcomment %} - - Custom firewall rules are not maintained during an upgrade. {% comment %} https://github.com/github/enterprise2/issues/2823 {% endcomment %} - - 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. {% comment %} https://github.com/github/github/issues/54684 {% endcomment %} - - 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. {% comment %} https://github.com/github/github/issues/107731 {% endcomment %} - - 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. {% comment %} https://github.com/github/admin-experience/issues/571 {% endcomment %} - - 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. diff --git a/data/release-notes/enterprise-server/2-22/5.yml b/data/release-notes/enterprise-server/2-22/5.yml deleted file mode 100644 index c5de818bb8..0000000000 --- a/data/release-notes/enterprise-server/2-22/5.yml +++ /dev/null @@ -1,22 +0,0 @@ -date: '2020-12-03' -sections: - bugs: - - 'Authorization service was being detected as unhealthy due to a race condition in the bootstrap which led to restart of the service. {% comment %} https://github.com/github/authzd/pull/1275, https://github.com/github/authzd/pull/1274 {% endcomment %}' - - 'The Elasticsearch upgrade process was not getting captured by ghe-diagnostics. {% comment %} https://github.com/github/enterprise2/pull/23905, https://github.com/github/enterprise2/pull/23874 {% endcomment %}' - - 'Enabling GitHub Actions on an upgraded high availability configuration caused errors in replication. {% comment %} https://github.com/github/enterprise2/pull/23979, https://github.com/github/c2c-actions-platform/issues/2479 {% endcomment %}' - - 'An underlying behavior was causing a service to become unavailable during the hotpatch upgrade process. {% comment %} https://github.com/github/enterprise2/pull/24055 {% endcomment %}' - - 'Users connecting to an active replica would get an error connecting to the live updates websocket. {% comment %} https://github.com/github/enterprise2/pull/24079, https://github.com/github/enterprise2/pull/24058 {% endcomment %}' - - 'A subset of log forwarding SSL certificates was not being applied correctly. {% comment %} https://github.com/github/enterprise2/pull/24114, https://github.com/github/enterprise2/pull/23981 {% endcomment %}' - - 'Email notifications sent to suspended users when they were removed from a Team or an Organization. {% comment %} https://github.com/github/github/pull/162973, https://github.com/github/github/pull/162742 {% endcomment %}' - - 'The way SSH certificates were applied between Organizations and Businesses was inconsistent. {% comment %} https://github.com/github/github/pull/163423, https://github.com/github/github/pull/159538, https://github.com/github/authentication/issues/115 {% endcomment %}' - - 'When an account was rate limited due to using incorrect passwords, it could be locked out for up to 24 hours. {% comment %} https://github.com/github/github/pull/163433, https://github.com/github/github/pull/162938, https://github.com/github/github-ds/pull/51 {% endcomment %}' - - 'Pull request synchronization on repositories with many references could cause worker queues to fall behind. {% comment %} https://github.com/github/github/pull/163573, https://github.com/github/github/pull/163142 {% endcomment %}' - - 'When signing in with a local username and password (built-in authentication) after attempting to visit a specific page, the user was sent to the home page instead of their intended destination. {% comment %} https://github.com/github/github/pull/163782, https://github.com/github/github/pull/163579, https://github.com/github/github/pull/154117, https://github.com/github/ecosystem-apps/issues/1076 {% endcomment %}' - - 'For GHES instances using built-in authentication with an internal SAML identity provider, users without an associated email address could not create a commit from the web interface. {% comment %} https://github.com/github/github/pull/164009, https://github.com/github/github/pull/163530, https://github.com/github/github/issues/163524 {% endcomment %}' - known_issues: - - 'On a freshly set up GitHub Enterprise Server without any users, an attacker could create the first admin user. {% comment %} https://github.com/github/enterprise2/issues/1889 {% endcomment %}' - - 'Custom firewall rules are not maintained during an upgrade. {% comment %} https://github.com/github/enterprise2/issues/2823 {% endcomment %}' - - '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. {% comment %} https://github.com/github/github/issues/54684 {% endcomment %}' - - '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. {% comment %} https://github.com/github/github/issues/107731 {% endcomment %}' - - '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. {% comment %} https://github.com/github/admin-experience/issues/571 {% endcomment %}' - - '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.' diff --git a/data/release-notes/enterprise-server/2-22/6.yml b/data/release-notes/enterprise-server/2-22/6.yml deleted file mode 100644 index bcf822612e..0000000000 --- a/data/release-notes/enterprise-server/2-22/6.yml +++ /dev/null @@ -1,18 +0,0 @@ -date: '2020-12-17' -sections: - security_fixes: - - '**LOW:** High CPU usage could be triggered by a specially crafted request to the SVN bridge resulting in Denial of Service (DoS). {% comment %} https://github.com/github/slumlord/pull/1022, https://github.com/github/slumlord/pull/1017 {% endcomment %}' - - 'Packages have been updated to the latest security versions. {% comment %} https://github.com/github/enterprise2/pull/24353, https://github.com/github/enterprise2/pull/23866 {% endcomment %}' - bugs: - - 'Requests for some file resources like a zip archive or raw file could enter a redirection loop. {% comment %} https://github.com/github/enterprise2/pull/24193, https://github.com/github/enterprise2/pull/24075 {% endcomment %}' - - 'A timeout could prevent some Issues and Pull Requests searches from providing complete search results. {% comment %} https://github.com/github/github/pull/164155, https://github.com/github/github/pull/163845 {% endcomment %}' - - 'Custom tabs with non-alphabetic characters in small screens did not render correctly. {% comment %} https://github.com/github/github/pull/164310, https://github.com/github/github/pull/164159 {% endcomment %}' - - 'An underlying behavior was causing failures when pushing content to a Git LFS-enabled repository. {% comment %} https://github.com/github/github/pull/164663, https://github.com/github/github/pull/150179 {% endcomment %}' - - 'In some rare cases issues could cause a 500 error when accessed via the web interface. {% comment %} https://github.com/github/github/pull/165298, https://github.com/github/github/pull/159674 {% endcomment %}' - known_issues: - - 'On a freshly set up GitHub Enterprise Server without any users, an attacker could create the first admin user. {% comment %} https://github.com/github/enterprise2/issues/1889 {% endcomment %}' - - 'Custom firewall rules are not maintained during an upgrade. {% comment %} https://github.com/github/enterprise2/issues/2823 {% endcomment %}' - - '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. {% comment %} https://github.com/github/github/issues/54684 {% endcomment %}' - - '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. {% comment %} https://github.com/github/github/issues/107731 {% endcomment %}' - - '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. {% comment %} https://github.com/github/admin-experience/issues/571 {% endcomment %}' - - '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.' diff --git a/data/release-notes/enterprise-server/2-22/7.yml b/data/release-notes/enterprise-server/2-22/7.yml deleted file mode 100644 index 094ce031ed..0000000000 --- a/data/release-notes/enterprise-server/2-22/7.yml +++ /dev/null @@ -1,57 +0,0 @@ -date: '2021-03-02' -sections: - security_fixes: - - '**HIGH:** An improper access control vulnerability was identified in GitHub Enterprise Server that allowed authenticated users of the instance to gain write access to unauthorized repositories via specifically crafted pull requests and REST API requests. An attacker would need to be able to fork the targeted repository, a setting that is disabled by default for organization owned private repositories. Branch protections such as required pull request reviews or status checks would prevent unauthorized commits from being merged without further review or validation. This vulnerability has been assigned CVE-2021-22861. This issue was reported via the [GitHub Bug Bounty Program](https://bounty.github.com).' - - '**HIGH:** An improper access control vulnerability was identified in the GitHub Enterprise Server GraphQL API that allowed authenticated users of the instance to modify the maintainer collaboration permission of a pull request without proper authorization. By exploiting this vulnerability, an attacker would be able to gain access to head branches of pull requests opened on repositories of which they are a maintainer. Forking is disabled by default for organization owned private repositories and would prevent this vulnerability. Additionally, branch protections such as required pull request reviews or status checks would prevent unauthorized commits from being merged without further review or validation. This vulnerability has been assigned CVE-2021-22863. This issue was reported via the [GitHub Bug Bounty Program](https://bounty.github.com).' - - '**HIGH:** A remote code execution vulnerability was identified in GitHub Enterprise Server that could be exploited when building a GitHub Pages site. User-controlled configuration of the underlying parsers used by GitHub Pages were not sufficiently restricted and made it possible to execute commands on the GitHub Enterprise Server instance. To exploit this vulnerability, an attacker would need permission to create and build a GitHub Pages site on the GitHub Enterprise Server instance. This vulnerability has been assigned CVE-2020-10519 and was reported via the [GitHub Bug Bounty Program](https://bounty.github.com).' - - '**MEDIUM:** GitHub Tokens from GitHub Pages builds could end up in logs.' - - '**LOW:** A specially crafted request to the SVN bridge could trigger a long wait before failure resulting in Denial of Service (DoS).' - - 'Packages have been updated to the latest security versions.' - bugs: - - 'The load-balancer health checks in some cases could cause the babeld logs to fill up with errors about the PROXY protocol.' - - 'An informational message was unintentionally logged as an error during GitHub Enterprise Backup Utilities snapshots, which resulted in unnecessary emails being sent when backups were scheduled by cron jobs that listen for output to stderr.' - - 'While restoring a large backup, exception logging related to Redis memory exhaustion could cause the restore to fail due to a full disk.' - - 'When first setting up a new instance, if you selected "Configure as Replica" you would be unable to start replication.' - - 'When GitHub Actions was enabled, disabling maintenance mode in the management console failed.' - - 'When editing a wiki page a user could experience a 500 error when clicking the Save button.' - - 'An S/MIME signed commit using a certificate with multiple names in the subject alternative name would incorrectly show as "Unverified" in the commit badge.' - - 'Suspended user was sent emails when added to a team.' - - 'User saw 500 error when executing git operations on an instance configured with LDAP authentication.' - - 'The `remove_org_member_package_access` background job was visible in the management console and would continually increase.' - - 'When a repository had a large number of manifests an error `You have reached the maximum number of allowed manifest files (20) for this repository.` was shown on the Insights -> Dependency graph tab. For more information, see [Visualization limits](https://docs.github.com/en/github/managing-security-vulnerabilities/troubleshooting-the-detection-of-vulnerable-dependencies#are-there-limits-which-affect-the-dependency-graph-data).' - - 'When uploading a new license file with a different number of seats from the previous license file, the seat difference was not correctly represented in the enterprise account Settings -> License page.' - - 'The "Prevent repository admins from changing anonymous Git read access" checkbox available in the enterprise account settings could not be successfully enabled or disabled.' - - 'When a GitHub Pages build failed, the email notification contained an incorrect link for support location.' - - 'During a leap year, the user was getting a 404 response when trying to view Contribution activity on a Monday.' - changes: - - 'Added support for [AWS EC2 r5b instance types](https://aws.amazon.com/about-aws/whats-new/2020/12/introducing-new-amazon-ec2-r5b-instances-featuring-60-gbps-of-ebs-bandwidth-and-260K-iops/).' - - 'Adjusted background queue prioritization to more evenly distribute jobs.' - known_issues: - - 'On a freshly set up GitHub Enterprise 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.' - - | - Users may experience assets such as avatars not loading, or a failure to push/pull code. This may be caused by a PID mismatch in the `haproxy-cluster-proxy` service. To determine if you have an affected instance: - - **Single instance** - - 1. Run this in the [administrative shell](https://docs.github.com/en/enterprise-server/admin/configuration/accessing-the-administrative-shell-ssh) (SSH): - - ``` - if [ $(cat /var/run/haproxy-cluster-proxy.pid) -ne $(systemctl show --property MainPID --value haproxy-cluster-proxy) ]; then echo 'Main PID of haproxy-cluster-proxy does not match /var/run/haproxy-cluster-proxy.pid'; fi - ``` - - 2. If it shows that there is a mismatch, reboot the instance. - - **Cluster or High Availability configuration** - - 1. Run this in the [administrative shell](https://docs.github.com/en/enterprise-server/admin/configuration/accessing-the-administrative-shell-ssh) (SSH): - - ``` - ghe-cluster-each -- 'if [ $(cat /var/run/haproxy-cluster-proxy.pid) -ne $(systemctl show --property MainPID --value haproxy-cluster-proxy) ]; then echo 'Main PID of haproxy-cluster-proxy does not match /var/run/haproxy-cluster-proxy.pid'; fi' - ``` - - 2. If it shows one or more nodes are affected, reboot the affected nodes. - - 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. diff --git a/data/release-notes/enterprise-server/2-22/8.yml b/data/release-notes/enterprise-server/2-22/8.yml deleted file mode 100644 index cee7e07523..0000000000 --- a/data/release-notes/enterprise-server/2-22/8.yml +++ /dev/null @@ -1,37 +0,0 @@ -date: '2021-03-16' -sections: - security_fixes: - - Packages have been updated to the latest security versions. - bugs: - - Systemd journal logs were duplicated in multiple places. - - A site admin could get a 500 error page while trying to view issues referenced from private repositories. - - Importing of repository archives from GitHub Enterprise Server that are missing repository files would fail with an error. - known_issues: - - On a freshly set up GitHub Enterprise 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. - - | - Users may experience assets such as avatars not loading, or a failure to push/pull code. This may be caused by a PID mismatch in the `haproxy-cluster-proxy` service. To determine if you have an affected instance: - - **Single instance** - - 1. Run this in the [administrative shell](https://docs.github.com/en/enterprise-server/admin/configuration/accessing-the-administrative-shell-ssh) (SSH): - - ``` - if [ $(cat /var/run/haproxy-cluster-proxy.pid) -ne $(systemctl show --property MainPID --value haproxy-cluster-proxy) ]; then echo 'Main PID of haproxy-cluster-proxy does not match /var/run/haproxy-cluster-proxy.pid'; fi - ``` - - 2. If it shows that there is a mismatch, reboot the instance. - - **Cluster or High Availability configuration** - - 1. Run this in the [administrative shell](https://docs.github.com/en/enterprise-server/admin/configuration/accessing-the-administrative-shell-ssh) (SSH): - - ``` - ghe-cluster-each -- 'if [ $(cat /var/run/haproxy-cluster-proxy.pid) -ne $(systemctl show --property MainPID --value haproxy-cluster-proxy) ]; then echo 'Main PID of haproxy-cluster-proxy does not match /var/run/haproxy-cluster-proxy.pid'; fi' - ``` - - 2. If it shows one or more nodes are affected, reboot the affected nodes. - - 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. diff --git a/data/release-notes/enterprise-server/2-22/9.yml b/data/release-notes/enterprise-server/2-22/9.yml deleted file mode 100644 index a7186ca8df..0000000000 --- a/data/release-notes/enterprise-server/2-22/9.yml +++ /dev/null @@ -1,33 +0,0 @@ -date: '2021-03-23' -intro: Downloads have been disabled due to a major bug affecting multiple customers. A fix will be available in the next patch. -sections: - security_fixes: - - '**HIGH:** A remote code execution vulnerability was identified in GitHub Enterprise Server that could be exploited when building a GitHub Pages site. User-controlled configuration options used by GitHub Pages were not sufficiently restricted and made it possible to override environment variables leading to code execution on the GitHub Enterprise Server instance. To exploit this vulnerability, an attacker would need permission to create and build a GitHub Pages site on the GitHub Enterprise Server instance. This vulnerability affected all versions of GitHub Enterprise Server prior to 3.0.3 and was fixed in 3.0.3, 2.22.9, and 2.21.17. This vulnerability was reported via the GitHub Bug Bounty program and has been assigned CVE-2021-22864.' - - Packages have been updated to the latest security versions. - bugs: - - Running `ghe-cluster-config-init` could cause a cluster to become inoperable. - - Systemd could lose track of HAProxy's PID. - - The mysql-failover warning was displayed indefinitely after a successful failover. - - The `ghe-cluster-config-init` run was not fully accounting for the exit code of background jobs leading to improper handling of preflight checks. - - A Security & Analysis link did not appear in the left-side navigation on the Settings page for repositories. - - After disabling GitHub Packages, some organization pages would return an HTTP 500 error response. - changes: - - Improves reliability of nomad services by implementing the same restart policy introduced in GitHub Enterprise Server 3.0. - - Use a relative number for consul and nomad `bootstrap_expect` allowing for a cluster to bootstrap even if a handful of nodes are down. - - Logs will rotate based on size in addition to time. - - Added kafka-lite to the `ghe-cluster-status` command. - known_issues: - - On a freshly set up GitHub Enterprise 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. - - | - Log rotation may fail to signal services to transition to new log files, leading to older log files continuing to be used, and eventual root disk space exhaustion. - To remedy and/or prevent this issue, run the following commands in the [administrative shell](https://docs.github.com/en/enterprise-server/admin/configuration/accessing-the-administrative-shell-ssh) (SSH), or contact [GitHub Enterprise Support](https://support.github.com/contact) for assistance: - - ``` - printf "PATH=/usr/local/sbin:/usr/local/bin:/usr/local/share/enterprise:/usr/sbin:/usr/bin:/sbin:/bin\n29,59 * * * * root /usr/sbin/logrotate /etc/logrotate.conf\n" | sudo sponge /etc/cron.d/logrotate - sudo /usr/sbin/logrotate -f /etc/logrotate.conf - ``` - - '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.' diff --git a/data/release-notes/enterprise-server/3-0/0-rc1.yml b/data/release-notes/enterprise-server/3-0/0-rc1.yml deleted file mode 100644 index 60882dadd1..0000000000 --- a/data/release-notes/enterprise-server/3-0/0-rc1.yml +++ /dev/null @@ -1,25 +0,0 @@ -date: '2021-01-12' -release_candidate: true -deprecated: true -intro: Release candidate versions should be tested on non-production environments. For more information about the Release Candidate Program, see the [GitHub Blog](https://github.blog/2020-12-03-improving-the-ghes-release-process-release-candidates/) or "[About upgrades to new releases](/admin/overview/about-upgrades-to-new-releases)". -sections: - bugs: - - 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. - known_issues: - - On a freshly set up {% data variables.product.prodname_ghe_server %} without any users, an attacker could create the first admin user. - - Release Candidate 1 does not support Cluster mode. - - 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. - - Following an unsuccessful attempt to set up Actions, if you then disable Actions you will not be able to create the first user and use the appliance - - The "Mandatory message viewed" audit log event is not being saved - - '`ghe-config-apply` must be run on a replica during first setup before `ghe-repl-setup` can be run to start replication.' - - Backup-utils can trigger unnecessary emails to administrators - - Incorrect Packages settings are being displayed in the Organization member view page - - After removing oneself as an Enterprise Owner, you are redirected to a 404 page. The operation is successful. - - '`ghe-config-apply` occasionally fails with `ERROR: Failure waiting for nomad jobs to apply` until the Nomad job queue is cleared. This currently requires as admin to delete `/etc/nomad-jobs/queue`.' - - When configuring a multiple replica node, the status of the replica can be incorrectly synchronized. - - Customers attempting to restore a 3.0 backup to a new instance should not pre-configure the instance, as it may lead to a bad state for user logins. We recommend restoring to a fresh, unconfigured instance. - - GitHub Enterprise Server 3.0 release candidates are not yet available in the Azure marketplace. To test release candidates in staging environments, start a 2.21 or 2.22 instance, and then upgrade it with the Azure upgrade package on the download page. - - The image and upgrade package download size has increased. Customers on slow internet connections may find the packages take longer to download. diff --git a/data/release-notes/enterprise-server/3-0/0-rc2.yml b/data/release-notes/enterprise-server/3-0/0-rc2.yml deleted file mode 100644 index a21cbb9e64..0000000000 --- a/data/release-notes/enterprise-server/3-0/0-rc2.yml +++ /dev/null @@ -1,24 +0,0 @@ -date: '2021-01-29' -release_candidate: true -deprecated: true -intro: Release candidate versions should be tested on non-production environments. For more information about the Release Candidate Program, see the [GitHub Blog](https://github.blog/2020-12-03-improving-the-ghes-release-process-release-candidates/) or "[About upgrades to new releases](/admin/overview/about-upgrades-to-new-releases)." -sections: - bugs: - - heading: Fixes for known issues from Release Candidate 1 - notes: - - If you disabled GitHub Actions following an unsuccessful attempt to set up GitHub Actions, then you will not be able to create the first user and use the appliance. - - The "Mandatory message viewed" audit log event was not being saved. - - '`ghe-config-apply` needed to run on a replica during an initial setup before `ghe-repl-setup` could run to start replication.' - - Removing yourself as an enterprise owner returned a 404. - - 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 can only be enabled if the required storage is also configured. - - '`ghe-repl-status` could silently fail if MSSQL replication is not configured.' - - known_issues: - - The known issues for Release Candidate 1 still apply, excluding the bug fixes listed. diff --git a/data/release-notes/enterprise-server/3-0/0.yml b/data/release-notes/enterprise-server/3-0/0.yml deleted file mode 100644 index 36d3d58fab..0000000000 --- a/data/release-notes/enterprise-server/3-0/0.yml +++ /dev/null @@ -1,160 +0,0 @@ -date: '2021-02-16' -intro: The minimum infrastructure requirements have increased for {% data variables.product.prodname_ghe_server %} 3.0+. For more information, see "[About minimum requirements for GitHub Enterprise Server 3.0 and later](/admin/enterprise-management/upgrading-github-enterprise-server#about-minimum-requirements-for-github-enterprise-server-30-and-later)." -sections: - security_fixes: - - '**HIGH:** A remote code execution vulnerability was identified in {% data variables.product.prodname_ghe_server %} that could be exploited when building a {% data variables.product.prodname_pages %} site. User-controlled configuration of the underlying parsers used by {% data variables.product.prodname_pages %} were not sufficiently restricted and made it possible to execute commands on the {% data variables.product.prodname_ghe_server %} instance. To exploit this vulnerability, an attacker would need permission to create and build a {% data variables.product.prodname_pages %} site on the {% data variables.product.prodname_ghe_server %} instance. This vulnerability has been assigned CVE-2020-10519 and was reported via the [GitHub Bug Bounty Program](https://bounty.github.com).' - features: - - heading: GitHub Actions - notes: - - | - [{% data variables.product.prodname_actions %}](https://github.com/features/actions) is now generally available on {% data variables.product.prodname_ghe_server %} 3.0+. Build, test, and deploy your code from {% data variables.product.prodname_dotcom %}. Submit code reviews, branch management, and issue triaging work the way you want. - - This release includes several improvements from the beta of {% data variables.product.prodname_actions %} on {% data variables.product.prodname_ghe_server %}: - - - Enterprise, organization, and repository admins can create security policies for access to {% data variables.product.prodname_actions %} on {% data variables.product.prodname_dotcom_the_website %}. - - Enterprise, organization, and repository admins can allow public repositories to use self-hosted runners. - - Enterprise, organization, and repository admins can now allow workflows to [run on pull requests raised from forks of private repositories](/enterprise-server@3.0/github/setting-up-and-managing-organizations-and-teams/disabling-or-limiting-github-actions-for-your-organization#enabling-workflows-for-private-repository-forks). - - The `workflow_run` event is [now supported](/enterprise-server@3.0/actions/reference/events-that-trigger-workflows#workflow_run) - - Users now have the ability to [disable workflows and enable them at a later date](/enterprise-server@3.0/actions/managing-workflow-runs/disabling-and-enabling-a-workflow). - - Workflow logs have been enhanced for a [better user experience](/enterprise-server@3.0/actions/managing-workflow-runs/using-workflow-run-logs). - - Users can now use private images in container jobs and services. - - The max retention days for [artifacts and logs can now be customized](/enterprise-server@3.0/github/setting-up-and-managing-your-enterprise/configuring-the-retention-period-for-github-actions-artifacts-and-logs-in-your-enterprise-account). - - The runner group API now includes [labels](/enterprise-server@3.0/actions/hosting-your-own-runners/using-labels-with-self-hosted-runners). - - You can now create reusable actions using shell scripts with compose run steps. - - [Encrypted secrets for an organization](/enterprise-server@3.0/actions/reference/encrypted-secrets#creating-encrypted-secrets-for-an-organization) allows you to consolidate secrets across repositories. - - [Workflow templates for an organization](/enterprise-server@3.0/actions/learn-github-actions/sharing-workflows-with-your-organization) streamlines and promotes best practices and consistency across your organization. - - {% data variables.product.prodname_actions %} is not currently supported for enterprises using cluster configurations. - - - heading: GitHub Packages - notes: - - | - [{% data variables.product.prodname_registry %}](https://github.com/features/packages) is a package hosting service, natively integrated with GitHub APIs, Actions, and webhooks. Create an [end-to-end DevOps workflow](/enterprise/3.0/admin/packages/configuring-packages-support-for-your-enterprise) that includes your code, continuous integration, and deployment solutions. - - Supported storage back ends include AWS S3 and MinIO with support for Azure blob coming in a future release. Please note that the current Docker support will be replaced by a beta of the new GitHub Container Registry in the next release. Please review the [updated minimum requirements for your platform](/enterprise/3.0/admin/installation/setting-up-a-github-enterprise-server-instance) before you turn on {% data variables.product.prodname_registry %}. - - When publishing packages to NuGet, users can now use the `--api-key` option to pass their authentication token instead of writing it into a file. For more information, see [Configuring dotnet CLI for use with GitHub Packages](/enterprise-server@3.0/packages/guides/configuring-dotnet-cli-for-use-with-github-packages#publishing-a-package) - - {% data variables.product.prodname_registry %} is not currently supported for enterprises using cluster configurations. - - - heading: GitHub Mobile beta - notes: - - | - [{% data variables.product.prodname_mobile %}](https://github.com/features/) beta allows you to triage notifications and manage issues and pull requests from your device. You can be simultaneously signed into mobile with one user account on {% data variables.product.prodname_dotcom_the_website %} and one user account on {% data variables.product.prodname_ghe_server %}. - - {% data variables.product.prodname_mobile %} beta is now available for {% data variables.product.prodname_ghe_server %}. Sign in with our [Android](https://play.google.com/store/apps/details?id=com.github.android) and [iOS](https://apps.apple.com/app/github/id1477376905) apps to triage notifications and manage issues and pull requests on the go. Administrators can disable mobile support for their Enterprise using the management console or by running `ghe-config app.mobile.enabled false`. - - - heading: Advanced Security Secret Scanning beta - notes: - - | - [Secret Scanning beta](https://github.com/features/security) scans public and private repositories for committed credentials, finds secrets, and notifies the secret provider or admin the moment they are committed into a repository. - - Administrators using {% data variables.product.prodname_GH_advanced_security %} can [enable and configure](/enterprise-server@3.0/admin/configuration/configuring-secret-scanning-for-your-appliance) {% data variables.product.prodname_GH_advanced_security %} secret scanning. You can review the [updated minimum requirements for your platform](/enterprise/3.0/admin/installation/setting-up-a-github-enterprise-server-instance) before you turn on {% data variables.product.prodname_GH_advanced_security %} secret scanning. - - - heading: Advanced Security Code Scanning - notes: - - | - [GitHub Advanced Security code scanning](https://github.com/features/security) is now generally available on GitHub Enterprise Server. Organizations who have purchased Advanced Security can use this capability to do static analysis security testing against their code, and prevent vulnerabilities from making it to their production code using CodeQL, our semantic analysis engine. For more information, see "[Configuring code scanning on your appliance](/en/enterprise-server@3.0/admin/configuration/configuring-code-scanning-for-your-appliance#running-code-scanning-using-github-actions)" - - changes: - - heading: Administration Changes - notes: - - The webhook events delivery system has been rearchitected for higher throughput, faster deliveries, and fewer delayed messages. It also uses less CPU and memory in {% data variables.product.prodname_ghe_server %} 3.0+. - - Organization and Enterprise owners can now see when a team member has been promoted to or demoted from being a team maintainer in the audit log through the new `team.promote_maintainer` and `team.demote_maintainer` audit log events. For more information, see "[Audited actions](/enterprise-server@3.0/admin/user-management/audited-actions)." - - Repository maintainers with existing {% data variables.product.prodname_pages %} sites can [easily update their prior default branch name](/enterprise-server@3.0/github/working-with-github-pages/about-github-pages#publishing-sources-for-github-pages-sites). - - Additional hardware resources are required to run {% data variables.product.prodname_ghe_server %} with any of Actions, Packages or Advanced Security enabled. For more information on the minimum required resources for each supported platform, see "[Setting up a {% data variables.product.prodname_ghe_server %} instance](/enterprise-server@3.0/admin/installation/setting-up-a-github-enterprise-server-instance)." - - Administrators can now [publish a message](/enterprise-server@3.0/admin/user-management/customizing-user-messages-for-your-enterprise), which all users must accept. This can help to onboard new users and surface other organization-specific information and policies. - - - heading: Security Changes - notes: - - Organization owners can now disable publication of {% data variables.product.prodname_pages %} sites from repositories in the organization. Disabling {% data variables.product.prodname_pages %} for the organization will prevent members from creating new Pages sites but will not unpublish existing sites. For more information, see "[Disabling publication of {% data variables.product.prodname_pages %} sites for your organization](/enterprise-server@3.0/github/setting-up-and-managing-organizations-and-teams/disabling-publication-of-github-pages-sites-for-your-organization)." - - A datacenter must be explicitly defined on all nodes before enabling an active replica. - - All usage of SSH fingerprints has been switched to use SHA256 fingerprints as they are used with OpenSSH since version 6.8 as well. This applies to the web interface and also the API where fingerprints are returned such as in GraphQL. The fingerprints follow the OpenSSH format. - - SHA-1 and SHA-256 signature headers (two headers) are sent on webhooks. - - - heading: Developer Changes - notes: - - Majority of the services running in {% data variables.product.prodname_ghe_server %} 3.0+ are now on containers which internally enables GitHub to iterate fast and ship high quality releases - - The webhook events delivery system has been rearchitected for higher throughput, faster deliveries, and fewer delayed messages. - - - heading: API Changes - notes: - - Administrators can now configure and manage the site-wide announcement banner via the REST API. For more information, see the endpoints for "[GitHub Enterprise administration](/enterprise-server@3.0/rest/reference/enterprise-admin#annoucements)." - - A new API endpoint enables the exchange of a user to server token for a user to server token scoped to specific repositories. For more information, see "[Apps](/enterprise-server@3.0/rest/reference/apps#create-a-scoped-access-token)" in the {% data variables.product.prodname_dotcom %} REST API documentation. - - - 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).' diff --git a/data/release-notes/enterprise-server/3-0/1.yml b/data/release-notes/enterprise-server/3-0/1.yml deleted file mode 100644 index b298260e62..0000000000 --- a/data/release-notes/enterprise-server/3-0/1.yml +++ /dev/null @@ -1,71 +0,0 @@ -date: '2021-03-02' -intro: The minimum infrastructure requirements have increased for {% data variables.product.prodname_ghe_server %} 3.0+. For more information, see "[About minimum requirements for GitHub Enterprise Server 3.0 and later](/admin/enterprise-management/upgrading-github-enterprise-server#about-minimum-requirements-for-github-enterprise-server-30-and-later)." -sections: - security_fixes: - - '**HIGH:** An improper access control vulnerability was identified in GitHub Enterprise Server that allowed authenticated users of the instance to gain write access to unauthorized repositories via specifically crafted pull requests and REST API requests. An attacker would need to be able to fork the targeted repository, a setting that is disabled by default for organization owned private repositories. Branch protections such as required pull request reviews or status checks would prevent unauthorized commits from being merged without further review or validation. This vulnerability has been assigned CVE-2021-22861. This issue was reported via the [GitHub Bug Bounty Program](https://bounty.github.com).' - - '**HIGH:** An improper access control vulnerability was identified in the GitHub Enterprise Server GraphQL API that allowed authenticated users of the instance to modify the maintainer collaboration permission of a pull request without proper authorization. By exploiting this vulnerability, an attacker would be able to gain access to head branches of pull requests opened on repositories of which they are a maintainer. Forking is disabled by default for organization owned private repositories and would prevent this vulnerability. Additionally, branch protections such as required pull request reviews or status checks would prevent unauthorized commits from being merged without further review or validation. This vulnerability has been assigned CVE-2021-22863. This issue was reported via the [GitHub Bug Bounty Program](https://bounty.github.com).' - - '**HIGH:** An improper access control vulnerability was identified in GitHub Enterprise Server that allowed an authenticated user with the ability to fork a repository to disclose Actions secrets for the parent repository of the fork. This vulnerability existed due to a flaw that allowed the base reference of a pull request to be updated to point to an arbitrary SHA or another pull request outside of the fork repository. By establishing this incorrect reference in a PR, the restrictions that limit the Actions secrets sent a workflow from forks could be bypassed. This vulnerability affected GitHub Enterprise Server versions 3.0.0, 3.0.0.rc2, and 3.0.0.rc1 and has been assigned CVE-2021-22862. This vulnerability was reported via the GitHub Bug Bounty program.' - - '**MEDIUM:** GitHub Tokens from GitHub Pages builds could end up in logs.' - - 'Packages have been updated to the latest security versions.' - bugs: - - 'The load-balancer health checks in some cases could cause the babeld logs to fill up with errors about the PROXY protocol.' - - 'The HTTP headers were not compliant with HTTP RFC standards in specific responses like 304 status for archives.' - - 'On instances that host Python repositories with the Dependency Graph feature enabled, the instance could become unresponsive due to the root disk filling with error logs.' - - 'An informational message was unintentionally logged as an error during GitHub Enterprise Backup Utilities snapshots, which resulted in unnecessary emails being sent when backups were scheduled by cron jobs that listen for output to stderr.' - - 'On VMWare ESX 6.7 the initial configuration could hang while creating host keys which left the instance inaccessible via SSH.' - - 'When GitHub Actions was enabled, disabling maintenance mode in the management console failed.' - - 'The Package creation setting was shown on the organization member settings page, though this feature is not yet available.' - - 'While enabling secret scanning on the Security & Analysis page the dialog incorrectly mentions private repositories.' - - 'When editing a wiki page a user could experience a 500 error when clicking the Save button.' - - 'An S/MIME signed commit using a certificate with multiple names in the subject alternative name would incorrectly show as "Unverified" in the commit badge.' - - 'User saw 500 error when executing git operations on an instance configured with LDAP authentication.' - - 'Suspended user was sent emails when added to a team.' - - 'When a repository had a large number of manifests an error `You have reached the maximum number of allowed manifest files (20) for this repository.` was shown on the Insights -> Dependency graph tab. For more information, see [Visualization limits](https://docs.github.com/en/github/managing-security-vulnerabilities/troubleshooting-the-detection-of-vulnerable-dependencies#are-there-limits-which-affect-the-dependency-graph-data).' - - 'Fixes users being shown the option to set up the Code Scanning CodeQL Action even if Actions was not enabled for their repository.' - - 'The "Prevent repository admins from changing anonymous Git read access" checkbox available in the enterprise account settings could not be successfully enabled or disabled.' - - 'The modal used to display a mandatory message contained no vertical scrollbar, meaning longer messages could not be viewed in full.' - - 'Redis would sometimes fail to start after a hard reboot or application crash.' - - '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.' - changes: - - 'Satisfy requests concurrently when multiple users are downloading the same archive, resulting in improved performance.' - known_issues: - - 'On a freshly set up GitHub Enterprise 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.' - - '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 [GitHub Enterprise Support](https://support.github.com/contact).' - - '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 `yarn.lock` Javascript manifest files, resulting in HTTP 500 errors in logs.' - - '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.' - - | - Users may experience assets such as avatars not loading, or a failure to push/pull code. This may be caused by a PID mismatch in the `haproxy-cluster-proxy` service. To determine if you have an affected instance: - - **Single instance** - - 1. Run this in the [administrative shell](https://docs.github.com/en/enterprise-server/admin/configuration/accessing-the-administrative-shell-ssh) (SSH): - - ``` - if [ $(cat /var/run/haproxy-cluster-proxy.pid) -ne $(systemctl show --property MainPID --value haproxy-cluster-proxy) ]; then echo 'Main PID of haproxy-cluster-proxy does not match /var/run/haproxy-cluster-proxy.pid'; fi - ``` - - 2. If it shows that there is a mismatch, reboot the instance. - - **Cluster or High Availability configuration** - - 1. Run this in the [administrative shell](https://docs.github.com/en/enterprise-server/admin/configuration/accessing-the-administrative-shell-ssh) (SSH): - - ``` - ghe-cluster-each -- 'if [ $(cat /var/run/haproxy-cluster-proxy.pid) -ne $(systemctl show --property MainPID --value haproxy-cluster-proxy) ]; then echo 'Main PID of haproxy-cluster-proxy does not match /var/run/haproxy-cluster-proxy.pid'; fi' - ``` - - 2. If it shows one or more nodes are affected, reboot the affected nodes. - - '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. diff --git a/data/release-notes/enterprise-server/3-0/10.yml b/data/release-notes/enterprise-server/3-0/10.yml deleted file mode 100644 index 39752a8bbb..0000000000 --- a/data/release-notes/enterprise-server/3-0/10.yml +++ /dev/null @@ -1,19 +0,0 @@ -date: '2021-06-24' -sections: - security_fixes: - - Packages have been updated to the latest security versions. - bugs: - - A large number of `gauge-dependency-graph-api-dispatch_dispatch` metrics could accumulate in the Management Console. - - The sshd service would sometimes fail to start on instances running on Google Cloud Platform. - - Old upgrade files would persist on the user disk, sometimes resulting in out of space conditions. - - Log rotation could sometimes interrupt background jobs. - - '`gh-migrator` displayed an incorrect path to its log output.' - - An export archive would fail to import if it contained review requests from teams not present in the archive. - known_issues: - - On a freshly set up GitHub Enterprise 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. - - 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. diff --git a/data/release-notes/enterprise-server/3-0/11.yml b/data/release-notes/enterprise-server/3-0/11.yml deleted file mode 100644 index 97aa9141b2..0000000000 --- a/data/release-notes/enterprise-server/3-0/11.yml +++ /dev/null @@ -1,26 +0,0 @@ -date: '2021-07-14' -sections: - security_fixes: - - '**HIGH:** A path traversal vulnerability was identified in GitHub Enterprise Server that could be exploited when building a GitHub Pages site. User-controlled configuration options used by GitHub Pages were not sufficiently restricted and made it possible to read files on the GitHub Enterprise Server instance. To exploit this vulnerability, an attacker would need permission to create and build a GitHub Pages site on the GitHub Enterprise Server instance. This vulnerability affected all versions of GitHub Enterprise Server prior to 3.1.3 and has been assigned CVE-2021-22867. This vulnerability was reported via the GitHub Bug Bounty program.' - - Packages have been updated to the latest security versions. - bugs: - - SAML expiration date variable was not configurable. - - Application services would fail their health checks during config apply before they could enter a healthy state. - - '`ghe-cluster-config-node-init` would fail during cluster setup if HTTP proxy is enabled.' - - Pre-receive hooks could encounter an error `Failed to resolve full path of the current executable` due to `/proc` not being mounted on the container. - - Collectd would not resolve the forwarding destination hostname after the initial startup. - - The job that purged stale deleted repositories could fail to make progress if some of those repositories were protected from deletion by legal holds. - - Running `git nw-gc --pristine` would result in an error. - - Background jobs were being queued to the `spam` queue which were not being processed. - - The preferred merge method would be reset when retrying after a failed PR merge. - - Git pushes could result in a 500 Internal Server Error during the user reconciliation process on instances using LDAP authentication mode. - changes: - - Improved the efficiency of config apply by skipping IP allow firewall rules that had not changed, which saved significant time on large clusters. - known_issues: - - On a freshly set up GitHub Enterprise 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. - - 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. diff --git a/data/release-notes/enterprise-server/3-0/12.yml b/data/release-notes/enterprise-server/3-0/12.yml deleted file mode 100644 index 506b66a4ee..0000000000 --- a/data/release-notes/enterprise-server/3-0/12.yml +++ /dev/null @@ -1,21 +0,0 @@ -date: '2021-07-27' -sections: - security_fixes: - - Packages have been updated to the latest security versions. - bugs: - - 'Custom pre-receive hooks could lead to an error like `error: object directory /data/user/repositories/0/nw/12/34/56/7890/network.git/objects does not exist; check .git/objects/info/alternates`.' - - Unauthenticated HTTP proxy for the pages containers build was not supported for any users that use HTTP proxies. - - A significant number of 503 errors were logged every time a user visited a repository''s `/settings` page if the dependency graph was not enabled. - - Internal repositories were only returned when a user had affiliations with the repository through a team or through collaborator status, or queried with the `?type=internal` parameter. - - Failed background jobs had unlimited retries which could cause large queue depths. - - A significant number of 503 errors were being created if the scheduled job to sync vulnerabilities with GitHub.com attempted to run when dependency graph was not enabled and content analysis was enabled. - changes: - - The logs for `babeld` now include a `cmd` field for HTTP ref advertisement requests instead of only including it during the negotiation requests. - 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. - - 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. diff --git a/data/release-notes/enterprise-server/3-0/13.yml b/data/release-notes/enterprise-server/3-0/13.yml deleted file mode 100644 index 627ee2c467..0000000000 --- a/data/release-notes/enterprise-server/3-0/13.yml +++ /dev/null @@ -1,17 +0,0 @@ -date: '2021-08-10' -sections: - bugs: - - When GitHub Actions is enabled without running regular scheduled backups the MSSQL Transaction Log could grow unbounded and can consume all available space on the appliance's Data Disk causing a possible outage. - - Audit log entries for changes made to "Repository creation" organization settings were inaccurate. - - Excessive logging of `ActionController::UnknownFormat` exceptions caused unnecessary disk usage. - - "LDAP `group_dn` values longer than 255 characters would result in errors being logged: `Data truncated for column 'group_dn' at row 1`." - changes: - - Abuse rate limits are now called Secondary rate limits, since the behavior they limit is not always abusive. - 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. - - 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. diff --git a/data/release-notes/enterprise-server/3-0/14.yml b/data/release-notes/enterprise-server/3-0/14.yml deleted file mode 100644 index 73e827224e..0000000000 --- a/data/release-notes/enterprise-server/3-0/14.yml +++ /dev/null @@ -1,21 +0,0 @@ -date: '2021-08-24' -sections: - security_fixes: - - Packages have been updated to the latest security versions. - bugs: - - Attaching very large images or animated GIFs to images or pull requests would fail. - - Journald messages related to automatic updates (`Adding h/m/s random time.`) were logged to syslog. - - 'Custom pre-receive hooks that used a bash subshell would return an error: `No such file or directory`.' - - Custom pre-receive hooks that created named pipes (FIFOs) would crash or hang, resulting in a timeout error. - - Adding filters to the audit log advanced search page did not populate the query text box in real-time with the correct facet prefix and value. - - Git hooks to the internal API that result in failing requests returned the exception `undefined method body for "success":String (NoMethodError)` instead of returning an explicit `nil`. - - When an integration was removed, it was possible for an unrelated OAuth application or integration to also be removed. - - When a mandatory message containing an emoji character was added, attempting to view or change the message would return a 500 Internal Server Error. - 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. - - 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. diff --git a/data/release-notes/enterprise-server/3-0/15.yml b/data/release-notes/enterprise-server/3-0/15.yml deleted file mode 100644 index be396eff72..0000000000 --- a/data/release-notes/enterprise-server/3-0/15.yml +++ /dev/null @@ -1,17 +0,0 @@ -date: '2021-09-07' -sections: - security_fixes: - - Packages have been updated to the latest security versions. - bugs: - - Attempting to tear down a newly-added replica node by specifying its UUID with `ghe-repl-teardown` would fail without reporting an error if replication was not started. - - GitHub Pages builds were being passed through an external proxy if there was one configured. - - Custom pre-receive hooks that created sub-processes would lack a `PATH` variable in their environment, resulting in "No such file or directory" errors. - - MySQL could failover during an upgrade if `mysql-auto-failover` was enabled. - 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. - - 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. diff --git a/data/release-notes/enterprise-server/3-0/16.yml b/data/release-notes/enterprise-server/3-0/16.yml deleted file mode 100644 index c8c0de3aa3..0000000000 --- a/data/release-notes/enterprise-server/3-0/16.yml +++ /dev/null @@ -1,18 +0,0 @@ -date: '2021-09-24' -sections: - security_fixes: - - '**HIGH:** A path traversal vulnerability was identified in {% data variables.product.prodname_ghe_server %} that could be exploited when building a {% data variables.product.prodname_pages %} site. User-controlled configuration options used by {% data variables.product.prodname_pages %} were not sufficiently restricted and made it possible to read files on the {% data variables.product.prodname_ghe_server %} instance. To exploit this vulnerability, an attacker would need permission to create and build a {% data variables.product.prodname_pages %} site on the {% data variables.product.prodname_ghe_server %} instance. This vulnerability affected all versions of {% data variables.product.prodname_ghe_server %} prior to 3.1.8 and was fixed in 3.1.8, 3.0.16, and 2.22.22. This is the result of an incomplete fix for CVE-2021-22867. This vulnerability was reported via the GitHub Bug Bounty program and has been assigned CVE-2021-22868. {% comment %} https://github.com/github/pages/pull/3360, https://github.com/github/pages/pull/3357 {% endcomment %}' - - '**MEDIUM:** An improper access control vulnerability in {% data variables.product.prodname_ghe_server %} allowed a workflow job to execute in a self-hosted runner group it should not have had access to. This affects customers using self-hosted runner groups for access control. A repository with access to one enterprise runner group could access all of the enterprise runner groups within the organization because of improper authentication checks during the request. This could cause code to be run unintentionally by the incorrect runner group. This vulnerability affected {% data variables.product.prodname_ghe_server %} versions from 3.0.0 to 3.0.15 and 3.1.0 to 3.1.7 and was fixed in 3.0.16 and 3.1.8 releases. It has been assigned CVE-2021-22869. {% comment %} https://github.com/github/enterprise2/pull/27003 {% endcomment %}' - bugs: - - 'Resque worker counts were displayed incorrectly during maintenance mode. {% comment %} https://github.com/github/enterprise2/pull/26898, https://github.com/github/enterprise2/pull/26883 {% endcomment %}' - - 'Allocated memcached memory could be zero in clustering mode. {% comment %} https://github.com/github/enterprise2/pull/26927, https://github.com/github/enterprise2/pull/26832 {% endcomment %}' - - 'Fixes {% data variables.product.prodname_pages %} builds so they take into account the NO_PROXY setting of the appliance. This is relevant to appliances configured with an HTTP proxy only. (update 2021-09-30) {% comment %} https://github.com/github/pages/pull/3360 {% endcomment %}' - - 'The GitHub Connect configuration of the source instance was always restored to new instances even when the `--config` option for `ghe-restore` was not used. This would lead to a conflict with the GitHub Connect connection and license synchronization if both the source and destination instances were online at the same time. The fix also requires updating backup-utils to 3.2.0 or higher. [updated: 2021-11-18]' - 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. - - 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. diff --git a/data/release-notes/enterprise-server/3-0/17.yml b/data/release-notes/enterprise-server/3-0/17.yml deleted file mode 100644 index ab0a13b159..0000000000 --- a/data/release-notes/enterprise-server/3-0/17.yml +++ /dev/null @@ -1,25 +0,0 @@ -date: '2021-10-12' -sections: - security_fixes: - - 'Packages have been updated to the latest security versions. {% comment %} https://github.com/github/enterprise2/pull/27034, https://github.com/github/enterprise2/pull/27010 {% endcomment %}' - bugs: - - 'Custom pre-receive hooks could have failed due to too restrictive virtual memory or CPU time limits. {% comment %} https://github.com/github/enterprise2/pull/26971, https://github.com/github/enterprise2/pull/26955 {% endcomment %}' - - 'Attempting to wipe all existing configuration settings with `ghe-cleanup-settings` failed to restart the Management Console service. {% comment %} https://github.com/github/enterprise2/pull/26986, https://github.com/github/enterprise2/pull/26901 {% endcomment %}' - - 'During replication teardown via `ghe-repl-teardown` Memcached failed to be restarted. {% comment %} https://github.com/github/enterprise2/pull/26992, https://github.com/github/enterprise2/pull/26983 {% endcomment %}' - - 'During periods of high load, users would receive HTTP 503 status codes when upstream services failed internal healthchecks. {% comment %} https://github.com/github/enterprise2/pull/27081, https://github.com/github/enterprise2/pull/26999 {% endcomment %}' - - 'Pre-receive hook environments were forbidden from calling the cat command via BusyBox on Alpine. {% comment %} https://github.com/github/enterprise2/pull/27114, https://github.com/github/enterprise2/pull/27094 {% endcomment %}' - - 'The external database password was logged in plaintext. {% comment %} https://github.com/github/enterprise2/pull/27172, https://github.com/github/enterprise2/pull/26413 {% endcomment %}' - - 'An erroneous `jq` error message may have been displayed when running `ghe-config-apply`. {% comment %} https://github.com/github/enterprise2/pull/27203, https://github.com/github/enterprise2/pull/26784 {% endcomment %}' - - 'Failing over from a primary Cluster datacenter to a secondary Cluster datacenter succeeds, but then failing back over to the original primary Cluster datacenter failed to promote Elasticsearch indicies. {% comment %} https://github.com/github/github/pull/193180, https://github.com/github/github/pull/192447 {% endcomment %}' - - 'The Site Admin page for repository self-hosted runners returned an HTTP 500. {% comment %} https://github.com/github/github/pull/194205 {% endcomment %}' - - 'In some cases, GitHub Enterprise Administrators attempting to view the `Dormant users` page received `502 Bad Gateway` or `504 Gateway Timeout` response. {% comment %} https://github.com/github/github/pull/194259, https://github.com/github/github/pull/193609 {% endcomment %}' - changes: - - 'More effectively delete Webhook logs that fall out of the Webhook log retention window. {% comment %} https://github.com/github/enterprise2/pull/27157 {% endcomment %}' - 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. - - 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. diff --git a/data/release-notes/enterprise-server/3-0/18.yml b/data/release-notes/enterprise-server/3-0/18.yml deleted file mode 100644 index 1ae95a4465..0000000000 --- a/data/release-notes/enterprise-server/3-0/18.yml +++ /dev/null @@ -1,15 +0,0 @@ -date: '2021-10-28' -sections: - security_fixes: - - 'Several known weak SSH public keys have been added to the deny list and can no longer be registered. In addition, versions of GitKraken known to generate weak SSH keys (7.6.x, 7.7.x and 8.0.0) have been blocked from registering new public keys.' - - 'Packages have been updated to the latest security versions.' - bugs: - - 'Several parts of the application were unusable for users who are owners of many organizations.' - 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. - - 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. diff --git a/data/release-notes/enterprise-server/3-0/19.yml b/data/release-notes/enterprise-server/3-0/19.yml deleted file mode 100644 index a5b796aa23..0000000000 --- a/data/release-notes/enterprise-server/3-0/19.yml +++ /dev/null @@ -1,23 +0,0 @@ -date: '2021-11-09' -sections: - security_fixes: - - A path traversal vulnerability was identified in {% data variables.product.prodname_pages %} builds on {% data variables.product.prodname_ghe_server %} that could allow an attacker to read system files. To exploit this vulnerability, an attacker needed permission to create and build a {% data variables.product.prodname_pages %} site on the {% data variables.product.prodname_ghe_server %} instance. This vulnerability affected all versions of {% data variables.product.prodname_ghe_server %} prior to 3.3, and was fixed in versions 3.0.19, 3.1.11, and 3.2.3. This vulnerability was reported through the {% data variables.product.company_short %} Bug Bounty program and has been assigned CVE-2021-22870. - - Packages have been updated to the latest security versions. - bugs: - - Some Git operations failed after upgrading a {% data variables.product.prodname_ghe_server %} 3.x cluster because of the HAProxy configuration. - - Unicorn worker counts might have been set incorrectly in clustering mode. - - Resqued worker counts might have been set incorrectly in clustering mode. - - If Ubuntu's Uncomplicated Firewall (UFW) status was inactive, a client could not clearly see it in the logs. - - Some pages and Git-related background jobs might not run in cluster mode with certain cluster configurations. - - The enterprise audit log page would not display audit events for {% data variables.product.prodname_secret_scanning %}. - - 'Users were not warned about potentially dangerous bidirectional unicode characters when viewing files. For more information, see "[Warning about bidirectional Unicode text](https://github.co/hiddenchars)" in {% data variables.product.prodname_blog %}.' - - Hookshot Go sent distribution type metrics that Collectd could not handle, which caused a ballooning of parsing errors. - - Public repositories displayed unexpected results from {% data variables.product.prodname_secret_scanning %} with a type of `Unknown Token`. - 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. - - 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. diff --git a/data/release-notes/enterprise-server/3-0/2.yml b/data/release-notes/enterprise-server/3-0/2.yml deleted file mode 100644 index c50eeb2eb9..0000000000 --- a/data/release-notes/enterprise-server/3-0/2.yml +++ /dev/null @@ -1,57 +0,0 @@ -date: '2021-03-16' -intro: The minimum infrastructure requirements have increased for {% data variables.product.prodname_ghe_server %} 3.0+. For more information, see "[About minimum requirements for GitHub Enterprise Server 3.0 and later](/admin/enterprise-management/upgrading-github-enterprise-server#about-minimum-requirements-for-github-enterprise-server-30-and-later)." -sections: - security_fixes: - - Packages have been updated to the latest security versions. - bugs: - - During a backup an error "Warning: One or more storage objects were not found on the source appliance." was occurring when attempting to clean up purgeable storage objects. - - Dependency graph failed to parse `yarn.lock` JavaScript manifest files, resulting in HTTP 500 errors in logs. - - Disabling GitHub Actions would sometimes fail. - - Custom pre-receive hooks weren't allowed to write to `/tmp`, preventing some scripts from running correctly. - - Systemd journal logs were duplicated in multiple places. - - A timezone set on GitHub Enterprise 11.10.x or earlier was reset to UTC time after upgrading to 3.0 which caused timestamps to shift in some instances. - - Clicking "Publish your first package" in the packages sidebar on a repository would lead to an empty page. - - A site admin could get a 500 error page while trying to view issues referenced from private repositories. - - After disabling GitHub Packages, some organization pages would return an HTTP 500 error response. - - Importing of repository archives from GitHub Enterprise Server that are missing repository files would fail with an error. - - Repository [deploy keys](/developers/overview/managing-deploy-keys) were unable to be used with repositories containing LFS objects. - - In the packages sidebar of a repository, the Docker icon was gray and a tool tip displayed "This service is deprecated". - - Webhooks configured with a content type of `application/x-www-form-urlencoded` did not receive query parameters in the POST request body. - - Users could dismiss a mandatory message without checking all checkboxes. - - In some cases after upgrading from a 2.22.X instance, the web interface assets were missing and the page would not render correctly. - - Running `ghe-config-apply` could time out with `Failure waiting for nomad jobs to apply` due to `'job' stanza not found`. - known_issues: - - On a freshly set up GitHub Enterprise 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. - - 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 [GitHub Enterprise Support](https://support.github.com/contact). - - 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. - - 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. - - | - Users may experience assets such as avatars not loading, or a failure to push/pull code. This may be caused by a PID mismatch in the `haproxy-cluster-proxy` service. To determine if you have an affected instance: - - **Single instance** - - 1. Run this in the [administrative shell](https://docs.github.com/en/enterprise-server/admin/configuration/accessing-the-administrative-shell-ssh) (SSH): - - ``` - if [ $(cat /var/run/haproxy-cluster-proxy.pid) -ne $(systemctl show --property MainPID --value haproxy-cluster-proxy) ]; then echo 'Main PID of haproxy-cluster-proxy does not match /var/run/haproxy-cluster-proxy.pid'; fi - ``` - - 2. If it shows that there is a mismatch, reboot the instance. - - **Cluster or High Availability configuration** - - 1. Run this in the [administrative shell](https://docs.github.com/en/enterprise-server/admin/configuration/accessing-the-administrative-shell-ssh) (SSH): - - ``` - ghe-cluster-each -- 'if [ $(cat /var/run/haproxy-cluster-proxy.pid) -ne $(systemctl show --property MainPID --value haproxy-cluster-proxy) ]; then echo 'Main PID of haproxy-cluster-proxy does not match /var/run/haproxy-cluster-proxy.pid'; fi' - ``` - - 2. If it shows one or more nodes are affected, reboot the affected nodes. - - 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. diff --git a/data/release-notes/enterprise-server/3-0/20.yml b/data/release-notes/enterprise-server/3-0/20.yml deleted file mode 100644 index 58777fda86..0000000000 --- a/data/release-notes/enterprise-server/3-0/20.yml +++ /dev/null @@ -1,21 +0,0 @@ -date: '2021-11-23' -sections: - security_fixes: - - Packages have been updated to the latest security versions. - bugs: - - Pre-receive hooks would fail due to undefined `PATH`. - - 'Running `ghe-repl-setup` would return an error: `cannot create directory /data/user/elasticsearch: File exists` if the instance had previously been configured as a replica.' - - In large cluster environments, the authentication backend could be unavailable on a subset of frontend nodes. - - Some critical services may not have been available on backend nodes in GHES Cluster. - changes: - - An additional outer layer of `gzip` compression when creating a cluster support bundle with `ghe-cluster-suport-bundle` is now turned off by default. This outer compression can optionally be applied with the `ghe-cluster-suport-bundle -c` command line option. - - We have added extra text to the admin console to remind users about the mobile apps' data collection for experience improvement purposes. - - The {% data variables.product.prodname_github_connect %} data connection record now includes a list of enabled {% data variables.product.prodname_github_connect %} features. [Updated 2021-12-09] - 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. - - 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. diff --git a/data/release-notes/enterprise-server/3-0/21.yml b/data/release-notes/enterprise-server/3-0/21.yml deleted file mode 100644 index b9454cd228..0000000000 --- a/data/release-notes/enterprise-server/3-0/21.yml +++ /dev/null @@ -1,22 +0,0 @@ -date: '2021-12-07' -sections: - security_fixes: - - Support bundles could include sensitive files if they met a specific set of conditions. - - A UI misrepresentation vulnerability was identified in GitHub Enterprise Server that allowed more permissions to be granted during a GitHub App's user-authorization web flow than was displayed to the user during approval. This vulnerability affected all versions of GitHub Enterprise Server prior to 3.3 and was fixed in versions 3.2.5, 3.1.13, 3.0.21. This vulnerability was reported via the GitHub Bug Bounty program and has been assigned [CVE-2021-41598](https://www.cve.org/CVERecord?id=CVE-2021-41598). - - A remote code execution vulnerability was identified in GitHub Enterprise Server that could be exploited when building a GitHub Pages site. This vulnerability affected all versions of GitHub Enterprise Server prior to 3.3 and was fixed in versions 3.0.21, 3.1.13, 3.2.5. This vulnerability was reported via the GitHub Bug Bounty program and has been assigned [CVE-2021-41599](https://www.cve.org/CVERecord?id=CVE-2021-41599). Updated February 17, 2022. - bugs: - - Running `ghe-config-apply` could sometimes fail because of permission issues in `/data/user/tmp/pages`. - - A misconfiguration in the Management Console caused scheduling errors. - - Docker would hold log files open after a log rotation. - - GraphQL requests did not set the GITHUB_USER_IP variable in pre-receive hook environments. - changes: - - Clarifies explanation of Actions path-style in documentation. - - Updates support contact URLs to use the current support site, support.github.com. - 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. - - 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. diff --git a/data/release-notes/enterprise-server/3-0/22.yml b/data/release-notes/enterprise-server/3-0/22.yml deleted file mode 100644 index f1ffddca83..0000000000 --- a/data/release-notes/enterprise-server/3-0/22.yml +++ /dev/null @@ -1,13 +0,0 @@ -date: '2021-12-13' -sections: - security_fixes: - - '{% octicon "alert" aria-label="The alert icon" %} **Critical:** A remote code execution vulnerability in the Log4j library, identified as [CVE-2021-44228](https://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2021-44228), affected all versions of {% data variables.product.prodname_ghe_server %} prior to 3.3.1. The Log4j library is used in an open source service running on the {% data variables.product.prodname_ghe_server %} instance. This vulnerability was fixed in {% data variables.product.prodname_ghe_server %} versions 3.0.22, 3.1.14, 3.2.6, and 3.3.1. For more information, please see [this post](https://github.blog/2021-12-13-githubs-response-to-log4j-vulnerability-cve-2021-44228/) on the GitHub Blog.' - - '**December 17, 2021 update**: The fixes in place for this release also mitigate [CVE-2021-45046](https://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2021-45046), which was published after this release. No additional upgrade for {% data variables.product.prodname_ghe_server %} is required to mitigate both CVE-2021-44228 and CVE-2021-45046.' - 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. - - 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. diff --git a/data/release-notes/enterprise-server/3-0/23.yml b/data/release-notes/enterprise-server/3-0/23.yml deleted file mode 100644 index 557f85290c..0000000000 --- a/data/release-notes/enterprise-server/3-0/23.yml +++ /dev/null @@ -1,19 +0,0 @@ -date: '2022-01-18' -sections: - security_fixes: - - 'Packages have been updated to the latest security versions. In these updates, Log4j has been updated to version 2.17.1. Note: previous mitigations released in 3.3.1, 3.2.6, 3.1.14, and 3.0.22 are sufficient to address the impact of CVE-2021-44228, CVE-2021-45046, CVE-2021-45105, and CVE-2021-44832 in these versions of GitHub Enterprise Server.' - - Sanitize more secrets in the generated support bundles - - Packages have been updated to the latest security versions. - bugs: - - Running `ghe-config-apply` could sometimes fail because of permission issues in `/data/user/tmp/pages`. - - The save button in management console was unreachable by scrolling in lower resolution browsers. - - IOPS and Storage Traffic monitoring graphs were not updating after collectd version upgrade. - - Some webhook related jobs could generated large amount of logs. - 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. - - 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. diff --git a/data/release-notes/enterprise-server/3-0/24.yml b/data/release-notes/enterprise-server/3-0/24.yml deleted file mode 100644 index ba44d2770f..0000000000 --- a/data/release-notes/enterprise-server/3-0/24.yml +++ /dev/null @@ -1,20 +0,0 @@ -date: '2022-02-01' -sections: - security_fixes: - - Packages have been updated to the latest security versions. - bugs: - - Pages would become unavailable following a MySQL secret rotation until `nginx` was manually restarted. - - When setting the maintenance schedule with a ISO 8601 date, the actual scheduled time wouldn't match due to the timezone not being transformed to UTC. - - The version number would not be correctly updated after a installing a hotpatch using `ghe-cluster-each`. - - Spurious error messages concerning the `cloud-config.service` would be output to the console. - - When using CAS authentication and the "Reactivate suspended users" option was enabled, suspended users were not automatically reactivated. - changes: - - The GitHub Connect data connection record now includes a count of the number of active and dormant users and the configured dormancy period. - 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. - - 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. diff --git a/data/release-notes/enterprise-server/3-0/25.yml b/data/release-notes/enterprise-server/3-0/25.yml deleted file mode 100644 index 76dd1b8d58..0000000000 --- a/data/release-notes/enterprise-server/3-0/25.yml +++ /dev/null @@ -1,12 +0,0 @@ -date: '2022-02-17' -sections: - security_fixes: - - Packages have been updated to the latest security versions. - 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. - - 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. diff --git a/data/release-notes/enterprise-server/3-0/3.yml b/data/release-notes/enterprise-server/3-0/3.yml deleted file mode 100644 index 468174853d..0000000000 --- a/data/release-notes/enterprise-server/3-0/3.yml +++ /dev/null @@ -1,42 +0,0 @@ -date: '2021-03-23' -intro: Downloads have been disabled due to a major bug affecting multiple customers. A fix will be available in the next patch. -sections: - security_fixes: - - '**HIGH:** A remote code execution vulnerability was identified in GitHub Enterprise Server that could be exploited when building a GitHub Pages site. User-controlled configuration options used by GitHub Pages were not sufficiently restricted and made it possible to override environment variables leading to code execution on the GitHub Enterprise Server instance. To exploit this vulnerability, an attacker would need permission to create and build a GitHub Pages site on the GitHub Enterprise Server instance. This vulnerability affected all versions of GitHub Enterprise Server prior to 3.0.3 and was fixed in 3.0.3, 2.22.9, and 2.21.17. This vulnerability was reported via the GitHub Bug Bounty program and has been assigned CVE-2021-22864.' - - Packages have been updated to the latest security versions. - bugs: - - Running `ghe-cluster-config-init` could cause a cluster to become inoperable. - - Resolving merge conflicts in the GUI would fail when custom pre-receive hooks are configured on the repository. - - '`launch-deployer` and `launch-receiver` were logging at DEBUG level and filling logs with unnecessary information.' - - Systemd could lose track of HAProxy's PID. - - When Actions was configured to use S3 storage, the logs for an action would sometimes fail to load. - - The mysql-failover warning was displayed indefinitely after a successful failover. - - The `ghe-cluster-config-init` run was not fully accounting for the exit code of background jobs leading to improper handling of preflight checks. - - When enabling GitHub Actions, initialization could fail silently. - - When vulnerability alerting is enabled, upgrades to the 3.0 series would fail. - - Jobs related to Codespaces were being enqueued leading to an accumulation of unprocessed jobs. - changes: - - Use a relative number for consul and nomad `bootstrap_expect` allowing for a cluster to bootstrap even if a handful of nodes are down. - - Logs will rotate based on size in addition to time. - - Added kafka-lite to the `ghe-cluster-status` command. - known_issues: - - On a freshly set up GitHub Enterprise 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. - - 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 [GitHub Enterprise Support](https://support.github.com/contact). - - 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. - - 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. - - | - Log rotation may fail to signal services to transition to new log files, leading to older log files continuing to be used, and eventual root disk space exhaustion. - To remedy and/or prevent this issue, run the following commands in the [administrative shell](https://docs.github.com/en/enterprise-server/admin/configuration/accessing-the-administrative-shell-ssh) (SSH), or contact [GitHub Enterprise Support](https://support.github.com/) for assistance: - - ``` - printf "PATH=/usr/local/sbin:/usr/local/bin:/usr/local/share/enterprise:/usr/sbin:/usr/bin:/sbin:/bin\n29,59 * * * * root /usr/sbin/logrotate /etc/logrotate.conf\n" | sudo sponge /etc/cron.d/logrotate - sudo /usr/sbin/logrotate -f /etc/logrotate.conf - ``` - - 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. diff --git a/data/release-notes/enterprise-server/3-0/4.yml b/data/release-notes/enterprise-server/3-0/4.yml deleted file mode 100644 index d9e9e60811..0000000000 --- a/data/release-notes/enterprise-server/3-0/4.yml +++ /dev/null @@ -1,27 +0,0 @@ -date: '2021-04-01' -intro: The minimum infrastructure requirements have increased for {% data variables.product.prodname_ghe_server %} 3.0+. For more information, see "[About minimum requirements for GitHub Enterprise Server 3.0 and later](/admin/enterprise-management/upgrading-github-enterprise-server#about-minimum-requirements-for-github-enterprise-server-30-and-later)." -sections: - security_fixes: - - "**HIGH:** An improper access control vulnerability was identified in GitHub Enterprise Server that allowed access tokens generated from a GitHub App's [web authentication flow](https://docs.github.com/en/developers/apps/identifying-and-authorizing-users-for-github-apps#web-application-flow) to read private repository metadata via the REST API without having been granted the appropriate permissions. To exploit this vulnerability, an attacker would need to create a GitHub App on the instance and have a user authorize the application through the web authentication flow. The private repository metadata returned would be limited to repositories owned by the user the token identifies. This vulnerability affected all versions of GitHub Enterprise Server prior to 3.0.4 and was fixed in versions 3.0.4, 2.22.10, 2.21.18. This vulnerability has been assigned CVE-2021-22865 and was reported via the [GitHub Bug Bounty Program](https://bounty.github.com)." - - Packages have been updated to the latest security versions. - bugs: - - When maintenance mode was enabled, some services continued to be listed as "active processes" even though they were expected to be running, and should not have been listed. - - After upgrading from 2.22.x to 3.0.x with GitHub Actions enabled, the self-hosted runner version was not updated and no self-hosted updates were made. - - Old GitHub Pages builds were not cleaned up leading to increased disk usage. - - '`memcached` was not running on active replicas.' - - Upgrade failed when updating file permissions when GitHub Actions was enabled. - - A timezone set on GitHub Enterprise 11.10.x or earlier was not being used by some services which were defaulting to UTC time. - - Services were not transitioning to new log files as part of log rotation, resulting in increased disk usage. - - The `ghe-saml-mapping-csv` command-line utility produced a warning message. - - The label on search results for internal repositories was shown as "Private" instead of "Internal". - known_issues: - - On a freshly set up GitHub Enterprise 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. - - 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. - - 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. diff --git a/data/release-notes/enterprise-server/3-0/5.yml b/data/release-notes/enterprise-server/3-0/5.yml deleted file mode 100644 index 959741e81e..0000000000 --- a/data/release-notes/enterprise-server/3-0/5.yml +++ /dev/null @@ -1,28 +0,0 @@ -date: '2021-04-14' -intro: The minimum infrastructure requirements have increased for {% data variables.product.prodname_ghe_server %} 3.0+. For more information, see "[About minimum requirements for GitHub Enterprise Server 3.0 and later](/admin/enterprise-management/upgrading-github-enterprise-server#about-minimum-requirements-for-github-enterprise-server-30-and-later)." -sections: - security_fixes: - - Packages have been updated to the latest security versions. - bugs: - - Some logs were not included in the log forwarding configuration. - - 'A warning message `jq: error (at :0): Cannot index number with string "settings"` could occur during replica promotion.' - - Continuously restoring backups to a cluster could fail due to MySQL replicas failing to connect to the primary. - - Pages were not getting published when using custom CA certificate. - - Packages related subdomains were not showing up in the "Test domain settings" prompt for subdomain isolation. - - The `X-GitHub-Enterprise-Host` header sent with webhooks included a random string, rather than the hostname of the GitHub Enterprise Server instance that sent the HTTP POST payload. - - Upgrading from 2.22.x to 3.0.x would fail if GitHub Actions had previously been enabled, but disabled before the upgrade. - - Visiting the `/settings/emails` page would store state that could cause improper redirects when logging out and logging back in. - - GitHub integration apps were not able to notify teams when mentioned directly via an at-mention in an issue comment. - - reStructuredText (RST) rendering in the web UI would fail and instead displayed raw RST markup text. - - Email notifications for Secret Scanning alerts were not sent to authorized users when the Dependency Graph was not fully enabled. - - When ghe-migrator encountered import errors, it would sometimes abort the entire process, and the logs did not include enough context. - - Jupyter notebooks with non-ASCII characters could fail to render. - known_issues: - - On a freshly set up GitHub Enterprise 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. - - 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. diff --git a/data/release-notes/enterprise-server/3-0/6.yml b/data/release-notes/enterprise-server/3-0/6.yml deleted file mode 100644 index 86dbb56f54..0000000000 --- a/data/release-notes/enterprise-server/3-0/6.yml +++ /dev/null @@ -1,31 +0,0 @@ -date: '2021-04-28' -sections: - security_fixes: - - Packages have been updated to the latest security versions. - bugs: - - During upgrades, the process would pause indefinitely after `cleanup nomad job`. - - 'Failing `ghe-cluster-failover` with the error message `Trilogy::Error: trilogy_connect`.' - - '`ghe-cluster-status-mysql` showed warnings about failovers as errors.' - - Setup script running on MySQL replication may have caused unnecessary database reseeding during database failover. - - Upgrades did not include the latest version of Actions runner properly installed. - - '`github-env` configuration could result in zombie processes.' - - '`config-apply` could take longer than necessary due to `rake db:migrate` being called unnecessarily.' - - Orchestrator could have failed over to a MySQL replica which was not replicating from primary during seeding phase when primary could not be connected. - - Organizations or projects with errors blocked migration and could not be excluded. - - The Create Repository button was disabled for users who belonged to more than 50 organizations. - - Deleting a branch would temporarily flash an error message indicating something went wrong when the deletion was successful. - - The `rms-packages` index was shown in the site admin dashboard. - - Organization owner was unable to create internal repository due to the correct visibility options not being displayed on the form. - - The repository actions tab rendered a 500 in cases where the actions starter workflows were misconfigured. - - Customers with more than three storage hosts were unable to restore to their disaster-recovery cluster due to the fullest disks being selected instead of empty nodes. - - Code Scanning backend services did not start up reliably after applying hotpatches. - changes: - - Preflight checks allow all AWS instance types by default. - known_issues: - - On a freshly set up GitHub Enterprise 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. - - 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. diff --git a/data/release-notes/enterprise-server/3-0/7.yml b/data/release-notes/enterprise-server/3-0/7.yml deleted file mode 100644 index 658076a1d7..0000000000 --- a/data/release-notes/enterprise-server/3-0/7.yml +++ /dev/null @@ -1,24 +0,0 @@ -date: '2021-05-13' -sections: - security_fixes: - - "**HIGH:** A UI misrepresentation vulnerability was identified in GitHub Enterprise Server that allowed more permissions to be granted during a GitHub App's user-authorization web flow than was displayed to the user during approval. To exploit this vulnerability, an attacker would need to create a GitHub App on the instance and have a user authorize the application through the web authentication flow. All permissions being granted would properly be shown during the first authorization, but in certain circumstances, if the user revisits the authorization flow after the GitHub App has configured additional user-level permissions, those additional permissions may not be shown, leading to more permissions being granted than the user potentially intended. This vulnerability affected GitHub Enterprise Server 3.0.x prior to 3.0.7 and 2.22.x prior to 2.22.13. It was fixed in versions 3.0.7 and 2.22.13. This vulnerability has been assigned CVE-2021-22866 and was reported via the [GitHub Bug Bounty Program](https://bounty.github.com/)." - - Packages have been updated to the latest security versions. - bugs: - - Quotes included in Actions or Packages storage configuration could cause errors. - - Custom pre-receive hooks could fail due to too restrictive file size or number of open file limits. - - Orchestrator auto failover could be enabled during the phase of config apply. - - Users with maintainer permissions to a repository were shown an e-mail verification warning instead of a successful page build on the repository Pages settings page. - - The code owner of a wildcard rule would be incorrectly added to the list of owners for the code owners badge even if a later rule took precedence for that path. - - OpenAPI documentation referred to an invalid header. - - 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. - changes: - - Added logging for config change on HAProxy reload. - - Added logging for repository creation. - known_issues: - - On a freshly set up GitHub Enterprise 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. - - 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. diff --git a/data/release-notes/enterprise-server/3-0/8.yml b/data/release-notes/enterprise-server/3-0/8.yml deleted file mode 100644 index 302c8471fe..0000000000 --- a/data/release-notes/enterprise-server/3-0/8.yml +++ /dev/null @@ -1,27 +0,0 @@ -date: '2021-05-25' -sections: - 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: - - On the "Configure Actions and Packages" page of the initial installation process, when an admin clicked the "Test domain settings" button the test did not complete. - - Running `ghe-btop` failed with error `cannot find a 'babeld' container`. - - Users were experiencing service unavailability after upgrading due to a mismatch of internal and external timeout values. - - Normal replication delays in MSSQL generated warnings. - - Link for GitHub Enterprise Clustering Guide on management console was incorrect. - - An IP address added by an admin using the "Create Whitelist Entry" button could still be locked out. - - References to the "Dependency graph" and "Dependabot alerts" features were shown on repositories where they were not enabled. - - HTTP POST requests to the `/hooks` endpoint could fail with a 401 response due to the `hookID` being set incorrectly. - - 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".' - changes: - - Check annotations older than 4 months will be archived. - 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. - - On a freshly set up GitHub Enterprise 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. - - 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. diff --git a/data/release-notes/enterprise-server/3-0/9.yml b/data/release-notes/enterprise-server/3-0/9.yml deleted file mode 100644 index 2db2c8f61d..0000000000 --- a/data/release-notes/enterprise-server/3-0/9.yml +++ /dev/null @@ -1,24 +0,0 @@ -date: '2021-06-10' -sections: - security_fixes: - - Packages have been updated to the latest security versions. - bugs: - - The upgrade process could fail while upgrading Actions if the instance could not make self-requests using its configured hostname. - - SVN 1.7 and older clients showed an error when using the `svn co` and `svn export` commands. - - Accessing a repository through the administrative shell using `ghe-repo /` would hang. - - After upgrading, users experienced reduced availability during heavy usage, because services restarted too frequently. This would occur due to timeout mismatches between the nomad configuration and that of the internal services. - - In some instances, running `ghe-repl-status` after setting up GitHub Actions would produce an error and `ghe-actions-teardown` would fail. - - '`ghe-dbconsole` would return errors under some circumstances.' - - Import failures of organizations or repositories from non-GitHub sources could produce an `undefined method '[]' for nil:NilClass` error. - - GitHub profile names might have changed unintentionally when using SAML authentication, if the GitHub profile name did not match the value of the attribute mapped to the `Full name` field in the Management Console. - changes: - - The `firstPatchedVersion` field is now available on `SecurityVulnerability` objects in the GraphQL API. - - Users of the GraphQL API can query the public field `closingIssuesReferences` on the `PullRequest` object. This field retrieves issues that will be automatically closed when the related pull request is merged. This approach will also allow this data to be migrated in future, as part of a higher fidelity migration process. - known_issues: - - On a freshly set up GitHub Enterprise 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. - - 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. diff --git a/data/release-notes/enterprise-server/3-1/0-rc1.yml b/data/release-notes/enterprise-server/3-1/0-rc1.yml deleted file mode 100644 index 520bfd612f..0000000000 --- a/data/release-notes/enterprise-server/3-1/0-rc1.yml +++ /dev/null @@ -1,20 +0,0 @@ -date: '2021-05-06' -release_candidate: true -deprecated: true -intro: If {% data variables.location.product_location %} is running a release candidate build, you can't upgrade with a hotpatch. We recommend only running release candidates on test environments. -sections: - 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: - - 'A scheduled cleanup job can cause performance to degrade on an instance with a very large `check_annotations` table.' - changes: - - Check annotations older than 4 months will be archived. - - 'The `firstPatchedVersion` field is now available on `SecurityVulnerability` objects in the GraphQL API.' - known_issues: - - The GitHub Packages 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 GitHub Enterprise 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. diff --git a/data/release-notes/enterprise-server/3-1/0.yml b/data/release-notes/enterprise-server/3-1/0.yml deleted file mode 100644 index 3b24968dd8..0000000000 --- a/data/release-notes/enterprise-server/3-1/0.yml +++ /dev/null @@ -1,173 +0,0 @@ -date: '2021-06-03' -intro: For minimum infrastructure requirements, see "[About minimum requirements for {% data variables.product.prodname_ghe_server %} 3.0 and later](/admin/enterprise-management/upgrading-github-enterprise-server#about-minimum-requirements-for-github-enterprise-server-30-and-later)." -sections: - features: - - heading: GitHub Advanced Security Secret Scanning - notes: - - | - [Secret Scanning](https://github.com/features/security) is now generally available on {% data variables.product.prodname_ghe_server %} 3.1+. Scan public and private repositories for committed credentials, find secrets, and notify the secret provider or admin the moment they are committed into a repository. - - This release includes several improvements from the beta of Secret Scanning on {% data variables.product.prodname_ghe_server %}: - - - Expanded our [pattern coverage](/enterprise-server@3.1/code-security/secret-security/about-secret-scanning#about-secret-scanning-for-private-repositories) from 24 partners to 37 - - Added an [API](/rest/reference/secret-scanning) and [webhooks](/developers/webhooks-and-events/webhook-events-and-payloads#secret_scanning_alert) - - Added [notifications for commit authors](https://github.blog/changelog/2021-03-05-secret-scanning-notifications-for-commit-authors-on-private-repositories/) when they commit secrets - - Updated the index view to made it easy to triage secrets in bulk - - Reduced the false positive rate on many patterns - - Administrators using {% data variables.product.prodname_GH_advanced_security %} can [enable and configure](/enterprise-server@3.1/admin/configuration/configuring-secret-scanning-for-your-appliance) {% data variables.product.prodname_GH_advanced_security %} secret scanning. You can review the [updated minimum requirements for your platform](/enterprise-server@3.1/admin/installation/setting-up-a-github-enterprise-server-instance) before you turn on {% data variables.product.prodname_GH_advanced_security %} secret scanning. - - - heading: GitHub Advanced Security billing improvements - notes: - - | - This release includes several improvements to {% data variables.product.prodname_GH_advanced_security %} billing in {% data variables.product.prodname_ghe_server %}: - - - {% data variables.product.prodname_GH_advanced_security %} customers can now view their active committer count and the remaining number of unused committer seats on their organization or enterprise account’s Billing page. If Advanced Security is purchased for an enterprise, administrators can also view the active committer seats which are being used by other organizations within their enterprise. For more information, see "[About GitHub Advanced Security licensing](/enterprise-server@3.1/admin/advanced-security/about-licensing-for-github-advanced-security)" and "[Viewing your GitHub Advanced Security usage](/enterprise-server@3.1/admin/advanced-security/viewing-your-github-advanced-security-usage)." - - GitHub Advanced Security customers can now view their active committer count for any Advanced Security enabled repositories on their organization or enterprise account's Billing page. These changes help billing administrators track their usage against how many committer licenses they purchased. For more information see "[Managing security and analysis settings for your organization](/enterprise-server@3.1/organizations/keeping-your-organization-secure/managing-security-and-analysis-settings-for-your-organization)." - - - heading: Dependabot improvements - notes: - - | - This release includes improvements to Dependabot alerts in {% data variables.product.prodname_ghe_server %}: - - - Users with Dependabot alerts enabled can see which of their repositories are impacted by a given vulnerability by navigating to its entry in the [GitHub Advisory Database](https://github.com/advisories). This feature is available in public beta. For more information, see "[Viewing and updating vulnerable dependencies in your repository](/enterprise-server@3.1/code-security/supply-chain-security/viewing-and-updating-vulnerable-dependencies-in-your-repository)." - - When a vulnerability is added to GitHub Advisory Database, you will no longer receive [email and web notifications](https://github.com/notifications) for Dependabot alerts on low and moderate severity vulnerabilities. These alerts are still accessible from the repository's Security tab. For more information, see "[Viewing and updating vulnerable dependencies in your repository](/enterprise-server@3.1/code-security/supply-chain-security/viewing-and-updating-vulnerable-dependencies-in-your-repository)." - - You can now give people instructions on how to responsibly report security vulnerabilities in your project by adding a `SECURITY.md` file to your repository's `root`, `docs`, or `.github` folder. When someone creates an issue in your repository, they will see a link to your project's security policy. For more information, see "[Adding a security policy to your repository](/enterprise-server@3.1/code-security/getting-started/adding-a-security-policy-to-your-repository)." - - - heading: GitHub Actions Workflow Visualization beta - notes: - - | - {% data variables.product.prodname_actions %} can now generate a visual graph of your workflow on every run. With workflow visualization, you can: - - View and understand complex workflows - - Track progress of workflows in real-time - - Troubleshoot runs quickly by easily accessing logs and jobs metadata - - Monitor progress of deployment jobs and easily access deployment targets - - For more information, see "[Using the visualization graph](/actions/managing-workflow-runs/using-the-visualization-graph)." - - - heading: OAuth 2.0 Device Authorization Grant - notes: - - | - [OAuth 2.0 Device Authorization Grant](https://github.com/login/device) allows any CLI client or developer tool to authenticate using a secondary system with a browser. - - Administrators using [OAuth Apps](/developers/apps/authorizing-oauth-apps#device-flow) and [GitHub Apps](/developers/apps/authorizing-oauth-apps#device-flow) can enable and configure OAuth 2.0 Device Authorization Flow, in addition to the existing Web Application Flow. You can review the [updated minimum requirements for your platform](/enterprise-server@3.1/admin/installation/setting-up-a-github-enterprise-server-instance) before you enable OAuth 2.0 Device Authorization Flow. - - - heading: Pull request auto-merge - notes: - - | - With auto-merge, pull requests can be set to merge automatically when all merge requirements have been satisfied. This saves users from needing to constantly check the state of their pull requests just to merge them. Auto-merge can be enabled by a user with permission to merge and on pull requests that have unsatisfied merge requirements. For more information, see "[Automatically merging a pull request](/enterprise-server@3.1/github/collaborating-with-issues-and-pull-requests/automatically-merging-a-pull-request)." - - - heading: Custom notifications - notes: - - | - You can customize the types of notifications you want to receive from individual repositories. For more information, see "[Configuring notifications](/enterprise-server@3.1/github/managing-subscriptions-and-notifications-on-github/configuring-notifications#configuring-your-watch-settings-for-an-individual-repository)." - - - heading: GitHub Mobile filtering - notes: - - | - [{% data variables.product.prodname_mobile %}](https://github.com/mobile) filtering allows you to search for and find issues, pull requests, and discussions from your device. New metadata for issues and pull request list items allow you to filter by assignees, checks status, review states, and comment counts. - - {% data variables.product.prodname_mobile %} beta is available for {% data variables.product.prodname_ghe_server %}. Sign in with our [Android](https://play.google.com/store/apps/details?id=com.github.android) and [iOS](https://apps.apple.com/app/github/id1477376905) apps to triage notifications and manage issues and pull requests on the go. Administrators can disable mobile support for their Enterprise using the management console or by running `ghe-config app.mobile.enabled false`. For more information, see "[GitHub Mobile](/get-started/using-github/github-mobile)." - - changes: - - heading: Administration Changes - notes: - - By precomputing checksums, the amount of time a repository is under the lock has reduced dramatically, allowing more write operations to succeed immediately and improving monorepo performance. - - The latest release of the CodeQL CLI supports uploading analysis results to GitHub. This makes it easier to run code analysis for customers who wish to use CI/CD systems other than {% data variables.product.prodname_actions %}. Previously, such users had to use the separate CodeQL runner, which will continue to be available. For more information, see "[About CodeQL code scanning in your CI system](/enterprise-server@3.1/code-security/secure-coding/about-codeql-code-scanning-in-your-ci-system)." - - '{% data variables.product.prodname_actions %} now supports skipping `push` and `pull_request` workflows by looking for some common keywords in your commit message.' - - Check annotations older than four months will be archived. - - Scaling of worker allocation for background tasks has been revised. We recommend validating that the new defaults are appropriate for your workload. Custom background worker overrides should be unset in most cases. [Updated 2022-03-18] - - - heading: Security Changes - notes: - - Following feedback, display of Code Scanning results on a pull request without submitting with a pull request ID will remain supported. For more information, see "[Configuring code scanning](/enterprise-server@3.1/code-security/secure-coding/configuring-code-scanning#scanning-pull-requests)" and "[Configuring CodeQL code scanning in your CI system](/enterprise-server@3.1/code-security/secure-coding/configuring-codeql-code-scanning-in-your-ci-system#scanning-pull-requests). - - SARIF upload support increased to a maximum of 5000 results per upload. - - - heading: Developer Changes - notes: - - You can specify multiple callback URLs while configuring a GitHub App. This can be used in services with multiple domains or subdomains. GitHub will always deny authorization if the callback URL from the request is not in the authorization callback URL list. - - The GitHub App file permission has been updated to allow an app developer to specify up to 10 files for read-only or read-write access that their app can request access to. - - CodeQL now supports more [libraries and frameworks](https://codeql.github.com/docs/codeql-overview/supported-languages-and-frameworks/) for a variety of 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),[Java](https://github.com/github/codeql/tree/main/java), [Go](https://github.com/github/codeql-go/tree/main)). The CodeQL engine can now detect more sources of untrusted user data, which improves the quality and depth of the code scanning alerts. For more information, see "[About CodeQL](https://codeql.github.com/docs/codeql-overview/about-codeql/)." - - When configuring a GitHub App, the authorization callback URL is a required field. Now, we allow the developer to specify multiple callback URLs. This can be used in services with multiple domains or subdomains. GitHub will always deny authorization if the callback URL from the request is not in the authorization callback URL list. - - Delete an entire directory of files, including subdirectories, from your web browser. For more information, see "[Deleting a file or directory](/enterprise-server@3.1/github/managing-files-in-a-repository/deleting-files-in-a-repository#deleting-a-directory)." - - 'Include multiple words after the `#` in an issue, discussion, or pull request comment to further narrow your search.' - - 'When you’re writing an issue, pull request, or discussion comment the list syntax for bullets, numbers, and tasks autocompletes after you press `return` or `enter`.' - - - 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).' diff --git a/data/release-notes/enterprise-server/3-1/1.yml b/data/release-notes/enterprise-server/3-1/1.yml deleted file mode 100644 index 81341e76c4..0000000000 --- a/data/release-notes/enterprise-server/3-1/1.yml +++ /dev/null @@ -1,30 +0,0 @@ -date: '2021-06-10' -sections: - security_fixes: - - Packages have been updated to the latest security versions. - bugs: - - SVN 1.7 and older clients showed an error when using the `svn co` and `svn export` commands. - - Accessing a repository through the administrative shell using `ghe-repo /` would hang. - - After upgrading, users experienced reduced availability during heavy usage, because services restarted too frequently. This would occur due to timeout mismatches between the nomad configuration and that of the internal services. - - In some instances, running `ghe-repl-status` after setting up GitHub Actions would produce an error and `ghe-actions-teardown` would fail. - - '`ghe-dbconsole` would return errors under some circumstances.' - - Import failures of organizations or repositories from non-GitHub sources could produce an `undefined method '[]' for nil:NilClass` error. - - GitHub profile names might have changed unintentionally when using SAML authentication, if the GitHub profile name did not match the value of the attribute mapped to the `Full name` field in the Management Console. - - Upgrading an instance that had previously ran a 2.13 release, but not a 2.14 release, resulted in a database migration error relating to the `AddRepositoryIdToCheckRuns` data transition. - changes: - - Users of the GraphQL API can query the public field `closingIssuesReferences` on the `PullRequest` object. This field retrieves issues that will be automatically closed when the related pull request is merged. This approach will also allow this data to be migrated in future, as part of a higher fidelity migration process. - known_issues: - - The {% data variables.product.prodname_registry %} npm registry no longer returns a time value in metadata responses. This was done to allow for substantial performance improvements. We continue to have all the data necessary to return a time value as part of the metadata response and will resume returning this value in the future once we have solved the existing performance issues. - - 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. - - | - 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. - - If {% data variables.product.prodname_actions %} is enabled for {% data variables.product.prodname_ghe_server %}, teardown of a replica node with `ghe-repl-teardown` will succeed, but may return `ERROR:Running migrations`. - - Resource limits that are specific to processing pre-receive hooks may cause some pre-receive hooks to fail. diff --git a/data/release-notes/enterprise-server/3-1/10.yml b/data/release-notes/enterprise-server/3-1/10.yml deleted file mode 100644 index ea45f7b83d..0000000000 --- a/data/release-notes/enterprise-server/3-1/10.yml +++ /dev/null @@ -1,21 +0,0 @@ -date: '2021-10-28' -sections: - security_fixes: - - 'It was possible for cleartext passwords to end up in certain log files.' - - 'Several known weak SSH public keys have been added to the deny list and can no longer be registered. In addition, versions of GitKraken known to generate weak SSH keys (7.6.x, 7.7.x and 8.0.0) have been blocked from registering new public keys.' - - 'Packages have been updated to the latest security versions.' - bugs: - - 'Restore might fail for enterprise server in clustering mode if orchestrator isnt healthily.' - - 'Several parts of the application were unusable for users who are owners of many organizations.' - - 'Fixed a link to https://docs.github.com.' - changes: - - 'Browsing and job performance optimizations for repositories with many refs.' - known_issues: - - The {% data variables.product.prodname_registry %} npm registry no longer returns a time value in metadata responses. This was done to allow for substantial performance improvements. We continue to have all the data necessary to return a time value as part of the metadata response and will resume returning this value in the future once we have solved the existing performance issues. - - 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. - - If {% data variables.product.prodname_actions %} is enabled for {% data variables.product.prodname_ghe_server %}, teardown of a replica node with `ghe-repl-teardown` will succeed, but may return `ERROR:Running migrations`. - - Resource limits that are specific to processing pre-receive hooks may cause some pre-receive hooks to fail. diff --git a/data/release-notes/enterprise-server/3-1/11.yml b/data/release-notes/enterprise-server/3-1/11.yml deleted file mode 100644 index 724c3efc7c..0000000000 --- a/data/release-notes/enterprise-server/3-1/11.yml +++ /dev/null @@ -1,28 +0,0 @@ -date: '2021-11-09' -sections: - security_fixes: - - A path traversal vulnerability was identified in {% data variables.product.prodname_pages %} builds on {% data variables.product.prodname_ghe_server %} that could allow an attacker to read system files. To exploit this vulnerability, an attacker needed permission to create and build a {% data variables.product.prodname_pages %} site on the {% data variables.product.prodname_ghe_server %} instance. This vulnerability affected all versions of {% data variables.product.prodname_ghe_server %} prior to 3.3, and was fixed in versions 3.0.19, 3.1.11, and 3.2.3. This vulnerability was reported through the {% data variables.product.company_short %} Bug Bounty program and has been assigned CVE-2021-22870. - - Packages have been updated to the latest security versions. - bugs: - - Some Git operations failed after upgrading a {% data variables.product.prodname_ghe_server %} 3.x cluster because of the HAProxy configuration. - - Unicorn worker counts might have been set incorrectly in clustering mode. - - Resqued worker counts might have been set incorrectly in clustering mode. - - If Ubuntu's Uncomplicated Firewall (UFW) status was inactive, a client could not clearly see it in the logs. - - Upgrading from {% data variables.product.prodname_ghe_server %} 2.x to 3.x failed when there were UTF8 characters in an LDAP configuration. - - Some pages and Git-related background jobs might not run in cluster mode with certain cluster configurations. - - When a new tag was created, the [push](/developers/webhooks-and-events/webhooks/webhook-events-and-payloads#push) webhook payload did not display a correct `head_commit` object. Now, when a new tag is created, the 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. - - The enterprise audit log page would not display audit events for {% data variables.product.prodname_secret_scanning %}. - - There was an insufficient job timeout for replica repairs. - - 'Users were not warned about potentially dangerous bidirectional unicode characters when viewing files. For more information, see "[Warning about bidirectional Unicode text](https://github.co/hiddenchars)" in {% data variables.product.prodname_blog %}.' - - Hookshot Go sent distribution type metrics that Collectd could not handle, which caused a ballooning of parsing errors. - changes: - - Kafka configuration improvements have been added. When deleting repositories, package files are now immediately deleted from storage account to free up space. `DestroyDeletedPackageVersionsJob` now deletes package files from storage account for stale packages along with metadata records. - known_issues: - - The {% data variables.product.prodname_registry %} npm registry no longer returns a time value in metadata responses. This was done to allow for substantial performance improvements. We continue to have all the data necessary to return a time value as part of the metadata response and will resume returning this value in the future once we have solved the existing performance issues. - - 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. - - If {% data variables.product.prodname_actions %} is enabled for {% data variables.product.prodname_ghe_server %}, teardown of a replica node with `ghe-repl-teardown` will succeed, but may return `ERROR:Running migrations`. - - Resource limits that are specific to processing pre-receive hooks may cause some pre-receive hooks to fail. diff --git a/data/release-notes/enterprise-server/3-1/12.yml b/data/release-notes/enterprise-server/3-1/12.yml deleted file mode 100644 index feb0161f06..0000000000 --- a/data/release-notes/enterprise-server/3-1/12.yml +++ /dev/null @@ -1,24 +0,0 @@ -date: '2021-11-23' -sections: - security_fixes: - - Packages have been updated to the latest security versions. - bugs: - - Running `ghe-repl-start` or `ghe-repl-status` would sometimes return errors connecting to the database when GitHub Actions was enabled. - - Pre-receive hooks would fail due to undefined `PATH`. - - 'Running `ghe-repl-setup` would return an error: `cannot create directory /data/user/elasticsearch: File exists` if the instance had previously been configured as a replica.' - - 'After setting up a high availability replica, `ghe-repl-status` included an error in the output: `unexpected unclosed action in command`.' - - In large cluster environments, the authentication backend could be unavailable on a subset of frontend nodes. - - Some critical services may not have been available on backend nodes in GHES Cluster. - changes: - - An additional outer layer of `gzip` compression when creating a cluster support bundle with `ghe-cluster-suport-bundle` is now turned off by default. This outer compression can optionally be applied with the `ghe-cluster-suport-bundle -c` command line option. - - We have added extra text to the admin console to remind users about the mobile apps' data collection for experience improvement purposes. - - The {% data variables.product.prodname_github_connect %} data connection record now includes a list of enabled {% data variables.product.prodname_github_connect %} features. [Updated 2021-12-09] - known_issues: - - The {% data variables.product.prodname_registry %} npm registry no longer returns a time value in metadata responses. This was done to allow for substantial performance improvements. We continue to have all the data necessary to return a time value as part of the metadata response and will resume returning this value in the future once we have solved the existing performance issues. - - 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. - - If {% data variables.product.prodname_actions %} is enabled for {% data variables.product.prodname_ghe_server %}, teardown of a replica node with `ghe-repl-teardown` will succeed, but may return `ERROR:Running migrations`. - - Resource limits that are specific to processing pre-receive hooks may cause some pre-receive hooks to fail. diff --git a/data/release-notes/enterprise-server/3-1/13.yml b/data/release-notes/enterprise-server/3-1/13.yml deleted file mode 100644 index 19a568a849..0000000000 --- a/data/release-notes/enterprise-server/3-1/13.yml +++ /dev/null @@ -1,23 +0,0 @@ -date: '2021-12-07' -sections: - security_fixes: - - Support bundles could include sensitive files if they met a specific set of conditions. - - A UI misrepresentation vulnerability was identified in GitHub Enterprise Server that allowed more permissions to be granted during a GitHub App's user-authorization web flow than was displayed to the user during approval. This vulnerability affected all versions of GitHub Enterprise Server prior to 3.3 and was fixed in versions 3.2.5, 3.1.13, 3.0.21. This vulnerability was reported via the GitHub Bug Bounty program and has been assigned [CVE-2021-41598](https://www.cve.org/CVERecord?id=CVE-2021-41598). - - A remote code execution vulnerability was identified in GitHub Enterprise Server that could be exploited when building a GitHub Pages site. This vulnerability affected all versions of GitHub Enterprise Server prior to 3.3 and was fixed in versions 3.0.21, 3.1.13, 3.2.5. This vulnerability was reported via the GitHub Bug Bounty program and has been assigned [CVE-2021-41599](https://www.cve.org/CVERecord?id=CVE-2021-41599). Updated February 17, 2022 - bugs: - - Running `ghe-config-apply` could sometimes fail because of permission issues in `/data/user/tmp/pages`. - - A misconfiguration in the Management Console caused scheduling errors. - - Docker would hold log files open after a log rotation. - - GraphQL requests did not set the GITHUB_USER_IP variable in pre-receive hook environments. - changes: - - Clarifies explanation of Actions path-style in documentation. - - Updates support contact URLs to use the current support site, support.github.com. - known_issues: - - The {% data variables.product.prodname_registry %} npm registry no longer returns a time value in metadata responses. This was done to allow for substantial performance improvements. We continue to have all the data necessary to return a time value as part of the metadata response and will resume returning this value in the future once we have solved the existing performance issues. - - 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. - - If {% data variables.product.prodname_actions %} is enabled for {% data variables.product.prodname_ghe_server %}, teardown of a replica node with `ghe-repl-teardown` will succeed, but may return `ERROR:Running migrations`. - - Resource limits that are specific to processing pre-receive hooks may cause some pre-receive hooks to fail. diff --git a/data/release-notes/enterprise-server/3-1/14.yml b/data/release-notes/enterprise-server/3-1/14.yml deleted file mode 100644 index 5a7f55939a..0000000000 --- a/data/release-notes/enterprise-server/3-1/14.yml +++ /dev/null @@ -1,14 +0,0 @@ -date: '2021-12-13' -sections: - security_fixes: - - '{% octicon "alert" aria-label="The alert icon" %} **Critical:** A remote code execution vulnerability in the Log4j library, identified as [CVE-2021-44228](https://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2021-44228), affected all versions of {% data variables.product.prodname_ghe_server %} prior to 3.3.1. The Log4j library is used in an open source service running on the {% data variables.product.prodname_ghe_server %} instance. This vulnerability was fixed in {% data variables.product.prodname_ghe_server %} versions 3.0.22, 3.1.14, 3.2.6, and 3.3.1. For more information, please see [this post](https://github.blog/2021-12-13-githubs-response-to-log4j-vulnerability-cve-2021-44228/) on the GitHub Blog.' - - '**December 17, 2021 update**: The fixes in place for this release also mitigate [CVE-2021-45046](https://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2021-45046), which was published after this release. No additional upgrade for {% data variables.product.prodname_ghe_server %} is required to mitigate both CVE-2021-44228 and CVE-2021-45046.' - known_issues: - - The {% data variables.product.prodname_registry %} npm registry no longer returns a time value in metadata responses. This was done to allow for substantial performance improvements. We continue to have all the data necessary to return a time value as part of the metadata response and will resume returning this value in the future once we have solved the existing performance issues. - - 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. - - If {% data variables.product.prodname_actions %} is enabled for {% data variables.product.prodname_ghe_server %}, teardown of a replica node with `ghe-repl-teardown` will succeed, but may return `ERROR:Running migrations`. - - Resource limits that are specific to processing pre-receive hooks may cause some pre-receive hooks to fail. diff --git a/data/release-notes/enterprise-server/3-1/15.yml b/data/release-notes/enterprise-server/3-1/15.yml deleted file mode 100644 index 533cd364d8..0000000000 --- a/data/release-notes/enterprise-server/3-1/15.yml +++ /dev/null @@ -1,21 +0,0 @@ -date: '2022-01-18' -sections: - security_fixes: - - 'Packages have been updated to the latest security versions. In these updates, Log4j has been updated to version 2.17.1. Note: previous mitigations released in 3.3.1, 3.2.6, 3.1.14, and 3.0.22 are sufficient to address the impact of CVE-2021-44228, CVE-2021-45046, CVE-2021-45105, and CVE-2021-44832 in these versions of GitHub Enterprise Server.' - - Sanitize more secrets in the generated support bundles - - Packages have been updated to the latest security versions. - bugs: - - Running `ghe-config-apply` could sometimes fail because of permission issues in `/data/user/tmp/pages`. - - The save button in management console was unreachable by scrolling in lower resolution browsers. - - IOPS and Storage Traffic monitoring graphs were not updating after collectd version upgrade. - - Some webhook related jobs could generated large amount of logs. - - The repository permissions to the user returned by the `/repos` API would not return the full list. - known_issues: - - The {% data variables.product.prodname_registry %} npm registry no longer returns a time value in metadata responses. This was done to allow for substantial performance improvements. We continue to have all the data necessary to return a time value as part of the metadata response and will resume returning this value in the future once we have solved the existing performance issues. - - 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. - - If {% data variables.product.prodname_actions %} is enabled for {% data variables.product.prodname_ghe_server %}, teardown of a replica node with `ghe-repl-teardown` will succeed, but may return `ERROR:Running migrations`. - - Resource limits that are specific to processing pre-receive hooks may cause some pre-receive hooks to fail. diff --git a/data/release-notes/enterprise-server/3-1/16.yml b/data/release-notes/enterprise-server/3-1/16.yml deleted file mode 100644 index 7fd3cbeeed..0000000000 --- a/data/release-notes/enterprise-server/3-1/16.yml +++ /dev/null @@ -1,24 +0,0 @@ -date: '2022-02-01' -sections: - security_fixes: - - Packages have been updated to the latest security versions. - bugs: - - Pages would become unavailable following a MySQL secret rotation until `nginx` was manually restarted. - - When setting the maintenance schedule with a ISO 8601 date, the actual scheduled time wouldn't match due to the timezone not being transformed to UTC. - - Spurious error messages concerning the `cloud-config.service` would be output to the console. - - The version number would not be correctly updated after a installing a hotpatch using `ghe-cluster-each`. - - Webhook table cleanup jobs could run simultaneously, causing resource contention and increasing job run time. - - When using CAS authentication and the "Reactivate suspended users" option was enabled, suspended users were not automatically reactivated. - - The ability to limit email-based notifications to users with emails on a verified or approved domain did not work correctly. - - Several documentation links resulted in a 404 Not Found error. - changes: - - The GitHub Connect data connection record now includes a count of the number of active and dormant users and the configured dormancy period. - known_issues: - - The {% data variables.product.prodname_registry %} npm registry no longer returns a time value in metadata responses. This was done to allow for substantial performance improvements. We continue to have all the data necessary to return a time value as part of the metadata response and will resume returning this value in the future once we have solved the existing performance issues. - - 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. - - If {% data variables.product.prodname_actions %} is enabled for {% data variables.product.prodname_ghe_server %}, teardown of a replica node with `ghe-repl-teardown` will succeed, but may return `ERROR:Running migrations`. - - Resource limits that are specific to processing pre-receive hooks may cause some pre-receive hooks to fail. diff --git a/data/release-notes/enterprise-server/3-1/17.yml b/data/release-notes/enterprise-server/3-1/17.yml deleted file mode 100644 index d49abec3b9..0000000000 --- a/data/release-notes/enterprise-server/3-1/17.yml +++ /dev/null @@ -1,15 +0,0 @@ -date: '2022-02-17' -sections: - security_fixes: - - Packages have been updated to the latest security versions. - bugs: - - Fixes SystemStackError (stack too deep) when getting more than 2^16 keys from memcached. - known_issues: - - The {% data variables.product.prodname_registry %} npm registry no longer returns a time value in metadata responses. This was done to allow for substantial performance improvements. We continue to have all the data necessary to return a time value as part of the metadata response and will resume returning this value in the future once we have solved the existing performance issues. - - 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. - - If {% data variables.product.prodname_actions %} is enabled for {% data variables.product.prodname_ghe_server %}, teardown of a replica node with `ghe-repl-teardown` will succeed, but may return `ERROR:Running migrations`. - - Resource limits that are specific to processing pre-receive hooks may cause some pre-receive hooks to fail. diff --git a/data/release-notes/enterprise-server/3-1/18.yml b/data/release-notes/enterprise-server/3-1/18.yml deleted file mode 100644 index aea88e5c50..0000000000 --- a/data/release-notes/enterprise-server/3-1/18.yml +++ /dev/null @@ -1,16 +0,0 @@ -date: '2022-03-01' -sections: - security_fixes: - - "HIGH: An integer overflow vulnerability was identified in GitHub's markdown parser that could potentially lead to information leaks and RCE. This vulnerability was reported through the GitHub Bug Bounty program by Felix Wilhelm of Google's Project Zero and has been assigned CVE-2022-24724." - bugs: - - Upgrades could sometimes fail if a high-availability replica's clock was out of sync with the primary. - - OAuth Applications created after September 1st, 2020 were not able to use the [Check an Authorization](https://docs.github.com/en/enterprise-server@3.1/rest/reference/apps#check-an-authorization) API endpoint. - known_issues: - - The {% data variables.product.prodname_registry %} npm registry no longer returns a time value in metadata responses. This was done to allow for substantial performance improvements. We continue to have all the data necessary to return a time value as part of the metadata response and will resume returning this value in the future once we have solved the existing performance issues. - - 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. - - If {% data variables.product.prodname_actions %} is enabled for {% data variables.product.prodname_ghe_server %}, teardown of a replica node with `ghe-repl-teardown` will succeed, but may return `ERROR:Running migrations`. - - Resource limits that are specific to processing pre-receive hooks may cause some pre-receive hooks to fail. diff --git a/data/release-notes/enterprise-server/3-1/19.yml b/data/release-notes/enterprise-server/3-1/19.yml deleted file mode 100644 index d53167b7a5..0000000000 --- a/data/release-notes/enterprise-server/3-1/19.yml +++ /dev/null @@ -1,41 +0,0 @@ -date: '2022-04-04' -sections: - security_fixes: - - 'MEDIUM: A path traversal vulnerability was identified in {% data variables.product.prodname_ghe_server %} Management Console that allowed the bypass of CSRF protections. This vulnerability affected all versions of {% data variables.product.prodname_ghe_server %} prior to 3.5 and was fixed in versions 3.1.19, 3.2.11, 3.3.6, 3.4.1. This vulnerability was reported via the {% data variables.product.prodname_dotcom %} Bug Bounty program and has been assigned CVE-2022-23732.' - - 'MEDIUM: An integer overflow vulnerability was identified in the 1.x branch and the 2.x branch of `yajil` which leads to subsequent heap memory corruption when dealing with large (~2GB) inputs. This vulnerability was reported internally and has been assigned CVE-2022-24795. ' - - Support bundles could include sensitive files if {% data variables.product.prodname_actions %} was enabled. - - Packages have been updated to the latest security versions. - bugs: - - The options to enable `TLS 1.0` and `TLS 1.1` in the Privacy settings of the Management Console were shown, although removal of those protocol versions occurred in an earlier release. - - In a HA environment, configuring MSSQL replication could require additional manual steps after enabling {% data variables.product.prodname_actions %} for the first time. - - A subset of internal configuration files are more reliably updated after a hotpatch. - - The `ghe-run-migrations` script would sometimes fail to generate temporary certificate names correctly. - - In a cluster environment, Git LFS operations could fail with failed internal API calls that crossed multiple web nodes. - - Pre-receive hooks that used `gpg --import` timed out due to insufficient `syscall` privileges. - - In some cluster topologies, webhook delivery information was not available. - - In HA configurations, tearing down a replica would fail if {% data variables.product.prodname_actions %} had previously been enabled. - - Elasticsearch health checks would not allow a yellow cluster status when running migrations. - - Organizations created as a result of a user transforming their user account into an organization were not added to the global enterprise account. - - When using `ghe-migrator` or exporting from {% data variables.product.prodname_dotcom_the_website %}, a long-running export would fail when data was deleted mid-export. - - Links to inaccessible pages were removed. - - Adding a team as a reviewer to a pull request would sometimes show the incorrect number of members on that team. - - A large number of dormant users could cause a {% data variables.product.prodname_github_connect %} configuration to fail. - - The "Feature & beta enrollments" page in the Site admin web UI was incorrectly available. - - The "Site admin mode" link in the site footer did not change state when clicked. - changes: - - Memcached connection limits were increased to better accommodate large cluster topologies. - - More effectively identify and delete webhook logs that are outside of the webhook log retention window. - - The Dependency Graph API previously ran with a statically defined port. - - The default shard counts for cluster-related Elasticsearch shard settings have been updated. - - The “Triage” and “Maintain” team roles are preserved during repository migrations. - - '`NotProcessedError` exceptions were occurring unnecessarily.' - - Performance has been improved for web requests made by enterprise owners. - known_issues: - - The {% data variables.product.prodname_registry %} npm registry no longer returns a time value in metadata responses. This was done to allow for substantial performance improvements. We continue to have all the data necessary to return a time value as part of the metadata response and will resume returning this value in the future once we have solved the existing performance issues. - - On a freshly set up {% data variables.product.prodname_ghe_server %} instance without any users, an attacker could create the first admin user. - - Custom firewall rules are removed during the upgrade process. - - Git LFS tracked files [uploaded through the web interface](https://github.com/blog/2105-upload-files-to-your-repositories) are incorrectly added directly to the repository. - - Issues cannot be closed if they contain a permalink to a blob in the same repository, where the blob's file path is longer than 255 characters. - - When "Users can search GitHub.com" is enabled with {% data variables.product.prodname_github_connect %}, issues in private and internal repositories are not included in {% data variables.product.prodname_dotcom_the_website %} search results. - - If {% data variables.product.prodname_actions %} is enabled for {% data variables.product.prodname_ghe_server %}, teardown of a replica node with `ghe-repl-teardown` will succeed, but may return `ERROR:Running migrations`. - - Resource limits that are specific to processing pre-receive hooks may cause some pre-receive hooks to fail. diff --git a/data/release-notes/enterprise-server/3-1/2.yml b/data/release-notes/enterprise-server/3-1/2.yml deleted file mode 100644 index 015a7300ab..0000000000 --- a/data/release-notes/enterprise-server/3-1/2.yml +++ /dev/null @@ -1,26 +0,0 @@ -date: '2021-06-24' -sections: - security_fixes: - - Packages have been updated to the latest security versions. - bugs: - - A large number of `gauge-dependency-graph-api-dispatch_dispatch` metrics could accumulate in the Management Console. - - The sshd service would sometimes fail to start on instances running on Google Cloud Platform. - - Old upgrade files would persist on the user disk, sometimes resulting in out of space conditions. - - '`gh-migrator` displayed an incorrect path to its log output.' - - An export archive would silently fail to import pull requests if they contained review requests from teams not present in the archive. - changes: - - Update the {% data variables.product.prodname_actions %} Runner version in GHES 3.1 to [v2.278.0](https://github.com/actions/runner/releases/tag/v2.278.0) - known_issues: - - The {% data variables.product.prodname_registry %} npm registry no longer returns a time value in metadata responses. This was done to allow for substantial performance improvements. We continue to have all the data necessary to return a time value as part of the metadata response and will resume returning this value in the future once we have solved the existing performance issues. - - 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. - - | - 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" - ``` - - If {% data variables.product.prodname_actions %} is enabled for {% data variables.product.prodname_ghe_server %}, teardown of a replica node with `ghe-repl-teardown` will succeed, but may return `ERROR:Running migrations`. - - Resource limits that are specific to processing pre-receive hooks may cause some pre-receive hooks to fail. diff --git a/data/release-notes/enterprise-server/3-1/20.yml b/data/release-notes/enterprise-server/3-1/20.yml deleted file mode 100644 index d26167604c..0000000000 --- a/data/release-notes/enterprise-server/3-1/20.yml +++ /dev/null @@ -1,22 +0,0 @@ -date: '2022-04-20' -sections: - security_fixes: - - Packages have been updated to the latest security versions. - bugs: - - Upgrading the nodes in a high availability pair with an upgrade package could cause Elasticsearch to enter an inconsistent state in some cases. - - In some cluster topologies, the command line utilities `ghe-spokesctl` and `ghe-btop` failed to run. - - Elasticsearch indices could be duplicated during a package upgrade, due to an `elasticsearch-upgrade` service running multiple times in parallel. - - The `maint_host_low` job queues were not processed, resulting in some maintenance tasks failing to run. - - When converting a user account to an organization, if the user account was an owner of the {% data variables.product.prodname_ghe_server %} enterprise account, the converted organization would incorrectly appear in the enterprise owner list. - - Creating an impersonation OAuth token using the Enterprise Administration REST API resulted in an error when an integration matching the OAuth Application ID already existed. - changes: - - When attempting to cache a value larger than the maximum allowed in Memcached, an error was raised however the key was not reported. - known_issues: - - The {% data variables.product.prodname_registry %} npm registry no longer returns a time value in metadata responses. This was done to allow for substantial performance improvements. We continue to have all the data necessary to return a time value as part of the metadata response and will resume returning this value in the future once we have solved the existing performance issues. - - On a freshly set up {% data variables.product.prodname_ghe_server %} instance without any users, an attacker could create the first admin user. - - Custom firewall rules are removed during the upgrade process. - - Git LFS tracked files [uploaded through the web interface](https://github.com/blog/2105-upload-files-to-your-repositories) are incorrectly added directly to the repository. - - Issues cannot be closed if they contain a permalink to a blob in the same repository, where the blob's file path is longer than 255 characters. - - When "Users can search GitHub.com" is enabled with {% data variables.product.prodname_github_connect %}, issues in private and internal repositories are not included in {% data variables.product.prodname_dotcom_the_website %} search results. - - If {% data variables.product.prodname_actions %} is enabled for {% data variables.product.prodname_ghe_server %}, teardown of a replica node with `ghe-repl-teardown` will succeed, but may return `ERROR:Running migrations`. - - Resource limits that are specific to processing pre-receive hooks may cause some pre-receive hooks to fail. diff --git a/data/release-notes/enterprise-server/3-1/21.yml b/data/release-notes/enterprise-server/3-1/21.yml deleted file mode 100644 index fae05e4fc2..0000000000 --- a/data/release-notes/enterprise-server/3-1/21.yml +++ /dev/null @@ -1,25 +0,0 @@ -date: '2022-05-17' -sections: - security_fixes: - - '**MEDIUM:** A security issue in nginx resolver was identified, where an attacker who could forge UDP packets from the DNS server could cause 1-byte memory overwrite, resulting in worker process crashes or other potentially damaging impacts. The vulnerability has been assigned [CVE-2021-23017](https://nvd.nist.gov/vuln/detail/CVE-2021-23017).' - - Updated the `actions/checkout@v2` and `actions/checkout@v3` actions to address new vulnerabilities announced in the [Git security enforcement blog post](https://github.blog/2022-04-12-git-security-vulnerability-announced/). - - Packages have been updated to the latest security versions. - bugs: - - In some cluster topologies, the `ghe-cluster-status` command left behind empty directories in `/tmp`. - - SNMP incorrectly logged a high number of `Cannot statfs` error messages to syslog. - - For instances configured with SAML authentication and built-in fallback enabled, built-in users would get stuck in a “login” loop when attempting to sign in from the page generated after logging out. - - When using SAML encrypted assertions, some assertions were not correctly marking SSH keys as verified. - - 'The Releases page would return a 500 error when the repository has tags that contain non-ASCII characters. [Updated: 2022-06-10]' - changes: - - In high availability configurations, clarify that the replication overview page in the Management Console only displays the current replication configuration, not the current replication status. - - When enabling {% data variables.product.prodname_registry %}, clarify that using a Shared Access Signature (SAS) token as connection string is not supported. - - Support bundles now include the row count of tables stored in MySQL. - known_issues: - - The {% data variables.product.prodname_registry %} npm registry no longer returns a time value in metadata responses. This was done to allow for substantial performance improvements. We continue to have all the data necessary to return a time value as part of the metadata response and will resume returning this value in the future once we have solved the existing performance issues. - - On a freshly set up {% data variables.product.prodname_ghe_server %} instance without any users, an attacker could create the first admin user. - - Custom firewall rules are removed during the upgrade process. - - Git LFS tracked files [uploaded through the web interface](https://github.com/blog/2105-upload-files-to-your-repositories) are incorrectly added directly to the repository. - - Issues cannot be closed if they contain a permalink to a blob in the same repository, where the blob's file path is longer than 255 characters. - - When "Users can search GitHub.com" is enabled with {% data variables.product.prodname_github_connect %}, issues in private and internal repositories are not included in {% data variables.product.prodname_dotcom_the_website %} search results. - - If {% data variables.product.prodname_actions %} is enabled for {% data variables.product.prodname_ghe_server %}, teardown of a replica node with `ghe-repl-teardown` will succeed, but may return `ERROR:Running migrations`. - - Resource limits that are specific to processing pre-receive hooks may cause some pre-receive hooks to fail. diff --git a/data/release-notes/enterprise-server/3-1/22.yml b/data/release-notes/enterprise-server/3-1/22.yml deleted file mode 100644 index d37c2da9e6..0000000000 --- a/data/release-notes/enterprise-server/3-1/22.yml +++ /dev/null @@ -1,20 +0,0 @@ -date: '2022-06-09' -sections: - security_fixes: - - Packages have been updated to the latest security versions. - bugs: - - An internal script to validate hostnames in the {% data variables.product.prodname_ghe_server %} configuration file would return an error if the hostname string started with a "." (period character). - - In HA configurations where the primary node's hostname was longer than 60 characters, MySQL would fail to be configured. - - The calculation of "maximum committers across entire instance" reported in the site admin dashboard was incorrect. - - An incorrect database entry for repository replicas caused database corruption when performing a restore using {% data variables.product.prodname_enterprise_backup_utilities %}. - changes: - - In HA configurations where Elasticsearch reported a valid yellow status, changes introduced in a previous fix would block the `ghe-repl-stop` command and not allow replication to be stopped. Using `ghe-repo-stop --force` will now force Elasticsearch to stop when the service is in a normal or valid yellow status. - known_issues: - - The {% data variables.product.prodname_registry %} npm registry no longer returns a time value in metadata responses. This was done to allow for substantial performance improvements. We continue to have all the data necessary to return a time value as part of the metadata response and will resume returning this value in the future once we have solved the existing performance issues. - - On a freshly set up {% data variables.product.prodname_ghe_server %} instance without any users, an attacker could create the first admin user. - - Custom firewall rules are removed during the upgrade process. - - Git LFS tracked files [uploaded through the web interface](https://github.com/blog/2105-upload-files-to-your-repositories) are incorrectly added directly to the repository. - - Issues cannot be closed if they contain a permalink to a blob in the same repository, where the blob's file path is longer than 255 characters. - - When "Users can search GitHub.com" is enabled with {% data variables.product.prodname_github_connect %}, issues in private and internal repositories are not included in {% data variables.product.prodname_dotcom_the_website %} search results. - - If {% data variables.product.prodname_actions %} is enabled for {% data variables.product.prodname_ghe_server %}, teardown of a replica node with `ghe-repl-teardown` will succeed, but may return `ERROR:Running migrations`. - - Resource limits that are specific to processing pre-receive hooks may cause some pre-receive hooks to fail. diff --git a/data/release-notes/enterprise-server/3-1/3.yml b/data/release-notes/enterprise-server/3-1/3.yml deleted file mode 100644 index f93c61a388..0000000000 --- a/data/release-notes/enterprise-server/3-1/3.yml +++ /dev/null @@ -1,27 +0,0 @@ -date: '2021-07-14' -sections: - security_fixes: - - '**HIGH:** A path traversal vulnerability was identified in GitHub Enterprise Server that could be exploited when building a GitHub Pages site. User-controlled configuration options used by GitHub Pages were not sufficiently restricted and made it possible to read files on the GitHub Enterprise Server instance. To exploit this vulnerability, an attacker would need permission to create and build a GitHub Pages site on the GitHub Enterprise Server instance. This vulnerability affected all versions of GitHub Enterprise Server prior to 3.1.3 and has been assigned CVE-2021-22867. This vulnerability was reported via the GitHub Bug Bounty program.' - - Packages have been updated to the latest security versions. - bugs: - - SAML expiration date variable was not configurable. - - Application services would fail their health checks during config apply before they could enter a healthy state. - - '`ghe-cluster-config-node-init` would fail during cluster setup if HTTP proxy is enabled.' - - Pre-receive hooks could encounter an error `Failed to resolve full path of the current executable` due to `/proc` not being mounted on the container. - - Collectd would not resolve the forwarding destination hostname after the initial startup. - - The job that purged stale deleted repositories could fail to make progress if some of those repositories were protected from deletion by legal holds. - - Background jobs were being queued to the `spam` queue which were not being processed. - - The preferred merge method would be reset when retrying after a failed PR merge. - - Git pushes could result in a 500 Internal Server Error during the user reconciliation process on instances using LDAP authentication mode. - - 'After upgrading from 3.0.x to 3.1.x, in some cases GitHub Actions would fail with an error: `An unexpected error occurred when executing this workflow.`' - changes: - - Improved the efficiency of config apply by skipping IP allow firewall rules that had not changed, which saved significant time on large clusters. - known_issues: - - The {% data variables.product.prodname_registry %} npm registry no longer returns a time value in metadata responses. This was done to allow for substantial performance improvements. We continue to have all the data necessary to return a time value as part of the metadata response and will resume returning this value in the future once we have solved the existing performance issues. - - 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. - - If {% data variables.product.prodname_actions %} is enabled for {% data variables.product.prodname_ghe_server %}, teardown of a replica node with `ghe-repl-teardown` will succeed, but may return `ERROR:Running migrations`. - - Resource limits that are specific to processing pre-receive hooks may cause some pre-receive hooks to fail. diff --git a/data/release-notes/enterprise-server/3-1/4.yml b/data/release-notes/enterprise-server/3-1/4.yml deleted file mode 100644 index 4846e1652c..0000000000 --- a/data/release-notes/enterprise-server/3-1/4.yml +++ /dev/null @@ -1,36 +0,0 @@ -date: '2021-07-27' -sections: - security_fixes: - - Packages have been updated to the latest security versions. - bugs: - - The counts on packages pages were not being incremented when a package was downloaded. - - '`ghe-config-apply` would timeout, ask for a prompt or fail for a customer that had {% data variables.product.prodname_secret_scanning %} enabled, and had either disabled or never enabled {% data variables.product.prodname_actions %} on their instance.' - - Log files were not reopened after rotation in some cases leading to high disk space usage on instances with high uptime. - - Upgrade could fail from older version of {% data variables.product.prodname_ghe_server %} due to a missing job in {% data variables.product.prodname_actions %}. - - 'Custom pre-receive hooks could lead to an error like `error: object directory /data/user/repositories/0/nw/12/34/56/7890/network.git/objects does not exist; check .git/objects/info/alternates`.' - - Unauthenticated HTTP proxy for the pages containers build was not supported for any users that use HTTP proxies. - - A significant number of 503 errors were logged every time a user visited a repository's `/settings` page if the dependency graph was not enabled. - - Internal repositories were only returned when a user had affiliations with the repository through a team or through collaborator status, or queried with the `?type=internal` parameter. - - Failed background jobs had unlimited retries which could cause large queue depths. - - A significant number of 503 errors were being created if the scheduled job to sync vulnerabilities with GitHub.com attempted to run when dependency graph was not enabled and content analysis was enabled. - - | - When {% data variables.product.prodname_actions %} is enabled without running regular scheduled backups, the MSSQL transaction log could grow unbounded and can consume all available space on the appliance's data disk, causing a possible outage. - - If you have configured regularly scheduled MSSQL backups, no further actions is required. Otherwise, if you have {% data variables.product.prodname_actions %} previously enabled, run the following commands after installing this patch. - - ``` - ghe-actions-console -s Mps -c 'Update-Service -Force' - ghe-actions-console -s Token -c 'Update-Service -Force' - ghe-actions-console -s Actions -c 'Update-Service -Force' - ``` - changes: - - The logs for `babeld` now include a `cmd` field for HTTP ref advertisement requests instead of only including it during the negotiation requests. - known_issues: - - The {% data variables.product.prodname_registry %} npm registry no longer returns a time value in metadata responses. This was done to allow for substantial performance improvements. We continue to have all the data necessary to return a time value as part of the metadata response and will resume returning this value in the future once we have solved the existing performance issues. - - 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. - - If {% data variables.product.prodname_actions %} is enabled for {% data variables.product.prodname_ghe_server %}, teardown of a replica node with `ghe-repl-teardown` will succeed, but may return `ERROR:Running migrations`. - - Resource limits that are specific to processing pre-receive hooks may cause some pre-receive hooks to fail. diff --git a/data/release-notes/enterprise-server/3-1/5.yml b/data/release-notes/enterprise-server/3-1/5.yml deleted file mode 100644 index d5e39f6448..0000000000 --- a/data/release-notes/enterprise-server/3-1/5.yml +++ /dev/null @@ -1,20 +0,0 @@ -date: '2021-08-10' -sections: - bugs: - - 'Custom pre-receive hooks that used a bash subshell would return an error: `No such file or directory`.' - - When GitHub Actions is enabled without running regular scheduled backups the MSSQL Transaction Log could grow unbounded and can consume all available space on the appliance's Data Disk causing a possible outage. - - Unnecessary database logging consumed a large amount of disk space on instances with heavy LFS usage. - - Audit log entries for changes made to "Repository creation" organization settings were inaccurate. - - Excessive logging of `ActionController::UnknownFormat` exceptions caused unnecessary disk usage. - - "LDAP `group_dn` values longer than 255 characters would result in errors being logged: `Data truncated for column 'group_dn' at row 1`." - changes: - - Abuse rate limits are now called Secondary rate limits, since the behavior they limit is not always abusive. - known_issues: - - The {% data variables.product.prodname_registry %} npm registry no longer returns a time value in metadata responses. This was done to allow for substantial performance improvements. We continue to have all the data necessary to return a time value as part of the metadata response and will resume returning this value in the future once we have solved the existing performance issues. - - 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. - - If {% data variables.product.prodname_actions %} is enabled for {% data variables.product.prodname_ghe_server %}, teardown of a replica node with `ghe-repl-teardown` will succeed, but may return `ERROR:Running migrations`. - - Resource limits that are specific to processing pre-receive hooks may cause some pre-receive hooks to fail. diff --git a/data/release-notes/enterprise-server/3-1/6.yml b/data/release-notes/enterprise-server/3-1/6.yml deleted file mode 100644 index 7bee782a80..0000000000 --- a/data/release-notes/enterprise-server/3-1/6.yml +++ /dev/null @@ -1,23 +0,0 @@ -date: '2021-08-24' -sections: - security_fixes: - - Packages have been updated to the latest security versions. - bugs: - - Attaching very large images or animated GIFs to images or pull requests would fail. - - Journald messages related to automatic updates (`Adding h/m/s random time.`) were logged to syslog. - - Custom pre-receive hooks that created named pipes (FIFOs) would crash or hang, resulting in a timeout error. - - Adding filters to the audit log advanced search page did not populate the query text box in real-time with the correct facet prefix and value. - - Git hooks to the internal API that result in failing requests returned the exception `undefined method body for "success":String (NoMethodError)` instead of returning an explicit `nil`. - - When an integration was removed, it was possible for an unrelated OAuth application or integration to also be removed. - - When a mandatory message containing an emoji character was added, attempting to view or change the message would return a 500 Internal Server Error. - changes: - - Adds `triage` and `maintain` to the list of permissions returned by the REST API. - known_issues: - - The {% data variables.product.prodname_registry %} npm registry no longer returns a time value in metadata responses. This was done to allow for substantial performance improvements. We continue to have all the data necessary to return a time value as part of the metadata response and will resume returning this value in the future once we have solved the existing performance issues. - - 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. - - If {% data variables.product.prodname_actions %} is enabled for {% data variables.product.prodname_ghe_server %}, teardown of a replica node with `ghe-repl-teardown` will succeed, but may return `ERROR:Running migrations`. - - Resource limits that are specific to processing pre-receive hooks may cause some pre-receive hooks to fail. diff --git a/data/release-notes/enterprise-server/3-1/7.yml b/data/release-notes/enterprise-server/3-1/7.yml deleted file mode 100644 index 782460c8ca..0000000000 --- a/data/release-notes/enterprise-server/3-1/7.yml +++ /dev/null @@ -1,18 +0,0 @@ -date: '2021-09-07' -sections: - security_fixes: - - Packages have been updated to the latest security versions. - bugs: - - Attempting to tear down a newly-added replica node by specifying its UUID with `ghe-repl-teardown` would fail without reporting an error if replication was not started. - - GitHub Pages builds were being passed through an external proxy if there was one configured. - - Custom pre-receive hooks that created sub-processes would lack a `PATH` variable in their environment, resulting in "No such file or directory" errors. - - MySQL could failover during an upgrade if `mysql-auto-failover` was enabled. - known_issues: - - The {% data variables.product.prodname_registry %} npm registry no longer returns a time value in metadata responses. This was done to allow for substantial performance improvements. We continue to have all the data necessary to return a time value as part of the metadata response and will resume returning this value in the future once we have solved the existing performance issues. - - 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. - - If {% data variables.product.prodname_actions %} is enabled for {% data variables.product.prodname_ghe_server %}, teardown of a replica node with `ghe-repl-teardown` will succeed, but may return `ERROR:Running migrations`. - - Resource limits that are specific to processing pre-receive hooks may cause some pre-receive hooks to fail. diff --git a/data/release-notes/enterprise-server/3-1/8.yml b/data/release-notes/enterprise-server/3-1/8.yml deleted file mode 100644 index 8f2e886f89..0000000000 --- a/data/release-notes/enterprise-server/3-1/8.yml +++ /dev/null @@ -1,20 +0,0 @@ -date: '2021-09-24' -sections: - security_fixes: - - '**HIGH:** A path traversal vulnerability was identified in {% data variables.product.prodname_ghe_server %} that could be exploited when building a {% data variables.product.prodname_pages %} site. User-controlled configuration options used by {% data variables.product.prodname_pages %} were not sufficiently restricted and made it possible to read files on the {% data variables.product.prodname_ghe_server %} instance. To exploit this vulnerability, an attacker would need permission to create and build a {% data variables.product.prodname_pages %} site on the {% data variables.product.prodname_ghe_server %} instance. This vulnerability affected all versions of {% data variables.product.prodname_ghe_server %} prior to 3.1.8 and was fixed in 3.1.8, 3.0.16, and 2.22.22. This is the result of an incomplete fix for CVE-2021-22867. This vulnerability was reported via the GitHub Bug Bounty program and has been assigned CVE-2021-22868. {% comment %} https://github.com/github/pages/pull/3361, https://github.com/github/pages/pull/3357 {% endcomment %}' - - '**MEDIUM:** An improper access control vulnerability in {% data variables.product.prodname_ghe_server %} allowed a workflow job to execute in a self-hosted runner group it should not have had access to. This affects customers using self-hosted runner groups for access control. A repository with access to one enterprise runner group could access all of the enterprise runner groups within the organization because of improper authentication checks during the request. This could cause code to be run unintentionally by the incorrect runner group. This vulnerability affected {% data variables.product.prodname_ghe_server %} versions from 3.0.0 to 3.0.15 and 3.1.0 to 3.1.7 and was fixed in 3.0.16 and 3.1.8 releases. It has been assigned CVE-2021-22869. {% comment %} https://github.com/github/enterprise2/pull/27013 {% endcomment %}' - bugs: - - 'Resque worker counts were displayed incorrectly during maintenance mode. {% comment %} https://github.com/github/enterprise2/pull/26899, https://github.com/github/enterprise2/pull/26883 {% endcomment %}' - - 'Allocated memcached memory could be zero in clustering mode. {% comment %} https://github.com/github/enterprise2/pull/26928, https://github.com/github/enterprise2/pull/26832 {% endcomment %}' - - 'Non-empty binary files displayed an incorrect file type and size on the pull request "Files" tab. {% comment %} https://github.com/github/github/pull/192810, https://github.com/github/github/pull/172284, https://github.com/github/coding/issues/694 {% endcomment %}' - - 'Fixes {% data variables.product.prodname_pages %} builds so they take into account the NO_PROXY setting of the appliance. This is relevant to appliances configured with an HTTP proxy only. (update 2021-09-30) {% comment %} https://github.com/github/pages/pull/3360 {% endcomment %}' - - 'The GitHub Connect configuration of the source instance was always restored to new instances even when the `--config` option for `ghe-restore` was not used. This would lead to a conflict with the GitHub Connect connection and license synchronization if both the source and destination instances were online at the same time. The fix also requires updating backup-utils to 3.2.0 or higher. [updated: 2021-11-18]' - known_issues: - - The {% data variables.product.prodname_registry %} npm registry no longer returns a time value in metadata responses. This was done to allow for substantial performance improvements. We continue to have all the data necessary to return a time value as part of the metadata response and will resume returning this value in the future once we have solved the existing performance issues. - - 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. - - If {% data variables.product.prodname_actions %} is enabled for {% data variables.product.prodname_ghe_server %}, teardown of a replica node with `ghe-repl-teardown` will succeed, but may return `ERROR:Running migrations`. - - Resource limits that are specific to processing pre-receive hooks may cause some pre-receive hooks to fail. diff --git a/data/release-notes/enterprise-server/3-1/9.yml b/data/release-notes/enterprise-server/3-1/9.yml deleted file mode 100644 index be28140c54..0000000000 --- a/data/release-notes/enterprise-server/3-1/9.yml +++ /dev/null @@ -1,28 +0,0 @@ -date: '2021-10-12' -sections: - security_fixes: - - 'Packages have been updated to the latest security versions. {% comment %} https://github.com/github/enterprise2/pull/27035, https://github.com/github/enterprise2/pull/27010 {% endcomment %}' - bugs: - - 'Custom pre-receive hooks could have failed due to too restrictive virtual memory or CPU time limits. {% comment %} https://github.com/github/enterprise2/pull/26972, https://github.com/github/enterprise2/pull/26955 {% endcomment %}' - - 'Attempting to wipe all existing configuration settings with `ghe-cleanup-settings` failed to restart the Management Console service. {% comment %} https://github.com/github/enterprise2/pull/26987, https://github.com/github/enterprise2/pull/26901 {% endcomment %}' - - 'During replication teardown via `ghe-repl-teardown` Memcached failed to be restarted. {% comment %} https://github.com/github/enterprise2/pull/26993, https://github.com/github/enterprise2/pull/26983 {% endcomment %}' - - 'During periods of high load, users would receive HTTP 503 status codes when upstream services failed internal healthchecks. {% comment %} https://github.com/github/enterprise2/pull/27082, https://github.com/github/enterprise2/pull/26999 {% endcomment %}' - - 'With Actions configured, MSSQL replication would fail after restoring from a GitHub Enterprise Backup Utilities snapshot. {% comment %} https://github.com/github/enterprise2/pull/27097, https://github.com/github/enterprise2/pull/26254 {% endcomment %}' - - 'An erroneous `jq` error message may have been displayed when running `ghe-config-apply`. {% comment %} https://github.com/github/enterprise2/pull/27194, https://github.com/github/enterprise2/pull/26784 {% endcomment %}' - - 'Pre-receive hook environments were forbidden from calling the cat command via BusyBox on Alpine. {% comment %} https://github.com/github/enterprise2/pull/27115, https://github.com/github/enterprise2/pull/27094 {% endcomment %}' - - 'The external database password was logged in plaintext. {% comment %} https://github.com/github/enterprise2/pull/27173, https://github.com/github/enterprise2/pull/26413 {% endcomment %}' - - 'Failing over from a primary Cluster datacenter to a secondary Cluster datacenter succeeds, but then failing back over to the original primary Cluster datacenter failed to promote Elasticsearch indicies. {% comment %} https://github.com/github/github/pull/193181, https://github.com/github/github/pull/192447 {% endcomment %}' - - 'The "Import teams" button on the Teams page for an Organization returned an HTTP 404. {% comment %} https://github.com/github/github/pull/193302 {% endcomment %}' - - 'In some cases, GitHub Enterprise Administrators attempting to view the `Dormant users` page received `502 Bad Gateway` or `504 Gateway Timeout` response. {% comment %} https://github.com/github/github/pull/194260, https://github.com/github/github/pull/193609 {% endcomment %}' - - 'Performance was negatively impacted in certain high load situations as a result of the increased number of `SynchronizePullRequestJob` jobs. {% comment %} https://github.com/github/github/pull/195253, https://github.com/github/github/pull/194591 {% endcomment %}' - changes: - - 'More effectively delete Webhook logs that fall out of the Webhook log retention window. {% comment %} https://github.com/github/enterprise2/pull/27158 {% endcomment %}' - known_issues: - - The {% data variables.product.prodname_registry %} npm registry no longer returns a time value in metadata responses. This was done to allow for substantial performance improvements. We continue to have all the data necessary to return a time value as part of the metadata response and will resume returning this value in the future once we have solved the existing performance issues. - - 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. - - If {% data variables.product.prodname_actions %} is enabled for {% data variables.product.prodname_ghe_server %}, teardown of a replica node with `ghe-repl-teardown` will succeed, but may return `ERROR:Running migrations`. - - Resource limits that are specific to processing pre-receive hooks may cause some pre-receive hooks to fail. diff --git a/data/release-notes/enterprise-server/3-2/0-rc1.yml b/data/release-notes/enterprise-server/3-2/0-rc1.yml deleted file mode 100644 index 634366e5e1..0000000000 --- a/data/release-notes/enterprise-server/3-2/0-rc1.yml +++ /dev/null @@ -1,309 +0,0 @@ -date: '2021-09-09' -release_candidate: true -deprecated: true -intro: If {% data variables.location.product_location %} is running a release candidate build, you can't upgrade with a hotpatch. We recommend only running release candidates on test environments. -sections: - features: - - heading: Custom patterns for secret scanning - notes: - # https://github.com/github/releases/issues/1426 - - | - {% data variables.product.prodname_GH_advanced_security %} customers can now specify custom patterns for secret scanning. When a new pattern is specified, secret scanning searches a repository's entire Git history for the pattern, as well as any new commits. - - User defined patterns are in beta for {% data variables.product.prodname_ghe_server %} 3.2. They can be defined at the repository, organization, and enterprise levels. For more information, see "[Defining custom patterns for secret scanning](/code-security/secret-scanning/defining-custom-patterns-for-secret-scanning)." - - - heading: Security overview for Advanced Security (beta) - notes: - # https://github.com/github/releases/issues/1381 - - | - {% data variables.product.prodname_GH_advanced_security %} customers now have an organization-level view of the application security risks detected by {% data variables.product.prodname_code_scanning %}, {% data variables.product.prodname_dependabot %}, and {% data variables.product.prodname_secret_scanning %}. The security overview shows the enablement status of security features on each repository, as well as the number of alerts detected. - - In addition, the security overview lists all {% data variables.product.prodname_secret_scanning %} alerts at the organization level. Similar views for {% data variables.product.prodname_dependabot %} and {% data variables.product.prodname_code_scanning %} alerts are coming in future releases. For more information, see "[About the security overview](/code-security/security-overview/about-the-security-overview)." - - ![Screenshot of security overview](/assets/images/enterprise/3.2/release-notes/security-overview-UI.png) - - - heading: Dependency review (beta) - notes: - # https://github.com/github/releases/issues/1364 - - | - {% data variables.product.prodname_GH_advanced_security %} customers can now see a rich diff of the dependencies changed in a pull request. 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 these dependencies. 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)." - - - heading: GitHub Actions environments - notes: - # https://github.com/github/releases/issues/1308 - - | - Environments, environment protection rules, and environment secrets are now generally available for {% data variables.product.prodname_actions %} on {% data variables.product.product_name %}. For more information, see "[Environments](/actions/reference/environments)." - - ![Environment protection rules](/assets/images/enterprise/3.2/release-notes/actions-environments.png) - - - heading: SSH authentication with security keys - notes: - # https://github.com/github/releases/issues/1276 - - | - SSH authentication using a FIDO2 security key is now supported when you add a `sk-ecdsa-sha2-nistp256@openssh.com` or `sk-ssh-ed25519@openssh.com` SSH key to your account. SSH security keys store secret key material on a separate hardware device that requires verification, such as a tap, to operate. For more information, see "[Generating a new SSH key and adding it to the ssh-agent](/github/authenticating-to-github/connecting-to-github-with-ssh/generating-a-new-ssh-key-and-adding-it-to-the-ssh-agent#generating-a-new-ssh-key-for-a-hardware-security-key)." - - - heading: 'Dark and dark dimmed themes' - notes: - # https://github.com/github/releases/issues/1260 - - | - Dark and dark dimmed themes are now available for the web UI. {% data variables.product.product_name %} will match your system preferences when you haven't set theme preferences in {% data variables.product.product_name %}. You can also choose which themes are active during the day and night. For more information, see "[Managing your theme settings](/github/setting-up-and-managing-your-github-user-account/managing-user-account-settings/managing-your-theme-settings)." - - ![Dark and dark dimmed themes](https://user-images.githubusercontent.com/33528647/114629560-d2231f80-9c86-11eb-9bde-cc301a97040d.gif) - - - heading: 'Approving unverified domains for email notifications' - notes: - # https://github.com/github/releases/issues/1244 - - Domains that are not able to be verified can now be approved for email notification routing. Enterprise and organization owners will be able to approve domains and immediately augment their email notification restriction policy, allowing notifications to be sent to collaborators, consultants, acquisitions, or other partners. For more information, see "[Verifying or approving a domain for your enterprise](/admin/configuration/configuring-your-enterprise/verifying-or-approving-a-domain-for-your-enterprise#about-approval-of-domains)" and "[Restricting email notifications for your enterprise](/admin/policies/enforcing-policies-for-your-enterprise/restricting-email-notifications-for-your-enterprise#restricting-email-notifications-for-your-enterprise-account)." - - - heading: 'Git Credential Manager (GCM) secure credential storage and multi-factor authentication support' - notes: - # https://github.com/github/releases/issues/1406 - - | - Git Credential Manager (GCM) versions 2.0.452 and later now provide security-hardened credential storage and multi-factor authentication support for {% data variables.product.product_name %}. - - GCM with support for {% data variables.product.product_name %} is included with [Git for Windows](https://gitforwindows.org) versions 2.32 and later. GCM is not included with Git for macOS or Linux, but can be installed separately. For more information, see the [latest release](https://github.com/GitCredentialManager/git-credential-manager/releases/) and [installation instructions](https://github.com/GitCredentialManager/git-credential-manager/releases/) in the `GitCredentialManager/git-credential-manager` repository. - - changes: - - heading: Administration Changes - notes: - # https://github.com/github/releases/issues/1309 - - A 'User Agent Referrer Policy' setting has been added to the enterprise settings. This allows an admin to set a stricter `Referrer-Policy` to hide the hostname of a {% data variables.product.prodname_ghe_server %} installation from external sites. The setting is disabled by default and is tracked by audit log events for staff and enterprise owners when enabled or disabled. For more information, see "[Configuring Referrer Policy for your enterprise](/admin/configuration/configuring-your-enterprise/configuring-the-referrer-policy-for-your-enterprise)." - - # https://github.com/github/releases/issues/1515 - - The MySQL health check was changed to use `mysqladmin ping` instead of TCP checks, which removes some unnecessary noise in the MySQL error log. Also, Orchestrator failover checks were improved to prevent unnecessary MySQL failovers when applying cluster config changes. - - # https://github.com/github/releases/issues/1287 - - The Resque service, which supports background job processing, has been replaced with Aqueduct Lite. This change makes the job system easier to manage and should not affect the user experience. For the new administration and debugging commands for Aqueduct, see "[Command-line utilities](/admin/configuration/configuring-your-enterprise/command-line-utilities#ghe-aqueduct)." - - - heading: Token Changes - notes: - # https://github.com/github/releases/issues/1235 - - | - The format of authentication tokens for {% data variables.product.product_name %} has changed. The change affects the format of personal access tokens and access tokens for {% data variables.product.prodname_oauth_apps %}, as well as user-to-server, server-to-server, and refresh tokens for {% data variables.product.prodname_github_apps %}. - - The different token types now have unique identifiable prefixes, which allows for secret scanning to detect the tokens so that you can mitigate the impact of someone accidentally committing a token to a repository. {% data variables.product.company_short %} recommends updating existing tokens as soon as possible. For more information, see "[About authentication to {% data variables.product.prodname_dotcom %}](/github/authenticating-to-github/keeping-your-account-and-data-secure/about-authentication-to-github#githubs-token-formats)" and "[About {% data variables.product.prodname_secret_scanning %}](/code-security/secret-security/about-secret-scanning)." - - - heading: 'Repositories changes' - notes: - # https://github.com/github/releases/issues/1295 - - Repositories on user profiles and organization profiles now support sorting by star count. - - # https://github.com/github/releases/issues/1327 - - When viewing the commit history of a single file, you can now click {% octicon "file-code" aria-label="The code icon" %} to view that file at the selected point in history. - - # https://github.com/github/releases/issues/1254 - - When a submodule is defined with a relative path in {% data variables.location.product_location %}, the submodule is now clickable in the web UI. Clicking the submodule in the web UI will take you to the linked repository. Previously, only submodules with absolute URLs were clickable. This is supported for relative paths for repositories with the same owner that follow the pattern ../REPOSITORY or relative paths for repositories with a different owner that follow the pattern ../OWNER/REPOSITORY. For more information about working with submodules, see [Working with submodules](https://github.blog/2016-02-01-working-with-submodules/) on {% data variables.product.prodname_blog %}. - - # https://github.com/github/releases/issues/1250 - - The web UI can now be used to synchronize an out-of-date branch of a fork with the fork's upstream branch. If there are no merge conflicts between the branches, the branch is updated either by fast-forwarding or by merging from upstream. If there are conflicts, you will be prompted to create a pull request to resolve the conflicts. For more information, see "[Syncing a fork](/github/collaborating-with-pull-requests/working-with-forks/syncing-a-fork#syncing-a-fork-from-the-web-ui)." - - - heading: 'Markdown changes' - notes: - # https://github.com/github/releases/issues/1477 - - 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).' diff --git a/data/release-notes/enterprise-server/3-2/0.yml b/data/release-notes/enterprise-server/3-2/0.yml deleted file mode 100644 index 708b798394..0000000000 --- a/data/release-notes/enterprise-server/3-2/0.yml +++ /dev/null @@ -1,317 +0,0 @@ -date: '2021-09-28' -intro: For upgrade instructions, see "[Upgrading {% data variables.product.prodname_ghe_server %}](/admin/enterprise-management/updating-the-virtual-machine-and-physical-resources/upgrading-github-enterprise-server)." -sections: - features: - - heading: Custom patterns for secret scanning - notes: - # https://github.com/github/releases/issues/1426 - - | - {% data variables.product.prodname_GH_advanced_security %} customers can now specify custom patterns for secret scanning. When a new pattern is specified, secret scanning searches a repository's entire Git history for the pattern, as well as any new commits. - - User defined patterns are in beta for {% data variables.product.prodname_ghe_server %} 3.2. They can be defined at the repository, organization, and enterprise levels. For more information, see "[Defining custom patterns for secret scanning](/code-security/secret-scanning/defining-custom-patterns-for-secret-scanning)." - - - heading: Security overview for Advanced Security (beta) - notes: - # https://github.com/github/releases/issues/1381 - - | - {% data variables.product.prodname_GH_advanced_security %} customers now have an organization-level view of the application security risks detected by {% data variables.product.prodname_code_scanning %}, {% data variables.product.prodname_dependabot %}, and {% data variables.product.prodname_secret_scanning %}. The security overview shows the enablement status of security features on each repository, as well as the number of alerts detected. - - In addition, the security overview lists all {% data variables.product.prodname_secret_scanning %} alerts at the organization level. Similar views for {% data variables.product.prodname_dependabot %} and {% data variables.product.prodname_code_scanning %} alerts are coming in future releases. For more information, see "[About the security overview](/code-security/security-overview/about-the-security-overview)." - - ![Screenshot of security overview](/assets/images/enterprise/3.2/release-notes/security-overview-UI.png) - - - heading: Dependency review (beta) - notes: - # https://github.com/github/releases/issues/1364 - - | - {% data variables.product.prodname_GH_advanced_security %} customers can now see a rich diff of the dependencies changed in a pull request. 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 these dependencies. 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)." - - - heading: GitHub Actions environments - notes: - # https://github.com/github/releases/issues/1308 - - | - Environments, environment protection rules, and environment secrets are now generally available for {% data variables.product.prodname_actions %} on {% data variables.product.product_name %}. For more information, see "[Environments](/actions/reference/environments)." - - ![Environment protection rules](/assets/images/enterprise/3.2/release-notes/actions-environments.png) - - - heading: SSH authentication with security keys - notes: - # https://github.com/github/releases/issues/1276 - - | - SSH authentication using a FIDO2 security key is now supported when you add a `sk-ecdsa-sha2-nistp256@openssh.com` or `sk-ssh-ed25519@openssh.com` SSH key to your account. SSH security keys store secret key material on a separate hardware device that requires verification, such as a tap, to operate. For more information, see "[Generating a new SSH key and adding it to the ssh-agent](/github/authenticating-to-github/connecting-to-github-with-ssh/generating-a-new-ssh-key-and-adding-it-to-the-ssh-agent#generating-a-new-ssh-key-for-a-hardware-security-key)." - - - heading: 'Dark and dark dimmed themes' - notes: - # https://github.com/github/releases/issues/1260 - - | - Dark and dark dimmed themes are now available for the web UI. {% data variables.product.product_name %} will match your system preferences when you haven't set theme preferences in {% data variables.product.product_name %}. You can also choose which themes are active during the day and night. For more information, see "[Managing your theme settings](/github/setting-up-and-managing-your-github-user-account/managing-user-account-settings/managing-your-theme-settings)." - - ![Dark and dark dimmed themes](https://user-images.githubusercontent.com/33528647/114629560-d2231f80-9c86-11eb-9bde-cc301a97040d.gif) - - - heading: 'Approving unverified domains for email notifications' - notes: - # https://github.com/github/releases/issues/1244 - - Domains that are not able to be verified can now be approved for email notification routing. Enterprise and organization owners will be able to approve domains and immediately augment their email notification restriction policy, allowing notifications to be sent to collaborators, consultants, acquisitions, or other partners. For more information, see "[Verifying or approving a domain for your enterprise](/admin/configuration/configuring-your-enterprise/verifying-or-approving-a-domain-for-your-enterprise#about-approval-of-domains)" and "[Restricting email notifications for your enterprise](/admin/policies/enforcing-policies-for-your-enterprise/restricting-email-notifications-for-your-enterprise#restricting-email-notifications-for-your-enterprise-account)." - - - heading: 'Git Credential Manager (GCM) secure credential storage and multi-factor authentication support' - notes: - # https://github.com/github/releases/issues/1406 - - | - Git Credential Manager (GCM) versions 2.0.452 and later now provide security-hardened credential storage and multi-factor authentication support for {% data variables.product.product_name %}. - - GCM with support for {% data variables.product.product_name %} is included with [Git for Windows](https://gitforwindows.org) versions 2.32 and later. GCM is not included with Git for macOS or Linux, but can be installed separately. For more information, see the [latest release](https://github.com/GitCredentialManager/git-credential-manager/releases/) and [installation instructions](https://github.com/GitCredentialManager/git-credential-manager/releases/) in the `GitCredentialManager/git-credential-manager` repository. - - changes: - - heading: Administration Changes - notes: - # https://github.com/github/releases/issues/1309 - - A 'User Agent Referrer Policy' setting has been added to the enterprise settings. This allows an admin to set a stricter `Referrer-Policy` to hide the hostname of a {% data variables.product.prodname_ghe_server %} installation from external sites. The setting is disabled by default and is tracked by audit log events for staff and enterprise owners when enabled or disabled. For more information, see "[Configuring Referrer Policy for your enterprise](/admin/configuration/configuring-your-enterprise/configuring-the-referrer-policy-for-your-enterprise)." - - # https://github.com/github/releases/issues/1515 - - The MySQL health check was changed to use `mysqladmin ping` instead of TCP checks, which removes some unnecessary noise in the MySQL error log. Also, Orchestrator failover checks were improved to prevent unnecessary MySQL failovers when applying cluster config changes. - - # https://github.com/github/releases/issues/1287 - - The Resque service, which supports background job processing, has been replaced with Aqueduct Lite. This change makes the job system easier to manage and should not affect the user experience. For the new administration and debugging commands for Aqueduct, see "[Command-line utilities](/admin/configuration/configuring-your-enterprise/command-line-utilities#ghe-aqueduct)." - - - heading: Token Changes - notes: - # https://github.com/github/releases/issues/1235 - - | - The format of authentication tokens for {% data variables.product.product_name %} has changed. The change affects the format of personal access tokens and access tokens for {% data variables.product.prodname_oauth_apps %}, as well as user-to-server, server-to-server, and refresh tokens for {% data variables.product.prodname_github_apps %}. - - The different token types now have unique identifiable prefixes, which allows for secret scanning to detect the tokens so that you can mitigate the impact of someone accidentally committing a token to a repository. {% data variables.product.company_short %} recommends updating existing tokens as soon as possible. For more information, see "[About authentication to {% data variables.product.prodname_dotcom %}](/github/authenticating-to-github/keeping-your-account-and-data-secure/about-authentication-to-github#githubs-token-formats)" and "[About {% data variables.product.prodname_secret_scanning %}](/code-security/secret-security/about-secret-scanning)." - - - heading: 'Repositories changes' - notes: - # https://github.com/github/releases/issues/1295 - - Repositories on user profiles and organization profiles now support sorting by star count. - - # https://github.com/github/releases/issues/1327 - - When viewing the commit history of a single file, you can now click {% octicon "file-code" aria-label="The code icon" %} to view that file at the selected point in history. - - # https://github.com/github/releases/issues/1254 - - When a submodule is defined with a relative path in {% data variables.location.product_location %}, the submodule is now clickable in the web UI. Clicking the submodule in the web UI will take you to the linked repository. Previously, only submodules with absolute URLs were clickable. This is supported for relative paths for repositories with the same owner that follow the pattern ../REPOSITORY or relative paths for repositories with a different owner that follow the pattern ../OWNER/REPOSITORY. For more information about working with submodules, see [Working with submodules](https://github.blog/2016-02-01-working-with-submodules/) on {% data variables.product.prodname_blog %}. - - # https://github.com/github/releases/issues/1250 - - The web UI can now be used to synchronize an out-of-date branch of a fork with the fork's upstream branch. If there are no merge conflicts between the branches, the branch is updated either by fast-forwarding or by merging from upstream. If there are conflicts, you will be prompted to create a pull request to resolve the conflicts. For more information, see "[Syncing a fork](/github/collaborating-with-pull-requests/working-with-forks/syncing-a-fork#syncing-a-fork-from-the-web-ui)." - - - heading: 'Markdown changes' - notes: - # https://github.com/github/releases/issues/1477 - - 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).' diff --git a/data/release-notes/enterprise-server/3-2/1.yml b/data/release-notes/enterprise-server/3-2/1.yml deleted file mode 100644 index 8396e4236a..0000000000 --- a/data/release-notes/enterprise-server/3-2/1.yml +++ /dev/null @@ -1,28 +0,0 @@ -date: '2021-10-12' -sections: - security_fixes: - - 'Packages have been updated to the latest security versions. {% comment %} https://github.com/github/enterprise2/pull/27118, https://github.com/github/enterprise2/pull/27110 {% endcomment %}' - bugs: - - 'Custom pre-receive hooks could have failed due to too restrictive virtual memory or CPU time limits. {% comment %} https://github.com/github/enterprise2/pull/26973, https://github.com/github/enterprise2/pull/26955 {% endcomment %}' - - 'In a GitHub Enterprise Server clustering configuration, Dependency Graph settings could have been incorrectly applied. {% comment %} https://github.com/github/enterprise2/pull/26981, https://github.com/github/enterprise2/pull/26861 {% endcomment %}' - - 'Attempting to wipe all existing configuration settings with `ghe-cleanup-settings` failed to restart the Management Console service. {% comment %} https://github.com/github/enterprise2/pull/26988, https://github.com/github/enterprise2/pull/26901 {% endcomment %}' - - 'During replication teardown via `ghe-repl-teardown` Memcached failed to be restarted. {% comment %} https://github.com/github/enterprise2/pull/26994, https://github.com/github/enterprise2/pull/26983 {% endcomment %}' - - 'During periods of high load, users would receive HTTP 503 status codes when upstream services failed internal healthchecks. {% comment %} https://github.com/github/enterprise2/pull/27083, https://github.com/github/enterprise2/pull/26999 {% endcomment %}' - - 'Pre-receive hook environments were forbidden from calling the cat command via BusyBox on Alpine. {% comment %} https://github.com/github/enterprise2/pull/27116, https://github.com/github/enterprise2/pull/27094 {% endcomment %}' - - 'Failing over from a primary Cluster datacenter to a secondary Cluster datacenter succeeds, but then failing back over to the original primary Cluster datacenter failed to promote Elasticsearch indicies. {% comment %} https://github.com/github/github/pull/193182, https://github.com/github/github/pull/192447 {% endcomment %}' - - 'The "Import teams" button on the Teams page for an Organization returned an HTTP 404. {% comment %} https://github.com/github/github/pull/193303 {% endcomment %}' - - 'Using the API to disable Secret Scanning correctly disabled the property but incorrectly returned an HTTP 422 and an error message. {% comment %} https://github.com/github/github/pull/193455, https://github.com/github/github/pull/192907 {% endcomment %}' - - 'In some cases, GitHub Enterprise Administrators attempting to view the `Dormant users` page received `502 Bad Gateway` or `504 Gateway Timeout` response. {% comment %} https://github.com/github/github/pull/194262, https://github.com/github/github/pull/193609 {% endcomment %}' - - 'Performance was negatively impacted in certain high load situations as a result of the increased number of `SynchronizePullRequestJob` jobs. {% comment %} https://github.com/github/github/pull/195256, https://github.com/github/github/pull/194591 {% endcomment %}' - - 'A user defined pattern created for Secret Scanning would continue getting scanned even after it was deleted. {% comment %} https://github.com/github/token-scanning-service/pull/1039, https://github.com/github/token-scanning-service/pull/822 {% endcomment %}' - changes: - - 'GitHub Apps now set the Secret Scanning feature on a repository consistently with the API. {% comment %} https://github.com/github/github/pull/193456, https://github.com/github/github/pull/193125 {% endcomment %}' - 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 %}' \ No newline at end of file diff --git a/data/release-notes/enterprise-server/3-2/10.yml b/data/release-notes/enterprise-server/3-2/10.yml deleted file mode 100644 index 45ddff2f81..0000000000 --- a/data/release-notes/enterprise-server/3-2/10.yml +++ /dev/null @@ -1,16 +0,0 @@ -date: '2022-03-01' -sections: - security_fixes: - - "HIGH: An integer overflow vulnerability was identified in GitHub's markdown parser that could potentially lead to information leaks and RCE. This vulnerability was reported through the GitHub Bug Bounty program by Felix Wilhelm of Google's Project Zero and has been assigned CVE-2022-24724." - bugs: - - Upgrades could sometimes fail if a high-availability replica's clock was out of sync with the primary. - - OAuth Applications created after September 1st, 2020 were not able to use the [Check an Authorization](https://docs.github.com/en/enterprise-server@3.2/rest/reference/apps#check-an-authorization) API endpoint. - 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. - - '{% data reusables.release-notes.ghas-3.4-secret-scanning-known-issue %}' \ No newline at end of file diff --git a/data/release-notes/enterprise-server/3-2/11.yml b/data/release-notes/enterprise-server/3-2/11.yml deleted file mode 100644 index 8e12cf93c0..0000000000 --- a/data/release-notes/enterprise-server/3-2/11.yml +++ /dev/null @@ -1,44 +0,0 @@ -date: '2022-04-04' -sections: - security_fixes: - - 'MEDIUM: A path traversal vulnerability was identified in {% data variables.product.prodname_ghe_server %} Management Console that allowed the bypass of CSRF protections. This vulnerability affected all versions of {% data variables.product.prodname_ghe_server %} prior to 3.5 and was fixed in versions 3.1.19, 3.2.11, 3.3.6, 3.4.1. This vulnerability was reported via the {% data variables.product.prodname_dotcom %} Bug Bounty program and has been assigned CVE-2022-23732.' - - 'MEDIUM: An integer overflow vulnerability was identified in the 1.x branch and the 2.x branch of `yajil` which leads to subsequent heap memory corruption when dealing with large (~2GB) inputs. This vulnerability was reported internally and has been assigned CVE-2022-24795. ' - - Support bundles could include sensitive files if {% data variables.product.prodname_actions %} was enabled. - - Packages have been updated to the latest security versions. - bugs: - - Minio processes would have high CPU usage if an old configuration option was present after upgrading {% data variables.product.prodname_ghe_server %}. - - The options to enable `TLS 1.0` and `TLS 1.1` in the Privacy settings of the Management Console were shown, although removal of those protocol versions occurred in an earlier release. - - In a HA environment, configuring MSSQL replication could require additional manual steps after enabling {% data variables.product.prodname_actions %} for the first time. - - A subset of internal configuration files are more reliably updated after a hotpatch. - - The `ghe-run-migrations` script would sometimes fail to generate temporary certificate names correctly. - - In a cluster environment, Git LFS operations could fail with failed internal API calls that crossed multiple web nodes. - - Pre-receive hooks that used `gpg --import` timed out due to insufficient `syscall` privileges. - - In some cluster topologies, webhook delivery information was not available. - - In HA configurations, tearing down a replica would fail if {% data variables.product.prodname_actions %} had previously been enabled. - - Elasticsearch health checks would not allow a yellow cluster status when running migrations. - - Organizations created as a result of a user transforming their user account into an organization were not added to the global enterprise account. - - When using `ghe-migrator` or exporting from {% data variables.product.prodname_dotcom_the_website %}, a long-running export would fail when data was deleted mid-export. - - The {% data variables.product.prodname_actions %} deployment graph would display an error when rendering a pending job. - - Links to inaccessible pages were removed. - - Navigating away from a comparison of two commits in the web UI would have the diff persist in other pages. - - Adding a team as a reviewer to a pull request would sometimes show the incorrect number of members on that team. - - The [Remove team membership for a user](/rest/reference/teams#remove-team-membership-for-a-user) API endpoint would respond with an error when attempting to remove a member managed externally by a SCIM group. - - A large number of dormant users could cause a {% data variables.product.prodname_github_connect %} configuration to fail. - - The "Feature & beta enrollments" page in the Site admin web UI was incorrectly available. - - The "Site admin mode" link in the site footer did not change state when clicked. - - 'The `spokesctl cache-policy rm` command no longer fails with the message `error: failed to delete cache policy`.' - changes: - - Memcached connection limits were increased to better accommodate large cluster topologies. - - The Dependency Graph API previously ran with a statically defined port. - - The default shard counts for cluster-related Elasticsearch shard settings have been updated. - - The “Triage” and “Maintain” team roles are preserved during repository migrations. - - Performance has been improved for web requests made by enterprise owners. - known_issues: - - On a freshly set up {% data variables.product.prodname_ghe_server %} instance without any users, an attacker could create the first admin user. - - Custom firewall rules are removed during the upgrade process. - - Git LFS tracked files [uploaded through the web interface](https://github.com/blog/2105-upload-files-to-your-repositories) are incorrectly added directly to the repository. - - Issues cannot be closed if they contain a permalink to a blob in the same repository, where the blob's file path is longer than 255 characters. - - When "Users can search GitHub.com" is enabled with {% data variables.product.prodname_github_connect %}, issues in private and internal repositories are not included in {% data variables.product.prodname_dotcom_the_website %} search results. - - The {% data variables.product.prodname_registry %} npm registry no longer returns a time value in metadata responses. This was done to allow for substantial performance improvements. We continue to have all the data necessary to return a time value as part of the metadata response and will resume returning this value in the future once we have solved the existing performance issues. - - Resource limits that are specific to processing pre-receive hooks may cause some pre-receive hooks to fail. - - '{% data reusables.release-notes.ghas-3.4-secret-scanning-known-issue %}' \ No newline at end of file diff --git a/data/release-notes/enterprise-server/3-2/12.yml b/data/release-notes/enterprise-server/3-2/12.yml deleted file mode 100644 index 61e2d92238..0000000000 --- a/data/release-notes/enterprise-server/3-2/12.yml +++ /dev/null @@ -1,24 +0,0 @@ -date: '2022-04-20' -sections: - security_fixes: - - Packages have been updated to the latest security versions. - bugs: - - Upgrading the nodes in a high availability pair with an upgrade package could cause Elasticsearch to enter an inconsistent state in some cases. - - In some cluster topologies, the command line utilities `ghe-spokesctl` and `ghe-btop` failed to run. - - Elasticsearch indices could be duplicated during a package upgrade, due to an `elasticsearch-upgrade` service running multiple times in parallel. - - When converting a user account to an organization, if the user account was an owner of the {% data variables.product.prodname_ghe_server %} enterprise account, the converted organization would incorrectly appear in the enterprise owner list. - - Creating an impersonation OAuth token using the Enterprise Administration REST API worked incorrectly when an integration matching the OAuth Application ID already existed. - changes: - - Configuration errors that halt a config apply run are now output to the terminal in addition to the configuration log. - - When attempting to cache a value larger than the maximum allowed in Memcached, an error was raised however the key was not reported. - - The {% data variables.product.prodname_codeql %} starter workflow no longer errors even if the default token permissions for {% data variables.product.prodname_actions %} are not used. - - If {% data variables.product.prodname_GH_advanced_security %} features are enabled on your instance, the performance of background jobs has improved when processing batches for repository contributions. - known_issues: - - On a freshly set up {% data variables.product.prodname_ghe_server %} instance without any users, an attacker could create the first admin user. - - Custom firewall rules are removed during the upgrade process. - - Git LFS tracked files [uploaded through the web interface](https://github.com/blog/2105-upload-files-to-your-repositories) are incorrectly added directly to the repository. - - Issues cannot be closed if they contain a permalink to a blob in the same repository, where the blob's file path is longer than 255 characters. - - When "Users can search GitHub.com" is enabled with {% data variables.product.prodname_github_connect %}, issues in private and internal repositories are not included in {% data variables.product.prodname_dotcom_the_website %} search results. - - The {% data variables.product.prodname_registry %} npm registry no longer returns a time value in metadata responses. This was done to allow for substantial performance improvements. We continue to have all the data necessary to return a time value as part of the metadata response and will resume returning this value in the future once we have solved the existing performance issues. - - Resource limits that are specific to processing pre-receive hooks may cause some pre-receive hooks to fail. - - '{% data reusables.release-notes.ghas-3.4-secret-scanning-known-issue %}' \ No newline at end of file diff --git a/data/release-notes/enterprise-server/3-2/13.yml b/data/release-notes/enterprise-server/3-2/13.yml deleted file mode 100644 index dab4acdb61..0000000000 --- a/data/release-notes/enterprise-server/3-2/13.yml +++ /dev/null @@ -1,28 +0,0 @@ -date: '2022-05-17' -sections: - security_fixes: - - '**MEDIUM:** A security issue in nginx resolver was identified, where an attacker who could forge UDP packets from the DNS server could cause 1-byte memory overwrite, resulting in worker process crashes or other potentially damaging impacts. The vulnerability has been assigned [CVE-2021-23017](https://nvd.nist.gov/vuln/detail/CVE-2021-23017).' - - Updated the `actions/checkout@v2` and `actions/checkout@v3` actions to address new vulnerabilities announced in the [Git security enforcement blog post](https://github.blog/2022-04-12-git-security-vulnerability-announced/). - - Packages have been updated to the latest security versions. - bugs: - - In some cluster topologies, the `ghe-cluster-status` command left behind empty directories in `/tmp`. - - SNMP incorrectly logged a high number of `Cannot statfs` error messages to syslog. - - For instances configured with SAML authentication and built-in fallback enabled, built-in users would get stuck in a “login” loop when attempting to sign in from the page generated after logging out. - - Videos uploaded to issue comments would not be rendered properly. - - When using SAML encrypted assertions, some assertions were not correctly marking SSH keys as verified. - - When using `ghe-migrator`, a migration would fail to import video file attachments in issues and pull requests. - - 'The Releases page would return a 500 error when the repository has tags that contain non-ASCII characters. [Updated: 2022-06-10]' - changes: - - In high availability configurations, clarify that the replication overview page in the Management Console only displays the current replication configuration, not the current replication status. - - When enabling {% data variables.product.prodname_registry %}, clarify that using a Shared Access Signature (SAS) token as connection string is not currently supported. - - Support bundles now include the row count of tables stored in MySQL. - - Dependency Graph can now be enabled without vulnerability data, allowing you to see what dependencies are in use and at what versions. Enabling Dependency Graph without enabling {% data variables.product.prodname_github_connect %} will **not** provide vulnerability information. - known_issues: - - On a freshly set up {% data variables.product.prodname_ghe_server %} instance without any users, an attacker could create the first admin user. - - Custom firewall rules are removed during the upgrade process. - - Git LFS tracked files [uploaded through the web interface](https://github.com/blog/2105-upload-files-to-your-repositories) are incorrectly added directly to the repository. - - Issues cannot be closed if they contain a permalink to a blob in the same repository, where the blob's file path is longer than 255 characters. - - When "Users can search GitHub.com" is enabled with {% data variables.product.prodname_github_connect %}, issues in private and internal repositories are not included in {% data variables.product.prodname_dotcom_the_website %} search results. - - The {% data variables.product.prodname_registry %} npm registry no longer returns a time value in metadata responses. This was done to allow for substantial performance improvements. We continue to have all the data necessary to return a time value as part of the metadata response and will resume returning this value in the future once we have solved the existing performance issues. - - Resource limits that are specific to processing pre-receive hooks may cause some pre-receive hooks to fail. - - '{% data reusables.release-notes.ghas-3.4-secret-scanning-known-issue %}' \ No newline at end of file diff --git a/data/release-notes/enterprise-server/3-2/14.yml b/data/release-notes/enterprise-server/3-2/14.yml deleted file mode 100644 index 3fb623097b..0000000000 --- a/data/release-notes/enterprise-server/3-2/14.yml +++ /dev/null @@ -1,23 +0,0 @@ -date: '2022-06-09' -sections: - security_fixes: - - Packages have been updated to the latest security versions. - bugs: - - An internal script to validate hostnames in the {% data variables.product.prodname_ghe_server %} configuration file would return an error if the hostname string started with a "." (period character). - - In HA configurations where the primary node's hostname was longer than 60 characters, MySQL would fail to be configured. - - The `--gateway` argument was added to the `ghe-setup-network` command, to allow passing the gateway address when configuring network settings using the command line. - - Image attachments that were deleted would return a `500 Internal Server Error` instead of a `404 Not Found` error. - - The calculation of "maximum committers across entire instance" reported in the site admin dashboard was incorrect. - - An incorrect database entry for repository replicas caused database corruption when performing a restore using {% data variables.product.prodname_enterprise_backup_utilities %}. - changes: - - Optimised the inclusion of metrics when generating a cluster support bundle. - - In HA configurations where Elasticsearch reported a valid yellow status, changes introduced in a previous fix would block the `ghe-repl-stop` command and not allow replication to be stopped. Using `ghe-repo-stop --force` will now force Elasticsearch to stop when the service is in a normal or valid yellow status. - known_issues: - - On a freshly set up {% data variables.product.prodname_ghe_server %} instance without any users, an attacker could create the first admin user. - - Custom firewall rules are removed during the upgrade process. - - Git LFS tracked files [uploaded through the web interface](https://github.com/blog/2105-upload-files-to-your-repositories) are incorrectly added directly to the repository. - - Issues cannot be closed if they contain a permalink to a blob in the same repository, where the blob's file path is longer than 255 characters. - - When "Users can search GitHub.com" is enabled with {% data variables.product.prodname_github_connect %}, issues in private and internal repositories are not included in {% data variables.product.prodname_dotcom_the_website %} search results. - - The {% data variables.product.prodname_registry %} npm registry no longer returns a time value in metadata responses. This was done to allow for substantial performance improvements. We continue to have all the data necessary to return a time value as part of the metadata response and will resume returning this value in the future once we have solved the existing performance issues. - - Resource limits that are specific to processing pre-receive hooks may cause some pre-receive hooks to fail. - - '{% data reusables.release-notes.ghas-3.4-secret-scanning-known-issue %}' \ No newline at end of file diff --git a/data/release-notes/enterprise-server/3-2/15.yml b/data/release-notes/enterprise-server/3-2/15.yml deleted file mode 100644 index 49fa7789c6..0000000000 --- a/data/release-notes/enterprise-server/3-2/15.yml +++ /dev/null @@ -1,20 +0,0 @@ -date: '2022-06-28' -sections: - security_fixes: - - "**MEDIUM**: Ensures that `github.company.com` and `github-company.com` are not evaluated by internal services as identical hostnames, preventing a potential server-side security forgery (SSRF) attack." - - "**LOW**: An attacker could access the Management Console with a path traversal attack via HTTP even if external firewall rules blocked HTTP access." - - Packages have been updated to the latest security versions. - bugs: - - In some cases, site administrators were not automatically added as enterprise owners. - - After merging a branch into the default branch, the "History" link for a file would still link to the previous branch instead of the target branch. - changes: - - Creating or updating check runs or check suites could return `500 Internal Server Error` if the value for certain fields, like the name, was too long. - known_issues: - - On a freshly set up {% data variables.product.prodname_ghe_server %} instance without any users, an attacker could create the first admin user. - - Custom firewall rules are removed during the upgrade process. - - Git LFS tracked files [uploaded through the web interface](https://github.com/blog/2105-upload-files-to-your-repositories) are incorrectly added directly to the repository. - - Issues cannot be closed if they contain a permalink to a blob in the same repository, where the blob's file path is longer than 255 characters. - - When "Users can search GitHub.com" is enabled with {% data variables.product.prodname_github_connect %}, issues in private and internal repositories are not included in {% data variables.product.prodname_dotcom_the_website %} search results. - - The {% data variables.product.prodname_registry %} npm registry no longer returns a time value in metadata responses. This was done to allow for substantial performance improvements. We continue to have all the data necessary to return a time value as part of the metadata response and will resume returning this value in the future once we have solved the existing performance issues. - - Resource limits that are specific to processing pre-receive hooks may cause some pre-receive hooks to fail. - - '{% data reusables.release-notes.ghas-3.4-secret-scanning-known-issue %}' \ No newline at end of file diff --git a/data/release-notes/enterprise-server/3-2/16.yml b/data/release-notes/enterprise-server/3-2/16.yml deleted file mode 100644 index bcd8841c50..0000000000 --- a/data/release-notes/enterprise-server/3-2/16.yml +++ /dev/null @@ -1,27 +0,0 @@ -date: '2022-07-21' -sections: - security_fixes: - - "**MEDIUM**: Prevents an attack where a server-side request forgery (SSRF) could potentially force the Subversion (SVN) bridge to execute remote code by injecting arbitrary data into Memcached." - - Updates Grafana to version 7.5.16, which addresses various security vulnerabilities including [CVE-2020-13379](https://github.com/advisories/GHSA-wc9w-wvq2-ffm9) and [CVE-2022-21702](https://github.com/grafana/grafana/security/advisories/GHSA-xc3p-28hw-q24g). - - Packages have been updated to the latest security versions. - - "**MEDIUM**: A vulnerability involving deserialization of untrusted data was identified in GitHub Enterprise Server that could potentially lead to remote code execution on the Subversion (SVN) bridge. To exploit this vulnerability, an attacker would need to gain access via a server-side request forgery (SSRF) that would let an attacker control the data being deserialized. This vulnerability was reported via the GitHub Bug Bounty program and has been assigned [CVE-2022-23734](https://www.cve.org/CVERecord?id=CVE-2022-23734)." - bugs: - - Fixed an issue where the files inside the artifact zip archives had permissions of 000 when unpacked using an unzip tool. Now the files will have the permissions set to 644, the same way as it works in GitHub.com. - - In some cases, the collectd daemon could consume excess memory. - - In some cases, backups of rotated log files could accumulate and consume excess storage. - - After an upgrade to a new feature release and subsequent configuration run, Elasticsearch could log excessive exceptions while rebuilding indices. - - In some cases where a protected branch required more than one approving review, a pull request could be merged with fewer than the required number of approving reviews. - - On instances using LDAP authentication, the authentication prompt for sudo mode incorrectly placed the cursor within the password field by default when text fields for both a username and password were visible. - changes: - - The `ghe-set-password` command-line utility starts required services automatically when the instance is booted in recovery mode. - - Metrics for `aqueduct` background processes are gathered for Collectd forwarding and display in the Management Console. - - The location of the database migration and configuration run log, `/data/user/common/ghe-config.log`, is now displayed on the page that details a migration in progress. - known_issues: - - On a freshly set up {% data variables.product.prodname_ghe_server %} instance without any users, an attacker could create the first admin user. - - Custom firewall rules are removed during the upgrade process. - - Git LFS tracked files [uploaded through the web interface](https://github.com/blog/2105-upload-files-to-your-repositories) are incorrectly added directly to the repository. - - Issues cannot be closed if they contain a permalink to a blob in the same repository, where the blob's file path is longer than 255 characters. - - When "Users can search GitHub.com" is enabled with {% data variables.product.prodname_github_connect %}, issues in private and internal repositories are not included in {% data variables.product.prodname_dotcom_the_website %} search results. - - The {% data variables.product.prodname_registry %} npm registry no longer returns a time value in metadata responses. This was done to allow for substantial performance improvements. We continue to have all the data necessary to return a time value as part of the metadata response and will resume returning this value in the future once we have solved the existing performance issues. - - Resource limits that are specific to processing pre-receive hooks may cause some pre-receive hooks to fail. - - '{% data reusables.release-notes.ghas-3.4-secret-scanning-known-issue %}' diff --git a/data/release-notes/enterprise-server/3-2/17.yml b/data/release-notes/enterprise-server/3-2/17.yml deleted file mode 100644 index 38943c2361..0000000000 --- a/data/release-notes/enterprise-server/3-2/17.yml +++ /dev/null @@ -1,18 +0,0 @@ -date: '2022-08-11' -sections: - security_fixes: - - | - **CRITICAL**: GitHub Enterprise Server's Elasticsearch container used a version of OpenJDK 8 that was vulnerable to an integer truncation issue when processing malicious XSLT stylesheets. The vulnerability is tracked as [CVE-2022-34169](https://github.com/advisories/GHSA-9339-86wc-4qgf). - - | - **HIGH**: Previously installed apps on user accounts were automatically granted permission to access an organization on scoped access tokens after the user account was transformed into an organization account. This vulnerability was reported via the [GitHub Bug Bounty program](https://bounty.github.com). - bugs: - - When a custom dormancy threshold was set for the instance, suspending all dormant users did not reliably respect the threshold. For more information about dormancy, see "[Managing dormant users](/admin/user-management/managing-users-in-your-enterprise/managing-dormant-users)." - known_issues: - - On a freshly set up {% data variables.product.prodname_ghe_server %} instance without any users, an attacker could create the first admin user. - - Custom firewall rules are removed during the upgrade process. - - Git LFS tracked files [uploaded through the web interface](https://github.com/blog/2105-upload-files-to-your-repositories) are incorrectly added directly to the repository. - - Issues cannot be closed if they contain a permalink to a blob in the same repository, where the blob's file path is longer than 255 characters. - - When "Users can search GitHub.com" is enabled with {% data variables.product.prodname_github_connect %}, issues in private and internal repositories are not included in {% data variables.product.prodname_dotcom_the_website %} search results. - - The {% data variables.product.prodname_registry %} npm registry no longer returns a time value in metadata responses. This was done to allow for substantial performance improvements. We continue to have all the data necessary to return a time value as part of the metadata response and will resume returning this value in the future once we have solved the existing performance issues. - - Resource limits that are specific to processing pre-receive hooks may cause some pre-receive hooks to fail. - - '{% data reusables.release-notes.ghas-3.4-secret-scanning-known-issue %}' diff --git a/data/release-notes/enterprise-server/3-2/18.yml b/data/release-notes/enterprise-server/3-2/18.yml deleted file mode 100644 index 818d03df01..0000000000 --- a/data/release-notes/enterprise-server/3-2/18.yml +++ /dev/null @@ -1,16 +0,0 @@ -date: '2022-08-30' -sections: - bugs: - - Duplicate administrative SSH keys could appear in both the Management Console and the `/home/admin/.ssh/authorized_keys` file. - - In some cases, background tasks could stall due to a library that was used concurrently despite not being thread-safe. - changes: - - Generation of support bundles is faster as a result of parallelized log sanitization. For more information about support bundles, see "[Providing data to GitHub Support](/support/contacting-github-support/providing-data-to-github-support)." - known_issues: - - On a freshly set up {% data variables.product.prodname_ghe_server %} instance without any users, an attacker could create the first admin user. - - Custom firewall rules are removed during the upgrade process. - - Git LFS tracked files [uploaded through the web interface](https://github.com/blog/2105-upload-files-to-your-repositories) are incorrectly added directly to the repository. - - Issues cannot be closed if they contain a permalink to a blob in the same repository, where the blob's file path is longer than 255 characters. - - When "Users can search GitHub.com" is enabled with {% data variables.product.prodname_github_connect %}, issues in private and internal repositories are not included in {% data variables.product.prodname_dotcom_the_website %} search results. - - The {% data variables.product.prodname_registry %} npm registry no longer returns a time value in metadata responses. This was done to allow for substantial performance improvements. We continue to have all the data necessary to return a time value as part of the metadata response and will resume returning this value in the future once we have solved the existing performance issues. - - Resource limits that are specific to processing pre-receive hooks may cause some pre-receive hooks to fail. - - '{% data reusables.release-notes.ghas-3.4-secret-scanning-known-issue %}' diff --git a/data/release-notes/enterprise-server/3-2/19.yml b/data/release-notes/enterprise-server/3-2/19.yml deleted file mode 100644 index 142a371a7f..0000000000 --- a/data/release-notes/enterprise-server/3-2/19.yml +++ /dev/null @@ -1,24 +0,0 @@ -date: '2022-09-21' -sections: - security_fixes: - - | - **HIGH**: A GitHub App could use a scoped user-to-server token to bypass user authorization logic and escalate privileges. - - | - **MEDIUM**: The use of a Unicode right-to-left override character in the list of accessible files for a GitHub App could obscure additional files that the app could access. - - Packages have been updated to the latest security versions. - bugs: - - In a cluster configuration, running `ghe-cluster-config-apply` could cause unconfigured nodes to replicate configuration to the rest of the cluster, potentially removing configurations from existing nodes. - - In some cases, the Management Console's monitor dashboard would not load correctly. - - When sending a support bundle to GitHub Enterprise Support using `ghe-support-upload`, the `-t` option would not successfully associate the uploaded bundle with the specified ticket. - - After a user deleted or restored packages from the web interface, counts for packages could render incorrectly. - - Manually disabled GitHub Actions workflows in a repository were re-enabled if the repository received a push containing more than 2048 commits, or if the repository's default branch changed. - - When using a VPC endpoint URL as an AWS S3 URL for GitHub Packages, publication and installation of packages failed. - known_issues: - - On a freshly set up {% data variables.product.prodname_ghe_server %} instance without any users, an attacker could create the first admin user. - - Custom firewall rules are removed during the upgrade process. - - Git LFS tracked files [uploaded through the web interface](https://github.com/blog/2105-upload-files-to-your-repositories) are incorrectly added directly to the repository. - - Issues cannot be closed if they contain a permalink to a blob in the same repository, where the blob's file path is longer than 255 characters. - - When "Users can search GitHub.com" is enabled with {% data variables.product.prodname_github_connect %}, issues in private and internal repositories are not included in {% data variables.product.prodname_dotcom_the_website %} search results. - - The {% data variables.product.prodname_registry %} npm registry no longer returns a time value in metadata responses. This was done to allow for substantial performance improvements. We continue to have all the data necessary to return a time value as part of the metadata response and will resume returning this value in the future once we have solved the existing performance issues. - - Resource limits that are specific to processing pre-receive hooks may cause some pre-receive hooks to fail. - - '{% data reusables.release-notes.ghas-3.4-secret-scanning-known-issue %}' diff --git a/data/release-notes/enterprise-server/3-2/2.yml b/data/release-notes/enterprise-server/3-2/2.yml deleted file mode 100644 index 536365cd7d..0000000000 --- a/data/release-notes/enterprise-server/3-2/2.yml +++ /dev/null @@ -1,23 +0,0 @@ -date: '2021-10-28' -sections: - security_fixes: - - 'It was possible for cleartext passwords to end up in certain log files.' - - 'Several known weak SSH public keys have been added to the deny list and can no longer be registered. In addition, versions of GitKraken known to generate weak SSH keys (7.6.x, 7.7.x and 8.0.0) have been blocked from registering new public keys.' - - 'Packages have been updated to the latest security versions.' - bugs: - - 'Restore might fail for enterprise server in clustering mode if orchestrator is not healthily.' - - 'Codespaces links were displayed in organization settings.' - - 'Several parts of the application were unusable for users who are owners of many organizations.' - - 'Fixed a link to https://docs.github.com.' - changes: - - 'Browsing and job performance optimizations for repositories with many refs.' - known_issues: - - After saving a new release on a repository, the `/releases` page shows a 500 error. A fix for this issue is expected to ship in 3.2.3. - - 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 %}' \ No newline at end of file diff --git a/data/release-notes/enterprise-server/3-2/20.yml b/data/release-notes/enterprise-server/3-2/20.yml deleted file mode 100644 index 4966e70f68..0000000000 --- a/data/release-notes/enterprise-server/3-2/20.yml +++ /dev/null @@ -1,23 +0,0 @@ -date: '2022-10-25' -sections: - security_fixes: - - | - **HIGH**: Updated dependencies for the Management Console to the latest patch versions, which addresses security vulnerabilities including [CVE-2022-30123](https://github.com/advisories/GHSA-wq4h-7r42-5hrr) and [CVE-2022-29181](https://github.com/advisories/GHSA-xh29-r2w5-wx8m). - - | - **HIGH**: Added checks to address an improper cache key vulnerability that allowed an unauthorized actor to access private repository files through a public repository. This vulnerability has been assigned [CVE-2022-23738](https://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2022-23738). - - | - **MEDIUM**: Updated [CommonMarker](https://github.com/gjtorikian/commonmarker) to address a scenario where parallel requests to the Markdown REST API could result in unbounded resource exhaustion. This vulnerability has been assigned [CVE-2022-39209](https://nvd.nist.gov/vuln/detail/CVE-2022-39209). - - | - **LOW**: Due to a CSRF vulnerability, a `GET` request to the instance's `site/toggle_site_admin_and_employee_status` endpoint could toggle a user's site administrator status unknowingly. - bugs: - - | - After a site administrator installed a hotpatch containing changes to web interface assets such as JavaScript files or images, the instance did not serve the new assets. - known_issues: - - On a freshly set up {% data variables.product.prodname_ghe_server %} instance without any users, an attacker could create the first admin user. - - Custom firewall rules are removed during the upgrade process. - - Git LFS tracked files [uploaded through the web interface](https://github.com/blog/2105-upload-files-to-your-repositories) are incorrectly added directly to the repository. - - Issues cannot be closed if they contain a permalink to a blob in the same repository, where the blob's file path is longer than 255 characters. - - When "Users can search GitHub.com" is enabled with {% data variables.product.prodname_github_connect %}, issues in private and internal repositories are not included in {% data variables.product.prodname_dotcom_the_website %} search results. - - The {% data variables.product.prodname_registry %} npm registry no longer returns a time value in metadata responses. This was done to allow for substantial performance improvements. We continue to have all the data necessary to return a time value as part of the metadata response and will resume returning this value in the future once we have solved the existing performance issues. - - Resource limits that are specific to processing pre-receive hooks may cause some pre-receive hooks to fail. - - '{% data reusables.release-notes.ghas-3.4-secret-scanning-known-issue %}' diff --git a/data/release-notes/enterprise-server/3-2/3.yml b/data/release-notes/enterprise-server/3-2/3.yml deleted file mode 100644 index 1d68a8ef65..0000000000 --- a/data/release-notes/enterprise-server/3-2/3.yml +++ /dev/null @@ -1,31 +0,0 @@ -date: '2021-11-09' -sections: - security_fixes: - - A path traversal vulnerability was identified in {% data variables.product.prodname_pages %} builds on {% data variables.product.prodname_ghe_server %} that could allow an attacker to read system files. To exploit this vulnerability, an attacker needed permission to create and build a {% data variables.product.prodname_pages %} site on the {% data variables.product.prodname_ghe_server %} instance. This vulnerability affected all versions of {% data variables.product.prodname_ghe_server %} prior to 3.3, and was fixed in versions 3.0.19, 3.1.11, and 3.2.3. This vulnerability was reported through the {% data variables.product.company_short %} Bug Bounty program and has been assigned CVE-2021-22870. - - Packages have been updated to the latest security versions. - bugs: - - Some Git operations failed after upgrading a {% data variables.product.prodname_ghe_server %} 3.x cluster because of the HAProxy configuration. - - Unicorn worker counts might have been set incorrectly in clustering mode. - - Resqued worker counts might have been set incorrectly in clustering mode. - - If Ubuntu's Uncomplicated Firewall (UFW) status was inactive, a client could not clearly see it in the logs. - - Upgrading from {% data variables.product.prodname_ghe_server %} 2.x to 3.x failed when there were UTF8 characters in an LDAP configuration. - - Some pages and Git-related background jobs might not run in cluster mode with certain cluster configurations. - - The documentation link for Server Statistics was broken. - - When a new tag was created, the [push](/developers/webhooks-and-events/webhooks/webhook-events-and-payloads#push) webhook payload did not display a correct `head_commit` object. Now, when a new tag is created, the 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. - - The enterprise audit log page would not display audit events for {% data variables.product.prodname_secret_scanning %}. - - There was an insufficient job timeout for replica repairs. - - A repository's releases page would return a 500 error when viewing releases. - - 'Users were not warned about potentially dangerous bidirectional unicode characters when viewing files. For more information, see "[Warning about bidirectional Unicode text](https://github.co/hiddenchars)" in {% data variables.product.prodname_blog %}.' - - Hookshot Go sent distribution type metrics that Collectd could not handle, which caused a ballooning of parsing errors. - - Public repositories displayed unexpected results from {% data variables.product.prodname_secret_scanning %} with a type of `Unknown Token`. - changes: - - Kafka configuration improvements have been added. When deleting repositories, package files are now immediately deleted from storage account to free up space. `DestroyDeletedPackageVersionsJob` now deletes package files from storage account for stale packages along with metadata records. - 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 %}' \ No newline at end of file diff --git a/data/release-notes/enterprise-server/3-2/4.yml b/data/release-notes/enterprise-server/3-2/4.yml deleted file mode 100644 index d35854b876..0000000000 --- a/data/release-notes/enterprise-server/3-2/4.yml +++ /dev/null @@ -1,30 +0,0 @@ -date: '2021-11-23' -intro: Downloads have been disabled due to a major bug affecting multiple customers. A fix will be available in the next patch. -sections: - security_fixes: - - Packages have been updated to the latest security versions. - bugs: - - Running `ghe-repl-start` or `ghe-repl-status` would sometimes return errors connecting to the database when GitHub Actions was enabled. - - Pre-receive hooks would fail due to undefined `PATH`. - - 'Running `ghe-repl-setup` would return an error: `cannot create directory /data/user/elasticsearch: File exists` if the instance had previously been configured as a replica.' - - 'Running `ghe-support-bundle` returned an error: `integer expression expected`.' - - 'After setting up a high availability replica, `ghe-repl-status` included an error in the output: `unexpected unclosed action in command`.' - - In large cluster environments, the authentication backend could be unavailable on a subset of frontend nodes. - - Some critical services may not have been available on backend nodes in GHES Cluster. - - The repository permissions to the user returned by the `/repos` API would not return the full list. - - The `childTeams` connection on the `Team` object in the GraphQL schema produced incorrect results under some circumstances. - - In a high availability configuration, repository maintenance always showed up as failed in stafftools, even when it succeeded. - - User defined patterns would not detect secrets in files like `package.json` or `yarn.lock`. - changes: - - An additional outer layer of `gzip` compression when creating a cluster support bundle with `ghe-cluster-suport-bundle` is now turned off by default. This outer compression can optionally be applied with the `ghe-cluster-suport-bundle -c` command line option. - - We have added extra text to the admin console to remind users about the mobile apps' data collection for experience improvement purposes. - - The {% data variables.product.prodname_github_connect %} data connection record now includes a list of enabled {% data variables.product.prodname_github_connect %} features. [Updated 2021-12-09] - 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 %}' \ No newline at end of file diff --git a/data/release-notes/enterprise-server/3-2/5.yml b/data/release-notes/enterprise-server/3-2/5.yml deleted file mode 100644 index 97310e09cd..0000000000 --- a/data/release-notes/enterprise-server/3-2/5.yml +++ /dev/null @@ -1,28 +0,0 @@ -date: '2021-12-07' -sections: - security_fixes: - - Support bundles could include sensitive files if they met a specific set of conditions. - - A UI misrepresentation vulnerability was identified in GitHub Enterprise Server that allowed more permissions to be granted during a GitHub App's user-authorization web flow than was displayed to the user during approval. This vulnerability affected all versions of GitHub Enterprise Server prior to 3.3 and was fixed in versions 3.2.5, 3.1.13, 3.0.21. This vulnerability was reported via the GitHub Bug Bounty program and has been assigned [CVE-2021-41598](https://www.cve.org/CVERecord?id=CVE-2021-41598). - - A remote code execution vulnerability was identified in GitHub Enterprise Server that could be exploited when building a GitHub Pages site. This vulnerability affected all versions of GitHub Enterprise Server prior to 3.3 and was fixed in versions 3.0.21, 3.1.13, 3.2.5. This vulnerability was reported via the GitHub Bug Bounty program and has been assigned [CVE-2021-41599](https://www.cve.org/CVERecord?id=CVE-2021-41599). Updated February 17, 2022. - bugs: - - In some cases when Actions was not enabled, `ghe-support-bundle` reported an unexpected message `Unable to find MS SQL container.` - - Running `ghe-config-apply` could sometimes fail because of permission issues in `/data/user/tmp/pages`. - - A misconfiguration in the Management Console caused scheduling errors. - - Docker would hold log files open after a log rotation. - - Migrations could get stuck due to incorrect handling of `blob_path` values that are not UTF-8 compatible. - - GraphQL requests did not set the GITHUB_USER_IP variable in pre-receive hook environments. - - Pagination links on org audit logs would not persist query parameters. - - During a hotpatch, it was possible for duplicate hashes if a transition ran more than once. - changes: - - Clarifies explanation of Actions path-style in documentation. - - Updates support contact URLs to use the current support site, support.github.com. - - Additional troubleshooting provided when running `ghe-mssql-diagnostic`. - 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 %}' \ No newline at end of file diff --git a/data/release-notes/enterprise-server/3-2/6.yml b/data/release-notes/enterprise-server/3-2/6.yml deleted file mode 100644 index 257725162c..0000000000 --- a/data/release-notes/enterprise-server/3-2/6.yml +++ /dev/null @@ -1,14 +0,0 @@ -date: '2021-12-13' -sections: - security_fixes: - - '{% octicon "alert" aria-label="The alert icon" %} **Critical:** A remote code execution vulnerability in the Log4j library, identified as [CVE-2021-44228](https://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2021-44228), affected all versions of {% data variables.product.prodname_ghe_server %} prior to 3.3.1. The Log4j library is used in an open source service running on the {% data variables.product.prodname_ghe_server %} instance. This vulnerability was fixed in {% data variables.product.prodname_ghe_server %} versions 3.0.22, 3.1.14, 3.2.6, and 3.3.1. For more information, please see [this post](https://github.blog/2021-12-13-githubs-response-to-log4j-vulnerability-cve-2021-44228/) on the GitHub Blog.' - - '**December 17, 2021 update**: The fixes in place for this release also mitigate [CVE-2021-45046](https://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2021-45046), which was published after this release. No additional upgrade for {% data variables.product.prodname_ghe_server %} is required to mitigate both CVE-2021-44228 and CVE-2021-45046.' - 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 %}' \ No newline at end of file diff --git a/data/release-notes/enterprise-server/3-2/7.yml b/data/release-notes/enterprise-server/3-2/7.yml deleted file mode 100644 index 95b7aea41c..0000000000 --- a/data/release-notes/enterprise-server/3-2/7.yml +++ /dev/null @@ -1,23 +0,0 @@ -date: '2022-01-18' -sections: - security_fixes: - - 'Packages have been updated to the latest security versions. In these updates, Log4j has been updated to version 2.17.1. Note: previous mitigations released in 3.3.1, 3.2.6, 3.1.14, and 3.0.22 are sufficient to address the impact of CVE-2021-44228, CVE-2021-45046, CVE-2021-45105, and CVE-2021-44832 in these versions of GitHub Enterprise Server.' - - Sanitize more secrets in the generated support bundles - - Packages have been updated to the latest security versions. - bugs: - - Actions self hosted runners would fail to self-update or run new jobs after upgrading from an older GHES installation. - - Storage settings could not be validated when configuring MinIO as blob storage for GitHub Packages. - - Running `ghe-config-apply` could sometimes fail because of permission issues in `/data/user/tmp/pages`. - - The save button in management console was unreachable by scrolling in lower resolution browsers. - - IOPS and Storage Traffic monitoring graphs were not updating after collectd version upgrade. - - Some webhook related jobs could generated large amount of logs. - - Several documentation links resulted in a 404 Not Found error. - 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 %}' \ No newline at end of file diff --git a/data/release-notes/enterprise-server/3-2/8.yml b/data/release-notes/enterprise-server/3-2/8.yml deleted file mode 100644 index 02bd8c1b31..0000000000 --- a/data/release-notes/enterprise-server/3-2/8.yml +++ /dev/null @@ -1,26 +0,0 @@ -date: '2022-02-01' -sections: - security_fixes: - - Packages have been updated to the latest security versions. - bugs: - - Pages would become unavailable following a MySQL secret rotation until `nginx` was manually restarted. - - Migrations could fail when {% data variables.product.prodname_actions %} was enabled. - - When setting the maintenance schedule with a ISO 8601 date, the actual scheduled time wouldn't match due to the timezone not being transformed to UTC. - - Spurious error messages concerning the `cloud-config.service` would be output to the console. - - The version number would not be correctly updated after a installing a hotpatch using `ghe-cluster-each`. - - Webhook table cleanup jobs could run simultaneously, causing resource contention and increasing job run time. - - When run from the primary, `ghe-repl-teardown` on a replica would not remove the replica from the MSSQL availability group. - - When using CAS authentication and the "Reactivate suspended users" option was enabled, suspended users were not automatically reactivated. - - The ability to limit email-based notifications to users with emails on a verified or approved domain did not work correctly. - - A long-running database migration related to Security Alert settings could delay upgrade completion. - changes: - - The GitHub Connect data connection record now includes a count of the number of active and dormant users and the configured dormancy period. - 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 %}' \ No newline at end of file diff --git a/data/release-notes/enterprise-server/3-2/9.yml b/data/release-notes/enterprise-server/3-2/9.yml deleted file mode 100644 index a096c338ed..0000000000 --- a/data/release-notes/enterprise-server/3-2/9.yml +++ /dev/null @@ -1,20 +0,0 @@ -date: '2022-02-17' -sections: - security_fixes: - - It was possible for a user to register a user or organization named "saml". - - Packages have been updated to the latest security versions. - bugs: - - GitHub Packages storage settings could not be validated and saved in the Management Console when Azure Blob Storage was used. - - The mssql.backup.cadence configuration option failed ghe-config-check with an invalid characterset warning. - - Fixes SystemStackError (stack too deep) when getting more than 2^16 keys from memcached. - changes: - - Secret scanning will skip scanning ZIP and other archive files for secrets. - 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. - - '{% data reusables.release-notes.ghas-3.4-secret-scanning-known-issue %}' \ No newline at end of file diff --git a/data/reusables/organizations/about-custom-repo-roles.md b/data/reusables/organizations/about-custom-repo-roles.md new file mode 100644 index 0000000000..377c321e11 --- /dev/null +++ b/data/reusables/organizations/about-custom-repo-roles.md @@ -0,0 +1 @@ +A custom repository role is a configurable set of permissions with a custom name you choose. \ No newline at end of file diff --git a/data/reusables/organizations/custom-repo-roles-ghec-only.md b/data/reusables/organizations/custom-repo-roles-ghec-only.md new file mode 100644 index 0000000000..03c3240261 --- /dev/null +++ b/data/reusables/organizations/custom-repo-roles-ghec-only.md @@ -0,0 +1,7 @@ +{% ifversion ghec %} +{% note %} + +**Note:** Only organizations that use {% data variables.product.prodname_ghe_cloud %} can create custom repository roles. {% data reusables.enterprise.link-to-ghec-trial %} + +{% endnote %} +{% endif %} \ No newline at end of file diff --git a/data/reusables/secret-scanning/secret-list-private-push-protection.md b/data/reusables/secret-scanning/secret-list-private-push-protection.md index dbc3bc76dd..016e7b23c1 100644 --- a/data/reusables/secret-scanning/secret-list-private-push-protection.md +++ b/data/reusables/secret-scanning/secret-list-private-push-protection.md @@ -49,6 +49,10 @@ Google | Google Cloud Storage Service Account Access Key ID with Google Cloud St Google | Google Cloud Storage User Access Key ID with Google Cloud Storage Access Key Secret | google_cloud_storage_user_access_key_id
google_cloud_storage_access_key_secret Google | Google OAuth Client ID with Google OAuth Client Secret | google_oauth_client_id
google_oauth_client_secret Grafana | Grafana API Key | grafana_api_key +{%- ifversion fpt or ghec or ghes > 3.8 or ghae > 3.8 %} +HashiCorp | HashiCorp Vault Batch Token (v1.10.0+) | hashicorp_vault_batch_token +HashiCorp | HashiCorp Vault Root Service Token (v1.10.0+) | hashicorp_vault_root_service_token +HashiCorp | HashiCorp Vault Service Token (v1.10.0+) | hashicorp_vault_service_token{% endif %} Hubspot | Hubspot API Key | hubspot_api_key Intercom | Intercom Access Token | intercom_access_token {%- ifversion fpt or ghec or ghes > 3.6 or ghae > 3.6 %} diff --git a/data/reusables/user-settings/patv2-filters.md b/data/reusables/user-settings/patv2-filters.md new file mode 100644 index 0000000000..052394680e --- /dev/null +++ b/data/reusables/user-settings/patv2-filters.md @@ -0,0 +1,4 @@ +1. Optionally, use filters to only display certain tokens. + - Use the **Owner** dropdown to filter the tokens by the member who created the token. + - Use the **Repository** dropdown to filter the tokens by repository access. + - Use the **Permissions** dropdown to filter the tokens by permission. diff --git a/lib/graphql/static/changelog.json b/lib/graphql/static/changelog.json index 2e8061d85b..18efab4781 100644 --- a/lib/graphql/static/changelog.json +++ b/lib/graphql/static/changelog.json @@ -1,4 +1,48 @@ [ + { + "schemaChanges": [ + { + "title": "The GraphQL schema includes these changes:", + "changes": [ + "

Type 'ArchiveProjectV2ItemInput' was added

", + "

Type 'ArchiveProjectV2ItemPayload' was added

", + "

Type 'LinkProjectV2ToRepositoryInput' was added

", + "

Type 'LinkProjectV2ToRepositoryPayload' was added

", + "

Type 'UnarchiveProjectV2ItemInput' was added

", + "

Type 'UnarchiveProjectV2ItemPayload' was added

", + "

Type 'UnlinkProjectV2FromRepositoryInput' was added

", + "

Type 'UnlinkProjectV2FromRepositoryPayload' was added

", + "

Field lockAllowsFetchAndMerge was added to object type BranchProtectionRule

", + "

Field lockBranch was added to object type BranchProtectionRule

", + "

Field requireLastPushApproval was added to object type BranchProtectionRule

", + "

Input field lockAllowsFetchAndMerge was added to input object type CreateBranchProtectionRuleInput

", + "

Input field lockBranch was added to input object type CreateBranchProtectionRuleInput

", + "

Input field requireLastPushApproval was added to input object type CreateBranchProtectionRuleInput

", + "

Field 'archiveProjectV2Itemwas added to object typeMutation'

", + "

Field 'linkProjectV2ToRepositorywas added to object typeMutation'

", + "

Field 'unarchiveProjectV2Itemwas added to object typeMutation'

", + "

Field 'unlinkProjectV2FromRepositorywas added to object typeMutation'

", + "

Enum value 'TRACKED_BYwas added to enumProjectNextFieldType'

", + "

Enum value 'TRACKED_BYwas added to enumProjectV2FieldType'

", + "

Field hasDiscussionsEnabled was added to object type Repository

", + "

Input field lockAllowsFetchAndMerge was added to input object type UpdateBranchProtectionRuleInput

", + "

Input field lockBranch was added to input object type UpdateBranchProtectionRuleInput

", + "

Input field requireLastPushApproval was added to input object type UpdateBranchProtectionRuleInput

", + "

Input field hasDiscussionsEnabled was added to input object type UpdateRepositoryInput

" + ] + } + ], + "previewChanges": [], + "upcomingChanges": [ + { + "title": "The following changes will be made to the schema:", + "changes": [ + "

On member ProjectNextFieldType.TRACKED_BY:TRACKED_BY will be removed. Follow the ProjectV2 guide at https://github.blog/changelog/2022-06-23-the-new-github-issues-june-23rd-update/, to find a suitable replacement. Effective 2023-01-01.

" + ] + } + ], + "date": "2022-11-02" + }, { "schemaChanges": [ { diff --git a/lib/graphql/static/previews.json b/lib/graphql/static/previews.json index 62e69982c2..3d3725b9d1 100644 --- a/lib/graphql/static/previews.json +++ b/lib/graphql/static/previews.json @@ -297,6 +297,135 @@ "href": "/graphql/overview/schema-previews#team-review-assignments-preview" } ], + "ghes-3.7": [ + { + "title": "Access to package version deletion preview", + "description": "This preview adds support for the DeletePackageVersion mutation which enables deletion of private package versions.", + "toggled_by": "package-deletes-preview", + "toggled_on": [ + "Mutation.deletePackageVersion" + ], + "owning_teams": [ + "@github/pe-package-registry" + ], + "accept_header": "application/vnd.github.package-deletes-preview+json", + "href": "/graphql/overview/schema-previews#access-to-package-version-deletion-preview" + }, + { + "title": "Deployments preview", + "description": "This preview adds support for deployments mutations and new deployments features.", + "toggled_by": "flash-preview", + "toggled_on": [ + "DeploymentStatus.environment", + "Mutation.createDeploymentStatus", + "Mutation.createDeployment" + ], + "owning_teams": [ + "@github/c2c-actions-service" + ], + "accept_header": "application/vnd.github.flash-preview+json", + "href": "/graphql/overview/schema-previews#deployments-preview" + }, + { + "title": "Merge info preview", + "description": "This preview adds support for accessing fields that provide more detailed information about a pull request's merge state.", + "toggled_by": "merge-info-preview", + "toggled_on": [ + "PullRequest.canBeRebased", + "PullRequest.mergeStateStatus" + ], + "owning_teams": [ + "@github/pe-pull-requests" + ], + "accept_header": "application/vnd.github.merge-info-preview+json", + "href": "/graphql/overview/schema-previews#merge-info-preview" + }, + { + "title": "Update refs preview", + "description": "This preview adds support for updating multiple refs in a single operation.", + "toggled_by": "update-refs-preview", + "toggled_on": [ + "Mutation.updateRefs", + "GitRefname", + "RefUpdate" + ], + "owning_teams": [ + "@github/reponauts" + ], + "accept_header": "application/vnd.github.update-refs-preview+json", + "href": "/graphql/overview/schema-previews#update-refs-preview" + }, + { + "title": "Project event details preview", + "description": "This preview adds project, project card, and project column details to project-related issue events.", + "toggled_by": "starfox-preview", + "toggled_on": [ + "AddedToProjectEvent.project", + "AddedToProjectEvent.projectCard", + "AddedToProjectEvent.projectColumnName", + "ConvertedNoteToIssueEvent.project", + "ConvertedNoteToIssueEvent.projectCard", + "ConvertedNoteToIssueEvent.projectColumnName", + "MovedColumnsInProjectEvent.project", + "MovedColumnsInProjectEvent.projectCard", + "MovedColumnsInProjectEvent.projectColumnName", + "MovedColumnsInProjectEvent.previousProjectColumnName", + "RemovedFromProjectEvent.project", + "RemovedFromProjectEvent.projectColumnName" + ], + "owning_teams": [ + "@github/github-projects" + ], + "accept_header": "application/vnd.github.starfox-preview+json", + "href": "/graphql/overview/schema-previews#project-event-details-preview" + }, + { + "title": "Labels preview", + "description": "This preview adds support for adding, updating, creating and deleting labels.", + "toggled_by": "bane-preview", + "toggled_on": [ + "Mutation.createLabel", + "Mutation.deleteLabel", + "Mutation.updateLabel" + ], + "owning_teams": [ + "@github/pe-pull-requests" + ], + "accept_header": "application/vnd.github.bane-preview+json", + "href": "/graphql/overview/schema-previews#labels-preview" + }, + { + "title": "Import project preview", + "description": "This preview adds support for importing projects.", + "toggled_by": "slothette-preview", + "toggled_on": [ + "Mutation.importProject" + ], + "owning_teams": [ + "@github/pe-issues-projects" + ], + "accept_header": "application/vnd.github.slothette-preview+json", + "href": "/graphql/overview/schema-previews#import-project-preview" + }, + { + "title": "Team review assignments preview", + "description": "This preview adds support for updating the settings for team review assignment.", + "toggled_by": "stone-crop-preview", + "toggled_on": [ + "Mutation.updateTeamReviewAssignment", + "TeamReviewAssignmentAlgorithm", + "Team.reviewRequestDelegationEnabled", + "Team.reviewRequestDelegationAlgorithm", + "Team.reviewRequestDelegationMemberCount", + "Team.reviewRequestDelegationNotifyTeam" + ], + "owning_teams": [ + "@github/pe-pull-requests" + ], + "accept_header": "application/vnd.github.stone-crop-preview+json", + "href": "/graphql/overview/schema-previews#team-review-assignments-preview" + } + ], "ghes-3.6": [ { "title": "Access to package version deletion preview", @@ -826,148 +955,6 @@ "href": "/graphql/overview/schema-previews#team-review-assignments-preview" } ], - "ghes-3.2": [ - { - "title": "Access to package version deletion preview", - "description": "This preview adds support for the DeletePackageVersion mutation which enables deletion of private package versions.", - "toggled_by": "package-deletes-preview", - "toggled_on": [ - "Mutation.deletePackageVersion" - ], - "owning_teams": [ - "@github/pe-package-registry" - ], - "accept_header": "application/vnd.github.package-deletes-preview+json", - "href": "/graphql/overview/schema-previews#access-to-package-version-deletion-preview" - }, - { - "title": "Deployments preview", - "description": "This preview adds support for deployments mutations and new deployments features.", - "toggled_by": "flash-preview", - "toggled_on": [ - "DeploymentStatus.environment", - "Mutation.createDeploymentStatus", - "Mutation.createDeployment" - ], - "owning_teams": [ - "@github/c2c-actions-service" - ], - "accept_header": "application/vnd.github.flash-preview+json", - "href": "/graphql/overview/schema-previews#deployments-preview" - }, - { - "title": "Merge info preview", - "description": "This preview adds support for accessing fields that provide more detailed information about a pull request's merge state.", - "toggled_by": "merge-info-preview", - "toggled_on": [ - "PullRequest.canBeRebased", - "PullRequest.mergeStateStatus" - ], - "owning_teams": [ - "@github/pe-pull-requests" - ], - "accept_header": "application/vnd.github.merge-info-preview+json", - "href": "/graphql/overview/schema-previews#merge-info-preview" - }, - { - "title": "Update refs preview", - "description": "This preview adds support for updating multiple refs in a single operation.", - "toggled_by": "update-refs-preview", - "toggled_on": [ - "Mutation.updateRefs", - "GitRefname", - "RefUpdate" - ], - "owning_teams": [ - "@github/reponauts" - ], - "accept_header": "application/vnd.github.update-refs-preview+json", - "href": "/graphql/overview/schema-previews#update-refs-preview" - }, - { - "title": "Project event details preview", - "description": "This preview adds project, project card, and project column details to project-related issue events.", - "toggled_by": "starfox-preview", - "toggled_on": [ - "AddedToProjectEvent.project", - "AddedToProjectEvent.projectCard", - "AddedToProjectEvent.projectColumnName", - "ConvertedNoteToIssueEvent.project", - "ConvertedNoteToIssueEvent.projectCard", - "ConvertedNoteToIssueEvent.projectColumnName", - "MovedColumnsInProjectEvent.project", - "MovedColumnsInProjectEvent.projectCard", - "MovedColumnsInProjectEvent.projectColumnName", - "MovedColumnsInProjectEvent.previousProjectColumnName", - "RemovedFromProjectEvent.project", - "RemovedFromProjectEvent.projectColumnName" - ], - "owning_teams": [ - "@github/github-projects" - ], - "accept_header": "application/vnd.github.starfox-preview+json", - "href": "/graphql/overview/schema-previews#project-event-details-preview" - }, - { - "title": "Create content attachments preview", - "description": "This preview adds support for creating content attachments.", - "toggled_by": "corsair-preview", - "toggled_on": [ - "Mutation.createContentAttachment" - ], - "owning_teams": [ - "@github/feature-lifecycle" - ], - "accept_header": "application/vnd.github.corsair-preview+json", - "href": "/graphql/overview/schema-previews#create-content-attachments-preview" - }, - { - "title": "Labels preview", - "description": "This preview adds support for adding, updating, creating and deleting labels.", - "toggled_by": "bane-preview", - "toggled_on": [ - "Mutation.createLabel", - "Mutation.deleteLabel", - "Mutation.updateLabel" - ], - "owning_teams": [ - "@github/pe-pull-requests" - ], - "accept_header": "application/vnd.github.bane-preview+json", - "href": "/graphql/overview/schema-previews#labels-preview" - }, - { - "title": "Import project preview", - "description": "This preview adds support for importing projects.", - "toggled_by": "slothette-preview", - "toggled_on": [ - "Mutation.importProject" - ], - "owning_teams": [ - "@github/pe-issues-projects" - ], - "accept_header": "application/vnd.github.slothette-preview+json", - "href": "/graphql/overview/schema-previews#import-project-preview" - }, - { - "title": "Team review assignments preview", - "description": "This preview adds support for updating the settings for team review assignment.", - "toggled_by": "stone-crop-preview", - "toggled_on": [ - "Mutation.updateTeamReviewAssignment", - "TeamReviewAssignmentAlgorithm", - "Team.reviewRequestDelegationEnabled", - "Team.reviewRequestDelegationAlgorithm", - "Team.reviewRequestDelegationMemberCount", - "Team.reviewRequestDelegationNotifyTeam" - ], - "owning_teams": [ - "@github/pe-pull-requests" - ], - "accept_header": "application/vnd.github.stone-crop-preview+json", - "href": "/graphql/overview/schema-previews#team-review-assignments-preview" - } - ], "ghae": [ { "title": "Access to package version deletion preview", @@ -1096,134 +1083,5 @@ "accept_header": "application/vnd.github.stone-crop-preview+json", "href": "/graphql/overview/schema-previews#team-review-assignments-preview" } - ], - "ghes-3.7": [ - { - "title": "Access to package version deletion preview", - "description": "This preview adds support for the DeletePackageVersion mutation which enables deletion of private package versions.", - "toggled_by": "package-deletes-preview", - "toggled_on": [ - "Mutation.deletePackageVersion" - ], - "owning_teams": [ - "@github/pe-package-registry" - ], - "accept_header": "application/vnd.github.package-deletes-preview+json", - "href": "/graphql/overview/schema-previews#access-to-package-version-deletion-preview" - }, - { - "title": "Deployments preview", - "description": "This preview adds support for deployments mutations and new deployments features.", - "toggled_by": "flash-preview", - "toggled_on": [ - "DeploymentStatus.environment", - "Mutation.createDeploymentStatus", - "Mutation.createDeployment" - ], - "owning_teams": [ - "@github/c2c-actions-service" - ], - "accept_header": "application/vnd.github.flash-preview+json", - "href": "/graphql/overview/schema-previews#deployments-preview" - }, - { - "title": "Merge info preview", - "description": "This preview adds support for accessing fields that provide more detailed information about a pull request's merge state.", - "toggled_by": "merge-info-preview", - "toggled_on": [ - "PullRequest.canBeRebased", - "PullRequest.mergeStateStatus" - ], - "owning_teams": [ - "@github/pe-pull-requests" - ], - "accept_header": "application/vnd.github.merge-info-preview+json", - "href": "/graphql/overview/schema-previews#merge-info-preview" - }, - { - "title": "Update refs preview", - "description": "This preview adds support for updating multiple refs in a single operation.", - "toggled_by": "update-refs-preview", - "toggled_on": [ - "Mutation.updateRefs", - "GitRefname", - "RefUpdate" - ], - "owning_teams": [ - "@github/reponauts" - ], - "accept_header": "application/vnd.github.update-refs-preview+json", - "href": "/graphql/overview/schema-previews#update-refs-preview" - }, - { - "title": "Project event details preview", - "description": "This preview adds project, project card, and project column details to project-related issue events.", - "toggled_by": "starfox-preview", - "toggled_on": [ - "AddedToProjectEvent.project", - "AddedToProjectEvent.projectCard", - "AddedToProjectEvent.projectColumnName", - "ConvertedNoteToIssueEvent.project", - "ConvertedNoteToIssueEvent.projectCard", - "ConvertedNoteToIssueEvent.projectColumnName", - "MovedColumnsInProjectEvent.project", - "MovedColumnsInProjectEvent.projectCard", - "MovedColumnsInProjectEvent.projectColumnName", - "MovedColumnsInProjectEvent.previousProjectColumnName", - "RemovedFromProjectEvent.project", - "RemovedFromProjectEvent.projectColumnName" - ], - "owning_teams": [ - "@github/github-projects" - ], - "accept_header": "application/vnd.github.starfox-preview+json", - "href": "/graphql/overview/schema-previews#project-event-details-preview" - }, - { - "title": "Labels preview", - "description": "This preview adds support for adding, updating, creating and deleting labels.", - "toggled_by": "bane-preview", - "toggled_on": [ - "Mutation.createLabel", - "Mutation.deleteLabel", - "Mutation.updateLabel" - ], - "owning_teams": [ - "@github/pe-pull-requests" - ], - "accept_header": "application/vnd.github.bane-preview+json", - "href": "/graphql/overview/schema-previews#labels-preview" - }, - { - "title": "Import project preview", - "description": "This preview adds support for importing projects.", - "toggled_by": "slothette-preview", - "toggled_on": [ - "Mutation.importProject" - ], - "owning_teams": [ - "@github/pe-issues-projects" - ], - "accept_header": "application/vnd.github.slothette-preview+json", - "href": "/graphql/overview/schema-previews#import-project-preview" - }, - { - "title": "Team review assignments preview", - "description": "This preview adds support for updating the settings for team review assignment.", - "toggled_by": "stone-crop-preview", - "toggled_on": [ - "Mutation.updateTeamReviewAssignment", - "TeamReviewAssignmentAlgorithm", - "Team.reviewRequestDelegationEnabled", - "Team.reviewRequestDelegationAlgorithm", - "Team.reviewRequestDelegationMemberCount", - "Team.reviewRequestDelegationNotifyTeam" - ], - "owning_teams": [ - "@github/pe-pull-requests" - ], - "accept_header": "application/vnd.github.stone-crop-preview+json", - "href": "/graphql/overview/schema-previews#team-review-assignments-preview" - } ] } \ No newline at end of file diff --git a/lib/graphql/static/schema-dotcom.json b/lib/graphql/static/schema-dotcom.json index e8ef11d1b3..5e4f30e97a 100644 --- a/lib/graphql/static/schema-dotcom.json +++ b/lib/graphql/static/schema-dotcom.json @@ -1746,6 +1746,40 @@ } ] }, + { + "name": "archiveProjectV2Item", + "kind": "mutations", + "id": "archiveprojectv2item", + "href": "/graphql/reference/mutations#archiveprojectv2item", + "description": "

Archives a ProjectV2Item.

", + "inputFields": [ + { + "name": "input", + "type": "ArchiveProjectV2ItemInput!", + "id": "archiveprojectv2iteminput", + "kind": "input-objects", + "href": "/graphql/reference/input-objects#archiveprojectv2iteminput" + } + ], + "returnFields": [ + { + "name": "clientMutationId", + "type": "String", + "id": "string", + "kind": "scalars", + "href": "/graphql/reference/scalars#string", + "description": "

A unique identifier for the client performing the mutation.

" + }, + { + "name": "item", + "type": "ProjectV2Item", + "id": "projectv2item", + "kind": "objects", + "href": "/graphql/reference/objects#projectv2item", + "description": "

The item archived from the project.

" + } + ] + }, { "name": "archiveRepository", "kind": "mutations", @@ -4170,6 +4204,40 @@ } ] }, + { + "name": "linkProjectV2ToRepository", + "kind": "mutations", + "id": "linkprojectv2torepository", + "href": "/graphql/reference/mutations#linkprojectv2torepository", + "description": "

Links a project to a repository.

", + "inputFields": [ + { + "name": "input", + "type": "LinkProjectV2ToRepositoryInput!", + "id": "linkprojectv2torepositoryinput", + "kind": "input-objects", + "href": "/graphql/reference/input-objects#linkprojectv2torepositoryinput" + } + ], + "returnFields": [ + { + "name": "clientMutationId", + "type": "String", + "id": "string", + "kind": "scalars", + "href": "/graphql/reference/scalars#string", + "description": "

A unique identifier for the client performing the mutation.

" + }, + { + "name": "repository", + "type": "Repository", + "id": "repository", + "kind": "objects", + "href": "/graphql/reference/objects#repository", + "description": "

The repository the project is linked to.

" + } + ] + }, { "name": "linkRepositoryToProject", "kind": "mutations", @@ -5550,6 +5618,40 @@ } ] }, + { + "name": "unarchiveProjectV2Item", + "kind": "mutations", + "id": "unarchiveprojectv2item", + "href": "/graphql/reference/mutations#unarchiveprojectv2item", + "description": "

Unarchives a ProjectV2Item.

", + "inputFields": [ + { + "name": "input", + "type": "UnarchiveProjectV2ItemInput!", + "id": "unarchiveprojectv2iteminput", + "kind": "input-objects", + "href": "/graphql/reference/input-objects#unarchiveprojectv2iteminput" + } + ], + "returnFields": [ + { + "name": "clientMutationId", + "type": "String", + "id": "string", + "kind": "scalars", + "href": "/graphql/reference/scalars#string", + "description": "

A unique identifier for the client performing the mutation.

" + }, + { + "name": "item", + "type": "ProjectV2Item", + "id": "projectv2item", + "kind": "objects", + "href": "/graphql/reference/objects#projectv2item", + "description": "

The item unarchived from the project.

" + } + ] + }, { "name": "unarchiveRepository", "kind": "mutations", @@ -5652,6 +5754,40 @@ } ] }, + { + "name": "unlinkProjectV2FromRepository", + "kind": "mutations", + "id": "unlinkprojectv2fromrepository", + "href": "/graphql/reference/mutations#unlinkprojectv2fromrepository", + "description": "

Unlinks a project from a repository.

", + "inputFields": [ + { + "name": "input", + "type": "UnlinkProjectV2FromRepositoryInput!", + "id": "unlinkprojectv2fromrepositoryinput", + "kind": "input-objects", + "href": "/graphql/reference/input-objects#unlinkprojectv2fromrepositoryinput" + } + ], + "returnFields": [ + { + "name": "clientMutationId", + "type": "String", + "id": "string", + "kind": "scalars", + "href": "/graphql/reference/scalars#string", + "description": "

A unique identifier for the client performing the mutation.

" + }, + { + "name": "repository", + "type": "Repository", + "id": "repository", + "kind": "objects", + "href": "/graphql/reference/objects#repository", + "description": "

The repository the project is no longer linked to.

" + } + ] + }, { "name": "unlinkRepositoryFromProject", "kind": "mutations", @@ -9567,6 +9703,22 @@ "kind": "scalars", "href": "/graphql/reference/scalars#boolean" }, + { + "name": "lockAllowsFetchAndMerge", + "description": "

Whether users can pull changes from upstream when the branch is locked. Set to\ntrue to allow fork syncing. Set to false to prevent fork syncing.

", + "type": "Boolean!", + "id": "boolean", + "kind": "scalars", + "href": "/graphql/reference/scalars#boolean" + }, + { + "name": "lockBranch", + "description": "

Whether to set the branch as read-only. If this is true, users will not be able to push to the branch.

", + "type": "Boolean!", + "id": "boolean", + "kind": "scalars", + "href": "/graphql/reference/scalars#boolean" + }, { "name": "matchingRefs", "description": "

Repository refs that are protected by this rule.

", @@ -9693,6 +9845,14 @@ "kind": "objects", "href": "/graphql/reference/objects#repository" }, + { + "name": "requireLastPushApproval", + "description": "

Whether someone other than the person who last pushed to the branch must approve this pull request.

", + "type": "Boolean!", + "id": "boolean", + "kind": "scalars", + "href": "/graphql/reference/scalars#boolean" + }, { "name": "requiredApprovingReviewCount", "description": "

Number of approving reviews required to update matching branches.

", @@ -56223,6 +56383,14 @@ "kind": "objects", "href": "/graphql/reference/objects#fundinglink" }, + { + "name": "hasDiscussionsEnabled", + "description": "

Are discussions available on this repository?.

", + "type": "Boolean!", + "id": "boolean", + "kind": "scalars", + "href": "/graphql/reference/scalars#boolean" + }, { "name": "hasIssuesEnabled", "description": "

Indicates if the repository has issues feature enabled.

", @@ -77302,6 +77470,10 @@ "name": "TITLE", "description": "

Title.

" }, + { + "name": "TRACKED_BY", + "description": "

Tracked by.

" + }, { "name": "TRACKS", "description": "

Tracks.

" @@ -77472,6 +77644,10 @@ "name": "TITLE", "description": "

Title.

" }, + { + "name": "TRACKED_BY", + "description": "

Tracked by.

" + }, { "name": "TRACKS", "description": "

Tracks.

" @@ -82230,6 +82406,41 @@ } ] }, + { + "name": "ArchiveProjectV2ItemInput", + "kind": "inputObjects", + "id": "archiveprojectv2iteminput", + "href": "/graphql/reference/input-objects#archiveprojectv2iteminput", + "description": "

Autogenerated input type of ArchiveProjectV2Item.

", + "inputFields": [ + { + "name": "clientMutationId", + "description": "

A unique identifier for the client performing the mutation.

", + "type": "String", + "id": "string", + "kind": "scalars", + "href": "/graphql/reference/scalars#string" + }, + { + "name": "itemId", + "description": "

The ID of the ProjectV2Item to archive.

", + "type": "ID!", + "id": "id", + "kind": "scalars", + "href": "/graphql/reference/scalars#id", + "isDeprecated": false + }, + { + "name": "projectId", + "description": "

The ID of the Project to archive the item from.

", + "type": "ID!", + "id": "id", + "kind": "scalars", + "href": "/graphql/reference/scalars#id", + "isDeprecated": false + } + ] + }, { "name": "ArchiveRepositoryInput", "kind": "inputObjects", @@ -83273,6 +83484,22 @@ "kind": "scalars", "href": "/graphql/reference/scalars#boolean" }, + { + "name": "lockAllowsFetchAndMerge", + "description": "

Whether users can pull changes from upstream when the branch is locked. Set to\ntrue to allow fork syncing. Set to false to prevent fork syncing.

", + "type": "Boolean", + "id": "boolean", + "kind": "scalars", + "href": "/graphql/reference/scalars#boolean" + }, + { + "name": "lockBranch", + "description": "

Whether to set the branch as read-only. If this is true, users will not be able to push to the branch.

", + "type": "Boolean", + "id": "boolean", + "kind": "scalars", + "href": "/graphql/reference/scalars#boolean" + }, { "name": "pattern", "description": "

The glob-like pattern used to determine matching branches.

", @@ -83298,6 +83525,14 @@ "href": "/graphql/reference/scalars#id", "isDeprecated": false }, + { + "name": "requireLastPushApproval", + "description": "

Whether someone other than the person who last pushed to the branch must approve this pull request.

", + "type": "Boolean", + "id": "boolean", + "kind": "scalars", + "href": "/graphql/reference/scalars#boolean" + }, { "name": "requiredApprovingReviewCount", "description": "

Number of approving reviews required to update matching branches.

", @@ -86467,6 +86702,41 @@ } ] }, + { + "name": "LinkProjectV2ToRepositoryInput", + "kind": "inputObjects", + "id": "linkprojectv2torepositoryinput", + "href": "/graphql/reference/input-objects#linkprojectv2torepositoryinput", + "description": "

Autogenerated input type of LinkProjectV2ToRepository.

", + "inputFields": [ + { + "name": "clientMutationId", + "description": "

A unique identifier for the client performing the mutation.

", + "type": "String", + "id": "string", + "kind": "scalars", + "href": "/graphql/reference/scalars#string" + }, + { + "name": "projectId", + "description": "

The ID of the project to link to the repository.

", + "type": "ID!", + "id": "id", + "kind": "scalars", + "href": "/graphql/reference/scalars#id", + "isDeprecated": false + }, + { + "name": "repositoryId", + "description": "

The ID of the repository to link to the project.

", + "type": "ID!", + "id": "id", + "kind": "scalars", + "href": "/graphql/reference/scalars#id", + "isDeprecated": false + } + ] + }, { "name": "LinkRepositoryToProjectInput", "kind": "inputObjects", @@ -89005,6 +89275,41 @@ } ] }, + { + "name": "UnarchiveProjectV2ItemInput", + "kind": "inputObjects", + "id": "unarchiveprojectv2iteminput", + "href": "/graphql/reference/input-objects#unarchiveprojectv2iteminput", + "description": "

Autogenerated input type of UnarchiveProjectV2Item.

", + "inputFields": [ + { + "name": "clientMutationId", + "description": "

A unique identifier for the client performing the mutation.

", + "type": "String", + "id": "string", + "kind": "scalars", + "href": "/graphql/reference/scalars#string" + }, + { + "name": "itemId", + "description": "

The ID of the ProjectV2Item to unarchive.

", + "type": "ID!", + "id": "id", + "kind": "scalars", + "href": "/graphql/reference/scalars#id", + "isDeprecated": false + }, + { + "name": "projectId", + "description": "

The ID of the Project to archive the item from.

", + "type": "ID!", + "id": "id", + "kind": "scalars", + "href": "/graphql/reference/scalars#id", + "isDeprecated": false + } + ] + }, { "name": "UnarchiveRepositoryInput", "kind": "inputObjects", @@ -89083,6 +89388,41 @@ } ] }, + { + "name": "UnlinkProjectV2FromRepositoryInput", + "kind": "inputObjects", + "id": "unlinkprojectv2fromrepositoryinput", + "href": "/graphql/reference/input-objects#unlinkprojectv2fromrepositoryinput", + "description": "

Autogenerated input type of UnlinkProjectV2FromRepository.

", + "inputFields": [ + { + "name": "clientMutationId", + "description": "

A unique identifier for the client performing the mutation.

", + "type": "String", + "id": "string", + "kind": "scalars", + "href": "/graphql/reference/scalars#string" + }, + { + "name": "projectId", + "description": "

The ID of the project to unlink from the repository.

", + "type": "ID!", + "id": "id", + "kind": "scalars", + "href": "/graphql/reference/scalars#id", + "isDeprecated": false + }, + { + "name": "repositoryId", + "description": "

The ID of the repository to unlink from the project.

", + "type": "ID!", + "id": "id", + "kind": "scalars", + "href": "/graphql/reference/scalars#id", + "isDeprecated": false + } + ] + }, { "name": "UnlinkRepositoryFromProjectInput", "kind": "inputObjects", @@ -89397,6 +89737,22 @@ "kind": "scalars", "href": "/graphql/reference/scalars#boolean" }, + { + "name": "lockAllowsFetchAndMerge", + "description": "

Whether users can pull changes from upstream when the branch is locked. Set to\ntrue to allow fork syncing. Set to false to prevent fork syncing.

", + "type": "Boolean", + "id": "boolean", + "kind": "scalars", + "href": "/graphql/reference/scalars#boolean" + }, + { + "name": "lockBranch", + "description": "

Whether to set the branch as read-only. If this is true, users will not be able to push to the branch.

", + "type": "Boolean", + "id": "boolean", + "kind": "scalars", + "href": "/graphql/reference/scalars#boolean" + }, { "name": "pattern", "description": "

The glob-like pattern used to determine matching branches.

", @@ -89413,6 +89769,14 @@ "kind": "scalars", "href": "/graphql/reference/scalars#id" }, + { + "name": "requireLastPushApproval", + "description": "

Whether someone other than the person who last pushed to the branch must approve this pull request.

", + "type": "Boolean", + "id": "boolean", + "kind": "scalars", + "href": "/graphql/reference/scalars#boolean" + }, { "name": "requiredApprovingReviewCount", "description": "

Number of approving reviews required to update matching branches.

", @@ -91685,6 +92049,14 @@ "kind": "scalars", "href": "/graphql/reference/scalars#string" }, + { + "name": "hasDiscussionsEnabled", + "description": "

Indicates if the repository should have the discussions feature enabled.

", + "type": "Boolean", + "id": "boolean", + "kind": "scalars", + "href": "/graphql/reference/scalars#boolean" + }, { "name": "hasIssuesEnabled", "description": "

Indicates if the repository should have the issues feature enabled.

", diff --git a/lib/graphql/static/schema-ghae.json b/lib/graphql/static/schema-ghae.json index 33ff30bee2..1537355158 100644 --- a/lib/graphql/static/schema-ghae.json +++ b/lib/graphql/static/schema-ghae.json @@ -7860,6 +7860,22 @@ "kind": "scalars", "href": "/graphql/reference/scalars#boolean" }, + { + "name": "lockAllowsFetchAndMerge", + "description": "

Whether users can pull changes from upstream when the branch is locked. Set to\ntrue to allow fork syncing. Set to false to prevent fork syncing.

", + "type": "Boolean!", + "id": "boolean", + "kind": "scalars", + "href": "/graphql/reference/scalars#boolean" + }, + { + "name": "lockBranch", + "description": "

Whether to set the branch as read-only. If this is true, users will not be able to push to the branch.

", + "type": "Boolean!", + "id": "boolean", + "kind": "scalars", + "href": "/graphql/reference/scalars#boolean" + }, { "name": "matchingRefs", "description": "

Repository refs that are protected by this rule.

", @@ -7986,6 +8002,14 @@ "kind": "objects", "href": "/graphql/reference/objects#repository" }, + { + "name": "requireLastPushApproval", + "description": "

Whether someone other than the person who last pushed to the branch must approve this pull request.

", + "type": "Boolean!", + "id": "boolean", + "kind": "scalars", + "href": "/graphql/reference/scalars#boolean" + }, { "name": "requiredApprovingReviewCount", "description": "

Number of approving reviews required to update matching branches.

", @@ -46029,6 +46053,14 @@ "kind": "scalars", "href": "/graphql/reference/scalars#boolean" }, + { + "name": "hasDiscussionsEnabled", + "description": "

Are discussions available on this repository?.

", + "type": "Boolean!", + "id": "boolean", + "kind": "scalars", + "href": "/graphql/reference/scalars#boolean" + }, { "name": "hasIssuesEnabled", "description": "

Indicates if the repository has issues feature enabled.

", @@ -67768,6 +67800,22 @@ "kind": "scalars", "href": "/graphql/reference/scalars#boolean" }, + { + "name": "lockAllowsFetchAndMerge", + "description": "

Whether users can pull changes from upstream when the branch is locked. Set to\ntrue to allow fork syncing. Set to false to prevent fork syncing.

", + "type": "Boolean", + "id": "boolean", + "kind": "scalars", + "href": "/graphql/reference/scalars#boolean" + }, + { + "name": "lockBranch", + "description": "

Whether to set the branch as read-only. If this is true, users will not be able to push to the branch.

", + "type": "Boolean", + "id": "boolean", + "kind": "scalars", + "href": "/graphql/reference/scalars#boolean" + }, { "name": "pattern", "description": "

The glob-like pattern used to determine matching branches.

", @@ -67793,6 +67841,14 @@ "href": "/graphql/reference/scalars#id", "isDeprecated": false }, + { + "name": "requireLastPushApproval", + "description": "

Whether someone other than the person who last pushed to the branch must approve this pull request.

", + "type": "Boolean", + "id": "boolean", + "kind": "scalars", + "href": "/graphql/reference/scalars#boolean" + }, { "name": "requiredApprovingReviewCount", "description": "

Number of approving reviews required to update matching branches.

", @@ -72582,6 +72638,22 @@ "kind": "scalars", "href": "/graphql/reference/scalars#boolean" }, + { + "name": "lockAllowsFetchAndMerge", + "description": "

Whether users can pull changes from upstream when the branch is locked. Set to\ntrue to allow fork syncing. Set to false to prevent fork syncing.

", + "type": "Boolean", + "id": "boolean", + "kind": "scalars", + "href": "/graphql/reference/scalars#boolean" + }, + { + "name": "lockBranch", + "description": "

Whether to set the branch as read-only. If this is true, users will not be able to push to the branch.

", + "type": "Boolean", + "id": "boolean", + "kind": "scalars", + "href": "/graphql/reference/scalars#boolean" + }, { "name": "pattern", "description": "

The glob-like pattern used to determine matching branches.

", @@ -72598,6 +72670,14 @@ "kind": "scalars", "href": "/graphql/reference/scalars#id" }, + { + "name": "requireLastPushApproval", + "description": "

Whether someone other than the person who last pushed to the branch must approve this pull request.

", + "type": "Boolean", + "id": "boolean", + "kind": "scalars", + "href": "/graphql/reference/scalars#boolean" + }, { "name": "requiredApprovingReviewCount", "description": "

Number of approving reviews required to update matching branches.

", @@ -74412,6 +74492,14 @@ "kind": "scalars", "href": "/graphql/reference/scalars#string" }, + { + "name": "hasDiscussionsEnabled", + "description": "

Indicates if the repository should have the discussions feature enabled.

", + "type": "Boolean", + "id": "boolean", + "kind": "scalars", + "href": "/graphql/reference/scalars#boolean" + }, { "name": "hasIssuesEnabled", "description": "

Indicates if the repository should have the issues feature enabled.

", diff --git a/lib/graphql/static/schema-ghec.json b/lib/graphql/static/schema-ghec.json index e8ef11d1b3..5e4f30e97a 100644 --- a/lib/graphql/static/schema-ghec.json +++ b/lib/graphql/static/schema-ghec.json @@ -1746,6 +1746,40 @@ } ] }, + { + "name": "archiveProjectV2Item", + "kind": "mutations", + "id": "archiveprojectv2item", + "href": "/graphql/reference/mutations#archiveprojectv2item", + "description": "

Archives a ProjectV2Item.

", + "inputFields": [ + { + "name": "input", + "type": "ArchiveProjectV2ItemInput!", + "id": "archiveprojectv2iteminput", + "kind": "input-objects", + "href": "/graphql/reference/input-objects#archiveprojectv2iteminput" + } + ], + "returnFields": [ + { + "name": "clientMutationId", + "type": "String", + "id": "string", + "kind": "scalars", + "href": "/graphql/reference/scalars#string", + "description": "

A unique identifier for the client performing the mutation.

" + }, + { + "name": "item", + "type": "ProjectV2Item", + "id": "projectv2item", + "kind": "objects", + "href": "/graphql/reference/objects#projectv2item", + "description": "

The item archived from the project.

" + } + ] + }, { "name": "archiveRepository", "kind": "mutations", @@ -4170,6 +4204,40 @@ } ] }, + { + "name": "linkProjectV2ToRepository", + "kind": "mutations", + "id": "linkprojectv2torepository", + "href": "/graphql/reference/mutations#linkprojectv2torepository", + "description": "

Links a project to a repository.

", + "inputFields": [ + { + "name": "input", + "type": "LinkProjectV2ToRepositoryInput!", + "id": "linkprojectv2torepositoryinput", + "kind": "input-objects", + "href": "/graphql/reference/input-objects#linkprojectv2torepositoryinput" + } + ], + "returnFields": [ + { + "name": "clientMutationId", + "type": "String", + "id": "string", + "kind": "scalars", + "href": "/graphql/reference/scalars#string", + "description": "

A unique identifier for the client performing the mutation.

" + }, + { + "name": "repository", + "type": "Repository", + "id": "repository", + "kind": "objects", + "href": "/graphql/reference/objects#repository", + "description": "

The repository the project is linked to.

" + } + ] + }, { "name": "linkRepositoryToProject", "kind": "mutations", @@ -5550,6 +5618,40 @@ } ] }, + { + "name": "unarchiveProjectV2Item", + "kind": "mutations", + "id": "unarchiveprojectv2item", + "href": "/graphql/reference/mutations#unarchiveprojectv2item", + "description": "

Unarchives a ProjectV2Item.

", + "inputFields": [ + { + "name": "input", + "type": "UnarchiveProjectV2ItemInput!", + "id": "unarchiveprojectv2iteminput", + "kind": "input-objects", + "href": "/graphql/reference/input-objects#unarchiveprojectv2iteminput" + } + ], + "returnFields": [ + { + "name": "clientMutationId", + "type": "String", + "id": "string", + "kind": "scalars", + "href": "/graphql/reference/scalars#string", + "description": "

A unique identifier for the client performing the mutation.

" + }, + { + "name": "item", + "type": "ProjectV2Item", + "id": "projectv2item", + "kind": "objects", + "href": "/graphql/reference/objects#projectv2item", + "description": "

The item unarchived from the project.

" + } + ] + }, { "name": "unarchiveRepository", "kind": "mutations", @@ -5652,6 +5754,40 @@ } ] }, + { + "name": "unlinkProjectV2FromRepository", + "kind": "mutations", + "id": "unlinkprojectv2fromrepository", + "href": "/graphql/reference/mutations#unlinkprojectv2fromrepository", + "description": "

Unlinks a project from a repository.

", + "inputFields": [ + { + "name": "input", + "type": "UnlinkProjectV2FromRepositoryInput!", + "id": "unlinkprojectv2fromrepositoryinput", + "kind": "input-objects", + "href": "/graphql/reference/input-objects#unlinkprojectv2fromrepositoryinput" + } + ], + "returnFields": [ + { + "name": "clientMutationId", + "type": "String", + "id": "string", + "kind": "scalars", + "href": "/graphql/reference/scalars#string", + "description": "

A unique identifier for the client performing the mutation.

" + }, + { + "name": "repository", + "type": "Repository", + "id": "repository", + "kind": "objects", + "href": "/graphql/reference/objects#repository", + "description": "

The repository the project is no longer linked to.

" + } + ] + }, { "name": "unlinkRepositoryFromProject", "kind": "mutations", @@ -9567,6 +9703,22 @@ "kind": "scalars", "href": "/graphql/reference/scalars#boolean" }, + { + "name": "lockAllowsFetchAndMerge", + "description": "

Whether users can pull changes from upstream when the branch is locked. Set to\ntrue to allow fork syncing. Set to false to prevent fork syncing.

", + "type": "Boolean!", + "id": "boolean", + "kind": "scalars", + "href": "/graphql/reference/scalars#boolean" + }, + { + "name": "lockBranch", + "description": "

Whether to set the branch as read-only. If this is true, users will not be able to push to the branch.

", + "type": "Boolean!", + "id": "boolean", + "kind": "scalars", + "href": "/graphql/reference/scalars#boolean" + }, { "name": "matchingRefs", "description": "

Repository refs that are protected by this rule.

", @@ -9693,6 +9845,14 @@ "kind": "objects", "href": "/graphql/reference/objects#repository" }, + { + "name": "requireLastPushApproval", + "description": "

Whether someone other than the person who last pushed to the branch must approve this pull request.

", + "type": "Boolean!", + "id": "boolean", + "kind": "scalars", + "href": "/graphql/reference/scalars#boolean" + }, { "name": "requiredApprovingReviewCount", "description": "

Number of approving reviews required to update matching branches.

", @@ -56223,6 +56383,14 @@ "kind": "objects", "href": "/graphql/reference/objects#fundinglink" }, + { + "name": "hasDiscussionsEnabled", + "description": "

Are discussions available on this repository?.

", + "type": "Boolean!", + "id": "boolean", + "kind": "scalars", + "href": "/graphql/reference/scalars#boolean" + }, { "name": "hasIssuesEnabled", "description": "

Indicates if the repository has issues feature enabled.

", @@ -77302,6 +77470,10 @@ "name": "TITLE", "description": "

Title.

" }, + { + "name": "TRACKED_BY", + "description": "

Tracked by.

" + }, { "name": "TRACKS", "description": "

Tracks.

" @@ -77472,6 +77644,10 @@ "name": "TITLE", "description": "

Title.

" }, + { + "name": "TRACKED_BY", + "description": "

Tracked by.

" + }, { "name": "TRACKS", "description": "

Tracks.

" @@ -82230,6 +82406,41 @@ } ] }, + { + "name": "ArchiveProjectV2ItemInput", + "kind": "inputObjects", + "id": "archiveprojectv2iteminput", + "href": "/graphql/reference/input-objects#archiveprojectv2iteminput", + "description": "

Autogenerated input type of ArchiveProjectV2Item.

", + "inputFields": [ + { + "name": "clientMutationId", + "description": "

A unique identifier for the client performing the mutation.

", + "type": "String", + "id": "string", + "kind": "scalars", + "href": "/graphql/reference/scalars#string" + }, + { + "name": "itemId", + "description": "

The ID of the ProjectV2Item to archive.

", + "type": "ID!", + "id": "id", + "kind": "scalars", + "href": "/graphql/reference/scalars#id", + "isDeprecated": false + }, + { + "name": "projectId", + "description": "

The ID of the Project to archive the item from.

", + "type": "ID!", + "id": "id", + "kind": "scalars", + "href": "/graphql/reference/scalars#id", + "isDeprecated": false + } + ] + }, { "name": "ArchiveRepositoryInput", "kind": "inputObjects", @@ -83273,6 +83484,22 @@ "kind": "scalars", "href": "/graphql/reference/scalars#boolean" }, + { + "name": "lockAllowsFetchAndMerge", + "description": "

Whether users can pull changes from upstream when the branch is locked. Set to\ntrue to allow fork syncing. Set to false to prevent fork syncing.

", + "type": "Boolean", + "id": "boolean", + "kind": "scalars", + "href": "/graphql/reference/scalars#boolean" + }, + { + "name": "lockBranch", + "description": "

Whether to set the branch as read-only. If this is true, users will not be able to push to the branch.

", + "type": "Boolean", + "id": "boolean", + "kind": "scalars", + "href": "/graphql/reference/scalars#boolean" + }, { "name": "pattern", "description": "

The glob-like pattern used to determine matching branches.

", @@ -83298,6 +83525,14 @@ "href": "/graphql/reference/scalars#id", "isDeprecated": false }, + { + "name": "requireLastPushApproval", + "description": "

Whether someone other than the person who last pushed to the branch must approve this pull request.

", + "type": "Boolean", + "id": "boolean", + "kind": "scalars", + "href": "/graphql/reference/scalars#boolean" + }, { "name": "requiredApprovingReviewCount", "description": "

Number of approving reviews required to update matching branches.

", @@ -86467,6 +86702,41 @@ } ] }, + { + "name": "LinkProjectV2ToRepositoryInput", + "kind": "inputObjects", + "id": "linkprojectv2torepositoryinput", + "href": "/graphql/reference/input-objects#linkprojectv2torepositoryinput", + "description": "

Autogenerated input type of LinkProjectV2ToRepository.

", + "inputFields": [ + { + "name": "clientMutationId", + "description": "

A unique identifier for the client performing the mutation.

", + "type": "String", + "id": "string", + "kind": "scalars", + "href": "/graphql/reference/scalars#string" + }, + { + "name": "projectId", + "description": "

The ID of the project to link to the repository.

", + "type": "ID!", + "id": "id", + "kind": "scalars", + "href": "/graphql/reference/scalars#id", + "isDeprecated": false + }, + { + "name": "repositoryId", + "description": "

The ID of the repository to link to the project.

", + "type": "ID!", + "id": "id", + "kind": "scalars", + "href": "/graphql/reference/scalars#id", + "isDeprecated": false + } + ] + }, { "name": "LinkRepositoryToProjectInput", "kind": "inputObjects", @@ -89005,6 +89275,41 @@ } ] }, + { + "name": "UnarchiveProjectV2ItemInput", + "kind": "inputObjects", + "id": "unarchiveprojectv2iteminput", + "href": "/graphql/reference/input-objects#unarchiveprojectv2iteminput", + "description": "

Autogenerated input type of UnarchiveProjectV2Item.

", + "inputFields": [ + { + "name": "clientMutationId", + "description": "

A unique identifier for the client performing the mutation.

", + "type": "String", + "id": "string", + "kind": "scalars", + "href": "/graphql/reference/scalars#string" + }, + { + "name": "itemId", + "description": "

The ID of the ProjectV2Item to unarchive.

", + "type": "ID!", + "id": "id", + "kind": "scalars", + "href": "/graphql/reference/scalars#id", + "isDeprecated": false + }, + { + "name": "projectId", + "description": "

The ID of the Project to archive the item from.

", + "type": "ID!", + "id": "id", + "kind": "scalars", + "href": "/graphql/reference/scalars#id", + "isDeprecated": false + } + ] + }, { "name": "UnarchiveRepositoryInput", "kind": "inputObjects", @@ -89083,6 +89388,41 @@ } ] }, + { + "name": "UnlinkProjectV2FromRepositoryInput", + "kind": "inputObjects", + "id": "unlinkprojectv2fromrepositoryinput", + "href": "/graphql/reference/input-objects#unlinkprojectv2fromrepositoryinput", + "description": "

Autogenerated input type of UnlinkProjectV2FromRepository.

", + "inputFields": [ + { + "name": "clientMutationId", + "description": "

A unique identifier for the client performing the mutation.

", + "type": "String", + "id": "string", + "kind": "scalars", + "href": "/graphql/reference/scalars#string" + }, + { + "name": "projectId", + "description": "

The ID of the project to unlink from the repository.

", + "type": "ID!", + "id": "id", + "kind": "scalars", + "href": "/graphql/reference/scalars#id", + "isDeprecated": false + }, + { + "name": "repositoryId", + "description": "

The ID of the repository to unlink from the project.

", + "type": "ID!", + "id": "id", + "kind": "scalars", + "href": "/graphql/reference/scalars#id", + "isDeprecated": false + } + ] + }, { "name": "UnlinkRepositoryFromProjectInput", "kind": "inputObjects", @@ -89397,6 +89737,22 @@ "kind": "scalars", "href": "/graphql/reference/scalars#boolean" }, + { + "name": "lockAllowsFetchAndMerge", + "description": "

Whether users can pull changes from upstream when the branch is locked. Set to\ntrue to allow fork syncing. Set to false to prevent fork syncing.

", + "type": "Boolean", + "id": "boolean", + "kind": "scalars", + "href": "/graphql/reference/scalars#boolean" + }, + { + "name": "lockBranch", + "description": "

Whether to set the branch as read-only. If this is true, users will not be able to push to the branch.

", + "type": "Boolean", + "id": "boolean", + "kind": "scalars", + "href": "/graphql/reference/scalars#boolean" + }, { "name": "pattern", "description": "

The glob-like pattern used to determine matching branches.

", @@ -89413,6 +89769,14 @@ "kind": "scalars", "href": "/graphql/reference/scalars#id" }, + { + "name": "requireLastPushApproval", + "description": "

Whether someone other than the person who last pushed to the branch must approve this pull request.

", + "type": "Boolean", + "id": "boolean", + "kind": "scalars", + "href": "/graphql/reference/scalars#boolean" + }, { "name": "requiredApprovingReviewCount", "description": "

Number of approving reviews required to update matching branches.

", @@ -91685,6 +92049,14 @@ "kind": "scalars", "href": "/graphql/reference/scalars#string" }, + { + "name": "hasDiscussionsEnabled", + "description": "

Indicates if the repository should have the discussions feature enabled.

", + "type": "Boolean", + "id": "boolean", + "kind": "scalars", + "href": "/graphql/reference/scalars#boolean" + }, { "name": "hasIssuesEnabled", "description": "

Indicates if the repository should have the issues feature enabled.

", diff --git a/lib/graphql/static/schema-ghes-3.7.json b/lib/graphql/static/schema-ghes-3.7.json index a844450d2d..c7d6ee6a29 100644 --- a/lib/graphql/static/schema-ghes-3.7.json +++ b/lib/graphql/static/schema-ghes-3.7.json @@ -741,6 +741,40 @@ } ] }, + { + "name": "addDiscussionPollVote", + "kind": "mutations", + "id": "adddiscussionpollvote", + "href": "/graphql/reference/mutations#adddiscussionpollvote", + "description": "

Vote for an option in a discussion poll.

", + "inputFields": [ + { + "name": "input", + "type": "AddDiscussionPollVoteInput!", + "id": "adddiscussionpollvoteinput", + "kind": "input-objects", + "href": "/graphql/reference/input-objects#adddiscussionpollvoteinput" + } + ], + "returnFields": [ + { + "name": "clientMutationId", + "type": "String", + "id": "string", + "kind": "scalars", + "href": "/graphql/reference/scalars#string", + "description": "

A unique identifier for the client performing the mutation.

" + }, + { + "name": "pollOption", + "type": "DiscussionPollOption", + "id": "discussionpolloption", + "kind": "objects", + "href": "/graphql/reference/objects#discussionpolloption", + "description": "

The poll option that a vote was added to.

" + } + ] + }, { "name": "addEnterpriseAdmin", "kind": "mutations", @@ -917,6 +951,74 @@ } ] }, + { + "name": "addProjectV2DraftIssue", + "kind": "mutations", + "id": "addprojectv2draftissue", + "href": "/graphql/reference/mutations#addprojectv2draftissue", + "description": "

Creates a new draft issue and add it to a Project.

", + "inputFields": [ + { + "name": "input", + "type": "AddProjectV2DraftIssueInput!", + "id": "addprojectv2draftissueinput", + "kind": "input-objects", + "href": "/graphql/reference/input-objects#addprojectv2draftissueinput" + } + ], + "returnFields": [ + { + "name": "clientMutationId", + "type": "String", + "id": "string", + "kind": "scalars", + "href": "/graphql/reference/scalars#string", + "description": "

A unique identifier for the client performing the mutation.

" + }, + { + "name": "projectItem", + "type": "ProjectV2Item", + "id": "projectv2item", + "kind": "objects", + "href": "/graphql/reference/objects#projectv2item", + "description": "

The draft issue added to the project.

" + } + ] + }, + { + "name": "addProjectV2ItemById", + "kind": "mutations", + "id": "addprojectv2itembyid", + "href": "/graphql/reference/mutations#addprojectv2itembyid", + "description": "

Links an existing content instance to a Project.

", + "inputFields": [ + { + "name": "input", + "type": "AddProjectV2ItemByIdInput!", + "id": "addprojectv2itembyidinput", + "kind": "input-objects", + "href": "/graphql/reference/input-objects#addprojectv2itembyidinput" + } + ], + "returnFields": [ + { + "name": "clientMutationId", + "type": "String", + "id": "string", + "kind": "scalars", + "href": "/graphql/reference/scalars#string", + "description": "

A unique identifier for the client performing the mutation.

" + }, + { + "name": "item", + "type": "ProjectV2Item", + "id": "projectv2item", + "kind": "objects", + "href": "/graphql/reference/objects#projectv2item", + "description": "

The item added to the project.

" + } + ] + }, { "name": "addPullRequestReview", "kind": "mutations", @@ -2109,6 +2211,40 @@ } ] }, + { + "name": "createProjectV2", + "kind": "mutations", + "id": "createprojectv2", + "href": "/graphql/reference/mutations#createprojectv2", + "description": "

Creates a new project.

", + "inputFields": [ + { + "name": "input", + "type": "CreateProjectV2Input!", + "id": "createprojectv2input", + "kind": "input-objects", + "href": "/graphql/reference/input-objects#createprojectv2input" + } + ], + "returnFields": [ + { + "name": "clientMutationId", + "type": "String", + "id": "string", + "kind": "scalars", + "href": "/graphql/reference/scalars#string", + "description": "

A unique identifier for the client performing the mutation.

" + }, + { + "name": "projectV2", + "type": "ProjectV2", + "id": "projectv2", + "kind": "objects", + "href": "/graphql/reference/objects#projectv2", + "description": "

The new project.

" + } + ] + }, { "name": "createPullRequest", "kind": "mutations", @@ -2727,6 +2863,40 @@ } ] }, + { + "name": "deleteProjectV2Item", + "kind": "mutations", + "id": "deleteprojectv2item", + "href": "/graphql/reference/mutations#deleteprojectv2item", + "description": "

Deletes an item from a Project.

", + "inputFields": [ + { + "name": "input", + "type": "DeleteProjectV2ItemInput!", + "id": "deleteprojectv2iteminput", + "kind": "input-objects", + "href": "/graphql/reference/input-objects#deleteprojectv2iteminput" + } + ], + "returnFields": [ + { + "name": "clientMutationId", + "type": "String", + "id": "string", + "kind": "scalars", + "href": "/graphql/reference/scalars#string", + "description": "

A unique identifier for the client performing the mutation.

" + }, + { + "name": "deletedItemId", + "type": "ID", + "id": "id", + "kind": "scalars", + "href": "/graphql/reference/scalars#id", + "description": "

The ID of the deleted item.

" + } + ] + }, { "name": "deletePullRequestReview", "kind": "mutations", @@ -4730,7 +4900,7 @@ "kind": "mutations", "id": "updatebranchprotectionrule", "href": "/graphql/reference/mutations#updatebranchprotectionrule", - "description": "

Create a new branch protection rule.

", + "description": "

Update a branch protection rule.

", "inputFields": [ { "name": "input", @@ -5889,6 +6059,48 @@ } ] }, + { + "name": "updateOrganizationWebCommitSignoffSetting", + "kind": "mutations", + "id": "updateorganizationwebcommitsignoffsetting", + "href": "/graphql/reference/mutations#updateorganizationwebcommitsignoffsetting", + "description": "

Sets whether contributors are required to sign off on web-based commits for repositories in an organization.

", + "inputFields": [ + { + "name": "input", + "type": "UpdateOrganizationWebCommitSignoffSettingInput!", + "id": "updateorganizationwebcommitsignoffsettinginput", + "kind": "input-objects", + "href": "/graphql/reference/input-objects#updateorganizationwebcommitsignoffsettinginput" + } + ], + "returnFields": [ + { + "name": "clientMutationId", + "type": "String", + "id": "string", + "kind": "scalars", + "href": "/graphql/reference/scalars#string", + "description": "

A unique identifier for the client performing the mutation.

" + }, + { + "name": "message", + "type": "String", + "id": "string", + "kind": "scalars", + "href": "/graphql/reference/scalars#string", + "description": "

A message confirming the result of updating the web commit signoff setting.

" + }, + { + "name": "organization", + "type": "Organization", + "id": "organization", + "kind": "objects", + "href": "/graphql/reference/objects#organization", + "description": "

The organization with the updated web commit signoff setting.

" + } + ] + }, { "name": "updateProject", "kind": "mutations", @@ -5991,6 +6203,142 @@ } ] }, + { + "name": "updateProjectV2", + "kind": "mutations", + "id": "updateprojectv2", + "href": "/graphql/reference/mutations#updateprojectv2", + "description": "

Updates an existing project (beta).

", + "inputFields": [ + { + "name": "input", + "type": "UpdateProjectV2Input!", + "id": "updateprojectv2input", + "kind": "input-objects", + "href": "/graphql/reference/input-objects#updateprojectv2input" + } + ], + "returnFields": [ + { + "name": "clientMutationId", + "type": "String", + "id": "string", + "kind": "scalars", + "href": "/graphql/reference/scalars#string", + "description": "

A unique identifier for the client performing the mutation.

" + }, + { + "name": "projectV2", + "type": "ProjectV2", + "id": "projectv2", + "kind": "objects", + "href": "/graphql/reference/objects#projectv2", + "description": "

The updated Project.

" + } + ] + }, + { + "name": "updateProjectV2DraftIssue", + "kind": "mutations", + "id": "updateprojectv2draftissue", + "href": "/graphql/reference/mutations#updateprojectv2draftissue", + "description": "

Updates a draft issue within a Project.

", + "inputFields": [ + { + "name": "input", + "type": "UpdateProjectV2DraftIssueInput!", + "id": "updateprojectv2draftissueinput", + "kind": "input-objects", + "href": "/graphql/reference/input-objects#updateprojectv2draftissueinput" + } + ], + "returnFields": [ + { + "name": "clientMutationId", + "type": "String", + "id": "string", + "kind": "scalars", + "href": "/graphql/reference/scalars#string", + "description": "

A unique identifier for the client performing the mutation.

" + }, + { + "name": "draftIssue", + "type": "DraftIssue", + "id": "draftissue", + "kind": "objects", + "href": "/graphql/reference/objects#draftissue", + "description": "

The draft issue updated in the project.

" + } + ] + }, + { + "name": "updateProjectV2ItemFieldValue", + "kind": "mutations", + "id": "updateprojectv2itemfieldvalue", + "href": "/graphql/reference/mutations#updateprojectv2itemfieldvalue", + "description": "

This mutation updates the value of a field for an item in a Project. Currently\nonly single-select, text, number, date, and iteration fields are supported.

", + "inputFields": [ + { + "name": "input", + "type": "UpdateProjectV2ItemFieldValueInput!", + "id": "updateprojectv2itemfieldvalueinput", + "kind": "input-objects", + "href": "/graphql/reference/input-objects#updateprojectv2itemfieldvalueinput" + } + ], + "returnFields": [ + { + "name": "clientMutationId", + "type": "String", + "id": "string", + "kind": "scalars", + "href": "/graphql/reference/scalars#string", + "description": "

A unique identifier for the client performing the mutation.

" + }, + { + "name": "projectV2Item", + "type": "ProjectV2Item", + "id": "projectv2item", + "kind": "objects", + "href": "/graphql/reference/objects#projectv2item", + "description": "

The updated item.

" + } + ] + }, + { + "name": "updateProjectV2ItemPosition", + "kind": "mutations", + "id": "updateprojectv2itemposition", + "href": "/graphql/reference/mutations#updateprojectv2itemposition", + "description": "

This mutation updates the position of the item in the project, where the position represents the priority of an item.

", + "inputFields": [ + { + "name": "input", + "type": "UpdateProjectV2ItemPositionInput!", + "id": "updateprojectv2itempositioninput", + "kind": "input-objects", + "href": "/graphql/reference/input-objects#updateprojectv2itempositioninput" + } + ], + "returnFields": [ + { + "name": "clientMutationId", + "type": "String", + "id": "string", + "kind": "scalars", + "href": "/graphql/reference/scalars#string", + "description": "

A unique identifier for the client performing the mutation.

" + }, + { + "name": "items", + "type": "ProjectV2ItemConnection", + "id": "projectv2itemconnection", + "kind": "objects", + "href": "/graphql/reference/objects#projectv2itemconnection", + "description": "

The items in the new order.

" + } + ] + }, { "name": "updatePullRequest", "kind": "mutations", @@ -6245,6 +6593,48 @@ } ] }, + { + "name": "updateRepositoryWebCommitSignoffSetting", + "kind": "mutations", + "id": "updaterepositorywebcommitsignoffsetting", + "href": "/graphql/reference/mutations#updaterepositorywebcommitsignoffsetting", + "description": "

Sets whether contributors are required to sign off on web-based commits for a repository.

", + "inputFields": [ + { + "name": "input", + "type": "UpdateRepositoryWebCommitSignoffSettingInput!", + "id": "updaterepositorywebcommitsignoffsettinginput", + "kind": "input-objects", + "href": "/graphql/reference/input-objects#updaterepositorywebcommitsignoffsettinginput" + } + ], + "returnFields": [ + { + "name": "clientMutationId", + "type": "String", + "id": "string", + "kind": "scalars", + "href": "/graphql/reference/scalars#string", + "description": "

A unique identifier for the client performing the mutation.

" + }, + { + "name": "message", + "type": "String", + "id": "string", + "kind": "scalars", + "href": "/graphql/reference/scalars#string", + "description": "

A message confirming the result of updating the web commit signoff setting.

" + }, + { + "name": "repository", + "type": "Repository", + "id": "repository", + "kind": "objects", + "href": "/graphql/reference/objects#repository", + "description": "

The updated repository.

" + } + ] + }, { "name": "updateSubscription", "kind": "mutations", @@ -10927,7 +11317,7 @@ }, { "name": "minimizedReason", - "description": "

Returns why the comment was minimized.

", + "description": "

Returns why the comment was minimized. One of abuse, off-topic,\noutdated, resolved, duplicate and spam. Note that the case and\nformatting of these values differs from the inputs to the MinimizeComment mutation.

", "type": "String", "id": "string", "kind": "scalars", @@ -12180,7 +12570,7 @@ }, { "name": "pullRequestReviewContributions", - "description": "

Pull request review contributions made by the user.

", + "description": "

Pull request review contributions made by the user. Returns the most recently\nsubmitted review for each PR reviewed by the user.

", "type": "CreatedPullRequestReviewContributionConnection!", "id": "createdpullrequestreviewcontributionconnection", "kind": "objects", @@ -15234,6 +15624,14 @@ "kind": "scalars", "href": "/graphql/reference/scalars#int" }, + { + "name": "poll", + "description": "

The poll associated with this discussion, if one exists.

", + "type": "DiscussionPoll", + "id": "discussionpoll", + "kind": "objects", + "href": "/graphql/reference/objects#discussionpoll" + }, { "name": "publishedAt", "description": "

Identifies when the comment was published at.

", @@ -15559,6 +15957,14 @@ "kind": "objects", "href": "/graphql/reference/objects#repository" }, + { + "name": "slug", + "description": "

The slug of this category.

", + "type": "String!", + "id": "string", + "kind": "scalars", + "href": "/graphql/reference/scalars#string" + }, { "name": "updatedAt", "description": "

Identifies the date and time when the object was last updated.

", @@ -15806,7 +16212,7 @@ }, { "name": "minimizedReason", - "description": "

Returns why the comment was minimized.

", + "description": "

Returns why the comment was minimized. One of abuse, off-topic,\noutdated, resolved, duplicate and spam. Note that the case and\nformatting of these values differs from the inputs to the MinimizeComment mutation.

", "type": "String", "id": "string", "kind": "scalars", @@ -16321,6 +16727,16 @@ "kind": "scalars", "href": "/graphql/reference/scalars#int" } + }, + { + "name": "orderBy", + "description": "

How to order the options for the discussion poll.

", + "type": { + "name": "DiscussionPollOptionOrder", + "id": "discussionpolloptionorder", + "kind": "input-objects", + "href": "/graphql/reference/input-objects#discussionpolloptionorder" + } } ] }, @@ -16472,6 +16888,228 @@ } ] }, + { + "name": "DraftIssue", + "kind": "objects", + "id": "draftissue", + "href": "/graphql/reference/objects#draftissue", + "description": "

A draft issue within a project.

", + "implements": [ + { + "name": "Node", + "id": "node", + "href": "/graphql/reference/interfaces#node" + } + ], + "fields": [ + { + "name": "assignees", + "description": "

A list of users to assigned to this draft issue.

", + "type": "UserConnection!", + "id": "userconnection", + "kind": "objects", + "href": "/graphql/reference/objects#userconnection", + "arguments": [ + { + "name": "after", + "description": "

Returns the elements in the list that come after the specified cursor.

", + "type": { + "name": "String", + "id": "string", + "kind": "scalars", + "href": "/graphql/reference/scalars#string" + } + }, + { + "name": "before", + "description": "

Returns the elements in the list that come before the specified cursor.

", + "type": { + "name": "String", + "id": "string", + "kind": "scalars", + "href": "/graphql/reference/scalars#string" + } + }, + { + "name": "first", + "description": "

Returns the first n elements from the list.

", + "type": { + "name": "Int", + "id": "int", + "kind": "scalars", + "href": "/graphql/reference/scalars#int" + } + }, + { + "name": "last", + "description": "

Returns the last n elements from the list.

", + "type": { + "name": "Int", + "id": "int", + "kind": "scalars", + "href": "/graphql/reference/scalars#int" + } + } + ] + }, + { + "name": "body", + "description": "

The body of the draft issue.

", + "type": "String!", + "id": "string", + "kind": "scalars", + "href": "/graphql/reference/scalars#string" + }, + { + "name": "bodyHTML", + "description": "

The body of the draft issue rendered to HTML.

", + "type": "HTML!", + "id": "html", + "kind": "scalars", + "href": "/graphql/reference/scalars#html" + }, + { + "name": "bodyText", + "description": "

The body of the draft issue rendered to text.

", + "type": "String!", + "id": "string", + "kind": "scalars", + "href": "/graphql/reference/scalars#string" + }, + { + "name": "createdAt", + "description": "

Identifies the date and time when the object was created.

", + "type": "DateTime!", + "id": "datetime", + "kind": "scalars", + "href": "/graphql/reference/scalars#datetime" + }, + { + "name": "creator", + "description": "

The actor who created this draft issue.

", + "type": "Actor", + "id": "actor", + "kind": "interfaces", + "href": "/graphql/reference/interfaces#actor" + }, + { + "name": "projectV2Items", + "description": "

List of items linked with the draft issue (currently draft issue can be linked to only one item).

", + "type": "ProjectV2ItemConnection!", + "id": "projectv2itemconnection", + "kind": "objects", + "href": "/graphql/reference/objects#projectv2itemconnection", + "arguments": [ + { + "name": "after", + "description": "

Returns the elements in the list that come after the specified cursor.

", + "type": { + "name": "String", + "id": "string", + "kind": "scalars", + "href": "/graphql/reference/scalars#string" + } + }, + { + "name": "before", + "description": "

Returns the elements in the list that come before the specified cursor.

", + "type": { + "name": "String", + "id": "string", + "kind": "scalars", + "href": "/graphql/reference/scalars#string" + } + }, + { + "name": "first", + "description": "

Returns the first n elements from the list.

", + "type": { + "name": "Int", + "id": "int", + "kind": "scalars", + "href": "/graphql/reference/scalars#int" + } + }, + { + "name": "last", + "description": "

Returns the last n elements from the list.

", + "type": { + "name": "Int", + "id": "int", + "kind": "scalars", + "href": "/graphql/reference/scalars#int" + } + } + ] + }, + { + "name": "projectsV2", + "description": "

Projects that link to this draft issue (currently draft issue can be linked to only one project).

", + "type": "ProjectV2Connection!", + "id": "projectv2connection", + "kind": "objects", + "href": "/graphql/reference/objects#projectv2connection", + "arguments": [ + { + "name": "after", + "description": "

Returns the elements in the list that come after the specified cursor.

", + "type": { + "name": "String", + "id": "string", + "kind": "scalars", + "href": "/graphql/reference/scalars#string" + } + }, + { + "name": "before", + "description": "

Returns the elements in the list that come before the specified cursor.

", + "type": { + "name": "String", + "id": "string", + "kind": "scalars", + "href": "/graphql/reference/scalars#string" + } + }, + { + "name": "first", + "description": "

Returns the first n elements from the list.

", + "type": { + "name": "Int", + "id": "int", + "kind": "scalars", + "href": "/graphql/reference/scalars#int" + } + }, + { + "name": "last", + "description": "

Returns the last n elements from the list.

", + "type": { + "name": "Int", + "id": "int", + "kind": "scalars", + "href": "/graphql/reference/scalars#int" + } + } + ] + }, + { + "name": "title", + "description": "

The title of the draft issue.

", + "type": "String!", + "id": "string", + "kind": "scalars", + "href": "/graphql/reference/scalars#string" + }, + { + "name": "updatedAt", + "description": "

Identifies the date and time when the object was last updated.

", + "type": "DateTime!", + "id": "datetime", + "kind": "scalars", + "href": "/graphql/reference/scalars#datetime" + } + ] + }, { "name": "Enterprise", "kind": "objects", @@ -16774,58 +17412,6 @@ "kind": "scalars", "href": "/graphql/reference/scalars#uri" }, - { - "name": "userAccounts", - "description": "

A list of user accounts on this enterprise.

", - "type": "EnterpriseUserAccountConnection!", - "id": "enterpriseuseraccountconnection", - "kind": "objects", - "href": "/graphql/reference/objects#enterpriseuseraccountconnection", - "arguments": [ - { - "name": "after", - "description": "

Returns the elements in the list that come after the specified cursor.

", - "type": { - "name": "String", - "id": "string", - "kind": "scalars", - "href": "/graphql/reference/scalars#string" - } - }, - { - "name": "before", - "description": "

Returns the elements in the list that come before the specified cursor.

", - "type": { - "name": "String", - "id": "string", - "kind": "scalars", - "href": "/graphql/reference/scalars#string" - } - }, - { - "name": "first", - "description": "

Returns the first n elements from the list.

", - "type": { - "name": "Int", - "id": "int", - "kind": "scalars", - "href": "/graphql/reference/scalars#int" - } - }, - { - "name": "last", - "description": "

Returns the last n elements from the list.

", - "type": { - "name": "Int", - "id": "int", - "kind": "scalars", - "href": "/graphql/reference/scalars#int" - } - } - ], - "isDeprecated": true, - "deprecationReason": "

The Enterprise.userAccounts field is being removed. Use the Enterprise.members field instead. Removal on 2022-07-01 UTC.

" - }, { "name": "viewerIsAdmin", "description": "

Is the current viewer an admin of this enterprise?.

", @@ -20345,72 +20931,6 @@ } ] }, - { - "name": "EnterpriseUserAccountConnection", - "kind": "objects", - "id": "enterpriseuseraccountconnection", - "href": "/graphql/reference/objects#enterpriseuseraccountconnection", - "description": "

The connection type for EnterpriseUserAccount.

", - "fields": [ - { - "name": "edges", - "description": "

A list of edges.

", - "type": "[EnterpriseUserAccountEdge]", - "id": "enterpriseuseraccountedge", - "kind": "objects", - "href": "/graphql/reference/objects#enterpriseuseraccountedge" - }, - { - "name": "nodes", - "description": "

A list of nodes.

", - "type": "[EnterpriseUserAccount]", - "id": "enterpriseuseraccount", - "kind": "objects", - "href": "/graphql/reference/objects#enterpriseuseraccount" - }, - { - "name": "pageInfo", - "description": "

Information to aid in pagination.

", - "type": "PageInfo!", - "id": "pageinfo", - "kind": "objects", - "href": "/graphql/reference/objects#pageinfo" - }, - { - "name": "totalCount", - "description": "

Identifies the total count of items in the connection.

", - "type": "Int!", - "id": "int", - "kind": "scalars", - "href": "/graphql/reference/scalars#int" - } - ] - }, - { - "name": "EnterpriseUserAccountEdge", - "kind": "objects", - "id": "enterpriseuseraccountedge", - "href": "/graphql/reference/objects#enterpriseuseraccountedge", - "description": "

An edge in a connection.

", - "fields": [ - { - "name": "cursor", - "description": "

A cursor for use in pagination.

", - "type": "String!", - "id": "string", - "kind": "scalars", - "href": "/graphql/reference/scalars#string" - }, - { - "name": "node", - "description": "

The item at the end of the edge.

", - "type": "EnterpriseUserAccount", - "id": "enterpriseuseraccount", - "kind": "objects", - "href": "/graphql/reference/objects#enterpriseuseraccount" - } - ] - }, { "name": "Environment", "kind": "objects", @@ -21410,7 +21930,7 @@ }, { "name": "minimizedReason", - "description": "

Returns why the comment was minimized.

", + "description": "

Returns why the comment was minimized. One of abuse, off-topic,\noutdated, resolved, duplicate and spam. Note that the case and\nformatting of these values differs from the inputs to the MinimizeComment mutation.

", "type": "String", "id": "string", "kind": "scalars", @@ -22325,6 +22845,11 @@ "id": "node", "href": "/graphql/reference/interfaces#node" }, + { + "name": "ProjectV2Owner", + "id": "projectv2owner", + "href": "/graphql/reference/interfaces#projectv2owner" + }, { "name": "Reactable", "id": "reactable", @@ -22826,6 +23351,96 @@ } ] }, + { + "name": "projectV2", + "description": "

Find a project by number.

", + "type": "ProjectV2", + "id": "projectv2", + "kind": "objects", + "href": "/graphql/reference/objects#projectv2", + "arguments": [ + { + "name": "number", + "description": "

The project number.

", + "type": { + "name": "Int!", + "id": "int", + "kind": "scalars", + "href": "/graphql/reference/scalars#int" + } + } + ] + }, + { + "name": "projectsV2", + "description": "

A list of projects under the owner.

", + "type": "ProjectV2Connection!", + "id": "projectv2connection", + "kind": "objects", + "href": "/graphql/reference/objects#projectv2connection", + "arguments": [ + { + "name": "after", + "description": "

Returns the elements in the list that come after the specified cursor.

", + "type": { + "name": "String", + "id": "string", + "kind": "scalars", + "href": "/graphql/reference/scalars#string" + } + }, + { + "name": "before", + "description": "

Returns the elements in the list that come before the specified cursor.

", + "type": { + "name": "String", + "id": "string", + "kind": "scalars", + "href": "/graphql/reference/scalars#string" + } + }, + { + "name": "first", + "description": "

Returns the first n elements from the list.

", + "type": { + "name": "Int", + "id": "int", + "kind": "scalars", + "href": "/graphql/reference/scalars#int" + } + }, + { + "name": "last", + "description": "

Returns the last n elements from the list.

", + "type": { + "name": "Int", + "id": "int", + "kind": "scalars", + "href": "/graphql/reference/scalars#int" + } + }, + { + "name": "orderBy", + "description": "

How to order the returned projects.

", + "type": { + "name": "ProjectV2Order", + "id": "projectv2order", + "kind": "input-objects", + "href": "/graphql/reference/input-objects#projectv2order" + } + }, + { + "name": "query", + "description": "

A project to search for under the the owner.

", + "type": { + "name": "String", + "id": "string", + "kind": "scalars", + "href": "/graphql/reference/scalars#string" + } + } + ] + }, { "name": "publishedAt", "description": "

Identifies when the comment was published at.

", @@ -23373,7 +23988,7 @@ }, { "name": "minimizedReason", - "description": "

Returns why the comment was minimized.

", + "description": "

Returns why the comment was minimized. One of abuse, off-topic,\noutdated, resolved, duplicate and spam. Note that the case and\nformatting of these values differs from the inputs to the MinimizeComment mutation.

", "type": "String", "id": "string", "kind": "scalars", @@ -31336,6 +31951,16 @@ "id": "projectowner", "href": "/graphql/reference/interfaces#projectowner" }, + { + "name": "ProjectV2Owner", + "id": "projectv2owner", + "href": "/graphql/reference/interfaces#projectv2owner" + }, + { + "name": "ProjectV2Recent", + "id": "projectv2recent", + "href": "/graphql/reference/interfaces#projectv2recent" + }, { "name": "RepositoryDiscussionAuthor", "id": "repositorydiscussionauthor", @@ -32222,6 +32847,26 @@ } ] }, + { + "name": "projectV2", + "description": "

Find a project by number.

", + "type": "ProjectV2", + "id": "projectv2", + "kind": "objects", + "href": "/graphql/reference/objects#projectv2", + "arguments": [ + { + "name": "number", + "description": "

The project number.

", + "type": { + "name": "Int!", + "id": "int", + "kind": "scalars", + "href": "/graphql/reference/scalars#int" + } + } + ] + }, { "name": "projects", "description": "

A list of projects under the owner.

", @@ -32318,6 +32963,126 @@ "kind": "scalars", "href": "/graphql/reference/scalars#uri" }, + { + "name": "projectsV2", + "description": "

A list of projects under the owner.

", + "type": "ProjectV2Connection!", + "id": "projectv2connection", + "kind": "objects", + "href": "/graphql/reference/objects#projectv2connection", + "arguments": [ + { + "name": "after", + "description": "

Returns the elements in the list that come after the specified cursor.

", + "type": { + "name": "String", + "id": "string", + "kind": "scalars", + "href": "/graphql/reference/scalars#string" + } + }, + { + "name": "before", + "description": "

Returns the elements in the list that come before the specified cursor.

", + "type": { + "name": "String", + "id": "string", + "kind": "scalars", + "href": "/graphql/reference/scalars#string" + } + }, + { + "name": "first", + "description": "

Returns the first n elements from the list.

", + "type": { + "name": "Int", + "id": "int", + "kind": "scalars", + "href": "/graphql/reference/scalars#int" + } + }, + { + "name": "last", + "description": "

Returns the last n elements from the list.

", + "type": { + "name": "Int", + "id": "int", + "kind": "scalars", + "href": "/graphql/reference/scalars#int" + } + }, + { + "name": "orderBy", + "description": "

How to order the returned projects.

", + "type": { + "name": "ProjectV2Order", + "id": "projectv2order", + "kind": "input-objects", + "href": "/graphql/reference/input-objects#projectv2order" + } + }, + { + "name": "query", + "description": "

A project to search for under the the owner.

", + "type": { + "name": "String", + "id": "string", + "kind": "scalars", + "href": "/graphql/reference/scalars#string" + } + } + ] + }, + { + "name": "recentProjects", + "description": "

Recent projects that this user has modified in the context of the owner.

", + "type": "ProjectV2Connection!", + "id": "projectv2connection", + "kind": "objects", + "href": "/graphql/reference/objects#projectv2connection", + "arguments": [ + { + "name": "after", + "description": "

Returns the elements in the list that come after the specified cursor.

", + "type": { + "name": "String", + "id": "string", + "kind": "scalars", + "href": "/graphql/reference/scalars#string" + } + }, + { + "name": "before", + "description": "

Returns the elements in the list that come before the specified cursor.

", + "type": { + "name": "String", + "id": "string", + "kind": "scalars", + "href": "/graphql/reference/scalars#string" + } + }, + { + "name": "first", + "description": "

Returns the first n elements from the list.

", + "type": { + "name": "Int", + "id": "int", + "kind": "scalars", + "href": "/graphql/reference/scalars#int" + } + }, + { + "name": "last", + "description": "

Returns the last n elements from the list.

", + "type": { + "name": "Int", + "id": "int", + "kind": "scalars", + "href": "/graphql/reference/scalars#int" + } + } + ] + }, { "name": "repositories", "description": "

A list of repositories that the user owns.

", @@ -32951,6 +33716,14 @@ "kind": "scalars", "href": "/graphql/reference/scalars#boolean" }, + { + "name": "webCommitSignoffRequired", + "description": "

Whether contributors are required to sign off on web-based commits for repositories in this organization.

", + "type": "Boolean!", + "id": "boolean", + "kind": "scalars", + "href": "/graphql/reference/scalars#boolean" + }, { "name": "websiteUrl", "description": "

The organization's public profile URL.

", @@ -36102,6 +36875,2476 @@ } ] }, + { + "name": "ProjectV2", + "kind": "objects", + "id": "projectv2", + "href": "/graphql/reference/objects#projectv2", + "description": "

New projects that manage issues, pull requests and drafts using tables and boards.

", + "implements": [ + { + "name": "Closable", + "id": "closable", + "href": "/graphql/reference/interfaces#closable" + }, + { + "name": "Node", + "id": "node", + "href": "/graphql/reference/interfaces#node" + }, + { + "name": "Updatable", + "id": "updatable", + "href": "/graphql/reference/interfaces#updatable" + } + ], + "fields": [ + { + "name": "closed", + "description": "

Returns true if the project is closed.

", + "type": "Boolean!", + "id": "boolean", + "kind": "scalars", + "href": "/graphql/reference/scalars#boolean" + }, + { + "name": "closedAt", + "description": "

Identifies the date and time when the object was closed.

", + "type": "DateTime", + "id": "datetime", + "kind": "scalars", + "href": "/graphql/reference/scalars#datetime" + }, + { + "name": "createdAt", + "description": "

Identifies the date and time when the object was created.

", + "type": "DateTime!", + "id": "datetime", + "kind": "scalars", + "href": "/graphql/reference/scalars#datetime" + }, + { + "name": "creator", + "description": "

The actor who originally created the project.

", + "type": "Actor", + "id": "actor", + "kind": "interfaces", + "href": "/graphql/reference/interfaces#actor" + }, + { + "name": "databaseId", + "description": "

Identifies the primary key from the database.

", + "type": "Int", + "id": "int", + "kind": "scalars", + "href": "/graphql/reference/scalars#int" + }, + { + "name": "field", + "description": "

A field of the project.

", + "type": "ProjectV2FieldConfiguration", + "id": "projectv2fieldconfiguration", + "kind": "unions", + "href": "/graphql/reference/unions#projectv2fieldconfiguration", + "arguments": [ + { + "name": "name", + "description": "

The name of the field.

", + "type": { + "name": "String!", + "id": "string", + "kind": "scalars", + "href": "/graphql/reference/scalars#string" + } + } + ] + }, + { + "name": "fields", + "description": "

List of fields and their constraints in the project.

", + "type": "ProjectV2FieldConfigurationConnection!", + "id": "projectv2fieldconfigurationconnection", + "kind": "objects", + "href": "/graphql/reference/objects#projectv2fieldconfigurationconnection", + "arguments": [ + { + "name": "after", + "description": "

Returns the elements in the list that come after the specified cursor.

", + "type": { + "name": "String", + "id": "string", + "kind": "scalars", + "href": "/graphql/reference/scalars#string" + } + }, + { + "name": "before", + "description": "

Returns the elements in the list that come before the specified cursor.

", + "type": { + "name": "String", + "id": "string", + "kind": "scalars", + "href": "/graphql/reference/scalars#string" + } + }, + { + "name": "first", + "description": "

Returns the first n elements from the list.

", + "type": { + "name": "Int", + "id": "int", + "kind": "scalars", + "href": "/graphql/reference/scalars#int" + } + }, + { + "name": "last", + "description": "

Returns the last n elements from the list.

", + "type": { + "name": "Int", + "id": "int", + "kind": "scalars", + "href": "/graphql/reference/scalars#int" + } + }, + { + "name": "orderBy", + "description": "

Ordering options for project v2 fields returned from the connection.

", + "type": { + "name": "ProjectV2FieldOrder", + "id": "projectv2fieldorder", + "kind": "input-objects", + "href": "/graphql/reference/input-objects#projectv2fieldorder" + } + } + ] + }, + { + "name": "items", + "description": "

List of items in the project.

", + "type": "ProjectV2ItemConnection!", + "id": "projectv2itemconnection", + "kind": "objects", + "href": "/graphql/reference/objects#projectv2itemconnection", + "arguments": [ + { + "name": "after", + "description": "

Returns the elements in the list that come after the specified cursor.

", + "type": { + "name": "String", + "id": "string", + "kind": "scalars", + "href": "/graphql/reference/scalars#string" + } + }, + { + "name": "before", + "description": "

Returns the elements in the list that come before the specified cursor.

", + "type": { + "name": "String", + "id": "string", + "kind": "scalars", + "href": "/graphql/reference/scalars#string" + } + }, + { + "name": "first", + "description": "

Returns the first n elements from the list.

", + "type": { + "name": "Int", + "id": "int", + "kind": "scalars", + "href": "/graphql/reference/scalars#int" + } + }, + { + "name": "last", + "description": "

Returns the last n elements from the list.

", + "type": { + "name": "Int", + "id": "int", + "kind": "scalars", + "href": "/graphql/reference/scalars#int" + } + }, + { + "name": "orderBy", + "description": "

Ordering options for project v2 items returned from the connection.

", + "type": { + "name": "ProjectV2ItemOrder", + "id": "projectv2itemorder", + "kind": "input-objects", + "href": "/graphql/reference/input-objects#projectv2itemorder" + } + } + ] + }, + { + "name": "number", + "description": "

The project's number.

", + "type": "Int!", + "id": "int", + "kind": "scalars", + "href": "/graphql/reference/scalars#int" + }, + { + "name": "owner", + "description": "

The project's owner. Currently limited to organizations and users.

", + "type": "ProjectV2Owner!", + "id": "projectv2owner", + "kind": "interfaces", + "href": "/graphql/reference/interfaces#projectv2owner" + }, + { + "name": "public", + "description": "

Returns true if the project is public.

", + "type": "Boolean!", + "id": "boolean", + "kind": "scalars", + "href": "/graphql/reference/scalars#boolean" + }, + { + "name": "readme", + "description": "

The project's readme.

", + "type": "String", + "id": "string", + "kind": "scalars", + "href": "/graphql/reference/scalars#string" + }, + { + "name": "repositories", + "description": "

The repositories the project is linked to.

", + "type": "RepositoryConnection!", + "id": "repositoryconnection", + "kind": "objects", + "href": "/graphql/reference/objects#repositoryconnection", + "arguments": [ + { + "name": "after", + "description": "

Returns the elements in the list that come after the specified cursor.

", + "type": { + "name": "String", + "id": "string", + "kind": "scalars", + "href": "/graphql/reference/scalars#string" + } + }, + { + "name": "before", + "description": "

Returns the elements in the list that come before the specified cursor.

", + "type": { + "name": "String", + "id": "string", + "kind": "scalars", + "href": "/graphql/reference/scalars#string" + } + }, + { + "name": "first", + "description": "

Returns the first n elements from the list.

", + "type": { + "name": "Int", + "id": "int", + "kind": "scalars", + "href": "/graphql/reference/scalars#int" + } + }, + { + "name": "last", + "description": "

Returns the last n elements from the list.

", + "type": { + "name": "Int", + "id": "int", + "kind": "scalars", + "href": "/graphql/reference/scalars#int" + } + }, + { + "name": "orderBy", + "description": "

Ordering options for repositories returned from the connection.

", + "type": { + "name": "RepositoryOrder", + "id": "repositoryorder", + "kind": "input-objects", + "href": "/graphql/reference/input-objects#repositoryorder" + } + } + ] + }, + { + "name": "resourcePath", + "description": "

The HTTP path for this project.

", + "type": "URI!", + "id": "uri", + "kind": "scalars", + "href": "/graphql/reference/scalars#uri" + }, + { + "name": "shortDescription", + "description": "

The project's short description.

", + "type": "String", + "id": "string", + "kind": "scalars", + "href": "/graphql/reference/scalars#string" + }, + { + "name": "title", + "description": "

The project's name.

", + "type": "String!", + "id": "string", + "kind": "scalars", + "href": "/graphql/reference/scalars#string" + }, + { + "name": "updatedAt", + "description": "

Identifies the date and time when the object was last updated.

", + "type": "DateTime!", + "id": "datetime", + "kind": "scalars", + "href": "/graphql/reference/scalars#datetime" + }, + { + "name": "url", + "description": "

The HTTP URL for this project.

", + "type": "URI!", + "id": "uri", + "kind": "scalars", + "href": "/graphql/reference/scalars#uri" + }, + { + "name": "viewerCanUpdate", + "description": "

Check if the current viewer can update this object.

", + "type": "Boolean!", + "id": "boolean", + "kind": "scalars", + "href": "/graphql/reference/scalars#boolean" + }, + { + "name": "views", + "description": "

List of views in the project.

", + "type": "ProjectV2ViewConnection!", + "id": "projectv2viewconnection", + "kind": "objects", + "href": "/graphql/reference/objects#projectv2viewconnection", + "arguments": [ + { + "name": "after", + "description": "

Returns the elements in the list that come after the specified cursor.

", + "type": { + "name": "String", + "id": "string", + "kind": "scalars", + "href": "/graphql/reference/scalars#string" + } + }, + { + "name": "before", + "description": "

Returns the elements in the list that come before the specified cursor.

", + "type": { + "name": "String", + "id": "string", + "kind": "scalars", + "href": "/graphql/reference/scalars#string" + } + }, + { + "name": "first", + "description": "

Returns the first n elements from the list.

", + "type": { + "name": "Int", + "id": "int", + "kind": "scalars", + "href": "/graphql/reference/scalars#int" + } + }, + { + "name": "last", + "description": "

Returns the last n elements from the list.

", + "type": { + "name": "Int", + "id": "int", + "kind": "scalars", + "href": "/graphql/reference/scalars#int" + } + }, + { + "name": "orderBy", + "description": "

Ordering options for project v2 views returned from the connection.

", + "type": { + "name": "ProjectV2ViewOrder", + "id": "projectv2vieworder", + "kind": "input-objects", + "href": "/graphql/reference/input-objects#projectv2vieworder" + } + } + ] + } + ] + }, + { + "name": "ProjectV2Connection", + "kind": "objects", + "id": "projectv2connection", + "href": "/graphql/reference/objects#projectv2connection", + "description": "

The connection type for ProjectV2.

", + "fields": [ + { + "name": "edges", + "description": "

A list of edges.

", + "type": "[ProjectV2Edge]", + "id": "projectv2edge", + "kind": "objects", + "href": "/graphql/reference/objects#projectv2edge" + }, + { + "name": "nodes", + "description": "

A list of nodes.

", + "type": "[ProjectV2]", + "id": "projectv2", + "kind": "objects", + "href": "/graphql/reference/objects#projectv2" + }, + { + "name": "pageInfo", + "description": "

Information to aid in pagination.

", + "type": "PageInfo!", + "id": "pageinfo", + "kind": "objects", + "href": "/graphql/reference/objects#pageinfo" + }, + { + "name": "totalCount", + "description": "

Identifies the total count of items in the connection.

", + "type": "Int!", + "id": "int", + "kind": "scalars", + "href": "/graphql/reference/scalars#int" + } + ] + }, + { + "name": "ProjectV2Edge", + "kind": "objects", + "id": "projectv2edge", + "href": "/graphql/reference/objects#projectv2edge", + "description": "

An edge in a connection.

", + "fields": [ + { + "name": "cursor", + "description": "

A cursor for use in pagination.

", + "type": "String!", + "id": "string", + "kind": "scalars", + "href": "/graphql/reference/scalars#string" + }, + { + "name": "node", + "description": "

The item at the end of the edge.

", + "type": "ProjectV2", + "id": "projectv2", + "kind": "objects", + "href": "/graphql/reference/objects#projectv2" + } + ] + }, + { + "name": "ProjectV2Field", + "kind": "objects", + "id": "projectv2field", + "href": "/graphql/reference/objects#projectv2field", + "description": "

A field inside a project.

", + "implements": [ + { + "name": "Node", + "id": "node", + "href": "/graphql/reference/interfaces#node" + }, + { + "name": "ProjectV2FieldCommon", + "id": "projectv2fieldcommon", + "href": "/graphql/reference/interfaces#projectv2fieldcommon" + } + ], + "fields": [ + { + "name": "createdAt", + "description": "

Identifies the date and time when the object was created.

", + "type": "DateTime!", + "id": "datetime", + "kind": "scalars", + "href": "/graphql/reference/scalars#datetime" + }, + { + "name": "dataType", + "description": "

The field's type.

", + "type": "ProjectV2FieldType!", + "id": "projectv2fieldtype", + "kind": "enums", + "href": "/graphql/reference/enums#projectv2fieldtype" + }, + { + "name": "databaseId", + "description": "

Identifies the primary key from the database.

", + "type": "Int", + "id": "int", + "kind": "scalars", + "href": "/graphql/reference/scalars#int" + }, + { + "name": "name", + "description": "

The project field's name.

", + "type": "String!", + "id": "string", + "kind": "scalars", + "href": "/graphql/reference/scalars#string" + }, + { + "name": "project", + "description": "

The project that contains this field.

", + "type": "ProjectV2!", + "id": "projectv2", + "kind": "objects", + "href": "/graphql/reference/objects#projectv2" + }, + { + "name": "updatedAt", + "description": "

Identifies the date and time when the object was last updated.

", + "type": "DateTime!", + "id": "datetime", + "kind": "scalars", + "href": "/graphql/reference/scalars#datetime" + } + ] + }, + { + "name": "ProjectV2FieldConfigurationConnection", + "kind": "objects", + "id": "projectv2fieldconfigurationconnection", + "href": "/graphql/reference/objects#projectv2fieldconfigurationconnection", + "description": "

The connection type for ProjectV2FieldConfiguration.

", + "fields": [ + { + "name": "edges", + "description": "

A list of edges.

", + "type": "[ProjectV2FieldConfigurationEdge]", + "id": "projectv2fieldconfigurationedge", + "kind": "objects", + "href": "/graphql/reference/objects#projectv2fieldconfigurationedge" + }, + { + "name": "nodes", + "description": "

A list of nodes.

", + "type": "[ProjectV2FieldConfiguration]", + "id": "projectv2fieldconfiguration", + "kind": "unions", + "href": "/graphql/reference/unions#projectv2fieldconfiguration" + }, + { + "name": "pageInfo", + "description": "

Information to aid in pagination.

", + "type": "PageInfo!", + "id": "pageinfo", + "kind": "objects", + "href": "/graphql/reference/objects#pageinfo" + }, + { + "name": "totalCount", + "description": "

Identifies the total count of items in the connection.

", + "type": "Int!", + "id": "int", + "kind": "scalars", + "href": "/graphql/reference/scalars#int" + } + ] + }, + { + "name": "ProjectV2FieldConfigurationEdge", + "kind": "objects", + "id": "projectv2fieldconfigurationedge", + "href": "/graphql/reference/objects#projectv2fieldconfigurationedge", + "description": "

An edge in a connection.

", + "fields": [ + { + "name": "cursor", + "description": "

A cursor for use in pagination.

", + "type": "String!", + "id": "string", + "kind": "scalars", + "href": "/graphql/reference/scalars#string" + }, + { + "name": "node", + "description": "

The item at the end of the edge.

", + "type": "ProjectV2FieldConfiguration", + "id": "projectv2fieldconfiguration", + "kind": "unions", + "href": "/graphql/reference/unions#projectv2fieldconfiguration" + } + ] + }, + { + "name": "ProjectV2FieldConnection", + "kind": "objects", + "id": "projectv2fieldconnection", + "href": "/graphql/reference/objects#projectv2fieldconnection", + "description": "

The connection type for ProjectV2Field.

", + "fields": [ + { + "name": "edges", + "description": "

A list of edges.

", + "type": "[ProjectV2FieldEdge]", + "id": "projectv2fieldedge", + "kind": "objects", + "href": "/graphql/reference/objects#projectv2fieldedge" + }, + { + "name": "nodes", + "description": "

A list of nodes.

", + "type": "[ProjectV2Field]", + "id": "projectv2field", + "kind": "objects", + "href": "/graphql/reference/objects#projectv2field" + }, + { + "name": "pageInfo", + "description": "

Information to aid in pagination.

", + "type": "PageInfo!", + "id": "pageinfo", + "kind": "objects", + "href": "/graphql/reference/objects#pageinfo" + }, + { + "name": "totalCount", + "description": "

Identifies the total count of items in the connection.

", + "type": "Int!", + "id": "int", + "kind": "scalars", + "href": "/graphql/reference/scalars#int" + } + ] + }, + { + "name": "ProjectV2FieldEdge", + "kind": "objects", + "id": "projectv2fieldedge", + "href": "/graphql/reference/objects#projectv2fieldedge", + "description": "

An edge in a connection.

", + "fields": [ + { + "name": "cursor", + "description": "

A cursor for use in pagination.

", + "type": "String!", + "id": "string", + "kind": "scalars", + "href": "/graphql/reference/scalars#string" + }, + { + "name": "node", + "description": "

The item at the end of the edge.

", + "type": "ProjectV2Field", + "id": "projectv2field", + "kind": "objects", + "href": "/graphql/reference/objects#projectv2field" + } + ] + }, + { + "name": "ProjectV2Item", + "kind": "objects", + "id": "projectv2item", + "href": "/graphql/reference/objects#projectv2item", + "description": "

An item within a Project.

", + "implements": [ + { + "name": "Node", + "id": "node", + "href": "/graphql/reference/interfaces#node" + } + ], + "fields": [ + { + "name": "content", + "description": "

The content of the referenced draft issue, issue, or pull request.

", + "type": "ProjectV2ItemContent", + "id": "projectv2itemcontent", + "kind": "unions", + "href": "/graphql/reference/unions#projectv2itemcontent" + }, + { + "name": "createdAt", + "description": "

Identifies the date and time when the object was created.

", + "type": "DateTime!", + "id": "datetime", + "kind": "scalars", + "href": "/graphql/reference/scalars#datetime" + }, + { + "name": "creator", + "description": "

The actor who created the item.

", + "type": "Actor", + "id": "actor", + "kind": "interfaces", + "href": "/graphql/reference/interfaces#actor" + }, + { + "name": "databaseId", + "description": "

Identifies the primary key from the database.

", + "type": "Int", + "id": "int", + "kind": "scalars", + "href": "/graphql/reference/scalars#int" + }, + { + "name": "fieldValueByName", + "description": "

A specific field value given a field name.

", + "type": "ProjectV2ItemFieldValue", + "id": "projectv2itemfieldvalue", + "kind": "unions", + "href": "/graphql/reference/unions#projectv2itemfieldvalue", + "arguments": [ + { + "name": "name", + "description": "

The name of the field to return the field value of.

", + "type": { + "name": "String!", + "id": "string", + "kind": "scalars", + "href": "/graphql/reference/scalars#string" + } + } + ] + }, + { + "name": "fieldValues", + "description": "

List of field values.

", + "type": "ProjectV2ItemFieldValueConnection!", + "id": "projectv2itemfieldvalueconnection", + "kind": "objects", + "href": "/graphql/reference/objects#projectv2itemfieldvalueconnection", + "arguments": [ + { + "name": "after", + "description": "

Returns the elements in the list that come after the specified cursor.

", + "type": { + "name": "String", + "id": "string", + "kind": "scalars", + "href": "/graphql/reference/scalars#string" + } + }, + { + "name": "before", + "description": "

Returns the elements in the list that come before the specified cursor.

", + "type": { + "name": "String", + "id": "string", + "kind": "scalars", + "href": "/graphql/reference/scalars#string" + } + }, + { + "name": "first", + "description": "

Returns the first n elements from the list.

", + "type": { + "name": "Int", + "id": "int", + "kind": "scalars", + "href": "/graphql/reference/scalars#int" + } + }, + { + "name": "last", + "description": "

Returns the last n elements from the list.

", + "type": { + "name": "Int", + "id": "int", + "kind": "scalars", + "href": "/graphql/reference/scalars#int" + } + }, + { + "name": "orderBy", + "description": "

Ordering options for project v2 item field values returned from the connection.

", + "type": { + "name": "ProjectV2ItemFieldValueOrder", + "id": "projectv2itemfieldvalueorder", + "kind": "input-objects", + "href": "/graphql/reference/input-objects#projectv2itemfieldvalueorder" + } + } + ] + }, + { + "name": "isArchived", + "description": "

Whether the item is archived.

", + "type": "Boolean!", + "id": "boolean", + "kind": "scalars", + "href": "/graphql/reference/scalars#boolean" + }, + { + "name": "project", + "description": "

The project that contains this item.

", + "type": "ProjectV2!", + "id": "projectv2", + "kind": "objects", + "href": "/graphql/reference/objects#projectv2" + }, + { + "name": "type", + "description": "

The type of the item.

", + "type": "ProjectV2ItemType!", + "id": "projectv2itemtype", + "kind": "enums", + "href": "/graphql/reference/enums#projectv2itemtype" + }, + { + "name": "updatedAt", + "description": "

Identifies the date and time when the object was last updated.

", + "type": "DateTime!", + "id": "datetime", + "kind": "scalars", + "href": "/graphql/reference/scalars#datetime" + } + ] + }, + { + "name": "ProjectV2ItemConnection", + "kind": "objects", + "id": "projectv2itemconnection", + "href": "/graphql/reference/objects#projectv2itemconnection", + "description": "

The connection type for ProjectV2Item.

", + "fields": [ + { + "name": "edges", + "description": "

A list of edges.

", + "type": "[ProjectV2ItemEdge]", + "id": "projectv2itemedge", + "kind": "objects", + "href": "/graphql/reference/objects#projectv2itemedge" + }, + { + "name": "nodes", + "description": "

A list of nodes.

", + "type": "[ProjectV2Item]", + "id": "projectv2item", + "kind": "objects", + "href": "/graphql/reference/objects#projectv2item" + }, + { + "name": "pageInfo", + "description": "

Information to aid in pagination.

", + "type": "PageInfo!", + "id": "pageinfo", + "kind": "objects", + "href": "/graphql/reference/objects#pageinfo" + }, + { + "name": "totalCount", + "description": "

Identifies the total count of items in the connection.

", + "type": "Int!", + "id": "int", + "kind": "scalars", + "href": "/graphql/reference/scalars#int" + } + ] + }, + { + "name": "ProjectV2ItemEdge", + "kind": "objects", + "id": "projectv2itemedge", + "href": "/graphql/reference/objects#projectv2itemedge", + "description": "

An edge in a connection.

", + "fields": [ + { + "name": "cursor", + "description": "

A cursor for use in pagination.

", + "type": "String!", + "id": "string", + "kind": "scalars", + "href": "/graphql/reference/scalars#string" + }, + { + "name": "node", + "description": "

The item at the end of the edge.

", + "type": "ProjectV2Item", + "id": "projectv2item", + "kind": "objects", + "href": "/graphql/reference/objects#projectv2item" + } + ] + }, + { + "name": "ProjectV2ItemFieldDateValue", + "kind": "objects", + "id": "projectv2itemfielddatevalue", + "href": "/graphql/reference/objects#projectv2itemfielddatevalue", + "description": "

The value of a date field in a Project item.

", + "implements": [ + { + "name": "Node", + "id": "node", + "href": "/graphql/reference/interfaces#node" + }, + { + "name": "ProjectV2ItemFieldValueCommon", + "id": "projectv2itemfieldvaluecommon", + "href": "/graphql/reference/interfaces#projectv2itemfieldvaluecommon" + } + ], + "fields": [ + { + "name": "createdAt", + "description": "

Identifies the date and time when the object was created.

", + "type": "DateTime!", + "id": "datetime", + "kind": "scalars", + "href": "/graphql/reference/scalars#datetime" + }, + { + "name": "creator", + "description": "

The actor who created the item.

", + "type": "Actor", + "id": "actor", + "kind": "interfaces", + "href": "/graphql/reference/interfaces#actor" + }, + { + "name": "databaseId", + "description": "

Identifies the primary key from the database.

", + "type": "Int", + "id": "int", + "kind": "scalars", + "href": "/graphql/reference/scalars#int" + }, + { + "name": "date", + "description": "

Date value for the field.

", + "type": "Date", + "id": "date", + "kind": "scalars", + "href": "/graphql/reference/scalars#date" + }, + { + "name": "field", + "description": "

The project field that contains this value.

", + "type": "ProjectV2FieldConfiguration!", + "id": "projectv2fieldconfiguration", + "kind": "unions", + "href": "/graphql/reference/unions#projectv2fieldconfiguration" + }, + { + "name": "item", + "description": "

The project item that contains this value.

", + "type": "ProjectV2Item!", + "id": "projectv2item", + "kind": "objects", + "href": "/graphql/reference/objects#projectv2item" + }, + { + "name": "updatedAt", + "description": "

Identifies the date and time when the object was last updated.

", + "type": "DateTime!", + "id": "datetime", + "kind": "scalars", + "href": "/graphql/reference/scalars#datetime" + } + ] + }, + { + "name": "ProjectV2ItemFieldIterationValue", + "kind": "objects", + "id": "projectv2itemfielditerationvalue", + "href": "/graphql/reference/objects#projectv2itemfielditerationvalue", + "description": "

The value of an iteration field in a Project item.

", + "implements": [ + { + "name": "Node", + "id": "node", + "href": "/graphql/reference/interfaces#node" + }, + { + "name": "ProjectV2ItemFieldValueCommon", + "id": "projectv2itemfieldvaluecommon", + "href": "/graphql/reference/interfaces#projectv2itemfieldvaluecommon" + } + ], + "fields": [ + { + "name": "createdAt", + "description": "

Identifies the date and time when the object was created.

", + "type": "DateTime!", + "id": "datetime", + "kind": "scalars", + "href": "/graphql/reference/scalars#datetime" + }, + { + "name": "creator", + "description": "

The actor who created the item.

", + "type": "Actor", + "id": "actor", + "kind": "interfaces", + "href": "/graphql/reference/interfaces#actor" + }, + { + "name": "databaseId", + "description": "

Identifies the primary key from the database.

", + "type": "Int", + "id": "int", + "kind": "scalars", + "href": "/graphql/reference/scalars#int" + }, + { + "name": "duration", + "description": "

The duration of the iteration in days.

", + "type": "Int!", + "id": "int", + "kind": "scalars", + "href": "/graphql/reference/scalars#int" + }, + { + "name": "field", + "description": "

The project field that contains this value.

", + "type": "ProjectV2FieldConfiguration!", + "id": "projectv2fieldconfiguration", + "kind": "unions", + "href": "/graphql/reference/unions#projectv2fieldconfiguration" + }, + { + "name": "item", + "description": "

The project item that contains this value.

", + "type": "ProjectV2Item!", + "id": "projectv2item", + "kind": "objects", + "href": "/graphql/reference/objects#projectv2item" + }, + { + "name": "iterationId", + "description": "

The ID of the iteration.

", + "type": "String!", + "id": "string", + "kind": "scalars", + "href": "/graphql/reference/scalars#string" + }, + { + "name": "startDate", + "description": "

The start date of the iteration.

", + "type": "Date!", + "id": "date", + "kind": "scalars", + "href": "/graphql/reference/scalars#date" + }, + { + "name": "title", + "description": "

The title of the iteration.

", + "type": "String!", + "id": "string", + "kind": "scalars", + "href": "/graphql/reference/scalars#string" + }, + { + "name": "titleHTML", + "description": "

The title of the iteration, with HTML.

", + "type": "String!", + "id": "string", + "kind": "scalars", + "href": "/graphql/reference/scalars#string" + }, + { + "name": "updatedAt", + "description": "

Identifies the date and time when the object was last updated.

", + "type": "DateTime!", + "id": "datetime", + "kind": "scalars", + "href": "/graphql/reference/scalars#datetime" + } + ] + }, + { + "name": "ProjectV2ItemFieldLabelValue", + "kind": "objects", + "id": "projectv2itemfieldlabelvalue", + "href": "/graphql/reference/objects#projectv2itemfieldlabelvalue", + "description": "

The value of the labels field in a Project item.

", + "fields": [ + { + "name": "field", + "description": "

The field that contains this value.

", + "type": "ProjectV2FieldConfiguration!", + "id": "projectv2fieldconfiguration", + "kind": "unions", + "href": "/graphql/reference/unions#projectv2fieldconfiguration" + }, + { + "name": "labels", + "description": "

Labels value of a field.

", + "type": "LabelConnection", + "id": "labelconnection", + "kind": "objects", + "href": "/graphql/reference/objects#labelconnection", + "arguments": [ + { + "name": "after", + "description": "

Returns the elements in the list that come after the specified cursor.

", + "type": { + "name": "String", + "id": "string", + "kind": "scalars", + "href": "/graphql/reference/scalars#string" + } + }, + { + "name": "before", + "description": "

Returns the elements in the list that come before the specified cursor.

", + "type": { + "name": "String", + "id": "string", + "kind": "scalars", + "href": "/graphql/reference/scalars#string" + } + }, + { + "name": "first", + "description": "

Returns the first n elements from the list.

", + "type": { + "name": "Int", + "id": "int", + "kind": "scalars", + "href": "/graphql/reference/scalars#int" + } + }, + { + "name": "last", + "description": "

Returns the last n elements from the list.

", + "type": { + "name": "Int", + "id": "int", + "kind": "scalars", + "href": "/graphql/reference/scalars#int" + } + } + ] + } + ] + }, + { + "name": "ProjectV2ItemFieldMilestoneValue", + "kind": "objects", + "id": "projectv2itemfieldmilestonevalue", + "href": "/graphql/reference/objects#projectv2itemfieldmilestonevalue", + "description": "

The value of a milestone field in a Project item.

", + "fields": [ + { + "name": "field", + "description": "

The field that contains this value.

", + "type": "ProjectV2FieldConfiguration!", + "id": "projectv2fieldconfiguration", + "kind": "unions", + "href": "/graphql/reference/unions#projectv2fieldconfiguration" + }, + { + "name": "milestone", + "description": "

Milestone value of a field.

", + "type": "Milestone", + "id": "milestone", + "kind": "objects", + "href": "/graphql/reference/objects#milestone" + } + ] + }, + { + "name": "ProjectV2ItemFieldNumberValue", + "kind": "objects", + "id": "projectv2itemfieldnumbervalue", + "href": "/graphql/reference/objects#projectv2itemfieldnumbervalue", + "description": "

The value of a number field in a Project item.

", + "implements": [ + { + "name": "Node", + "id": "node", + "href": "/graphql/reference/interfaces#node" + }, + { + "name": "ProjectV2ItemFieldValueCommon", + "id": "projectv2itemfieldvaluecommon", + "href": "/graphql/reference/interfaces#projectv2itemfieldvaluecommon" + } + ], + "fields": [ + { + "name": "createdAt", + "description": "

Identifies the date and time when the object was created.

", + "type": "DateTime!", + "id": "datetime", + "kind": "scalars", + "href": "/graphql/reference/scalars#datetime" + }, + { + "name": "creator", + "description": "

The actor who created the item.

", + "type": "Actor", + "id": "actor", + "kind": "interfaces", + "href": "/graphql/reference/interfaces#actor" + }, + { + "name": "databaseId", + "description": "

Identifies the primary key from the database.

", + "type": "Int", + "id": "int", + "kind": "scalars", + "href": "/graphql/reference/scalars#int" + }, + { + "name": "field", + "description": "

The project field that contains this value.

", + "type": "ProjectV2FieldConfiguration!", + "id": "projectv2fieldconfiguration", + "kind": "unions", + "href": "/graphql/reference/unions#projectv2fieldconfiguration" + }, + { + "name": "item", + "description": "

The project item that contains this value.

", + "type": "ProjectV2Item!", + "id": "projectv2item", + "kind": "objects", + "href": "/graphql/reference/objects#projectv2item" + }, + { + "name": "number", + "description": "

Number as a float(8).

", + "type": "Float", + "id": "float", + "kind": "scalars", + "href": "/graphql/reference/scalars#float" + }, + { + "name": "updatedAt", + "description": "

Identifies the date and time when the object was last updated.

", + "type": "DateTime!", + "id": "datetime", + "kind": "scalars", + "href": "/graphql/reference/scalars#datetime" + } + ] + }, + { + "name": "ProjectV2ItemFieldPullRequestValue", + "kind": "objects", + "id": "projectv2itemfieldpullrequestvalue", + "href": "/graphql/reference/objects#projectv2itemfieldpullrequestvalue", + "description": "

The value of a pull request field in a Project item.

", + "fields": [ + { + "name": "field", + "description": "

The field that contains this value.

", + "type": "ProjectV2FieldConfiguration!", + "id": "projectv2fieldconfiguration", + "kind": "unions", + "href": "/graphql/reference/unions#projectv2fieldconfiguration" + }, + { + "name": "pullRequests", + "description": "

The pull requests for this field.

", + "type": "PullRequestConnection", + "id": "pullrequestconnection", + "kind": "objects", + "href": "/graphql/reference/objects#pullrequestconnection", + "arguments": [ + { + "name": "after", + "description": "

Returns the elements in the list that come after the specified cursor.

", + "type": { + "name": "String", + "id": "string", + "kind": "scalars", + "href": "/graphql/reference/scalars#string" + } + }, + { + "name": "before", + "description": "

Returns the elements in the list that come before the specified cursor.

", + "type": { + "name": "String", + "id": "string", + "kind": "scalars", + "href": "/graphql/reference/scalars#string" + } + }, + { + "name": "first", + "description": "

Returns the first n elements from the list.

", + "type": { + "name": "Int", + "id": "int", + "kind": "scalars", + "href": "/graphql/reference/scalars#int" + } + }, + { + "name": "last", + "description": "

Returns the last n elements from the list.

", + "type": { + "name": "Int", + "id": "int", + "kind": "scalars", + "href": "/graphql/reference/scalars#int" + } + }, + { + "name": "orderBy", + "description": "

Ordering options for pull requests.

", + "type": { + "name": "PullRequestOrder", + "id": "pullrequestorder", + "kind": "input-objects", + "href": "/graphql/reference/input-objects#pullrequestorder" + } + } + ] + } + ] + }, + { + "name": "ProjectV2ItemFieldRepositoryValue", + "kind": "objects", + "id": "projectv2itemfieldrepositoryvalue", + "href": "/graphql/reference/objects#projectv2itemfieldrepositoryvalue", + "description": "

The value of a repository field in a Project item.

", + "fields": [ + { + "name": "field", + "description": "

The field that contains this value.

", + "type": "ProjectV2FieldConfiguration!", + "id": "projectv2fieldconfiguration", + "kind": "unions", + "href": "/graphql/reference/unions#projectv2fieldconfiguration" + }, + { + "name": "repository", + "description": "

The repository for this field.

", + "type": "Repository", + "id": "repository", + "kind": "objects", + "href": "/graphql/reference/objects#repository" + } + ] + }, + { + "name": "ProjectV2ItemFieldReviewerValue", + "kind": "objects", + "id": "projectv2itemfieldreviewervalue", + "href": "/graphql/reference/objects#projectv2itemfieldreviewervalue", + "description": "

The value of a reviewers field in a Project item.

", + "fields": [ + { + "name": "field", + "description": "

The field that contains this value.

", + "type": "ProjectV2FieldConfiguration!", + "id": "projectv2fieldconfiguration", + "kind": "unions", + "href": "/graphql/reference/unions#projectv2fieldconfiguration" + }, + { + "name": "reviewers", + "description": "

The reviewers for this field.

", + "type": "RequestedReviewerConnection", + "id": "requestedreviewerconnection", + "kind": "objects", + "href": "/graphql/reference/objects#requestedreviewerconnection", + "arguments": [ + { + "name": "after", + "description": "

Returns the elements in the list that come after the specified cursor.

", + "type": { + "name": "String", + "id": "string", + "kind": "scalars", + "href": "/graphql/reference/scalars#string" + } + }, + { + "name": "before", + "description": "

Returns the elements in the list that come before the specified cursor.

", + "type": { + "name": "String", + "id": "string", + "kind": "scalars", + "href": "/graphql/reference/scalars#string" + } + }, + { + "name": "first", + "description": "

Returns the first n elements from the list.

", + "type": { + "name": "Int", + "id": "int", + "kind": "scalars", + "href": "/graphql/reference/scalars#int" + } + }, + { + "name": "last", + "description": "

Returns the last n elements from the list.

", + "type": { + "name": "Int", + "id": "int", + "kind": "scalars", + "href": "/graphql/reference/scalars#int" + } + } + ] + } + ] + }, + { + "name": "ProjectV2ItemFieldSingleSelectValue", + "kind": "objects", + "id": "projectv2itemfieldsingleselectvalue", + "href": "/graphql/reference/objects#projectv2itemfieldsingleselectvalue", + "description": "

The value of a single select field in a Project item.

", + "implements": [ + { + "name": "Node", + "id": "node", + "href": "/graphql/reference/interfaces#node" + }, + { + "name": "ProjectV2ItemFieldValueCommon", + "id": "projectv2itemfieldvaluecommon", + "href": "/graphql/reference/interfaces#projectv2itemfieldvaluecommon" + } + ], + "fields": [ + { + "name": "createdAt", + "description": "

Identifies the date and time when the object was created.

", + "type": "DateTime!", + "id": "datetime", + "kind": "scalars", + "href": "/graphql/reference/scalars#datetime" + }, + { + "name": "creator", + "description": "

The actor who created the item.

", + "type": "Actor", + "id": "actor", + "kind": "interfaces", + "href": "/graphql/reference/interfaces#actor" + }, + { + "name": "databaseId", + "description": "

Identifies the primary key from the database.

", + "type": "Int", + "id": "int", + "kind": "scalars", + "href": "/graphql/reference/scalars#int" + }, + { + "name": "field", + "description": "

The project field that contains this value.

", + "type": "ProjectV2FieldConfiguration!", + "id": "projectv2fieldconfiguration", + "kind": "unions", + "href": "/graphql/reference/unions#projectv2fieldconfiguration" + }, + { + "name": "item", + "description": "

The project item that contains this value.

", + "type": "ProjectV2Item!", + "id": "projectv2item", + "kind": "objects", + "href": "/graphql/reference/objects#projectv2item" + }, + { + "name": "name", + "description": "

The name of the selected single select option.

", + "type": "String", + "id": "string", + "kind": "scalars", + "href": "/graphql/reference/scalars#string" + }, + { + "name": "nameHTML", + "description": "

The html name of the selected single select option.

", + "type": "String", + "id": "string", + "kind": "scalars", + "href": "/graphql/reference/scalars#string" + }, + { + "name": "optionId", + "description": "

The id of the selected single select option.

", + "type": "String", + "id": "string", + "kind": "scalars", + "href": "/graphql/reference/scalars#string" + }, + { + "name": "updatedAt", + "description": "

Identifies the date and time when the object was last updated.

", + "type": "DateTime!", + "id": "datetime", + "kind": "scalars", + "href": "/graphql/reference/scalars#datetime" + } + ] + }, + { + "name": "ProjectV2ItemFieldTextValue", + "kind": "objects", + "id": "projectv2itemfieldtextvalue", + "href": "/graphql/reference/objects#projectv2itemfieldtextvalue", + "description": "

The value of a text field in a Project item.

", + "implements": [ + { + "name": "Node", + "id": "node", + "href": "/graphql/reference/interfaces#node" + }, + { + "name": "ProjectV2ItemFieldValueCommon", + "id": "projectv2itemfieldvaluecommon", + "href": "/graphql/reference/interfaces#projectv2itemfieldvaluecommon" + } + ], + "fields": [ + { + "name": "createdAt", + "description": "

Identifies the date and time when the object was created.

", + "type": "DateTime!", + "id": "datetime", + "kind": "scalars", + "href": "/graphql/reference/scalars#datetime" + }, + { + "name": "creator", + "description": "

The actor who created the item.

", + "type": "Actor", + "id": "actor", + "kind": "interfaces", + "href": "/graphql/reference/interfaces#actor" + }, + { + "name": "databaseId", + "description": "

Identifies the primary key from the database.

", + "type": "Int", + "id": "int", + "kind": "scalars", + "href": "/graphql/reference/scalars#int" + }, + { + "name": "field", + "description": "

The project field that contains this value.

", + "type": "ProjectV2FieldConfiguration!", + "id": "projectv2fieldconfiguration", + "kind": "unions", + "href": "/graphql/reference/unions#projectv2fieldconfiguration" + }, + { + "name": "item", + "description": "

The project item that contains this value.

", + "type": "ProjectV2Item!", + "id": "projectv2item", + "kind": "objects", + "href": "/graphql/reference/objects#projectv2item" + }, + { + "name": "text", + "description": "

Text value of a field.

", + "type": "String", + "id": "string", + "kind": "scalars", + "href": "/graphql/reference/scalars#string" + }, + { + "name": "updatedAt", + "description": "

Identifies the date and time when the object was last updated.

", + "type": "DateTime!", + "id": "datetime", + "kind": "scalars", + "href": "/graphql/reference/scalars#datetime" + } + ] + }, + { + "name": "ProjectV2ItemFieldUserValue", + "kind": "objects", + "id": "projectv2itemfielduservalue", + "href": "/graphql/reference/objects#projectv2itemfielduservalue", + "description": "

The value of a user field in a Project item.

", + "fields": [ + { + "name": "field", + "description": "

The field that contains this value.

", + "type": "ProjectV2FieldConfiguration!", + "id": "projectv2fieldconfiguration", + "kind": "unions", + "href": "/graphql/reference/unions#projectv2fieldconfiguration" + }, + { + "name": "users", + "description": "

The users for this field.

", + "type": "UserConnection", + "id": "userconnection", + "kind": "objects", + "href": "/graphql/reference/objects#userconnection", + "arguments": [ + { + "name": "after", + "description": "

Returns the elements in the list that come after the specified cursor.

", + "type": { + "name": "String", + "id": "string", + "kind": "scalars", + "href": "/graphql/reference/scalars#string" + } + }, + { + "name": "before", + "description": "

Returns the elements in the list that come before the specified cursor.

", + "type": { + "name": "String", + "id": "string", + "kind": "scalars", + "href": "/graphql/reference/scalars#string" + } + }, + { + "name": "first", + "description": "

Returns the first n elements from the list.

", + "type": { + "name": "Int", + "id": "int", + "kind": "scalars", + "href": "/graphql/reference/scalars#int" + } + }, + { + "name": "last", + "description": "

Returns the last n elements from the list.

", + "type": { + "name": "Int", + "id": "int", + "kind": "scalars", + "href": "/graphql/reference/scalars#int" + } + } + ] + } + ] + }, + { + "name": "ProjectV2ItemFieldValueConnection", + "kind": "objects", + "id": "projectv2itemfieldvalueconnection", + "href": "/graphql/reference/objects#projectv2itemfieldvalueconnection", + "description": "

The connection type for ProjectV2ItemFieldValue.

", + "fields": [ + { + "name": "edges", + "description": "

A list of edges.

", + "type": "[ProjectV2ItemFieldValueEdge]", + "id": "projectv2itemfieldvalueedge", + "kind": "objects", + "href": "/graphql/reference/objects#projectv2itemfieldvalueedge" + }, + { + "name": "nodes", + "description": "

A list of nodes.

", + "type": "[ProjectV2ItemFieldValue]", + "id": "projectv2itemfieldvalue", + "kind": "unions", + "href": "/graphql/reference/unions#projectv2itemfieldvalue" + }, + { + "name": "pageInfo", + "description": "

Information to aid in pagination.

", + "type": "PageInfo!", + "id": "pageinfo", + "kind": "objects", + "href": "/graphql/reference/objects#pageinfo" + }, + { + "name": "totalCount", + "description": "

Identifies the total count of items in the connection.

", + "type": "Int!", + "id": "int", + "kind": "scalars", + "href": "/graphql/reference/scalars#int" + } + ] + }, + { + "name": "ProjectV2ItemFieldValueEdge", + "kind": "objects", + "id": "projectv2itemfieldvalueedge", + "href": "/graphql/reference/objects#projectv2itemfieldvalueedge", + "description": "

An edge in a connection.

", + "fields": [ + { + "name": "cursor", + "description": "

A cursor for use in pagination.

", + "type": "String!", + "id": "string", + "kind": "scalars", + "href": "/graphql/reference/scalars#string" + }, + { + "name": "node", + "description": "

The item at the end of the edge.

", + "type": "ProjectV2ItemFieldValue", + "id": "projectv2itemfieldvalue", + "kind": "unions", + "href": "/graphql/reference/unions#projectv2itemfieldvalue" + } + ] + }, + { + "name": "ProjectV2IterationField", + "kind": "objects", + "id": "projectv2iterationfield", + "href": "/graphql/reference/objects#projectv2iterationfield", + "description": "

An iteration field inside a project.

", + "implements": [ + { + "name": "Node", + "id": "node", + "href": "/graphql/reference/interfaces#node" + }, + { + "name": "ProjectV2FieldCommon", + "id": "projectv2fieldcommon", + "href": "/graphql/reference/interfaces#projectv2fieldcommon" + } + ], + "fields": [ + { + "name": "configuration", + "description": "

Iteration configuration settings.

", + "type": "ProjectV2IterationFieldConfiguration!", + "id": "projectv2iterationfieldconfiguration", + "kind": "objects", + "href": "/graphql/reference/objects#projectv2iterationfieldconfiguration" + }, + { + "name": "createdAt", + "description": "

Identifies the date and time when the object was created.

", + "type": "DateTime!", + "id": "datetime", + "kind": "scalars", + "href": "/graphql/reference/scalars#datetime" + }, + { + "name": "dataType", + "description": "

The field's type.

", + "type": "ProjectV2FieldType!", + "id": "projectv2fieldtype", + "kind": "enums", + "href": "/graphql/reference/enums#projectv2fieldtype" + }, + { + "name": "databaseId", + "description": "

Identifies the primary key from the database.

", + "type": "Int", + "id": "int", + "kind": "scalars", + "href": "/graphql/reference/scalars#int" + }, + { + "name": "name", + "description": "

The project field's name.

", + "type": "String!", + "id": "string", + "kind": "scalars", + "href": "/graphql/reference/scalars#string" + }, + { + "name": "project", + "description": "

The project that contains this field.

", + "type": "ProjectV2!", + "id": "projectv2", + "kind": "objects", + "href": "/graphql/reference/objects#projectv2" + }, + { + "name": "updatedAt", + "description": "

Identifies the date and time when the object was last updated.

", + "type": "DateTime!", + "id": "datetime", + "kind": "scalars", + "href": "/graphql/reference/scalars#datetime" + } + ] + }, + { + "name": "ProjectV2IterationFieldConfiguration", + "kind": "objects", + "id": "projectv2iterationfieldconfiguration", + "href": "/graphql/reference/objects#projectv2iterationfieldconfiguration", + "description": "

Iteration field configuration for a project.

", + "fields": [ + { + "name": "completedIterations", + "description": "

The iteration's completed iterations.

", + "type": "[ProjectV2IterationFieldIteration!]!", + "id": "projectv2iterationfielditeration", + "kind": "objects", + "href": "/graphql/reference/objects#projectv2iterationfielditeration" + }, + { + "name": "duration", + "description": "

The iteration's duration in days.

", + "type": "Int!", + "id": "int", + "kind": "scalars", + "href": "/graphql/reference/scalars#int" + }, + { + "name": "iterations", + "description": "

The iteration's iterations.

", + "type": "[ProjectV2IterationFieldIteration!]!", + "id": "projectv2iterationfielditeration", + "kind": "objects", + "href": "/graphql/reference/objects#projectv2iterationfielditeration" + }, + { + "name": "startDay", + "description": "

The iteration's start day of the week.

", + "type": "Int!", + "id": "int", + "kind": "scalars", + "href": "/graphql/reference/scalars#int" + } + ] + }, + { + "name": "ProjectV2IterationFieldIteration", + "kind": "objects", + "id": "projectv2iterationfielditeration", + "href": "/graphql/reference/objects#projectv2iterationfielditeration", + "description": "

Iteration field iteration settings for a project.

", + "fields": [ + { + "name": "duration", + "description": "

The iteration's duration in days.

", + "type": "Int!", + "id": "int", + "kind": "scalars", + "href": "/graphql/reference/scalars#int" + }, + { + "name": "id", + "description": "

The iteration's ID.

", + "type": "String!", + "id": "string", + "kind": "scalars", + "href": "/graphql/reference/scalars#string" + }, + { + "name": "startDate", + "description": "

The iteration's start date.

", + "type": "Date!", + "id": "date", + "kind": "scalars", + "href": "/graphql/reference/scalars#date" + }, + { + "name": "title", + "description": "

The iteration's title.

", + "type": "String!", + "id": "string", + "kind": "scalars", + "href": "/graphql/reference/scalars#string" + }, + { + "name": "titleHTML", + "description": "

The iteration's html title.

", + "type": "String!", + "id": "string", + "kind": "scalars", + "href": "/graphql/reference/scalars#string" + } + ] + }, + { + "name": "ProjectV2SingleSelectField", + "kind": "objects", + "id": "projectv2singleselectfield", + "href": "/graphql/reference/objects#projectv2singleselectfield", + "description": "

A single select field inside a project.

", + "implements": [ + { + "name": "Node", + "id": "node", + "href": "/graphql/reference/interfaces#node" + }, + { + "name": "ProjectV2FieldCommon", + "id": "projectv2fieldcommon", + "href": "/graphql/reference/interfaces#projectv2fieldcommon" + } + ], + "fields": [ + { + "name": "createdAt", + "description": "

Identifies the date and time when the object was created.

", + "type": "DateTime!", + "id": "datetime", + "kind": "scalars", + "href": "/graphql/reference/scalars#datetime" + }, + { + "name": "dataType", + "description": "

The field's type.

", + "type": "ProjectV2FieldType!", + "id": "projectv2fieldtype", + "kind": "enums", + "href": "/graphql/reference/enums#projectv2fieldtype" + }, + { + "name": "databaseId", + "description": "

Identifies the primary key from the database.

", + "type": "Int", + "id": "int", + "kind": "scalars", + "href": "/graphql/reference/scalars#int" + }, + { + "name": "name", + "description": "

The project field's name.

", + "type": "String!", + "id": "string", + "kind": "scalars", + "href": "/graphql/reference/scalars#string" + }, + { + "name": "options", + "description": "

Options for the single select field.

", + "type": "[ProjectV2SingleSelectFieldOption!]!", + "id": "projectv2singleselectfieldoption", + "kind": "objects", + "href": "/graphql/reference/objects#projectv2singleselectfieldoption" + }, + { + "name": "project", + "description": "

The project that contains this field.

", + "type": "ProjectV2!", + "id": "projectv2", + "kind": "objects", + "href": "/graphql/reference/objects#projectv2" + }, + { + "name": "updatedAt", + "description": "

Identifies the date and time when the object was last updated.

", + "type": "DateTime!", + "id": "datetime", + "kind": "scalars", + "href": "/graphql/reference/scalars#datetime" + } + ] + }, + { + "name": "ProjectV2SingleSelectFieldOption", + "kind": "objects", + "id": "projectv2singleselectfieldoption", + "href": "/graphql/reference/objects#projectv2singleselectfieldoption", + "description": "

Single select field option for a configuration for a project.

", + "fields": [ + { + "name": "id", + "description": "

The option's ID.

", + "type": "String!", + "id": "string", + "kind": "scalars", + "href": "/graphql/reference/scalars#string" + }, + { + "name": "name", + "description": "

The option's name.

", + "type": "String!", + "id": "string", + "kind": "scalars", + "href": "/graphql/reference/scalars#string" + }, + { + "name": "nameHTML", + "description": "

The option's html name.

", + "type": "String!", + "id": "string", + "kind": "scalars", + "href": "/graphql/reference/scalars#string" + } + ] + }, + { + "name": "ProjectV2SortBy", + "kind": "objects", + "id": "projectv2sortby", + "href": "/graphql/reference/objects#projectv2sortby", + "description": "

Represents a sort by field and direction.

", + "fields": [ + { + "name": "direction", + "description": "

The direction of the sorting. Possible values are ASC and DESC.

", + "type": "OrderDirection!", + "id": "orderdirection", + "kind": "enums", + "href": "/graphql/reference/enums#orderdirection" + }, + { + "name": "field", + "description": "

The field by which items are sorted.

", + "type": "ProjectV2Field!", + "id": "projectv2field", + "kind": "objects", + "href": "/graphql/reference/objects#projectv2field" + } + ] + }, + { + "name": "ProjectV2SortByConnection", + "kind": "objects", + "id": "projectv2sortbyconnection", + "href": "/graphql/reference/objects#projectv2sortbyconnection", + "description": "

The connection type for ProjectV2SortBy.

", + "fields": [ + { + "name": "edges", + "description": "

A list of edges.

", + "type": "[ProjectV2SortByEdge]", + "id": "projectv2sortbyedge", + "kind": "objects", + "href": "/graphql/reference/objects#projectv2sortbyedge" + }, + { + "name": "nodes", + "description": "

A list of nodes.

", + "type": "[ProjectV2SortBy]", + "id": "projectv2sortby", + "kind": "objects", + "href": "/graphql/reference/objects#projectv2sortby" + }, + { + "name": "pageInfo", + "description": "

Information to aid in pagination.

", + "type": "PageInfo!", + "id": "pageinfo", + "kind": "objects", + "href": "/graphql/reference/objects#pageinfo" + }, + { + "name": "totalCount", + "description": "

Identifies the total count of items in the connection.

", + "type": "Int!", + "id": "int", + "kind": "scalars", + "href": "/graphql/reference/scalars#int" + } + ] + }, + { + "name": "ProjectV2SortByEdge", + "kind": "objects", + "id": "projectv2sortbyedge", + "href": "/graphql/reference/objects#projectv2sortbyedge", + "description": "

An edge in a connection.

", + "fields": [ + { + "name": "cursor", + "description": "

A cursor for use in pagination.

", + "type": "String!", + "id": "string", + "kind": "scalars", + "href": "/graphql/reference/scalars#string" + }, + { + "name": "node", + "description": "

The item at the end of the edge.

", + "type": "ProjectV2SortBy", + "id": "projectv2sortby", + "kind": "objects", + "href": "/graphql/reference/objects#projectv2sortby" + } + ] + }, + { + "name": "ProjectV2View", + "kind": "objects", + "id": "projectv2view", + "href": "/graphql/reference/objects#projectv2view", + "description": "

A view within a ProjectV2.

", + "implements": [ + { + "name": "Node", + "id": "node", + "href": "/graphql/reference/interfaces#node" + } + ], + "fields": [ + { + "name": "createdAt", + "description": "

Identifies the date and time when the object was created.

", + "type": "DateTime!", + "id": "datetime", + "kind": "scalars", + "href": "/graphql/reference/scalars#datetime" + }, + { + "name": "databaseId", + "description": "

Identifies the primary key from the database.

", + "type": "Int", + "id": "int", + "kind": "scalars", + "href": "/graphql/reference/scalars#int" + }, + { + "name": "filter", + "description": "

The project view's filter.

", + "type": "String", + "id": "string", + "kind": "scalars", + "href": "/graphql/reference/scalars#string" + }, + { + "name": "groupBy", + "description": "

The view's group-by field.

", + "type": "ProjectV2FieldConnection", + "id": "projectv2fieldconnection", + "kind": "objects", + "href": "/graphql/reference/objects#projectv2fieldconnection", + "arguments": [ + { + "name": "after", + "description": "

Returns the elements in the list that come after the specified cursor.

", + "type": { + "name": "String", + "id": "string", + "kind": "scalars", + "href": "/graphql/reference/scalars#string" + } + }, + { + "name": "before", + "description": "

Returns the elements in the list that come before the specified cursor.

", + "type": { + "name": "String", + "id": "string", + "kind": "scalars", + "href": "/graphql/reference/scalars#string" + } + }, + { + "name": "first", + "description": "

Returns the first n elements from the list.

", + "type": { + "name": "Int", + "id": "int", + "kind": "scalars", + "href": "/graphql/reference/scalars#int" + } + }, + { + "name": "last", + "description": "

Returns the last n elements from the list.

", + "type": { + "name": "Int", + "id": "int", + "kind": "scalars", + "href": "/graphql/reference/scalars#int" + } + }, + { + "name": "orderBy", + "description": "

Ordering options for the project v2 fields returned from the connection.

", + "type": { + "name": "ProjectV2FieldOrder", + "id": "projectv2fieldorder", + "kind": "input-objects", + "href": "/graphql/reference/input-objects#projectv2fieldorder" + } + } + ] + }, + { + "name": "layout", + "description": "

The project view's layout.

", + "type": "ProjectV2ViewLayout!", + "id": "projectv2viewlayout", + "kind": "enums", + "href": "/graphql/reference/enums#projectv2viewlayout" + }, + { + "name": "name", + "description": "

The project view's name.

", + "type": "String!", + "id": "string", + "kind": "scalars", + "href": "/graphql/reference/scalars#string" + }, + { + "name": "number", + "description": "

The project view's number.

", + "type": "Int!", + "id": "int", + "kind": "scalars", + "href": "/graphql/reference/scalars#int" + }, + { + "name": "project", + "description": "

The project that contains this view.

", + "type": "ProjectV2!", + "id": "projectv2", + "kind": "objects", + "href": "/graphql/reference/objects#projectv2" + }, + { + "name": "sortBy", + "description": "

The view's sort-by config.

", + "type": "ProjectV2SortByConnection", + "id": "projectv2sortbyconnection", + "kind": "objects", + "href": "/graphql/reference/objects#projectv2sortbyconnection", + "arguments": [ + { + "name": "after", + "description": "

Returns the elements in the list that come after the specified cursor.

", + "type": { + "name": "String", + "id": "string", + "kind": "scalars", + "href": "/graphql/reference/scalars#string" + } + }, + { + "name": "before", + "description": "

Returns the elements in the list that come before the specified cursor.

", + "type": { + "name": "String", + "id": "string", + "kind": "scalars", + "href": "/graphql/reference/scalars#string" + } + }, + { + "name": "first", + "description": "

Returns the first n elements from the list.

", + "type": { + "name": "Int", + "id": "int", + "kind": "scalars", + "href": "/graphql/reference/scalars#int" + } + }, + { + "name": "last", + "description": "

Returns the last n elements from the list.

", + "type": { + "name": "Int", + "id": "int", + "kind": "scalars", + "href": "/graphql/reference/scalars#int" + } + } + ] + }, + { + "name": "updatedAt", + "description": "

Identifies the date and time when the object was last updated.

", + "type": "DateTime!", + "id": "datetime", + "kind": "scalars", + "href": "/graphql/reference/scalars#datetime" + }, + { + "name": "verticalGroupBy", + "description": "

The view's vertical-group-by field.

", + "type": "ProjectV2FieldConnection", + "id": "projectv2fieldconnection", + "kind": "objects", + "href": "/graphql/reference/objects#projectv2fieldconnection", + "arguments": [ + { + "name": "after", + "description": "

Returns the elements in the list that come after the specified cursor.

", + "type": { + "name": "String", + "id": "string", + "kind": "scalars", + "href": "/graphql/reference/scalars#string" + } + }, + { + "name": "before", + "description": "

Returns the elements in the list that come before the specified cursor.

", + "type": { + "name": "String", + "id": "string", + "kind": "scalars", + "href": "/graphql/reference/scalars#string" + } + }, + { + "name": "first", + "description": "

Returns the first n elements from the list.

", + "type": { + "name": "Int", + "id": "int", + "kind": "scalars", + "href": "/graphql/reference/scalars#int" + } + }, + { + "name": "last", + "description": "

Returns the last n elements from the list.

", + "type": { + "name": "Int", + "id": "int", + "kind": "scalars", + "href": "/graphql/reference/scalars#int" + } + }, + { + "name": "orderBy", + "description": "

Ordering options for the project v2 fields returned from the connection.

", + "type": { + "name": "ProjectV2FieldOrder", + "id": "projectv2fieldorder", + "kind": "input-objects", + "href": "/graphql/reference/input-objects#projectv2fieldorder" + } + } + ] + }, + { + "name": "visibleFields", + "description": "

The view's visible fields.

", + "type": "ProjectV2FieldConnection", + "id": "projectv2fieldconnection", + "kind": "objects", + "href": "/graphql/reference/objects#projectv2fieldconnection", + "arguments": [ + { + "name": "after", + "description": "

Returns the elements in the list that come after the specified cursor.

", + "type": { + "name": "String", + "id": "string", + "kind": "scalars", + "href": "/graphql/reference/scalars#string" + } + }, + { + "name": "before", + "description": "

Returns the elements in the list that come before the specified cursor.

", + "type": { + "name": "String", + "id": "string", + "kind": "scalars", + "href": "/graphql/reference/scalars#string" + } + }, + { + "name": "first", + "description": "

Returns the first n elements from the list.

", + "type": { + "name": "Int", + "id": "int", + "kind": "scalars", + "href": "/graphql/reference/scalars#int" + } + }, + { + "name": "last", + "description": "

Returns the last n elements from the list.

", + "type": { + "name": "Int", + "id": "int", + "kind": "scalars", + "href": "/graphql/reference/scalars#int" + } + }, + { + "name": "orderBy", + "description": "

Ordering options for the project v2 fields returned from the connection.

", + "type": { + "name": "ProjectV2FieldOrder", + "id": "projectv2fieldorder", + "kind": "input-objects", + "href": "/graphql/reference/input-objects#projectv2fieldorder" + } + } + ] + } + ] + }, + { + "name": "ProjectV2ViewConnection", + "kind": "objects", + "id": "projectv2viewconnection", + "href": "/graphql/reference/objects#projectv2viewconnection", + "description": "

The connection type for ProjectV2View.

", + "fields": [ + { + "name": "edges", + "description": "

A list of edges.

", + "type": "[ProjectV2ViewEdge]", + "id": "projectv2viewedge", + "kind": "objects", + "href": "/graphql/reference/objects#projectv2viewedge" + }, + { + "name": "nodes", + "description": "

A list of nodes.

", + "type": "[ProjectV2View]", + "id": "projectv2view", + "kind": "objects", + "href": "/graphql/reference/objects#projectv2view" + }, + { + "name": "pageInfo", + "description": "

Information to aid in pagination.

", + "type": "PageInfo!", + "id": "pageinfo", + "kind": "objects", + "href": "/graphql/reference/objects#pageinfo" + }, + { + "name": "totalCount", + "description": "

Identifies the total count of items in the connection.

", + "type": "Int!", + "id": "int", + "kind": "scalars", + "href": "/graphql/reference/scalars#int" + } + ] + }, + { + "name": "ProjectV2ViewEdge", + "kind": "objects", + "id": "projectv2viewedge", + "href": "/graphql/reference/objects#projectv2viewedge", + "description": "

An edge in a connection.

", + "fields": [ + { + "name": "cursor", + "description": "

A cursor for use in pagination.

", + "type": "String!", + "id": "string", + "kind": "scalars", + "href": "/graphql/reference/scalars#string" + }, + { + "name": "node", + "description": "

The item at the end of the edge.

", + "type": "ProjectV2View", + "id": "projectv2view", + "kind": "objects", + "href": "/graphql/reference/objects#projectv2view" + } + ] + }, { "name": "PublicKey", "kind": "objects", @@ -36269,6 +39512,11 @@ "id": "node", "href": "/graphql/reference/interfaces#node" }, + { + "name": "ProjectV2Owner", + "id": "projectv2owner", + "href": "/graphql/reference/interfaces#projectv2owner" + }, { "name": "Reactable", "id": "reactable", @@ -37274,6 +40522,96 @@ } ] }, + { + "name": "projectV2", + "description": "

Find a project by number.

", + "type": "ProjectV2", + "id": "projectv2", + "kind": "objects", + "href": "/graphql/reference/objects#projectv2", + "arguments": [ + { + "name": "number", + "description": "

The project number.

", + "type": { + "name": "Int!", + "id": "int", + "kind": "scalars", + "href": "/graphql/reference/scalars#int" + } + } + ] + }, + { + "name": "projectsV2", + "description": "

A list of projects under the owner.

", + "type": "ProjectV2Connection!", + "id": "projectv2connection", + "kind": "objects", + "href": "/graphql/reference/objects#projectv2connection", + "arguments": [ + { + "name": "after", + "description": "

Returns the elements in the list that come after the specified cursor.

", + "type": { + "name": "String", + "id": "string", + "kind": "scalars", + "href": "/graphql/reference/scalars#string" + } + }, + { + "name": "before", + "description": "

Returns the elements in the list that come before the specified cursor.

", + "type": { + "name": "String", + "id": "string", + "kind": "scalars", + "href": "/graphql/reference/scalars#string" + } + }, + { + "name": "first", + "description": "

Returns the first n elements from the list.

", + "type": { + "name": "Int", + "id": "int", + "kind": "scalars", + "href": "/graphql/reference/scalars#int" + } + }, + { + "name": "last", + "description": "

Returns the last n elements from the list.

", + "type": { + "name": "Int", + "id": "int", + "kind": "scalars", + "href": "/graphql/reference/scalars#int" + } + }, + { + "name": "orderBy", + "description": "

How to order the returned projects.

", + "type": { + "name": "ProjectV2Order", + "id": "projectv2order", + "kind": "input-objects", + "href": "/graphql/reference/input-objects#projectv2order" + } + }, + { + "name": "query", + "description": "

A project to search for under the the owner.

", + "type": { + "name": "String", + "id": "string", + "kind": "scalars", + "href": "/graphql/reference/scalars#string" + } + } + ] + }, { "name": "publishedAt", "description": "

Identifies when the comment was published at.

", @@ -37834,6 +41172,14 @@ "kind": "scalars", "href": "/graphql/reference/scalars#boolean" }, + { + "name": "viewerCanEditFiles", + "description": "

Can the viewer edit files within this pull request.

", + "type": "Boolean!", + "id": "boolean", + "kind": "scalars", + "href": "/graphql/reference/scalars#boolean" + }, { "name": "viewerCanEnableAutoMerge", "description": "

Whether or not the viewer can enable auto-merge.

", @@ -39097,7 +42443,7 @@ }, { "name": "minimizedReason", - "description": "

Returns why the comment was minimized.

", + "description": "

Returns why the comment was minimized. One of abuse, off-topic,\noutdated, resolved, duplicate and spam. Note that the case and\nformatting of these values differs from the inputs to the MinimizeComment mutation.

", "type": "String", "id": "string", "kind": "scalars", @@ -39938,6 +43284,154 @@ } ] }, + { + "name": "PullRequestThread", + "kind": "objects", + "id": "pullrequestthread", + "href": "/graphql/reference/objects#pullrequestthread", + "description": "

A threaded list of comments for a given pull request.

", + "implements": [ + { + "name": "Node", + "id": "node", + "href": "/graphql/reference/interfaces#node" + } + ], + "fields": [ + { + "name": "comments", + "description": "

A list of pull request comments associated with the thread.

", + "type": "PullRequestReviewCommentConnection!", + "id": "pullrequestreviewcommentconnection", + "kind": "objects", + "href": "/graphql/reference/objects#pullrequestreviewcommentconnection", + "arguments": [ + { + "name": "after", + "description": "

Returns the elements in the list that come after the specified cursor.

", + "type": { + "name": "String", + "id": "string", + "kind": "scalars", + "href": "/graphql/reference/scalars#string" + } + }, + { + "name": "before", + "description": "

Returns the elements in the list that come before the specified cursor.

", + "type": { + "name": "String", + "id": "string", + "kind": "scalars", + "href": "/graphql/reference/scalars#string" + } + }, + { + "name": "first", + "description": "

Returns the first n elements from the list.

", + "type": { + "name": "Int", + "id": "int", + "kind": "scalars", + "href": "/graphql/reference/scalars#int" + } + }, + { + "name": "last", + "description": "

Returns the last n elements from the list.

", + "type": { + "name": "Int", + "id": "int", + "kind": "scalars", + "href": "/graphql/reference/scalars#int" + } + }, + { + "name": "skip", + "description": "

Skips the first n elements in the list.

", + "type": { + "name": "Int", + "id": "int", + "kind": "scalars", + "href": "/graphql/reference/scalars#int" + } + } + ] + }, + { + "name": "isCollapsed", + "description": "

Whether or not the thread has been collapsed (resolved).

", + "type": "Boolean!", + "id": "boolean", + "kind": "scalars", + "href": "/graphql/reference/scalars#boolean" + }, + { + "name": "isOutdated", + "description": "

Indicates whether this thread was outdated by newer changes.

", + "type": "Boolean!", + "id": "boolean", + "kind": "scalars", + "href": "/graphql/reference/scalars#boolean" + }, + { + "name": "isResolved", + "description": "

Whether this thread has been resolved.

", + "type": "Boolean!", + "id": "boolean", + "kind": "scalars", + "href": "/graphql/reference/scalars#boolean" + }, + { + "name": "pullRequest", + "description": "

Identifies the pull request associated with this thread.

", + "type": "PullRequest!", + "id": "pullrequest", + "kind": "objects", + "href": "/graphql/reference/objects#pullrequest" + }, + { + "name": "repository", + "description": "

Identifies the repository associated with this thread.

", + "type": "Repository!", + "id": "repository", + "kind": "objects", + "href": "/graphql/reference/objects#repository" + }, + { + "name": "resolvedBy", + "description": "

The user who resolved this thread.

", + "type": "User", + "id": "user", + "kind": "objects", + "href": "/graphql/reference/objects#user" + }, + { + "name": "viewerCanReply", + "description": "

Indicates whether the current viewer can reply to this thread.

", + "type": "Boolean!", + "id": "boolean", + "kind": "scalars", + "href": "/graphql/reference/scalars#boolean" + }, + { + "name": "viewerCanResolve", + "description": "

Whether or not the viewer can resolve this thread.

", + "type": "Boolean!", + "id": "boolean", + "kind": "scalars", + "href": "/graphql/reference/scalars#boolean" + }, + { + "name": "viewerCanUnresolve", + "description": "

Whether or not the viewer can unresolve this thread.

", + "type": "Boolean!", + "id": "boolean", + "kind": "scalars", + "href": "/graphql/reference/scalars#boolean" + } + ] + }, { "name": "PullRequestTimelineConnection", "kind": "objects", @@ -45928,6 +49422,11 @@ "id": "projectowner", "href": "/graphql/reference/interfaces#projectowner" }, + { + "name": "ProjectV2Recent", + "id": "projectv2recent", + "href": "/graphql/reference/interfaces#projectv2recent" + }, { "name": "RepositoryInfo", "id": "repositoryinfo", @@ -46481,6 +49980,26 @@ } ] }, + { + "name": "discussionCategory", + "description": "

A discussion category by slug.

", + "type": "DiscussionCategory", + "id": "discussioncategory", + "kind": "objects", + "href": "/graphql/reference/objects#discussioncategory", + "arguments": [ + { + "name": "slug", + "description": "

The slug of the discussion category to be returned.

", + "type": { + "name": "String!", + "id": "string", + "kind": "scalars", + "href": "/graphql/reference/scalars#string" + } + } + ] + }, { "name": "discussions", "description": "

A list of discussions that have been opened in the repository.

", @@ -47261,6 +50780,22 @@ "kind": "scalars", "href": "/graphql/reference/scalars#boolean" }, + { + "name": "mergeCommitMessage", + "description": "

How the default commit message will be generated when merging a pull request.

", + "type": "MergeCommitMessage!", + "id": "mergecommitmessage", + "kind": "enums", + "href": "/graphql/reference/enums#mergecommitmessage" + }, + { + "name": "mergeCommitTitle", + "description": "

How the default commit title will be generated when merging a pull request.

", + "type": "MergeCommitTitle!", + "id": "mergecommittitle", + "kind": "enums", + "href": "/graphql/reference/enums#mergecommittitle" + }, { "name": "milestone", "description": "

Returns a single milestone from the current repository by number.

", @@ -47897,6 +51432,56 @@ "kind": "scalars", "href": "/graphql/reference/scalars#boolean" }, + { + "name": "recentProjects", + "description": "

Recent projects that this user has modified in the context of the owner.

", + "type": "ProjectV2Connection!", + "id": "projectv2connection", + "kind": "objects", + "href": "/graphql/reference/objects#projectv2connection", + "arguments": [ + { + "name": "after", + "description": "

Returns the elements in the list that come after the specified cursor.

", + "type": { + "name": "String", + "id": "string", + "kind": "scalars", + "href": "/graphql/reference/scalars#string" + } + }, + { + "name": "before", + "description": "

Returns the elements in the list that come before the specified cursor.

", + "type": { + "name": "String", + "id": "string", + "kind": "scalars", + "href": "/graphql/reference/scalars#string" + } + }, + { + "name": "first", + "description": "

Returns the first n elements from the list.

", + "type": { + "name": "Int", + "id": "int", + "kind": "scalars", + "href": "/graphql/reference/scalars#int" + } + }, + { + "name": "last", + "description": "

Returns the last n elements from the list.

", + "type": { + "name": "Int", + "id": "int", + "kind": "scalars", + "href": "/graphql/reference/scalars#int" + } + } + ] + }, { "name": "ref", "description": "

Fetch a given ref from the repository.

", @@ -48182,6 +51767,22 @@ "kind": "scalars", "href": "/graphql/reference/scalars#boolean" }, + { + "name": "squashMergeCommitMessage", + "description": "

How the default commit message will be generated when squash merging a pull request.

", + "type": "SquashMergeCommitMessage!", + "id": "squashmergecommitmessage", + "kind": "enums", + "href": "/graphql/reference/enums#squashmergecommitmessage" + }, + { + "name": "squashMergeCommitTitle", + "description": "

How the default commit title will be generated when squash merging a pull request.

", + "type": "SquashMergeCommitTitle!", + "id": "squashmergecommittitle", + "kind": "enums", + "href": "/graphql/reference/enums#squashmergecommittitle" + }, { "name": "squashPrTitleUsedAsDefault", "description": "

Whether a squash merge commit can use the pull request title as default.

", @@ -48472,6 +52073,16 @@ "href": "/graphql/reference/scalars#string" } }, + { + "name": "dependencyScopes", + "description": "

Filter by the scope of the alert's dependency.

", + "type": { + "name": "[RepositoryVulnerabilityAlertDependencyScope!]", + "id": "repositoryvulnerabilityalertdependencyscope", + "kind": "enums", + "href": "/graphql/reference/enums#repositoryvulnerabilityalertdependencyscope" + } + }, { "name": "first", "description": "

Returns the first n elements from the list.

", @@ -48553,6 +52164,14 @@ } } ] + }, + { + "name": "webCommitSignoffRequired", + "description": "

Whether contributors are required to sign off on web-based commits in this repository.

", + "type": "Boolean!", + "id": "boolean", + "kind": "scalars", + "href": "/graphql/reference/scalars#boolean" } ] }, @@ -49628,6 +53247,22 @@ "kind": "objects", "href": "/graphql/reference/objects#dependabotupdate" }, + { + "name": "dependencyScope", + "description": "

The scope of an alert's dependency.

", + "type": "RepositoryVulnerabilityAlertDependencyScope", + "id": "repositoryvulnerabilityalertdependencyscope", + "kind": "enums", + "href": "/graphql/reference/enums#repositoryvulnerabilityalertdependencyscope" + }, + { + "name": "dismissComment", + "description": "

Comment explaining the reason the alert was dismissed.

", + "type": "String", + "id": "string", + "kind": "scalars", + "href": "/graphql/reference/scalars#string" + }, { "name": "dismissReason", "description": "

The reason the alert was dismissed.

", @@ -49658,7 +53293,9 @@ "type": "String", "id": "string", "kind": "scalars", - "href": "/graphql/reference/scalars#string" + "href": "/graphql/reference/scalars#string", + "isDeprecated": true, + "deprecationReason": "

The fixReason field is being removed. You can still use fixedAt and dismissReason. Removal on 2022-10-01 UTC.

" }, { "name": "fixedAt", @@ -49800,6 +53437,72 @@ } ] }, + { + "name": "RequestedReviewerConnection", + "kind": "objects", + "id": "requestedreviewerconnection", + "href": "/graphql/reference/objects#requestedreviewerconnection", + "description": "

The connection type for RequestedReviewer.

", + "fields": [ + { + "name": "edges", + "description": "

A list of edges.

", + "type": "[RequestedReviewerEdge]", + "id": "requestedrevieweredge", + "kind": "objects", + "href": "/graphql/reference/objects#requestedrevieweredge" + }, + { + "name": "nodes", + "description": "

A list of nodes.

", + "type": "[RequestedReviewer]", + "id": "requestedreviewer", + "kind": "unions", + "href": "/graphql/reference/unions#requestedreviewer" + }, + { + "name": "pageInfo", + "description": "

Information to aid in pagination.

", + "type": "PageInfo!", + "id": "pageinfo", + "kind": "objects", + "href": "/graphql/reference/objects#pageinfo" + }, + { + "name": "totalCount", + "description": "

Identifies the total count of items in the connection.

", + "type": "Int!", + "id": "int", + "kind": "scalars", + "href": "/graphql/reference/scalars#int" + } + ] + }, + { + "name": "RequestedReviewerEdge", + "kind": "objects", + "id": "requestedrevieweredge", + "href": "/graphql/reference/objects#requestedrevieweredge", + "description": "

An edge in a connection.

", + "fields": [ + { + "name": "cursor", + "description": "

A cursor for use in pagination.

", + "type": "String!", + "id": "string", + "kind": "scalars", + "href": "/graphql/reference/scalars#string" + }, + { + "name": "node", + "description": "

The item at the end of the edge.

", + "type": "RequestedReviewer", + "id": "requestedreviewer", + "kind": "unions", + "href": "/graphql/reference/unions#requestedreviewer" + } + ] + }, { "name": "RequiredStatusCheckDescription", "kind": "objects", @@ -51195,6 +54898,86 @@ } ] }, + { + "name": "SshSignature", + "kind": "objects", + "id": "sshsignature", + "href": "/graphql/reference/objects#sshsignature", + "description": "

Represents an SSH signature on a Commit or Tag.

", + "implements": [ + { + "name": "GitSignature", + "id": "gitsignature", + "href": "/graphql/reference/interfaces#gitsignature" + } + ], + "fields": [ + { + "name": "email", + "description": "

Email used to sign this object.

", + "type": "String!", + "id": "string", + "kind": "scalars", + "href": "/graphql/reference/scalars#string" + }, + { + "name": "isValid", + "description": "

True if the signature is valid and verified by GitHub.

", + "type": "Boolean!", + "id": "boolean", + "kind": "scalars", + "href": "/graphql/reference/scalars#boolean" + }, + { + "name": "keyFingerprint", + "description": "

Hex-encoded fingerprint of the key that signed this object.

", + "type": "String", + "id": "string", + "kind": "scalars", + "href": "/graphql/reference/scalars#string" + }, + { + "name": "payload", + "description": "

Payload for GPG signing object. Raw ODB object without the signature header.

", + "type": "String!", + "id": "string", + "kind": "scalars", + "href": "/graphql/reference/scalars#string" + }, + { + "name": "signature", + "description": "

ASCII-armored signature header from object.

", + "type": "String!", + "id": "string", + "kind": "scalars", + "href": "/graphql/reference/scalars#string" + }, + { + "name": "signer", + "description": "

GitHub user corresponding to the email signing this commit.

", + "type": "User", + "id": "user", + "kind": "objects", + "href": "/graphql/reference/objects#user" + }, + { + "name": "state", + "description": "

The state of this signature. VALID if signature is valid and verified by\nGitHub, otherwise represents reason why signature is considered invalid.

", + "type": "GitSignatureState!", + "id": "gitsignaturestate", + "kind": "enums", + "href": "/graphql/reference/enums#gitsignaturestate" + }, + { + "name": "wasSignedByGitHub", + "description": "

True if the signature was made with GitHub's signing key.

", + "type": "Boolean!", + "id": "boolean", + "kind": "scalars", + "href": "/graphql/reference/scalars#boolean" + } + ] + }, { "name": "StargazerConnection", "kind": "objects", @@ -52657,7 +56440,7 @@ }, { "name": "query", - "description": "

The search string to look for.

", + "description": "

The search string to look for. Repositories will be returned where the name contains your search string.

", "type": { "name": "String", "id": "string", @@ -55727,6 +59510,14 @@ "kind": "objects", "href": "/graphql/reference/objects#repository" }, + { + "name": "size", + "description": "

Entry byte size.

", + "type": "Int!", + "id": "int", + "kind": "scalars", + "href": "/graphql/reference/scalars#int" + }, { "name": "submodule", "description": "

If the TreeEntry is for a directory occupied by a submodule project, this returns the corresponding submodule.

", @@ -56131,6 +59922,16 @@ "id": "projectowner", "href": "/graphql/reference/interfaces#projectowner" }, + { + "name": "ProjectV2Owner", + "id": "projectv2owner", + "href": "/graphql/reference/interfaces#projectv2owner" + }, + { + "name": "ProjectV2Recent", + "id": "projectv2recent", + "href": "/graphql/reference/interfaces#projectv2recent" + }, { "name": "RepositoryDiscussionAuthor", "id": "repositorydiscussionauthor", @@ -57201,6 +61002,26 @@ } ] }, + { + "name": "projectV2", + "description": "

Find a project by number.

", + "type": "ProjectV2", + "id": "projectv2", + "kind": "objects", + "href": "/graphql/reference/objects#projectv2", + "arguments": [ + { + "name": "number", + "description": "

The project number.

", + "type": { + "name": "Int!", + "id": "int", + "kind": "scalars", + "href": "/graphql/reference/scalars#int" + } + } + ] + }, { "name": "projects", "description": "

A list of projects under the owner.

", @@ -57297,6 +61118,76 @@ "kind": "scalars", "href": "/graphql/reference/scalars#uri" }, + { + "name": "projectsV2", + "description": "

A list of projects under the owner.

", + "type": "ProjectV2Connection!", + "id": "projectv2connection", + "kind": "objects", + "href": "/graphql/reference/objects#projectv2connection", + "arguments": [ + { + "name": "after", + "description": "

Returns the elements in the list that come after the specified cursor.

", + "type": { + "name": "String", + "id": "string", + "kind": "scalars", + "href": "/graphql/reference/scalars#string" + } + }, + { + "name": "before", + "description": "

Returns the elements in the list that come before the specified cursor.

", + "type": { + "name": "String", + "id": "string", + "kind": "scalars", + "href": "/graphql/reference/scalars#string" + } + }, + { + "name": "first", + "description": "

Returns the first n elements from the list.

", + "type": { + "name": "Int", + "id": "int", + "kind": "scalars", + "href": "/graphql/reference/scalars#int" + } + }, + { + "name": "last", + "description": "

Returns the last n elements from the list.

", + "type": { + "name": "Int", + "id": "int", + "kind": "scalars", + "href": "/graphql/reference/scalars#int" + } + }, + { + "name": "orderBy", + "description": "

How to order the returned projects.

", + "type": { + "name": "ProjectV2Order", + "id": "projectv2order", + "kind": "input-objects", + "href": "/graphql/reference/input-objects#projectv2order" + } + }, + { + "name": "query", + "description": "

A project to search for under the the owner.

", + "type": { + "name": "String", + "id": "string", + "kind": "scalars", + "href": "/graphql/reference/scalars#string" + } + } + ] + }, { "name": "publicKeys", "description": "

A list of public keys associated with this user.

", @@ -57447,6 +61338,56 @@ } ] }, + { + "name": "recentProjects", + "description": "

Recent projects that this user has modified in the context of the owner.

", + "type": "ProjectV2Connection!", + "id": "projectv2connection", + "kind": "objects", + "href": "/graphql/reference/objects#projectv2connection", + "arguments": [ + { + "name": "after", + "description": "

Returns the elements in the list that come after the specified cursor.

", + "type": { + "name": "String", + "id": "string", + "kind": "scalars", + "href": "/graphql/reference/scalars#string" + } + }, + { + "name": "before", + "description": "

Returns the elements in the list that come before the specified cursor.

", + "type": { + "name": "String", + "id": "string", + "kind": "scalars", + "href": "/graphql/reference/scalars#string" + } + }, + { + "name": "first", + "description": "

Returns the first n elements from the list.

", + "type": { + "name": "Int", + "id": "int", + "kind": "scalars", + "href": "/graphql/reference/scalars#int" + } + }, + { + "name": "last", + "description": "

Returns the last n elements from the list.

", + "type": { + "name": "Int", + "id": "int", + "kind": "scalars", + "href": "/graphql/reference/scalars#int" + } + } + ] + }, { "name": "repositories", "description": "

A list of repositories that the user owns.

", @@ -58940,6 +62881,66 @@ "kind": "scalars", "href": "/graphql/reference/scalars#string" }, + { + "name": "runs", + "description": "

The runs of the workflow.

", + "type": "WorkflowRunConnection!", + "id": "workflowrunconnection", + "kind": "objects", + "href": "/graphql/reference/objects#workflowrunconnection", + "arguments": [ + { + "name": "after", + "description": "

Returns the elements in the list that come after the specified cursor.

", + "type": { + "name": "String", + "id": "string", + "kind": "scalars", + "href": "/graphql/reference/scalars#string" + } + }, + { + "name": "before", + "description": "

Returns the elements in the list that come before the specified cursor.

", + "type": { + "name": "String", + "id": "string", + "kind": "scalars", + "href": "/graphql/reference/scalars#string" + } + }, + { + "name": "first", + "description": "

Returns the first n elements from the list.

", + "type": { + "name": "Int", + "id": "int", + "kind": "scalars", + "href": "/graphql/reference/scalars#int" + } + }, + { + "name": "last", + "description": "

Returns the last n elements from the list.

", + "type": { + "name": "Int", + "id": "int", + "kind": "scalars", + "href": "/graphql/reference/scalars#int" + } + }, + { + "name": "orderBy", + "description": "

Ordering options for the connection.

", + "type": { + "name": "WorkflowRunOrder", + "id": "workflowrunorder", + "kind": "input-objects", + "href": "/graphql/reference/input-objects#workflowrunorder" + } + } + ] + }, { "name": "updatedAt", "description": "

Identifies the date and time when the object was last updated.

", @@ -59129,6 +63130,72 @@ "href": "/graphql/reference/objects#workflow" } ] + }, + { + "name": "WorkflowRunConnection", + "kind": "objects", + "id": "workflowrunconnection", + "href": "/graphql/reference/objects#workflowrunconnection", + "description": "

The connection type for WorkflowRun.

", + "fields": [ + { + "name": "edges", + "description": "

A list of edges.

", + "type": "[WorkflowRunEdge]", + "id": "workflowrunedge", + "kind": "objects", + "href": "/graphql/reference/objects#workflowrunedge" + }, + { + "name": "nodes", + "description": "

A list of nodes.

", + "type": "[WorkflowRun]", + "id": "workflowrun", + "kind": "objects", + "href": "/graphql/reference/objects#workflowrun" + }, + { + "name": "pageInfo", + "description": "

Information to aid in pagination.

", + "type": "PageInfo!", + "id": "pageinfo", + "kind": "objects", + "href": "/graphql/reference/objects#pageinfo" + }, + { + "name": "totalCount", + "description": "

Identifies the total count of items in the connection.

", + "type": "Int!", + "id": "int", + "kind": "scalars", + "href": "/graphql/reference/scalars#int" + } + ] + }, + { + "name": "WorkflowRunEdge", + "kind": "objects", + "id": "workflowrunedge", + "href": "/graphql/reference/objects#workflowrunedge", + "description": "

An edge in a connection.

", + "fields": [ + { + "name": "cursor", + "description": "

A cursor for use in pagination.

", + "type": "String!", + "id": "string", + "kind": "scalars", + "href": "/graphql/reference/scalars#string" + }, + { + "name": "node", + "description": "

The item at the end of the edge.

", + "type": "WorkflowRun", + "id": "workflowrun", + "kind": "objects", + "href": "/graphql/reference/objects#workflowrun" + } + ] } ], "interfaces": [ @@ -60036,7 +64103,7 @@ }, { "name": "minimizedReason", - "description": "

Returns why the comment was minimized.

", + "description": "

Returns why the comment was minimized. One of abuse, off-topic,\noutdated, resolved, duplicate and spam. Note that the case and\nformatting of these values differs from the inputs to the MinimizeComment mutation.

", "type": "String", "id": "string", "kind": "scalars", @@ -60588,6 +64655,278 @@ } ] }, + { + "name": "ProjectV2FieldCommon", + "kind": "interfaces", + "id": "projectv2fieldcommon", + "href": "/graphql/reference/interfaces#projectv2fieldcommon", + "description": "

Common fields across different project field types.

", + "fields": [ + { + "name": "createdAt", + "description": "

Identifies the date and time when the object was created.

", + "type": "DateTime!", + "id": "datetime", + "kind": "scalars", + "href": "/graphql/reference/scalars#datetime" + }, + { + "name": "dataType", + "description": "

The field's type.

", + "type": "ProjectV2FieldType!", + "id": "projectv2fieldtype", + "kind": "enums", + "href": "/graphql/reference/enums#projectv2fieldtype" + }, + { + "name": "databaseId", + "description": "

Identifies the primary key from the database.

", + "type": "Int", + "id": "int", + "kind": "scalars", + "href": "/graphql/reference/scalars#int" + }, + { + "name": "name", + "description": "

The project field's name.

", + "type": "String!", + "id": "string", + "kind": "scalars", + "href": "/graphql/reference/scalars#string" + }, + { + "name": "project", + "description": "

The project that contains this field.

", + "type": "ProjectV2!", + "id": "projectv2", + "kind": "objects", + "href": "/graphql/reference/objects#projectv2" + }, + { + "name": "updatedAt", + "description": "

Identifies the date and time when the object was last updated.

", + "type": "DateTime!", + "id": "datetime", + "kind": "scalars", + "href": "/graphql/reference/scalars#datetime" + } + ] + }, + { + "name": "ProjectV2ItemFieldValueCommon", + "kind": "interfaces", + "id": "projectv2itemfieldvaluecommon", + "href": "/graphql/reference/interfaces#projectv2itemfieldvaluecommon", + "description": "

Common fields across different project field value types.

", + "fields": [ + { + "name": "createdAt", + "description": "

Identifies the date and time when the object was created.

", + "type": "DateTime!", + "id": "datetime", + "kind": "scalars", + "href": "/graphql/reference/scalars#datetime" + }, + { + "name": "creator", + "description": "

The actor who created the item.

", + "type": "Actor", + "id": "actor", + "kind": "interfaces", + "href": "/graphql/reference/interfaces#actor" + }, + { + "name": "databaseId", + "description": "

Identifies the primary key from the database.

", + "type": "Int", + "id": "int", + "kind": "scalars", + "href": "/graphql/reference/scalars#int" + }, + { + "name": "field", + "description": "

The project field that contains this value.

", + "type": "ProjectV2FieldConfiguration!", + "id": "projectv2fieldconfiguration", + "kind": "unions", + "href": "/graphql/reference/unions#projectv2fieldconfiguration" + }, + { + "name": "item", + "description": "

The project item that contains this value.

", + "type": "ProjectV2Item!", + "id": "projectv2item", + "kind": "objects", + "href": "/graphql/reference/objects#projectv2item" + }, + { + "name": "updatedAt", + "description": "

Identifies the date and time when the object was last updated.

", + "type": "DateTime!", + "id": "datetime", + "kind": "scalars", + "href": "/graphql/reference/scalars#datetime" + } + ] + }, + { + "name": "ProjectV2Owner", + "kind": "interfaces", + "id": "projectv2owner", + "href": "/graphql/reference/interfaces#projectv2owner", + "description": "

Represents an owner of a project (beta).

", + "fields": [ + { + "name": "projectV2", + "description": "

Find a project by number.

", + "type": "ProjectV2", + "id": "projectv2", + "kind": "objects", + "href": "/graphql/reference/objects#projectv2", + "arguments": [ + { + "name": "number", + "description": "

The project number.

", + "type": { + "name": "Int!", + "id": "int", + "kind": "scalars", + "href": "/graphql/reference/scalars#int" + } + } + ] + }, + { + "name": "projectsV2", + "description": "

A list of projects under the owner.

", + "type": "ProjectV2Connection!", + "id": "projectv2connection", + "kind": "objects", + "href": "/graphql/reference/objects#projectv2connection", + "arguments": [ + { + "name": "after", + "description": "

Returns the elements in the list that come after the specified cursor.

", + "type": { + "name": "String", + "id": "string", + "kind": "scalars", + "href": "/graphql/reference/scalars#string" + } + }, + { + "name": "before", + "description": "

Returns the elements in the list that come before the specified cursor.

", + "type": { + "name": "String", + "id": "string", + "kind": "scalars", + "href": "/graphql/reference/scalars#string" + } + }, + { + "name": "first", + "description": "

Returns the first n elements from the list.

", + "type": { + "name": "Int", + "id": "int", + "kind": "scalars", + "href": "/graphql/reference/scalars#int" + } + }, + { + "name": "last", + "description": "

Returns the last n elements from the list.

", + "type": { + "name": "Int", + "id": "int", + "kind": "scalars", + "href": "/graphql/reference/scalars#int" + } + }, + { + "name": "orderBy", + "description": "

How to order the returned projects.

", + "type": { + "name": "ProjectV2Order", + "id": "projectv2order", + "kind": "input-objects", + "href": "/graphql/reference/input-objects#projectv2order" + } + }, + { + "name": "query", + "description": "

A project to search for under the the owner.

", + "type": { + "name": "String", + "id": "string", + "kind": "scalars", + "href": "/graphql/reference/scalars#string" + } + } + ] + } + ] + }, + { + "name": "ProjectV2Recent", + "kind": "interfaces", + "id": "projectv2recent", + "href": "/graphql/reference/interfaces#projectv2recent", + "description": "

Recent projects for the owner.

", + "fields": [ + { + "name": "recentProjects", + "description": "

Recent projects that this user has modified in the context of the owner.

", + "type": "ProjectV2Connection!", + "id": "projectv2connection", + "kind": "objects", + "href": "/graphql/reference/objects#projectv2connection", + "arguments": [ + { + "name": "after", + "description": "

Returns the elements in the list that come after the specified cursor.

", + "type": { + "name": "String", + "id": "string", + "kind": "scalars", + "href": "/graphql/reference/scalars#string" + } + }, + { + "name": "before", + "description": "

Returns the elements in the list that come before the specified cursor.

", + "type": { + "name": "String", + "id": "string", + "kind": "scalars", + "href": "/graphql/reference/scalars#string" + } + }, + { + "name": "first", + "description": "

Returns the first n elements from the list.

", + "type": { + "name": "Int", + "id": "int", + "kind": "scalars", + "href": "/graphql/reference/scalars#int" + } + }, + { + "name": "last", + "description": "

Returns the last n elements from the list.

", + "type": { + "name": "Int", + "id": "int", + "kind": "scalars", + "href": "/graphql/reference/scalars#int" + } + } + ] + } + ] + }, { "name": "Reactable", "kind": "interfaces", @@ -62170,6 +66509,23 @@ } ] }, + { + "name": "DiscussionPollOptionOrderField", + "kind": "enums", + "id": "discussionpolloptionorderfield", + "href": "/graphql/reference/enums#discussionpolloptionorderfield", + "description": "

Properties by which discussion poll option connections can be ordered.

", + "values": [ + { + "name": "AUTHORED_ORDER", + "description": "

Order poll options by the order that the poll author specified when creating the poll.

" + }, + { + "name": "VOTE_COUNT", + "description": "

Order poll options by the number of votes it has.

" + } + ] + }, { "name": "DismissReason", "kind": "enums", @@ -62946,6 +67302,44 @@ } ] }, + { + "name": "MergeCommitMessage", + "kind": "enums", + "id": "mergecommitmessage", + "href": "/graphql/reference/enums#mergecommitmessage", + "description": "

The possible default commit messages for merges.

", + "values": [ + { + "name": "BLANK", + "description": "

Default to a blank commit message.

" + }, + { + "name": "PR_BODY", + "description": "

Default to the pull request's body.

" + }, + { + "name": "PR_TITLE", + "description": "

Default to the pull request's title.

" + } + ] + }, + { + "name": "MergeCommitTitle", + "kind": "enums", + "id": "mergecommittitle", + "href": "/graphql/reference/enums#mergecommittitle", + "description": "

The possible default commit titles for merges.

", + "values": [ + { + "name": "MERGE_MESSAGE", + "description": "

Default to the classic title for a merge message (e.g., Merge pull request #123 from branch-name).

" + }, + { + "name": "PR_TITLE", + "description": "

Default to the pull request's title.

" + } + ] + }, { "name": "MergeStateStatus", "kind": "enums", @@ -63023,17 +67417,9 @@ "name": "BITBUCKET_SERVER", "description": "

A Bitbucket Server migration source.

" }, - { - "name": "GITHUB", - "description": "

A GitHub migration source.

" - }, { "name": "GITHUB_ARCHIVE", "description": "

A GitHub Migration API source.

" - }, - { - "name": "GITLAB", - "description": "

A GitLab migration source.

" } ] }, @@ -63311,6 +67697,10 @@ "name": "OUTSIDE_COLLABORATOR", "description": "

An outside collaborator is a person who isn't explicitly a member of the\nOrganization, but who has Read, Write, or Admin permissions to one or more\nrepositories in the organization.

" }, + { + "name": "SUSPENDED", + "description": "

A suspended member.

" + }, { "name": "UNAFFILIATED", "description": "

An unaffiliated collaborator is a person who is not a member of the\nOrganization and does not have access to any repositories in the Organization.

" @@ -63902,6 +68292,202 @@ } ] }, + { + "name": "ProjectV2FieldOrderField", + "kind": "enums", + "id": "projectv2fieldorderfield", + "href": "/graphql/reference/enums#projectv2fieldorderfield", + "description": "

Properties by which project v2 field connections can be ordered.

", + "values": [ + { + "name": "CREATED_AT", + "description": "

Order project v2 fields by creation time.

" + }, + { + "name": "NAME", + "description": "

Order project v2 fields by name.

" + }, + { + "name": "POSITION", + "description": "

Order project v2 fields by position.

" + } + ] + }, + { + "name": "ProjectV2FieldType", + "kind": "enums", + "id": "projectv2fieldtype", + "href": "/graphql/reference/enums#projectv2fieldtype", + "description": "

The type of a project field.

", + "values": [ + { + "name": "ASSIGNEES", + "description": "

Assignees.

" + }, + { + "name": "DATE", + "description": "

Date.

" + }, + { + "name": "ITERATION", + "description": "

Iteration.

" + }, + { + "name": "LABELS", + "description": "

Labels.

" + }, + { + "name": "LINKED_PULL_REQUESTS", + "description": "

Linked Pull Requests.

" + }, + { + "name": "MILESTONE", + "description": "

Milestone.

" + }, + { + "name": "NUMBER", + "description": "

Number.

" + }, + { + "name": "REPOSITORY", + "description": "

Repository.

" + }, + { + "name": "REVIEWERS", + "description": "

Reviewers.

" + }, + { + "name": "SINGLE_SELECT", + "description": "

Single Select.

" + }, + { + "name": "TEXT", + "description": "

Text.

" + }, + { + "name": "TITLE", + "description": "

Title.

" + }, + { + "name": "TRACKS", + "description": "

Tracks.

" + } + ] + }, + { + "name": "ProjectV2ItemFieldValueOrderField", + "kind": "enums", + "id": "projectv2itemfieldvalueorderfield", + "href": "/graphql/reference/enums#projectv2itemfieldvalueorderfield", + "description": "

Properties by which project v2 item field value connections can be ordered.

", + "values": [ + { + "name": "POSITION", + "description": "

Order project v2 item field values by the their position in the project.

" + } + ] + }, + { + "name": "ProjectV2ItemOrderField", + "kind": "enums", + "id": "projectv2itemorderfield", + "href": "/graphql/reference/enums#projectv2itemorderfield", + "description": "

Properties by which project v2 item connections can be ordered.

", + "values": [ + { + "name": "POSITION", + "description": "

Order project v2 items by the their position in the project.

" + } + ] + }, + { + "name": "ProjectV2ItemType", + "kind": "enums", + "id": "projectv2itemtype", + "href": "/graphql/reference/enums#projectv2itemtype", + "description": "

The type of a project item.

", + "values": [ + { + "name": "DRAFT_ISSUE", + "description": "

Draft Issue.

" + }, + { + "name": "ISSUE", + "description": "

Issue.

" + }, + { + "name": "PULL_REQUEST", + "description": "

Pull Request.

" + }, + { + "name": "REDACTED", + "description": "

Redacted Item.

" + } + ] + }, + { + "name": "ProjectV2OrderField", + "kind": "enums", + "id": "projectv2orderfield", + "href": "/graphql/reference/enums#projectv2orderfield", + "description": "

Properties by which projects can be ordered.

", + "values": [ + { + "name": "CREATED_AT", + "description": "

The project's date and time of creation.

" + }, + { + "name": "NUMBER", + "description": "

The project's number.

" + }, + { + "name": "TITLE", + "description": "

The project's title.

" + }, + { + "name": "UPDATED_AT", + "description": "

The project's date and time of update.

" + } + ] + }, + { + "name": "ProjectV2ViewLayout", + "kind": "enums", + "id": "projectv2viewlayout", + "href": "/graphql/reference/enums#projectv2viewlayout", + "description": "

The layout of a project v2 view.

", + "values": [ + { + "name": "BOARD_LAYOUT", + "description": "

Board layout.

" + }, + { + "name": "TABLE_LAYOUT", + "description": "

Table layout.

" + } + ] + }, + { + "name": "ProjectV2ViewOrderField", + "kind": "enums", + "id": "projectv2vieworderfield", + "href": "/graphql/reference/enums#projectv2vieworderfield", + "description": "

Properties by which project v2 view connections can be ordered.

", + "values": [ + { + "name": "CREATED_AT", + "description": "

Order project v2 views by creation time.

" + }, + { + "name": "NAME", + "description": "

Order project v2 views by name.

" + }, + { + "name": "POSITION", + "description": "

Order project v2 views by position.

" + } + ] + }, { "name": "PullRequestMergeMethod", "kind": "enums", @@ -64785,6 +69371,23 @@ } ] }, + { + "name": "RepositoryVulnerabilityAlertDependencyScope", + "kind": "enums", + "id": "repositoryvulnerabilityalertdependencyscope", + "href": "/graphql/reference/enums#repositoryvulnerabilityalertdependencyscope", + "description": "

The possible scopes of an alert's dependency.

", + "values": [ + { + "name": "DEVELOPMENT", + "description": "

A dependency that is only used in development.

" + }, + { + "name": "RUNTIME", + "description": "

A dependency that is leveraged during application runtime.

" + } + ] + }, { "name": "RepositoryVulnerabilityAlertState", "kind": "enums", @@ -64968,10 +69571,18 @@ "href": "/graphql/reference/enums#securityadvisoryecosystem", "description": "

The possible ecosystems of a security vulnerability's package.

", "values": [ + { + "name": "ACTIONS", + "description": "

GitHub Actions.

" + }, { "name": "COMPOSER", "description": "

PHP packages hosted at packagist.org.

" }, + { + "name": "ERLANG", + "description": "

Erlang/Elixir packages hosted at hex.pm.

" + }, { "name": "GO", "description": "

Go modules.

" @@ -65027,6 +69638,44 @@ } ] }, + { + "name": "SquashMergeCommitMessage", + "kind": "enums", + "id": "squashmergecommitmessage", + "href": "/graphql/reference/enums#squashmergecommitmessage", + "description": "

The possible default commit messages for squash merges.

", + "values": [ + { + "name": "BLANK", + "description": "

Default to a blank commit message.

" + }, + { + "name": "COMMIT_MESSAGES", + "description": "

Default to the branch's commit messages.

" + }, + { + "name": "PR_BODY", + "description": "

Default to the pull request's body.

" + } + ] + }, + { + "name": "SquashMergeCommitTitle", + "kind": "enums", + "id": "squashmergecommittitle", + "href": "/graphql/reference/enums#squashmergecommittitle", + "description": "

The possible default commit titles for squash merges.

", + "values": [ + { + "name": "COMMIT_OR_PR_TITLE", + "description": "

Default to the commit's title (if only one commit) or the pull request's title (when more than one commit).

" + }, + { + "name": "PR_TITLE", + "description": "

Default to the pull request's title.

" + } + ] + }, { "name": "StarOrderField", "kind": "enums", @@ -65345,6 +69994,19 @@ "description": "

Order verifiable domains by the domain name.

" } ] + }, + { + "name": "WorkflowRunOrderField", + "kind": "enums", + "id": "workflowrunorderfield", + "href": "/graphql/reference/enums#workflowrunorderfield", + "description": "

Properties by which workflow run connections can be ordered.

", + "values": [ + { + "name": "CREATED_AT", + "description": "

Order workflow runs by most recently created.

" + } + ] } ], "unions": [ @@ -66192,6 +70854,25 @@ } ] }, + { + "name": "OrganizationOrUser", + "kind": "unions", + "id": "organizationoruser", + "href": "/graphql/reference/unions#organizationoruser", + "description": "

Used for argument of CreateProjectV2 mutation.

", + "possibleTypes": [ + { + "name": "Organization", + "id": "organization", + "href": "/graphql/reference/objects#organization" + }, + { + "name": "User", + "id": "user", + "href": "/graphql/reference/objects#user" + } + ] + }, { "name": "PermissionGranter", "kind": "unions", @@ -66254,6 +70935,118 @@ } ] }, + { + "name": "ProjectV2FieldConfiguration", + "kind": "unions", + "id": "projectv2fieldconfiguration", + "href": "/graphql/reference/unions#projectv2fieldconfiguration", + "description": "

Configurations for project fields.

", + "possibleTypes": [ + { + "name": "ProjectV2Field", + "id": "projectv2field", + "href": "/graphql/reference/objects#projectv2field" + }, + { + "name": "ProjectV2IterationField", + "id": "projectv2iterationfield", + "href": "/graphql/reference/objects#projectv2iterationfield" + }, + { + "name": "ProjectV2SingleSelectField", + "id": "projectv2singleselectfield", + "href": "/graphql/reference/objects#projectv2singleselectfield" + } + ] + }, + { + "name": "ProjectV2ItemContent", + "kind": "unions", + "id": "projectv2itemcontent", + "href": "/graphql/reference/unions#projectv2itemcontent", + "description": "

Types that can be inside Project Items.

", + "possibleTypes": [ + { + "name": "DraftIssue", + "id": "draftissue", + "href": "/graphql/reference/objects#draftissue" + }, + { + "name": "Issue", + "id": "issue", + "href": "/graphql/reference/objects#issue" + }, + { + "name": "PullRequest", + "id": "pullrequest", + "href": "/graphql/reference/objects#pullrequest" + } + ] + }, + { + "name": "ProjectV2ItemFieldValue", + "kind": "unions", + "id": "projectv2itemfieldvalue", + "href": "/graphql/reference/unions#projectv2itemfieldvalue", + "description": "

Project field values.

", + "possibleTypes": [ + { + "name": "ProjectV2ItemFieldDateValue", + "id": "projectv2itemfielddatevalue", + "href": "/graphql/reference/objects#projectv2itemfielddatevalue" + }, + { + "name": "ProjectV2ItemFieldIterationValue", + "id": "projectv2itemfielditerationvalue", + "href": "/graphql/reference/objects#projectv2itemfielditerationvalue" + }, + { + "name": "ProjectV2ItemFieldLabelValue", + "id": "projectv2itemfieldlabelvalue", + "href": "/graphql/reference/objects#projectv2itemfieldlabelvalue" + }, + { + "name": "ProjectV2ItemFieldMilestoneValue", + "id": "projectv2itemfieldmilestonevalue", + "href": "/graphql/reference/objects#projectv2itemfieldmilestonevalue" + }, + { + "name": "ProjectV2ItemFieldNumberValue", + "id": "projectv2itemfieldnumbervalue", + "href": "/graphql/reference/objects#projectv2itemfieldnumbervalue" + }, + { + "name": "ProjectV2ItemFieldPullRequestValue", + "id": "projectv2itemfieldpullrequestvalue", + "href": "/graphql/reference/objects#projectv2itemfieldpullrequestvalue" + }, + { + "name": "ProjectV2ItemFieldRepositoryValue", + "id": "projectv2itemfieldrepositoryvalue", + "href": "/graphql/reference/objects#projectv2itemfieldrepositoryvalue" + }, + { + "name": "ProjectV2ItemFieldReviewerValue", + "id": "projectv2itemfieldreviewervalue", + "href": "/graphql/reference/objects#projectv2itemfieldreviewervalue" + }, + { + "name": "ProjectV2ItemFieldSingleSelectValue", + "id": "projectv2itemfieldsingleselectvalue", + "href": "/graphql/reference/objects#projectv2itemfieldsingleselectvalue" + }, + { + "name": "ProjectV2ItemFieldTextValue", + "id": "projectv2itemfieldtextvalue", + "href": "/graphql/reference/objects#projectv2itemfieldtextvalue" + }, + { + "name": "ProjectV2ItemFieldUserValue", + "id": "projectv2itemfielduservalue", + "href": "/graphql/reference/objects#projectv2itemfielduservalue" + } + ] + }, { "name": "PullRequestTimelineItem", "kind": "unions", @@ -67078,6 +71871,32 @@ } ] }, + { + "name": "AddDiscussionPollVoteInput", + "kind": "inputObjects", + "id": "adddiscussionpollvoteinput", + "href": "/graphql/reference/input-objects#adddiscussionpollvoteinput", + "description": "

Autogenerated input type of AddDiscussionPollVote.

", + "inputFields": [ + { + "name": "clientMutationId", + "description": "

A unique identifier for the client performing the mutation.

", + "type": "String", + "id": "string", + "kind": "scalars", + "href": "/graphql/reference/scalars#string" + }, + { + "name": "pollOptionId", + "description": "

The Node ID of the discussion poll option to vote for.

", + "type": "ID!", + "id": "id", + "kind": "scalars", + "href": "/graphql/reference/scalars#id", + "isDeprecated": false + } + ] + }, { "name": "AddEnterpriseAdminInput", "kind": "inputObjects", @@ -67224,6 +72043,92 @@ } ] }, + { + "name": "AddProjectV2DraftIssueInput", + "kind": "inputObjects", + "id": "addprojectv2draftissueinput", + "href": "/graphql/reference/input-objects#addprojectv2draftissueinput", + "description": "

Autogenerated input type of AddProjectV2DraftIssue.

", + "inputFields": [ + { + "name": "assigneeIds", + "description": "

The IDs of the assignees of the draft issue.

", + "type": "[ID!]", + "id": "id", + "kind": "scalars", + "href": "/graphql/reference/scalars#id", + "isDeprecated": false + }, + { + "name": "body", + "description": "

The body of the draft issue.

", + "type": "String", + "id": "string", + "kind": "scalars", + "href": "/graphql/reference/scalars#string" + }, + { + "name": "clientMutationId", + "description": "

A unique identifier for the client performing the mutation.

", + "type": "String", + "id": "string", + "kind": "scalars", + "href": "/graphql/reference/scalars#string" + }, + { + "name": "projectId", + "description": "

The ID of the Project to add the draft issue to.

", + "type": "ID!", + "id": "id", + "kind": "scalars", + "href": "/graphql/reference/scalars#id", + "isDeprecated": false + }, + { + "name": "title", + "description": "

The title of the draft issue.

", + "type": "String!", + "id": "string", + "kind": "scalars", + "href": "/graphql/reference/scalars#string" + } + ] + }, + { + "name": "AddProjectV2ItemByIdInput", + "kind": "inputObjects", + "id": "addprojectv2itembyidinput", + "href": "/graphql/reference/input-objects#addprojectv2itembyidinput", + "description": "

Autogenerated input type of AddProjectV2ItemById.

", + "inputFields": [ + { + "name": "clientMutationId", + "description": "

A unique identifier for the client performing the mutation.

", + "type": "String", + "id": "string", + "kind": "scalars", + "href": "/graphql/reference/scalars#string" + }, + { + "name": "contentId", + "description": "

The id of the Issue or Pull Request to add.

", + "type": "ID!", + "id": "id", + "kind": "scalars", + "href": "/graphql/reference/scalars#id", + "isDeprecated": false + }, + { + "name": "projectId", + "description": "

The ID of the Project to add the item to.

", + "type": "ID!", + "id": "id", + "kind": "scalars", + "href": "/graphql/reference/scalars#id", + "isDeprecated": false + } + ] + }, { "name": "AddPullRequestReviewCommentInput", "kind": "inputObjects", @@ -67908,13 +72813,29 @@ "kind": "enums", "href": "/graphql/reference/enums#checkruntype" }, + { + "name": "conclusions", + "description": "

Filters the check runs by these conclusions.

", + "type": "[CheckConclusionState!]", + "id": "checkconclusionstate", + "kind": "enums", + "href": "/graphql/reference/enums#checkconclusionstate" + }, { "name": "status", - "description": "

Filters the check runs by this status.

", + "description": "

Filters the check runs by this status. Superceded by statuses.

", "type": "CheckStatusState", "id": "checkstatusstate", "kind": "enums", "href": "/graphql/reference/enums#checkstatusstate" + }, + { + "name": "statuses", + "description": "

Filters the check runs by this status. Overrides status.

", + "type": "[CheckStatusState!]", + "id": "checkstatusstate", + "kind": "enums", + "href": "/graphql/reference/enums#checkstatusstate" } ] }, @@ -68350,7 +73271,7 @@ "kind": "inputObjects", "id": "committablebranch", "href": "/graphql/reference/input-objects#committablebranch", - "description": "

A git ref for a commit to be appended to.

\n

The ref must be a branch, i.e. its fully qualified name must start\nwith refs/heads/ (although the input is not required to be fully\nqualified).

\n

The Ref may be specified by its global node ID or by the\nrepository nameWithOwner and branch name.

\n

Examples

\n

Specify a branch using a global node ID:

\n
{ \"id\": \"MDM6UmVmMTpyZWZzL2hlYWRzL21haW4=\" }\n
\n

Specify a branch using nameWithOwner and branch name:

\n
{\n  \"nameWithOwner\": \"github/graphql-client\",\n  \"branchName\": \"main\"\n}.\n
", + "description": "

A git ref for a commit to be appended to.

\n

The ref must be a branch, i.e. its fully qualified name must start\nwith refs/heads/ (although the input is not required to be fully\nqualified).

\n

The Ref may be specified by its global node ID or by the\nrepositoryNameWithOwner and branchName.

\n

Examples

\n

Specify a branch using a global node ID:

\n
{ \"id\": \"MDM6UmVmMTpyZWZzL2hlYWRzL21haW4=\" }\n
\n

Specify a branch using repositoryNameWithOwner and branchName:

\n
{\n  \"repositoryNameWithOwner\": \"github/graphql-client\",\n  \"branchName\": \"main\"\n}.\n
", "inputFields": [ { "name": "branchName", @@ -69522,6 +74443,40 @@ } ] }, + { + "name": "CreateProjectV2Input", + "kind": "inputObjects", + "id": "createprojectv2input", + "href": "/graphql/reference/input-objects#createprojectv2input", + "description": "

Autogenerated input type of CreateProjectV2.

", + "inputFields": [ + { + "name": "clientMutationId", + "description": "

A unique identifier for the client performing the mutation.

", + "type": "String", + "id": "string", + "kind": "scalars", + "href": "/graphql/reference/scalars#string" + }, + { + "name": "ownerId", + "description": "

The owner ID to create the project under.

", + "type": "ID!", + "id": "id", + "kind": "scalars", + "href": "/graphql/reference/scalars#id", + "isDeprecated": false + }, + { + "name": "title", + "description": "

The title of the project.

", + "type": "String!", + "id": "string", + "kind": "scalars", + "href": "/graphql/reference/scalars#string" + } + ] + }, { "name": "CreatePullRequestInput", "kind": "inputObjects", @@ -70167,6 +75122,41 @@ } ] }, + { + "name": "DeleteProjectV2ItemInput", + "kind": "inputObjects", + "id": "deleteprojectv2iteminput", + "href": "/graphql/reference/input-objects#deleteprojectv2iteminput", + "description": "

Autogenerated input type of DeleteProjectV2Item.

", + "inputFields": [ + { + "name": "clientMutationId", + "description": "

A unique identifier for the client performing the mutation.

", + "type": "String", + "id": "string", + "kind": "scalars", + "href": "/graphql/reference/scalars#string" + }, + { + "name": "itemId", + "description": "

The ID of the item to be removed.

", + "type": "ID!", + "id": "id", + "kind": "scalars", + "href": "/graphql/reference/scalars#id", + "isDeprecated": false + }, + { + "name": "projectId", + "description": "

The ID of the Project from which the item should be removed.

", + "type": "ID!", + "id": "id", + "kind": "scalars", + "href": "/graphql/reference/scalars#id", + "isDeprecated": false + } + ] + }, { "name": "DeletePullRequestReviewCommentInput", "kind": "inputObjects", @@ -70399,6 +75389,31 @@ } ] }, + { + "name": "DiscussionPollOptionOrder", + "kind": "inputObjects", + "id": "discussionpolloptionorder", + "href": "/graphql/reference/input-objects#discussionpolloptionorder", + "description": "

Ordering options for discussion poll option connections.

", + "inputFields": [ + { + "name": "direction", + "description": "

The ordering direction.

", + "type": "OrderDirection!", + "id": "orderdirection", + "kind": "enums", + "href": "/graphql/reference/enums#orderdirection" + }, + { + "name": "field", + "description": "

The field to order poll options by.

", + "type": "DiscussionPollOptionOrderField!", + "id": "discussionpolloptionorderfield", + "kind": "enums", + "href": "/graphql/reference/enums#discussionpolloptionorderfield" + } + ] + }, { "name": "DismissPullRequestReviewInput", "kind": "inputObjects", @@ -70598,7 +75613,7 @@ }, { "name": "mergeMethod", - "description": "

The merge method to use. If omitted, defaults to 'MERGE'.

", + "description": "

The merge method to use. If omitted, defaults to MERGE.

", "type": "PullRequestMergeMethod", "id": "pullrequestmergemethod", "kind": "enums", @@ -71866,6 +76881,180 @@ } ] }, + { + "name": "ProjectV2FieldOrder", + "kind": "inputObjects", + "id": "projectv2fieldorder", + "href": "/graphql/reference/input-objects#projectv2fieldorder", + "description": "

Ordering options for project v2 field connections.

", + "inputFields": [ + { + "name": "direction", + "description": "

The ordering direction.

", + "type": "OrderDirection!", + "id": "orderdirection", + "kind": "enums", + "href": "/graphql/reference/enums#orderdirection" + }, + { + "name": "field", + "description": "

The field to order the project v2 fields by.

", + "type": "ProjectV2FieldOrderField!", + "id": "projectv2fieldorderfield", + "kind": "enums", + "href": "/graphql/reference/enums#projectv2fieldorderfield" + } + ] + }, + { + "name": "ProjectV2FieldValue", + "kind": "inputObjects", + "id": "projectv2fieldvalue", + "href": "/graphql/reference/input-objects#projectv2fieldvalue", + "description": "

The values that can be used to update a field of an item inside a Project. Only 1 value can be updated at a time.

", + "inputFields": [ + { + "name": "date", + "description": "

The ISO 8601 date to set on the field.

", + "type": "Date", + "id": "date", + "kind": "scalars", + "href": "/graphql/reference/scalars#date" + }, + { + "name": "iterationId", + "description": "

The id of the iteration to set on the field.

", + "type": "String", + "id": "string", + "kind": "scalars", + "href": "/graphql/reference/scalars#string" + }, + { + "name": "number", + "description": "

The number to set on the field.

", + "type": "Float", + "id": "float", + "kind": "scalars", + "href": "/graphql/reference/scalars#float" + }, + { + "name": "singleSelectOptionId", + "description": "

The id of the single select option to set on the field.

", + "type": "String", + "id": "string", + "kind": "scalars", + "href": "/graphql/reference/scalars#string" + }, + { + "name": "text", + "description": "

The text to set on the field.

", + "type": "String", + "id": "string", + "kind": "scalars", + "href": "/graphql/reference/scalars#string" + } + ] + }, + { + "name": "ProjectV2ItemFieldValueOrder", + "kind": "inputObjects", + "id": "projectv2itemfieldvalueorder", + "href": "/graphql/reference/input-objects#projectv2itemfieldvalueorder", + "description": "

Ordering options for project v2 item field value connections.

", + "inputFields": [ + { + "name": "direction", + "description": "

The ordering direction.

", + "type": "OrderDirection!", + "id": "orderdirection", + "kind": "enums", + "href": "/graphql/reference/enums#orderdirection" + }, + { + "name": "field", + "description": "

The field to order the project v2 item field values by.

", + "type": "ProjectV2ItemFieldValueOrderField!", + "id": "projectv2itemfieldvalueorderfield", + "kind": "enums", + "href": "/graphql/reference/enums#projectv2itemfieldvalueorderfield" + } + ] + }, + { + "name": "ProjectV2ItemOrder", + "kind": "inputObjects", + "id": "projectv2itemorder", + "href": "/graphql/reference/input-objects#projectv2itemorder", + "description": "

Ordering options for project v2 item connections.

", + "inputFields": [ + { + "name": "direction", + "description": "

The ordering direction.

", + "type": "OrderDirection!", + "id": "orderdirection", + "kind": "enums", + "href": "/graphql/reference/enums#orderdirection" + }, + { + "name": "field", + "description": "

The field to order the project v2 items by.

", + "type": "ProjectV2ItemOrderField!", + "id": "projectv2itemorderfield", + "kind": "enums", + "href": "/graphql/reference/enums#projectv2itemorderfield" + } + ] + }, + { + "name": "ProjectV2Order", + "kind": "inputObjects", + "id": "projectv2order", + "href": "/graphql/reference/input-objects#projectv2order", + "description": "

Ways in which lists of projects can be ordered upon return.

", + "inputFields": [ + { + "name": "direction", + "description": "

The direction in which to order projects by the specified field.

", + "type": "OrderDirection!", + "id": "orderdirection", + "kind": "enums", + "href": "/graphql/reference/enums#orderdirection" + }, + { + "name": "field", + "description": "

The field in which to order projects by.

", + "type": "ProjectV2OrderField!", + "id": "projectv2orderfield", + "kind": "enums", + "href": "/graphql/reference/enums#projectv2orderfield" + } + ] + }, + { + "name": "ProjectV2ViewOrder", + "kind": "inputObjects", + "id": "projectv2vieworder", + "href": "/graphql/reference/input-objects#projectv2vieworder", + "description": "

Ordering options for project v2 view connections.

", + "inputFields": [ + { + "name": "direction", + "description": "

The ordering direction.

", + "type": "OrderDirection!", + "id": "orderdirection", + "kind": "enums", + "href": "/graphql/reference/enums#orderdirection" + }, + { + "name": "field", + "description": "

The field to order the project v2 views by.

", + "type": "ProjectV2ViewOrderField!", + "id": "projectv2vieworderfield", + "kind": "enums", + "href": "/graphql/reference/enums#projectv2vieworderfield" + } + ] + }, { "name": "PullRequestOrder", "kind": "inputObjects", @@ -72754,6 +77943,14 @@ "kind": "scalars", "href": "/graphql/reference/scalars#string" }, + { + "name": "lockSource", + "description": "

Whether to lock the source repository.

", + "type": "Boolean", + "id": "boolean", + "kind": "scalars", + "href": "/graphql/reference/scalars#boolean" + }, { "name": "metadataArchiveUrl", "description": "

The signed URL to access the user-uploaded metadata archive.

", @@ -72803,6 +78000,14 @@ "id": "uri", "kind": "scalars", "href": "/graphql/reference/scalars#uri" + }, + { + "name": "targetRepoVisibility", + "description": "

The visibility of the imported repository.

", + "type": "String", + "id": "string", + "kind": "scalars", + "href": "/graphql/reference/scalars#string" } ] }, @@ -72997,6 +78202,14 @@ "kind": "scalars", "href": "/graphql/reference/scalars#string" }, + { + "name": "createLabelsIfMissing", + "description": "

Whether to create labels if they don't exist in the target repository (matched by name).

", + "type": "Boolean", + "id": "boolean", + "kind": "scalars", + "href": "/graphql/reference/scalars#boolean" + }, { "name": "issueId", "description": "

The Node ID of the issue to be transferred.

", @@ -74779,6 +79992,40 @@ } ] }, + { + "name": "UpdateOrganizationWebCommitSignoffSettingInput", + "kind": "inputObjects", + "id": "updateorganizationwebcommitsignoffsettinginput", + "href": "/graphql/reference/input-objects#updateorganizationwebcommitsignoffsettinginput", + "description": "

Autogenerated input type of UpdateOrganizationWebCommitSignoffSetting.

", + "inputFields": [ + { + "name": "clientMutationId", + "description": "

A unique identifier for the client performing the mutation.

", + "type": "String", + "id": "string", + "kind": "scalars", + "href": "/graphql/reference/scalars#string" + }, + { + "name": "organizationId", + "description": "

The ID of the organization on which to set the web commit signoff setting.

", + "type": "ID!", + "id": "id", + "kind": "scalars", + "href": "/graphql/reference/scalars#id", + "isDeprecated": false + }, + { + "name": "webCommitSignoffRequired", + "description": "

Enable signoff on web-based commits for repositories in the organization?.

", + "type": "Boolean!", + "id": "boolean", + "kind": "scalars", + "href": "/graphql/reference/scalars#boolean" + } + ] + }, { "name": "UpdateProjectCardInput", "kind": "inputObjects", @@ -74913,6 +80160,219 @@ } ] }, + { + "name": "UpdateProjectV2DraftIssueInput", + "kind": "inputObjects", + "id": "updateprojectv2draftissueinput", + "href": "/graphql/reference/input-objects#updateprojectv2draftissueinput", + "description": "

Autogenerated input type of UpdateProjectV2DraftIssue.

", + "inputFields": [ + { + "name": "assigneeIds", + "description": "

The IDs of the assignees of the draft issue.

", + "type": "[ID!]", + "id": "id", + "kind": "scalars", + "href": "/graphql/reference/scalars#id", + "isDeprecated": false + }, + { + "name": "body", + "description": "

The body of the draft issue.

", + "type": "String", + "id": "string", + "kind": "scalars", + "href": "/graphql/reference/scalars#string" + }, + { + "name": "clientMutationId", + "description": "

A unique identifier for the client performing the mutation.

", + "type": "String", + "id": "string", + "kind": "scalars", + "href": "/graphql/reference/scalars#string" + }, + { + "name": "draftIssueId", + "description": "

The ID of the draft issue to update.

", + "type": "ID!", + "id": "id", + "kind": "scalars", + "href": "/graphql/reference/scalars#id", + "isDeprecated": false + }, + { + "name": "title", + "description": "

The title of the draft issue.

", + "type": "String", + "id": "string", + "kind": "scalars", + "href": "/graphql/reference/scalars#string" + } + ] + }, + { + "name": "UpdateProjectV2Input", + "kind": "inputObjects", + "id": "updateprojectv2input", + "href": "/graphql/reference/input-objects#updateprojectv2input", + "description": "

Autogenerated input type of UpdateProjectV2.

", + "inputFields": [ + { + "name": "clientMutationId", + "description": "

A unique identifier for the client performing the mutation.

", + "type": "String", + "id": "string", + "kind": "scalars", + "href": "/graphql/reference/scalars#string" + }, + { + "name": "closed", + "description": "

Set the project to closed or open.

", + "type": "Boolean", + "id": "boolean", + "kind": "scalars", + "href": "/graphql/reference/scalars#boolean" + }, + { + "name": "projectId", + "description": "

The ID of the Project to update.

", + "type": "ID!", + "id": "id", + "kind": "scalars", + "href": "/graphql/reference/scalars#id", + "isDeprecated": false + }, + { + "name": "public", + "description": "

Set the project to public or private.

", + "type": "Boolean", + "id": "boolean", + "kind": "scalars", + "href": "/graphql/reference/scalars#boolean" + }, + { + "name": "readme", + "description": "

Set the readme description of the project.

", + "type": "String", + "id": "string", + "kind": "scalars", + "href": "/graphql/reference/scalars#string" + }, + { + "name": "shortDescription", + "description": "

Set the short description of the project.

", + "type": "String", + "id": "string", + "kind": "scalars", + "href": "/graphql/reference/scalars#string" + }, + { + "name": "title", + "description": "

Set the title of the project.

", + "type": "String", + "id": "string", + "kind": "scalars", + "href": "/graphql/reference/scalars#string" + } + ] + }, + { + "name": "UpdateProjectV2ItemFieldValueInput", + "kind": "inputObjects", + "id": "updateprojectv2itemfieldvalueinput", + "href": "/graphql/reference/input-objects#updateprojectv2itemfieldvalueinput", + "description": "

Autogenerated input type of UpdateProjectV2ItemFieldValue.

", + "inputFields": [ + { + "name": "clientMutationId", + "description": "

A unique identifier for the client performing the mutation.

", + "type": "String", + "id": "string", + "kind": "scalars", + "href": "/graphql/reference/scalars#string" + }, + { + "name": "fieldId", + "description": "

The ID of the field to be updated.

", + "type": "ID!", + "id": "id", + "kind": "scalars", + "href": "/graphql/reference/scalars#id", + "isDeprecated": false + }, + { + "name": "itemId", + "description": "

The ID of the item to be updated.

", + "type": "ID!", + "id": "id", + "kind": "scalars", + "href": "/graphql/reference/scalars#id", + "isDeprecated": false + }, + { + "name": "projectId", + "description": "

The ID of the Project.

", + "type": "ID!", + "id": "id", + "kind": "scalars", + "href": "/graphql/reference/scalars#id", + "isDeprecated": false + }, + { + "name": "value", + "description": "

The value which will be set on the field.

", + "type": "ProjectV2FieldValue!", + "id": "projectv2fieldvalue", + "kind": "input-objects", + "href": "/graphql/reference/input-objects#projectv2fieldvalue" + } + ] + }, + { + "name": "UpdateProjectV2ItemPositionInput", + "kind": "inputObjects", + "id": "updateprojectv2itempositioninput", + "href": "/graphql/reference/input-objects#updateprojectv2itempositioninput", + "description": "

Autogenerated input type of UpdateProjectV2ItemPosition.

", + "inputFields": [ + { + "name": "afterId", + "description": "

The ID of the item to position this item after. If omitted or set to null the item will be moved to top.

", + "type": "ID", + "id": "id", + "kind": "scalars", + "href": "/graphql/reference/scalars#id", + "isDeprecated": false + }, + { + "name": "clientMutationId", + "description": "

A unique identifier for the client performing the mutation.

", + "type": "String", + "id": "string", + "kind": "scalars", + "href": "/graphql/reference/scalars#string" + }, + { + "name": "itemId", + "description": "

The ID of the item to be moved.

", + "type": "ID!", + "id": "id", + "kind": "scalars", + "href": "/graphql/reference/scalars#id", + "isDeprecated": false + }, + { + "name": "projectId", + "description": "

The ID of the Project.

", + "type": "ID!", + "id": "id", + "kind": "scalars", + "href": "/graphql/reference/scalars#id", + "isDeprecated": false + } + ] + }, { "name": "UpdatePullRequestBranchInput", "kind": "inputObjects", @@ -75290,6 +80750,40 @@ } ] }, + { + "name": "UpdateRepositoryWebCommitSignoffSettingInput", + "kind": "inputObjects", + "id": "updaterepositorywebcommitsignoffsettinginput", + "href": "/graphql/reference/input-objects#updaterepositorywebcommitsignoffsettinginput", + "description": "

Autogenerated input type of UpdateRepositoryWebCommitSignoffSetting.

", + "inputFields": [ + { + "name": "clientMutationId", + "description": "

A unique identifier for the client performing the mutation.

", + "type": "String", + "id": "string", + "kind": "scalars", + "href": "/graphql/reference/scalars#string" + }, + { + "name": "repositoryId", + "description": "

The ID of the repository to update.

", + "type": "ID!", + "id": "id", + "kind": "scalars", + "href": "/graphql/reference/scalars#id", + "isDeprecated": false + }, + { + "name": "webCommitSignoffRequired", + "description": "

Indicates if the repository should require signoff on web-based commits.

", + "type": "Boolean!", + "id": "boolean", + "kind": "scalars", + "href": "/graphql/reference/scalars#boolean" + } + ] + }, { "name": "UpdateSubscriptionInput", "kind": "inputObjects", @@ -75662,6 +81156,31 @@ "isDeprecated": false } ] + }, + { + "name": "WorkflowRunOrder", + "kind": "inputObjects", + "id": "workflowrunorder", + "href": "/graphql/reference/input-objects#workflowrunorder", + "description": "

Ways in which lists of workflow runs can be ordered upon return.

", + "inputFields": [ + { + "name": "direction", + "description": "

The direction in which to order workflow runs by the specified field.

", + "type": "OrderDirection!", + "id": "orderdirection", + "kind": "enums", + "href": "/graphql/reference/enums#orderdirection" + }, + { + "name": "field", + "description": "

The field by which to order workflows.

", + "type": "WorkflowRunOrderField!", + "id": "workflowrunorderfield", + "kind": "enums", + "href": "/graphql/reference/enums#workflowrunorderfield" + } + ] } ], "scalars": [ diff --git a/lib/graphql/static/upcoming-changes.json b/lib/graphql/static/upcoming-changes.json index a77d4ad587..c1dabb358d 100644 --- a/lib/graphql/static/upcoming-changes.json +++ b/lib/graphql/static/upcoming-changes.json @@ -747,6 +747,14 @@ "criticality": "breaking", "owner": "lukewar" }, + { + "location": "ProjectNextFieldType.TRACKED_BY", + "description": "

TRACKED_BY will be removed. Follow the ProjectV2 guide at https://github.blog/changelog/2022-06-23-the-new-github-issues-june-23rd-update/, to find a suitable replacement.

", + "reason": "

The ProjectNext API is deprecated in favour of the more capable ProjectV2 API.

", + "date": "2023-01-01", + "criticality": "breaking", + "owner": "lukewar" + }, { "location": "ProjectNextFieldType.TITLE", "description": "

TITLE will be removed. Follow the ProjectV2 guide at https://github.blog/changelog/2022-06-23-the-new-github-issues-june-23rd-update/, to find a suitable replacement.

", @@ -2205,6 +2213,14 @@ "criticality": "breaking", "owner": "lukewar" }, + { + "location": "ProjectNextFieldType.TRACKED_BY", + "description": "

TRACKED_BY will be removed. Follow the ProjectV2 guide at https://github.blog/changelog/2022-06-23-the-new-github-issues-june-23rd-update/, to find a suitable replacement.

", + "reason": "

The ProjectNext API is deprecated in favour of the more capable ProjectV2 API.

", + "date": "2023-01-01", + "criticality": "breaking", + "owner": "lukewar" + }, { "location": "ProjectNextFieldType.TITLE", "description": "

TITLE will be removed. Follow the ProjectV2 guide at https://github.blog/changelog/2022-06-23-the-new-github-issues-june-23rd-update/, to find a suitable replacement.

", @@ -2915,6 +2931,250 @@ } ] }, + "ghes-3.7": { + "2022-10-01": [ + { + "location": "UnlockAndResetMergeGroupInput.branch", + "description": "

branch will be removed.

", + "reason": "

The current merge group for the repository's default branch, the branch argument is now a no-op

", + "date": "2022-10-01", + "criticality": "breaking", + "owner": "jhunschejones" + }, + { + "location": "RepositoryVulnerabilityAlert.fixReason", + "description": "

fixReason will be removed.

", + "reason": "

The fixReason field is being removed. You can still use fixedAt and dismissReason.

", + "date": "2022-10-01", + "criticality": "breaking", + "owner": "jamestran201" + }, + { + "location": "RemovePullRequestFromMergeQueueInput.branch", + "description": "

branch will be removed.

", + "reason": "

PRs are removed from the merge queue for the base branch, the branch argument is now a no-op

", + "date": "2022-10-01", + "criticality": "breaking", + "owner": "jhunschejones" + }, + { + "location": "ProjectNextFieldType.TRACKS", + "description": "

TRACKS will be removed. Follow the ProjectV2 guide at https://github.blog/changelog/2022-06-23-the-new-github-issues-june-23rd-update/, to find a suitable replacement.

", + "reason": "

The ProjectNext API is deprecated in favour of the more capable ProjectV2 API.

", + "date": "2022-10-01", + "criticality": "breaking", + "owner": "lukewar" + }, + { + "location": "ProjectNextFieldType.TITLE", + "description": "

TITLE will be removed. Follow the ProjectV2 guide at https://github.blog/changelog/2022-06-23-the-new-github-issues-june-23rd-update/, to find a suitable replacement.

", + "reason": "

The ProjectNext API is deprecated in favour of the more capable ProjectV2 API.

", + "date": "2022-10-01", + "criticality": "breaking", + "owner": "lukewar" + }, + { + "location": "ProjectNextFieldType.TEXT", + "description": "

TEXT will be removed. Follow the ProjectV2 guide at https://github.blog/changelog/2022-06-23-the-new-github-issues-june-23rd-update/, to find a suitable replacement.

", + "reason": "

The ProjectNext API is deprecated in favour of the more capable ProjectV2 API.

", + "date": "2022-10-01", + "criticality": "breaking", + "owner": "lukewar" + }, + { + "location": "ProjectNextFieldType.SINGLE_SELECT", + "description": "

SINGLE_SELECT will be removed. Follow the ProjectV2 guide at https://github.blog/changelog/2022-06-23-the-new-github-issues-june-23rd-update/, to find a suitable replacement.

", + "reason": "

The ProjectNext API is deprecated in favour of the more capable ProjectV2 API.

", + "date": "2022-10-01", + "criticality": "breaking", + "owner": "lukewar" + }, + { + "location": "ProjectNextFieldType.REVIEWERS", + "description": "

REVIEWERS will be removed. Follow the ProjectV2 guide at https://github.blog/changelog/2022-06-23-the-new-github-issues-june-23rd-update/, to find a suitable replacement.

", + "reason": "

The ProjectNext API is deprecated in favour of the more capable ProjectV2 API.

", + "date": "2022-10-01", + "criticality": "breaking", + "owner": "lukewar" + }, + { + "location": "ProjectNextFieldType.REPOSITORY", + "description": "

REPOSITORY will be removed. Follow the ProjectV2 guide at https://github.blog/changelog/2022-06-23-the-new-github-issues-june-23rd-update/, to find a suitable replacement.

", + "reason": "

The ProjectNext API is deprecated in favour of the more capable ProjectV2 API.

", + "date": "2022-10-01", + "criticality": "breaking", + "owner": "lukewar" + }, + { + "location": "ProjectNextFieldType.NUMBER", + "description": "

NUMBER will be removed. Follow the ProjectV2 guide at https://github.blog/changelog/2022-06-23-the-new-github-issues-june-23rd-update/, to find a suitable replacement.

", + "reason": "

The ProjectNext API is deprecated in favour of the more capable ProjectV2 API.

", + "date": "2022-10-01", + "criticality": "breaking", + "owner": "lukewar" + }, + { + "location": "ProjectNextFieldType.MILESTONE", + "description": "

MILESTONE will be removed. Follow the ProjectV2 guide at https://github.blog/changelog/2022-06-23-the-new-github-issues-june-23rd-update/, to find a suitable replacement.

", + "reason": "

The ProjectNext API is deprecated in favour of the more capable ProjectV2 API.

", + "date": "2022-10-01", + "criticality": "breaking", + "owner": "lukewar" + }, + { + "location": "ProjectNextFieldType.LINKED_PULL_REQUESTS", + "description": "

LINKED_PULL_REQUESTS will be removed. Follow the ProjectV2 guide at https://github.blog/changelog/2022-06-23-the-new-github-issues-june-23rd-update/, to find a suitable replacement.

", + "reason": "

The ProjectNext API is deprecated in favour of the more capable ProjectV2 API.

", + "date": "2022-10-01", + "criticality": "breaking", + "owner": "lukewar" + }, + { + "location": "ProjectNextFieldType.LABELS", + "description": "

LABELS will be removed. Follow the ProjectV2 guide at https://github.blog/changelog/2022-06-23-the-new-github-issues-june-23rd-update/, to find a suitable replacement.

", + "reason": "

The ProjectNext API is deprecated in favour of the more capable ProjectV2 API.

", + "date": "2022-10-01", + "criticality": "breaking", + "owner": "lukewar" + }, + { + "location": "ProjectNextFieldType.ITERATION", + "description": "

ITERATION will be removed. Follow the ProjectV2 guide at https://github.blog/changelog/2022-06-23-the-new-github-issues-june-23rd-update/, to find a suitable replacement.

", + "reason": "

The ProjectNext API is deprecated in favour of the more capable ProjectV2 API.

", + "date": "2022-10-01", + "criticality": "breaking", + "owner": "lukewar" + }, + { + "location": "ProjectNextFieldType.DATE", + "description": "

DATE will be removed. Follow the ProjectV2 guide at https://github.blog/changelog/2022-06-23-the-new-github-issues-june-23rd-update/, to find a suitable replacement.

", + "reason": "

The ProjectNext API is deprecated in favour of the more capable ProjectV2 API.

", + "date": "2022-10-01", + "criticality": "breaking", + "owner": "lukewar" + }, + { + "location": "ProjectNextFieldType.ASSIGNEES", + "description": "

ASSIGNEES will be removed. Follow the ProjectV2 guide at https://github.blog/changelog/2022-06-23-the-new-github-issues-june-23rd-update/, to find a suitable replacement.

", + "reason": "

The ProjectNext API is deprecated in favour of the more capable ProjectV2 API.

", + "date": "2022-10-01", + "criticality": "breaking", + "owner": "lukewar" + }, + { + "location": "MergeLockedMergeGroupInput.branch", + "description": "

branch will be removed.

", + "reason": "

Changes are merged into the repository's default branch, the branch argument is now a no-op

", + "date": "2022-10-01", + "criticality": "breaking", + "owner": "jhunschejones" + }, + { + "location": "LockMergeQueueInput.branch", + "description": "

branch will be removed.

", + "reason": "

The merge queue is locked for the repository's default branch, the branch argument is now a no-op

", + "date": "2022-10-01", + "criticality": "breaking", + "owner": "jhunschejones" + } + ], + "2022-07-01": [ + { + "location": "AddPullRequestToMergeQueueInput.branch", + "description": "

branch will be removed.

", + "reason": "

PRs are added to the merge queue for the base branch, the branch argument is now a no-op

", + "date": "2022-07-01", + "criticality": "breaking", + "owner": "jhunschejones" + } + ], + "2022-04-01": [ + { + "location": "Repository.defaultMergeQueue", + "description": "

defaultMergeQueue will be removed. Use Repository.mergeQueue instead.

", + "reason": "

defaultMergeQueue will be removed.

", + "date": "2022-04-01", + "criticality": "breaking", + "owner": "colinshum" + } + ], + "2021-10-01": [ + { + "location": "ReactionGroup.users", + "description": "

users will be removed. Use the reactors field instead.

", + "reason": "

Reactors can now be mannequins, bots, and organizations.

", + "date": "2021-10-01", + "criticality": "breaking", + "owner": "synthead" + } + ], + "2021-06-21": [ + { + "location": "PackageType.DOCKER", + "description": "

DOCKER will be removed.

", + "reason": "

DOCKER will be removed from this enum as this type will be migrated to only be used by the Packages REST API.

", + "date": "2021-06-21", + "criticality": "breaking", + "owner": "reybard" + } + ], + "2021-01-01": [ + { + "location": "MergeStateStatus.DRAFT", + "description": "

DRAFT will be removed. Use PullRequest.isDraft instead.

", + "reason": "

DRAFT state will be removed from this enum and isDraft should be used instead

", + "date": "2021-01-01", + "criticality": "breaking", + "owner": "nplasterer" + } + ], + "2020-10-01": [ + { + "location": "PullRequest.timeline", + "description": "

timeline will be removed. Use PullRequest.timelineItems instead.

", + "reason": "

timeline will be removed

", + "date": "2020-10-01", + "criticality": "breaking", + "owner": "mikesea" + }, + { + "location": "Issue.timeline", + "description": "

timeline will be removed. Use Issue.timelineItems instead.

", + "reason": "

timeline will be removed

", + "date": "2020-10-01", + "criticality": "breaking", + "owner": "mikesea" + } + ], + "2020-01-01": [ + { + "location": "UnassignedEvent.user", + "description": "

user will be removed. Use the assignee field instead.

", + "reason": "

Assignees can now be mannequins.

", + "date": "2020-01-01", + "criticality": "breaking", + "owner": "tambling" + }, + { + "location": "AssignedEvent.user", + "description": "

user will be removed. Use the assignee field instead.

", + "reason": "

Assignees can now be mannequins.

", + "date": "2020-01-01", + "criticality": "breaking", + "owner": "tambling" + } + ], + "2019-04-01": [ + { + "location": "LegacyMigration.uploadUrlTemplate", + "description": "

uploadUrlTemplate will be removed. Use uploadUrl instead.

", + "reason": "

uploadUrlTemplate is being removed because it is not a standard URL and adds an extra user step.

", + "date": "2019-04-01", + "criticality": "breaking", + "owner": "tambling" + } + ] + }, "ghes-3.6": { "2022-10-01": [ { @@ -3467,168 +3727,6 @@ } ] }, - "ghes-3.2": { - "2021-10-01": [ - { - "location": "ReactionGroup.users", - "description": "

users will be removed. Use the reactors field instead.

", - "reason": "

Reactors can now be mannequins, bots, and organizations.

", - "date": "2021-10-01", - "criticality": "breaking", - "owner": "synthead" - } - ], - "2021-06-21": [ - { - "location": "PackageType.DOCKER", - "description": "

DOCKER will be removed.

", - "reason": "

DOCKER will be removed from this enum as this type will be migrated to only be used by the Packages REST API.

", - "date": "2021-06-21", - "criticality": "breaking", - "owner": "reybard" - } - ], - "2021-01-01": [ - { - "location": "MergeStateStatus.DRAFT", - "description": "

DRAFT will be removed. Use PullRequest.isDraft instead.

", - "reason": "

DRAFT state will be removed from this enum and isDraft should be used instead

", - "date": "2021-01-01", - "criticality": "breaking", - "owner": "nplasterer" - }, - { - "location": "EnterprisePendingCollaboratorEdge.isUnlicensed", - "description": "

isUnlicensed will be removed.

", - "reason": "

All pending collaborators consume a license

", - "date": "2021-01-01", - "criticality": "breaking", - "owner": "BrentWheeldon" - }, - { - "location": "EnterpriseOutsideCollaboratorEdge.isUnlicensed", - "description": "

isUnlicensed will be removed.

", - "reason": "

All outside collaborators consume a license

", - "date": "2021-01-01", - "criticality": "breaking", - "owner": "BrentWheeldon" - }, - { - "location": "EnterpriseMemberEdge.isUnlicensed", - "description": "

isUnlicensed will be removed.

", - "reason": "

All members consume a license

", - "date": "2021-01-01", - "criticality": "breaking", - "owner": "BrentWheeldon" - } - ], - "2020-10-01": [ - { - "location": "Sponsorship.sponsor", - "description": "

sponsor will be removed. Use Sponsorship.sponsorEntity instead.

", - "reason": "

Sponsorship.sponsor will be removed.

", - "date": "2020-10-01", - "criticality": "breaking", - "owner": "nholden" - }, - { - "location": "RepositoryInvitationOrderField.INVITEE_LOGIN", - "description": "

INVITEE_LOGIN will be removed.

", - "reason": "

INVITEE_LOGIN is no longer a valid field value. Repository invitations can now be associated with an email, not only an invitee.

", - "date": "2020-10-01", - "criticality": "breaking", - "owner": "jdennes" - }, - { - "location": "PullRequest.timeline", - "description": "

timeline will be removed. Use PullRequest.timelineItems instead.

", - "reason": "

timeline will be removed

", - "date": "2020-10-01", - "criticality": "breaking", - "owner": "mikesea" - }, - { - "location": "Issue.timeline", - "description": "

timeline will be removed. Use Issue.timelineItems instead.

", - "reason": "

timeline will be removed

", - "date": "2020-10-01", - "criticality": "breaking", - "owner": "mikesea" - }, - { - "location": "EnterpriseOwnerInfo.pendingCollaborators", - "description": "

pendingCollaborators will be removed. Use the pendingCollaboratorInvitations field instead.

", - "reason": "

Repository invitations can now be associated with an email, not only an invitee.

", - "date": "2020-10-01", - "criticality": "breaking", - "owner": "jdennes" - } - ], - "2020-07-01": [ - { - "location": "EnterprisePendingMemberInvitationEdge.isUnlicensed", - "description": "

isUnlicensed will be removed.

", - "reason": "

All pending members consume a license

", - "date": "2020-07-01", - "criticality": "breaking", - "owner": "BrentWheeldon" - } - ], - "2020-04-01": [ - { - "location": "Sponsorship.maintainer", - "description": "

maintainer will be removed. Use Sponsorship.sponsorable instead.

", - "reason": "

Sponsorship.maintainer will be removed.

", - "date": "2020-04-01", - "criticality": "breaking", - "owner": "antn" - } - ], - "2020-01-01": [ - { - "location": "UnassignedEvent.user", - "description": "

user will be removed. Use the assignee field instead.

", - "reason": "

Assignees can now be mannequins.

", - "date": "2020-01-01", - "criticality": "breaking", - "owner": "tambling" - }, - { - "location": "EnterpriseBillingInfo.seats", - "description": "

seats will be removed. Use EnterpriseBillingInfo.totalLicenses instead.

", - "reason": "

seats will be replaced with totalLicenses to provide more clarity on the value being returned

", - "date": "2020-01-01", - "criticality": "breaking", - "owner": "BlakeWilliams" - }, - { - "location": "EnterpriseBillingInfo.availableSeats", - "description": "

availableSeats will be removed. Use EnterpriseBillingInfo.totalAvailableLicenses instead.

", - "reason": "

availableSeats will be replaced with totalAvailableLicenses to provide more clarity on the value being returned

", - "date": "2020-01-01", - "criticality": "breaking", - "owner": "BlakeWilliams" - }, - { - "location": "AssignedEvent.user", - "description": "

user will be removed. Use the assignee field instead.

", - "reason": "

Assignees can now be mannequins.

", - "date": "2020-01-01", - "criticality": "breaking", - "owner": "tambling" - } - ], - "2019-04-01": [ - { - "location": "LegacyMigration.uploadUrlTemplate", - "description": "

uploadUrlTemplate will be removed. Use uploadUrl instead.

", - "reason": "

uploadUrlTemplate is being removed because it is not a standard URL and adds an extra user step.

", - "date": "2019-04-01", - "criticality": "breaking", - "owner": "tambling" - } - ] - }, "ghae": { "2023-04-01": [ { @@ -3673,6 +3771,14 @@ "criticality": "breaking", "owner": "lukewar" }, + { + "location": "ProjectNextFieldType.TRACKED_BY", + "description": "

TRACKED_BY will be removed. Follow the ProjectV2 guide at https://github.blog/changelog/2022-06-23-the-new-github-issues-june-23rd-update/, to find a suitable replacement.

", + "reason": "

The ProjectNext API is deprecated in favour of the more capable ProjectV2 API.

", + "date": "2023-01-01", + "criticality": "breaking", + "owner": "lukewar" + }, { "location": "ProjectNextFieldType.TITLE", "description": "

TITLE will be removed. Follow the ProjectV2 guide at https://github.blog/changelog/2022-06-23-the-new-github-issues-june-23rd-update/, to find a suitable replacement.

", @@ -3892,121 +3998,5 @@ "owner": "tambling" } ] - }, - "ghes-3.7": { - "2022-10-01": [ - { - "location": "RemovePullRequestFromMergeQueueInput.branch", - "description": "

branch will be removed.

", - "reason": "

PRs are removed from the merge queue for the base branch, the branch argument is now a no-op

", - "date": "2022-10-01", - "criticality": "breaking", - "owner": "jhunschejones" - } - ], - "2022-07-01": [ - { - "location": "Enterprise.userAccounts", - "description": "

userAccounts will be removed. Use the Enterprise.members field instead.

", - "reason": "

The Enterprise.userAccounts field is being removed.

", - "date": "2022-07-01", - "criticality": "breaking", - "owner": "jdennes" - }, - { - "location": "AddPullRequestToMergeQueueInput.branch", - "description": "

branch will be removed.

", - "reason": "

PRs are added to the merge queue for the base branch, the branch argument is now a no-op

", - "date": "2022-07-01", - "criticality": "breaking", - "owner": "jhunschejones" - } - ], - "2022-04-01": [ - { - "location": "Repository.defaultMergeQueue", - "description": "

defaultMergeQueue will be removed. Use Repository.mergeQueue instead.

", - "reason": "

defaultMergeQueue will be removed.

", - "date": "2022-04-01", - "criticality": "breaking", - "owner": "colinshum" - } - ], - "2021-10-01": [ - { - "location": "ReactionGroup.users", - "description": "

users will be removed. Use the reactors field instead.

", - "reason": "

Reactors can now be mannequins, bots, and organizations.

", - "date": "2021-10-01", - "criticality": "breaking", - "owner": "synthead" - } - ], - "2021-06-21": [ - { - "location": "PackageType.DOCKER", - "description": "

DOCKER will be removed.

", - "reason": "

DOCKER will be removed from this enum as this type will be migrated to only be used by the Packages REST API.

", - "date": "2021-06-21", - "criticality": "breaking", - "owner": "reybard" - } - ], - "2021-01-01": [ - { - "location": "MergeStateStatus.DRAFT", - "description": "

DRAFT will be removed. Use PullRequest.isDraft instead.

", - "reason": "

DRAFT state will be removed from this enum and isDraft should be used instead

", - "date": "2021-01-01", - "criticality": "breaking", - "owner": "nplasterer" - } - ], - "2020-10-01": [ - { - "location": "PullRequest.timeline", - "description": "

timeline will be removed. Use PullRequest.timelineItems instead.

", - "reason": "

timeline will be removed

", - "date": "2020-10-01", - "criticality": "breaking", - "owner": "mikesea" - }, - { - "location": "Issue.timeline", - "description": "

timeline will be removed. Use Issue.timelineItems instead.

", - "reason": "

timeline will be removed

", - "date": "2020-10-01", - "criticality": "breaking", - "owner": "mikesea" - } - ], - "2020-01-01": [ - { - "location": "UnassignedEvent.user", - "description": "

user will be removed. Use the assignee field instead.

", - "reason": "

Assignees can now be mannequins.

", - "date": "2020-01-01", - "criticality": "breaking", - "owner": "tambling" - }, - { - "location": "AssignedEvent.user", - "description": "

user will be removed. Use the assignee field instead.

", - "reason": "

Assignees can now be mannequins.

", - "date": "2020-01-01", - "criticality": "breaking", - "owner": "tambling" - } - ], - "2019-04-01": [ - { - "location": "LegacyMigration.uploadUrlTemplate", - "description": "

uploadUrlTemplate will be removed. Use uploadUrl instead.

", - "reason": "

uploadUrlTemplate is being removed because it is not a standard URL and adds an extra user step.

", - "date": "2019-04-01", - "criticality": "breaking", - "owner": "tambling" - } - ] } } \ No newline at end of file diff --git a/package-lock.json b/package-lock.json index def7128827..f5798e3c2b 100644 --- a/package-lock.json +++ b/package-lock.json @@ -57,7 +57,7 @@ "morgan": "^1.10.0", "msgpack5rpc": "^1.1.0", "next": "12.2.4", - "parse5": "7.0.0", + "parse5": "7.1.1", "port-used": "^2.0.8", "react": "^17.0.2", "react-dom": "^17.0.2", @@ -16109,10 +16109,11 @@ } }, "node_modules/parse5": { - "version": "7.0.0", - "license": "MIT", + "version": "7.1.1", + "resolved": "https://registry.npmjs.org/parse5/-/parse5-7.1.1.tgz", + "integrity": "sha512-kwpuwzB+px5WUg9pyK0IcK/shltJN5/OVhQagxhCQNtT9Y9QRZqNY2e1cmbu/paRh5LMnz/oVTVLBpjFmMZhSg==", "dependencies": { - "entities": "^4.3.0" + "entities": "^4.4.0" }, "funding": { "url": "https://github.com/inikulin/parse5?sponsor=1" @@ -16131,8 +16132,9 @@ } }, "node_modules/parse5/node_modules/entities": { - "version": "4.3.0", - "license": "BSD-2-Clause", + "version": "4.4.0", + "resolved": "https://registry.npmjs.org/entities/-/entities-4.4.0.tgz", + "integrity": "sha512-oYp7156SP8LkeGD0GF85ad1X9Ai79WtRsZ2gxJqtBuzH+98YUV6jkHEKlZkMbcrjJjIVJNIDP/3WL9wQkoPbWA==", "engines": { "node": ">=0.12" }, @@ -32016,13 +32018,17 @@ "devOptional": true }, "parse5": { - "version": "7.0.0", + "version": "7.1.1", + "resolved": "https://registry.npmjs.org/parse5/-/parse5-7.1.1.tgz", + "integrity": "sha512-kwpuwzB+px5WUg9pyK0IcK/shltJN5/OVhQagxhCQNtT9Y9QRZqNY2e1cmbu/paRh5LMnz/oVTVLBpjFmMZhSg==", "requires": { - "entities": "^4.3.0" + "entities": "^4.4.0" }, "dependencies": { "entities": { - "version": "4.3.0" + "version": "4.4.0", + "resolved": "https://registry.npmjs.org/entities/-/entities-4.4.0.tgz", + "integrity": "sha512-oYp7156SP8LkeGD0GF85ad1X9Ai79WtRsZ2gxJqtBuzH+98YUV6jkHEKlZkMbcrjJjIVJNIDP/3WL9wQkoPbWA==" } } }, diff --git a/package.json b/package.json index aae6ec5c74..9034682438 100644 --- a/package.json +++ b/package.json @@ -59,7 +59,7 @@ "morgan": "^1.10.0", "msgpack5rpc": "^1.1.0", "next": "12.2.4", - "parse5": "7.0.0", + "parse5": "7.1.1", "port-used": "^2.0.8", "react": "^17.0.2", "react-dom": "^17.0.2", diff --git a/stylesheets/extended-markdown.scss b/stylesheets/extended-markdown.scss index ece27f2679..056c09608d 100644 --- a/stylesheets/extended-markdown.scss +++ b/stylesheets/extended-markdown.scss @@ -16,6 +16,7 @@ &.note pre code { color: var(--color-fg-default); + margin: 1rem; } &.note pre { @@ -28,8 +29,8 @@ &.warning, &.tip, &.danger { - p { - margin: 0; + p:last-child { + margin-bottom: 0; } } } diff --git a/translations/es-ES/content/authentication/connecting-to-github-with-ssh/about-ssh.md b/translations/es-ES/content/authentication/connecting-to-github-with-ssh/about-ssh.md index 294dc0dd7d..6364a1d251 100644 --- a/translations/es-ES/content/authentication/connecting-to-github-with-ssh/about-ssh.md +++ b/translations/es-ES/content/authentication/connecting-to-github-with-ssh/about-ssh.md @@ -1,6 +1,6 @@ --- -title: About SSH -intro: 'Using the SSH protocol, you can connect and authenticate to remote servers and services. With SSH keys, you can connect to {% data variables.product.product_name %} without supplying your username and {% data variables.product.pat_generic %} at each visit.{% ifversion ssh-commit-verification %} You can also use an SSH key to sign commits.{% endif %}' +title: Acerca de SSH +intro: 'Usando el protocolo SSH, te puedes conectar y autenticar con servicios y servidores remotos. Con las claves SSH puedes conectarte a {% data variables.product.product_name %} sin necesidad de proporcionar el nombre de usuario y el {% data variables.product.pat_generic %} en cada visita.{% ifversion ssh-commit-verification %} También puedes usar una clave SSH para firmar confirmaciones.{% endif %}' redirect_from: - /articles/about-ssh - /github/authenticating-to-github/about-ssh @@ -12,27 +12,29 @@ versions: ghec: '*' topics: - SSH +ms.openlocfilehash: 51a72821217e5d47092ed77e923b38f4cf248010 +ms.sourcegitcommit: a0ad3bfe2a99c3092e76ca9b3d476cf30988ca55 +ms.translationtype: HT +ms.contentlocale: es-ES +ms.lasthandoff: 10/28/2022 +ms.locfileid: '148118983' --- +{% data reusables.ssh.about-ssh %} Para obtener más información sobre SSH, consulta [Secure Shell](https://en.wikipedia.org/wiki/Secure_Shell) en Wikipedia. -{% data reusables.ssh.about-ssh %} For more information about SSH, see [Secure Shell](https://en.wikipedia.org/wiki/Secure_Shell) on Wikipedia. +Cuando configures SSH, necesitarás generar una clave SSH privada nueva y agregarla al agente SSH. También debes agregar la clave SSH pública a tu cuenta en {% data variables.product.product_name %} antes de utilizarla para autenticarte{% ifversion ssh-commit-verification %} o firmar confirmaciones{% endif %}. Para obtener más información, consulta "[Generación de una nueva clave SSH e incorporación al agente ssh](/authentication/connecting-to-github-with-ssh/generating-a-new-ssh-key-and-adding-it-to-the-ssh-agent)"{% ifversion ssh-commit-verification %}, {% else %} e{% endif %} "[Incorporación de una nueva clave SSH a la cuenta de {% data variables.product.prodname_dotcom %}](/authentication/connecting-to-github-with-ssh/adding-a-new-ssh-key-to-your-github-account){% ifversion ssh-commit-verification %}" y "[Acerca de la verificación de firma de confirmación](/articles/about-commit-signature-verification){% endif %}". -When you set up SSH, you will need to generate a new private SSH key and add it to the SSH agent. You must also add the public SSH key to your account on {% data variables.product.product_name %} before you use the key to authenticate{% ifversion ssh-commit-verification %} or sign commits{% endif %}. For more information, see "[Generating a new SSH key and adding it to the ssh-agent](/authentication/connecting-to-github-with-ssh/generating-a-new-ssh-key-and-adding-it-to-the-ssh-agent)"{% ifversion ssh-commit-verification %}, {% else %} and{% endif %} "[Adding a new SSH key to your {% data variables.product.prodname_dotcom %} account](/authentication/connecting-to-github-with-ssh/adding-a-new-ssh-key-to-your-github-account){% ifversion ssh-commit-verification %}" and "[About commit signature verification](/articles/about-commit-signature-verification){% endif %}." +Puedes asegurar tu llave SSH aún más si utilizas una llave de seguridad de hardware, la cual requiere que esta última se conecte físicamente a tu computadora cuando se utilice el par de llaves para autenticarte con SSH. También puedes asegurar tu llave SSH si la agregas al ssh-agent y utiliza una contraseña. Para obtener más información, consulta "[Trabajo con frases de contraseña de clave de SSH](/authentication/connecting-to-github-with-ssh/working-with-ssh-key-passphrases)". -You can further secure your SSH key by using a hardware security key, which requires the physical hardware security key to be attached to your computer when the key pair is used to authenticate with SSH. You can also secure your SSH key by adding your key to the ssh-agent and using a passphrase. For more information, see "[Working with SSH key passphrases](/authentication/connecting-to-github-with-ssh/working-with-ssh-key-passphrases)." +{% ifversion fpt or ghec %}Para usar la clave SSH con un repositorio propiedad de una organización que usa el inicio de sesión único de SAML, debes autorizar la clave. Para obtener más información, consulta "[Autorización de una clave SSH para usarla con el inicio de sesión único de SAML](/enterprise-cloud@latest/authentication/authenticating-with-saml-single-sign-on/authorizing-an-ssh-key-for-use-with-saml-single-sign-on){% ifversion fpt %}" en la documentación de {% data variables.product.prodname_ghe_cloud %}.{% else %}".{% endif %}{% endif %} -{% ifversion fpt or ghec %}To use your SSH key with a repository owned by an organization that uses SAML single sign-on, you must authorize the key. For more information, see "[Authorizing an SSH key for use with SAML single sign-on](/enterprise-cloud@latest/authentication/authenticating-with-saml-single-sign-on/authorizing-an-ssh-key-for-use-with-saml-single-sign-on){% ifversion fpt %}" in the {% data variables.product.prodname_ghe_cloud %} documentation.{% else %}."{% endif %}{% endif %} +Para mantener la seguridad de cuenta, puedes revisar tu lista de llaves SSH frecuentemente y retirar cualquier llave que sea inválida o que se haya puesto en riesgo. Para obtener más información, consulta "[Revisión de las claves SSH](/github/authenticating-to-github/reviewing-your-ssh-keys)". -To maintain account security, you can regularly review your SSH keys list and revoke any keys that are invalid or have been compromised. For more information, see "[Reviewing your SSH keys](/github/authenticating-to-github/reviewing-your-ssh-keys)." - -{% ifversion fpt or ghec %} -If you haven't used your SSH key for a year, then {% data variables.product.prodname_dotcom %} will automatically delete your inactive SSH key as a security precaution. For more information, see "[Deleted or missing SSH keys](/articles/deleted-or-missing-ssh-keys)." +{% ifversion fpt or ghec %} Si no has usado tu clave SSH por un año, entonces {% data variables.product.prodname_dotcom %} automáticamente eliminará tu clave SSH inactiva, como medida de seguridad. Para obtener más información, consulta "[Claves SSH eliminadas o ausentes](/articles/deleted-or-missing-ssh-keys)". {% endif %} -{% ifversion fpt %} -Organizations that use {% data variables.product.prodname_ghe_cloud %} can provide SSH certificates, which members can use to access that organization's repositories without adding the certificate to their account on {% data variables.product.product_name %}. If you're using an SSH certificate, you cannot use the certificate to access forks of the organization's repositories, if the fork is owned by your personal account. For more information, see "[About SSH certificate authorities](/enterprise-cloud@latest/organizations/managing-git-access-to-your-organizations-repositories/about-ssh-certificate-authorities)" in the {% data variables.product.prodname_ghe_cloud %} documentation. -{% else ghec or ghes or ghae %} -If you're a member of an organization that provides SSH certificates, you can use your certificate to access that organization's repositories without adding the certificate to your account on {% data variables.product.product_name %}. You cannot use your certificate to access forks of the organization's repositories, if the forks is owned by your personal account. For more information, see "[About SSH certificate authorities](/organizations/managing-git-access-to-your-organizations-repositories/about-ssh-certificate-authorities)." +{% ifversion fpt %} Las organizaciones que usan {% data variables.product.prodname_ghe_cloud %} pueden proporcionar certificados SSH, que los miembros pueden usar para acceder a los repositorios de estas sin tener que agregar el certificado a su cuenta de {% data variables.product.product_name %}. Si usas un certificado SSH, no puedes acceder con él a bifurcaciones de los repositorios de la organización, si la bifurcación es propiedad de tu cuenta personal. Para más información, consulta "[Acerca de las entidades de certificación de SSH](/enterprise-cloud@latest/organizations/managing-git-access-to-your-organizations-repositories/about-ssh-certificate-authorities) en la documentación de {% data variables.product.prodname_ghe_cloud %}. +{% else ghec or ghes or ghae %} Si eres miembro de una organización que proporciona certificados SSH, puedes usar tu certificado para acceder a los repositorios de esa organización sin agregar el certificado a tu cuenta de {% data variables.product.product_name %}. No puedes utilizar tu certificado para acceder a bifurcaciones de los repositorios de la organización, si estas pertenecen a tu cuenta personal. Para más información, vea "[Acerca de las entidades de certificación de SSH](/organizations/managing-git-access-to-your-organizations-repositories/about-ssh-certificate-authorities)". {% endif %} -## Further reading +## Información adicional -- "[Troubleshooting SSH](/articles/troubleshooting-ssh)" +- "[Solucionar problemas de SSH](/articles/troubleshooting-ssh)" diff --git a/translations/es-ES/content/authentication/managing-commit-signature-verification/telling-git-about-your-signing-key.md b/translations/es-ES/content/authentication/managing-commit-signature-verification/telling-git-about-your-signing-key.md index 1b1c1fbd9f..55d6721afd 100644 --- a/translations/es-ES/content/authentication/managing-commit-signature-verification/telling-git-about-your-signing-key.md +++ b/translations/es-ES/content/authentication/managing-commit-signature-verification/telling-git-about-your-signing-key.md @@ -1,6 +1,6 @@ --- -title: Telling Git about your signing key -intro: 'To sign commits locally, you need to inform Git that there''s a GPG{% ifversion ssh-commit-verification %}, SSH,{% endif %} or X.509 key you''d like to use.' +title: Informarle a Git acerca de tu clave de firma +intro: 'Para firmar las confirmaciones localmente, necesitas informar a Git que hay una clave de GPG{% ifversion ssh-commit-verification %}, SSH,{% endif %} o X.509 que quieres utilizar.' redirect_from: - /articles/telling-git-about-your-gpg-key - /articles/telling-git-about-your-signing-key @@ -15,38 +15,39 @@ topics: - Identity - Access management shortTitle: Tell Git your signing key +ms.openlocfilehash: e78306bb1519f2b7f51ab6bc039bff0b982e48cf +ms.sourcegitcommit: a0ad3bfe2a99c3092e76ca9b3d476cf30988ca55 +ms.translationtype: HT +ms.contentlocale: es-ES +ms.lasthandoff: 10/28/2022 +ms.locfileid: '148118999' --- {% mac %} -## Telling Git about your GPG key +## Informarle a Git acerca de tu llave GPG -If you're using a GPG key that matches your committer identity and your verified email address associated with your account on {% ifversion ghae %}{% data variables.product.product_name %}{% else %}{% data variables.location.product_location %}{% endif %}, then you can begin signing commits and signing tags. +Si estás utilizando una clave GPG que coincide con tu identidad de confirmante y tu dirección de correo electrónico verificada asociada a tu cuenta de {% ifversion ghae %}{% data variables.product.product_name %}{% else %}{% data variables.location.product_location %}{% endif %}, entonces puedes comenzar a firmar confirmaciones y etiquetas. {% note %} -If you don't have a GPG key that matches your committer identity, you need to associate an email with an existing key. For more information, see "[Associating an email with your GPG key](/articles/associating-an-email-with-your-gpg-key)". +Si no tienes una llave GPG que coincida con la identidad de la persona que confirma el cambio, debes asociar un correo electrónico a una llave existente. Para más información, vea "[Asociación de un correo electrónico con la clave de GPG](/articles/associating-an-email-with-your-gpg-key)". {% endnote %} -If you have multiple GPG keys, you need to tell Git which one to use. +Si tienes múltiples llaves GPG, le debes decir a Git cuál utilizar. -{% data reusables.command_line.open_the_multi_os_terminal %} -{% data reusables.gpg.configure-gpg-signing %} -{% data reusables.gpg.list-keys-with-note %} -{% data reusables.gpg.copy-gpg-key-id %} -{% data reusables.gpg.paste-gpg-key-id %} -{% data reusables.gpg.set-auto-sign %} -1. If you aren't using the GPG suite, run the following command in the `zsh` shell to add the GPG key to your `.zshrc` file, if it exists, or your `.zprofile` file: +{% data reusables.command_line.open_the_multi_os_terminal %} {% data reusables.gpg.configure-gpg-signing %} {% data reusables.gpg.list-keys-with-note %} {% data reusables.gpg.copy-gpg-key-id %} {% data reusables.gpg.paste-gpg-key-id %} {% data reusables.gpg.set-auto-sign %} +1. Si no usa el conjunto de GPG, ejecute el comando siguiente en el shell de `zsh` para agregar la clave de GPG al archivo `.zshrc`, si existe, o bien al archivo `.zprofile`: ```shell $ if [ -r ~/.zshrc ]; then echo 'export GPG_TTY=$(tty)' >> ~/.zshrc; \ else echo 'export GPG_TTY=$(tty)' >> ~/.zprofile; fi ``` - Alternatively, if you use the `bash` shell, run this command: + Como alternativa, si usa el shell de `bash`, ejecute este comando: ```shell $ if [ -r ~/.bash_profile ]; then echo 'export GPG_TTY=$(tty)' >> ~/.bash_profile; \ else echo 'export GPG_TTY=$(tty)' >> ~/.profile; fi ``` -1. Optionally, to prompt you to enter a PIN or passphrase when required, install `pinentry-mac`. For example, using [Homebrew](https://brew.sh/): +1. Opcionalmente, para que se le solicite que escriba un PIN o una frase de contraseña cuando sea necesario, instale `pinentry-mac`. Por ejemplo, con [Homebrew](https://brew.sh/): ```shell $ brew install pinentry-mac $ echo "pinentry-program $(which pinentry-mac)" >> ~/.gnupg/gpg-agent.conf @@ -57,70 +58,56 @@ If you have multiple GPG keys, you need to tell Git which one to use. {% windows %} -## Telling Git about your GPG key +## Informarle a Git acerca de tu llave GPG -If you're using a GPG key that matches your committer identity and your verified email address associated with your account on {% ifversion ghae %}{% data variables.product.product_name %}{% else %}{% data variables.location.product_location %}{% endif %}, then you can begin signing commits and signing tags. +Si estás utilizando una clave GPG que coincide con tu identidad de confirmante y tu dirección de correo electrónico verificada asociada a tu cuenta de {% ifversion ghae %}{% data variables.product.product_name %}{% else %}{% data variables.location.product_location %}{% endif %}, entonces puedes comenzar a firmar confirmaciones y etiquetas. {% note %} -If you don't have a GPG key that matches your committer identity, you need to associate an email with an existing key. For more information, see "[Associating an email with your GPG key](/articles/associating-an-email-with-your-gpg-key)". +Si no tienes una llave GPG que coincida con la identidad de la persona que confirma el cambio, debes asociar un correo electrónico a una llave existente. Para más información, vea "[Asociación de un correo electrónico con la clave de GPG](/articles/associating-an-email-with-your-gpg-key)". {% endnote %} -If you have multiple GPG keys, you need to tell Git which one to use. +Si tienes múltiples llaves GPG, le debes decir a Git cuál utilizar. -{% data reusables.command_line.open_the_multi_os_terminal %} -{% data reusables.gpg.configure-gpg-signing %} -{% data reusables.gpg.list-keys-with-note %} -{% data reusables.gpg.copy-gpg-key-id %} -{% data reusables.gpg.paste-gpg-key-id %} -{% data reusables.gpg.set-auto-sign %} +{% data reusables.command_line.open_the_multi_os_terminal %} {% data reusables.gpg.configure-gpg-signing %} {% data reusables.gpg.list-keys-with-note %} {% data reusables.gpg.copy-gpg-key-id %} {% data reusables.gpg.paste-gpg-key-id %} {% data reusables.gpg.set-auto-sign %} {% endwindows %} {% linux %} -## Telling Git about your GPG key +## Informarle a Git acerca de tu llave GPG -If you're using a GPG key that matches your committer identity and your verified email address associated with your account on {% ifversion ghae %}{% data variables.product.product_name %}{% else %}{% data variables.location.product_location %}{% endif %}, then you can begin signing commits and signing tags. +Si estás utilizando una clave GPG que coincide con tu identidad de confirmante y tu dirección de correo electrónico verificada asociada a tu cuenta de {% ifversion ghae %}{% data variables.product.product_name %}{% else %}{% data variables.location.product_location %}{% endif %}, entonces puedes comenzar a firmar confirmaciones y etiquetas. {% note %} -If you don't have a GPG key that matches your committer identity, you need to associate an email with an existing key. For more information, see "[Associating an email with your GPG key](/articles/associating-an-email-with-your-gpg-key)". +Si no tienes una llave GPG que coincida con la identidad de la persona que confirma el cambio, debes asociar un correo electrónico a una llave existente. Para más información, vea "[Asociación de un correo electrónico con la clave de GPG](/articles/associating-an-email-with-your-gpg-key)". {% endnote %} -If you have multiple GPG keys, you need to tell Git which one to use. +Si tienes múltiples llaves GPG, le debes decir a Git cuál utilizar. -{% data reusables.command_line.open_the_multi_os_terminal %} -{% data reusables.gpg.configure-gpg-signing %} -{% data reusables.gpg.list-keys-with-note %} -{% data reusables.gpg.copy-gpg-key-id %} -{% data reusables.gpg.paste-gpg-key-id %} -{% data reusables.gpg.set-auto-sign %} -1. To add your GPG key to your `.bashrc` startup file, run the following command: +{% data reusables.command_line.open_the_multi_os_terminal %} {% data reusables.gpg.configure-gpg-signing %} {% data reusables.gpg.list-keys-with-note %} {% data reusables.gpg.copy-gpg-key-id %} {% data reusables.gpg.paste-gpg-key-id %} {% data reusables.gpg.set-auto-sign %} +1. Para agregar la clave de GPG al archivo de inicio de `.bashrc`, ejecute el comando siguiente: ```bash $ [ -f ~/.bashrc ] && echo 'export GPG_TTY=$(tty)' >> ~/.bashrc ``` -{% endlinux %} -{% ifversion ssh-commit-verification %} +{% endlinux %} {% ifversion ssh-commit-verification %} -## Telling Git about your SSH key +## Indicación a Git acerca de tu clave SSH -You can use an existing SSH key to sign commits and tags, or generate a new one specifically for signing. For more information, see "[Generating a new SSH key and adding it to the ssh-agent](/github/authenticating-to-github/generating-a-new-ssh-key-and-adding-it-to-the-ssh-agent)." +Puedes usar una clave SSH existente para firmar confirmaciones y etiquetas, o generar una nueva específicamente para firmar. Para obtener más información, consulta "[Generación de una nueva clave SSH y adición a ssh-agent](/github/authenticating-to-github/generating-a-new-ssh-key-and-adding-it-to-the-ssh-agent)". {% data reusables.gpg.ssh-git-version %} -{% data reusables.command_line.open_the_multi_os_terminal %} -{% data reusables.gpg.configure-ssh-signing %} -{% data reusables.gpg.copy-ssh-public-key %} -{% data reusables.gpg.paste-ssh-public-key %} +{% data reusables.command_line.open_the_multi_os_terminal %} {% data reusables.gpg.configure-ssh-signing %} {% data reusables.gpg.copy-ssh-public-key %} {% data reusables.gpg.paste-ssh-public-key %} {% endif %} {% data reusables.gpg.x-509-key %} -## Further reading +## Información adicional -- "[Adding a new SSH key to your GitHub account](/authentication/connecting-to-github-with-ssh/adding-a-new-ssh-key-to-your-github-account)." -- "[Signing commits](/articles/signing-commits)" -- "[Signing tags](/articles/signing-tags)" +- "[incorporación de una clave SSH nueva a tu cuenta de GitHub](/authentication/connecting-to-github-with-ssh/adding-a-new-ssh-key-to-your-github-account)". +- "[Firma de confirmaciones](/articles/signing-commits)" +- "[Firma de etiquetas](/articles/signing-tags)" diff --git a/translations/es-ES/content/code-security/supply-chain-security/understanding-your-software-supply-chain/troubleshooting-the-dependency-graph.md b/translations/es-ES/content/code-security/supply-chain-security/understanding-your-software-supply-chain/troubleshooting-the-dependency-graph.md index c1879f3d31..2ea290fe37 100644 --- a/translations/es-ES/content/code-security/supply-chain-security/understanding-your-software-supply-chain/troubleshooting-the-dependency-graph.md +++ b/translations/es-ES/content/code-security/supply-chain-security/understanding-your-software-supply-chain/troubleshooting-the-dependency-graph.md @@ -48,7 +48,7 @@ Yes, the dependency graph has two categories of limits: Manifests over 0.5 MB in size are only processed for enterprise accounts. For other accounts, manifests over 0.5 MB are ignored and will not create {% data variables.product.prodname_dependabot_alerts %}. - By default, {% data variables.product.prodname_dotcom %} will not process more than 20 manifests per repository. {% data variables.product.prodname_dependabot_alerts %} are not created for manifests beyond this limit. If you need to increase the limit, contact {% data variables.contact.contact_support %}. + By default, {% data variables.product.prodname_dotcom %} will not process more than {% ifversion fpt %}150{% else %}600{% endif %} manifests per repository. {% data variables.product.prodname_dependabot_alerts %} are not created for manifests beyond this limit. If you need to increase the limit, contact {% data variables.contact.contact_support %}. 2. **Visualization limits** diff --git a/translations/es-ES/content/education/manage-coursework-with-github-classroom/integrate-github-classroom-with-an-ide/using-github-codespaces-with-github-classroom.md b/translations/es-ES/content/education/manage-coursework-with-github-classroom/integrate-github-classroom-with-an-ide/using-github-codespaces-with-github-classroom.md index 5485268315..d2d9a09f01 100644 --- a/translations/es-ES/content/education/manage-coursework-with-github-classroom/integrate-github-classroom-with-an-ide/using-github-codespaces-with-github-classroom.md +++ b/translations/es-ES/content/education/manage-coursework-with-github-classroom/integrate-github-classroom-with-an-ide/using-github-codespaces-with-github-classroom.md @@ -81,7 +81,7 @@ When a student opens an assignment, the repository's README file includes their ![Screenshot of the Codespaces note in the README for a student assignment repository](/assets/images/help/classroom/student-codespaces-readme-link.png) -Students can launch a new or existing codespace by clicking the **{% octicon "code" aria-label="The code icon" %} Code** button on the main page of the assignment repository, then selecting the **Codespaces** tab. For more information, see "[Creating a codespace](/codespaces/developing-in-codespaces/creating-a-codespace#creating-a-codespace)." +Students can launch a new or existing codespace by clicking the **Open in GitHub Codespace** button in the README, or by clicking the **{% octicon "code" aria-label="The code icon" %} Code** button on the main page of the assignment repository, then selecting the **Codespaces** tab. From the **Codespaces** tab you can select an existing codespace or create a new one. For more information, see "[Creating a codespace](/codespaces/developing-in-codespaces/creating-a-codespace#creating-a-codespace)." ![Launch new codespace in assignment repository](/assets/images/help/classroom/student-launch-new-codespace.png) diff --git a/translations/es-ES/content/get-started/getting-started-with-git/about-remote-repositories.md b/translations/es-ES/content/get-started/getting-started-with-git/about-remote-repositories.md index 9f811b3086..c1276038d8 100644 --- a/translations/es-ES/content/get-started/getting-started-with-git/about-remote-repositories.md +++ b/translations/es-ES/content/get-started/getting-started-with-git/about-remote-repositories.md @@ -34,12 +34,12 @@ You can use the `git remote add` command to match a remote URL with a name. For example, you'd type the following in the command line: ```shell -git remote add origin <REMOTE_URL> +git remote add origin <REMOTE_URL> ``` This associates the name `origin` with the `REMOTE_URL`. -You can use the command `git remote set-url` to [change a remote's URL](/github/getting-started-with-github/managing-remote-repositories). +You can use the command `git remote set-url` to [change a remote's URL](/get-started/getting-started-with-git/managing-remote-repositories). ## Choosing a URL for your remote repository @@ -47,7 +47,7 @@ There are several ways to clone repositories available on {% data variables.loca When you view a repository while signed in to your account, the URLs you can use to clone the project onto your computer are available below the repository details. -For information on setting or changing your remote URL, see "[Managing remote repositories](/github/getting-started-with-github/managing-remote-repositories)." +For information on setting or changing your remote URL, see "[Managing remote repositories](/get-started/getting-started-with-git/managing-remote-repositories)." ## Cloning with HTTPS URLs diff --git a/translations/es-ES/content/organizations/managing-peoples-access-to-your-organization-with-roles/index.md b/translations/es-ES/content/organizations/managing-peoples-access-to-your-organization-with-roles/index.md index bb8ae49976..24e4ce4ea6 100644 --- a/translations/es-ES/content/organizations/managing-peoples-access-to-your-organization-with-roles/index.md +++ b/translations/es-ES/content/organizations/managing-peoples-access-to-your-organization-with-roles/index.md @@ -15,8 +15,9 @@ topics: - Teams children: - /roles-in-an-organization - - /maintaining-ownership-continuity-for-your-organization + - /about-custom-repository-roles - /managing-custom-repository-roles-for-an-organization + - /maintaining-ownership-continuity-for-your-organization - /adding-a-billing-manager-to-your-organization - /removing-a-billing-manager-from-your-organization - /managing-security-managers-in-your-organization diff --git a/translations/es-ES/content/organizations/managing-peoples-access-to-your-organization-with-roles/managing-custom-repository-roles-for-an-organization.md b/translations/es-ES/content/organizations/managing-peoples-access-to-your-organization-with-roles/managing-custom-repository-roles-for-an-organization.md index 81b3fe91e1..0cb62007f0 100644 --- a/translations/es-ES/content/organizations/managing-peoples-access-to-your-organization-with-roles/managing-custom-repository-roles-for-an-organization.md +++ b/translations/es-ES/content/organizations/managing-peoples-access-to-your-organization-with-roles/managing-custom-repository-roles-for-an-organization.md @@ -1,176 +1,67 @@ --- -title: Administrar roles de repositorio personalizados en una organización -intro: Puedes controlar el acceso a los repositorios de tu organización de forma más granular si creas roles de repositorio personalizados. +title: Managing custom repository roles for an organization +intro: You can create, edit, or delete custom repository roles for your organization. permissions: Organization owners can manage custom repository roles. versions: feature: custom-repository-roles topics: - Organizations - Teams -shortTitle: Custom repository roles +shortTitle: Manage custom roles redirect_from: - /early-access/github/articles/managing-custom-repository-roles-for-an-organization -ms.openlocfilehash: e37e7822abc378cd91fb719dd472edaf35af4465 -ms.sourcegitcommit: 478f2931167988096ae6478a257f492ecaa11794 -ms.translationtype: HT -ms.contentlocale: es-ES -ms.lasthandoff: 09/09/2022 -ms.locfileid: '147858688' --- -## Acerca de los roles de repositorio personalizados -Para llevar a cabo cualquier acción en {% data variables.product.product_name %}, tal como crear una solicitud de cambios en un repositorio o cambiar los ajustes de facturación de una organización, los individuos deben tener acceso suficiente a la cuenta o recurso relevante. Los permisos son los que controlan este tipo de acceso. Un permiso es la capacidad de llevar a cabo una acción específica. Por ejemplo, la capacidad de borrar una propuesta constituye un permiso. Un rol es un conjunto de permisos que puedes asignar a los individuos o equipos. +{% data reusables.organizations.custom-repo-roles-ghec-only %} -Dentro de una organización, puedes asignar roles a nivel de repositorio, equipo u organización. Para obtener más información acerca de los distintos niveles de roles, vea "[Roles en una organización](/organizations/managing-peoples-access-to-your-organization-with-roles/roles-in-an-organization)". +## About custom repository roles -Puede tener un control más pormenorizado sobre los permisos que concede en el nivel de repositorio. Para ello, cree hasta tres roles de repositorio personalizados. Un rol de repositorio personalizado es un conjunto de permisos configurables con un nombre personalizado de tu elección. Después de que creas un rol personalizado, cualquiera con acceso administrativo a un repositorio puede asignar el rol a un individuo o equipo. Para obtener más información, consulta "[Administración del acceso de una persona a un repositorio de la organización](/organizations/managing-access-to-your-organizations-repositories/managing-an-individuals-access-to-an-organization-repository)" y "[Administración del acceso de equipo a un repositorio de la organización](/organizations/managing-access-to-your-organizations-repositories/managing-team-access-to-an-organization-repository)". +{% data reusables.organizations.about-custom-repo-roles %} For more information, see "[About custom repository roles](/organizations/managing-peoples-access-to-your-organization-with-roles/about-custom-repository-roles)." -{% ifversion custom-repo-role-api %} +## Creating a repository role -También puedes usar la API de REST para crear y administrar roles de repositorio personalizados. Para obtener más información, consulta "[Roles de repositorio personalizados](/rest/orgs/custom-roles)". +To create a new repository role, you add permissions to an inherited role and give the custom role a name. -{% else %} +{% data reusables.profile.access_profile %} +{% data reusables.profile.access_org %} +{% data reusables.organizations.org_settings %} +{% data reusables.organizations.org-list %} +{% data reusables.organizations.org-settings-repository-roles %} +5. Click **Create a Role**. + ![Screenshot of "Create a Role" button](/assets/images/help/organizations/repository-role-create-role.png) +4. Under "Name", type the name of your repository role. + ![Field to type a name for the repository role](/assets/images/help/organizations/repository-role-name.png) +5. Under "Description", type a description of your repository role. + ![Field to type a description for the repository role](/assets/images/help/organizations/repository-role-description.png) +6. Under "Choose a role to inherit", select the role you want to inherit. + ![Selecting repository role base role option](/assets/images/help/organizations/repository-role-base-role-option.png) +7. Under "Add Permissions", use the drop-down menu to select the permissions you want your custom role to include. + ![Selecting permission levels from repository role drop-down](/assets/images/help/organizations/repository-role-drop-down.png) +7. Click **Create role**. + ![Confirm creating a repository role](/assets/images/help/organizations/repository-role-creation-confirm.png) -También puedes usar la API de REST para enumerar los roles de repositorio personalizados disponibles en tu organización. Para obtener más información, consulta "[API de roles de repositorio personalizados](/rest/orgs/custom-roles)". +## Editing a repository role -{% endif %} +{% data reusables.profile.access_profile %} +{% data reusables.profile.access_org %} +{% data reusables.organizations.org_settings %} +{% data reusables.organizations.org-list %} +{% data reusables.organizations.org-settings-repository-roles %} +3. To the right of the role you want to edit, click {% octicon "kebab-horizontal" aria-label="The horizontal kebab icon" %}, then click **Edit**. + ![Edit option in drop-down menu for repository roles](/assets/images/help/organizations/repository-role-edit-setting.png) +4. Edit, then click **Update role**. + ![Edit fields and update repository roles](/assets/images/help/organizations/repository-role-update.png) -## Acerca del rol heredado +## Deleting a repository role -Cuando creas un rol de repositorio personalizado, comenzarás eligiendo un rol heredado de un conjunto de opciones predefinidas. El rol heredado determinará el conjunto inicial de permisos que se incluyen en el rol personalizado. Entonces, podrás seguir personalizando el rol si eliges permisos adicionales para asignarle a este. Para obtener la lista completa de permisos disponibles, vea "[Permisos adicionales para roles personalizados](#additional-permissions-for-custom-roles)". +If you delete an existing repository role, all pending invitations, teams, and users with the custom role will be reassigned to the organization's base permissions. -Tus opciones para escoger el rol heredado se estandarizan para tipos diferentes de contribuyentes en tu repositorio. - -| Rol heredado | Diseñada para | -|----|----| -| **Lectura** | Contribuyentes diferentes a los de código que quieren ver o debatir en tu proyecto. | -| **Evaluación de errores** | Contribuyentes que necesitan administrar propuestas y solicitudes de cambio proactivamente sin acceso de escritura. | -| **Escritura** | Miembros de la organización y colaboradores que suben información a tu proyecto activamente. | -| **Mantenimiento** | Administradores de proyectos que necesitan administrar el repositorio sin acceso a las acciones destructivas o sensibles. - -## Roles personalizados de ejemplo - -Aquí te mostramos ejemplos de los roles de repositorio personalizados que puedes configurar. - -| Rol de repositorio personalizado | Resumen | Rol heredado | Permisos adicionales | -|----|----|----|----| -| Ingeniero de seguridad | Puede contribuir con código y mantener el mapa de seguridad | **Mantenimiento** | Borrar los resultados del escaneo de código | -| Contractor | Puede desarrollar integraciones de webhooks | **Escritura** | Administrar webhooks | -| Adminsitrador de comunidad | Puede manejar todas las interacciones de la comunidad sin poder contribuir con código | **Lectura** | - Marcar una incidencia como duplicada
- Administrar la configuración de la página de GitHub
- Administrar la configuración de la wiki
- Establecer la versión preliminar social
- Editar metadatos del repositorio
- Discusiones de evaluación de prioridades | - -## Permisos adicionales para los roles personalizados - -Después de haber elegido un rol heredado, puedes seleccionar los permisos adicionales para tu rol personalizado. - -Solo puedes elegir un permiso adicional si no se ha incluido ya en el rol heredado. Por ejemplo, si el rol heredado ofrece acceso de **Escritura** en un repositorio, el permiso de "Cerrar una solicitud de incorporación de cambios" ya se habrá incluido en el rol heredado. - -{% ifversion discussions %} -### Debates - -- **Crear una categoría de discusión**: capacidad para crear una nueva categoría de discusión. Para obtener más información, consulta «[Crear una nueva categoría de discusión](/discussions/managing-discussions-for-your-community/managing-categories-for-discussions#creating-a-category)». -- **Editar una categoría de discusión**: capacidad para editar una categoría de discusión. Para obtener más información, consulta «[Editar una categoría de discusión](/discussions/managing-discussions-for-your-community/managing-categories-for-discussions#editing-a-category)». -- **Eliminar una categoría de discusión**: capacidad para eliminar una categoría de discusión. Para obtener más información, consulta «[Eliminar una categoría de discusión](/discussions/managing-discussions-for-your-community/managing-categories-for-discussions#deleting-a-category)». -- **Marcar o desmarcar respuestas de discusión**: capacidad de marcar respuestas a una discusión si la categoría de la discusión acepta respuestas. Para obtener más información, consulta «[Marcar o desmarcar comentarios en una discusión como la respuesta](/discussions/managing-discussions-for-your-community/moderating-discussions#marking-a-comment-as-an-answer)». -- **Ocultar o mostrar comentarios de discusión**: capacidad de ocultar y mostrar comentarios en una discusión. Para más información, vea "[Moderación de debates](/communities/moderating-comments-and-conversations/managing-disruptive-comments#hiding-a-comment)". -- **Convertir problemas en discusiones**: capacidad para convertir un problema en una discusión. Para obtener más información, consulta «[Conversión de problemas en discusiones](/discussions/managing-discussions-for-your-community/moderating-discussions#converting-an-issue-to-a-discussion)». -{% endif %} - -### Propuestas y solicitudes de cambios - -- **Asignar o eliminar a un usuario**: asigna un usuario a una solicitud o solicitud de incorporación de cambios, o lo elimina de ellas. -- **Agregar o eliminar etiqueta**: agrega una etiqueta a una incidencia o solicitud de incorporación de cambios, o la elimina de ellas. - -### Problema - -- **Cerrar una incidencia** -- **Volver a abrir una incidencia que se había cerrado** -- **Eliminar una incidencia** -- **Marcar una incidencia como duplicada** - -### Solicitud de incorporación de cambios - -- **Cerrar una solicitud de incorporación de cambios** -- **Volver a abrir una solicitud de incorporación de cambios** -- **Solicitar una revisión de solicitud de incorporación de cambios**: solicite una revisión de un usuario o equipo. - -### Repositorio - -- **Establecer hitos**: agregue hitos a una incidencia o solicitud de incorporación de cambios. -- **Administrar la configuración de wiki**: active wikis para un repositorio. -- **Administrar la configuración del proyecto**: activar proyectos para un repositorio. -- **Administrar la configuración de combinación de solicitudes de incorporación de cambios**: elija el tipo de confirmaciones de combinación que se permiten en su repositorio, tales como la fusión mediante combinación, fusión mediante combinación con "squash" o fusión mediante combinación de base. -- **Administrar la configuración de {% data variables.product.prodname_pages %}** : habilite {% data variables.product.prodname_pages %} para el repositorio y seleccione la rama que quiera publicar. Para más información, vea "[Configuración de un origen de publicación para el sitio de {% data variables.product.prodname_pages %}](/pages/getting-started-with-github-pages/configuring-a-publishing-source-for-your-github-pages-site)". -- **Administrar webhooks**: agregue webhooks al repositorio. -- **Administrar claves de implementación**: agregue claves de implementación al repositorio. -- **Editar metadatos del repositorio**: actualice la descripción del repositorio, así como sus temas. -{%- ifversion ghec %} -- **Establecer límites de interacción**: restrinja temporalmente a usuarios determinados para que no puedan comentar, abrir incidencias o crear solicitudes de incorporación de cambios en el repositorio público y oblíguelos a pasar un periodo de tiempo con actividad limitada. Para más información, vea "[Limitación de las interacciones en el repositorio](/communities/moderating-comments-and-conversations/limiting-interactions-in-your-repository)". -{%- endif %} -- **Establecer la vista previa social**: agregue una imagen de identificación a su repositorio que aparezca en las plataformas de redes sociales cuando se vincule a este. Para obtener más información, vea "[Personalización de la versión preliminar de redes sociales del repositorio](/repositories/managing-your-repositorys-settings-and-features/customizing-your-repository/customizing-your-repositorys-social-media-preview)". -- **Insertar confirmaciones en ramas protegidas**: inserte en una rama marcada como rama protegida. Las reglas de protección de rama se seguirán aplicando y podrían dar lugar a que se rechace una inserción. -- **Crear etiquetas protegidas**: cree etiquetas que coincidan con una regla de protección de etiquetas. Para obtener más información, vea "[Configuración de reglas de protección de etiquetas](/repositories/managing-your-repositorys-settings-and-features/managing-repository-settings/configuring-tag-protection-rules)". -- **Eliminar etiquetas protegidas**: elimine etiquetas que coincidan con una regla de protección de etiquetas. Para obtener más información, consulta "[Configuración de reglas de protección de etiquetas](/repositories/managing-your-repositorys-settings-and-features/managing-repository-settings/configuring-tag-protection-rules)". {% ifversion bypass-branch-protections %} -- **Omitir protecciones de rama**: realizar la inserción en una rama protegida sin necesidad de cumplir con las reglas de protección de rama. {% endif %} - -### Seguridad - -- **Ver los resultados de {% data variables.product.prodname_code_scanning %}** : capacidad para ver las alertas de {% data variables.product.prodname_code_scanning %}. -- **Descartar o volver a abrir los resultados de {% data variables.product.prodname_code_scanning %}** : capacidad para descartar o volver a abrir las alertas de {% data variables.product.prodname_code_scanning %}. -- **Eliminar los resultados de {% data variables.product.prodname_code_scanning %}** : capacidad para eliminar las alertas de {% data variables.product.prodname_code_scanning %}. -- **Ver {% data variables.product.prodname_dependabot_alerts %}** : capacidad para ver {% data variables.product.prodname_dependabot_alerts %}. -- **Descartar o volver a abrir {% data variables.product.prodname_dependabot_alerts %}** : capacidad para descartar o volver a abrir {% data variables.product.prodname_dependabot_alerts %}. -- **Ver los resultados de {% data variables.product.prodname_secret_scanning %}** : capacidad para ver las alertas de {% data variables.product.prodname_secret_scanning %}. -- **Descartar o volver a abrir los resultados de {% data variables.product.prodname_secret_scanning %}** : capacidad para descartar o volver a abrir las alertas de {% data variables.product.prodname_secret_scanning %}. - -## Precedencia de los distintos niveles de acceso - -Si se otorga a una persona los diferentes niveles de acceso mediante vías diferentes, tales como la membrecía de equipo y los permisos base de una organización, el acceso superior anulará a los otros. Por ejemplo, si un propietario de una organización otorga a los miembros organizacionales un rol personalizado que utilice el rol heredado de "Lectura" y luego el propietario configura el permiso base de la organización en "Escritura", entonces este rol personalizado tendrá el acceso de escritura en conjunto con cualquier permiso adicional que se incluya en dicho rol personalizado. - -{% data reusables.organizations.mixed-roles-warning %} - -Para resolver el acceso que ocasiona el conflicto, puedes ajustar los permisos básicos de tu organización o el acceso del equipo o editar el rol personalizado. Para más información, consulte: - - "[Definición de permisos base para una organización](/github/setting-up-and-managing-organizations-and-teams/setting-base-permissions-for-an-organization)" - - "[Administración del acceso de equipo a un repositorio de la organización](/organizations/managing-access-to-your-organizations-repositories/managing-team-access-to-an-organization-repository)" - - "[Edición de un rol de repositorio](#editing-a-repository-role)" - -## Crear un rol de repositorio - -Para crear un rol de repositorio nuevo, puedes agregar permisos a un rol heredado y otorgarle un nombre a este. - -{% ifversion ghec %} {% note %} - -**Nota**: Solo las organizaciones que usan {% data variables.product.prodname_ghe_cloud %} pueden crear roles de repositorio personalizados. {% data reusables.enterprise.link-to-ghec-trial %} - -{% endnote %} {% endif %} - -{% data reusables.profile.access_profile %} {% data reusables.profile.access_org %} {% data reusables.organizations.org_settings %} {% data reusables.organizations.org-list %} {% data reusables.organizations.org-settings-repository-roles %} -5. Haga clic en **Create a Role** (Crear un rol). - ![Captura de pantalla del botón "Crear un rol"](/assets/images/help/organizations/repository-role-create-role.png) -4. Debajo de "Nombre", teclea el nombre del tu rol de repositorio. - ![Campo en el cual se escribe el nombre del rol del repositorio](/assets/images/help/organizations/repository-role-name.png) -5. Debajo de "Descripción", teclea la descripción de tu rol de repositorio. - ![Campo en el cual se escribe la descripción del rol de repositorio](/assets/images/help/organizations/repository-role-description.png) -6. Debajo de "Elige un rol a heredar", selecciona el rol que quieras heredar. - ![Selección de la opción de rol base para el rol de repositorio](/assets/images/help/organizations/repository-role-base-role-option.png) -7. Debajo de "Agregar permisos", utiliza el menú desplegable para seleccionar los permisos que quieras que incluya tu rol personalizado. - ![Selección de los niveles de permiso desde el menú desplegable del rol de repositorio](/assets/images/help/organizations/repository-role-drop-down.png) -7. Haga clic en **Create role** (Crear rol). - ![Confirmación de la creación de un rol de repositorio](/assets/images/help/organizations/repository-role-creation-confirm.png) - -## Editar un rol de repositorio - -{% data reusables.profile.access_profile %} {% data reusables.profile.access_org %} {% data reusables.organizations.org_settings %} {% data reusables.organizations.org-list %} {% data reusables.organizations.org-settings-repository-roles %} -3. A la derecha del rol que quiera editar, haga clic en {% octicon "kebab-horizontal" aria-label="The horizontal kebab icon" %} y luego en **Edit** (Editar). - ![Opción de editar en el menú desplegable de los roles de repositorio](/assets/images/help/organizations/repository-role-edit-setting.png) -4. Edítelo y, después, haga clic en **Update role** (Actualizar rol). - ![Campos de editar y actualizar roles de repositorio](/assets/images/help/organizations/repository-role-update.png) - -## Borrar un rol de repositorio - -Si borras un rol de repositorio existente, todas las invitaciones pendientes, equipos y usuarios con el rol personalizado se reasignarán a los permisos base de la organización. - -{% data reusables.profile.access_profile %} {% data reusables.profile.access_org %} {% data reusables.organizations.org_settings %} {% data reusables.organizations.org-list %} {% data reusables.organizations.org-settings-repository-roles %} -3. A la derecha del rol que quiera eliminar, haga clic en {% octicon "kebab-horizontal" aria-label="The horizontal kebab icon" %} y luego en **Delete** (Eliminar). - ![Opción de editar en el menú desplegable de los roles de repositorio](/assets/images/help/organizations/repository-role-delete-setting.png) -4. Revise los cambios del rol que quiere quitar y, después, haga clic en **Delete role** (Eliminar rol). - ![Confirmación de la eliminación de un rol de repositorio](/assets/images/help/organizations/repository-role-delete-confirm.png) +{% data reusables.profile.access_profile %} +{% data reusables.profile.access_org %} +{% data reusables.organizations.org_settings %} +{% data reusables.organizations.org-list %} +{% data reusables.organizations.org-settings-repository-roles %} +3. To the right of the role you want to delete, click {% octicon "kebab-horizontal" aria-label="The horizontal kebab icon" %}, then click **Delete**. + ![Edit option in drop-down menu for repository roles](/assets/images/help/organizations/repository-role-delete-setting.png) +4. Review changes for the role you want to remove, then click **Delete role**. + ![Confirm deleting a repository role](/assets/images/help/organizations/repository-role-delete-confirm.png) diff --git a/translations/es-ES/content/repositories/working-with-files/managing-large-files/about-git-large-file-storage.md b/translations/es-ES/content/repositories/working-with-files/managing-large-files/about-git-large-file-storage.md index 7a6fcdc772..17307e5faf 100644 --- a/translations/es-ES/content/repositories/working-with-files/managing-large-files/about-git-large-file-storage.md +++ b/translations/es-ES/content/repositories/working-with-files/managing-large-files/about-git-large-file-storage.md @@ -1,6 +1,6 @@ --- -title: About Git Large File Storage -intro: '{% data variables.product.product_name %} limits the size of files allowed in repositories. To track files beyond this limit, you can use {% data variables.large_files.product_name_long %}.' +title: Acerca de Large File Storage de Git +intro: '{% data variables.product.product_name %} limita el tamaño de los archivos permitidos en los repositorios. Para rastrear los archivos más allá de este límite, puedes utilizar {% data variables.large_files.product_name_long %}.' redirect_from: - /articles/about-large-file-storage - /articles/about-git-large-file-storage @@ -12,33 +12,37 @@ versions: ghae: '*' ghec: '*' shortTitle: Git Large File Storage +ms.openlocfilehash: f0ab54791645dc5c36cce2880ba3ae5c9b705f35 +ms.sourcegitcommit: 06726d24e73f1175f10749d6fdcf143d6094c9a5 +ms.translationtype: HT +ms.contentlocale: es-ES +ms.lasthandoff: 10/28/2022 +ms.locfileid: '148118754' --- +## Acerca de {% data variables.large_files.product_name_long %} -## About {% data variables.large_files.product_name_long %} +{% data variables.large_files.product_name_short %} maneja archivos grandes almacenando referencias del archivo en el repositorio, pero no el archivo real. Para trabajar en la arquitectura de Git, {% data variables.large_files.product_name_short %} crea un archivo de puntero que actúa como una referencia del archivo real (que se almacena en otro lugar). {% data variables.product.product_name %} administra este archivo puntero en tu repositorio. Cuando clonas el repositorio, {% data variables.product.product_name %} usa el archivo puntero como un mapa para ir y buscar el archivo grande por ti. -{% data variables.large_files.product_name_short %} handles large files by storing references to the file in the repository, but not the actual file itself. To work around Git's architecture, {% data variables.large_files.product_name_short %} creates a pointer file which acts as a reference to the actual file (which is stored somewhere else). {% data variables.product.product_name %} manages this pointer file in your repository. When you clone the repository down, {% data variables.product.product_name %} uses the pointer file as a map to go and find the large file for you. +{% ifversion fpt or ghec %} Con {% data variables.large_files.product_name_short %}, puede almacenar archivos hasta: -{% ifversion fpt or ghec %} -Using {% data variables.large_files.product_name_short %}, you can store files up to: - -| Product | Maximum file size | +| Producto | Tamaño de archivo máximo | |------- | ------- | | {% data variables.product.prodname_free_user %} | 2 GB | | {% data variables.product.prodname_pro %} | 2 GB | | {% data variables.product.prodname_team %} | 4 GB | | {% data variables.product.prodname_ghe_cloud %} | 5 GB |{% else %} -Using {% data variables.large_files.product_name_short %}, you can store files up to 5 GB in your repository. +Si utilizas {% data variables.large_files.product_name_short %}, puedes almacenar archivos de hasta 5 GB en tu repositorio. {% endif %} {% data reusables.repositories.git-lfs %} -You can also use {% data variables.large_files.product_name_short %} with {% data variables.product.prodname_desktop %}. For more information about cloning Git LFS repositories in {% data variables.product.prodname_desktop %}, see "[Cloning a repository from GitHub to GitHub Desktop](/desktop/guides/contributing-to-projects/cloning-a-repository-from-github-to-github-desktop)." +Tambié puedes usar {% data variables.large_files.product_name_short %} con {% data variables.product.prodname_desktop %}. Para más información sobre cómo clonar repositorios LFS de Git en {% data variables.product.prodname_desktop %}, vea "[Clonación de un repositorio desde GitHub en GitHub Desktop](/desktop/guides/contributing-to-projects/cloning-a-repository-from-github-to-github-desktop)". {% data reusables.large_files.can-include-lfs-objects-archives %} -## Pointer file format +## Formato de archivo puntero -{% data variables.large_files.product_name_short %}'s pointer file looks like this: +El archivo puntero de {% data variables.large_files.product_name_short %} se ve así: ``` version {% data variables.large_files.version_name %} @@ -46,16 +50,16 @@ oid sha256:4cac19622fc3ada9c0fdeadb33f88f367b541f38b89102a3f1261ac81fd5bcb5 size 84977953 ``` -It tracks the `version` of {% data variables.large_files.product_name_short %} you're using, followed by a unique identifier for the file (`oid`). It also stores the `size` of the final file. +Realiza el seguimiento del `version` de {% data variables.large_files.product_name_short %} que use, seguido de un identificador único para el archivo (`oid`). También almacena el valor `size` del archivo final. {% note %} -**Notes**: -- {% data variables.large_files.product_name_short %} cannot be used with {% data variables.product.prodname_pages %} sites. -- {% data variables.large_files.product_name_short %} cannot be used with template repositories. +**Notas**: +- {% data variables.large_files.product_name_short %} no puede utilizarse con los sitios de {% data variables.product.prodname_pages %}. +- {% data variables.large_files.product_name_short %} no se puede utilizar con repositorios de plantilla. {% endnote %} -## Further reading +## Información adicional -- "[Collaboration with {% data variables.large_files.product_name_long %}](/articles/collaboration-with-git-large-file-storage)" +- "[Colaboración con {% data variables.large_files.product_name_long %}](/articles/collaboration-with-git-large-file-storage)" diff --git a/translations/es-ES/data/release-notes/enterprise-server/2-20/0.yml b/translations/es-ES/data/release-notes/enterprise-server/2-20/0.yml deleted file mode 100644 index d016eaa09f..0000000000 --- a/translations/es-ES/data/release-notes/enterprise-server/2-20/0.yml +++ /dev/null @@ -1,44 +0,0 @@ -date: '2020-02-11' -sections: - features: - - 'En una rama de repositorio, los administradores de éste pueden rechazar cualquier subida que contenga una confirmación de fusión si habilitan el `Requerir un historial lineal` mediante [reglas de protección de rama](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 %}' - - 'Los administradores de repositorio pueden otorgar a todos los usuarios con acceso de subida la capacidad de subir información forzadamente a una rama protegida si habilitan `Permitir subidas forzadas` mediante [reglas de protección de rama](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 %}' - - 'Los administradores de repositorio pueden otorgar a todos los usuarios con permiso de subida la capacidad de borrar una rama protegida si habilitan `Permitir eliminación` mediante [reglas de protección de rama](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 %}' - - 'Los administradores pueden configurar un límite de `maxobjectsize` en los repositorios, [limitando el tamaño de las confirmaciones de subida](https://help.github.com/en/enterprise/admin/installation/setting-git-push-limits) para un repositorio que no esté en el [LFS de Git](https://help.github.com/en/enterprise/admin/installation/configuring-git-large-file-storage-on-github-enterprise-server).{% comment %} https://github.com/github/babeld/pull/864, https://team.githubapp.com/posts/33519, https://github.com/githubcustomers/Slack/issues/27 {% endcomment %}' - - 'Los propietarios de las organizaciones pueden crear un conjunto de etiquetas predeterminadas cuando crean un repositorio nuevo. {% comment %} https://github.com/github/issues-projects/issues/237, https://github.com/github/issues-projects/issues/179 {% endcomment %}' - security_fixes: - - 'Los paquetes se han actualizado a las últimas versiones de seguridad.' - bugs: - - 'Cuando los miembros de una organización intentan ver uno de sus repositorios públicos, un mensaje de SSO podría dañar la visualización de la página. {% comment %} https://github.com/github/github/issues/126677, https://github.com/github/github/pull/127501 {% endcomment %}' - - 'Cuando se visualiza el perfil de un usuario, los enlaces para los equipos de dicho usuario podrían estar rotos. {% comment %} https://github.com/github/github/issues/131771, https://github.com/github/github/pull/131865 {% endcomment %}' - - 'Los usuarios con el rol de `maintain` no pudieron editar los temas del repositorio. {% comment %} https://github.com/github/github/pull/129503, https://github.com/github/github/issues/119456 {% endcomment %}' - - "Los usuarios que no son administradores de una organización recibieron un error\_500 cuando intentaron acceder a la página de inicio de sesión. {% comment %} https://github.com/github/github/pull/129213, https://github.com/github/github/issues/129210, https://github.com/github/github/issues/129212 {% endcomment %}" - - 'El mensaje emergente de edición de historial no se mostró en los comentarios de los gist. {% comment %} https://github.com/github/github/pull/129134, https://github.com/github/github/issues/128496 {% endcomment %}' - - 'Una cuenta nueva pudo registrarse con un correo electrónico que ya estaba registrado. {% comment %} https://github.com/github/github/pull/127905, https://github.com/github/github/issues/127858 {% endcomment %}' - - 'Un servicio de almacenamiento estaba alcanzando un límite de descriptor de archivo y causando el bloqueo del kernel y que otros servicios registraran errores. {% comment %} https://github.com/github/enterprise2/pull/18775 {% endcomment %}' - - 'Cuando una referencia de autoenlace fue parte de una url, el hipervículo podría eliminarse. {% comment %} https://github.com/github/github/pull/126776 {% endcomment %}' - - 'Cuando se agrega un comentario a una solicitud de incorporación de cambios, la sección de `Incidencias vinculadas` de la barra lateral podría desaparecer. {% comment %} https://github.com/github/issues-projects/issues/384, https://github.com/github/github/pull/130514 {% endcomment %}' - - 'Al editar una invitación existente a una organización para un usuario, un encabezado duplicado podría haber aparecido en la tabla de `Equipos`. {% comment %} https://github.com/github/github/issues/120381, https://github.com/github/github/pull/128939 {% endcomment %}' - - 'El servicio `resqued` pudo haber dejado de registrar eventos cuando las colas se volvieron muy largas. {% comment %} https://github.com/github/github/pull/130087, https://github.com/github/business-support/issues/2696 {% endcomment %}' - - 'Los certificados autofirmados no se generan automáticamente al ejecutar el comando `ghe-config-apply` para las configuraciones de agrupamientos y de disponibilidad alta. {% comment %} https://github.com/github/enterprise2/pull/18773 {% endcomment %}' - changes: - - 'No se mostrará ningún logo para un tema si no se ha cargado alguno. {% comment %} https://github.com/github/github/issues/130513, https://github.com/github/github/pull/130515 {% endcomment %}' - - 'Cuando se visualiza una incidencia en un buscador móvil, sus metadatos se enumeran en la parte superior de la página. {% comment %} https://github.com/github/github/pull/127560 {% endcomment %}' - - 'El dominio de nivel superior de Consul cambió de ".consul" a ".ghe.local". {% comment %} https://github.com/github/enterprise2/pull/17443, https://github.com/github/enterprise2/issues/17701 {% endcomment %}' - - 'El servicio de hooshot ya no depende de ElasticSearch y solo usa MySQL como almacenamiento de base de datos. {% comment %} https://github.com/github/enterprise2/pull/18158, https://github.com/github/hookshot/pull/1128, https://github.com/github/enterprise2/pull/15898 {% endcomment %}' - - 'La distinción visual entre incidencias, proyectos y debates se implementó en tarjetas de notas de proyecto. {% comment %} https://github.com/github/github/pull/132038 {% endcomment %}' - - 'En una revisión de solicitud de incorporación de cambios, se muestra una notificación si un comentario de línea múltiple se trunca. {% comment %} https://github.com/github/github/issues/125948, https://github.com/github/github/pull/128677 {% endcomment %}' - - 'Los usuarios pueden visualizar su registro de auditoría en la pestaña de `Registro de seguridad` de su página de configuración personal. {% comment %} https://github.com/github/github/pull/123041{% endcomment %}' - known_issues: - - "En un servidor de GitHub\_Enterprise recién configurado sin ningún usuario, un atacante podía crear el primer usuario administrador. {% comment %} https://github.com/github/enterprise2/issues/1889 {% endcomment %}" - - 'Las reglas de cortafuegos personalizadas no se mantienen durante una actualización. {% comment %} https://github.com/github/enterprise2/issues/2823 {% endcomment %}' - - 'Los archivos supervisados de Git LFS [cargados desde la interfaz web](https://github.com/blog/2105-upload-files-to-your-repositories) se agregan de forma incorrecta y directa al repositorio. {% comment %} https://github.com/github/github/issues/54684 {% endcomment %}' - - "Las incidencias no se pueden cerrar si contienen un enlace permanente a un blob del mismo repositorio en el que la ruta es mayor de 255\_caracteres. {% comment %} https://github.com/github/github/issues/107731 {% endcomment %}" - - 'Al enviar cambios a un gist, se puede desencadenar una excepción durante el enlace posterior a la recepción. {% comment %} https://github.com/github/github/issues/129091 {% endcomment %}' - - 'Las entradas duplicadas de webhooks en la base de datos pueden causar que las actualizaciones de las versiones anteriores fallen. (actualizado 26-02-2020)' - - 'Las mejoras y actualizaciones de configuración producen errores si las configuraciones de los roles de trabajo en segundo plano se han actualizado. {% comment %} https://github.com/github/enterprise2/issues/19119, {% endcomment %}' - - 'Cuando se habilita "Los usuarios pueden buscar en GitHub.com" con GitHub Connect, las incidencias en los repositorios privados e internos no se incluyen en los resultados de la búsqueda de GitHub.com. {% comment %} https://github.com/github/admin-experience/issues/571 {% endcomment %}' - - 'Al actualizar desde versiones anteriores, es posible que no se generen roles de trabajo en segundo plano, lo que impide características esenciales como la combinación de solicitudes de incorporación de cambios. (Actualizado el 07-04-2020) {% comment %} https://github.com/github/enterprise2/issues/19232 {% endcomment %}' - - 'Las alertas de seguridad no se notifican cuando se envían cambios a un repositorio en la línea de comandos. (Actualizado el 23-06-2020) {% comment %} https://github.com/github/github/issues/143190 {% endcomment %}' - - 'El gráfico de dependencias no detectaba las dependencias cuando se implementaban en una configuración de clúster con múltiples nodos de Redis. (Actualizado el 30-06-2020) {% comment %} https://github.com/github/dependency-graph/issues/81 {% endcomment %}' - - 'Cuando un nodo de réplica está sin conexión en una configuración de disponibilidad alta, es posible que {% data variables.product.product_name %} enrute las solicitudes {% data variables.product.prodname_pages %} al nodo sin conexión, lo que reduce la disponibilidad de {% data variables.product.prodname_pages %} para los usuarios.' diff --git a/translations/es-ES/data/release-notes/enterprise-server/2-20/1.yml b/translations/es-ES/data/release-notes/enterprise-server/2-20/1.yml deleted file mode 100644 index c45740fdac..0000000000 --- a/translations/es-ES/data/release-notes/enterprise-server/2-20/1.yml +++ /dev/null @@ -1,21 +0,0 @@ -date: '2020-02-27' -sections: - security_fixes: - - 'Los paquetes se actualizaron a las últimas versiones de seguridad. {% comment %} https://github.com/github/enterprise2/pull/19116, https://github.com/github/enterprise2/pull/19110, https://github.com/github/enterprise2/pull/19154, https://github.com/github/enterprise2/pull/19142 {% endcomment %}' - bugs: - - 'La restauración de copias de seguridad producía un error de tipo "Invalid RDB version number". {% comment %} https://github.com/github/enterprise2/pull/19117, https://github.com/github/enterprise2/pull/19109 {% endcomment %}' - - 'La actualización de una réplica de alta disponibilidad estancaba indefinidamente la espera para que iniciara MySQL. {% comment %} https://github.com/github/enterprise2/pull/19168, https://github.com/github/enterprise2/pull/19101 {% endcomment %}' - - 'Los comentarios de revisión de las solicitudes de incorporación de cambios con valores inesperados para "position" o "original_position" causaba que fallaran las importaciones. {% comment %} https://github.com/github/github/pull/135439, https://github.com/github/github/pull/135374 {% endcomment %}' - - 'Las entradas de webhook duplicadas en la base de datos podrían causar que las mejoras de las versiones previas fallaran. {% comment %} https://github.com/github/hookshot/pull/1541, https://github.com/github/hookshot/pull/1426, https://github.com/github/hookshot/pull/1540 {% endcomment %}' - known_issues: - - 'En una instancia del servidor de GitHub Enterprise recién configurada sin ningún usuario, un atacante puede crear el primer usuario administrador. {% comment %} https://github.com/github/enterprise2/issues/1889 {% endcomment %}' - - 'Las reglas de firewall personalizadas no se mantienen durante una actualización. {% comment %} https://github.com/github/enterprise2/issues/2823 {% endcomment %}' - - 'Los archivos supervisados de Git LFS [cargados desde la interfaz web](https://github.com/blog/2105-upload-files-to-your-repositories) se agregan de forma incorrecta y directa al repositorio. {% comment %} https://github.com/github/github/issues/54684 {% endcomment %}' - - "Las incidencias no se pueden cerrar si contienen un enlace permanente a un blob del mismo repositorio en el que la ruta es mayor de 255\_caracteres. {% comment %} https://github.com/github/github/issues/107731 {% endcomment %}" - - 'Al enviar cambios a un gist, se puede desencadenar una excepción durante el enlace posterior a la recepción. {% comment %} https://github.com/github/github/issues/129091 {% endcomment %}' - - 'Las mejoras y actualizaciones de configuración producen errores si se personalizan las configuraciones en segundo plano de los trabajadores. {% comment %} https://github.com/github/enterprise2/issues/19119, {% endcomment %}' - - 'Cuando se habilita "Los usuarios pueden buscar en GitHub.com" con GitHub Connect, las incidencias en los repositorios privados e internos no se incluyen en los resultados de la búsqueda de GitHub.com. {% comment %} https://github.com/github/admin-experience/issues/571 {% endcomment %}' - - 'Al actualizar desde versiones anteriores, es posible que no se generen roles de trabajo en segundo plano, lo que impide características esenciales como la combinación de solicitudes de incorporación de cambios. (Actualizado el 07-04-2020) {% comment %} https://github.com/github/enterprise2/issues/19232 {% endcomment %}' - - 'Las alertas de seguridad no se notifican cuando se envían cambios a un repositorio en la línea de comandos. (Actualizado el 23-06-2020) {% comment %} https://github.com/github/github/issues/143190 {% endcomment %}' - - 'El gráfico de dependencias no detectaba las dependencias cuando se implementaban en una configuración de clúster con múltiples nodos de Redis. (Actualizado el 30-06-2020) {% comment %} https://github.com/github/dependency-graph/issues/81 {% endcomment %}' - - 'Cuando un nodo de réplica está sin conexión en una configuración de disponibilidad alta, es posible que {% data variables.product.product_name %} todavía enrute las solicitudes a {% data variables.product.prodname_pages %} al nodo sin conexión, lo que reduce la disponibilidad de {% data variables.product.prodname_pages %} para los usuarios.' diff --git a/translations/es-ES/data/release-notes/enterprise-server/2-20/10.yml b/translations/es-ES/data/release-notes/enterprise-server/2-20/10.yml deleted file mode 100644 index 05812f9f9d..0000000000 --- a/translations/es-ES/data/release-notes/enterprise-server/2-20/10.yml +++ /dev/null @@ -1,21 +0,0 @@ -date: '2020-06-23' -sections: - security_fixes: - - 'Los paquetes se han actualizado a sus últimas versiones de seguridad. {% comment %} https://github.com/github/enterprise2/pull/20746, https://github.com/github/enterprise2/pull/20727 {% endcomment %}' - bugs: - - 'Los registros de eventos excesivamente grandes podían ocasionar inestabilidad en el reenvío de registros cuando se utilizaba UDP como el mecanismo de transporte. {% comment %} https://github.com/github/enterprise2/pull/20457, https://github.com/github/enterprise2/pull/20445 {% endcomment %}' - - 'La anulación de la suspensión automática a un usuario mediante SSO no se completa si el atributo de las llaves SSH ya está asociado con la cuenta de usuario. {% comment %} https://github.com/github/github/pull/143474, https://github.com/github/github/pull/142927 {% endcomment %}' - - 'El hash de permiso del repositorio desde la API de REST no indicaba el acceso de los miembros de negocios que tenían acceso de lectura en los repositorios internos. {% comment %} https://github.com/github/github/pull/144755, https://github.com/github/github/pull/144292 {% endcomment %}' - - 'No se interpretaba adecuadamente la vista previa de la descripción de una GitHub App escrita en lenguaje de marcado. {% comment %} https://github.com/github/github/pull/145038, https://github.com/github/github/pull/133360 {% endcomment %}' - - 'El registro de auditoría no incluía los eventos de cambio de protección de rama. {% comment %} https://github.com/github/github/pull/145995, https://github.com/github/github/pull/145014 {% endcomment %}' - - 'Intentar asignar una revisión de código a un miembro de un equipo vacío causaba el error "500 Internal Server Error". {% comment %} https://github.com/github/github/pull/146328, https://github.com/github/github/pull/139330 {% endcomment %}' - - 'La asignación de revisión de código mediante el algoritmo de equilibrio de carga podía asignarse repetidamente al mismo miembro del equipo. {% comment %} https://github.com/github/github/pull/146329, https://github.com/github/github/pull/136504 {% endcomment %}' - known_issues: - - 'En una instancia del servidor de GitHub Enterprise recién configurada sin ningún usuario, un atacante podría crear el primer usuario administrador. {% comment %} https://github.com/github/enterprise2/issues/1889 {% endcomment %}' - - 'Las reglas de firewall personalizadas no se mantienen durante una actualización. {% comment %} https://github.com/github/enterprise2/issues/2823 {% endcomment %}' - - 'Los archivos supervisados de Git LFS [cargados desde la interfaz web](https://github.com/blog/2105-upload-files-to-your-repositories) se han agregado de forma incorrecta y directa al repositorio. {% comment %} https://github.com/github/github/issues/54684 {% endcomment %}' - - "Las incidencias no se pueden cerrar si contienen un enlace permanente a un blob del mismo repositorio en el que la ruta es mayor de 255\_caracteres. {% comment %} https://github.com/github/github/issues/107731 {% endcomment %}" - - 'Cuando se habilita "Los usuarios pueden buscar en GitHub.com" con GitHub Connect, las incidencias en los repositorios privados e internos no se incluyen en los resultados de la búsqueda de GitHub.com. {% comment %} https://github.com/github/admin-experience/issues/571 {% endcomment %}' - - 'Las alertas de seguridad no se notifican cuando se realiza la inserción en un repositorio en la línea de comandos. {% comment %} https://github.com/github/github/issues/143190 {% endcomment %}' - - 'El gráfico de dependencias no detectaba las dependencias cuando se implementaban en una configuración de clúster con múltiples nodos de Redis. (Actualizado el 30-06-2020) {% comment %} https://github.com/github/dependency-graph/issues/81 {% endcomment %}' - - 'Cuando un nodo de réplica está sin conexión en una configuración de disponibilidad alta, es posible que {% data variables.product.product_name %} todavía enrute las solicitudes a {% data variables.product.prodname_pages %} al nodo sin conexión, lo que reduce la disponibilidad de {% data variables.product.prodname_pages %} para los usuarios.' diff --git a/translations/es-ES/data/release-notes/enterprise-server/2-20/11.yml b/translations/es-ES/data/release-notes/enterprise-server/2-20/11.yml deleted file mode 100644 index 51752ed203..0000000000 --- a/translations/es-ES/data/release-notes/enterprise-server/2-20/11.yml +++ /dev/null @@ -1,19 +0,0 @@ -date: '2020-07-09' -sections: - security_fixes: - - '**MEDIA:** Se actualizó nginx a la versión 1.16.1 y se dirigió el CVE-2019-20372. (actualizado 2020-07-22) {% comment %} https://github.com/github/enterprise2/pull/21251 {% endcomment %}' - - 'Los paquetes se han actualizado a sus últimas versiones de seguridad. {% comment %} https://github.com/github/enterprise2/pull/21088, https://github.com/github/enterprise2/pull/21036 {% endcomment %}' - bugs: - - 'La gráfica de dependencias no estaba detectando dependencias cuando se desplegó en una configuración de agrupamiento con nodos múltiples de Redis. {% comment %} https://github.com/github/enterprise2/pull/21260, https://github.com/github/enterprise2/pull/21102 {% endcomment %}' - - 'Algunos archivos de bitácora no rotaron cada 7 días. {% comment %} https://github.com/github/enterprise2/pull/21278, https://github.com/github/enterprise2/pull/21264 {% endcomment %}' - - 'La reutilización rápida de puertos origen de webhooks dio como resultado conexiones rechazadas. {% comment %} https://github.com/github/enterprise2/pull/21289 {% endcomment %}' - - 'Los jobs incorrectos en segundo plano pudieron intentar ejecutarse en instancias que se configuraron como réplicas pasivas. {% comment %} https://github.com/github/enterprise2/pull/21318, https://github.com/github/enterprise2/pull/21212, https://github.com/github/enterprise2/issues/21167 {% endcomment %}' - - 'Los repositorios internos no se incluyeron correctamente en los resultados de búsqueda para las organizaciones habilitadas con SAML. {% comment %} https://github.com/github/github/pull/147503, https://github.com/github/github/pull/145692 {% endcomment %}' - known_issues: - - 'En una instancia del servidor de GitHub Enterprise recién configurada sin ningún usuario, un atacante puede crear el primer usuario administrador. {% comment %} https://github.com/github/enterprise2/issues/1889 {% endcomment %}' - - 'Las reglas de firewall personalizadas no se mantienen durante una actualización. {% comment %} https://github.com/github/enterprise2/issues/2823 {% endcomment %}' - - 'Los archivos supervisados de Git LFS [cargados desde la interfaz web](https://github.com/blog/2105-upload-files-to-your-repositories) se agregan de forma incorrecta y directa al repositorio. {% comment %} https://github.com/github/github/issues/54684 {% endcomment %}' - - "Las incidencias no se pueden cerrar si contienen un enlace permanente a un blob del mismo repositorio en el que la ruta es mayor de 255\_caracteres. {% comment %} https://github.com/github/github/issues/107731 {% endcomment %}" - - 'Cuando se habilita "Los usuarios pueden buscar en GitHub.com" con GitHub Connect, las incidencias en los repositorios privados e internos no se incluyen en los resultados de la búsqueda de GitHub.com. {% comment %} https://github.com/github/admin-experience/issues/571 {% endcomment %}' - - 'Las alertas de seguridad no se notifican cuando se realiza la inserción en un repositorio en la línea de comandos. {% comment %} https://github.com/github/github/issues/143190 {% endcomment %}' - - 'Cuando un nodo de réplica está sin conexión en una configuración de disponibilidad alta, es posible que {% data variables.product.product_name %} todavía enrute las solicitudes a {% data variables.product.prodname_pages %} al nodo sin conexión, lo que reduce la disponibilidad de {% data variables.product.prodname_pages %} para los usuarios.' diff --git a/translations/es-ES/data/release-notes/enterprise-server/2-20/12.yml b/translations/es-ES/data/release-notes/enterprise-server/2-20/12.yml deleted file mode 100644 index d64d1a434b..0000000000 --- a/translations/es-ES/data/release-notes/enterprise-server/2-20/12.yml +++ /dev/null @@ -1,17 +0,0 @@ -date: '2020-07-21' -sections: - security_fixes: - - 'Los paquetes se actualizaron a las últimas versiones de seguridad. {% comment %} https://github.com/github/enterprise2/pull/21437, https://github.com/github/enterprise2/pull/21402, https://github.com/github/enterprise2/pull/21495, https://github.com/github/enterprise2/pull/21479 {% endcomment %}' - bugs: - - 'Las gráficas de monitoreo de la consola de administración a veces no se muestran correctamente en pantallas grandes. {% comment %} https://github.com/github/enterprise2/pull/21397, https://github.com/github/enterprise2/pull/21381 {% endcomment %}' - - 'El flujo de creación de un manifiesto de una GitHub App no se pudo utilizar en algunos escenarios en donde se aplicó la política de cookies de SameSite. {% comment %} https://github.com/github/github/pull/147826, https://github.com/github/github/pull/144121 {% endcomment %}' - changes: - - 'Mejoras al escalamiento de HAProxy. {% comment %} https://github.com/github/enterprise2/pull/21383 {% endcomment %}' - known_issues: - - 'En una instancia del servidor de GitHub Enterprise recién configurada sin ningún usuario, un atacante podría crear el primer usuario administrador. {% comment %} https://github.com/github/enterprise2/issues/1889 {% endcomment %}' - - 'Las reglas de firewall personalizadas no se mantienen durante una actualización. {% comment %} https://github.com/github/enterprise2/issues/2823 {% endcomment %}' - - 'Los archivos supervisados de Git LFS [cargados desde la interfaz web](https://github.com/blog/2105-upload-files-to-your-repositories) se han agregado de forma incorrecta y directa al repositorio. {% comment %} https://github.com/github/github/issues/54684 {% endcomment %}' - - "Las incidencias no se pueden cerrar si contienen un enlace permanente a un blob del mismo repositorio en el que la ruta es mayor de 255\_caracteres. {% comment %} https://github.com/github/github/issues/107731 {% endcomment %}" - - 'Cuando se habilita "Los usuarios pueden buscar en GitHub.com" con GitHub Connect, las incidencias en los repositorios privados e internos no se incluyen en los resultados de la búsqueda de GitHub.com. {% comment %} https://github.com/github/admin-experience/issues/571 {% endcomment %}' - - 'Las alertas de seguridad no se notifican cuando se realiza la inserción en un repositorio en la línea de comandos. {% comment %} https://github.com/github/github/issues/143190 {% endcomment %}' - - 'Cuando un nodo de réplica está sin conexión en una configuración de disponibilidad alta, es posible que {% data variables.product.product_name %} todavía enrute las solicitudes a {% data variables.product.prodname_pages %} al nodo sin conexión, lo que reduce la disponibilidad de {% data variables.product.prodname_pages %} para los usuarios.' diff --git a/translations/es-ES/data/release-notes/enterprise-server/2-20/13.yml b/translations/es-ES/data/release-notes/enterprise-server/2-20/13.yml deleted file mode 100644 index 46d01f27b0..0000000000 --- a/translations/es-ES/data/release-notes/enterprise-server/2-20/13.yml +++ /dev/null @@ -1,22 +0,0 @@ -date: '2020-08-11' -sections: - security_fixes: - - '{% octicon "alert" aria-label="The alert icon" %} **Crítico:** Se ha identificado una vulnerabilidad de ejecución de código remoto en GitHub Pages que podría permitir a un atacante ejecutar comandos como parte de la creación de un sitio de GitHub Pages. Este problema se debía a una dependencia obsoleta y vulnerable que se usaba en el proceso de compilación de Pages. Para aprovechar esta vulnerabilidad de seguridad, un atacante necesitaría permiso para crear un sitio de GitHub Pages en la instancia del servidor de GitHub Enterprise. Esta vulnerabilidad ha afectado a todas las versiones del servidor de GitHub Enterprise. Para mitigar esta vulnerabilidad, se ha actualizado Kramdown a fin de solucionar CVE-2020-14001. {% comment %} https://github.com/github/pages/pull/2836, https://github.com/github/pages/pull/2827 {% endcomment %}' - - '**Alto:** un atacante podría insertar un argumento malintencionado en un subcomando de Git al ejecutarlo en un servidor de GitHub Enterprise. Esto permitiría a un atacante sobrescribir archivos arbitrarios con contenido parcialmente controlado por el usuario y, posiblemente, ejecutar comandos arbitrarios en la instancia del servidor de GitHub Enterprise. Para aprovechar esta vulnerabilidad, un atacante necesitaría permiso de acceso a los repositorios de la instancia del servidor de GitHub Enterprise. Pero debido a otras protecciones implementadas, no podríamos identificar una forma de aprovechar esta vulnerabilidad de forma activa. Esta vulnerabilidad se ha notificado desde el programa GitHub Security Bug Bounty. {% comment %} https://github.com/github/github/pull/151097 {% endcomment %}' - - 'Los paquetes se han actualizado a sus últimas versiones de seguridad. {% comment %} https://github.com/github/enterprise2/pull/21811, https://github.com/github/enterprise2/pull/21700 {% endcomment %}' - bugs: - - 'Un error de configuración de Consul evitó que algunos trabajos en segundo plano se procesaran en instancias independientes. {% comment %} https://github.com/github/enterprise2/pull/21464 {% endcomment %}' - - 'Los cálculos de asignación de memoria de servicio pudieron asignar una cantidad incorrecta o ilimitada de memoria a un servicio, lo que causó un rendimiento pobre del sistema. {% comment %} https://github.com/github/enterprise2/pull/21716 {% endcomment %}' - - 'La plataforma de virtualización para los sistemas de oVirt KVM no se detectó adecuadamente, lo cual ocasionó problemas durante las mejoras. {% comment %} https://github.com/github/enterprise2/pull/21730, https://github.com/github/enterprise2/pull/21669 {% endcomment %}' - - "El mensaje de error para la autenticación no válida con una contraseña mediante la línea de comandos de Git no llenó la URL que vinculaba a agregar el token o llave SSH adecuados. {% comment %} https://github.com/github/github/pull/149714 {% endcomment %}" - - 'GitHub Connect estaba utilizando un punto de conexión obsoleto de la API de GitHub.com. {% comment %} https://github.com/github/github/pull/150828, https://github.com/github/github/pull/150545 {% endcomment %}' - - 'Las propuestas no se pudieron clasificar por *Actualizadas recientemente* en los repositorios que se migraron a una instancia nueva. {% comment %} https://github.com/github/github/pull/150843, https://github.com/github/github/pull/149330 {% endcomment %}' - - 'La página con error 404 contenía los enlaces de estado y contacto de GitHub.com en el pié de página. {% comment %} https://github.com/github/github/pull/151316 {% endcomment %}' - known_issues: - - 'En una instancia del servidor de GitHub Enterprise recién configurada sin ningún usuario, un atacante podría crear el primer usuario administrador. {% comment %} https://github.com/github/enterprise2/issues/1889 {% endcomment %}' - - 'Las reglas de firewall personalizadas no se mantienen durante una actualización. {% comment %} https://github.com/github/enterprise2/issues/2823 {% endcomment %}' - - 'Los archivos supervisados de Git LFS [cargados desde la interfaz web](https://github.com/blog/2105-upload-files-to-your-repositories) se han agregado de forma incorrecta y directa al repositorio. {% comment %} https://github.com/github/github/issues/54684 {% endcomment %}' - - 'Las incidencias no se pueden cerrar si contienen un enlace permanente a un blob del mismo repositorio en el que la ruta es mayor de 255 caracteres. {% comment %} https://github.com/github/github/issues/107731 {% endcomment %}' - - 'Cuando se habilita "Los usuarios pueden buscar en GitHub.com" con GitHub Connect, las incidencias en los repositorios privados e internos no se incluyen en los resultados de la búsqueda de GitHub.com. {% comment %} https://github.com/github/admin-experience/issues/571 {% endcomment %}' - - 'Las alertas de seguridad no se notifican cuando se realiza la inserción en un repositorio en la línea de comandos. {% comment %} https://github.com/github/github/issues/143190 {% endcomment %}' - - 'Cuando un nodo de réplica está sin conexión en una configuración de disponibilidad alta, es posible que {% data variables.product.product_name %} todavía enrute las solicitudes a {% data variables.product.prodname_pages %} al nodo sin conexión, lo que reduce la disponibilidad de {% data variables.product.prodname_pages %} para los usuarios.' diff --git a/translations/es-ES/data/release-notes/enterprise-server/2-20/14.yml b/translations/es-ES/data/release-notes/enterprise-server/2-20/14.yml deleted file mode 100644 index 0229ddd4ee..0000000000 --- a/translations/es-ES/data/release-notes/enterprise-server/2-20/14.yml +++ /dev/null @@ -1,13 +0,0 @@ -date: '2020-08-12' -sections: - bugs: - - 'Se ha resuelto un problema que podía conllevar un uso alto de CPU mientras se generaban las plantillas de configuración del sistema. {% comment %} https://github.com/github/enterprise2/pull/21784, https://github.com/github/enterprise2/pull/21741 {% endcomment %}' - - 'Los cambios recientes a las asignaciones de memoria podían conllevar una degradación en el rendimiento del sistema {% comment %} https://github.com/github/enterprise2/pull/22067 {% endcomment %}' - known_issues: - - 'En una instancia de GitHub Enterprise Server recién configurada sin ningún usuario, un atacante podía crear el primer usuario administrador. {% comment %} https://github.com/github/enterprise2/issues/1889 {% endcomment %}' - - 'Las reglas de cortafuegos personalizadas no se mantienen durante una actualización. {% comment %} https://github.com/github/enterprise2/issues/2823 {% endcomment %}' - - 'Los archivos supervisados de Git LFS [cargados desde la interfaz web](https://github.com/blog/2105-upload-files-to-your-repositories) se agregan de forma incorrecta y directa al repositorio. {% comment %} https://github.com/github/github/issues/54684 {% endcomment %}' - - 'Las incidencias no se pueden cerrar si contienen un enlace permanente a un blob del mismo repositorio en el que la ruta es mayor de 255 caracteres. {% comment %} https://github.com/github/github/issues/107731 {% endcomment %}' - - 'Cuando se habilita "Los usuarios pueden buscar en GitHub.com" con GitHub Connect, las incidencias en los repositorios privados e internos no se incluyen en los resultados de la búsqueda de GitHub.com. {% comment %} https://github.com/github/admin-experience/issues/571 {% endcomment %}' - - 'Las alertas de seguridad no se notifican cuando se realiza la inserción en un repositorio en la línea de comandos. {% comment %} https://github.com/github/github/issues/143190 {% endcomment %}' - - 'Cuando un nodo de réplica está sin conexión en una configuración de disponibilidad alta, es posible que {% data variables.product.product_name %} todavía enrute las solicitudes a {% data variables.product.prodname_pages %} al nodo sin conexión, lo que reduce la disponibilidad de {% data variables.product.prodname_pages %} para los usuarios.' diff --git a/translations/es-ES/data/release-notes/enterprise-server/2-20/15.yml b/translations/es-ES/data/release-notes/enterprise-server/2-20/15.yml deleted file mode 100644 index 01f9c1eed7..0000000000 --- a/translations/es-ES/data/release-notes/enterprise-server/2-20/15.yml +++ /dev/null @@ -1,25 +0,0 @@ -date: '2020-08-26' -sections: - security_fixes: - - >- - {% octicon "alert" aria-label="The alert icon" %} **Critical:** A remote code execution vulnerability was identified in GitHub Pages that could be exploited when building a GitHub Pages site. User-controlled configuration of the underlying parsers used by GitHub Pages were not sufficiently restricted and made it possible to execute commands on the GitHub Enterprise Server instance. To exploit this vulnerability, an attacker would need permission to create and build a GitHub Pages site on the GitHub Enterprise Server instance. This vulnerability affected all versions of GitHub Enterprise Server. The underlying issues contributing to this vulnerability were identified both internally and through the GitHub Security Bug Bounty program. We have issued CVE-2020-10518. {% comment %} https://github.com/github/pages/pull/2883, https://github.com/github/pages/pull/2902, https://github.com/github/pages/pull/2894, https://github.com/github/pages/pull/2877, https://github.com/github/pages-gem/pull/700, - https://github.com/github/pages/pull/2890, https://github.com/github/pages/pull/2898, https://github.com/github/pages/pull/2909, https://github.com/github/pages/pull/2891, https://github.com/github/pages/pull/2884, https://github.com/github/pages/pull/2889 {% endcomment %} - - '**MEDIUM:** An improper access control vulnerability was identified that allowed authenticated users of the instance to determine the names of unauthorized private repositories given their numerical IDs. This vulnerability did not allow unauthorized access to any repository content besides the name. This vulnerability affected all versions of GitHub Enterprise Server prior to 2.22 and has been assigned [CVE-2020-10517](https://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2020-10517). The vulnerability was reported via the [GitHub Bug Bounty program](https://bounty.github.com). {% comment %} https://github.com/github/github/pull/151987, https://github.com/github/github/pull/151713 {% endcomment %}' - - 'Packages have been updated to the latest security versions. {% comment %} https://github.com/github/enterprise2/pull/21852, https://github.com/github/enterprise2/pull/21828, https://github.com/github/enterprise2/pull/22153, https://github.com/github/enterprise2/pull/21920, https://github.com/github/enterprise2/pull/22215, https://github.com/github/enterprise2/pull/22190 {% endcomment %}' - bugs: - - 'A message was not logged when the ghe-config-apply process had finished running ghe-es-auto-expand. {% comment %} https://github.com/github/enterprise2/pull/22177, https://github.com/github/enterprise2/pull/22171 {% endcomment %}' - - 'Excessive logging to the `syslog` file could occur on high-availability replicas if the primary appliance is unavailable. {% comment %} https://github.com/github/enterprise2/pull/22267, https://github.com/github/enterprise2/pull/22124 {% endcomment %}' - - "Database re-seeding on a replica could fail with an error: `Got packet bigger than 'max_allowed_packet'` {% comment %} https://github.com/github/enterprise2/pull/22321, https://github.com/github/enterprise2/pull/20063 {% endcomment %}" - - 'In some cases duplicate user data could cause a 500 error while running the ghe-license-usage script. {% comment %} https://github.com/github/github/pull/152638 {% endcomment %}' - changes: - - 'In a high availability or geo-replication configuration, replica instances would exit maintenance mode when ghe-config-apply ran. {% comment %} https://github.com/github/enterprise2/pull/21776, https://github.com/github/enterprise2/pull/21440 {% endcomment %}' - - "We've added support for the R5a and R5n AWS instance types. {% comment %} https://github.com/github/enterprise2/pull/21902, https://github.com/github/enterprise2/pull/21173 {% endcomment %}" - - 'Removed the license seat count information on the administrative SSH MOTD due to a performance issue impacting GitHub Enterprise Server clusters. {% comment %} https://github.com/github/enterprise2/pull/21993, https://github.com/github/enterprise2/pull/21870 {% endcomment %}' - known_issues: - - 'On a freshly set up GitHub Enterprise Server without any users, an attacker could create the first admin user. {% comment %} https://github.com/github/enterprise2/issues/1889 {% endcomment %}' - - 'Custom firewall rules are not maintained during an upgrade. {% comment %} https://github.com/github/enterprise2/issues/2823 {% endcomment %}' - - '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. {% comment %} https://github.com/github/github/issues/54684 {% endcomment %}' - - '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. {% comment %} https://github.com/github/github/issues/107731 {% endcomment %}' - - '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. {% comment %} https://github.com/github/admin-experience/issues/571 {% endcomment %}' - - 'Security alerts are not reported when pushing to a repository on the command line. {% comment %} https://github.com/github/github/issues/143190 {% endcomment %}' - - '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.' diff --git a/translations/es-ES/data/release-notes/enterprise-server/2-20/16.yml b/translations/es-ES/data/release-notes/enterprise-server/2-20/16.yml deleted file mode 100644 index c3085af749..0000000000 --- a/translations/es-ES/data/release-notes/enterprise-server/2-20/16.yml +++ /dev/null @@ -1,13 +0,0 @@ -date: '2020-09-08' -sections: - bugs: - - 'Una revisión del estado del servicio provocaba un crecimiento de la sesión que resultaba en el agotamiento del inode del sistema de archivos. {% comment %} https://github.com/github/enterprise2/pull/22480, https://github.com/github/enterprise2/pull/22475 {% endcomment %}' - - 'La realización de mejoras utilizando hotpatches podía fallar con un error de tipo `''libdbi1'' was not found` {% comment %} https://github.com/github/enterprise2/pull/22558, https://github.com/github/enterprise2/pull/22552 {% endcomment %}' - known_issues: - - "En una instancia de GitHub\_Enterprise Server recién configurada sin ningún usuario, un atacante podría crear el primer usuario administrador. {% comment %} https://github.com/github/enterprise2/issues/1889 {% endcomment %}" - - 'Las reglas de cortafuegos personalizadas no se mantienen durante una actualización. {% comment %} https://github.com/github/enterprise2/issues/2823 {% endcomment %}' - - 'Los archivos supervisados de Git LFS [cargados desde la interface web](https://github.com/blog/2105-upload-files-to-your-repositories) se han agregado de forma incorrecta y directa al repositorio. {% comment %} https://github.com/github/github/issues/54684 {% endcomment %}' - - "Las incidencias no se pueden cerrar si contienen un enlace permanente a un blob del mismo repositorio en el que la ruta es mayor de 255\_caracteres. {% comment %} https://github.com/github/github/issues/107731 {% endcomment %}" - - 'Cuando se habilita "Los usuarios pueden buscar en GitHub.com" con GitHub Connect, las incidencias en los repositorios privados e internos no se incluyen en los resultados de la búsqueda de GitHub.com. {% comment %} https://github.com/github/admin-experience/issues/571 {% endcomment %}' - - 'Las alertas de seguridad no se notifican cuando se realiza la inserción en un repositorio en la línea de comandos. {% comment %} https://github.com/github/github/issues/143190 {% endcomment %}' - - 'Cuando un nodo de réplica está sin conexión en una configuración de disponibilidad alta, es posible que {% data variables.product.product_name %} enrute las solicitudes a {% data variables.product.prodname_pages %} al nodo sin conexión, lo que reduce la disponibilidad de {% data variables.product.prodname_pages %} para los usuarios.' diff --git a/translations/es-ES/data/release-notes/enterprise-server/2-20/17.yml b/translations/es-ES/data/release-notes/enterprise-server/2-20/17.yml deleted file mode 100644 index c7bab047f0..0000000000 --- a/translations/es-ES/data/release-notes/enterprise-server/2-20/17.yml +++ /dev/null @@ -1,13 +0,0 @@ -date: '2020-09-23' -sections: - security_fixes: - - '**MEDIO**: ImageMagick se ha actualizado para abordar [DSA-4715-1](https://www.debian.org/security/2020/dsa-4715). {% comment %} https://github.com/github/enterprise2/pull/22625, https://github.com/github/enterprise2/pull/22610 {% endcomment %}' - - 'Los paquetes se han actualizado a las versiones de seguridad más recientes. {% comment %} https://github.com/github/enterprise2/pull/22601, https://github.com/github/enterprise2/pull/22592, https://github.com/github/enterprise2/pull/22605, https://github.com/github/enterprise2/pull/22426, https://github.com/github/enterprise2/pull/22718, https://github.com/github/enterprise2/pull/22699 {% endcomment %}' - known_issues: - - 'En una instancia de GitHub Enterprise Server recién configurada sin ningún usuario, un atacante podría crear el primer usuario administrador. {% comment %} https://github.com/github/enterprise2/issues/1889 {% endcomment %}' - - 'Las reglas de firewall personalizadas no se mantienen durante una actualización. {% comment %} https://github.com/github/enterprise2/issues/2823 {% endcomment %}' - - 'Los archivos supervisados de Git LFS [cargados a través de la interfaz web](https://github.com/blog/2105-upload-files-to-your-repositories) se agregaron incorrecta y directamente al repositorio. {% comment %} https://github.com/github/github/issues/54684 {% endcomment %}' - - 'Las incidencias no se pueden cerrar si contienen un vínculo permanente a un blob en el mismo repositorio en el que la ruta de acceso del archivo tiene más de 255 caracteres. {% comment %} https://github.com/github/github/issues/107731 {% endcomment %}' - - 'Cuando se habilita "Los usuarios pueden buscar en GitHub.com" con GitHub Connect, las incidencias en los repositorios privados e internos no se incluyen en los resultados de la búsqueda de GitHub.com. {% comment %} https://github.com/github/admin-experience/issues/571 {% endcomment %}' - - 'Las alertas de seguridad no se notifican cuando se realiza la inserción en un repositorio en la línea de comandos. {% comment %} https://github.com/github/github/issues/143190 {% endcomment %}' - - 'Cuando un nodo de réplica está sin conexión en una configuración de alta disponibilidad, {% data variables.product.product_name %} aún se pueden enrutar solicitudes de {% data variables.product.prodname_pages %} al nodo sin conexión, lo que reduce la disponibilidad de {% data variables.product.prodname_pages %} para los usuarios.' diff --git a/translations/es-ES/data/release-notes/enterprise-server/2-20/18.yml b/translations/es-ES/data/release-notes/enterprise-server/2-20/18.yml deleted file mode 100644 index 85669314cd..0000000000 --- a/translations/es-ES/data/release-notes/enterprise-server/2-20/18.yml +++ /dev/null @@ -1,26 +0,0 @@ -date: '2020-10-09' -sections: - security_fixes: - - 'Un usuario cuyo nombre de usuario del directorio LDAP se estandariza con el inicio de sesión de una cuenta GHES existente podría autenticarse en la cuenta existente. {% comment %} https://github.com/github/github/pull/156518, https://github.com/github/github/pull/155512 {% endcomment %}' - - 'Los paquetes se han actualizado a las versiones de seguridad más recientes. {% comment %} https://github.com/github/enterprise2/pull/22910, https://github.com/github/enterprise2/pull/22878 {% endcomment %}' - bugs: - - 'El menú desplegable Formato de NameID en la consola de administración se restablecería a "sin especificar" después de establecerlo en "persistente". {% comment %} https://github.com/github/enterprise2/pull/22403, https://github.com/github/enterprise2/pull/22331, https://github.com/github/enterprise2/issues/13446 {% endcomment %}' - - 'Guardar la configuración a través de la [consola de administración](/admin/configuration/accessing-the-management-console) anexaría una nueva línea a los archivos [certificado y clave TLS/SSL](/admin/configuration/configuring-tls) que activaron la recarga innecesaria de algunos servicios. {% comment %} https://github.com/github/enterprise2/pull/22607, https://github.com/github/enterprise2/pull/22540 {% endcomment %}' - - 'Los registros del sistema para Dependency Graph no estaban rotando, lo que permitía un crecimiento ilimitado del almacenamiento. {% comment %} https://github.com/github/enterprise2/pull/22765, https://github.com/github/enterprise2/pull/22733 {% endcomment %}' - - 'Los vínculos a los avisos de seguridad de GitHub utilizarían una dirección URL con el nombre de host de la instancia de GitHub Enterprise Server en lugar de GitHub.com, lo que dirigiría al usuario a una dirección URL inexistente. {% comment %} https://github.com/github/github/pull/153444, https://github.com/github/github/pull/151301 {% endcomment %}' - - 'Al importar un repositorio con "ghe-migrator", podría ocurrir una excepción inesperada cuando hay datos inconsistentes. {% comment %} https://github.com/github/github/pull/153848, https://github.com/github/github/pull/151552 {% endcomment %}' - - 'Al usar "ghe-migrator" para importar solicitudes de revisión PR, los registros asociados con los usuarios eliminados generarían registros extraños en la base de datos. {% comment %} https://github.com/github/github/pull/154958, https://github.com/github/github/pull/153169 {% endcomment %}' - - 'Al importar usuarios con "ghe-migrator", se produciría un error de "Correos electrónicos no válidos" si la dirección de correo electrónico generada por el sistema tuviera más de 100 caracteres. {% comment %} https://github.com/github/github/pull/155112, https://github.com/github/github/pull/152418 {% endcomment %}' - - 'El registro de la actividad de webhook podría usar grandes cantidades de espacio en disco y hacer que el disco raíz se llenara. {% comment %} https://github.com/github/github/pull/155655, https://github.com/github/github/pull/154100 {% endcomment %}' - changes: - - 'Se agrega soporte para el tipo de instancia AWS EC2 "m5.16xlarge". {% comment %} https://github.com/github/enterprise2/pull/22500, https://github.com/github/enterprise2/pull/22473 {% endcomment %}' - - 'Quita el requisito de huellas digitales SSH en los archivos "ghe-migrator", ya que siempre se puede calcular. {% comment %} https://github.com/github/github/pull/156944, https://github.com/github/github/pull/155387 {% endcomment %}' - - 'Los manifiestos de la aplicación de GitHub ahora incluyen el campo "request_oauth_on_install". {% comment %} https://github.com/github/github/pull/156996, https://github.com/github/github/pull/155010, https://github.com/github/ecosystem-apps/issues/1055 {% endcomment %}' - known_issues: - - 'En una instancia de GitHub Enterprise Server recién configurada sin ningún usuario, un atacante podría crear el primer usuario administrador. {% comment %} https://github.com/github/enterprise2/issues/1889 {% endcomment %}' - - 'Las reglas de firewall personalizadas no se mantienen durante una actualización. {% comment %} https://github.com/github/enterprise2/issues/2823 {% endcomment %}' - - 'Los archivos supervisados de Git LFS [cargados a través de la interfaz web](https://github.com/blog/2105-upload-files-to-your-repositories) se agregaron incorrecta y directamente al repositorio. {% comment %} https://github.com/github/github/issues/54684 {% endcomment %}' - - 'Las incidencias no se pueden cerrar si contienen un vínculo permanente a un blob en el mismo repositorio en el que la ruta de acceso del archivo tiene más de 255 caracteres. {% comment %} https://github.com/github/github/issues/107731 {% endcomment %}' - - 'Cuando se habilita "Los usuarios pueden buscar en GitHub.com" con GitHub Connect, las incidencias en los repositorios privados e internos no se incluyen en los resultados de la búsqueda de GitHub.com. {% comment %} https://github.com/github/admin-experience/issues/571 {% endcomment %}' - - 'Las alertas de seguridad no se notifican cuando se realiza la inserción en un repositorio en la línea de comandos. {% comment %} https://github.com/github/github/issues/143190 {% endcomment %}' - - 'Cuando un nodo de réplica está sin conexión en una configuración de alta disponibilidad, {% data variables.product.product_name %} aún se pueden enrutar solicitudes de {% data variables.product.prodname_pages %} al nodo sin conexión, lo que reduce la disponibilidad de {% data variables.product.prodname_pages %} para los usuarios.' diff --git a/translations/es-ES/data/release-notes/enterprise-server/2-20/19.yml b/translations/es-ES/data/release-notes/enterprise-server/2-20/19.yml deleted file mode 100644 index f355603577..0000000000 --- a/translations/es-ES/data/release-notes/enterprise-server/2-20/19.yml +++ /dev/null @@ -1,14 +0,0 @@ -date: '2020-10-20' -sections: - security_fixes: - - 'Los paquetes se han actualizado a sus últimas versiones de seguridad. {% comment %} https://github.com/github/enterprise2/pull/23095, https://github.com/github/enterprise2/pull/23081 {% endcomment %}' - bugs: - - 'El mensaje "Política de confirmación para el requisito bifactorial" en cuentas empresariales era incorrecto. {% comment %} https://github.com/github/github/pull/158737 {% endcomment %}' - known_issues: - - "En una instancia de GitHub\_Enterprise Server recién configurada sin ningún usuario, un atacante podría crear el primer usuario administrador. {% comment %} https://github.com/github/enterprise2/issues/1889 {% endcomment %}" - - 'Las reglas de cortafuegos personalizadas no se mantienen durante una actualización. {% comment %} https://github.com/github/enterprise2/issues/2823 {% endcomment %}' - - 'Los archivos supervisados de Git LFS [cargados desde la interfaz web](https://github.com/blog/2105-upload-files-to-your-repositories) se agregan de forma incorrecta y directa al repositorio. {% comment %} https://github.com/github/github/issues/54684 {% endcomment %}' - - "Las incidencias no se pueden cerrar si contienen un enlace permanente a un blob del mismo repositorio en el que la ruta es mayor de 255\_caracteres. {% comment %} https://github.com/github/github/issues/107731 {% endcomment %}" - - 'Cuando se habilita "Los usuarios pueden buscar en GitHub.com" con GitHub Connect, las incidencias en los repositorios privados e internos no se incluyen en los resultados de la búsqueda de GitHub.com. {% comment %} https://github.com/github/admin-experience/issues/571 {% endcomment %}' - - 'Las alertas de seguridad no se notifican cuando se realiza la inserción en un repositorio en la línea de comandos. {% comment %} https://github.com/github/github/issues/143190 {% endcomment %}' - - 'Cuando un nodo de réplica está sin conexión en una configuración de disponibilidad alta, es posible que {% data variables.product.product_name %} enrute las solicitudes a {% data variables.product.prodname_pages %} al nodo sin conexión, lo que reduce la disponibilidad de {% data variables.product.prodname_pages %} para los usuarios.' diff --git a/translations/es-ES/data/release-notes/enterprise-server/2-20/2.yml b/translations/es-ES/data/release-notes/enterprise-server/2-20/2.yml deleted file mode 100644 index ac8baccbb4..0000000000 --- a/translations/es-ES/data/release-notes/enterprise-server/2-20/2.yml +++ /dev/null @@ -1,28 +0,0 @@ -date: '2020-03-10' -sections: - security_fixes: - - 'Los paquetes se han actualizado a sus últimas versiones de seguridad. {% comment %} https://github.com/github/enterprise2/pull/19204, https://github.com/github/enterprise2/pull/19187 {% endcomment %}' - bugs: - - 'En algunos casos, las entradas de bitácora reenviadas, principalmente para audit.log, se truncaban. {% comment %} https://github.com/github/enterprise2/pull/19244, https://github.com/github/enterprise2/pull/19192, https://github.com/github/enterprise2/issues/16655 {% endcomment %}' - - 'La utilidad de línea de comandos `ghe-license-check` devolvía un error de "Invalid license file" para algunas licencias válidas, lo cual provocaba que fallaran los cambios de configuración. {% comment %} https://github.com/github/enterprise2/pull/19249, https://github.com/github/enterprise2/pull/19185, https://github.zendesk.com/agent/tickets/549903 {% endcomment %}' - - 'El syslog no reenviaba las bitácoras de excepciones de Alambic. {% comment %} https://github.com/github/enterprise2/pull/19263, https://github.com/github/enterprise2/pull/19123, https://github.com/github/enterprise2/issues/18734 {% endcomment %}' - - 'El [evento `org_block`](https://developer.github.com/v3/activity/events/types/#orgblockevent) estaba disponible pero aparecía en las GitHub Apps en GitHub Enterprise Server. {% comment %} https://github.com/github/github/pull/136227, https://github.com/github/github/pull/135640, https://github.com/github/ecosystem-apps/issues/693 {% endcomment %}' - - 'Las respuestas de consulta de GraphQL a veces devolvían identificadores de nodo que no coincidían para los objetos de `ProtectedBranch` {% comment %} https://github.com/github/github/pull/136376, https://github.com/github/github/pull/136214, https://github.com/github/github/issues/135407 {% endcomment %}' - - 'La credencial de GtHub App que utilizaba GitHub Connect no se actualizaba inmediatamente después de su vencimiento. {% comment %} https://github.com/github/github/pull/136384, https://github.com/github/github/pull/136259 {% endcomment %}' - - 'Al dejar comentarios de respuesta en un comentario de una solicitud de cambios se creaba intermitentemente una revisión de solicitud de cambios pendiente. {% comment %} https://github.com/github/github/pull/136454, https://github.com/github/github/pull/133697, https://github.com/github/github/issues/127401 {% endcomment %}' - - 'Al utilizar ghe-migrator o exportar desde GitHub.com, la exportación fallaba silenciosamente al exportar adjuntos que no fueran imágenes. {% comment %} https://github.com/github/github/pull/136487, https://github.com/github/github/pull/134524, https://github.com/github/github/issues/134358 {% endcomment %}' - - 'Los ganchos de pre-recepción devolvían un error 500 en la IU web cuando se encontraban caracteres UTF-8. {% comment %} https://github.com/github/github/pull/136699, https://github.com/github/github/pull/136014, https://github.com/github/github/issues/133501 {% endcomment %}' - changes: - - 'La utilidad de línea de comandos ` ghe-license-usage ` incluye una opción `--unencrypted` nueva para proporcionar visibilidad en el archivo de uso de licencia exportado. {% comment %} https://github.com/github/github/pull/136134, https://github.com/github/github/pull/136000 {% endcomment %}' - known_issues: - - "En una instancia de GitHub\_Enterprise Server recién configurada sin ningún usuario, un atacante podría crear el primer usuario administrador. {% comment %} https://github.com/github/enterprise2/issues/1889 {% endcomment %}" - - 'Las reglas de cortafuegos personalizadas no se mantienen durante una actualización. {% comment %} https://github.com/github/enterprise2/issues/2823 {% endcomment %}' - - 'Los archivos supervisados de Git LFS [cargados desde la interfaz web](https://github.com/blog/2105-upload-files-to-your-repositories) se agregan de forma incorrecta y directa al repositorio. {% comment %} https://github.com/github/github/issues/54684 {% endcomment %}' - - "Las incidencias no se pueden cerrar si contienen un enlace permanente a un blob del mismo repositorio en el que la ruta es mayor de 255\_caracteres. {% comment %} https://github.com/github/github/issues/107731 {% endcomment %}" - - 'Al enviar cambios a un gist, se podía desencadenar una excepción durante el gancho posterior a la recepción. {% comment %} https://github.com/github/github/issues/129091 {% endcomment %}' - - 'Las mejoras y actualizaciones de configuración producen errores si se personalizan las configuraciones en segundo plano de los roles de trabajo. {% comment %} https://github.com/github/enterprise2/issues/19119, {% endcomment %}' - - 'Cuando se habilita "Los usuarios pueden buscar en GitHub.com" con GitHub Connect, las incidencias en los repositorios privados e internos no se incluyen en los resultados de la búsqueda de GitHub.com. {% comment %} https://github.com/github/admin-experience/issues/571 {% endcomment %}' - - 'Al actualizar desde versiones anteriores, es posible que no se generen roles de trabajo en segundo plano, lo que impide características esenciales como la combinación de solicitudes de incorporación de cambios. (Actualizado el 07-04-2020) {% comment %} https://github.com/github/enterprise2/issues/19232 {% endcomment %}' - - 'Las alertas de seguridad no se notifican cuando se envían cambios a un repositorio en la línea de comandos. (Actualizado el 23-06-2020) {% comment %} https://github.com/github/github/issues/143190 {% endcomment %}' - - 'El gráfico de dependencias no detecta las dependencias cuando se implementan en una configuración de clúster con múltiples nodos de Redis. (Actualizado el 30-06-2020) {% comment %} https://github.com/github/dependency-graph/issues/81 {% endcomment %}' - - 'Cuando un nodo de réplica está sin conexión en una configuración de disponibilidad alta, es posible que {% data variables.product.product_name %} enrute las solicitudes a {% data variables.product.prodname_pages %} al nodo sin conexión, lo que reduce la disponibilidad de {% data variables.product.prodname_pages %} para los usuarios.' diff --git a/translations/es-ES/data/release-notes/enterprise-server/2-20/20.yml b/translations/es-ES/data/release-notes/enterprise-server/2-20/20.yml deleted file mode 100644 index 093015ac70..0000000000 --- a/translations/es-ES/data/release-notes/enterprise-server/2-20/20.yml +++ /dev/null @@ -1,16 +0,0 @@ -date: '2020-11-03' -sections: - security_fixes: - - '**MEDIA:** El uso elevado de CPU puede desencadenarse debido a una solicitud hecha específicamente al puente de SVN, lo cual resulta en una negación del servicio (DoS). {% comment %} https://github.com/github/slumlord/pull/1003, https://github.com/github/slumlord/pull/1000 {% endcomment %}' - - "**BAJA:** La validación incorrecta de un token provocaba una entropía reducida para la coincidencia de tokens durante la autenticación. El análisis muestra que, en la práctica, en este caso no hay riesgos de seguridad significativos. {% comment %} https://github.com/github/github/pull/159453, https://github.com/github/github/pull/159193 {% endcomment %}" - - 'Los paquetes se actualizaron a las últimas versiones de seguridad. {% comment %} https://github.com/github/enterprise2/pull/23538, https://github.com/github/enterprise2/pull/23171, https://github.com/github/enterprise2/pull/23691, https://github.com/github/enterprise2/pull/23677 {% endcomment %}' - bugs: - - 'Los usuarios suspendidos se incluían en la lista de usuarios sugeridos, posiblemente ocultando a los usuarios que no se habían suspendido. {% comment %} https://github.com/github/github/pull/159809, https://github.com/github/github/pull/140563, https://github.com/github/github/pull/142146 {% endcomment %}' - known_issues: - - 'En una instancia de GitHub Enterprise Server recién configurada sin ningún usuario, un atacante podría crear el primer usuario administrador. {% comment %} https://github.com/github/enterprise2/issues/1889 {% endcomment %}' - - 'Las reglas de cortafuegos personalizadas no se mantienen durante una actualización. {% comment %} https://github.com/github/enterprise2/issues/2823 {% endcomment %}' - - 'Los archivos supervisados de Git LFS [cargados desde la interface web](https://github.com/blog/2105-upload-files-to-your-repositories) se han agregado de forma incorrecta y directa al repositorio. {% comment %} https://github.com/github/github/issues/54684 {% endcomment %}' - - 'Las incidencias no se pueden cerrar si contienen un enlace permanente a un blob del mismo repositorio en el que la ruta es mayor de 255 caracteres. {% comment %} https://github.com/github/github/issues/107731 {% endcomment %}' - - 'Cuando se habilita "Los usuarios pueden buscar en GitHub.com" con GitHub Connect, las incidencias en los repositorios privados e internos no se incluyen en los resultados de la búsqueda de GitHub.com. {% comment %} https://github.com/github/admin-experience/issues/571 {% endcomment %}' - - 'Las alertas de seguridad no se notifican cuando se realiza la inserción en un repositorio en la línea de comandos. {% comment %} https://github.com/github/github/issues/143190 {% endcomment %}' - - 'Cuando un nodo de réplica está sin conexión en una configuración de disponibilidad alta, es posible que {% data variables.product.product_name %} enrute las solicitudes a {% data variables.product.prodname_pages %} al nodo sin conexión, lo que reduce la disponibilidad de {% data variables.product.prodname_pages %} para los usuarios.' diff --git a/translations/es-ES/data/release-notes/enterprise-server/2-20/21.yml b/translations/es-ES/data/release-notes/enterprise-server/2-20/21.yml deleted file mode 100644 index 0181aa02b5..0000000000 --- a/translations/es-ES/data/release-notes/enterprise-server/2-20/21.yml +++ /dev/null @@ -1,15 +0,0 @@ -date: '2020-11-17' -sections: - security_fixes: - - 'Los paquetes se han actualizado a las versiones de seguridad más recientes. {% comment %} https://github.com/github/enterprise2/pull/23843, https://github.com/github/enterprise2/pull/23712 {% endcomment %}' - bugs: - - 'Los registros de babeld no tenían un separador entre los segundos y microsegundos. {% comment %} https://github.com/github/babeld/pull/1004, https://github.com/github/babeld/pull/1002 {% endcomment %}' - - 'Cuando la directiva "Cambio de visibilidad del repositorio" de las cuentas empresariales se establecía en "Habilitada", los propietarios de las organizaciones no podían cambiar la visibilidad de los repositorios dentro de la organización. {% comment %} https://github.com/github/github/pull/160922, https://github.com/github/github/pull/160773 {% endcomment %}' - known_issues: - - 'En una instancia de GitHub Enterprise Server recién configurada sin ningún usuario, un atacante podría crear el primer usuario administrador. {% comment %} https://github.com/github/enterprise2/issues/1889 {% endcomment %}' - - 'Las reglas de firewall personalizadas no se mantienen durante una actualización. {% comment %} https://github.com/github/enterprise2/issues/2823 {% endcomment %}' - - 'Los archivos supervisados de Git LFS [cargados a través de la interfaz web](https://github.com/blog/2105-upload-files-to-your-repositories) se agregaron incorrecta y directamente al repositorio. {% comment %} https://github.com/github/github/issues/54684 {% endcomment %}' - - 'Las incidencias no se pueden cerrar si contienen un vínculo permanente a un blob en el mismo repositorio en el que la ruta de acceso del archivo tiene más de 255 caracteres. {% comment %} https://github.com/github/github/issues/107731 {% endcomment %}' - - 'Cuando se habilita "Los usuarios pueden buscar en GitHub.com" con GitHub Connect, las incidencias en los repositorios privados e internos no se incluyen en los resultados de la búsqueda de GitHub.com. {% comment %} https://github.com/github/admin-experience/issues/571 {% endcomment %}' - - 'Las alertas de seguridad no se notifican cuando se realiza la inserción en un repositorio en la línea de comandos. {% comment %} https://github.com/github/github/issues/143190 {% endcomment %}' - - 'Cuando un nodo de réplica está sin conexión en una configuración de alta disponibilidad, {% data variables.product.product_name %} aún se pueden enrutar solicitudes de {% data variables.product.prodname_pages %} al nodo sin conexión, lo que reduce la disponibilidad de {% data variables.product.prodname_pages %} para los usuarios.' diff --git a/translations/es-ES/data/release-notes/enterprise-server/2-20/22.yml b/translations/es-ES/data/release-notes/enterprise-server/2-20/22.yml deleted file mode 100644 index c7d963e6bf..0000000000 --- a/translations/es-ES/data/release-notes/enterprise-server/2-20/22.yml +++ /dev/null @@ -1,19 +0,0 @@ -date: '2020-12-03' -sections: - bugs: - - 'El servicio de autorización se detectaba como incorrecto debido a la condición de carrera en bootstrap, lo cual ocasionaba que se reiniciara el servicio. {% comment %} https://github.com/github/authzd/pull/1279 {% endcomment %}' - - 'Un comportamiento subyacente estaba causando que un servicio estuviera no disponible durante el proceso de mejora mediante un hotpatch. {% comment %} https://github.com/github/enterprise2/pull/24053, https://github.com/github/enterprise2/issues/23947 {% endcomment %}' - - 'Un subconjunto de certificados SSL que reenviaban bitácoras no se estaba aplicando correctamente. {% comment %} https://github.com/github/enterprise2/pull/24112, https://github.com/github/enterprise2/pull/23981 {% endcomment %}' - - 'Se enviaron notificaciones de correo electrónico para suspender usuarios cuando se eliminaban de un equipo o de una organización. {% comment %} https://github.com/github/github/pull/163107, https://github.com/github/github/pull/162742 {% endcomment %}' - - 'La forma en la que se aplicaban los certificados SSH entre las organizaciones y los negocios no era uniforme. {% comment %} https://github.com/github/github/pull/163429, https://github.com/github/github/pull/159538, https://github.com/github/authentication/issues/115 {% endcomment %}' - - 'Cuando se limitaba la tarifa de una cuenta debido al uso incorrecto de contraseñas, se podía bloquear hasta 24 horas. {% comment %} https://github.com/github/github/pull/163456, https://github.com/github/github/pull/162938, https://github.com/github/github-ds/pull/51 {% endcomment %}' - - 'La sincronización de solicitudes de cambios en los repositorios con muchas referencias podía provocar que se retrasaran las colas de los roles de trabajo. {% comment %} https://github.com/github/github/pull/163576, https://github.com/github/github/pull/163142 {% endcomment %}' - - 'Cuando se iniciaba sesión después de intentar visitar una página específica, se enviaba a los usuarios a la página de inicio en vez de al destino previsto. {% comment %} https://github.com/github/github/pull/163785, https://github.com/github/github/pull/163579, https://github.com/github/github/pull/154117, https://github.com/github/ecosystem-apps/issues/1076 {% endcomment %}' - known_issues: - - "En una instancia de GitHub\_Enterprise Server recién configurada sin ningún usuario, un atacante podría crear el primer usuario administrador. {% comment %} https://github.com/github/enterprise2/issues/1889 {% endcomment %}" - - 'Las reglas de cortafuegos personalizadas no se mantienen durante una actualización. {% comment %} https://github.com/github/enterprise2/issues/2823 {% endcomment %}' - - 'Los archivos supervisados de Git LFS [cargados desde la interfaz web](https://github.com/blog/2105-upload-files-to-your-repositories) se agregan de forma incorrecta y directa al repositorio. {% comment %} https://github.com/github/github/issues/54684 {% endcomment %}' - - "Las incidencias no se pueden cerrar si contienen un enlace permanente a un blob del mismo repositorio en el que la ruta es mayor de 255\_caracteres. {% comment %} https://github.com/github/github/issues/107731 {% endcomment %}" - - 'Cuando se habilita "Los usuarios pueden buscar en GitHub.com" con GitHub Connect, las incidencias en los repositorios privados e internos no se incluyen en los resultados de la búsqueda de GitHub.com. {% comment %} https://github.com/github/admin-experience/issues/571 {% endcomment %}' - - 'Las alertas de seguridad no se notifican cuando se realiza la inserción en un repositorio en la línea de comandos. {% comment %} https://github.com/github/github/issues/143190 {% endcomment %}' - - 'Cuando un nodo de réplica está sin conexión en una configuración de disponibilidad alta, es posible que {% data variables.product.product_name %} enrute las solicitudes a {% data variables.product.prodname_pages %} al nodo sin conexión, lo que reduce la disponibilidad de {% data variables.product.prodname_pages %} para los usuarios.' diff --git a/translations/es-ES/data/release-notes/enterprise-server/2-20/23.yml b/translations/es-ES/data/release-notes/enterprise-server/2-20/23.yml deleted file mode 100644 index 4f9a8918ff..0000000000 --- a/translations/es-ES/data/release-notes/enterprise-server/2-20/23.yml +++ /dev/null @@ -1,13 +0,0 @@ -date: '2020-12-17' -sections: - security_fixes: - - '**BAJO:** El uso elevado de CPU podría desencadenarse por una solicitud especialmente diseñada al puente SVN, lo cual da lugar a una denegación de servicio (DoS). {% comment %} https://github.com/github/slumlord/pull/1020, https://github.com/github/slumlord/pull/1017 {% endcomment %}' - - 'Los paquetes se han actualizado a las versiones de seguridad más recientes. {% comment %} https://github.com/github/enterprise2/pull/24351, https://github.com/github/enterprise2/pull/23866 {% endcomment %}' - known_issues: - - 'En una instancia de GitHub Enterprise Server recién configurada sin ningún usuario, un atacante podría crear el primer usuario administrador. {% comment %} https://github.com/github/enterprise2/issues/1889 {% endcomment %}' - - 'Las reglas de firewall personalizadas no se mantienen durante una actualización. {% comment %} https://github.com/github/enterprise2/issues/2823 {% endcomment %}' - - 'Los archivos supervisados de Git LFS [cargados a través de la interfaz web](https://github.com/blog/2105-upload-files-to-your-repositories) se agregaron incorrecta y directamente al repositorio. {% comment %} https://github.com/github/github/issues/54684 {% endcomment %}' - - 'Las incidencias no se pueden cerrar si contienen un vínculo permanente a un blob en el mismo repositorio en el que la ruta de acceso del archivo tiene más de 255 caracteres. {% comment %} https://github.com/github/github/issues/107731 {% endcomment %}' - - 'Cuando se habilita "Los usuarios pueden buscar en GitHub.com" con GitHub Connect, las incidencias en los repositorios privados e internos no se incluyen en los resultados de la búsqueda de GitHub.com. {% comment %} https://github.com/github/admin-experience/issues/571 {% endcomment %}' - - 'Las alertas de seguridad no se notifican cuando se realiza la inserción en un repositorio en la línea de comandos. {% comment %} https://github.com/github/github/issues/143190 {% endcomment %}' - - 'Cuando un nodo de réplica está sin conexión en una configuración de alta disponibilidad, {% data variables.product.product_name %} aún se pueden enrutar solicitudes de {% data variables.product.prodname_pages %} al nodo sin conexión, lo que reduce la disponibilidad de {% data variables.product.prodname_pages %} para los usuarios.' diff --git a/translations/es-ES/data/release-notes/enterprise-server/2-20/24.yml b/translations/es-ES/data/release-notes/enterprise-server/2-20/24.yml deleted file mode 100644 index e859e36717..0000000000 --- a/translations/es-ES/data/release-notes/enterprise-server/2-20/24.yml +++ /dev/null @@ -1,28 +0,0 @@ -date: '2021-03-02' -sections: - security_fixes: - - '**ALTO:** Se identificó una vulnerabilidad de control de acceso inadecuado en GitHub Enterprise Server que permitía a los usuarios autenticados de la instancia obtener acceso de escritura a repositorios no autorizados a través de solicitud de incorporación de cambios y solicitudes de API REST diseñadas específicamente. Un atacante necesitaría poder bifurcar el repositorio de destino, una configuración que está deshabilitada de forma predeterminada para los repositorios privados propiedad de la organización. Las protecciones de ramas, como las revisiones de solicitud de incorporación de cambios requeridas o las comprobaciones de estado, evitarían la combinación de confirmaciones no autorizadas sin una revisión o validación adicional. A esta vulnerabilidad se la ha asignado CVE-2021-22861. Este problema se informó a través del [programa de recompensas por errores de GitHub] (https://bounty.github.com).' - - '**ALTO:** Se identificó una vulnerabilidad de control de acceso inadecuado en la API de GraphQL de GitHub Enterprise Server que permitía a los usuarios autenticados de la instancia modificar el permiso de colaboración del mantenedor de una solicitud de incorporación de cambios sin la debida autorización. Al aprovechar esta vulnerabilidad, un atacante podría obtener acceso a las ramas principales de las solicitudes de incorporación de cambios abiertas en los repositorios de los que son responsables del mantenimiento. La bifurcación está deshabilitada de forma predeterminada para los repositorios privados propiedad de la organización y evitaría esta vulnerabilidad. Además, las protecciones de las ramas, como las revisiones de solicitud de incorporación de cambios requeridas o las comprobaciones de estado, evitarían la combinación de confirmaciones no autorizadas sin una revisión o validación adicional. A esta vulnerabilidad se la ha asignado CVE-2021-22863. Este problema se informó a través del [programa de recompensas por errores de GitHub] (https://bounty.github.com).' - - '**ALTO:** Se identificó una vulnerabilidad de ejecución de código remoto en GitHub Enterprise Server que podría aprovecharse al crear un sitio de GitHub Pages. La configuración controlada por el usuario de los analizadores subyacentes utilizados por GitHub Pages no estaba lo suficientemente restringida y permitía ejecutar comandos en la instancia de GitHub Enterprise Server. Para aprovechar esta vulnerabilidad, un atacante necesitaría permiso para crear y construir un sitio de GitHub Pages en la instancia de GitHub Enterprise Server. A esta vulnerabilidad se le asignó CVE-2020-10519 y se informó a través del [programa de recompensas por errores de GitHub] (https://bounty.github.com).' - - '**BAJO:** Una solicitud diseñada especialmente para el puente SVN podría desencadenar una larga espera antes de que se produjera un error y diera lugar a la denegación del servicio (DoS).' - - 'Los paquetes se han actualizado a las versiones de seguridad más recientes.' - bugs: - - 'Un mensaje informativo se registró involuntariamente como un error durante las instantáneas de GitHub Enterprise Backup Utilities, lo que provocó el envío de correos electrónicos innecesarios cuando las copias de seguridad estaban programadas por trabajos cron que escuchan la salida en stderr.' - - 'Al restaurar una copia de seguridad grande, el registro de excepciones relacionado con el agotamiento de la memoria de Redis podría provocar un error en la restauración debido a un disco lleno.' - - 'Al editar una página wiki, un usuario podría experimentar un error 500 al hacer clic en el botón Guardar.' - - 'Una confirmación firmada por S/MIME con un certificado con varios nombres en el nombre alternativo del sujeto se mostraría incorrectamente como "No verificado" en la notificación de confirmación.' - - 'Al usuario suspendido se le enviaron correos electrónicos cuando se agregó a un equipo.' - - 'Al cargar un nuevo archivo de licencia con un número diferente de puestos del archivo de licencia anterior, la diferencia de puestos no se representaba correctamente en la página Configuración -> Licencia de la cuenta empresarial.' - - 'La casilla "Evitar que los administradores del repositorio cambien el acceso de lectura de Git anónimo" disponible en la configuración de la cuenta empresarial no se pudo habilitar o deshabilitar correctamente.' - - 'Durante un año bisiesto, el usuario obtenía una respuesta 404 al intentar ver la actividad de contribución en un lunes.' - changes: - - 'Se agregó compatibilidad con [tipos de instancias de AWS EC2 r5b](https://aws.amazon.com/about-aws/whats-new/2020/12/introducing-new-amazon-ec2-r5b-instances-featuring-60-gbps-of-ebs-bandwidth-and-260K-iops/).' - - 'Se ajustó la priorización de la cola en segundo plano para distribuir los trabajos de manera más uniforme.' - known_issues: - - 'En una instancia de GitHub Enterprise Server recién configurada sin usuarios, un atacante podría crear el primer usuario administrador.' - - 'Las reglas de firewall personalizadas no se mantienen durante una actualización.' - - 'Los archivos supervisados de Git LFS [cargados a través la interfaz web](https://github.com/blog/2105-upload-files-to-your-repositories) se agregaron incorrecta y directamente al repositorio.' - - 'Las incidencias no se pueden cerrar si contienen un vínculo permanente a un blob en el mismo repositorio en el que la ruta de acceso de archivo tiene más de 255 caracteres.' - - 'Cuando se habilita "Los usuarios pueden buscar en GitHub.com" con GitHub Connect, las incidencias en los repositorios privados e internos no se incluyen en los resultados de la búsqueda de GitHub.com.' - - 'Las alertas de seguridad no se notifican cuando se insertan en un repositorio en la línea de comandos.' - - 'Cuando un nodo de réplica está sin conexión en una configuración de alta disponibilidad, {% data variables.product.product_name %} aún se pueden enrutar solicitudes de {% data variables.product.prodname_pages %} al nodo sin conexión, lo que reduce la disponibilidad de {% data variables.product.prodname_pages %} para los usuarios.' diff --git a/translations/es-ES/data/release-notes/enterprise-server/2-20/3.yml b/translations/es-ES/data/release-notes/enterprise-server/2-20/3.yml deleted file mode 100644 index c060b5435b..0000000000 --- a/translations/es-ES/data/release-notes/enterprise-server/2-20/3.yml +++ /dev/null @@ -1,15 +0,0 @@ -date: '2020-03-12' -sections: - bugs: - - 'Las mejoras y actualizaciones de configuración fallaban si se habían personalizado las configuraciones en segundo plano de los roles de trabajo. {% comment %} https://github.com/github/enterprise2/pull/19321, https://github.com/github/enterprise2/pull/19299 {% endcomment %}' - known_issues: - - "En una instancia de GitHub\_Enterprise Server recién configurada sin ningún usuario, un atacante podría crear el primer usuario administrador. {% comment %} https://github.com/github/enterprise2/issues/1889 {% endcomment %}" - - 'Las reglas de cortafuegos personalizadas no se mantienen durante una actualización. {% comment %} https://github.com/github/enterprise2/issues/2823 {% endcomment %}' - - 'Los archivos supervisados de Git LFS [cargados desde la interface web](https://github.com/blog/2105-upload-files-to-your-repositories) se han agregado de forma incorrecta y directa al repositorio. {% comment %} https://github.com/github/github/issues/54684 {% endcomment %}' - - "Las incidencias no se pueden cerrar si contienen un enlace permanente a un blob del mismo repositorio en el que la ruta es mayor de 255\_caracteres. {% comment %} https://github.com/github/github/issues/107731 {% endcomment %}" - - 'Al enviar cambios a un gist, se podría desencadenar una excepción durante el enlace posterior a la recepción. {% comment %} https://github.com/github/github/issues/129091 {% endcomment %}' - - 'Cuando se habilita "Los usuarios pueden buscar en GitHub.com" con GitHub Connect, las incidencias en los repositorios privados e internos no se incluyen en los resultados de la búsqueda de GitHub.com. {% comment %} https://github.com/github/admin-experience/issues/571 {% endcomment %}' - - 'Al actualizar desde versiones anteriores, es posible que no se generen roles de trabajo en segundo plano, lo que impide características esenciales como la combinación de solicitudes de incorporación de cambios. (Actualizado el 07-04-2020) {% comment %} https://github.com/github/enterprise2/issues/19232 {% endcomment %}' - - 'Las alertas de seguridad no se notifican cuando se envían cambios a un repositorio en la línea de comandos. (Actualizado el 23-06-2020) {% comment %} https://github.com/github/github/issues/143190 {% endcomment %}' - - 'El gráfico de dependencias no detecta las dependencias cuando se implementan en una configuración de clúster con múltiples nodos de Redis. (Actualizado el 30-06-2020) {% comment %} https://github.com/github/dependency-graph/issues/81 {% endcomment %}' - - 'Cuando un nodo de réplica está sin conexión en una configuración de disponibilidad alta, es posible que {% data variables.product.product_name %} enrute las solicitudes a {% data variables.product.prodname_pages %} al nodo sin conexión, lo que reduce la disponibilidad de {% data variables.product.prodname_pages %} para los usuarios.' diff --git a/translations/es-ES/data/release-notes/enterprise-server/2-20/4.yml b/translations/es-ES/data/release-notes/enterprise-server/2-20/4.yml deleted file mode 100644 index 7188a506c5..0000000000 --- a/translations/es-ES/data/release-notes/enterprise-server/2-20/4.yml +++ /dev/null @@ -1,18 +0,0 @@ -date: '2020-03-25' -sections: - bugs: - - 'Las solicitudes de autenticación de SAML y los metadatos no se han cifrado de manera estricta, lo que provoca que algunos proveedores de identidades no procesen correctamente las solicitudes de autenticación iniciadas por proveedores de servicios. {% comment %} https://github.com/github/github/pull/137150, https://github.com/github/github/pull/136770, https://github.com/github/github/issues/136766 {% endcomment %}' - - 'Las exportaciones de "ghe-migrator" no contenían usuarios de hito, lo que podría interrumpir las operaciones de importación. {% comment %} https://github.com/github/github/pull/138100, https://github.com/github/github/pull/137987, https://github.com/github/github/issues/137779 {% endcomment %}' - - 'Al enviar cambios a un gist, se podría desencadenar una excepción durante el enlace posterior a la recepción. {% comment %} https://github.com/github/github/pull/138460, https://github.com/github/github/pull/138313 {% endcomment %}' - - 'Se podría producir un error en "ghe-repl-status" al intentar mostrar los repositorios que no se han replicado totalmente. {% comment %} https://github.com/github/github/pull/138463, https://github.com/github/github/pull/138388 {% endcomment %}' - known_issues: - - "En una instancia de GitHub\_Enterprise Server recién configurada sin ningún usuario, un atacante podría crear el primer usuario administrador. {% comment %} https://github.com/github/enterprise2/issues/1889 {% endcomment %}" - - 'Las reglas de cortafuegos personalizadas no se mantienen durante una actualización. {% comment %} https://github.com/github/enterprise2/issues/2823 {% endcomment %}' - - 'Los archivos supervisados de Git LFS [cargados desde la interface web](https://github.com/blog/2105-upload-files-to-your-repositories) se han agregado de forma incorrecta y directa al repositorio. {% comment %} https://github.com/github/github/issues/54684 {% endcomment %}' - - "Las incidencias no se pueden cerrar si contienen un enlace permanente a un blob del mismo repositorio en el que la ruta es mayor de 255\_caracteres. {% comment %} https://github.com/github/github/issues/107731 {% endcomment %}" - - 'Al enviar cambios a un gist, se podría desencadenar una excepción durante el enlace posterior a la recepción. {% comment %} https://github.com/github/github/issues/129091 {% endcomment %}' - - 'Cuando se habilita "Los usuarios pueden buscar en GitHub.com" con GitHub Connect, las incidencias en los repositorios privados e internos no se incluyen en los resultados de la búsqueda de GitHub.com. {% comment %} https://github.com/github/admin-experience/issues/571 {% endcomment %}' - - 'Al actualizar desde versiones anteriores, es posible que no se generen roles de trabajo en segundo plano, lo que impide características esenciales como la combinación de solicitudes de incorporación de cambios. (Actualizado el 07-04-2020) {% comment %} https://github.com/github/enterprise2/issues/19232 {% endcomment %}' - - 'Las alertas de seguridad no se notifican cuando se envían cambios a un repositorio en la línea de comandos. (Actualizado el 23-06-2020) {% comment %} https://github.com/github/github/issues/143190 {% endcomment %}' - - 'El gráfico de dependencias no detecta las dependencias cuando se implementan en una configuración de clúster con múltiples nodos de Redis. (Actualizado el 30-06-2020) {% comment %} https://github.com/github/dependency-graph/issues/81 {% endcomment %}' - - 'Cuando un nodo de réplica está sin conexión en una configuración de disponibilidad alta, es posible que {% data variables.product.product_name %} todavía enrute las solicitudes a {% data variables.product.prodname_pages %} al nodo sin conexión, lo que reduce la disponibilidad de {% data variables.product.prodname_pages %} para los usuarios.' diff --git a/translations/es-ES/data/release-notes/enterprise-server/2-20/5.yml b/translations/es-ES/data/release-notes/enterprise-server/2-20/5.yml deleted file mode 100644 index 793f355b78..0000000000 --- a/translations/es-ES/data/release-notes/enterprise-server/2-20/5.yml +++ /dev/null @@ -1,20 +0,0 @@ -date: '2020-04-07' -sections: - security_fixes: - - 'Los paquetes se han actualizado a sus últimas versiones de seguridad. {% comment %} https://github.com/github/enterprise2/pull/19536, https://github.com/github/enterprise2/pull/19494 {% endcomment %}' - bugs: - - "El tamaño máximo de 100\_MB de un objeto de Git no se podía seleccionar para un repositorio cuando la cuenta empresarial global tenían configurada una opción de tamaño de objeto de Git diferente a 100\_MB. {% comment %} https://github.com/github/github/pull/138805, https://github.com/github/github/pull/138683 {% endcomment %}" - - 'Los resultados de la API de propuestas y solicitudes de cambio podían tener un comportamiento incoherente cuando se ordenaban por el campo `updated_at`. {% comment %} https://github.com/github/github/pull/139247, https://github.com/github/github/pull/138486 {% endcomment %}' - - 'El campo `package` de SecurityVulnerability no podía consultarse a través de la API de GraphQL. {% comment %} https://github.com/github/github/pull/139418, https://github.com/github/github/pull/138245 {% endcomment %}' - - 'Al cambiar un repositorio de *public* a *internal* aparecía un mensaje de facturación irrelevante. {% comment %} https://github.com/github/github/pull/139531, https://github.com/github/github/pull/139492 {% endcomment %}' - known_issues: - - "En una instancia de GitHub\_Enterprise Server recién configurada sin ningún usuario, un atacante podría crear el primer usuario administrador. {% comment %} https://github.com/github/enterprise2/issues/1889 {% endcomment %}" - - 'Las reglas de cortafuegos personalizadas no se mantienen durante una actualización. {% comment %} https://github.com/github/enterprise2/issues/2823 {% endcomment %}' - - 'Los archivos supervisados de Git LFS [cargados desde la interfaz web](https://github.com/blog/2105-upload-files-to-your-repositories) se agregan de forma incorrecta y directa al repositorio. {% comment %} https://github.com/github/github/issues/54684 {% endcomment %}' - - "Las incidencias no se pueden cerrar si contienen un enlace permanente a un blob del mismo repositorio en el que la ruta es mayor de 255\_caracteres. {% comment %} https://github.com/github/github/issues/107731 {% endcomment %}" - - 'Al enviar cambios a un gist, se podía desencadenar una excepción durante el gancho posterior a la recepción. {% comment %} https://github.com/github/github/issues/129091 {% endcomment %}' - - 'Cuando se habilita "Los usuarios pueden buscar en GitHub.com" con GitHub Connect, las incidencias en los repositorios privados e internos no se incluyen en los resultados de la búsqueda de GitHub.com. {% comment %} https://github.com/github/admin-experience/issues/571 {% endcomment %}' - - 'Cuando se actualizaba desde versiones anteriores, no se podían generar roles de trabajo de jobs en segundo plano, lo cual impedía usar las características esenciales tales como fusionar las solicitudes de cambios. {% comment %} https://github.com/github/enterprise2/issues/19232 {% endcomment %}' - - 'Las alertas de seguridad no se notifican cuando se envían cambios a un repositorio en la línea de comandos. (Actualizado el 23-06-2020) {% comment %} https://github.com/github/github/issues/143190 {% endcomment %}' - - 'El gráfico de dependencias no detecta las dependencias cuando se implementan en una configuración de clúster con múltiples nodos de Redis. (Actualizado el 30-06-2020) {% comment %} https://github.com/github/dependency-graph/issues/81 {% endcomment %}' - - 'Cuando un nodo de réplica está sin conexión en una configuración de disponibilidad alta, es posible que {% data variables.product.product_name %} enrute las solicitudes a {% data variables.product.prodname_pages %} al nodo sin conexión, lo que reduce la disponibilidad de {% data variables.product.prodname_pages %} para los usuarios.' diff --git a/translations/es-ES/data/release-notes/enterprise-server/2-20/6.yml b/translations/es-ES/data/release-notes/enterprise-server/2-20/6.yml deleted file mode 100644 index 5922cf56cb..0000000000 --- a/translations/es-ES/data/release-notes/enterprise-server/2-20/6.yml +++ /dev/null @@ -1,27 +0,0 @@ -date: '2020-04-23' -sections: - security_fixes: - - '**ALTO**: OpenSSL se ha actualizado para abordar [CVE-2020-1967](https://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2020-1967). {% comment %} https://github.com/github/enterprise2/pull/19889, https://github.com/github/enterprise2/pull/19885 {% endcomment %}' - - '**ALTO**: Git se ha actualizado para abordar [CVE-2020-5260](https://github.com/git/git/security/advisories/GHSA-qm7j-c969-7j4q) y [CVE-2020-11008](https://github.com/git/git/security/advisories/GHSA-hjc9-x69f-jqj7). Las nuevas restricciones evitan que los repositorios malintencionados se inserten en la instancia del servidor, protegiendo a los clientes a los que aún no se les ha aplicado una revisión. {% comment %} https://github.com/github/git/pull/990 {% endcomment %}' - - '**BAJO**: ImageMagick se ha actualizado para abordar [CVE-2019-10131](https://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2019-10131). {% comment %} https://github.com/github/enterprise2/pull/19655, https://github.com/github/enterprise2/pull/19617 {% endcomment %}' - - 'Los paquetes se han actualizado a las versiones de seguridad más recientes. {% comment %} https://github.com/github/enterprise2/pull/19809, https://github.com/github/enterprise2/pull/19792, https://github.com/github/enterprise2/pull/19899, https://github.com/github/enterprise2/pull/19882 {% endcomment %}' - bugs: - - 'El usuario de Git carecía de permisos para invocar los procesos necesarios para convertir repositorios existentes mediante Subversion, del formato v4 a v3 LRS. {% comment %} https://github.com/github/enterprise2/pull/19465, https://github.com/github/enterprise2/pull/19150 {% endcomment %}' - - 'Una falta de coincidencia en las configuraciones de MySQL podría hacer que las copias de seguridad dieran error en instalaciones grandes. {% comment %} https://github.com/github/enterprise2/pull/19688, https://github.com/github/enterprise2/pull/19409, https://github.com/github/enterprise2/issues/19055 {% endcomment %}' - - 'Al actualizar desde versiones anteriores, los trabajos en segundo plano a veces no se generaban, lo que impedía funciones esenciales como la combinación de solicitudes de incorporación de cambios. {% comment %} https://github.com/github/enterprise2/pull/19771, https://github.com/github/enterprise2/pull/19712 {% endcomment %}' - - 'Cuando una licencia de GitHub Enterprise Server contenía caracteres que no eran ASCII, una solicitud "GET" al punto de conexión "/setup/api/settings" de la API de la consola de administración generaría un error interno del servidor. {% comment %} https://github.com/github/enterprise2/pull/19790 {% endcomment %}' - - 'La consola de recuperación solicitaría una contraseña raíz, incluso si la cuenta raíz estaba bloqueada. {% comment %} https://github.com/github/enterprise2/pull/19810, https://github.com/github/enterprise2/pull/19788, https://github.com/github/enterprise2/issues/18425 {% endcomment %}' - - 'Un archivo CODEOWNERS con una marca BOM UTF-8 inicial provocaría que se omitieran todas las reglas de propietario de código. {% comment %} https://github.com/github/github/pull/140974, https://github.com/github/github/pull/140729 {% endcomment %}' - changes: - - 'Cuando se producía un error en el trabajo cron del orquestador-cliente, se enviaban varios correos electrónicos a la cuenta raíz. {% comment %} https://github.com/github/enterprise2/pull/19761, https://github.com/github/enterprise2/pull/19748 {% endcomment %}' - - 'Cuando un proveedor de identidad externo controlaba el estado de administrador del sitio del usuario, los usuarios no podían ser degradados a través de la utilidad de línea de comandos. {% comment %} https://github.com/github/github/pull/140522, https://github.com/github/github/pull/137807, https://github.com/github/github/issues/42727 {% endcomment %}' - known_issues: - - "En una instancia de GitHub\_Enterprise Server recién configurada sin ningún usuario, un atacante podría crear el primer usuario administrador. {% comment %} https://github.com/github/enterprise2/issues/1889 {% endcomment %}" - - 'Las reglas de firewall personalizadas no se mantienen durante una actualización. {% comment %} https://github.com/github/enterprise2/issues/2823 {% endcomment %}' - - 'Los archivos supervisados de Git LFS [cargados a través de la interfaz web](https://github.com/blog/2105-upload-files-to-your-repositories) se agregaron incorrecta y directamente al repositorio. {% comment %} https://github.com/github/github/issues/54684 {% endcomment %}' - - "Las incidencias no se pueden cerrar si contienen un vínculo permanente a un blob en el mismo repositorio en el que la ruta de acceso del archivo tiene más de 255\_caracteres. {% comment %} https://github.com/github/github/issues/107731 {% endcomment %}" - - 'Al insertar un gist, se podría desencadenar una excepción durante el enlace posterior a la recepción. {% comment %} https://github.com/github/github/issues/129091 {% endcomment %}' - - 'Cuando se habilita "Los usuarios pueden buscar en GitHub.com" con GitHub Connect, las incidencias en los repositorios privados e internos no se incluyen en los resultados de la búsqueda de GitHub.com. {% comment %} https://github.com/github/admin-experience/issues/571 {% endcomment %}' - - 'Las alertas de seguridad no se notifican cuando se insertan en un repositorio en la línea de comandos. (Actualizado: 2020-06-23) {% comment %} https://github.com/github/github/issues/143190 {% endcomment %}' - - 'El gráfico de dependencias no detecta las dependencias cuando se implementa en una configuración de clúster con varios nodos de Redis. (Actualizado: 2020-06-30) {% comment %} https://github.com/github/dependency-graph/issues/81 {% endcomment %}' - - 'Cuando un nodo de réplica está sin conexión en una configuración de alta disponibilidad, {% data variables.product.product_name %} aún se pueden enrutar solicitudes de {% data variables.product.prodname_pages %} al nodo sin conexión, lo que reduce la disponibilidad de {% data variables.product.prodname_pages %} para los usuarios.' diff --git a/translations/es-ES/data/release-notes/enterprise-server/2-20/7.yml b/translations/es-ES/data/release-notes/enterprise-server/2-20/7.yml deleted file mode 100644 index 029333fb8b..0000000000 --- a/translations/es-ES/data/release-notes/enterprise-server/2-20/7.yml +++ /dev/null @@ -1,21 +0,0 @@ -date: '2020-05-05' -sections: - security_fixes: - - 'Los paquetes se han actualizado a sus últimas versiones de seguridad. {% comment %} https://github.com/github/enterprise2/pull/20027, https://github.com/github/enterprise2/pull/19997 {% endcomment %}' - bugs: - - 'Tanto `ghe-repl-start` como `ghe-repl-status` presentaron errores de sintaxis. {% comment %} https://github.com/github/enterprise2/pull/19954, https://github.com/github/enterprise2/pull/19927 {% endcomment %}' - - 'Si un repositorio tenía habilitada la opción de "borrar ramas de encabezado automáticamente", la rama de encabezado no se borraba automáticamente cuando una solicitud de cambios se fusionaba con una instalación de la aplicación GitHub. {% comment %} https://github.com/github/github/pull/141588, https://github.com/github/github/pull/133698, https://github.com/github/github/pull/133871, https://github.com/github/github/issues/132588 {% endcomment %}' - - 'Cuando se restablecía a un miembro de una organización, la carga útil del webhook reportaba al usuario `ghost` como el remitente y no al usuario que realmente realizaba el restablecimiento. {% comment %} https://github.com/github/github/pull/141731, https://github.com/github/github/pull/140609 {% endcomment %}' - - 'Si un repositorio tenía habilitada la configuración de "borrar automáticamente las ramas de encabezado", la rama de encabezado no se borraba cuando el repositorio de encabezado era diferente al repositorio base. {% comment %} https://github.com/github/github/pull/142096, https://github.com/github/github/pull/133871 {% endcomment %}' - - 'La recolección de elementos no utilizados de archivos temporales podía generar un error de validación de licencia. {% comment %} https://github.com/github/github/pull/142209, https://github.com/github/github/pull/142189 {% endcomment %}' - - 'En algunas situaciones, por ejemplo, cuando un repositorio se creaba por primera vez, el gancho de pre-recepción se ejecutaba sin un valor rellenado para la variable de entorno GITHUB_REPO_PUBLIC. {% comment %} https://github.com/github/github/pull/139419, https://github.com/github/github/pull/136228, https://github.com/github/github/pull/134363 {% endcomment %}' - known_issues: - - "En una instancia de GitHub\_Enterprise Server recién configurada sin ningún usuario, un atacante podría crear el primer usuario administrador. {% comment %} https://github.com/github/enterprise2/issues/1889 {% endcomment %}" - - 'Las reglas de cortafuegos personalizadas no se mantienen durante una actualización. {% comment %} https://github.com/github/enterprise2/issues/2823 {% endcomment %}' - - 'Los archivos supervisados de Git LFS [cargados desde la interfaz web](https://github.com/blog/2105-upload-files-to-your-repositories) se agregan de forma incorrecta y directa al repositorio. {% comment %} https://github.com/github/github/issues/54684 {% endcomment %}' - - "Las incidencias no se pueden cerrar si contienen un enlace permanente a un blob del mismo repositorio en el que la ruta es mayor de 255\_caracteres. {% comment %} https://github.com/github/github/issues/107731 {% endcomment %}" - - 'Al enviar cambios a un gist, se podría desencadenar una excepción durante el enlace posterior a la recepción. {% comment %} https://github.com/github/github/issues/129091 {% endcomment %}' - - 'Cuando se habilita "Los usuarios pueden buscar en GitHub.com" con GitHub Connect, las incidencias en los repositorios privados e internos no se incluyen en los resultados de la búsqueda de GitHub.com. {% comment %} https://github.com/github/admin-experience/issues/571 {% endcomment %}' - - 'Las alertas de seguridad no se notifican cuando se envían cambios a un repositorio en la línea de comandos. (Actualizado el 23-06-2020) {% comment %} https://github.com/github/github/issues/143190 {% endcomment %}' - - 'El gráfico de dependencias no detecta las dependencias cuando se implementan en una configuración de clúster con múltiples nodos de Redis. (Actualizado el 30-06-2020) {% comment %} https://github.com/github/dependency-graph/issues/81 {% endcomment %}' - - 'Cuando un nodo de réplica está sin conexión en una configuración de disponibilidad alta, es posible que {% data variables.product.product_name %} enrute las solicitudes a {% data variables.product.prodname_pages %} al nodo sin conexión, lo que reduce la disponibilidad de {% data variables.product.prodname_pages %} para los usuarios.' diff --git a/translations/es-ES/data/release-notes/enterprise-server/2-20/8.yml b/translations/es-ES/data/release-notes/enterprise-server/2-20/8.yml deleted file mode 100644 index 9771ee57e0..0000000000 --- a/translations/es-ES/data/release-notes/enterprise-server/2-20/8.yml +++ /dev/null @@ -1,20 +0,0 @@ -date: '2020-05-19' -sections: - security_fixes: - - 'Los paquetes se han actualizado a las versiones de seguridad más recientes. {% comment %} https://github.com/github/enterprise2/pull/20108, https://github.com/github/enterprise2/pull/20086 {% endcomment %}' - bugs: - - 'Después de actualizar el archivo de licencia, los servicios no se han vuelto a cargar correctamente, lo que provoca pérdida de funcionalidad. {% comment %} https://github.com/github/enterprise2/pull/20072, https://github.com/github/enterprise2/pull/19989 {% endcomment %}' - - 'Se podía producir un error en las solicitudes internas a la API que actualizan la información del gráfico de dependencias si el cuerpo de la respuesta era muy largo. {% comment %} https://github.com/github/enterprise2/pull/20231, https://github.com/github/enterprise2/pull/20208 {% endcomment %}' - - 'No se ha respetado el argumento "affiliations" en algunas de las conexiones de repositorio de GraphQL. {% comment %} https://github.com/github/github/pull/142036, https://github.com/github/github/pull/140658 {% endcomment %}' - - 'La anulación de la suspensión un usuario mediante el SSO no se ha completado si en el atributo de correo electrónico de SAML se han usado mayúsculas y minúsculas distintas a las del correo electrónico de usuario de GitHub. {% comment %} https://github.com/github/github/pull/143321, https://github.com/github/github/pull/142915 {% endcomment %}' - - 'El restablecimiento de la pertenencia de un usuario a una organización no ha instrumentado al actor en las cargas de webhook y registro de auditoría. {% comment %} https://github.com/github/github/pull/143231, https://github.com/github/github/pull/140849 {% endcomment %}' - known_issues: - - "En una instancia de GitHub\_Enterprise Server recién configurada sin ningún usuario, un atacante podría crear el primer usuario administrador. {% comment %} https://github.com/github/enterprise2/issues/1889 {% endcomment %}" - - 'Las reglas de cortafuegos personalizadas no se mantienen durante una actualización. {% comment %} https://github.com/github/enterprise2/issues/2823 {% endcomment %}' - - 'Los archivos supervisados de Git LFS [cargados desde la interface web](https://github.com/blog/2105-upload-files-to-your-repositories) se han agregado de forma incorrecta y directa al repositorio. {% comment %} https://github.com/github/github/issues/54684 {% endcomment %}' - - "Las incidencias no se pueden cerrar si contienen un enlace permanente a un blob del mismo repositorio en el que la ruta es mayor de 255\_caracteres. {% comment %} https://github.com/github/github/issues/107731 {% endcomment %}" - - 'Al enviar cambios a un gist, se podría desencadenar una excepción durante el enlace posterior a la recepción. {% comment %} https://github.com/github/github/issues/129091 {% endcomment %}' - - 'Cuando se habilita "Los usuarios pueden buscar en GitHub.com" con GitHub Connect, las incidencias en los repositorios privados e internos no se incluyen en los resultados de la búsqueda de GitHub.com. {% comment %} https://github.com/github/admin-experience/issues/571 {% endcomment %}' - - 'Las alertas de seguridad no se notifican cuando se envían cambios a un repositorio en la línea de comandos. (Actualizado el 23-06-2020) {% comment %} https://github.com/github/github/issues/143190 {% endcomment %}' - - 'El gráfico de dependencias no detecta las dependencias cuando se implementan en una configuración de clúster con múltiples nodos de Redis. (Actualizado el 30-06-2020) {% comment %} https://github.com/github/dependency-graph/issues/81 {% endcomment %}' - - 'Cuando un nodo de réplica está sin conexión en una configuración de disponibilidad alta, es posible que {% data variables.product.product_name %} todavía enrute las solicitudes a {% data variables.product.prodname_pages %} al nodo sin conexión, lo que reduce la disponibilidad de {% data variables.product.prodname_pages %} para los usuarios.' diff --git a/translations/es-ES/data/release-notes/enterprise-server/2-20/9.yml b/translations/es-ES/data/release-notes/enterprise-server/2-20/9.yml deleted file mode 100644 index c6f8065b23..0000000000 --- a/translations/es-ES/data/release-notes/enterprise-server/2-20/9.yml +++ /dev/null @@ -1,17 +0,0 @@ -date: '2020-06-02' -sections: - security_fixes: - - '**ALTA**: se identificó una vulnerabilidad de control de acceso inadecuado en la API del servidor de GitHub Enterprise que permitía a un miembro de la organización escalar permisos y obtener acceso a repositorios no autorizados dentro de una organización. Esta vulnerabilidad afectó a todas las versiones de GitHub Enterprise Server anteriores a la 2.21. Hemos emitido [CVE-2020-10516](https://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2020-10516) en respuesta a esta incidencia. La vulnerabilidad se informó a través del [programa GitHub Bug Bounty](https://bounty.github.com). {% comment %} https://github.com/github/github/pull/144454, https://github.com/github/github/pull/143444 {% endcomment %}' - - 'Los paquetes se han actualizado a sus últimas versiones de seguridad. {% comment %} https://github.com/github/enterprise2/pull/20421, https://github.com/github/enterprise2/pull/20315 {% endcomment %}' - bugs: - - 'Los motores de búsqueda podían indizar las instancias de GitHub Enterprise Server de Internet. {% comment %} https://github.com/github/github/pull/145073, https://github.com/github/github/pull/144973 {% endcomment %}' - known_issues: - - "En una instancia de GitHub\_Enterprise Server recién configurada sin ningún usuario, un atacante podría crear el primer usuario administrador. {% comment %} https://github.com/github/enterprise2/issues/1889 {% endcomment %}" - - 'Las reglas de cortafuegos personalizadas no se mantienen durante una actualización. {% comment %} https://github.com/github/enterprise2/issues/2823 {% endcomment %}' - - 'Los archivos supervisados de Git LFS [cargados desde la interfaz web](https://github.com/blog/2105-upload-files-to-your-repositories) se agregan de forma incorrecta y directa al repositorio. {% comment %} https://github.com/github/github/issues/54684 {% endcomment %}' - - "Las incidencias no se pueden cerrar si contienen un enlace permanente a un blob del mismo repositorio en el que la ruta es mayor de 255\_caracteres. {% comment %} https://github.com/github/github/issues/107731 {% endcomment %}" - - 'Al enviar cambios a un gist, se podía desencadenar una excepción durante el gancho posterior a la recepción. {% comment %} https://github.com/github/github/issues/129091 {% endcomment %}' - - 'Cuando se habilita "Los usuarios pueden buscar en GitHub.com" con GitHub Connect, las incidencias en los repositorios privados e internos no se incluyen en los resultados de la búsqueda de GitHub.com. {% comment %} https://github.com/github/admin-experience/issues/571 {% endcomment %}' - - 'Las alertas de seguridad no se notifican cuando se envían cambios a un repositorio en la línea de comandos. (Actualizado el 23-06-2020) {% comment %} https://github.com/github/github/issues/143190 {% endcomment %}' - - 'El gráfico de dependencias no detecta las dependencias cuando se implementan en una configuración de clúster con múltiples nodos de Redis. (Actualizado el 30-06-2020) {% comment %} https://github.com/github/dependency-graph/issues/81 {% endcomment %}' - - 'Cuando un nodo de réplica está sin conexión en una configuración de disponibilidad alta, es posible que {% data variables.product.product_name %} enrute las solicitudes a {% data variables.product.prodname_pages %} al nodo sin conexión, lo que reduce la disponibilidad de {% data variables.product.prodname_pages %} para los usuarios.' diff --git a/translations/es-ES/data/release-notes/enterprise-server/2-21/0.yml b/translations/es-ES/data/release-notes/enterprise-server/2-21/0.yml deleted file mode 100644 index d86d0d6afa..0000000000 --- a/translations/es-ES/data/release-notes/enterprise-server/2-21/0.yml +++ /dev/null @@ -1,73 +0,0 @@ -date: '2020-06-09' -sections: - features: - - 'Los usuarios pueden [administrar notificaciones](https://help.github.com/en/enterprise/2.21/user/github/managing-subscriptions-and-notifications-on-github/about-notifications) sobre problemas, solicitudes de incorporación de cambios y otros asuntos al navegar desde una notificación web. {% comment %} https://github.com/github/enterprise-releases/issues/2135#issuecomment-633905096 {% endcomment %}' - - 'Los usuarios pueden [convertir una solicitud de incorporación de cambios nuevamente en un "Borrador"](https://github.blog/changelog/2020-04-08-convert-pull-request-to-draft/). {% comment %} https://github.com/github/releases/issues/800 {% endcomment %}' - - '[Sugerencias de varias líneas](https://github.blog/changelog/2020-04-15-multi-line-code-suggestions-general-availability/) permite que un usuario sugiera un cambio específico en varias líneas de código al revisar una solicitud de incorporación de cambios. {% comment %} https://github.com/github/releases/issues/810 {% endcomment %}' - - 'Los usuarios con acceso de escritura a un repositorio pueden [ocultar un comentario en una incidencia o una solicitud de incorporación de cambios como un "Duplicado"](https://help.github.com/en/enterprise/2.21/user/github/building-a-strong-community/managing-disruptive-comments#hiding-a-comment). {% comment %}https://github.com/github/github/pull/131746 {% endcomment %}' - - 'Al [crear un repositorio a partir de una plantilla](https://help.github.com/en/enterprise/2.21/user/github/creating-cloning-and-archiving-repositories/creating-a-repository-from-a-template) un usuario puede optar por incluir todas las ramas, en lugar de solo la rama predeterminada. {% comment %} https://github.com/github/releases/issues/580 {% endcomment %}' - - '[Las tarjetas de proyecto de incidencias incluyen una sección de solicitudes de incorporación de cambios vinculadas](https://github.blog/changelog/2020-02-04-project-issue-cards-include-linked-pull-requests/) de forma que un usuario puede ver qué trabajo de desarrollo está relacionado con la incidencia directamente desde el panel del proyecto. {% comment %} https://github.com/github/releases/issues/743 {% endcomment %}' - - 'Hay un nuevo conjunto de [puntos finales de "eliminación de reacciones"] (https://developer.github.com/changes/2020-02-26-new-delete-reactions-endpoints/) en la API de reacciones. Los puntos finales existentes "Eliminar reacciones" quedarán en desuso a principios de 2021. {% comment %} https://developer.github.com/changes/2020-02-26-new-delete-reactions-endpoints/ {% endcomment %}' - - 'Hay un nuevo conjunto de [puntos finales de API de Teams] (https://developer.github.com/changes/2020-01-21-moving-the-team-api-endpoints/) que permitirán que GitHub escale y admita la API de Teams a largo plazo. Los puntos finales de API existentes quedarán en desuso a principios de 2021. {% comment %} https://developer.github.com/changes/2020-01-21-moving-the-team-api-endpoints/ {% endcomment %}' - - 'Los usuarios pueden [crear vínculos entre propuestas y solicitudes de incorporación de cambios](https://help.github.com/en/enterprise/2.21/user/github/managing-your-work-on-github/linking-a-pull-request-to-an-issue#manually-linking-a-pull-request-to-an-issue) sin necesidad de usar palabras clave de cierre en la descripción de la solicitud de incorporación de cambios. {% comment %} https://github.com/github/releases/issues/704 {% endcomment %}' - security_fixes: - - 'Se identificó una vulnerabilidad de control de acceso inadecuado en la API de GitHub Enterprise Server que permitía a un miembro de la organización escalar permisos y obtener acceso a repositorios no autorizados dentro de una organización. Esta vulnerabilidad afectó a todas las versiones de GitHub Enterprise Server anteriores a la 2.21. Hemos emitido [CVE-2020-10516](https://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2020-10516) en respuesta a esta incidencia. La vulnerabilidad se informó a través del [programa de recompensas por errores de GitHub](https://bounty.github.com/). {% comment %} https://developer.github.com/changes/2020-02-26-new-delete-reactions-endpoints/ {% endcomment %}' - bugs: - - "Si un usuario con acceso de inserción minimizaba el comentario de otro usuario, el autor del comentario podía anular la minimización aunque no tuviera privilegios suficientes. {% comment %} https://github.com/github/github/pull/141237 {% endcomment %}" - - 'Los usuarios podían combinarse accidentalmente con el maestro desde el editor de la plantilla de incidencias y el editor de blobs. {% comment %} https://github.com/github/github/pull/134483, https://github.com/github/github/pull/134323 {% endcomment %}' - - 'Cuando un usuario eliminaba una cuenta de GitHub, los registros de auditoría no mostraban correctamente los registros de eliminación de la organización. {% comment %} https://github.com/github/github/pull/140940 {% endcomment %}' - - 'El avatar gist del usuario actual se vincularía a una dirección URL inexistente. {% comment %} https://github.com/github/github/pull/140925 {% endcomment %}' - - 'El recuento de la pestaña de repositorios de la organización no incluía los repositorios internos. {% comment %} https://github.com/github/github/pull/136323 {% endcomment %}' - - 'Hacer clic en el botón "Mostrar todos los equipos" al transferir un repositorio provocaba un error 500. {% comment %} https://github.com/github/github/pull/134455 {% endcomment %}' - - "Los nombres de archivo largos podrían causar problemas de desbordamiento al mostrar la etiqueta \"Cambiado desde la última vista\" o el cambio de diferencia \"Mostrar enriquecido\" en la vista de archivo de diferencias. {% comment %} https://github.com/github/github/pull/134453 {% endcomment %}" - - 'Las tarjetas flotantes para los equipos de la organización informaron erróneamente el tamaño de sus miembros. {% comment %} https://github.com/github/github/pull/133879 {% endcomment %}' - - 'La ventana emergente de comentarios de revisión de solicitud de incorporación de cambios tenía una incidencia de desplazamiento. {% comment %} https://github.com/github/github/pull/141157 {% endcomment %}' - - 'HAproxy podría saturarse y provocar una ralentización de las operaciones de Git. {% comment %} https://github.com/github/enterprise2/issues/19322 {% endcomment %}' - - 'La función Dependency Graph no se habilitó automáticamente después de la promoción de la réplica de alta disponibilidad. {% comment %} https://github.com/github/enterprise2/issues/18698 {% endcomment %}' - - 'Se podría desencadenar un tiempo de espera en la página de índice de versiones para repositorios con miles de solicitudes de incorporación de cambios de borrador. {% comment %} https://github.com/github/github/pull/131802 {% endcomment %}' - - 'No era posible filtrar las solicitudes de incorporación de cambios por estado y borrador al mismo tiempo. {% comment %} https://github.com/github/github/pull/132567 {% endcomment %}' - - 'Si una solicitud de incorporación de cambios cambiaba un puntero de submódulo, al hacer clic en "Editar archivo" en ese archivo de submódulo desde la pestaña "Archivos cambiados" de la página de solicitud de incorporación de cambios se producía un error 404. {% comment %} https://github.com/github/github/pull/132448 {% endcomment %}' - - 'No fue posible agregar usuarios a una organización o eliminar la organización, después de la eliminación masiva de todos los usuarios y administradores de esa organización. {% comment %} https://github.com/github/github/pull/132238 {% endcomment %}' - - 'Los comentarios de revisión en archivos que contengan signos diacríticos y caracteres no latinos en el nombre de archivo de la página "Archivos modificados" desaparecerían cuando se volviera a cargar la página. {% comment %} https://github.com/github/github/pull/131836 {% endcomment %}' - - 'El estado de la casilla "Visto" no se retenía para los archivos que contenían signos diacríticos y caracteres no latinos en el nombre de archivo en la página "Archivos cambiados". {% comment %} https://github.com/github/github/pull/131836 {% endcomment %}' - - 'Las solicitudes de incorporación de cambios mostraban la notificación "Aprobado" cuando no se habían realizado todas las revisiones requeridas. {% comment %} https://github.com/github/github/pull/131823 {% endcomment %}' - - 'El menú desplegable de etiquetas estaba vacío al buscar una etiqueta en repositorios con más de 100 etiquetas. {% comment %} https://github.com/github/github/pull/131914 {% endcomment %}' - - 'Las páginas de solicitudes de incorporación de cambios que muestran anotaciones con títulos que no son UTF-8 pueden encontrar errores de codificación en la representación de la vista. {% comment %} https://github.com/github/github/pull/138534 {% endcomment %}' - - 'Una condición de carrera para la actualización en la página de OAuth podría hacer que una redirección se ejecutara dos veces. {% comment %} https://github.com/github/github/pull/131964 {% endcomment %}' - - 'El tiempo de espera de la página "Tokens de acceso personal" se agotaría si hubiera más de 10 tokens. {% comment %} https://github.com/github/github/pull/132064 {% endcomment %}' - - 'Los trabajos de sincronización de equipos y usuarios LDAP programados podían iniciarse mientras los trabajos de sincronización programados anteriormente todavía estaban en proceso. Se ha implementado un mecanismo de bloqueo para evitar que se inicien nuevos trabajos de sincronización si todavía se está ejecutando uno. {% 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: - - 'La interfaz de notificaciones web, incluidos los nuevos [estados] (https://help.github.com/en/enterprise/2.21/user/github/managing-subscriptions-and-notifications-on-github/managing-notifications-from-your-inbox#triaging-options), [filtros](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) y [accesos directos](https://help.github.com/en/enterprise/2.21/user/github/getting-started-with-github/keyboard-shortcuts#notifications), se ha actualizado. {% comment %} https://github.com/github/enterprise-releases/issues/2135#issuecomment-633905096 {% endcomment %}' - - 'Ahora es posible deshabilitar la reactivación de los usuarios LDAP en la sincronización LDAP. {% comment %} https://github.com/github/github/pull/139023 {% endcomment %}' - - 'La redacción de la rama protegida de inserción se actualizó para aclarar que los administradores siempre pueden realizar inserciones y que los usuarios con el rol de mantenimiento pueden realizar inserciones cuando se superan las comprobaciones de estado. {% comment %} https://github.com/github/github/pull/141555 {% endcomment %}' - - 'Evite la confirmación en blanco cuando la sugerencia sea idéntica al texto original. {% comment %} https://github.com/github/github/pull/138587 {% endcomment %}' - - 'La paginación se admite como una forma de obtener más archivos en la diferencia asociada con una confirmación a través de API REST. {% comment %} https://github.com/github/github/pull/134341 {% endcomment %}' - - 'Los administradores pueden habilitar, deshabilitar, eliminar y buscar webhooks mediante el id. de webhook desde la línea de comandos con "ghe-webhook-manage". {% comment %} https://github.com/github/enterprise2/pull/19027 {% endcomment %}' - - 'El redireccionamiento base automático ocurrirá después de la limpieza manual de la referencia principal para una solicitud de incorporación de cambios combinada. {% comment %} https://github.com/github/github/pull/142133 {% endcomment %}' - - 'Los archivos SVG se manejan como texto y como imágenes en el visor de diferencias. {% comment %} https://github.com/github/render/pull/1129 {% endcomment %}' - - 'La configuración de "eliminación automática de ramas al combinar" se puede establecer al crear y actualizar repositorios mediante la API REST. {% comment %} https://github.com/github/github/pull/131728 {% endcomment %}' - - 'Se agregó un nuevo punto de conexión para eliminar una implementación a través de la API REST. {% comment %} https://github.com/github/github/pull/128733 {% endcomment %}' - - 'Los administradores pueden [habilitar alertas de seguridad](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-on-github-enterprise-server) pero deshabilitar todas las notificaciones de esas alertas. {% comment %} https://github.com/github/releases/issues/841 {% endcomment %}' - - 'El registro de Pages muestra el inicio de sesión del usuario que accede al sitio de GitHub Pages. {% comment %} https://github.com/github/enterprise2/pull/19905 {% endcomment %}' - - 'Los miembros de Enterprise pueden ver todas las organizaciones a las que pertenecen como parte de su cuenta Enterprise desde una sola vista yendo a "https://[ghes-hostname]/enterprises/[account-name]". {% comment %} https://github.com/github/releases/issues/832 {% endcomment %}' - - '[La compatibilidad de API REST con roles de evaluación de prioridades y mantenimiento](https://developer.github.com/changes/2020-04-07-expanding-rest-api-support-for-the-triage-and-maintain-roles/) se ha expandido. {% comment %} https://github.com/github/releases/issues/748 {% endcomment %}' - - 'Un usuario puede crear y compartir consultas de búsqueda que se resuelvan en el usuario actual utilizando la sintaxis de búsqueda "@me". {% comment %} https://github.com/github/github/pull/129624 {% endcomment %}' - - 'Se han [agregado] nuevas opciones de configuración de plantillas de incidencias(https://github.blog/changelog/2019-10-28-new-issue-template-configuration-options/). {% comment %} https://github.com/github/releases/issues/660 {% endcomment %}' - - 'Se ha mejorado la confiabilidad y el tiempo de finalización de la copia de seguridad y restauración de MySQL. {% comment %} https://github.com/github/ghes-infrastructure/issues/162 {% endcomment %}' - - '[Visibilidad mejorada](https://github.blog/2020-02-06-get-more-information-at-a-glance-with-issue-and-pull-request-linking/) de solicitudes de incorporación de cambios y referencias de incidencias en la barra lateral de incidencias, tarjetas de incidencias y lista de incidencias. {% comment %} https://github.com/github/releases/issues/704 {% endcomment %}' - - 'Los usuarios pueden filtrar y buscar por "linked:pr" o "linked:issue". {% comment %} https://github.com/github/releases/issues/744 {% endcomment %}' - - 'Ahora es posible la conmutación automática por error de MySQL dentro de una sola región para implementaciones de clúster. {% comment %} https://github.com/github/ghes-infrastructure/issues/136 {% endcomment %}' - - 'Un usuario puede comparar etiquetas entre dos versiones para determinar qué cambios se han realizado en la página de versiones. {% comment %} https://github.com/github/github/issues/107054 {% endcomment %}' - - 'Los comentarios obsoletos ya no se contraen de forma predeterminada en la línea de tiempo de la solicitud de incorporación de cambios. Se pueden contraer resolviendo el subproceso. {% comment %} https://github.com/github/enterprise-web/pull/6389#issuecomment-634201583 {% endcomment %}' - - 'Los administradores pueden ver una lista de inicios de sesión reservados para uso interno yendo a la pestaña de stafftools "Inicios de sesión reservados". {% comment %} https://github.com/github/enterprise-web/pull/6389#issuecomment-637846206 {% endcomment %}' - known_issues: - - 'En una instancia de GitHub Enterprise Server recién configurada sin ningún usuario, un atacante podría crear el primer usuario administrador. {% comment %} https://github.com/github/enterprise2/issues/1889 {% endcomment %}' - - 'Las reglas de firewall personalizadas no se mantienen durante una actualización. {% comment %} https://github.com/github/enterprise2/issues/2823 {% endcomment %}' - - 'Los archivos supervisados de Git LFS [cargados a través de la interfaz web](https://github.com/blog/2105-upload-files-to-your-repositories) se agregaron incorrecta y directamente al repositorio. {% comment %} https://github.com/github/github/issues/54684 {% endcomment %}' - - 'Las incidencias no se pueden cerrar si contienen un vínculo permanente a un blob en el mismo repositorio en el que la ruta de acceso del archivo tiene más de 255 caracteres. {% comment %} https://github.com/github/github/issues/107731 {% endcomment %}' - - 'Al insertar un gist, se podría desencadenar una excepción durante el enlace posterior a la recepción. {% comment %} https://github.com/github/github/issues/129091 {% endcomment %}' - - 'Cuando se habilita "Los usuarios pueden buscar en GitHub.com" con GitHub Connect, las incidencias en los repositorios privados e internos no se incluyen en los resultados de la búsqueda de GitHub.com. {% comment %} https://github.com/github/admin-experience/issues/571 {% endcomment %}' - - 'Las alertas de seguridad no se notifican cuando se insertan en un repositorio en la línea de comandos. (Actualizado: 2020-06-23) {% comment %} https://github.com/github/github/issues/143190 {% endcomment %}' - - 'Los registros de auditoría pueden atribuirse a 127.0.0.1 en lugar de a la dirección IP de origen real. (Actualizado: 2020-11-02) {% comment %} https://github.com/github/enterprise2/issues/21514 {% endcomment %}' - - "La configuración del permiso de un repositorio para \"Evaluación de prioridades\" o \"Mantener\" genera un mensaje de error." - - 'Cuando un nodo de réplica está sin conexión en una configuración de alta disponibilidad, {% data variables.product.product_name %} aún se pueden enrutar solicitudes de {% data variables.product.prodname_pages %} al nodo sin conexión, lo que reduce la disponibilidad de {% data variables.product.prodname_pages %} para los usuarios.' diff --git a/translations/es-ES/data/release-notes/enterprise-server/2-21/1.yml b/translations/es-ES/data/release-notes/enterprise-server/2-21/1.yml deleted file mode 100644 index a33bc34eb8..0000000000 --- a/translations/es-ES/data/release-notes/enterprise-server/2-21/1.yml +++ /dev/null @@ -1,21 +0,0 @@ -date: '2020-06-23' -sections: - security_fixes: - - 'Los paquetes se han actualizado a sus últimas versiones de seguridad. {% comment %} https://github.com/github/enterprise2/pull/20747, https://github.com/github/enterprise2/pull/20727 {% endcomment %}' - bugs: - - 'Las bitácoras de eventos excesivamente grandes podían ocasionar inestabilidad en el reenvío de bitácoras cuando se utilizaba UDP como el mecanismo de transporte. {% comment %} https://github.com/github/enterprise2/pull/20458, https://github.com/github/enterprise2/pull/20445 {% endcomment %}' - - 'El servicio de comunicación interno asociado para acceder a MySQL se reiniciaba más frecuentemente de lo necesario, incluida una parte del proceso de actualización, lo que podía provocar que la actualización fallara parcialmente. Hemos reducido la tasa de reinicios y fortalecido el código. {% comment %} https://github.com/github/enterprise2/pull/20957, https://github.com/github/enterprise2/pull/20972, https://github.com/github/github/pull/146974 {% endcomment %}' - - 'La anulación de la suspensión automática de un usuario mediante SSO no se completaba si el atributo de las llaves SSH ya estaba asociado con la cuenta de usuario. {% comment %} https://github.com/github/github/pull/143475, https://github.com/github/github/pull/142927 {% endcomment %}' - - 'El hash de permiso del repositorio de la API REST no indicaba acceso de los miembros empresariales que tenían acceso de lectura en los repositorios internos. {% comment %} https://github.com/github/github/pull/144756, https://github.com/github/github/pull/144292 {% endcomment %}' - - 'La política empresarial de "borrado de propuestas del repositorio" no reflejaba la configuración guardada. {% comment %} https://github.com/github/github/pull/145218, https://github.com/github/github/pull/145067 {% endcomment %}' - - 'El registro de auditoría no incluía los eventos de cambio de protección de rama. {% comment %} https://github.com/github/github/pull/145998, https://github.com/github/github/pull/145014 {% endcomment %}' - known_issues: - - "En una instancia de GitHub\_Enterprise Server recién configurada sin ningún usuario, un atacante podría crear el primer usuario administrador. {% comment %} https://github.com/github/enterprise2/issues/1889 {% endcomment %}" - - 'Las reglas de cortafuegos personalizadas no se mantienen durante una actualización. {% comment %} https://github.com/github/enterprise2/issues/2823 {% endcomment %}' - - 'Los archivos supervisados de Git LFS [cargados desde la interfaz web](https://github.com/blog/2105-upload-files-to-your-repositories) se agregan de forma incorrecta y directa al repositorio. {% comment %} https://github.com/github/github/issues/54684 {% endcomment %}' - - "Las incidencias no se pueden cerrar si contienen un enlace permanente a un blob del mismo repositorio en el que la ruta es mayor de 255\_caracteres. {% comment %} https://github.com/github/github/issues/107731 {% endcomment %}" - - 'Cuando se habilita "Los usuarios pueden buscar en GitHub.com" con GitHub Connect, las incidencias en los repositorios privados e internos no se incluyen en los resultados de la búsqueda de GitHub.com. {% comment %} https://github.com/github/admin-experience/issues/571 {% endcomment %}' - - 'Las alertas de seguridad no se notifican cuando se realiza la inserción en un repositorio en la línea de comandos. {% comment %} https://github.com/github/github/issues/143190 {% endcomment %}' - - 'Los registros de auditoría se pueden atribuir a 127.0.0.1 en lugar de a la dirección IP de origen real. (Actualizado el 02-11-2020) {% comment %} https://github.com/github/enterprise2/issues/21514 {% endcomment %}' - - 'La configuración del permiso de un repositorio en "Evaluación de errores" o "Mantenimiento" genera un mensaje de error.' - - 'Cuando un nodo de réplica está sin conexión en una configuración de disponibilidad alta, es posible que {% data variables.product.product_name %} enrute las solicitudes a {% data variables.product.prodname_pages %} al nodo sin conexión, lo que reduce la disponibilidad de {% data variables.product.prodname_pages %} para los usuarios.' diff --git a/translations/es-ES/data/release-notes/enterprise-server/2-21/10.yml b/translations/es-ES/data/release-notes/enterprise-server/2-21/10.yml deleted file mode 100644 index 4b6abb5058..0000000000 --- a/translations/es-ES/data/release-notes/enterprise-server/2-21/10.yml +++ /dev/null @@ -1,15 +0,0 @@ -date: '2020-10-20' -sections: - security_fixes: - - 'Los paquetes se han actualizado a sus últimas versiones de seguridad. {% comment %} https://github.com/github/enterprise2/pull/23096, https://github.com/github/enterprise2/pull/23081 {% endcomment %}' - bugs: - - 'El mensaje "Confirmar la directiva del requisito en dos fases" de una cuenta empresarial ha sido incorrecto. {% comment %} https://github.com/github/github/pull/158736 {% endcomment %}' - known_issues: - - "En una instancia de GitHub\_Enterprise Server recién configurada sin ningún usuario, un atacante podría crear el primer usuario administrador. {% comment %} https://github.com/github/enterprise2/issues/1889 {% endcomment %}" - - 'Las reglas de cortafuegos personalizadas no se mantienen durante una actualización. {% comment %} https://github.com/github/enterprise2/issues/2823 {% endcomment %}' - - 'Los archivos supervisados de Git LFS [cargados desde la interface web](https://github.com/blog/2105-upload-files-to-your-repositories) se han agregado de forma incorrecta y directa al repositorio. {% comment %} https://github.com/github/github/issues/54684 {% endcomment %}' - - "Las incidencias no se pueden cerrar si contienen un enlace permanente a un blob del mismo repositorio en el que la ruta es mayor de 255\_caracteres. {% comment %} https://github.com/github/github/issues/107731 {% endcomment %}" - - 'Cuando se habilita "Los usuarios pueden buscar en GitHub.com" con GitHub Connect, las incidencias en los repositorios privados e internos no se incluyen en los resultados de la búsqueda de GitHub.com. {% comment %} https://github.com/github/admin-experience/issues/571 {% endcomment %}' - - 'Las alertas de seguridad no se notifican cuando se realiza la inserción en un repositorio en la línea de comandos. {% comment %} https://github.com/github/github/issues/143190 {% endcomment %}' - - 'Los registros de auditoría se pueden atribuir a 127.0.0.1 en lugar de a la dirección IP de origen real. (Actualizado el 02-11-2020) {% comment %} https://github.com/github/enterprise2/issues/21514 {% endcomment %}' - - 'Cuando un nodo de réplica está sin conexión en una configuración de disponibilidad alta, es posible que {% data variables.product.product_name %} todavía enrute las solicitudes a {% data variables.product.prodname_pages %} al nodo sin conexión, lo que reduce la disponibilidad de {% data variables.product.prodname_pages %} para los usuarios.' diff --git a/translations/es-ES/data/release-notes/enterprise-server/2-21/11.yml b/translations/es-ES/data/release-notes/enterprise-server/2-21/11.yml deleted file mode 100644 index b9654553bd..0000000000 --- a/translations/es-ES/data/release-notes/enterprise-server/2-21/11.yml +++ /dev/null @@ -1,18 +0,0 @@ -date: '2020-11-03' -sections: - security_fixes: - - '**MEDIA:** El uso elevado de CPU podía deberse a una solicitud hecha específicamente al puente de SVN, lo cual resultaba en una negación del servicio (DoS). {% comment %} https://github.com/github/slumlord/pull/1004, https://github.com/github/slumlord/pull/1000 {% endcomment %}' - - "**BAJA:** La validación incorrecta de un token provocaba una entropía reducida para la coincidencia de tokens durante la autenticación. El análisis muestra que, en la práctica, en este caso no hay riesgos de seguridad significativos. {% comment %} https://github.com/github/github/pull/159455, https://github.com/github/github/pull/159193 {% endcomment %}" - - 'Los paquetes se actualizaron a las últimas versiones de seguridad. {% comment %} https://github.com/github/enterprise2/pull/23539, https://github.com/github/enterprise2/pull/23171, https://github.com/github/enterprise2/pull/23692, https://github.com/github/enterprise2/pull/23677 {% endcomment %}' - bugs: - - 'Al editar las plantillas de incidencias con los nombres de archivo que contienen caracteres que no son de ASCII, se producía un error con el mensaje "500 Internal Server Error". {% comment %} https://github.com/github/github/pull/160589, https://github.com/github/github/pull/159747 {% endcomment %}' - - 'Los métodos de recolección métrica para los trabajos en segundo plano incrementaba el uso de la CPU. (Actualizado el 03-11-2020) {% comment %} https://github.com/github/github/pull/160109 {% endcomment %}' - known_issues: - - 'En una instancia de GitHub Enterprise Server recién configurada sin ningún usuario, un atacante podría crear el primer usuario administrador. {% comment %} https://github.com/github/enterprise2/issues/1889 {% endcomment %}' - - 'Las reglas de cortafuegos personalizadas no se mantienen durante una actualización. {% comment %} https://github.com/github/enterprise2/issues/2823 {% endcomment %}' - - 'Los archivos supervisados de Git LFS [cargados desde la interface web](https://github.com/blog/2105-upload-files-to-your-repositories) se han agregado de forma incorrecta y directa al repositorio. {% comment %} https://github.com/github/github/issues/54684 {% endcomment %}' - - 'Las incidencias no se pueden cerrar si contienen un enlace permanente a un blob del mismo repositorio en el que la ruta es mayor de 255 caracteres. {% comment %} https://github.com/github/github/issues/107731 {% endcomment %}' - - 'Cuando se habilita "Los usuarios pueden buscar en GitHub.com" con GitHub Connect, las incidencias en los repositorios privados e internos no se incluyen en los resultados de la búsqueda de GitHub.com. {% comment %} https://github.com/github/admin-experience/issues/571 {% endcomment %}' - - 'Las alertas de seguridad no se notifican cuando se realiza la inserción en un repositorio en la línea de comandos. {% comment %} https://github.com/github/github/issues/143190 {% endcomment %}' - - 'Los registros de auditoría pueden atribuirse a 127.0.0.1 en vez de a la dirección IP de origen real. {% comment %} https://github.com/github/enterprise2/issues/21514 {% endcomment %}' - - 'Cuando un nodo de réplica está sin conexión en una configuración de disponibilidad alta, es posible que {% data variables.product.product_name %} enrute las solicitudes a {% data variables.product.prodname_pages %} al nodo sin conexión, lo que reduce la disponibilidad de {% data variables.product.prodname_pages %} para los usuarios.' diff --git a/translations/es-ES/data/release-notes/enterprise-server/2-21/12.yml b/translations/es-ES/data/release-notes/enterprise-server/2-21/12.yml deleted file mode 100644 index 5420d17a97..0000000000 --- a/translations/es-ES/data/release-notes/enterprise-server/2-21/12.yml +++ /dev/null @@ -1,16 +0,0 @@ -date: '2020-11-17' -sections: - security_fixes: - - 'Packages have been updated to the latest security versions. {% comment %} https://github.com/github/enterprise2/pull/23844, https://github.com/github/enterprise2/pull/23712 {% endcomment %}' - bugs: - - 'The babeld logs were missing a separator between seconds and microseconds. {% comment %} https://github.com/github/babeld/pull/1005, https://github.com/github/babeld/pull/1002 {% endcomment %}' - - 'When the enterprise account "Repository visibility change" policy was set to "Enabled", organization owners could not change the visibility of repositories within the organization. {% comment %} https://github.com/github/github/pull/160921, https://github.com/github/github/pull/160773 {% endcomment %}' - - 'Audit logs could be attributed to 127.0.0.1 instead of the actual source IP address. {% comment %} https://github.com/github/github/pull/162436, https://github.com/github/github/pull/161215 {% endcomment %}' - known_issues: - - 'On a freshly set up GitHub Enterprise Server without any users, an attacker could create the first admin user. {% comment %} https://github.com/github/enterprise2/issues/1889 {% endcomment %}' - - 'Custom firewall rules are not maintained during an upgrade. {% comment %} https://github.com/github/enterprise2/issues/2823 {% endcomment %}' - - '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. {% comment %} https://github.com/github/github/issues/54684 {% endcomment %}' - - '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. {% comment %} https://github.com/github/github/issues/107731 {% endcomment %}' - - '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. {% comment %} https://github.com/github/admin-experience/issues/571 {% endcomment %}' - - 'Security alerts are not reported when pushing to a repository on the command line. {% comment %} https://github.com/github/github/issues/143190 {% endcomment %}' - - '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.' diff --git a/translations/es-ES/data/release-notes/enterprise-server/2-21/13.yml b/translations/es-ES/data/release-notes/enterprise-server/2-21/13.yml deleted file mode 100644 index cf474bcf3b..0000000000 --- a/translations/es-ES/data/release-notes/enterprise-server/2-21/13.yml +++ /dev/null @@ -1,19 +0,0 @@ -date: '2020-12-03' -sections: - bugs: - - 'El servicio de autorización se detectó como incorrecto debido a la condición de carrera en bootstrap, lo cual ocasionó que se reiniciara el servicio. {% comment %} https://github.com/github/authzd/pull/1278 {% endcomment %}' - - 'Un comportamiento subyacente estaba causando que un servicio no estuviera disponible durante el proceso de actualización del hotpatch. {% comment %} https://github.com/github/enterprise2/pull/24054, https://github.com/github/enterprise2/issues/23947 {% endcomment %}' - - 'Un subconjunto de certificados SSL que reenviaban registros no se estaba aplicando correctamente. {% comment %} https://github.com/github/enterprise2/pull/24113, https://github.com/github/enterprise2/pull/23981 {% endcomment %}' - - 'Se enviaron notificaciones de correo electrónico para suspender usuarios cuando se eliminaban de un equipo o de una organización. {% comment %} https://github.com/github/github/pull/162971, https://github.com/github/github/pull/162742 {% endcomment %}' - - 'La forma en la que se aplicaron los certificados SSH entre las organizaciones y las empresas no fue uniforme. {% comment %} https://github.com/github/github/pull/163426, https://github.com/github/github/pull/159538, https://github.com/github/authentication/issues/115 {% endcomment %}' - - 'Cuando se limitaba la tarifa de una cuenta debido al uso incorrecto de contraseñas, se podía bloquear hasta 24 horas. {% comment %} https://github.com/github/github/pull/163436, https://github.com/github/github/pull/162938, https://github.com/github/github-ds/pull/51 {% endcomment %}' - - 'La sincronización de solicitudes de cambios en los repositorios con muchas referencias podían provocar que se retrasaran las colas de los roles de trabajo. {% comment %} https://github.com/github/github/pull/163575, https://github.com/github/github/pull/163142 {% endcomment %}' - - 'Cuando se iniciaba sesión después de intentar visitar una página específica, se enviaba a los usuarios a la página de inicio en vez de al destino previsto. {% comment %} https://github.com/github/github/pull/163784, https://github.com/github/github/pull/163579, https://github.com/github/github/pull/154117, https://github.com/github/ecosystem-apps/issues/1076 {% endcomment %}' - known_issues: - - "En una instancia de GitHub\_Enterprise Server recién configurada sin ningún usuario, un atacante podría crear el primer usuario administrador. {% comment %} https://github.com/github/enterprise2/issues/1889 {% endcomment %}" - - 'Las reglas de cortafuegos personalizadas no se mantienen durante una actualización. {% comment %} https://github.com/github/enterprise2/issues/2823 {% endcomment %}' - - 'Los archivos supervisados de Git LFS [cargados desde la interface web](https://github.com/blog/2105-upload-files-to-your-repositories) se han agregado de forma incorrecta y directa al repositorio. {% comment %} https://github.com/github/github/issues/54684 {% endcomment %}' - - "Las incidencias no se pueden cerrar si contienen un enlace permanente a un blob del mismo repositorio en el que la ruta es mayor de 255\_caracteres. {% comment %} https://github.com/github/github/issues/107731 {% endcomment %}" - - 'Cuando se habilita "Los usuarios pueden buscar en GitHub.com" con GitHub Connect, las incidencias en los repositorios privados e internos no se incluyen en los resultados de la búsqueda de GitHub.com. {% comment %} https://github.com/github/admin-experience/issues/571 {% endcomment %}' - - 'Las alertas de seguridad no se notifican cuando se realiza la inserción en un repositorio en la línea de comandos. {% comment %} https://github.com/github/github/issues/143190 {% endcomment %}' - - 'Cuando un nodo de réplica está sin conexión en una configuración de disponibilidad alta, es posible que {% data variables.product.product_name %} enrute las solicitudes a {% data variables.product.prodname_pages %} al nodo sin conexión, lo que reduce la disponibilidad de {% data variables.product.prodname_pages %} para los usuarios.' diff --git a/translations/es-ES/data/release-notes/enterprise-server/2-21/14.yml b/translations/es-ES/data/release-notes/enterprise-server/2-21/14.yml deleted file mode 100644 index 52e7bb88ab..0000000000 --- a/translations/es-ES/data/release-notes/enterprise-server/2-21/14.yml +++ /dev/null @@ -1,13 +0,0 @@ -date: '2020-12-17' -sections: - security_fixes: - - '**BAJO:** El uso elevado de CPU se puede desencadenar debido a una solicitud creada específicamente para el puente de SVN, lo que genera un ataque por denegación de servicio (DoS).{% comment %} https://github.com/github/slumlord/pull/1021, https://github.com/github/slumlord/pull/1017 {% endcomment %}' - - 'Los paquetes se han actualizado a sus últimas versiones de seguridad. {% comment %} https://github.com/github/enterprise2/pull/24352, https://github.com/github/enterprise2/pull/23866 {% endcomment %}' - known_issues: - - "En una instancia de GitHub\_Enterprise Server recién configurada sin ningún usuario, un atacante podría crear el primer usuario administrador. {% comment %} https://github.com/github/enterprise2/issues/1889 {% endcomment %}" - - 'Las reglas de cortafuegos personalizadas no se mantienen durante una actualización. {% comment %} https://github.com/github/enterprise2/issues/2823 {% endcomment %}' - - 'Los archivos supervisados de Git LFS [cargados desde la interface web](https://github.com/blog/2105-upload-files-to-your-repositories) se han agregado de forma incorrecta y directa al repositorio. {% comment %} https://github.com/github/github/issues/54684 {% endcomment %}' - - "Las incidencias no se pueden cerrar si contienen un enlace permanente a un blob del mismo repositorio en el que la ruta es mayor de 255\_caracteres. {% comment %} https://github.com/github/github/issues/107731 {% endcomment %}" - - 'Cuando se habilita "Los usuarios pueden buscar en GitHub.com" con GitHub Connect, las incidencias en los repositorios privados e internos no se incluyen en los resultados de la búsqueda de GitHub.com. {% comment %} https://github.com/github/admin-experience/issues/571 {% endcomment %}' - - 'Las alertas de seguridad no se notifican cuando se realiza la inserción en un repositorio en la línea de comandos. {% comment %} https://github.com/github/github/issues/143190 {% endcomment %}' - - 'Cuando un nodo de réplica está sin conexión en una configuración de disponibilidad alta, es posible que {% data variables.product.product_name %} todavía enrute las solicitudes a {% data variables.product.prodname_pages %} al nodo sin conexión, lo que reduce la disponibilidad de {% data variables.product.prodname_pages %} para los usuarios.' diff --git a/translations/es-ES/data/release-notes/enterprise-server/2-21/15.yml b/translations/es-ES/data/release-notes/enterprise-server/2-21/15.yml deleted file mode 100644 index c0e152fe05..0000000000 --- a/translations/es-ES/data/release-notes/enterprise-server/2-21/15.yml +++ /dev/null @@ -1,33 +0,0 @@ -date: '2021-03-02' -sections: - security_fixes: - - '**ALTA:** se identificó una vulnerabilidad de control de acceso inadecuado en GitHub Enterprise Server que permitía a los usuarios autenticados de la instancia obtener acceso de escritura a repositorios no autorizados a través de solicitud de incorporación de cambios y solicitudes de API REST diseñadas específicamente. Un atacante necesitaría poder bifurcar el repositorio de destino, una configuración que está deshabilitada de forma predeterminada para los repositorios privados propiedad de la organización. Las protecciones de ramas, como las revisiones de solicitud de incorporación de cambios requeridas o las comprobaciones de estado, evitarían la combinación de confirmaciones no autorizadas sin una revisión o validación adicional. A esta vulnerabilidad se le ha asignado el código CVE-2021-22861. Este problema se informó mediante el programa [GitHub Bug Bounty Program] (https://bounty.github.com).' - - '**ALTA:** se identificó una vulnerabilidad de control de acceso inadecuado en la API de GraphQL de GitHub Enterprise Server que permitía a los usuarios autenticados de la instancia modificar el permiso de colaboración del responsable de mantenimiento de una solicitud de incorporación de cambios sin la debida autorización. Al aprovecharse de esta vulnerabilidad, un atacante podía obtener acceso a las ramas principales de las solicitudes de incorporación de cambios abiertas en los repositorios de los que son responsables del mantenimiento. La bifurcación está deshabilitada de forma predeterminada para los repositorios privados propiedad de la organización y evitaría esta vulnerabilidad. Además, las protecciones de las ramas, como las revisiones de solicitud de incorporación de cambios requeridas o las comprobaciones de estado, evitarían la combinación de confirmaciones no autorizadas sin una revisión o validación adicional. A esta vulnerabilidad se le ha asignado el código CVE-2021-22863. Este problema se informó mediante el programa [GitHub Bug Bounty Program] (https://bounty.github.com).' - - "**ALTA:** se identificó una vulnerabilidad de ejecución de código remoto en GitHub Enterprise Server que podría aprovecharse al crear un sitio de GitHub Pages. La configuración controlada por el usuario de los analizadores subyacentes utilizados por GitHub Pages no estaba lo suficientemente restringida y permitía ejecutar comandos en la instancia de GitHub Enterprise Server. Para aprovechar esta vulnerabilidad de seguridad, un atacante necesitaría permiso para crear un sitio de GitHub Pages en la instancia de GitHub\_Enterprise Server. Esta vulnerabilidad se le ha asignado el código CVE-2020-10519 y se ha notificado mediante [GitHub\_Bug Bounty Program](https://bounty.github.com/)." - - '**MEDIA:** los tokens de GitHub de las compilaciones de GitHub Pages podían terminar en las bitácoras.' - - '**BAJA:** una solicitud que se elaboraba especialmente para el puente SVN podía desencadenar una larga espera antes de que se produjera un error, lo cual provocaba un una Negación del Servicio (DoS).' - - 'Los paquetes se han actualizado a las últimas versiones de seguridad.' - bugs: - - 'Las verificaciones de salud del equilibrador de carga podían provocar en algunos casos que las bitácoras de babeld se llenaran con errores sobre el protocolo PROXY.' - - 'Se registró sin querer un mensaje informativo como un error durante las capturas de pantalla de GitHub Enterprise Backup Utilities, lo cual dio como resultado que se enviaran correos electrónicos innecesarios cuando los jobs de cron programaban respaldos que escuchaban la salida a stderr.' - - 'Al restaurar una copia de seguridad grande, el registro de excepciones relacionado con el agotamiento de la memoria de Redis podría provocar un error en la restauración debido a un disco lleno.' - - 'Al editar una página wiki, un usuario podría experimentar un error 500 al hacer clic en el botón Guardar.' - - 'Una confirmación firmada por S/MIME con un certificado con varios nombres en el nombre alternativo del sujeto se mostraba incorrectamente como "No verificada" en la notificación de confirmación.' - - 'Se enviaban correos electrónicos a un usuario suspendido cuando se le agregaba a un equipo.' - - 'Cuando un repositorio tenía un gran número de manifiestos, se mostraba el error "You have reached the maximum number of allowed manifest files (20) for this repository" en la pestaña Información > Gráfico de dependencias. Para obtener más información, consulta [Límites de visualización](https://docs.github.com/en/github/managing-security-vulnerabilities/troubleshooting-the-detection-of-vulnerable-dependencies#are-there-limits-which-affect-the-dependency-graph-data).' - - 'Al cargar un archivo de licencia nuevo con una cantidad de plazas diferente del archivo de licencia anterior, la diferencia de plazas no se representaba correctamente en la página Configuración -> Licencia de la cuenta empresarial.' - - 'La casilla de verificación para impedir que los administradores del repositorio cambiaran el acceso de lectura anónimo de Git disponible en la configuración de cuenta empresarial no se podía habilitar o inhabilitar correctamente.' - - 'Cuando una compilación de GitHub Pages fallaba, la notificación de correo electrónico contenía un enlace incorrecto a la ubicación de soporte.' - - 'Durante un año bisiesto, el usuario obtenía una respuesta 404 cuando intentaba ver la actividad de contribución de un lunes.' - - 'Al visitar la sección *Explore* se producía un error interno del servidor 500.' - changes: - - 'Se agregó compatibilidad para los [tipos de instancia r5b de AWS EC2](https://aws.amazon.com/about-aws/whats-new/2020/12/introducing-new-amazon-ec2-r5b-instances-featuring-60-gbps-of-ebs-bandwidth-and-260K-iops/).' - - 'Se ajustó la priorización de la cola en segundo plano para distribuir los jobs más equitativamente.' - known_issues: - - 'En un servidor de GitHub Enterprise recién configurado sin usuarios, un atacante podría crear el primer usuario administrador.' - - 'Las reglas de firewall personalizadas no se mantienen durante una actualización.' - - 'Los archivos supervisados de Git LFS [cargados desde la interfaz web](https://github.com/blog/2105-upload-files-to-your-repositories) se agregan de manera incorrecta y directa al repositorio.' - - "Las incidencias no se pueden cerrar si contienen un vínculo permanente a un blob en el mismo repositorio en el que la ruta de acceso de archivo del blob tiene más de 255\_caracteres." - - 'Cuando se habilita "Los usuarios pueden buscar en GitHub.com" con GitHub Connect, las incidencias en los repositorios privados e internos no se incluyen en los resultados de la búsqueda de GitHub.com.' - - 'Las alertas de seguridad no se notifican cuando se envían cambios a un repositorio en la línea de comandos.' - - 'Cuando un nodo de réplica está sin conexión en una configuración de disponibilidad alta, es posible que {% data variables.product.product_name %} enrute las solicitudes a {% data variables.product.prodname_pages %} al nodo sin conexión, lo que reduce la disponibilidad de {% data variables.product.prodname_pages %} para los usuarios.' diff --git a/translations/es-ES/data/release-notes/enterprise-server/2-21/16.yml b/translations/es-ES/data/release-notes/enterprise-server/2-21/16.yml deleted file mode 100644 index c15777484d..0000000000 --- a/translations/es-ES/data/release-notes/enterprise-server/2-21/16.yml +++ /dev/null @@ -1,14 +0,0 @@ -date: '2021-03-16' -sections: - security_fixes: - - 'Los paquetes se han actualizado a las últimas versiones de seguridad.' - bugs: - - "Se producirá un error en la importación de repositorios archivados desde GitHub\_Enterprise Server en los que faltan archivos de repositorio." - known_issues: - - 'En un servidor de GitHub Enterprise recién configurado sin usuarios, un atacante podría crear el primer usuario administrador.' - - 'Las reglas de firewall personalizadas no se mantienen durante una actualización.' - - 'Los archivos supervisados de Git LFS [cargados desde la interface web](https://github.com/blog/2105-upload-files-to-your-repositories) se han agregado de manera incorrecta y directa al repositorio.' - - "Las incidencias no se pueden cerrar si contienen un vínculo permanente a un blob en el mismo repositorio en el que la ruta de acceso de archivo del blob tiene más de 255\_caracteres." - - 'Cuando se habilita "Los usuarios pueden buscar en GitHub.com" con GitHub Connect, las incidencias en los repositorios privados e internos no se incluyen en los resultados de la búsqueda de GitHub.com.' - - 'Las alertas de seguridad no se notifican cuando se envían cambios a un repositorio en la línea de comandos.' - - 'Cuando un nodo de réplica está sin conexión en una configuración de disponibilidad alta, es posible que {% data variables.product.product_name %} todavía enrute las solicitudes a {% data variables.product.prodname_pages %} al nodo sin conexión, lo que reduce la disponibilidad de {% data variables.product.prodname_pages %} para los usuarios.' diff --git a/translations/es-ES/data/release-notes/enterprise-server/2-21/17.yml b/translations/es-ES/data/release-notes/enterprise-server/2-21/17.yml deleted file mode 100644 index 9c2b33be60..0000000000 --- a/translations/es-ES/data/release-notes/enterprise-server/2-21/17.yml +++ /dev/null @@ -1,27 +0,0 @@ -date: '2021-03-23' -intro: Downloads have been disabled due to a major bug affecting multiple customers. A fix will be available in the next patch. -sections: - security_fixes: - - '**HIGH:** A remote code execution vulnerability was identified in GitHub Enterprise Server that could be exploited when building a GitHub Pages site. User-controlled configuration options used by GitHub Pages were not sufficiently restricted and made it possible to override environment variables leading to code execution on the GitHub Enterprise Server instance. To exploit this vulnerability, an attacker would need permission to create and build a GitHub Pages site on the GitHub Enterprise Server instance. This vulnerability affected all versions of GitHub Enterprise Server prior to 3.0.3 and was fixed in 3.0.3, 2.22.9, and 2.21.17. This vulnerability was reported via the GitHub Bug Bounty program and has been assigned CVE-2021-22864.' - - Packages have been updated to the latest security versions. - bugs: - - The `ghe-cluster-config-init` run was not fully accounting for the exit code of background jobs leading to improper handling of preflight checks. - changes: - - Logs will rotate based on size in addition to time. - - Use a relative number for consul and nomad `bootstrap_expect` allowing for a cluster to bootstrap even if a handful of nodes are down. - known_issues: - - On a freshly set up GitHub Enterprise 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. - - Security alerts are not reported when pushing to a repository on the command line. - - | - Log rotation may fail to signal services to transition to new log files, leading to older log files continuing to be used, and eventual root disk space exhaustion. - To remedy and/or prevent this issue, run the following commands in the [administrative shell](https://docs.github.com/en/enterprise-server/admin/configuration/accessing-the-administrative-shell-ssh) (SSH), or contact [GitHub Enterprise Support](https://support.github.com/contact) for assistance: - - ``` - printf "PATH=/usr/local/sbin:/usr/local/bin:/usr/local/share/enterprise:/usr/sbin:/usr/bin:/sbin:/bin\n29,59 * * * * root /usr/sbin/logrotate /etc/logrotate.conf\n" | sudo sponge /etc/cron.d/logrotate - sudo /usr/sbin/logrotate -f /etc/logrotate.conf - ``` - - 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. diff --git a/translations/es-ES/data/release-notes/enterprise-server/2-21/18.yml b/translations/es-ES/data/release-notes/enterprise-server/2-21/18.yml deleted file mode 100644 index e5c0229045..0000000000 --- a/translations/es-ES/data/release-notes/enterprise-server/2-21/18.yml +++ /dev/null @@ -1,16 +0,0 @@ -date: '2021-04-01' -sections: - security_fixes: - - "**ALTO:** Se ha identificado una vulnerabilidad de control de acceso incorrecta en GitHub\_Enterprise Server que permitía que tokens de acceso generados desde el [flujo de autenticación web] de una aplicación de GitHub (https://docs.github.com/en/developers/apps/identifying-and-authorizing-users-for-github-apps#web-application-flow) leyeran metadatos de repositorios privados mediante la API REST sin tener los permisos correctos asignados. Para aprovechar esta vulnerabilidad, un atacante tendría que crear una aplicación de GitHub en la instancia y hacer que el usuario la autorice mediante el flujo de autenticación web. Los metadatos de repositorio privado devueltos estarían limitados a repositorios propiedad del usuario identificado por el token. Esta vulnerabilidad afectaba a todas las versiones de GitHub\_Enterprise Server anteriores a la\_3.0.4 y se ha corregido en las versiones\_3.0.4, 2.22.10 y 2.21.18. Esta vulnerabilidad se ha asignado a CVE-2021-22865 y se ha notificado mediante [GitHub\_Bug Bounty Program](https://bounty.github.com)." - - 'Los paquetes se han actualizado a las últimas versiones de seguridad.' - bugs: - - 'Los servicios no realizaban la transición a los nuevos archivos de registro como parte de la rotación de registros, lo que genera un aumento del uso de disco.' - - 'La etiqueta de los resultados de la búsqueda para los repositorios internos se ha mostrado como "Privada" en vez de como "Interna".' - known_issues: - - 'En un servidor de GitHub Enterprise recién configurado sin usuarios, un atacante podría crear el primer usuario administrador.' - - 'Las reglas de firewall personalizadas no se mantienen durante una actualización.' - - 'Los archivos supervisados de Git LFS [cargados desde la interface web](https://github.com/blog/2105-upload-files-to-your-repositories) se han agregado de manera incorrecta y directa al repositorio.' - - "Las incidencias no se pueden cerrar si contienen un vínculo permanente a un blob en el mismo repositorio en el que la ruta de acceso de archivo del blob tiene más de 255\_caracteres." - - 'Cuando se habilita "Los usuarios pueden buscar en GitHub.com" con GitHub Connect, las incidencias en los repositorios privados e internos no se incluyen en los resultados de la búsqueda de GitHub.com.' - - 'Las alertas de seguridad no se notifican cuando se envían cambios a un repositorio en la línea de comandos.' - - 'Cuando un nodo de réplica está sin conexión en una configuración de disponibilidad alta, es posible que {% data variables.product.product_name %} todavía enrute las solicitudes a {% data variables.product.prodname_pages %} al nodo sin conexión, lo que reduce la disponibilidad de {% data variables.product.prodname_pages %} para los usuarios.' diff --git a/translations/es-ES/data/release-notes/enterprise-server/2-21/19.yml b/translations/es-ES/data/release-notes/enterprise-server/2-21/19.yml deleted file mode 100644 index f4efd5a5c1..0000000000 --- a/translations/es-ES/data/release-notes/enterprise-server/2-21/19.yml +++ /dev/null @@ -1,18 +0,0 @@ -date: '2021-04-14' -sections: - security_fixes: - - 'Los paquetes se han actualizado a las últimas versiones de seguridad.' - bugs: - - 'Podía generarse un mensaje de advertencia de tipo `jq: error (at :0): Cannot index number with string "settings"` durante la promoción de la réplica.' - - 'Al visitar la página `/settings/emails` se almacenaba el estado, lo que podía causar redireccionamientos inadecuados al cerrar sesión y volver a iniciarla.' - - 'Las alertas de la gráfica de dependencias no se mostraban para algunos componentes cuyos avisos tenían nombres de paquetes con mayúsculas en `vulnerable_version_ranges`.' - - 'Un usuario vio un error 500 al ejecutar operaciones de git en una instancia configurada con autenticación LDAP.' - - 'Cuando ghe-migrator detectaba errores de importación, algunas veces se cancelaba todo el proceso y las bitácoras no incluían suficiente contexto.' - known_issues: - - 'En un servidor de GitHub Enterprise recién configurado sin usuarios, un atacante podría crear el primer usuario administrador.' - - 'Las reglas de firewall personalizadas no se mantienen durante una actualización.' - - 'Los archivos rastreados de Git LFS [cargados a través de la interfaz web](https://github.com/blog/2105-upload-files-to-your-repositories) se agregan de forma incorrecta y directa al repositorio.' - - "Las incidencias no se pueden cerrar si contienen un vínculo permanente a un blob en el mismo repositorio en el que la ruta de acceso de archivo del blob tiene más de 255\_caracteres." - - 'Cuando se habilita "Los usuarios pueden buscar en GitHub.com" con GitHub Connect, las incidencias en los repositorios privados e internos no se incluyen en los resultados de la búsqueda de GitHub.com.' - - 'Las alertas de seguridad no se notifican cuando se envían cambios a un repositorio en la línea de comandos.' - - 'Cuando un nodo de réplica está sin conexión en una configuración de disponibilidad alta, es posible que {% data variables.product.product_name %} enrute las solicitudes a {% data variables.product.prodname_pages %} al nodo sin conexión, lo que reduce la disponibilidad de {% data variables.product.prodname_pages %} para los usuarios.' diff --git a/translations/es-ES/data/release-notes/enterprise-server/2-21/2.yml b/translations/es-ES/data/release-notes/enterprise-server/2-21/2.yml deleted file mode 100644 index 61ff910929..0000000000 --- a/translations/es-ES/data/release-notes/enterprise-server/2-21/2.yml +++ /dev/null @@ -1,21 +0,0 @@ -date: '2020-07-09' -sections: - security_fixes: - - "**MEDIO:** Se ha actualizado nginx a la versión\_1.16.1 y se ha solucionado CVE-2019-20372. (Actualizado el 22-07-2020) {% comment %} https://github.com/github/enterprise2/pull/21252 {% endcomment %}" - - 'Los paquetes se han actualizado a sus últimas versiones de seguridad. {% comment %} https://github.com/github/enterprise2/pull/21089, https://github.com/github/enterprise2/pull/21036 {% endcomment %}' - bugs: - - "Algunos archivos de registro no se han girado cada 7\_días. {% comment %} https://github.com/github/enterprise2/pull/21279, https://github.com/github/enterprise2/pull/21264 {% endcomment %}" - - 'La reutilización rápida de los puertos origen de webhook ha dado como resultado conexiones rechazadas. {% comment %} https://github.com/github/enterprise2/pull/21286, https://github.com/github/enterprise2/pull/21280 {% endcomment %}' - - 'Los trabajos incorrectos en segundo plano podrían intentar ejecutarse en instancias configuradas como réplicas pasivas. {% comment %} https://github.com/github/enterprise2/pull/21317, https://github.com/github/enterprise2/pull/21212, https://github.com/github/enterprise2/issues/21167 {% endcomment %}' - - 'Es posible que la VPN entre nodos se vuelva inestable y provoque el registro de errores y el agotamiento del espacio libre en el volumen raíz. {% comment %} https://github.com/github/enterprise2/pull/21360, https://github.com/github/enterprise2/pull/21357 {% endcomment %}' - - 'Los repositorios internos no se han incluido correctamente en los resultados de la búsqueda para las organizaciones habilitadas con SAML. {% comment %} https://github.com/github/github/pull/147505, https://github.com/github/github/pull/145692 {% endcomment %}' - known_issues: - - "En una instancia de GitHub\_Enterprise Server recién configurada sin ningún usuario, un atacante podría crear el primer usuario administrador. {% comment %} https://github.com/github/enterprise2/issues/1889 {% endcomment %}" - - 'Las reglas de cortafuegos personalizadas no se mantienen durante una actualización. {% comment %} https://github.com/github/enterprise2/issues/2823 {% endcomment %}' - - 'Los archivos supervisados de Git LFS [cargados desde la interface web](https://github.com/blog/2105-upload-files-to-your-repositories) se han agregado de forma incorrecta y directa al repositorio. {% comment %} https://github.com/github/github/issues/54684 {% endcomment %}' - - "Las incidencias no se pueden cerrar si contienen un enlace permanente a un blob del mismo repositorio en el que la ruta es mayor de 255\_caracteres. {% comment %} https://github.com/github/github/issues/107731 {% endcomment %}" - - 'Cuando se habilita "Los usuarios pueden buscar en GitHub.com" con GitHub Connect, las incidencias en los repositorios privados e internos no se incluyen en los resultados de la búsqueda de GitHub.com. {% comment %} https://github.com/github/admin-experience/issues/571 {% endcomment %}' - - 'Las alertas de seguridad no se notifican cuando se realiza la inserción en un repositorio en la línea de comandos. {% comment %} https://github.com/github/github/issues/143190 {% endcomment %}' - - 'Los registros de auditoría se pueden atribuir a 127.0.0.1 en lugar de a la dirección IP de origen real. (Actualizado el 02-11-2020) {% comment %} https://github.com/github/enterprise2/issues/21514 {% endcomment %}' - - 'La configuración del permiso de un repositorio en "Evaluación de errores" o "Mantenimiento" genera un mensaje de error.' - - 'Cuando un nodo de réplica está sin conexión en una configuración de disponibilidad alta, es posible que {% data variables.product.product_name %} todavía enrute las solicitudes a {% data variables.product.prodname_pages %} al nodo sin conexión, lo que reduce la disponibilidad de {% data variables.product.prodname_pages %} para los usuarios.' diff --git a/translations/es-ES/data/release-notes/enterprise-server/2-21/20.yml b/translations/es-ES/data/release-notes/enterprise-server/2-21/20.yml deleted file mode 100644 index da65139d80..0000000000 --- a/translations/es-ES/data/release-notes/enterprise-server/2-21/20.yml +++ /dev/null @@ -1,19 +0,0 @@ -date: '2021-04-28' -sections: - security_fixes: - - Packages have been updated to the latest security versions. - bugs: - - Setup script running on MySQL replication may have caused unnecessary database reseeding during database failover. - - '`config-apply` could take longer than necessary due to `rake db:migrate` being called unnecessarily.' - - Orchestrator could have failed over to a MySQL replica which was not replicating from primary during seeding phase when primary could not be connected. - - Organizations or projects with errors blocked migration and could not be excluded. - changes: - - Preflight checks allow all AWS instance types by default. - known_issues: - - On a freshly set up GitHub Enterprise 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. - - Security alerts are not reported when pushing to a repository on the command line. - - '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.' diff --git a/translations/es-ES/data/release-notes/enterprise-server/2-21/21.yml b/translations/es-ES/data/release-notes/enterprise-server/2-21/21.yml deleted file mode 100644 index eb1be9511e..0000000000 --- a/translations/es-ES/data/release-notes/enterprise-server/2-21/21.yml +++ /dev/null @@ -1,15 +0,0 @@ -date: '2021-05-13' -sections: - security_fixes: - - 'Los paquetes se han actualizado a las últimas versiones de seguridad.' - bugs: - - 'La conmutación por error automática de Orchestrator se puede habilitar durante la fase de aplicación de configuración.' - - 'A los usuarios con permiso de mantenedor en un repositorio se les mostraba una advertencia de verificación por correo electrónico en vez de una compilación de página correcta en la página de configuración de Pages del repositorio.' - known_issues: - - 'En un servidor de GitHub Enterprise recién configurado sin usuarios, un atacante podría crear el primer usuario administrador.' - - 'Las reglas de firewall personalizadas no se mantienen durante una actualización.' - - 'Los archivos supervisados de Git LFS [cargados desde la interface web](https://github.com/blog/2105-upload-files-to-your-repositories) se han agregado de manera incorrecta y directa al repositorio.' - - "Las incidencias no se pueden cerrar si contienen un vínculo permanente a un blob en el mismo repositorio en el que la ruta de acceso de archivo del blob tiene más de 255\_caracteres." - - 'Cuando se habilita "Los usuarios pueden buscar en GitHub.com" con GitHub Connect, las incidencias en los repositorios privados e internos no se incluyen en los resultados de la búsqueda de GitHub.com.' - - 'Las alertas de seguridad no se notifican cuando se envían cambios a un repositorio en la línea de comandos.' - - 'Cuando un nodo de réplica está sin conexión en una configuración de disponibilidad alta, es posible que {% data variables.product.product_name %} todavía enrute las solicitudes a {% data variables.product.prodname_pages %} al nodo sin conexión, lo que reduce la disponibilidad de {% data variables.product.prodname_pages %} para los usuarios.' diff --git a/translations/es-ES/data/release-notes/enterprise-server/2-21/22.yml b/translations/es-ES/data/release-notes/enterprise-server/2-21/22.yml deleted file mode 100644 index 24932df18f..0000000000 --- a/translations/es-ES/data/release-notes/enterprise-server/2-21/22.yml +++ /dev/null @@ -1,16 +0,0 @@ -date: '2021-05-25' -sections: - security_fixes: - - '**MEDIA:** Bajo ciertas circunstancias, los usuarios que se eliminaban de un equipo u organización podían retener el acceso de escritura a las ramas en las cuales tenían solicitudes de cambio existentes abiertas.' - - 'Los paquetes se han actualizado a las últimas versiones de seguridad.' - bugs: - - 'Las direcciones IP que agregaba un administrador utilizando el botón "Crear entrada de lista de admisión" podía bloquearse de todos modos.' - - 'En un entorno de clúster o de alta disponibilidad, las compilaciones de GitHub Pages podían activarse en nodos secundarios, donde generaban un error.' - known_issues: - - 'En un servidor de GitHub Enterprise recién configurado sin usuarios, un atacante podría crear el primer usuario administrador.' - - 'Las reglas de firewall personalizadas no se mantienen durante una actualización.' - - 'Los archivos rastreados de Git LFS [cargados a través de la interfaz web](https://github.com/blog/2105-upload-files-to-your-repositories) se agregan de forma incorrecta y directa al repositorio.' - - "Las incidencias no se pueden cerrar si contienen un vínculo permanente a un blob en el mismo repositorio en el que la ruta de acceso de archivo del blob tiene más de 255\_caracteres." - - 'Cuando se habilita "Los usuarios pueden buscar en GitHub.com" con GitHub Connect, las incidencias en los repositorios privados e internos no se incluyen en los resultados de la búsqueda de GitHub.com.' - - 'Las alertas de seguridad no se notifican cuando se envían cambios a un repositorio en la línea de comandos.' - - 'Cuando un nodo de réplica está sin conexión en una configuración de disponibilidad alta, es posible que {% data variables.product.product_name %} enrute las solicitudes a {% data variables.product.prodname_pages %} al nodo sin conexión, lo que reduce la disponibilidad de {% data variables.product.prodname_pages %} para los usuarios.' diff --git a/translations/es-ES/data/release-notes/enterprise-server/2-21/23.yml b/translations/es-ES/data/release-notes/enterprise-server/2-21/23.yml deleted file mode 100644 index 4859bfbd35..0000000000 --- a/translations/es-ES/data/release-notes/enterprise-server/2-21/23.yml +++ /dev/null @@ -1,16 +0,0 @@ -date: '2021-06-10' -sections: - security_fixes: - - 'Los paquetes se han actualizado a las últimas versiones de seguridad.' - bugs: - - 'Los errores de importación de organizaciones o repositorios desde orígenes distintos a GitHub podrían producir un error de tipo "método sin definir "[]" para nil:NilClass".' - changes: - - "Los usuarios de GraphQL\_API pueden consultar el campo público \"closingIssuesReferences\" en el objeto \"PullRequest\". Este campo recupera incidencias que se cerrarán de forma automática cuando se combine la solicitud de incorporación de cambios relacionada. Este enfoque también permitirá migrar estos datos en el futuro, como parte de un proceso de migración más fiel." - known_issues: - - 'En un servidor de GitHub Enterprise recién configurado sin usuarios, un atacante podría crear el primer usuario administrador.' - - 'Las reglas de cortafuegos personalizadas se eliminan durante el proceso de actualización.' - - 'Los archivos supervisados de Git LFS [cargados desde la interface web](https://github.com/blog/2105-upload-files-to-your-repositories) se han agregado de manera incorrecta y directa al repositorio.' - - "Las incidencias no se pueden cerrar si contienen un enlace permanente a un blob del mismo repositorio en el que la ruta es mayor de 255\_caracteres." - - 'Cuando se habilita "Los usuarios pueden buscar en GitHub.com" con GitHub Connect, las incidencias en los repositorios privados e internos no se incluyen en los resultados de la búsqueda de GitHub.com.' - - 'Las alertas de seguridad no se notifican cuando se envían cambios a un repositorio en la línea de comandos.' - - 'Cuando un nodo de réplica está sin conexión en una configuración de disponibilidad alta, es posible que {% data variables.product.product_name %} todavía enrute las solicitudes a {% data variables.product.prodname_pages %} al nodo sin conexión, lo que reduce la disponibilidad de {% data variables.product.prodname_pages %} para los usuarios.' diff --git a/translations/es-ES/data/release-notes/enterprise-server/2-21/3.yml b/translations/es-ES/data/release-notes/enterprise-server/2-21/3.yml deleted file mode 100644 index 02dfe2a080..0000000000 --- a/translations/es-ES/data/release-notes/enterprise-server/2-21/3.yml +++ /dev/null @@ -1,18 +0,0 @@ -date: '2020-07-21' -sections: - security_fixes: - - 'Los paquetes se actualizaron a las últimas versiones de seguridad. {% comment %} https://github.com/github/enterprise2/pull/21438, https://github.com/github/enterprise2/pull/21402, https://github.com/github/enterprise2/pull/21496, https://github.com/github/enterprise2/pull/21479 {% endcomment %}' - bugs: - - 'Las gráficas de monitoreo de la consola de administración a veces no se muestran correctamente en pantallas grandes. {% comment %} https://github.com/github/enterprise2/pull/21398, https://github.com/github/enterprise2/pull/21381 {% endcomment %}' - - 'El flujo de creación de un manifiesto de una GitHub App no se pudía utilizar en algunos escenarios en donde se aplicaba la política de SameSite Cookie. {% comment %} https://github.com/github/github/pull/147829, https://github.com/github/github/pull/144121 {% endcomment %}' - - 'En algunas circunstancias, al acceder a la página ''Explorar'', se producía un error en la aplicación. {% comment %} https://github.com/github/github/pull/149605, https://github.com/github/github/pull/148949 {% endcomment %}' - known_issues: - - "En una instancia de GitHub\_Enterprise Server recién configurada sin ningún usuario, un atacante podría crear el primer usuario administrador. {% comment %} https://github.com/github/enterprise2/issues/1889 {% endcomment %}" - - 'Las reglas de cortafuegos personalizadas no se mantienen durante una actualización. {% comment %} https://github.com/github/enterprise2/issues/2823 {% endcomment %}' - - 'Los archivos supervisados de Git LFS [cargados desde la interfaz web](https://github.com/blog/2105-upload-files-to-your-repositories) se agregan de forma incorrecta y directa al repositorio. {% comment %} https://github.com/github/github/issues/54684 {% endcomment %}' - - "Las incidencias no se pueden cerrar si contienen un enlace permanente a un blob del mismo repositorio en el que la ruta es mayor de 255\_caracteres. {% comment %} https://github.com/github/github/issues/107731 {% endcomment %}" - - 'Cuando se habilita "Los usuarios pueden buscar en GitHub.com" con GitHub Connect, las incidencias en los repositorios privados e internos no se incluyen en los resultados de la búsqueda de GitHub.com. {% comment %} https://github.com/github/admin-experience/issues/571 {% endcomment %}' - - 'Las alertas de seguridad no se notifican cuando se realiza la inserción en un repositorio en la línea de comandos. {% comment %} https://github.com/github/github/issues/143190 {% endcomment %}' - - 'Los registros de auditoría se pueden atribuir a 127.0.0.1 en lugar de a la dirección IP de origen real. (Actualizado el 02-11-2020) {% comment %} https://github.com/github/enterprise2/issues/21514 {% endcomment %}' - - 'La configuración del permiso de un repositorio en `Triage` o `Maintain` genera un mensaje de error.' - - 'Cuando un nodo de réplica está sin conexión en una configuración de disponibilidad alta, es posible que {% data variables.product.product_name %} enrute las solicitudes a {% data variables.product.prodname_pages %} al nodo sin conexión, lo que reduce la disponibilidad de {% data variables.product.prodname_pages %} para los usuarios.' diff --git a/translations/es-ES/data/release-notes/enterprise-server/2-21/4.yml b/translations/es-ES/data/release-notes/enterprise-server/2-21/4.yml deleted file mode 100644 index a78e07de75..0000000000 --- a/translations/es-ES/data/release-notes/enterprise-server/2-21/4.yml +++ /dev/null @@ -1,28 +0,0 @@ -date: '2020-08-11' -sections: - security_fixes: - - '{% octicon "alert" aria-label="The alert icon" %} **Crítico:** Se ha identificado una vulnerabilidad de ejecución de código remoto en GitHub Pages que podría permitir a un atacante ejecutar comandos como parte de la creación de un sitio de GitHub Pages. Es problema se debía a una dependencia obsoleta y vulnerable que se usaba en el proceso de compilación de Páginas. Para aprovechar esta vulnerabilidad de seguridad, un atacante necesitaría permiso para crear un sitio de GitHub Pages en la instancia de GitHub Enterprise Server. Esta vulnerabilidad ha afectado a todas las versiones de GitHub Enterprise Server. Para mitigar esta vulnerabilidad, se ha actualizado Kramdown a fin de solucionar CVE-2020-14001. {% comment %} https://github.com/github/pages/pull/2835, https://github.com/github/pages/pull/2827 {% endcomment %}' - - '**Alto:** Alto: Un atacante podría insertar un argumento malintencionado en un subcomando de Git al ejecutarlo en GitHub Enterprise Server. Esto permitiría a un atacante sobrescribir archivos arbitrarios con contenido parcialmente controlado por el usuario y, posiblemente, ejecutar comandos arbitrarios en la instancia de GitHub Enterprise Server. Para aprovechar esta vulnerabilidad, un atacante necesitaría permiso de acceso a los repositorios de la instancia de GHES. Pero debido a otras protecciones implementadas, no podríamos identificar una forma de aprovechar esta vulnerabilidad de forma activa. Esta vulnerabilidad se ha notificado desde el programa GitHub Security Bug Bounty. {% comment %} https://github.com/github/github/pull/150936, https://github.com/github/github/pull/150634 {% endcomment %}' - - 'Los paquetes se han actualizado a las versiones de seguridad más recientes. {% comment %} https://github.com/github/enterprise2/pull/21679, https://github.com/github/enterprise2/pull/21542, https://github.com/github/enterprise2/pull/21812, https://github.com/github/enterprise2/pull/21700 {% endcomment %}' - bugs: - - 'Un error de configuración de Consul ha impedido el procesamiento de algunos trabajos en segundo plano en instancias independientes. {% comment %} https://github.com/github/enterprise2/pull/21463 {% endcomment %}' - - 'El cálculo de asignación de memoria de servicio podría asignar una cantidad incorrecta o ilimitada de memoria a un servicio, lo que generaría un rendimiento incorrecto del sistema. {% comment %} https://github.com/github/enterprise2/pull/21689 {% endcomment %}' - - 'La plataforma de virtualización para los sistemas oVirt KVM no se ha detectado de forma correcta, lo que ha provocado problemas durante las actualizaciones. {% comment %} https://github.com/github/enterprise2/pull/21731, https://github.com/github/enterprise2/pull/21669 {% endcomment %}' - - "El mensaje de error para la autenticación no válida con una contraseña desde la línea de comandos de Git no ha completado la URL vinculada a la adición del token o la clave SSH adecuados. {% comment %} https://github.com/github/github/pull/149607, https://github.com/github/github/pull/149351 {% endcomment %}" - - 'La creación de una incidencia en un repositorio de usuario mediante la característica Plantillas de incidencia podría generar un error interno del servidor. {% comment %} https://github.com/github/github/pull/150173, https://github.com/github/github/pull/149445 {% endcomment %}' - - 'La visita a la sección *Explorar* ha generado un error interno del servidor 500. {% comment %} https://github.com/github/github/pull/150512, https://github.com/github/github/pull/150504 {% endcomment %}' - - 'Las incidencias no se han podido clasificar por *Actualizadas recientemente* en los repositorios que migrados a una instancia nueva. {% comment %} https://github.com/github/github/pull/150688, https://github.com/github/github/pull/149330 {% endcomment %}' - - 'GitHub Connect utilizaba un punto de conexión de API de GitHub.com obsoleto. {% comment %} https://github.com/github/github/pull/150827, https://github.com/github/github/pull/150545 {% endcomment %}' - - 'La recolección de métricas internas para los trabajos en segundo plano ha contribuido al uso innecesario de memoria y CPU. {% comment %} https://github.com/github/github/pull/151182, https://github.com/github/github/pull/147695 {% endcomment %}' - - 'La página Error 404 contenía los enlaces de estado y contacto de GitHub.com en el pie de página. {% comment %} https://github.com/github/github/pull/151315 {% endcomment %}' - - 'Los trabajos en segundo plano para una característica sin publicar se han puesto en cola y se han dejado sin procesar. {% comment %} https://github.com/github/github/pull/151395, https://github.com/github/github/pull/146248 {% endcomment %}' - known_issues: - - 'En una instancia de GitHub Enterprise Server recién configurada sin ningún usuario, un atacante podría crear el primer usuario administrador. {% comment %} https://github.com/github/enterprise2/issues/1889 {% endcomment %}' - - 'Las reglas de cortafuegos personalizadas no se mantienen durante una actualización. {% comment %} https://github.com/github/enterprise2/issues/2823 {% endcomment %}' - - 'Los archivos supervisados de Git LFS [cargados desde la interface web](https://github.com/blog/2105-upload-files-to-your-repositories) se han agregado de forma incorrecta y directa al repositorio. {% comment %} https://github.com/github/github/issues/54684 {% endcomment %}' - - 'Las incidencias no se pueden cerrar si contienen un enlace permanente a un blob del mismo repositorio en el que la ruta es mayor de 255 caracteres. {% comment %} https://github.com/github/github/issues/107731 {% endcomment %}' - - 'Cuando se habilita "Los usuarios pueden buscar en GitHub.com" con GitHub Connect, las incidencias en los repositorios privados e internos no se incluyen en los resultados de la búsqueda de GitHub.com. {% comment %} https://github.com/github/admin-experience/issues/571 {% endcomment %}' - - 'Las alertas de seguridad no se notifican cuando se realiza la inserción en un repositorio en la línea de comandos. {% comment %} https://github.com/github/github/issues/143190 {% endcomment %}' - - 'Los registros de auditoría se pueden atribuir a 127.0.0.1 en lugar de a la dirección IP de origen real. (Actualizado el 02-11-2020) {% comment %} https://github.com/github/enterprise2/issues/21514 {% endcomment %}' - - "La configuración del permiso de un repositorio en \"Evaluación de errores\" o \"Mantenimiento\" genera un mensaje de error." - - 'Cuando un nodo de réplica está sin conexión en una configuración de disponibilidad alta, es posible que {% data variables.product.product_name %} todavía enrute las solicitudes a {% data variables.product.prodname_pages %} al nodo sin conexión, lo que reduce la disponibilidad de {% data variables.product.prodname_pages %} para los usuarios.' diff --git a/translations/es-ES/data/release-notes/enterprise-server/2-21/5.yml b/translations/es-ES/data/release-notes/enterprise-server/2-21/5.yml deleted file mode 100644 index 586b1e7403..0000000000 --- a/translations/es-ES/data/release-notes/enterprise-server/2-21/5.yml +++ /dev/null @@ -1,16 +0,0 @@ -date: '2020-08-12' -sections: - bugs: - - 'Se resolvió un problema que pudo haber desencadenado un uso elevado de CPU mientras se generaban las plantillas de configuración del sistema. {% comment %} https://github.com/github/enterprise2/pull/21786, https://github.com/github/enterprise2/pull/21741 {% endcomment %}' - - 'Los cambios recientes en las asignaciones de memoria podían provocan una degradación del rendimiento del sistema {% comment %} https://github.com/github/enterprise2/pull/22066 {% endcomment %}' - - 'Los problemas temporales de conectividad mientras se ejecutaban las migraciones de base de datos podían causar una pérdida de datos. {% comment %} https://github.com/github/enterprise2/pull/22128, https://github.com/github/enterprise2/pull/22100 {% endcomment %}' - known_issues: - - 'En una instancia de GitHub Enterprise Server recién configurada sin ningún usuario, un atacante podría crear el primer usuario administrador. {% comment %} https://github.com/github/enterprise2/issues/1889 {% endcomment %}' - - 'Las reglas de cortafuegos personalizadas no se mantienen durante una actualización. {% comment %} https://github.com/github/enterprise2/issues/2823 {% endcomment %}' - - 'Los archivos supervisados de Git LFS [cargados desde la interfaz web](https://github.com/blog/2105-upload-files-to-your-repositories) se agregan de forma incorrecta y directa al repositorio. {% comment %} https://github.com/github/github/issues/54684 {% endcomment %}' - - 'Las incidencias no se pueden cerrar si contienen un enlace permanente a un blob del mismo repositorio en el que la ruta es mayor de 255 caracteres. {% comment %} https://github.com/github/github/issues/107731 {% endcomment %}' - - 'Cuando se habilita "Los usuarios pueden buscar en GitHub.com" con GitHub Connect, las incidencias en los repositorios privados e internos no se incluyen en los resultados de la búsqueda de GitHub.com. {% comment %} https://github.com/github/admin-experience/issues/571 {% endcomment %}' - - 'Las alertas de seguridad no se notifican cuando se realiza la inserción en un repositorio en la línea de comandos. {% comment %} https://github.com/github/github/issues/143190 {% endcomment %}' - - 'Los registros de auditoría se pueden atribuir a 127.0.0.1 en lugar de a la dirección IP de origen real. (Actualizado el 02-11-2020) {% comment %} https://github.com/github/enterprise2/issues/21514 {% endcomment %}' - - "La configuración del permiso de un repositorio en \"Evaluación de errores\" o \"Mantenimiento\" genera un mensaje de error." - - 'Cuando un nodo de réplica está sin conexión en una configuración de disponibilidad alta, es posible que {% data variables.product.product_name %} enrute las solicitudes a {% data variables.product.prodname_pages %} al nodo sin conexión, lo que reduce la disponibilidad de {% data variables.product.prodname_pages %} para los usuarios.' diff --git a/translations/es-ES/data/release-notes/enterprise-server/2-21/6.yml b/translations/es-ES/data/release-notes/enterprise-server/2-21/6.yml deleted file mode 100644 index c9ef772868..0000000000 --- a/translations/es-ES/data/release-notes/enterprise-server/2-21/6.yml +++ /dev/null @@ -1,28 +0,0 @@ -date: '2020-08-26' -sections: - security_fixes: - - >- - {% octicon "alert" aria-label="The alert icon" %} **Critical:** A remote code execution vulnerability was identified in GitHub Pages that could be exploited when building a GitHub Pages site. User-controlled configuration of the underlying parsers used by GitHub Pages were not sufficiently restricted and made it possible to execute commands on the GitHub Enterprise Server instance. To exploit this vulnerability, an attacker would need permission to create and build a GitHub Pages site on the GitHub Enterprise Server instance. This vulnerability affected all versions of GitHub Enterprise Server. The underlying issues contributing to this vulnerability were identified both internally and through the GitHub Security Bug Bounty program. We have issued CVE-2020-10518. {% comment %} https://github.com/github/pages/pull/2882, https://github.com/github/pages/pull/2902, https://github.com/github/pages/pull/2894, https://github.com/github/pages/pull/2877, https://github.com/github/pages-gem/pull/700, - https://github.com/github/pages/pull/2889, https://github.com/github/pages/pull/2899, https://github.com/github/pages/pull/2903, https://github.com/github/pages/pull/2890, https://github.com/github/pages/pull/2891, https://github.com/github/pages/pull/2884 {% endcomment %} - - '**Medium:** An improper access control vulnerability was identified that allowed authenticated users of the instance to determine the names of unauthorized private repositories given their numerical IDs. This vulnerability did not allow unauthorized access to any repository content besides the name. This vulnerability affected all versions of GitHub Enterprise Server prior to 2.22 and has been assigned [CVE-2020-10517](https://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2020-10517). The vulnerability was reported via the [GitHub Bug Bounty program](https://bounty.github.com). {% comment %} https://github.com/github/github/pull/151986, https://github.com/github/github/pull/151713 {% endcomment %}' - - 'Packages have been updated to the latest security versions. {% comment %} https://github.com/github/enterprise2/pull/21853, https://github.com/github/enterprise2/pull/21828, https://github.com/github/enterprise2/pull/22154, https://github.com/github/enterprise2/pull/21920, https://github.com/github/enterprise2/pull/22216, https://github.com/github/enterprise2/pull/22190 {% endcomment %}' - bugs: - - 'A message was not logged when the ghe-config-apply process had finished running ghe-es-auto-expand. {% comment %} https://github.com/github/enterprise2/pull/22178, https://github.com/github/enterprise2/pull/22171 {% endcomment %}' - - 'Excessive logging to the `syslog` file could occur on high-availability replicas if the primary appliance is unavailable. {% comment %} https://github.com/github/enterprise2/pull/22268, https://github.com/github/enterprise2/pull/22124 {% endcomment %}' - - "Database re-seeding on a replica could fail with an error: `Got packet bigger than 'max_allowed_packet'` {% comment %} https://github.com/github/enterprise2/pull/22322, https://github.com/github/enterprise2/pull/20063 {% endcomment %}" - - 'In some cases duplicate user data could cause a 500 error while running the ghe-license-usage script. {% comment %} https://github.com/github/github/pull/152637 {% endcomment %}' - - 'Using `ghe-migrator`, the `add` command would fail to lock a repository when using the `--lock` flag. {% comment %} https://github.com/github/github/pull/152780, https://github.com/github/github/pull/152588 {% endcomment %}' - changes: - - 'In a high availability or geo-replication configuration, replica instances would exit maintenance mode when ghe-config-apply ran. {% comment %} https://github.com/github/enterprise2/pull/21777, https://github.com/github/enterprise2/pull/21440 {% endcomment %}' - - "We've added support for the R5a and R5n AWS instance types. {% comment %} https://github.com/github/enterprise2/pull/21903, https://github.com/github/enterprise2/pull/21173 {% endcomment %}" - - 'Removed the license seat count information on the administrative SSH MOTD due to a performance issue impacting GitHub Enterprise Server clusters. {% comment %} https://github.com/github/enterprise2/pull/21994, https://github.com/github/enterprise2/pull/21870 {% endcomment %}' - known_issues: - - 'On a freshly set up GitHub Enterprise Server without any users, an attacker could create the first admin user. {% comment %} https://github.com/github/enterprise2/issues/1889 {% endcomment %}' - - 'Custom firewall rules are not maintained during an upgrade. {% comment %} https://github.com/github/enterprise2/issues/2823 {% endcomment %}' - - '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. {% comment %} https://github.com/github/github/issues/54684 {% endcomment %}' - - '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. {% comment %} https://github.com/github/github/issues/107731 {% endcomment %}' - - '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. {% comment %} https://github.com/github/admin-experience/issues/571 {% endcomment %}' - - 'Security alerts are not reported when pushing to a repository on the command line. {% comment %} https://github.com/github/github/issues/143190 {% endcomment %}' - - 'Audit logs may be attributed to 127.0.0.1 instead of the actual source IP address. (updated 2020-11-02) {% comment %} https://github.com/github/enterprise2/issues/21514 {% endcomment %}' - - "Configuring a repository's permission to `Triage` or `Maintain` fails with an error message." - - '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.' diff --git a/translations/es-ES/data/release-notes/enterprise-server/2-21/7.yml b/translations/es-ES/data/release-notes/enterprise-server/2-21/7.yml deleted file mode 100644 index c7cd3e632f..0000000000 --- a/translations/es-ES/data/release-notes/enterprise-server/2-21/7.yml +++ /dev/null @@ -1,15 +0,0 @@ -date: '2020-09-08' -sections: - bugs: - - 'Una revisión del estado del servicio provocaba un crecimiento de la sesión que resultaba en el agotamiento del inode del sistema de archivos. {% comment %} https://github.com/github/enterprise2/pull/22481, https://github.com/github/enterprise2/pull/22475 {% endcomment %}' - - 'La realización de mejoras utilizando hotpatches podía fallar con un error de tipo `''libdbi1'' was not found` {% comment %} https://github.com/github/enterprise2/pull/22556, https://github.com/github/enterprise2/pull/22552 {% endcomment %}' - - 'La configuración del permiso de un repositorio en `Triage` o `Maintain` ya no genera fallos.' - known_issues: - - "En una instancia de GitHub\_Enterprise Server recién configurada sin ningún usuario, un atacante podría crear el primer usuario administrador. {% comment %} https://github.com/github/enterprise2/issues/1889 {% endcomment %}" - - 'Las reglas de cortafuegos personalizadas no se mantienen durante una actualización. {% comment %} https://github.com/github/enterprise2/issues/2823 {% endcomment %}' - - 'Los archivos supervisados de Git LFS [cargados desde la interfaz web](https://github.com/blog/2105-upload-files-to-your-repositories) se agregan de forma incorrecta y directa al repositorio. {% comment %} https://github.com/github/github/issues/54684 {% endcomment %}' - - "Las incidencias no se pueden cerrar si contienen un enlace permanente a un blob del mismo repositorio en el que la ruta es mayor de 255\_caracteres. {% comment %} https://github.com/github/github/issues/107731 {% endcomment %}" - - 'Cuando se habilita "Los usuarios pueden buscar en GitHub.com" con GitHub Connect, las incidencias en los repositorios privados e internos no se incluyen en los resultados de la búsqueda de GitHub.com. {% comment %} https://github.com/github/admin-experience/issues/571 {% endcomment %}' - - 'Las alertas de seguridad no se notifican cuando se realiza la inserción en un repositorio en la línea de comandos. {% comment %} https://github.com/github/github/issues/143190 {% endcomment %}' - - 'Los registros de auditoría se pueden atribuir a 127.0.0.1 en lugar de a la dirección IP de origen real. (Actualizado el 02-11-2020) {% comment %} https://github.com/github/enterprise2/issues/21514 {% endcomment %}' - - 'Cuando un nodo de réplica está sin conexión en una configuración de disponibilidad alta, es posible que {% data variables.product.product_name %} enrute las solicitudes a {% data variables.product.prodname_pages %} al nodo sin conexión, lo que reduce la disponibilidad de {% data variables.product.prodname_pages %} para los usuarios.' diff --git a/translations/es-ES/data/release-notes/enterprise-server/2-21/8.yml b/translations/es-ES/data/release-notes/enterprise-server/2-21/8.yml deleted file mode 100644 index 8ba8902f82..0000000000 --- a/translations/es-ES/data/release-notes/enterprise-server/2-21/8.yml +++ /dev/null @@ -1,16 +0,0 @@ -date: '2020-09-23' -sections: - security_fixes: - - '**MEDIO**: ImageMagick se actualizó a la dirección [DSA-4715-1](https://www.debian.org/security/2020/dsa-4715). {% comment %} https://github.com/github/enterprise2/pull/22621, https://github.com/github/enterprise2/pull/22610 {% endcomment %}' - - 'Se actualizaron los paquetes a las últimas versiones de seguridad. {% comment %} https://github.com/github/enterprise2/pull/22571, https://github.com/github/enterprise2/pull/22426, https://github.com/github/enterprise2/pull/22602, https://github.com/github/enterprise2/pull/22592, https://github.com/github/enterprise2/pull/22719, https://github.com/github/enterprise2/pull/22699 {% endcomment %}' - bugs: - - 'Los administradores no pudieron ver los webhooks de repositorio que se entregaron y vieron la leyenda "Sorry, something went wrong and we weren''t able to fetch the deliveries for this hook" en su lugar. {% comment %} https://github.com/github/authzd/pull/1181, https://github.com/github/authzd/pull/980 {% endcomment %}' - known_issues: - - "En una instancia de GitHub\_Enterprise Server recién configurada sin ningún usuario, un atacante podría crear el primer usuario administrador. {% comment %} https://github.com/github/enterprise2/issues/1889 {% endcomment %}" - - 'Las reglas de cortafuegos personalizadas no se mantienen durante una actualización. {% comment %} https://github.com/github/enterprise2/issues/2823 {% endcomment %}' - - 'Los archivos supervisados de Git LFS [cargados desde la interface web](https://github.com/blog/2105-upload-files-to-your-repositories) se han agregado de forma incorrecta y directa al repositorio. {% comment %} https://github.com/github/github/issues/54684 {% endcomment %}' - - "Las incidencias no se pueden cerrar si contienen un enlace permanente a un blob del mismo repositorio en el que la ruta es mayor de 255\_caracteres. {% comment %} https://github.com/github/github/issues/107731 {% endcomment %}" - - 'Cuando se habilita "Los usuarios pueden buscar en GitHub.com" con GitHub Connect, las incidencias en los repositorios privados e internos no se incluyen en los resultados de la búsqueda de GitHub.com. {% comment %} https://github.com/github/admin-experience/issues/571 {% endcomment %}' - - 'Las alertas de seguridad no se notifican cuando se realiza la inserción en un repositorio en la línea de comandos. {% comment %} https://github.com/github/github/issues/143190 {% endcomment %}' - - 'Los registros de auditoría se pueden atribuir a 127.0.0.1 en lugar de a la dirección IP de origen real. (Actualizado el 02-11-2020) {% comment %} https://github.com/github/enterprise2/issues/21514 {% endcomment %}' - - 'Cuando un nodo de réplica está sin conexión en una configuración de disponibilidad alta, es posible que {% data variables.product.product_name %} enrute las solicitudes a {% data variables.product.prodname_pages %} al nodo sin conexión, lo que reduce la disponibilidad de {% data variables.product.prodname_pages %} para los usuarios.' diff --git a/translations/es-ES/data/release-notes/enterprise-server/2-21/9.yml b/translations/es-ES/data/release-notes/enterprise-server/2-21/9.yml deleted file mode 100644 index 0f2d081581..0000000000 --- a/translations/es-ES/data/release-notes/enterprise-server/2-21/9.yml +++ /dev/null @@ -1,29 +0,0 @@ -date: '2020-10-09' -sections: - security_fixes: - - 'Un usuario cuyo nombre de usuario del directorio de **LDAP** se estandarizaba a una información de inicio de sesión de cuenta de GHES podía autenticarse en la cuenta existente. {% comment %} https://github.com/github/github/pull/156517, https://github.com/github/github/pull/155512 {% endcomment %}' - - 'Los paquetes se han actualizado a sus últimas versiones de seguridad. {% comment %} https://github.com/github/enterprise2/pull/22911, https://github.com/github/enterprise2/pull/22878 {% endcomment %}' - bugs: - - 'El menú desplegable Formato de NameID en la consola de administración se restablecía a "sin especificar" después de establecerlo en "persistente". {% comment %} https://github.com/github/enterprise2/pull/22402, https://github.com/github/enterprise2/pull/22331, https://github.com/github/enterprise2/issues/13446 {% endcomment %}' - - 'La configuración de guardado a través de la [consola de administración](/admin/configuration/accessing-the-management-console) añadía una línea nueva a los archivos de [certificado y llave TLS/SSL](/admin/configuration/configuring-tls), que activaban la recarga innecesaria de algunos servicios. {% comment %} https://github.com/github/enterprise2/pull/22608, https://github.com/github/enterprise2/pull/22540 {% endcomment %}' - - 'Las bitácoras de sistema para la gráfica de dependencias no rotaban, lo cual produjo un crecimiento desmedido del almacenamiento. {% comment %} https://github.com/github/enterprise2/pull/22766, https://github.com/github/enterprise2/pull/22733 {% endcomment %}' - - 'La mejora podía fallar si los roles de trabajo que se volvían a poner en cola (resqued) invalidaban la configuración que se estaba utilizando. {% comment %} https://github.com/github/enterprise2/pull/22838, https://github.com/github/enterprise2/pull/22814 {% endcomment %}' - - 'Cuando se importaba un repositorio con un `ghe-migrator`, podía producirse una excepción inesperada cuando había datos inconsistentes. {% comment %} https://github.com/github/github/pull/153849, https://github.com/github/github/pull/151552 {% endcomment %}' - - 'Los enlaces a los avisos de seguridad de GitHub utilizaban una URL con el nombre de host de la instancia de GitHub Enterprise Server en vez de la de GitHub.com, lo cual dirigía al usuario a una URL inexistente. {% comment %} https://github.com/github/github/pull/153853, https://github.com/github/github/pull/151301 {% endcomment %}' - - 'La página de configuración de seguridad para cuentas empresariales mostraba un enlace para "Visualizar las configuraciones actuales de tus organizaciones" en el ajuste de "autenticación bifactorial" cuando el modo de autenticación no era compatible con la autenticación bifactorial integrada. {% comment %} https://github.com/github/github/pull/153861 {% endcomment %}' - - 'Cuando se utilizaba `ghe-migrator` para importar las solicitudes de revisión de PR, los registros asociados con los usuarios borrados generaban registros de una base de datos extraña. {% comment %} https://github.com/github/github/pull/154959, https://github.com/github/github/pull/153169 {% endcomment %}' - - 'Cuando se importaban usuarios con `ghe-migrator`, se producía un error de tipo "El correo electrónico no es válido" si la dirección de correo electrónico que generaba el sistema tenía una longitud superior a 100 caracteres. {% comment %} https://github.com/github/github/pull/155110, https://github.com/github/github/pull/152418 {% endcomment %}' - - 'Al registrar la actividad de los webhooks, podían utilizarse grandes cantidades de espacio en disco y provocar que el disco raíz se llenara. {% comment %} https://github.com/github/github/pull/155656, https://github.com/github/github/pull/154100 {% endcomment %}' - changes: - - 'Se ha agregado compatibilidad con el tipo de instancia `m5.16xlarge` de AWS EC2. {% comment %} https://github.com/github/enterprise2/pull/22501, https://github.com/github/enterprise2/pull/22473 {% endcomment %}' - - 'Se ha eliminado el requisito de las huellas dactilares de SSH en los archivos de `ghe-migrator`, ya que siempre se puede calcular. {% comment %} https://github.com/github/github/pull/156945, https://github.com/github/github/pull/155387 {% endcomment %}' - - 'Los manifiestos de las GitHub Apps ahora incluyen el campo `request_oauth_on_install`. {% comment %} https://github.com/github/github/pull/156994, https://github.com/github/github/pull/155010, https://github.com/github/ecosystem-apps/issues/1055 {% endcomment %}' - known_issues: - - "En una instancia de GitHub\_Enterprise Server recién configurada sin ningún usuario, un atacante podría crear el primer usuario administrador. {% comment %} https://github.com/github/enterprise2/issues/1889 {% endcomment %}" - - 'Las reglas de cortafuegos personalizadas no se mantienen durante una actualización. {% comment %} https://github.com/github/enterprise2/issues/2823 {% endcomment %}' - - 'Los archivos supervisados de Git LFS [cargados desde la interfaz web](https://github.com/blog/2105-upload-files-to-your-repositories) se agregan de forma incorrecta y directa al repositorio. {% comment %} https://github.com/github/github/issues/54684 {% endcomment %}' - - "Las incidencias no se pueden cerrar si contienen un enlace permanente a un blob del mismo repositorio en el que la ruta es mayor de 255\_caracteres. {% comment %} https://github.com/github/github/issues/107731 {% endcomment %}" - - 'Cuando se habilita "Los usuarios pueden buscar en GitHub.com" con GitHub Connect, las incidencias en los repositorios privados e internos no se incluyen en los resultados de la búsqueda de GitHub.com. {% comment %} https://github.com/github/admin-experience/issues/571 {% endcomment %}' - - 'Las alertas de seguridad no se notifican cuando se realiza la inserción en un repositorio en la línea de comandos. {% comment %} https://github.com/github/github/issues/143190 {% endcomment %}' - - 'Los registros de auditoría se pueden atribuir a 127.0.0.1 en lugar de a la dirección IP de origen real. (Actualizado el 02-11-2020) {% comment %} https://github.com/github/enterprise2/issues/21514 {% endcomment %}' - - 'Cuando un nodo de réplica está sin conexión en una configuración de disponibilidad alta, es posible que {% data variables.product.product_name %} enrute las solicitudes a {% data variables.product.prodname_pages %} al nodo sin conexión, lo que reduce la disponibilidad de {% data variables.product.prodname_pages %} para los usuarios.' diff --git a/translations/es-ES/data/release-notes/enterprise-server/2-22/0.yml b/translations/es-ES/data/release-notes/enterprise-server/2-22/0.yml deleted file mode 100644 index 8525a93483..0000000000 --- a/translations/es-ES/data/release-notes/enterprise-server/2-22/0.yml +++ /dev/null @@ -1,143 +0,0 @@ -intro: GitHub is excited to present GitHub Enterprise Server 2.22.0. -date: '2020-09-23' -sections: - features: - - heading: GitHub Actions Beta - notes: - - | - [GitHub Actions](https://github.com/features/actions) is a powerful, flexible solution for CI/CD and workflow automation. GitHub Actions on Enterprise Server includes tools to help you manage the service, including key metrics in the Management Console, audit logs and access controls to help you control the roll out. - - You will need to provide your own [storage](https://docs.github.com/en/enterprise/2.22/admin/github-actions/enabling-github-actions-and-configuring-storage) and runners for GitHub Actions. AWS S3, Azure Blob Storage and MinIO are supported. Please review the [updated minimum requirements for your platform](https://docs.github.com/en/enterprise/2.22/admin/installation/setting-up-a-github-enterprise-server-instance) before you turn on GitHub Actions. To learn more, contact the GitHub Sales team or [sign up for the beta](https://resources.github.com/beta-signup/). {% comment %} https://github.com/github/releases/issues/775 {% endcomment %} - - - heading: GitHub Packages Beta - notes: - - | - [GitHub Packages](https://github.com/features/packages) is a package hosting service, natively integrated with GitHub APIs, Actions, and webhooks. Create an [end-to-end DevOps workflow](https://docs.github.com/en/enterprise/2.22/admin/packages/configuring-packages-support-for-your-enterprise) that includes your code, continuous integration, and deployment solutions. - - Supported storage back ends include AWS S3 and MinIO with support for Azure blob coming in a future release. Please note that the current Docker support will be replaced by a beta of the new GitHub Container Registry in the next release. Please review the [updated minimum requirements for your platform](https://docs.github.com/en/enterprise/2.22/admin/installation/setting-up-a-github-enterprise-server-instance) before you turn on GitHub Packages. To learn more, contact the GitHub Sales team or [sign up for the beta](https://resources.github.com/beta-signup/). {% comment %} https://github.com/github/releases/issues/773 {% endcomment %} - - - heading: Advanced Security Code Scanning Beta - notes: - - | - [GitHub Advanced Security code scanning](https://github.com/features/security) is a developer-first, GitHub-native static application security testing (SAST). Easily find security vulnerabilities before they reach production, all powered by the world’s most powerful code analysis engine: CodeQL. - - Administrators using GitHub Advanced Security can [sign up for](https://resources.github.com/beta-signup/) and [enable](https://docs.github.com/en/enterprise/2.22/admin/configuration/configuring-code-scanning-for-your-appliance) GitHub Advanced Security code scanning beta. Please review the [updated minimum requirements for your platform](https://docs.github.com/en/enterprise/2.22/admin/installation/setting-up-a-github-enterprise-server-instance) before you turn on GitHub Advanced Security code scanning. {% comment %} https://github.com/github/releases/issues/768 {% endcomment %} - - - heading: Pull Request Retargeting - notes: - - | - When a [pull request's head branch](https://docs.github.com/en/enterprise/2.22/user/github/collaborating-with-issues-and-pull-requests/about-branches#working-with-branches) is merged and deleted, all other open pull requests in the same repository that target this branch are now retargeted to the merged pull request's base branch. Previously these pull requests were closed. {% comment %} https://github.com/github/releases/issues/801 {% endcomment %} - - - heading: Suspend and Unsuspend an App Installation - notes: - - | - Administrators and users can [suspend any GitHub App’s access](https://docs.github.com/enterprise/2.22/user/rest/reference/apps#suspend-an-app-installation) for as long as needed, and [unsuspend the app](https://docs.github.com/enterprise/2.22/user/rest/reference/apps#unsuspend-an-app-installation) on command through Settings and the API. Suspended apps cannot access the GitHub API or webhook events. You can use this instead of uninstalling an application, which deauthorises every user. {% comment %} https://github.com/github/github/pull/138316 https://github.com/github/github/pull/150869 {% endcomment %}'' - - - heading: Improved Large Scale Performance - notes: - - | - We have revised the approach we take to scheduling network maintenance for repositories, ensuring large monorepos are able to avoid failure states. {% comment %} https://github.com/github/github/pull/146789, https://github.com/github/github/pull/147931, https://github.com/github/github/pull/146724, https://github.com/github/git-protocols/issues/94 {% endcomment %}'' - - Passive replicas are now [supported and configurable on GitHub Enterprise Server cluster deployments](https://docs.github.com/en/enterprise/2.22/admin/enterprise-management/configuring-high-availability-replication-for-a-cluster). These changes will enable faster failover, reducing RTO and RPO. {% comment %} https://github.com/github/releases/issues/905 {% endcomment %} - - - heading: View All of Your Users - notes: - - | - For exceptionally large teams, administrators can [adjust the 1,500 default maximum for user lists](https://docs.github.com/en/enterprise/2.22/admin/configuration/command-line-utilities#ghe-config). {% comment %} https://github.com/github/github/pull/146508 {% endcomment %}'' - - changes: - - heading: Administration Changes - notes: - - Shared workers have been enabled to make live updates more resilient by sharing connections across tabs. {% comment %} https://github.com/github/releases/issues/914 {% endcomment %} - - The "Contact Support" link on `50x` error pages now links to the support email or link configured in the Management Console. {% comment %} https://github.com/github/github/pull/142123 {% endcomment %} - - It's now possible to [manage global announcements and expiration dates through the enterprise account settings](https://docs.github.com/en/enterprise/2.22/admin/installation/command-line-utilities#ghe-announce). {% comment %} https://github.com/github/releases/issues/945, https://github.com/github/github/pull/148475, https://github.com/github/github/pull/148494 {% endcomment %} - - You can now [exempt certain users from the default API rate limits configured in the management console](https://docs.github.com/en/enterprise/2.22/admin/configuration/configuring-rate-limits), if necessary. {% comment %} https://github.com/github/github/pull/148673 {% endcomment %} - - Repository administrators can now [set their repository to any available visibility option](https://docs.github.com/en/enterprise/2.22/user/github/administering-a-repository/setting-repository-visibility) from a single dialog in the repository's settings. Previously, you had to navigate separate sections, buttons, and dialog boxes for changing between public and private and between private and internal. {% comment %} https://github.com/github/releases/issues/882 {% endcomment %} - - A new Enterprise settings link on the user dropdown menu makes it easier to navigate to Enterprise Account Settings. {% comment %} https://github.com/github/releases/issues/946, https://github.com/github/github/pull/150595, https://github.com/github/github/pull/150520, https://github.com/github/github/pull/151121, https://github.com/github/hydro-schemas/pull/1244 {% endcomment %} - - The legacy "Admin Center" link on the /stafftools page has been removed. The "Enterprise" link is now the best way to navigate to the Enterprise Account from the /stafftools page. {% comment %} https://github.com/github/github/pull/147633 {% endcomment %} - - The Options sub-menu item in the Enterprise Account settings has been moved from the Settings section to the Policies section. {% comment %} https://github.com/github/releases/issues/944, https://github.com/github/github/pull/148477 {% endcomment %} - - '[Accessing resources by using a personal access token or SSH key now counts as user activity](https://docs.github.com/en/enterprise/2.22/admin/user-management/managing-dormant-users). This relieves administrators from the burden of filtering out certain users from the user dormancy reports and makes it safer to use the "Suspend all" button without accidentally suspending users who only accessed GitHub in a read-only way over the APIs with a Personal Access Token (PAT) or SSH key. {% comment %} https://github.com/github/github/pull/140433, https://github.com/github/help-docs/pull/14853, https://github.com/github/customer-feedback/issues/174, https://github.com/github/supportability/issues/14 {% endcomment %}' - - - heading: Security Changes - notes: - - Two-factor recovery codes can no longer be used during the two-factor sign in process. One-Time-Passwords are the only acceptable values. {% comment %} https://github.com/github/github/pull/145016, https://github.com/github/github/pull/140208 {% endcomment %} - - When a user is signed into GitHub Enterprise Server through single sign-on, the [default repository visibility selection is Private](https://docs.github.com/en/enterprise/2.22/user/github/administering-a-repository/setting-repository-visibility). {% comment %} https://github.com/github/releases/issues/872 {% endcomment %} - - Owners of GitHub Apps can now choose to have their [user-to-server access tokens expire after 8 hours](https://developer.github.com/changes/2020-04-30-expiring-user-to-server-access-tokens-for-github-apps/), to help enforce regular token rotation and reduce the impact of a compromised token. {% comment %} https://github.com/github/releases/issues/966 {% endcomment %} - - - heading: Developer Changes - notes: - - '[The GitHub UI has undergone a design refresh](https://github.blog/changelog/2020-06-23-design-updates-to-repositories-and-github-ui/), and the repositories homepage has been redesigned, including a responsive layout and improved mobile web experience. {% comment %} https://github.com/github/releases/issues/886 {% endcomment %}' - - In the "Clone with SSH" repository dropdown menu, users will now be notified if they do not have any keys setup. {% comment %} https://github.com/github/github/pull/149098 {% endcomment %} - - Commits are now ordered chronologically in the pull request timeline and commits tab. This new ordering is also reflected in the ["List commits on a pull request"](https://docs.github.com/en/enterprise/2.22/user/rest/reference/pulls#list-commits-on-a-pull-request) REST API and GraphQL ["PullRequest object"](https://docs.github.com/en/enterprise/2.22/user/graphql/reference/objects#pullrequest) timeline connection. {% comment %} https://github.com/github/releases/issues/867 {% endcomment %} - - Users can now [set a skin tone default for emoji autocomplete results](https://github.blog/changelog/2020-07-17-customizable-skin-tones-in-emoji-autocomplete/) in comment text areas. {% comment %} https://github.com/github/releases/issues/916 {% endcomment %} - - '[Tree-sitter](https://github.com/tree-sitter/tree-sitter) improves syntax highlighting and is now the default library used for language parsing. {% comment %} https://github.com/github/releases/issues/918, https://github.com/github/windrose/issues/44 {% endcomment %}' - - - heading: Users and organizations can add Twitter usernames to their GitHub profiles - notes: - - '[Developers and organizations can now add their Twitter username to their profile](https://github.blog/changelog/2020-07-22-users-and-organizations-can-now-add-twitter-usernames-to-their-github-profiles/) {% comment %} https://github.com/github/github/pull/145127 {% endcomment %}' - - - heading: API Changes - notes: - - | - #### Graduated Previews - - The following previews are now an official part of the API: - * The GitHub Apps API and endpoints that returned the `performed_via_github_app` property no longer require the [`machine-man`](https://developer.github.com/changes/2020-08-20-graduate-machine-man-and-sailor-v-previews/) preview header. {% comment %} https://github.com/github/releases/issues/965 {% endcomment %} - * To add and view a lock reason to an issue, you no longer need to use the [`sailor-v`](https://developer.github.com/changes/2020-08-20-graduate-machine-man-and-sailor-v-previews/) preview header. {% comment %} https://github.com/github/github/pull/143676 {% endcomment %} - - - | - #### GraphQL Schema Changes - - * [The GraphQL schema changes](https://docs.github.com/enterprise/2.22/user/graphql/overview/changelog) include backwards-compatible changes, schema previews, and upcoming breaking changes. - - - heading: VMware Network Driver Changes - notes: - - | - The GitHub Enterprise Server default network adapter type for VMware customers has been changed from E1000 to VMXNET3, starting with release 2.22.0. When upgrading from an earlier release to 2.22.0 or newer, if an E1000 network adapter is detected during the pre-upgrade check, the following message will be displayed at the command line: - - ``` - WARNING: Your virtual appliance is currently using an emulated Intel E1000 network adapter. - For optimal performance, please update the virtual machine configuration on your VMware host to use the VMXNET3 driver. - Proceed with installation? [y/N] - ``` - - The administrator can choose to update the network adapter type to VMXNET3 either before or after the GitHub Enterprise Server upgrade. The virtual appliance will need to be shutdown for this change. Customers should follow the VMware recommended steps for [changing the virtual machine network adapter configuration](https://docs.vmware.com/en/VMware-vSphere/7.0/com.vmware.vsphere.vm_admin.doc/GUID-3719A0BE-4B4A-44FF-8A21-290950918FBD.html) to VMXNET3. Please note that `VMXNET3` will not be an option if the OS version for the virtual appliance is set to `Other Linux (64-bit)`. In that case, the OS version would first need to be changed from `Other Linux (64-bit)` to `Other 2.6.x Linux (64-bit)` or if available, `Debian GNU/Linux 9` . We recommend testing these changes on a [staging instance](https://docs.github.com/en/enterprise-server@2.22/admin/installation/setting-up-a-staging-instance) before it is performed on a production GitHub Enterprise Server. {% comment %} https://github.com/github/ghes-infrastructure/issues/781 {% endcomment %} - - bugs: - - The stafftools page for viewing pending collaborator showed a `500 Internal Server Error` when there was a pending email invite. {% comment %} https://github.com/github/github/pull/150836 {% endcomment %} - - The Repository Health Check in stafftools could give incorrect results on busy repositories. {% comment %} https://github.com/github/github/pull/151160 {% endcomment %} - - A logged in user trying to accept an email invitation could get a `404 Not Found` error. {% comment %} https://github.com/github/github/pull/150848 {% endcomment %} - - If a user navigated to a repository whose name started with "repositories.", they were redirected to the owner's "Repositories" tab instead of landing on the repository overview page. {% comment %} https://github.com/github/github/pull/149704 {% endcomment %} - - Labels in the dashboard timeline did not have enough contrast. {% comment %} https://github.com/github/github/pull/146749 {% endcomment %} - - deprecations: - - heading: Upcoming Deprecation of GitHub Enterprise Server 2.19 - notes: - - '**GitHub Enterprise Server 2.19 will be 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 GitHub Enterprise 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 GitHub Enterprise Server 2.21.0 two legacy GitHub Apps-related webhook events have been deprecated and will be removed in GitHub Enterprise Server 2.25.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/). {% comment %} https://github.com/github/enterprise-web/pull/6419#issuecomment-668303461 {% endcomment %} - - heading: Deprecation of Legacy GitHub Apps Endpoint - notes: - - Starting with GitHub Enterprise Server 2.21.0 the legacy GitHub Apps endpoint for creating installation access tokens was deprecated and will be removed in GitHub Enterprise Server 2.25.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/). {% comment %} https://github.com/github/enterprise-web/pull/6419#issuecomment-668303461 {% endcomment %} - - 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 GitHub Enterprise Server 3.4. For more information, see the [deprecation announcement blog post](https://developer.github.com/changes/2020-02-14-deprecating-oauth-app-endpoint/). - - backups: - - GitHub Enterprise Server 2.22 requires at least [GitHub Enterprise Backup Utilities](https://github.com/github/backup-utils) 2.22.0 for [Backups and Disaster Recovery](https://help.github.com/enterprise/2.22/admin/guides/installation/backups-and-disaster-recovery/). - - known_issues: - - On a freshly set up GitHub Enterprise Server without any users, an attacker could create the first admin user. {% comment %} https://github.com/github/enterprise2/issues/1889 {% endcomment %} - - Custom firewall rules are not maintained during an upgrade. {% comment %} https://github.com/github/enterprise2/issues/2823 {% endcomment %} - - 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. {% comment %} https://github.com/github/github/issues/54684 {% endcomment %} - - 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. {% comment %} https://github.com/github/github/issues/107731 {% endcomment %} - - 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. {% comment %} https://github.com/github/admin-experience/issues/571 {% endcomment %} - - The Name ID Format dropdown in the Management Console resets to "unspecified" after setting instance to "persistent". {% comment %} https://github.com/github/enterprise2/issues/13446 {% endcomment %} - - The repository Settings page of a repository for a user or organization GitHub Pages sites will fail with a "500 Internal Server Error". {% comment %} https://github.com/github/github/issues/156183 {% endcomment %} - - Users may experience slower Git clone and fetch performance on an instance with high availability replicas due to reads being forwarded to a different node. {% comment %} https://github.com/github/spokesd/issues/746 {% endcomment %} - - '[Creating a GitHub App from a manifest](https://docs.github.com/en/enterprise/2.22/user/developers/apps/creating-a-github-app-from-a-manifest) fails. To work around this issue, users can follow the manual instructions for [creating a GitHub App](https://docs.github.com/en/enterprise/2.22/user/developers/apps/creating-a-github-app). {% comment %} https://github.com/github/enterprise2/issues/22849 {% endcomment %}' - - GitHub usernames may change unintentionally when using SAML authentication, if the GitHub username does not match the value of the attribute mapped to the `username` field in the Management Console. (updated 2020-10-08) {% comment %} https://github.com/github/external-identities/issues/335 {% endcomment %} - - On a freshly set up 2.22.0 instance or after upgrading to 2.22.0, the activity feed on an organization's dashboard will no longer update. (updated 2020-10-27) {% comment %}https://github.com/github/enterprise2/issues/23050{% endcomment %} - - Audit logs may be attributed to 127.0.0.1 instead of the actual source IP address. (updated 2020-11-02) {% comment %} https://github.com/github/enterprise2/issues/21514 {% endcomment %} - - 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. diff --git a/translations/es-ES/data/release-notes/enterprise-server/2-22/1.yml b/translations/es-ES/data/release-notes/enterprise-server/2-22/1.yml deleted file mode 100644 index 928b7fa41c..0000000000 --- a/translations/es-ES/data/release-notes/enterprise-server/2-22/1.yml +++ /dev/null @@ -1,74 +0,0 @@ -date: '2020-10-09' -sections: - security_fixes: - - '**MEDIUM**: ImageMagick has been updated to address [DSA-4715-1](https://www.debian.org/security/2020/dsa-4715). {% comment %} https://github.com/github/enterprise2/pull/22623, https://github.com/github/enterprise2/pull/22610 {% endcomment %}' - - 'Requests from a GitHub App integration to refresh an OAuth access token would be accepted if sent with a different, valid OAuth client ID and client secret than was used to create the refresh token. {% comment %} https://github.com/github/github/pull/154921, https://github.com/github/github/pull/154423, https://github.com/github/ecosystem-apps/issues/1066 {% endcomment %}' - - 'A user whose LDAP directory username standardizes to an existing GHES account login could authenticate into the existing account. {% comment %} https://github.com/github/github/pull/156513, https://github.com/github/github/pull/155512 {% endcomment %}' - - 'Packages have been updated to the latest security versions. {% comment %} https://github.com/github/enterprise2/pull/22912, https://github.com/github/enterprise2/pull/22878 {% endcomment %}' - - bugs: - - | - The NameID Format dropdown in the Management Console would be reset to "unspecified" after setting it to "persistent". {% comment %} https://github.com/github/enterprise2/pull/22376, https://github.com/github/enterprise2/pull/22331, https://github.com/github/enterprise2/issues/13446 {% endcomment %} - - | - Upgrading using a hotpatch could fail with an error: `'libdbi1' was not found` {% comment %} https://github.com/github/enterprise2/pull/22557, https://github.com/github/enterprise2/pull/22552 {% endcomment %} - - | - Saving settings via the [management console](/admin/configuration/accessing-the-management-console) would append a newline to the [TLS/SSL certificate and key](/admin/configuration/configuring-tls) files which triggered unnecessary reloading of some services. {% comment %} https://github.com/github/enterprise2/pull/22570, https://github.com/github/enterprise2/pull/22540 {% endcomment %} - - | - System logs for Dependency Graph were not rotating, allowing unbounded storage growth. {% comment %} https://github.com/github/enterprise2/pull/22767, https://github.com/github/enterprise2/pull/22733 {% endcomment %} - - | - The MS SQL Server performance graph showed statistics from the primary instance even when a replica was selected. {% comment %} https://github.com/github/enterprise2/pull/22778, https://github.com/github/enterprise2/pull/22750 {% endcomment %} - - | - `ghe-actions-precheck` would silently exit without running the storage checks if Actions was not enabled. {% comment %} https://github.com/github/enterprise2/pull/22787, https://github.com/github/enterprise2/pull/22742 {% endcomment %} - - | - Upgrade could fail if the resqued workers override setting is in use. {% comment %} https://github.com/github/enterprise2/pull/22836, https://github.com/github/enterprise2/pull/22814 {% endcomment %} - - | - Some services running in containers were not sending logs to the journal. {% comment %} https://github.com/github/enterprise2/pull/22994, https://github.com/github/enterprise2/pull/22518 {% endcomment %} - - | - Links to GitHub Security Advisories would use a URL with the hostname of the GitHub Enterprise Server instance instead of GitHub.com, directing the user to a nonexistent URL. {% comment %} https://github.com/github/github/pull/153316, https://github.com/github/github/pull/151301 {% endcomment %} - - | - When importing a repository with `ghe-migrator`, an unexpected exception could occur when inconsistent data is present. {% comment %} https://github.com/github/github/pull/153850, https://github.com/github/github/pull/151552 {% endcomment %} - - | - The enterprise account security settings page showed a "View your organizations' current configurations" link for the "Two-factor authentication" setting when the authentication mode in use does not support built in two-factor authentication. {% comment %} https://github.com/github/github/pull/153860 {% endcomment %} - - | - OAuth refresh tokens would be removed prematurely. {% comment %} https://github.com/github/github/pull/154271, https://github.com/github/github/pull/153694 {% endcomment %} - - | - Search repair tasks would generate exceptions during the migration phase of configuration. {% comment %} https://github.com/github/github/pull/154573, https://github.com/github/github/pull/153392 {% endcomment %} - - | - On the settings page for GitHub Apps, the "Beta Features" tab was not visible in some circumstances. {% comment %} https://github.com/github/github/pull/154612, https://github.com/github/github/pull/154417 {% endcomment %} - - | - When using `ghe-migrator` to import PR review requests, records associated with deleted users would result in extraneous database records. {% comment %} https://github.com/github/github/pull/154960, https://github.com/github/github/pull/153169 {% endcomment %} - - | - When importing users with `ghe-migrator`, an error of "Emails is invalid" would occur if the system-generated email address were longer than 100 characters. {% comment %} https://github.com/github/github/pull/155109, https://github.com/github/github/pull/152418 {% endcomment %} - - | - Logging webhook activity could use large amounts of disk space and cause the root disk to become full. {% comment %} https://github.com/github/github/pull/155657, https://github.com/github/github/pull/154100 {% endcomment %} - - | - Users experienced slower Git clone and fetch performance on an instance with high availability replicas due to reads being forwarded to a different node. {% comment %} https://github.com/github/github/pull/156195, https://github.com/github/github/pull/156016, https://github.com/github/spokesd/issues/746 {% endcomment %} - - | - The repository Settings page of a repository for a user or organization GitHub Pages sites would fail with a "500 Internal Server Error". {% comment %} https://github.com/github/github/pull/156439, https://github.com/github/github/issues/156183 {% endcomment %} - - | - Repository network maintenance operations could become stuck in a `running` state. {% comment %} https://github.com/github/github/pull/156669, https://github.com/github/github/pull/156036 {% endcomment %} - - | - A repository being deleted immediately after uploading a code scanning result could cause a stall in the processing of code scanning results for all repositories. {% comment %} https://github.com/github/github/pull/157063, https://github.com/github/github/pull/156437 {% endcomment %} - - | - When a large number of code scanning results were submitted at the same time, processing of batches could time out resulting in a stall in processing of code scanning results. {% comment %} https://github.com/github/github/pull/157065, https://github.com/github/github/pull/156462 {% endcomment %} - - | - [Creating a GitHub App from a manifest](https://docs.github.com/en/enterprise/2.22/user/developers/apps/creating-a-github-app-from-a-manifest) would fail. {% comment %} https://github.com/github/github/pull/157133, https://github.com/github/github/pull/156904, https://github.com/github/enterprise2/issues/22849 {% endcomment %} - - | - GitHub usernames were changed unintentionally when using SAML authentication, when the GitHub username did not match the value of the attribute mapped to the `username` field in the Management Console. {% comment %} https://github.com/github/github/pull/158131, https://github.com/github/github/pull/157936, https://github.com/github/external-identities/issues/335 {% endcomment %} - - changes: - - Support is added for the AWS EC2 instance type `m5.16xlarge`. {% comment %} https://github.com/github/enterprise2/pull/22502, https://github.com/github/enterprise2/pull/22473 {% endcomment %} - - Remove the requirement for SSH fingerprints in `ghe-migrator` archives as it can always be computed. {% comment %} https://github.com/github/github/pull/156946, https://github.com/github/github/pull/155387 {% endcomment %} - - GitHub App Manifests now include the `request_oauth_on_install` field. {% comment %} https://github.com/github/github/pull/156991, https://github.com/github/github/pull/155010, https://github.com/github/ecosystem-apps/issues/1055 {% endcomment %} - - known_issues: - - On a freshly set up GitHub Enterprise Server without any users, an attacker could create the first admin user. {% comment %} https://github.com/github/enterprise2/issues/1889 {% endcomment %} - - Custom firewall rules are not maintained during an upgrade. {% comment %} https://github.com/github/enterprise2/issues/2823 {% endcomment %} - - 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. {% comment %} https://github.com/github/github/issues/54684 {% endcomment %} - - 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. {% comment %} https://github.com/github/github/issues/107731 {% endcomment %} - - 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. {% comment %} https://github.com/github/admin-experience/issues/571 {% endcomment %} - - Configuration updates will fail when restoring data to a GitHub Actions-enabled instance if the original backup source did not have the feature enabled. {% comment %} https://github.com/github/c2c-actions-runtime/issues/915 {% endcomment %} - - GitHub Actions can fail to start up successfully if it was previously enabled on an instance running 2.22.0 and is upgraded to 2.22.1. (updated 2020-10-23) {% comment %} https://github.com/github/c2c-actions/issues/1680 {% endcomment %} - - On a freshly set up 2.22.1 instance or after upgrading to 2.22.1, the activity feed on an organization's dashboard will no longer update. (updated 2020-10-27) {% comment %}https://github.com/github/enterprise2/issues/23050{% endcomment %} - - Audit logs may be attributed to 127.0.0.1 instead of the actual source IP address. (updated 2020-11-02) {% comment %} https://github.com/github/enterprise2/issues/21514 {% endcomment %} - - 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. diff --git a/translations/es-ES/data/release-notes/enterprise-server/2-22/10.yml b/translations/es-ES/data/release-notes/enterprise-server/2-22/10.yml deleted file mode 100644 index d45792bfab..0000000000 --- a/translations/es-ES/data/release-notes/enterprise-server/2-22/10.yml +++ /dev/null @@ -1,16 +0,0 @@ -date: '2021-04-01' -sections: - security_fixes: - - "**ALTA:** Se ha identificado una vulnerabilidad de control de acceso incorrecta en GitHub\_Enterprise Server que permitía que tokens de acceso generados desde el [flujo de autenticación web] de una GitHub App (https://docs.github.com/en/developers/apps/identifying-and-authorizing-users-for-github-apps#web-application-flow) leyeran metadatos de repositorios privados mediante la API REST sin tener los permisos correctos asignados. Para aprovechar esta vulnerabilidad, un atacante tendría que crear una GitHub App en la instancia y hacer que el usuario la autorice mediante el flujo de autenticación web. Los metadatos de repositorio privado devueltos estarían limitados a repositorios propiedad del usuario identificado por el token. Esta vulnerabilidad afectaba a todas las versiones de GitHub\_Enterprise Server anteriores a la\_3.0.4 y se ha corregido en las versiones\_3.0.4, 2.22.10 y 2.21.18. Esta vulnerabilidad se ha asignado a CVE-2021-22865 y se ha notificado mediante [GitHub\_Bug Bounty Program](https://bounty.github.com)." - - 'Los paquetes se han actualizado a las últimas versiones de seguridad.' - bugs: - - 'Algunos servicios que daban la hora UTC de manera predeterminada no utilizaban la zona horaria definida en GitHub Enterprise 11.10.x o una versión anterior.' - - 'Los servicios no realizaban la transición a los nuevos archivos de bitácora como parte de la rotación de bitácoras, lo que generaba un aumento del uso de disco.' - - 'La etiqueta de los resultados de la búsqueda para los repositorios internos se mostraba como "Privada" en vez de como "Interna".' - known_issues: - - 'En un servidor de GitHub Enterprise recién configurado sin usuarios, un atacante podría crear el primer usuario administrador.' - - 'Las reglas de firewall personalizadas no se mantienen durante una actualización.' - - 'Los archivos rastreados de Git LFS [cargados a través de la interfaz web](https://github.com/blog/2105-upload-files-to-your-repositories) se agregan de forma incorrecta y directa al repositorio.' - - "Las incidencias no se pueden cerrar si contienen un vínculo permanente a un blob en el mismo repositorio en el que la ruta de acceso de archivo del blob tiene más de 255\_caracteres." - - 'Cuando se habilita "Los usuarios pueden buscar en GitHub.com" con GitHub Connect, las incidencias en los repositorios privados e internos no se incluyen en los resultados de la búsqueda de GitHub.com.' - - 'Cuando un nodo de réplica está sin conexión en una configuración de disponibilidad alta, es posible que {% data variables.product.product_name %} enrute las solicitudes a {% data variables.product.prodname_pages %} al nodo sin conexión, lo que reduce la disponibilidad de {% data variables.product.prodname_pages %} para los usuarios.' diff --git a/translations/es-ES/data/release-notes/enterprise-server/2-22/11.yml b/translations/es-ES/data/release-notes/enterprise-server/2-22/11.yml deleted file mode 100644 index c90c5347d9..0000000000 --- a/translations/es-ES/data/release-notes/enterprise-server/2-22/11.yml +++ /dev/null @@ -1,19 +0,0 @@ -date: '2021-04-14' -sections: - security_fixes: - - Los paquetes se han actualizado a las versiones de seguridad más recientes. - bugs: - - 'Un mensaje de advertencia "jq: error (en :0): No se puede indexar el número con la cadena "configuración"" podría aparecer durante la promoción de la réplica.' - - La restauración continua de copias de seguridad en un clúster podría dar error debido a que las réplicas de MySQL no se pueden conectar al principal. - - Pudo haber un error en el resaltado de sintaxis debido a que el contenedor de Treelights se quedó sin memoria. - - "Visitar la página \"/settings/emails\" almacenaría un estado que podría causar redireccionamientos inapropiados al cerrar sesión y volver a iniciar sesión." - - "Las alertas de gráfico de dependencias no se mostraban para algunos componentes cuyos avisos tienen nombres de paquete en mayúsculas en \"vulnerable_version_ranges\"." - - Las aplicaciones de integración de GitHub no pudieron notificar a los equipos cuando se mencionaron directamente a través de una @mención en un comentario de incidencia. - - "Cuando ghe-migrator encontraba errores de importación, a veces anulaba todo el proceso y los registros no incluían suficiente contexto." - known_issues: - - "En una instancia de GitHub Enterprise Server recién configurada sin usuarios, un atacante podría crear el primer usuario administrador." - - Las reglas de firewall personalizadas no se mantienen durante una actualización. - - "Los archivos supervisados de Git LFS [cargados a través la interfaz web](https://github.com/blog/2105-upload-files-to-your-repositories) se agregaron incorrecta y directamente al repositorio." - - Las incidencias no se pueden cerrar si contienen un vínculo permanente a un blob en el mismo repositorio en el que la ruta de acceso de archivo tiene más de 255 caracteres. - - "Cuando se habilita \"Los usuarios pueden buscar en GitHub.com\" con GitHub Connect, las incidencias en los repositorios privados e internos no se incluyen en los resultados de la búsqueda de GitHub.com." - - "Cuando un nodo de réplica está sin conexión en una configuración de alta disponibilidad, {% data variables.product.product_name %} aún se pueden enrutar solicitudes de {% data variables.product.prodname_pages %} al nodo sin conexión, lo que reduce la disponibilidad de {% data variables.product.prodname_pages %} para los usuarios." diff --git a/translations/es-ES/data/release-notes/enterprise-server/2-22/12.yml b/translations/es-ES/data/release-notes/enterprise-server/2-22/12.yml deleted file mode 100644 index daebf9f91f..0000000000 --- a/translations/es-ES/data/release-notes/enterprise-server/2-22/12.yml +++ /dev/null @@ -1,22 +0,0 @@ -date: '2021-04-28' -sections: - security_fixes: - - 'Los paquetes se han actualizado a las últimas versiones de seguridad.' - bugs: - - 'Durante las mejoras, el proceso se pausaba de forma indefinida después de un `cleanup nomad job`.' - - 'Fallo de `ghe-cluster-failover` con el mensaje de error `Trilogy::Error: trilogy_connect`.' - - '`ghe-cluster-status-mysql` mostraba advertencias sobre conmutaciones por error como errores.' - - 'El script de configuración que se ejecuta en la replica de MySQL puede haber causado una reinicialización innecesaria de la base de datos durante la recuperación de fallos de la base de datos.' - - '`config-apply` podía tardar más de lo necesario debido a que se llamaba a `rake db:migrate` innecesariamente.' - - 'El orquestador podía no conmutarse por error a una réplica de MySQL que no se estaba replicando desde la principal durante la fase de inicialización cuando la principal no se podía conectar.' - - 'Las organizaciones o los proyectos con errores bloqueaban la migración y no podían excluirse.' - - 'Los clientes con más de tres hosts de almacenamiento no podían restablecer su clúster de recuperación de desastres debido a que se seleccionaban los discos más llenos en vez de los nodos vacíos.' - changes: - - 'Las comprobaciones preparatorias permiten tipos de instancia de AWS de manera predeterminada.' - known_issues: - - 'En un servidor de GitHub Enterprise recién configurado sin usuarios, un atacante podría crear el primer usuario administrador.' - - 'Las reglas de firewall personalizadas no se mantienen durante una actualización.' - - 'Los archivos rastreados de Git LFS [cargados a través de la interfaz web](https://github.com/blog/2105-upload-files-to-your-repositories) se agregan de forma incorrecta y directa al repositorio.' - - "Las incidencias no se pueden cerrar si contienen un vínculo permanente a un blob en el mismo repositorio en el que la ruta de acceso de archivo del blob tiene más de 255\_caracteres." - - 'Cuando se habilita "Los usuarios pueden buscar en GitHub.com" con GitHub Connect, las incidencias en los repositorios privados e internos no se incluyen en los resultados de la búsqueda de GitHub.com.' - - 'Cuando un nodo de réplica está sin conexión en una configuración de disponibilidad alta, es posible que {% data variables.product.product_name %} enrute las solicitudes a {% data variables.product.prodname_pages %} al nodo sin conexión, lo que reduce la disponibilidad de {% data variables.product.prodname_pages %} para los usuarios.' diff --git a/translations/es-ES/data/release-notes/enterprise-server/2-22/13.yml b/translations/es-ES/data/release-notes/enterprise-server/2-22/13.yml deleted file mode 100644 index b46ddcc6e1..0000000000 --- a/translations/es-ES/data/release-notes/enterprise-server/2-22/13.yml +++ /dev/null @@ -1,20 +0,0 @@ -date: '2021-05-13' -sections: - security_fixes: - - "**ALTA:** se identificó una vulnerabilidad de representación incorrecta en la IU en el servidor de GitHub Enterprise que permitía otorgar más permisos de los que se mostraban al usuario en la aprobación durante el flujo web de autorización de usuarios en una GitHub App. Para aprovechar esta vulnerabilidad, un atacante tendría que crear una aplicación de GitHub en la instancia y hacer que el usuario la autorice mediante el flujo de autenticación web. Todos los permisos que se otorgaban se mostraban correctamente durante la primera autorización, pero en ciertas circunstancias, si el usuario volvía a visitar el flujo de autorización después de haber configurado los permisos de nivel de usuario en la GitHub App, los permisos adicionales podían no mostrarse, lo que causaba que el usuario otorgara más permisos de los previstos. Esta vulnerabilidad afectó al servidor de GitHub Enterprise desde la versión\_3.0.x hasta la\_3.0.7 y la versión\_2.22.x hasta la\_2.22.13. Se corrigió en las versiones 3.0.7 y 2.22.13. Esta vulnerabilidad se ha asignado a CVE-2021-22866 y se ha notificado mediante [GitHub\_Bug Bounty Program](https://bounty.github.com/)." - - 'Los paquetes se han actualizado a las últimas versiones de seguridad.' - bugs: - - 'La conmutación por error automática de Orchestrator se puede habilitar durante la fase de aplicación de la configuración.' - - 'A los usuarios con permiso de mantenedor en un repositorio se les mostraba una advertencia de verificación por correo electrónico en vez de una compilación de página correcta en la página de configuración de páginas del repositorio.' - - 'El propietario del código de una regla de comodín se agregaba incorrectamente a la lista de propietarios para la insignia de propietarios de código, incluso si una regla tardía prevalecía en dicha ruta.' - - 'Documentación de OpenAPI para un encabezado no válido.' - changes: - - 'Se agregó el registro en bitácora para cambios de configuración en una recarga de HAProxy.' - - 'Se agregó el registro en bitácora para la creación de repositorios.' - known_issues: - - 'En un servidor de GitHub Enterprise recién configurado sin usuarios, un atacante podría crear el primer usuario administrador.' - - 'Las reglas de firewall personalizadas no se mantienen durante una actualización.' - - 'Los archivos supervisados de Git LFS [cargados desde la interface web](https://github.com/blog/2105-upload-files-to-your-repositories) se han agregado de manera incorrecta y directa al repositorio.' - - "Las incidencias no se pueden cerrar si contienen un vínculo permanente a un blob en el mismo repositorio en el que la ruta de acceso de archivo del blob tiene más de 255\_caracteres." - - 'Cuando se habilita "Los usuarios pueden buscar en GitHub.com" con GitHub Connect, las incidencias en los repositorios privados e internos no se incluyen en los resultados de la búsqueda de GitHub.com.' - - 'Cuando un nodo de réplica está sin conexión en una configuración de disponibilidad alta, es posible que {% data variables.product.product_name %} enrute las solicitudes a {% data variables.product.prodname_pages %} al nodo sin conexión, lo que reduce la disponibilidad de {% data variables.product.prodname_pages %} para los usuarios.' diff --git a/translations/es-ES/data/release-notes/enterprise-server/2-22/14.yml b/translations/es-ES/data/release-notes/enterprise-server/2-22/14.yml deleted file mode 100644 index 83d768da3e..0000000000 --- a/translations/es-ES/data/release-notes/enterprise-server/2-22/14.yml +++ /dev/null @@ -1,18 +0,0 @@ -date: '2021-05-25' -sections: - security_fixes: - - '**MEDIA:** Bajo ciertas circunstancias, los usuarios que se eliminaban de un equipo u organización podían retener el acceso de escritura a las ramas en las cuales tenían solicitudes de cambio existentes abiertas.' - - 'Los paquetes se han actualizado a las últimas versiones de seguridad.' - bugs: - - 'La replicación normal se retrasa en las advertencias que genera MSSQL.' - - 'Las direcciones IP que agregaba un administrador utilizando el botón "Crear entrada de lista de admisión" podía bloquearse de todos modos.' - - '`spokesd` creaba entradas de bitácora excesivas, incluyendo la frase "fixing placement skipped".' - changes: - - 'Se archivarán las anotaciones de verificación anteriores a 4 meses.' - known_issues: - - 'En un servidor de GitHub Enterprise recién configurado sin usuarios, un atacante podría crear el primer usuario administrador.' - - 'Las reglas de firewall personalizadas no se mantienen durante una actualización.' - - 'Los archivos supervisados de Git LFS [cargados desde la interfaz web](https://github.com/blog/2105-upload-files-to-your-repositories) se agregan de manera incorrecta y directa al repositorio.' - - "Las incidencias no se pueden cerrar si contienen un vínculo permanente a un blob en el mismo repositorio en el que la ruta de acceso de archivo del blob tiene más de 255\_caracteres." - - 'Cuando se habilita "Los usuarios pueden buscar en GitHub.com" con GitHub Connect, las incidencias en los repositorios privados e internos no se incluyen en los resultados de la búsqueda de GitHub.com.' - - 'Cuando un nodo de réplica está sin conexión en una configuración de disponibilidad alta, es posible que {% data variables.product.product_name %} enrute las solicitudes a {% data variables.product.prodname_pages %} al nodo sin conexión, lo que reduce la disponibilidad de {% data variables.product.prodname_pages %} para los usuarios.' diff --git a/translations/es-ES/data/release-notes/enterprise-server/2-22/15.yml b/translations/es-ES/data/release-notes/enterprise-server/2-22/15.yml deleted file mode 100644 index 8f813cfe43..0000000000 --- a/translations/es-ES/data/release-notes/enterprise-server/2-22/15.yml +++ /dev/null @@ -1,16 +0,0 @@ -date: '2021-06-10' -sections: - security_fixes: - - 'Los paquetes se han actualizado a las versiones de seguridad más recientes.' - bugs: - - 'Los errores de importación de organizaciones o repositorios de fuentes que no son de GitHub podrían producir un error de "método indefinido "[]" para nil:NilClass".' - - 'Los nombres de perfil de GitHub podrían haber cambiado accidentalmente al usar la autenticación SAML, si el nombre de perfil de GitHub no coincidía con el valor del atributo asignado al campo "Nombre completo" en la consola de administración.' - changes: - - 'Los usuarios de la API de GraphQL pueden consultar el campo público "closingIssuesReferences" en el objeto "PullRequest". Este campo recupera incidencias que se cerrarán automáticamente cuando la solicitud de incorporación de cambios se fusione. Este enfoque también permitirá que estos datos se migren en un futuro, como parte de un proceso de migración de mayor fidelidad.' - known_issues: - - 'En una instancia de GitHub Enterprise Server recién configurada sin usuarios, un atacante podría crear el primer usuario administrador.' - - 'Las reglas de firewall personalizadas se eliminan durante el proceso de actualización.' - - 'Los archivos supervisados de Git LFS [cargados a través la interfaz web](https://github.com/blog/2105-upload-files-to-your-repositories) se agregaron incorrecta y directamente al repositorio.' - - "Las incidencias no se pueden cerrar si contienen un vínculo permanente a un blob en el mismo repositorio en el que la ruta de acceso del archivo del blob tiene más de 255\_caracteres." - - 'Cuando se habilita "Los usuarios pueden buscar en GitHub.com" con GitHub Connect, las incidencias en los repositorios privados e internos no se incluyen en los resultados de la búsqueda de GitHub.com.' - - 'Cuando un nodo de réplica está sin conexión en una configuración de alta disponibilidad, {% data variables.product.product_name %} aún se pueden enrutar solicitudes de {% data variables.product.prodname_pages %} al nodo sin conexión, lo que reduce la disponibilidad de {% data variables.product.prodname_pages %} para los usuarios.' diff --git a/translations/es-ES/data/release-notes/enterprise-server/2-22/16.yml b/translations/es-ES/data/release-notes/enterprise-server/2-22/16.yml deleted file mode 100644 index 09bc5ec201..0000000000 --- a/translations/es-ES/data/release-notes/enterprise-server/2-22/16.yml +++ /dev/null @@ -1,15 +0,0 @@ -date: '2021-06-24' -sections: - security_fixes: - - 'Los paquetes se han actualizado a las últimas versiones de seguridad.' - bugs: - - 'El servicio de sshd fallaba en algunas ocasiones al iniciarse en instancias que se estaban ejecutando en la Google Cloud Platform.' - - 'Los archivos de actualización antiguos persistían en el disco del usuario, lo cual algunas veces provocaba condiciones de falta de espacio.' - - 'Los archivos de exportación no importaban solicitudes de cambios si estas contenían solicitudes de revisión de equipos que no estaban presentes en el archivo.' - known_issues: - - 'En un servidor de GitHub Enterprise recién configurado sin usuarios, un atacante podría crear el primer usuario administrador.' - - 'Las reglas de cortafuegos personalizadas se eliminan durante el proceso de actualización.' - - 'Los archivos supervisados de Git LFS [cargados desde la interface web](https://github.com/blog/2105-upload-files-to-your-repositories) se han agregado de manera incorrecta y directa al repositorio.' - - "Las incidencias no se pueden cerrar si contienen un enlace permanente a un blob del mismo repositorio en el que la ruta es mayor de 255\_caracteres." - - 'Cuando se habilita "Los usuarios pueden buscar en GitHub.com" con GitHub Connect, las incidencias en los repositorios privados e internos no se incluyen en los resultados de la búsqueda de GitHub.com.' - - 'Cuando un nodo de réplica está sin conexión en una configuración de disponibilidad alta, es posible que {% data variables.product.product_name %} enrute las solicitudes a {% data variables.product.prodname_pages %} al nodo sin conexión, lo que reduce la disponibilidad de {% data variables.product.prodname_pages %} para los usuarios.' diff --git a/translations/es-ES/data/release-notes/enterprise-server/2-22/17.yml b/translations/es-ES/data/release-notes/enterprise-server/2-22/17.yml deleted file mode 100644 index 12abdf6146..0000000000 --- a/translations/es-ES/data/release-notes/enterprise-server/2-22/17.yml +++ /dev/null @@ -1,20 +0,0 @@ -date: '2021-07-14' -sections: - security_fixes: - - "**ALTA:** se ha identificado una vulnerabilidad de salto de directorio en GitHub Enterprise Server que podía explotarse al crear un sitio de GitHub Pages. Las opciones de configuración controladas por el usuario utilizadas por GitHub Pages no estaban lo suficientemente restringidas y permitían leer archivos en la instancia de GitHub Enterprise Server. Para aprovechar esta vulnerabilidad de seguridad, un atacante necesitaría permiso para crear un sitio de GitHub Pages en la instancia de GitHub\_Enterprise Server. Esta vulnerabilidad afectaba a todas las versiones de GitHub Enterprise Server anteriores a la\_3.1.3 y se le ha asignado el código CVE-2021-22867. Se informó de esta vulnerabilidad mediante el programa de GitHub Bug Bounty." - - 'Los paquetes se han actualizado a las últimas versiones de seguridad.' - bugs: - - '`ghe-cluster-config-node-init` fallaba durante la configuración de clúster si se había habilitado el proxy de HTTP.' - - 'Collectd no resolvía el nombre de host destino que se estaba reenviando después del inicio principal.' - - 'El job que purgaba los repositorios inactivos borrados podía fallar durante el progreso si alguno de estos repositorios estaba protegido contra borrado debido a limitaciones legales.' - - 'Las subidas de Git dieron como resultado un Error de servidor interno 500 durante el proceso de reconciliación del usuario en las instancias que utilizaban el modo de autenticación de LDAP.' - - "Una cantidad significativa de errores\_503 se registraba cada vez que un usuario visitaba la página `/settings` de un repositorio si la gráfica de dependencias no estaba habilitada." - changes: - - 'Se ha mejorado el rendimiento de la aplicación de configuración al omitir las reglas de cortafuegos para permitir IP, las cuales no hubieran cambiado, con lo cual se ha ahorrado tiempo significativo en los clústeres grandes.' - known_issues: - - 'En un servidor de GitHub Enterprise recién configurado sin usuarios, un atacante podría crear el primer usuario administrador.' - - 'Las reglas de cortafuegos personalizadas se eliminan durante el proceso de actualización.' - - 'Los archivos supervisados de Git LFS [cargados desde la interfaz web](https://github.com/blog/2105-upload-files-to-your-repositories) se agregan de manera incorrecta y directa al repositorio.' - - "Las incidencias no se pueden cerrar si contienen un enlace permanente a un blob del mismo repositorio en el que la ruta es mayor de 255\_caracteres." - - 'Cuando se habilita "Los usuarios pueden buscar en GitHub.com" con GitHub Connect, las incidencias en los repositorios privados e internos no se incluyen en los resultados de la búsqueda de GitHub.com.' - - 'Cuando un nodo de réplica está sin conexión en una configuración de disponibilidad alta, es posible que {% data variables.product.product_name %} enrute las solicitudes a {% data variables.product.prodname_pages %} al nodo sin conexión, lo que reduce la disponibilidad de {% data variables.product.prodname_pages %} para los usuarios.' diff --git a/translations/es-ES/data/release-notes/enterprise-server/2-22/18.yml b/translations/es-ES/data/release-notes/enterprise-server/2-22/18.yml deleted file mode 100644 index ce2df0e6a5..0000000000 --- a/translations/es-ES/data/release-notes/enterprise-server/2-22/18.yml +++ /dev/null @@ -1,16 +0,0 @@ -date: '2021-07-27' -sections: - security_fixes: - - 'Los paquetes se han actualizado a las últimas versiones de seguridad.' - bugs: - - 'Si el job programado para sincronizar vulnerabilidades con GitHub.com intentaba ejecutarse cuando la gráfica de dependencias no estaba habilitada y el análisis de contenido sí estaba habilitado, se creaban una cantidad significativa de 503 errores.' - - 'El proxy HTTP no autenticado para la compilación de contenedores de las páginas no era compatible para ningún usuario que utilizara proxys HTTP.' - changes: - - 'Las bitácoras de `babeld` ahora incluyen un campo `cmd` para las solicitudes de publicidad de ref de HTTP en vez de incluirlo únicamente durante las solicitudes de negociación.' - known_issues: - - 'En una instalación nueva de {% data variables.product.prodname_ghe_server %} que no tenga ningún usuario, cualquier atacante podría crear el primer usuario administrativo.' - - 'Las reglas de cortafuegos personalizadas se eliminan durante el proceso de actualización.' - - 'Los archivos supervisados de Git LFS [cargados desde la interfaz web](https://github.com/blog/2105-upload-files-to-your-repositories) se agregan de manera incorrecta y directa al repositorio.' - - "Las incidencias no se pueden cerrar si contienen un enlace permanente a un blob del mismo repositorio en el que la ruta es mayor de 255\_caracteres." - - 'Cuando se habilita "Los usuarios pueden buscar en GitHub.com" con GitHub Connect, las incidencias en los repositorios privados e internos no se incluyen en los resultados de la búsqueda de GitHub.com.' - - 'Cuando un nodo de réplica está sin conexión en una configuración de disponibilidad alta, es posible que {% data variables.product.product_name %} enrute las solicitudes a {% data variables.product.prodname_pages %} al nodo sin conexión, lo que reduce la disponibilidad de {% data variables.product.prodname_pages %} para los usuarios.' diff --git a/translations/es-ES/data/release-notes/enterprise-server/2-22/19.yml b/translations/es-ES/data/release-notes/enterprise-server/2-22/19.yml deleted file mode 100644 index d033e0c0ea..0000000000 --- a/translations/es-ES/data/release-notes/enterprise-server/2-22/19.yml +++ /dev/null @@ -1,13 +0,0 @@ -date: '2021-08-10' -sections: - bugs: - - "Las entradas de registro de auditoría para los cambios realizados a los ajustes de la organización de \"Creación de repositorios\" eran inexactas." - changes: - - "Los límites de frecuencia abusiva ahora se llaman límites de frecuencia secundarios, ya que el comportamiento que limitan no siempre es abusivo." - known_issues: - - "En una instalación nueva de {% data variables.product.prodname_ghe_server %} que no tenga ningún usuario, cualquier atacante podría crear el primer usuario administrativo." - - Las reglas de cortafuegos personalizadas se eliminan durante el proceso de actualización. - - "Los archivos supervisados de Git LFS [cargados desde la interfaz web](https://github.com/blog/2105-upload-files-to-your-repositories) se agregan de manera incorrecta y directa al repositorio." - - Las incidencias no se pueden cerrar si contienen un enlace permanente a un blob del mismo repositorio en el que la ruta es mayor de 255 caracteres. - - "Cuando se habilita \"Los usuarios pueden buscar en GitHub.com\" con GitHub Connect, las incidencias en los repositorios privados e internos no se incluyen en los resultados de la búsqueda de GitHub.com." - - "Cuando un nodo de réplica está sin conexión en una configuración de disponibilidad alta, es posible que {% data variables.product.product_name %} enrute las solicitudes a {% data variables.product.prodname_pages %} al nodo sin conexión, lo que reduce la disponibilidad de {% data variables.product.prodname_pages %} para los usuarios." diff --git a/translations/es-ES/data/release-notes/enterprise-server/2-22/2.yml b/translations/es-ES/data/release-notes/enterprise-server/2-22/2.yml deleted file mode 100644 index 42e92d228d..0000000000 --- a/translations/es-ES/data/release-notes/enterprise-server/2-22/2.yml +++ /dev/null @@ -1,31 +0,0 @@ -date: '2020-10-20' -sections: - security_fixes: - - Packages have been updated to the latest security versions. {% comment %} https://github.com/github/enterprise2/pull/23097, https://github.com/github/enterprise2/pull/23081 {% endcomment %} - - bugs: - - | - If the storage account settings failed to validate while configuring GitHub Actions, running `ghe-actions-teardown` was required before making a new attempt. {% comment %} https://github.com/github/enterprise2/pull/23057, https://github.com/github/enterprise2/pull/22981 {% endcomment %} - - | - A custom proxy configuration could adversely affect the GitHub Actions environment. {% comment %} https://github.com/github/enterprise2/pull/23121, https://github.com/github/enterprise2/pull/23092, https://github.com/github/c2c-actions-platform/issues/2254 {% endcomment %} - - | - On a change of an address on eth0, Nomad and Consul could get unresponsive. {% comment %} https://github.com/github/enterprise2/pull/23227, https://github.com/github/enterprise2/pull/23153 {% endcomment %} - - | - When using self-signed certificates, GHES could have SSL validation exceptions upon configuring GitHub Actions. {% comment %} https://github.com/github/enterprise2/pull/23381 {% endcomment %} - - | - Using a GitHub Action from a branch name with a `+` or `/` character resulted in an error: `Unable to resolve action`. {% comment %} https://github.com/github/github/pull/157942, https://github.com/github/github/pull/157819, https://github.com/github/launch/pull/3463 {% endcomment %} - - | - The enterprise account "Confirm two-factor requirement policy" messaging was incorrect. {% comment %} https://github.com/github/github/pull/158735 {% endcomment %} - - | - On certain requests above 100MB, Kafka's buffer could be over-allocated. {% comment %} https://github.com/github/kafka-lite/pull/286, https://github.com/github/kafka-lite/pull/285 {% endcomment %} - - known_issues: - - On a freshly set up GitHub Enterprise Server without any users, an attacker could create the first admin user. {% comment %} https://github.com/github/enterprise2/issues/1889 {% endcomment %} - - Custom firewall rules are not maintained during an upgrade. {% comment %} https://github.com/github/enterprise2/issues/2823 {% endcomment %} - - 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. {% comment %} https://github.com/github/github/issues/54684 {% endcomment %} - - 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. {% comment %} https://github.com/github/github/issues/107731 {% endcomment %} - - 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. {% comment %} https://github.com/github/admin-experience/issues/571 {% endcomment %} - - GitHub Actions can fail to start up successfully if it was previously enabled on an instance running 2.22.0 and is upgraded to 2.22.2. (updated 2020-10-23) {% comment %} https://github.com/github/c2c-actions/issues/1680 {% endcomment %} - - On a freshly set up 2.22.2 instance or after upgrading to 2.22.2, the activity feed on an organization's dashboard will no longer update. (updated 2020-10-27) {% comment %}https://github.com/github/enterprise2/issues/23050{% endcomment %} - - Audit logs may be attributed to 127.0.0.1 instead of the actual source IP address. (updated 2020-11-02) {% comment %} https://github.com/github/enterprise2/issues/21514 {% endcomment %} - - 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. diff --git a/translations/es-ES/data/release-notes/enterprise-server/2-22/20.yml b/translations/es-ES/data/release-notes/enterprise-server/2-22/20.yml deleted file mode 100644 index 2423f58cae..0000000000 --- a/translations/es-ES/data/release-notes/enterprise-server/2-22/20.yml +++ /dev/null @@ -1,14 +0,0 @@ -date: '2021-08-24' -sections: - security_fixes: - - Los paquetes se han actualizado a las últimas versiones de seguridad. - bugs: - - Los mensajes de Journald con relación a las actualizaciones automáticas (`Adding h/m/s random time.`) se registraron en syslog. - - "Los ganchos de Git hacia la API interna que generaban solicitudes fallidas devolvían la excepción `undefined method body for \"success\":String (NoMethodError)` en vez de devolver un `nil` explícito." - known_issues: - - "En una instalación nueva de {% data variables.product.prodname_ghe_server %} que no tenga ningún usuario, cualquier atacante podría crear el primer usuario administrativo." - - Las reglas de cortafuegos personalizadas se eliminan durante el proceso de actualización. - - "Los archivos supervisados de Git LFS [cargados desde la interfaz web](https://github.com/blog/2105-upload-files-to-your-repositories) se agregan de manera incorrecta y directa al repositorio." - - Las incidencias no se pueden cerrar si contienen un enlace permanente a un blob del mismo repositorio en el que la ruta es mayor de 255 caracteres. - - "Cuando se habilita \"Los usuarios pueden buscar en GitHub.com\" con GitHub Connect, las incidencias en los repositorios privados e internos no se incluyen en los resultados de la búsqueda de GitHub.com." - - "Cuando un nodo de réplica está sin conexión en una configuración de disponibilidad alta, es posible que {% data variables.product.product_name %} enrute las solicitudes a {% data variables.product.prodname_pages %} al nodo sin conexión, lo que reduce la disponibilidad de {% data variables.product.prodname_pages %} para los usuarios." diff --git a/translations/es-ES/data/release-notes/enterprise-server/2-22/21.yml b/translations/es-ES/data/release-notes/enterprise-server/2-22/21.yml deleted file mode 100644 index 5c6d1e27b3..0000000000 --- a/translations/es-ES/data/release-notes/enterprise-server/2-22/21.yml +++ /dev/null @@ -1,11 +0,0 @@ -date: '2021-09-07' -sections: - security_fixes: - - 'Los paquetes se han actualizado a las últimas versiones de seguridad.' - known_issues: - - 'En una instalación nueva de {% data variables.product.prodname_ghe_server %} que no tenga ningún usuario, cualquier atacante podría crear el primer usuario administrativo.' - - 'Las reglas de cortafuegos personalizadas se eliminan durante el proceso de actualización.' - - 'Los archivos supervisados de Git LFS [cargados desde la interfaz web](https://github.com/blog/2105-upload-files-to-your-repositories) se agregan de manera incorrecta y directa al repositorio.' - - "Las incidencias no se pueden cerrar si contienen un enlace permanente a un blob del mismo repositorio en el que la ruta es mayor de 255\_caracteres." - - 'Cuando se habilita "Los usuarios pueden buscar en GitHub.com" con GitHub Connect, las incidencias en los repositorios privados e internos no se incluyen en los resultados de la búsqueda de GitHub.com.' - - 'Cuando un nodo de réplica está sin conexión en una configuración de disponibilidad alta, es posible que {% data variables.product.product_name %} enrute las solicitudes a {% data variables.product.prodname_pages %} al nodo sin conexión, lo que reduce la disponibilidad de {% data variables.product.prodname_pages %} para los usuarios.' diff --git a/translations/es-ES/data/release-notes/enterprise-server/2-22/22.yml b/translations/es-ES/data/release-notes/enterprise-server/2-22/22.yml deleted file mode 100644 index 8c09ffbb52..0000000000 --- a/translations/es-ES/data/release-notes/enterprise-server/2-22/22.yml +++ /dev/null @@ -1,14 +0,0 @@ -date: '2021-09-24' -sections: - security_fixes: - - "**ALTA:** se ha identificado una vulnerabilidad de salto de directorio en {% data variables.product.prodname_ghe_server %} que podía aprovecharse al compilar un sitio de {% data variables.product.prodname_pages %}. Las opciones de configuración controladas por el usuario utilizadas por {% data variables.product.prodname_pages %} no estaban lo suficientemente restringidas y permitían leer archivos en la instancia de {% data variables.product.prodname_ghe_server %}. Para aprovecharse de esta vulnerabilidad, el atacante necesitaba permiso para crear y compilar un sitio de {% data variables.product.prodname_pages %} en la instancia de {% data variables.product.prodname_ghe_server %}. Esta vulnerabilidad afectó a todas las versiones de {% data variables.product.prodname_ghe_server %} anteriores a la\_3.1.8 y se corrigió en las versiones\_3.1.8, 3.0.16 y 2.22.22. Esto se debe a una corrección incompleta para CVE-2021-22867. La vulnerabilidad se reportó a través del programa GitHub Bug Bounty y se le ha asignado el código CVE-2021-22868. {% comment %} https://github.com/github/pages/pull/3359, https://github.com/github/pages/pull/3357 {% endcomment %}" - bugs: - - 'La configuración de {% data variables.product.prodname_github_connect %} de la instancia de origen siempre se restauraba en instancias nuevas, aunque no se utilizara la opción `--config` de `ghe-restore`. Esto podía ocasionar un conflicto con la conexión de {% data variables.product.prodname_github_connect %} y con la sincronización de licencias si tanto las instancias de origen como las de destino estaban conectadas al mismo tiempo. {% comment %} https://github.com/github/github/pull/192247, https://github.com/github/github/pull/191951, https://github.com/github/enterprise2/pull/26870, https://github.com/github/backup-utils/pull/770, https://github.com/github/connected-enterprise/issues/208 {% endcomment %}' - - 'Se han corregido las compilaciones de {% data variables.product.prodname_pages %} para que tengan en cuenta el ajuste NO_PROXY del dispositivo. Esto es importante para dispositivos configurados solo con un proxy HTTP. {% comment %} https://github.com/github/github/pull/192380 {% endcomment %}' - known_issues: - - 'En una instalación nueva de {% data variables.product.prodname_ghe_server %} que no tenga ningún usuario, cualquier atacante podría crear el primer usuario administrativo.' - - 'Las reglas de cortafuegos personalizadas se eliminan durante el proceso de actualización.' - - 'Los archivos supervisados de Git LFS [cargados desde la interfaz web](https://github.com/blog/2105-upload-files-to-your-repositories) se agregan de manera incorrecta y directa al repositorio.' - - "Las incidencias no se pueden cerrar si contienen un enlace permanente a un blob del mismo repositorio en el que la ruta es mayor de 255\_caracteres." - - 'Cuando se habilita "Los usuarios pueden buscar en GitHub.com" con {% data variables.product.prodname_github_connect %}, las propuestas en los repositorios privados e internos no se incluirán en los resultados de búsqueda de GitHub.com.' - - 'Cuando un nodo de réplica está sin conexión en una configuración de disponibilidad alta, es posible que {% data variables.product.product_name %} enrute las solicitudes a {% data variables.product.prodname_pages %} al nodo sin conexión, lo que reduce la disponibilidad de {% data variables.product.prodname_pages %} para los usuarios.' diff --git a/translations/es-ES/data/release-notes/enterprise-server/2-22/3.yml b/translations/es-ES/data/release-notes/enterprise-server/2-22/3.yml deleted file mode 100644 index 83b8ebfa6a..0000000000 --- a/translations/es-ES/data/release-notes/enterprise-server/2-22/3.yml +++ /dev/null @@ -1,25 +0,0 @@ -date: '2020-11-03' -sections: - security_fixes: - - | - **LOW:** High CPU usage could be triggered by a specially crafted request to the SVN bridge resulting in Denial of Service (DoS) on the SVN bridge service. (updated 2020-11-16) {% comment %} https://github.com/github/slumlord/pull/1005, https://github.com/github/slumlord/pull/1000 {% endcomment %} - - | - **LOW:** Incorrect token validation resulted in a reduced entropy for matching tokens during authentication. Analysis shows that in practice there's no significant security risk here. {% comment %} https://github.com/github/github/pull/159457, https://github.com/github/github/pull/159193 {% endcomment %} - - | - Packages have been updated to the latest security versions. {% comment %} https://github.com/github/enterprise2/pull/23540, https://github.com/github/enterprise2/pull/23171, https://github.com/github/enterprise2/pull/23693, https://github.com/github/enterprise2/pull/23677 {% endcomment %} - - bugs: - - GitHub Actions could fail to start up successfully if it was previously enabled on an instance running 2.22.0 and was upgraded to 2.22.1 or 2.22.2. {% comment %} https://github.com/github/enterprise2/pull/23622, https://github.com/github/enterprise2/pull/23490, https://github.com/github/c2c-actions/issues/1680 {% endcomment %} - - Configuration files for GitHub Actions were not copied to the replica when setting up high availability replicas potentially leading to errors during `ghe-repl-promote`. {% comment %} https://github.com/github/enterprise2/pull/23703, https://github.com/github/enterprise2/pull/23683 {% endcomment %} - - On a freshly set up 2.22.1 or 2.22.2 instance or after upgrading to 2.22.1 or 2.22.2, the activity feed on an organization's dashboard would not update. {% comment %} https://github.com/github/github/pull/159376, https://github.com/github/github/pull/159235, https://github.com/github/enterprise2/issues/23050 {% endcomment %} - - Editing issues templates with filenames containing non-ASCII characters would fail with a "500 Internal Server Error". {% comment %} https://github.com/github/github/pull/160588, https://github.com/github/github/pull/159747 {% endcomment %} - - A metric gathering method for background jobs increased CPU utilization. (updated 2020-11-03) {% comment %} https://github.com/github/github/pull/160109 {% endcomment %} - - known_issues: - - On a freshly set up GitHub Enterprise Server without any users, an attacker could create the first admin user. {% comment %} https://github.com/github/enterprise2/issues/1889 {% endcomment %} - - Custom firewall rules are not maintained during an upgrade. {% comment %} https://github.com/github/enterprise2/issues/2823 {% endcomment %} - - 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. {% comment %} https://github.com/github/github/issues/54684 {% endcomment %} - - 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. {% comment %} https://github.com/github/github/issues/107731 {% endcomment %} - - 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. {% comment %} https://github.com/github/admin-experience/issues/571 {% endcomment %} - - Audit logs may be attributed to 127.0.0.1 instead of the actual source IP address. {% comment %} https://github.com/github/enterprise2/issues/21514 {% endcomment %} - - 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. diff --git a/translations/es-ES/data/release-notes/enterprise-server/2-22/4.yml b/translations/es-ES/data/release-notes/enterprise-server/2-22/4.yml deleted file mode 100644 index 3ae5aa8b67..0000000000 --- a/translations/es-ES/data/release-notes/enterprise-server/2-22/4.yml +++ /dev/null @@ -1,16 +0,0 @@ -date: '2020-11-17' -sections: - security_fixes: - - 'Los paquetes se han actualizado a sus últimas versiones de seguridad. {% comment %} https://github.com/github/enterprise2/pull/23845, https://github.com/github/enterprise2/pull/23712 {% endcomment %}' - bugs: - - 'En los registros de babeld faltaba un separador entre los segundos y los microsegundos. {% comment %} https://github.com/github/babeld/pull/1006, https://github.com/github/babeld/pull/1002 {% endcomment %}' - - 'Después de actualizar a GHES con un hotpatch, los comandos `ghe-actions-precheck` y `ghe-packages-precheck` fallaron con el error `"docker load" accepts no arguments`. {% comment %} https://github.com/github/enterprise2/pull/23760, https://github.com/github/enterprise2/pull/23745 {% endcomment %}' - - 'Cuando la directiva "Cambio de visibilidad del repositorio" en las cuentas empresariales estaba configurada como "Habilitada", los propietarios de las organizaciones no podían cambiar la visibilidad de los repositorios dentro de las organizaciones. {% comment %} https://github.com/github/github/pull/160920, https://github.com/github/github/pull/160773 {% endcomment %}' - - 'Los registros de auditoría se podrían atribuir a 127.0.0.1 en lugar de a la dirección IP de origen real. {% comment %} https://github.com/github/github/pull/162438, https://github.com/github/github/pull/161215 {% endcomment %}' - known_issues: - - "En una instancia de GitHub\_Enterprise Server recién configurada sin ningún usuario, un atacante podría crear el primer usuario administrador. {% comment %} https://github.com/github/enterprise2/issues/1889 {% endcomment %}" - - 'Las reglas de cortafuegos personalizadas no se mantienen durante una actualización. {% comment %} https://github.com/github/enterprise2/issues/2823 {% endcomment %}' - - 'Los archivos supervisados de Git LFS [cargados desde la interface web](https://github.com/blog/2105-upload-files-to-your-repositories) se han agregado de forma incorrecta y directa al repositorio. {% comment %} https://github.com/github/github/issues/54684 {% endcomment %}' - - "Las incidencias no se pueden cerrar si contienen un enlace permanente a un blob del mismo repositorio en el que la ruta es mayor de 255\_caracteres. {% comment %} https://github.com/github/github/issues/107731 {% endcomment %}" - - 'Cuando se habilita "Los usuarios pueden buscar en GitHub.com" con GitHub Connect, las incidencias en los repositorios privados e internos no se incluyen en los resultados de la búsqueda de GitHub.com. {% comment %} https://github.com/github/admin-experience/issues/571 {% endcomment %}' - - 'Cuando un nodo de réplica está sin conexión en una configuración de disponibilidad alta, es posible que {% data variables.product.product_name %} enrute las solicitudes a {% data variables.product.prodname_pages %} al nodo sin conexión, lo que reduce la disponibilidad de {% data variables.product.prodname_pages %} para los usuarios.' diff --git a/translations/es-ES/data/release-notes/enterprise-server/2-22/5.yml b/translations/es-ES/data/release-notes/enterprise-server/2-22/5.yml deleted file mode 100644 index 63410a280a..0000000000 --- a/translations/es-ES/data/release-notes/enterprise-server/2-22/5.yml +++ /dev/null @@ -1,22 +0,0 @@ -date: '2020-12-03' -sections: - bugs: - - 'El servicio de autorización se detectaba como incorrecto debido a la condición de carrera en bootstrap, lo cual ocasionaba que se reiniciara el servicio. {% comment %} https://github.com/github/authzd/pull/1275, https://github.com/github/authzd/pull/1274 {% endcomment %}' - - 'ghe-diagnostics no capturaba el proceso de mejora de Elasticsearch. {% comment %} https://github.com/github/enterprise2/pull/23905, https://github.com/github/enterprise2/pull/23874 {% endcomment %}' - - 'Al habilitar las Acciones de GitHub en una configuración de alta disponibilidad mejorada generó errores en la replicación. {% comment %} https://github.com/github/enterprise2/pull/23979, https://github.com/github/c2c-actions-platform/issues/2479 {% endcomment %}' - - 'Un comportamiento subyacente estaba provocando que un servicio no estuviera disponible durante el proceso de mejora del hotpatch. {% comment %} https://github.com/github/enterprise2/pull/24055 {% endcomment %}' - - 'Los usuarios que se conectaban a una réplica activa obtenían un error al conectarse al websocket de las actualizaciones en vivo. {% comment %} https://github.com/github/enterprise2/pull/24079, https://github.com/github/enterprise2/pull/24058 {% endcomment %}' - - 'Un subconjunto de certificados SSL que reenviaban bitácoras no se estaba aplicando correctamente. {% comment %} https://github.com/github/enterprise2/pull/24114, https://github.com/github/enterprise2/pull/23981 {% endcomment %}' - - 'Se enviaron notificaciones de correo electrónico para suspender usuarios cuando se eliminaban de un equipo o de una organización. {% comment %} https://github.com/github/github/pull/162973, https://github.com/github/github/pull/162742 {% endcomment %}' - - 'La forma en la que se aplicaban los certificados SSH entre las organizaciones y los negocios no era uniforme. {% comment %} https://github.com/github/github/pull/163423, https://github.com/github/github/pull/159538, https://github.com/github/authentication/issues/115 {% endcomment %}' - - 'Cuando se limitaba la tarifa de una cuenta debido al uso incorrecto de contraseñas, se podía bloquear hasta 24 horas. {% comment %} https://github.com/github/github/pull/163433, https://github.com/github/github/pull/162938, https://github.com/github/github-ds/pull/51 {% endcomment %}' - - 'La sincronización de solicitudes de cambios en los repositorios con muchas referencias podía provocar que se retrasaran las colas de los roles de trabajo. {% comment %} https://github.com/github/github/pull/163573, https://github.com/github/github/pull/163142 {% endcomment %}' - - 'Al iniciar sesión con un nombre de usuario y contraseña locales (autenticación integrada) después de intentar visitar una página específica, se dirigía al usuario a la página principal en vez de al destino deseado. {% comment %} https://github.com/github/github/pull/163782, https://github.com/github/github/pull/163579, https://github.com/github/github/pull/154117, https://github.com/github/ecosystem-apps/issues/1076 {% endcomment %}' - - 'Para las instancias de GHES que utilizan una autenticación integrada con un proveedor de identidades de SAML interno, los usuarios sin una dirección de correo electrónico asociada no podían crear una confirmación desde la interfaz web. {% comment %} https://github.com/github/github/pull/164009, https://github.com/github/github/pull/163530, https://github.com/github/github/issues/163524 {% endcomment %}' - known_issues: - - "En una instancia de GitHub\_Enterprise Server recién configurada sin ningún usuario, un atacante podría crear el primer usuario administrador. {% comment %} https://github.com/github/enterprise2/issues/1889 {% endcomment %}" - - 'Las reglas de cortafuegos personalizadas no se mantienen durante una actualización. {% comment %} https://github.com/github/enterprise2/issues/2823 {% endcomment %}' - - 'Los archivos supervisados de Git LFS [cargados desde la interfaz web](https://github.com/blog/2105-upload-files-to-your-repositories) se agregan de forma incorrecta y directa al repositorio. {% comment %} https://github.com/github/github/issues/54684 {% endcomment %}' - - "Las incidencias no se pueden cerrar si contienen un enlace permanente a un blob del mismo repositorio en el que la ruta es mayor de 255\_caracteres. {% comment %} https://github.com/github/github/issues/107731 {% endcomment %}" - - 'Cuando se habilita "Los usuarios pueden buscar en GitHub.com" con GitHub Connect, las incidencias en los repositorios privados e internos no se incluyen en los resultados de la búsqueda de GitHub.com. {% comment %} https://github.com/github/admin-experience/issues/571 {% endcomment %}' - - 'Cuando un nodo de réplica está sin conexión en una configuración de disponibilidad alta, es posible que {% data variables.product.product_name %} enrute las solicitudes a {% data variables.product.prodname_pages %} al nodo sin conexión, lo que reduce la disponibilidad de {% data variables.product.prodname_pages %} para los usuarios.' diff --git a/translations/es-ES/data/release-notes/enterprise-server/2-22/6.yml b/translations/es-ES/data/release-notes/enterprise-server/2-22/6.yml deleted file mode 100644 index 10a8f7b123..0000000000 --- a/translations/es-ES/data/release-notes/enterprise-server/2-22/6.yml +++ /dev/null @@ -1,18 +0,0 @@ -date: '2020-12-17' -sections: - security_fixes: - - '**BAJA:** El uso elevado de CPU podía deberse a una solicitud hecha específicamente al puente de SVN, lo cual resultaba en una negación del servicio (DoS). {% comment %} https://github.com/github/slumlord/pull/1022, https://github.com/github/slumlord/pull/1017 {% endcomment %}' - - 'Los paquetes se han actualizado a sus últimas versiones de seguridad. {% comment %} https://github.com/github/enterprise2/pull/24353, https://github.com/github/enterprise2/pull/23866 {% endcomment %}' - bugs: - - 'Las solicitudes para algunos recursos de archivos como un archivo ZIP o un archivo RAW podían ingresar en un bucle de redirección. {% comment %} https://github.com/github/enterprise2/pull/24193, https://github.com/github/enterprise2/pull/24075 {% endcomment %}' - - 'Un límite de tiempo podía impedir que algunas búsquedas de propuestas y solicitudes de cambios proporcionasen resultados de búsqueda completos. {% comment %} https://github.com/github/github/pull/164155, https://github.com/github/github/pull/163845 {% endcomment %}' - - 'Las pestañas personalizadas con caracteres no alfabéticos en pantallas pequeñas no se interpretaban correctamente. {% comment %} https://github.com/github/github/pull/164310, https://github.com/github/github/pull/164159 {% endcomment %}' - - 'Un comportamiento subyacente provocaba fallos cuando se subía contenido a un repositorio de Git habilitado con LFS. {% comment %} https://github.com/github/github/pull/164663, https://github.com/github/github/pull/150179 {% endcomment %}' - - 'En algunos casos poco frecuentes las propuestas podían causar un error 500 cuando se accedía a ellas a través de la interfaz web. {% comment %} https://github.com/github/github/pull/165298, https://github.com/github/github/pull/159674 {% endcomment %}' - known_issues: - - "En una instancia de GitHub\_Enterprise Server recién configurada sin ningún usuario, un atacante podría crear el primer usuario administrador. {% comment %} https://github.com/github/enterprise2/issues/1889 {% endcomment %}" - - 'Las reglas de cortafuegos personalizadas no se mantienen durante una actualización. {% comment %} https://github.com/github/enterprise2/issues/2823 {% endcomment %}' - - 'Los archivos supervisados de Git LFS [cargados desde la interface web](https://github.com/blog/2105-upload-files-to-your-repositories) se han agregado de forma incorrecta y directa al repositorio. {% comment %} https://github.com/github/github/issues/54684 {% endcomment %}' - - "Las incidencias no se pueden cerrar si contienen un enlace permanente a un blob del mismo repositorio en el que la ruta es mayor de 255\_caracteres. {% comment %} https://github.com/github/github/issues/107731 {% endcomment %}" - - 'Cuando se habilita "Los usuarios pueden buscar en GitHub.com" con GitHub Connect, las incidencias en los repositorios privados e internos no se incluyen en los resultados de la búsqueda de GitHub.com. {% comment %} https://github.com/github/admin-experience/issues/571 {% endcomment %}' - - 'Cuando un nodo de réplica está sin conexión en una configuración de disponibilidad alta, es posible que {% data variables.product.product_name %} enrute las solicitudes a {% data variables.product.prodname_pages %} al nodo sin conexión, lo que reduce la disponibilidad de {% data variables.product.prodname_pages %} para los usuarios.' diff --git a/translations/es-ES/data/release-notes/enterprise-server/2-22/7.yml b/translations/es-ES/data/release-notes/enterprise-server/2-22/7.yml deleted file mode 100644 index 094ce031ed..0000000000 --- a/translations/es-ES/data/release-notes/enterprise-server/2-22/7.yml +++ /dev/null @@ -1,57 +0,0 @@ -date: '2021-03-02' -sections: - security_fixes: - - '**HIGH:** An improper access control vulnerability was identified in GitHub Enterprise Server that allowed authenticated users of the instance to gain write access to unauthorized repositories via specifically crafted pull requests and REST API requests. An attacker would need to be able to fork the targeted repository, a setting that is disabled by default for organization owned private repositories. Branch protections such as required pull request reviews or status checks would prevent unauthorized commits from being merged without further review or validation. This vulnerability has been assigned CVE-2021-22861. This issue was reported via the [GitHub Bug Bounty Program](https://bounty.github.com).' - - '**HIGH:** An improper access control vulnerability was identified in the GitHub Enterprise Server GraphQL API that allowed authenticated users of the instance to modify the maintainer collaboration permission of a pull request without proper authorization. By exploiting this vulnerability, an attacker would be able to gain access to head branches of pull requests opened on repositories of which they are a maintainer. Forking is disabled by default for organization owned private repositories and would prevent this vulnerability. Additionally, branch protections such as required pull request reviews or status checks would prevent unauthorized commits from being merged without further review or validation. This vulnerability has been assigned CVE-2021-22863. This issue was reported via the [GitHub Bug Bounty Program](https://bounty.github.com).' - - '**HIGH:** A remote code execution vulnerability was identified in GitHub Enterprise Server that could be exploited when building a GitHub Pages site. User-controlled configuration of the underlying parsers used by GitHub Pages were not sufficiently restricted and made it possible to execute commands on the GitHub Enterprise Server instance. To exploit this vulnerability, an attacker would need permission to create and build a GitHub Pages site on the GitHub Enterprise Server instance. This vulnerability has been assigned CVE-2020-10519 and was reported via the [GitHub Bug Bounty Program](https://bounty.github.com).' - - '**MEDIUM:** GitHub Tokens from GitHub Pages builds could end up in logs.' - - '**LOW:** A specially crafted request to the SVN bridge could trigger a long wait before failure resulting in Denial of Service (DoS).' - - 'Packages have been updated to the latest security versions.' - bugs: - - 'The load-balancer health checks in some cases could cause the babeld logs to fill up with errors about the PROXY protocol.' - - 'An informational message was unintentionally logged as an error during GitHub Enterprise Backup Utilities snapshots, which resulted in unnecessary emails being sent when backups were scheduled by cron jobs that listen for output to stderr.' - - 'While restoring a large backup, exception logging related to Redis memory exhaustion could cause the restore to fail due to a full disk.' - - 'When first setting up a new instance, if you selected "Configure as Replica" you would be unable to start replication.' - - 'When GitHub Actions was enabled, disabling maintenance mode in the management console failed.' - - 'When editing a wiki page a user could experience a 500 error when clicking the Save button.' - - 'An S/MIME signed commit using a certificate with multiple names in the subject alternative name would incorrectly show as "Unverified" in the commit badge.' - - 'Suspended user was sent emails when added to a team.' - - 'User saw 500 error when executing git operations on an instance configured with LDAP authentication.' - - 'The `remove_org_member_package_access` background job was visible in the management console and would continually increase.' - - 'When a repository had a large number of manifests an error `You have reached the maximum number of allowed manifest files (20) for this repository.` was shown on the Insights -> Dependency graph tab. For more information, see [Visualization limits](https://docs.github.com/en/github/managing-security-vulnerabilities/troubleshooting-the-detection-of-vulnerable-dependencies#are-there-limits-which-affect-the-dependency-graph-data).' - - 'When uploading a new license file with a different number of seats from the previous license file, the seat difference was not correctly represented in the enterprise account Settings -> License page.' - - 'The "Prevent repository admins from changing anonymous Git read access" checkbox available in the enterprise account settings could not be successfully enabled or disabled.' - - 'When a GitHub Pages build failed, the email notification contained an incorrect link for support location.' - - 'During a leap year, the user was getting a 404 response when trying to view Contribution activity on a Monday.' - changes: - - 'Added support for [AWS EC2 r5b instance types](https://aws.amazon.com/about-aws/whats-new/2020/12/introducing-new-amazon-ec2-r5b-instances-featuring-60-gbps-of-ebs-bandwidth-and-260K-iops/).' - - 'Adjusted background queue prioritization to more evenly distribute jobs.' - known_issues: - - 'On a freshly set up GitHub Enterprise 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.' - - | - Users may experience assets such as avatars not loading, or a failure to push/pull code. This may be caused by a PID mismatch in the `haproxy-cluster-proxy` service. To determine if you have an affected instance: - - **Single instance** - - 1. Run this in the [administrative shell](https://docs.github.com/en/enterprise-server/admin/configuration/accessing-the-administrative-shell-ssh) (SSH): - - ``` - if [ $(cat /var/run/haproxy-cluster-proxy.pid) -ne $(systemctl show --property MainPID --value haproxy-cluster-proxy) ]; then echo 'Main PID of haproxy-cluster-proxy does not match /var/run/haproxy-cluster-proxy.pid'; fi - ``` - - 2. If it shows that there is a mismatch, reboot the instance. - - **Cluster or High Availability configuration** - - 1. Run this in the [administrative shell](https://docs.github.com/en/enterprise-server/admin/configuration/accessing-the-administrative-shell-ssh) (SSH): - - ``` - ghe-cluster-each -- 'if [ $(cat /var/run/haproxy-cluster-proxy.pid) -ne $(systemctl show --property MainPID --value haproxy-cluster-proxy) ]; then echo 'Main PID of haproxy-cluster-proxy does not match /var/run/haproxy-cluster-proxy.pid'; fi' - ``` - - 2. If it shows one or more nodes are affected, reboot the affected nodes. - - 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. diff --git a/translations/es-ES/data/release-notes/enterprise-server/2-22/8.yml b/translations/es-ES/data/release-notes/enterprise-server/2-22/8.yml deleted file mode 100644 index cee7e07523..0000000000 --- a/translations/es-ES/data/release-notes/enterprise-server/2-22/8.yml +++ /dev/null @@ -1,37 +0,0 @@ -date: '2021-03-16' -sections: - security_fixes: - - Packages have been updated to the latest security versions. - bugs: - - Systemd journal logs were duplicated in multiple places. - - A site admin could get a 500 error page while trying to view issues referenced from private repositories. - - Importing of repository archives from GitHub Enterprise Server that are missing repository files would fail with an error. - known_issues: - - On a freshly set up GitHub Enterprise 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. - - | - Users may experience assets such as avatars not loading, or a failure to push/pull code. This may be caused by a PID mismatch in the `haproxy-cluster-proxy` service. To determine if you have an affected instance: - - **Single instance** - - 1. Run this in the [administrative shell](https://docs.github.com/en/enterprise-server/admin/configuration/accessing-the-administrative-shell-ssh) (SSH): - - ``` - if [ $(cat /var/run/haproxy-cluster-proxy.pid) -ne $(systemctl show --property MainPID --value haproxy-cluster-proxy) ]; then echo 'Main PID of haproxy-cluster-proxy does not match /var/run/haproxy-cluster-proxy.pid'; fi - ``` - - 2. If it shows that there is a mismatch, reboot the instance. - - **Cluster or High Availability configuration** - - 1. Run this in the [administrative shell](https://docs.github.com/en/enterprise-server/admin/configuration/accessing-the-administrative-shell-ssh) (SSH): - - ``` - ghe-cluster-each -- 'if [ $(cat /var/run/haproxy-cluster-proxy.pid) -ne $(systemctl show --property MainPID --value haproxy-cluster-proxy) ]; then echo 'Main PID of haproxy-cluster-proxy does not match /var/run/haproxy-cluster-proxy.pid'; fi' - ``` - - 2. If it shows one or more nodes are affected, reboot the affected nodes. - - 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. diff --git a/translations/es-ES/data/release-notes/enterprise-server/2-22/9.yml b/translations/es-ES/data/release-notes/enterprise-server/2-22/9.yml deleted file mode 100644 index a7186ca8df..0000000000 --- a/translations/es-ES/data/release-notes/enterprise-server/2-22/9.yml +++ /dev/null @@ -1,33 +0,0 @@ -date: '2021-03-23' -intro: Downloads have been disabled due to a major bug affecting multiple customers. A fix will be available in the next patch. -sections: - security_fixes: - - '**HIGH:** A remote code execution vulnerability was identified in GitHub Enterprise Server that could be exploited when building a GitHub Pages site. User-controlled configuration options used by GitHub Pages were not sufficiently restricted and made it possible to override environment variables leading to code execution on the GitHub Enterprise Server instance. To exploit this vulnerability, an attacker would need permission to create and build a GitHub Pages site on the GitHub Enterprise Server instance. This vulnerability affected all versions of GitHub Enterprise Server prior to 3.0.3 and was fixed in 3.0.3, 2.22.9, and 2.21.17. This vulnerability was reported via the GitHub Bug Bounty program and has been assigned CVE-2021-22864.' - - Packages have been updated to the latest security versions. - bugs: - - Running `ghe-cluster-config-init` could cause a cluster to become inoperable. - - Systemd could lose track of HAProxy's PID. - - The mysql-failover warning was displayed indefinitely after a successful failover. - - The `ghe-cluster-config-init` run was not fully accounting for the exit code of background jobs leading to improper handling of preflight checks. - - A Security & Analysis link did not appear in the left-side navigation on the Settings page for repositories. - - After disabling GitHub Packages, some organization pages would return an HTTP 500 error response. - changes: - - Improves reliability of nomad services by implementing the same restart policy introduced in GitHub Enterprise Server 3.0. - - Use a relative number for consul and nomad `bootstrap_expect` allowing for a cluster to bootstrap even if a handful of nodes are down. - - Logs will rotate based on size in addition to time. - - Added kafka-lite to the `ghe-cluster-status` command. - known_issues: - - On a freshly set up GitHub Enterprise 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. - - | - Log rotation may fail to signal services to transition to new log files, leading to older log files continuing to be used, and eventual root disk space exhaustion. - To remedy and/or prevent this issue, run the following commands in the [administrative shell](https://docs.github.com/en/enterprise-server/admin/configuration/accessing-the-administrative-shell-ssh) (SSH), or contact [GitHub Enterprise Support](https://support.github.com/contact) for assistance: - - ``` - printf "PATH=/usr/local/sbin:/usr/local/bin:/usr/local/share/enterprise:/usr/sbin:/usr/bin:/sbin:/bin\n29,59 * * * * root /usr/sbin/logrotate /etc/logrotate.conf\n" | sudo sponge /etc/cron.d/logrotate - sudo /usr/sbin/logrotate -f /etc/logrotate.conf - ``` - - '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.' diff --git a/translations/es-ES/data/release-notes/enterprise-server/3-0/0-rc1.yml b/translations/es-ES/data/release-notes/enterprise-server/3-0/0-rc1.yml deleted file mode 100644 index 6c90d76261..0000000000 --- a/translations/es-ES/data/release-notes/enterprise-server/3-0/0-rc1.yml +++ /dev/null @@ -1,25 +0,0 @@ -date: '2021-01-12' -release_candidate: true -deprecated: true -intro: "Las versiones candidatas para lanzamiento deben probarse en entornos de no producción. Para obtener más información acerca del Programa de candidatos a lanzamiento, consulta el [Blog de GitHub](https://github.blog/2020-12-03-improving-the-ghes-release-process-release-candidates/) o la sección \"[Acerca de las mejoras a lanzamientos nuevos](/admin/overview/about-upgrades-to-new-releases)\"." -sections: - bugs: - - "Ha cambiado el formato de varios archivos de registro, incluida la adición de un PID para diferentes tipos de registro. Esto no afecta a cómo el soporte técnico de GitHub Enterprise utiliza agrupaciones de soporte para solucionar problemas." - - "Al hacer una solicitud de PATCH a la API de configuración de webhook, ya no se borra el secreto del webhook." - known_issues: - - "En una instalación nueva de {% data variables.product.prodname_ghe_server %} que no tenga ningún usuario, cualquier atacante podría crear el primer usuario administrativo." - - El candidato de lanzamiento 1 no es compatible con el modo de agrupación de clústeres. - - Las reglas de firewall personalizadas no se mantienen durante una actualización. - - "Los archivos rastreados del LFS de Git que se [cargaron mediante la interfaz web](https://github.blog/2016-02-18-upload-files-to-your-repositories/) se agregaron incorrecta y directamente al repositorio." - - "Cuando se habilita \"Los usuarios pueden buscar en GitHub.com\" con GitHub Connect, las incidencias en los repositorios privados e internos no se incluyen en los resultados de la búsqueda de GitHub.com." - - "Tras un intento no exitoso de configurar las Acciones, si las inhabilitas después, no podrás crear el primer usuario ni utilizar el aplicativo." - - "El evento de registro de auditoría de \"Mensaje obligatorio visto\" no se está guardando." - - 'Se debe ejecutar a "ghe-config-apply" en una réplica durante la primera configuración antes de que se pueda ejecutar "ghe-repl-setup" para iniciar la replicación.' - - Las utilidades de copia de seguridad pueden activar correos electrónicos innecesarios para los administradores. - - La configuración incorrecta de los paquetes se muestra en la página de vista de miembros de la organización. - - "Después de eliminarte a ti mismo como propietario de la empresa, se te redireccionará a una página 404. La operación es exitosa." - - '"ghe-config-apply" ocasionalmente falla con "ERROR: Failure waiting for nomad jobs to apply" hasta que la cola de trabajos nómada se vacíe. Actualmente, esto requiere que un administrador elimine "/etc/nomad-jobs/queue".' - - "Cuando configuras un nodo de rélica múltiple, el estado de la réplica puede sincronizarse incorrectamente." - - "Los clientes que intentan restablecer un respaldo de 3.0 en una instancia nueva no deberán preconfigurarla, ya que esto podría conllevar a un estado malo para los inicios de sesión de usuario. Te recomendamos restablecerte a una instancia no configurada y nueva." - - "Las versiones candidatas para lanzamiento del servidor de GitHub Enterprise 3.0 aún no están disponibles en Azure Marketplace. Para probar las versiones candidatas para lanzamiento en los entornos de ensayo, inicia una instancia 2.21 o 2.22 y luego actualízala con el paquete de mejora de Azure en la página de descarga." - - Ha aumentado el tamaño de la descarga del paquete de imagen y actualización. Los clientes con conexiones a Internet lentas pueden tardar más tiempo en descargar los paquetes. diff --git a/translations/es-ES/data/release-notes/enterprise-server/3-0/0-rc2.yml b/translations/es-ES/data/release-notes/enterprise-server/3-0/0-rc2.yml deleted file mode 100644 index a320d8213b..0000000000 --- a/translations/es-ES/data/release-notes/enterprise-server/3-0/0-rc2.yml +++ /dev/null @@ -1,23 +0,0 @@ -date: '2021-01-29' -release_candidate: true -deprecated: true -intro: 'Las versiones candidatas para lanzamiento deben probarse en entornos de no producción. Para obtener más información acerca del Programa de candidatos a lanzamiento, consulta el [Blog de GitHub](https://github.blog/2020-12-03-improving-the-ghes-release-process-release-candidates/) o la sección "[Acerca de las mejoras a lanzamientos nuevos](/admin/overview/about-upgrades-to-new-releases)".' -sections: - bugs: - - heading: 'Correcciones para las propuestas conocidas del Candidato a lanzamiento 1' - notes: - - 'Si inhabilitas las Acciones de GitHub seguido de un intento fallido de configurarlas, entonces no podrás crear el primer usuario y utilizar el aplicativo.' - - 'El evento de registro de auditoría "Mensaje obligatorio visto" no se estaba guardando.' - - '"ghe-config-apply" necesitaba ejecutarse en una réplica durante una configuración inicial antes de que "ghe-repl-setup" pudiera ejecutarse para iniciar la replicación.' - - 'Eliminarse como propietario empresarial devolvía un error 404.' - - heading: 'Correcciones para otros problemas' - notes: - - 'Se arreglaron los problemas con las migraciones y mejoras a la versión 3.0.0.' - - 'El versionamiento de utilidades de respaldo ahora funciona para las versiones de candidatos de lanzamiento.' - - 'La generación de paquetes de soporte daba como resultado un error en los registros del orquestador.' - - 'Un restablecimiento grande pudo haber dado como resultado que Redis se quedara sin memoria.' - - 'La casilla de verificación para habilitar las Acciones de GitHub en la consola de administración ahora se puede ver con cualquier método de autenticación.' - - 'Las Acciones de GitHub solo pueden habilitarse si también se configuró el almacenamiento requerido.' - - '"ghe-repl-status" podría fallar silenciosamente si no está configurada la replicación de MSSQL.' - known_issues: - - 'Los problemas conocidos del Candidato a lanzamiento 1 aún se aplican, excluyendo las correcciones de errores listadas.' diff --git a/translations/es-ES/data/release-notes/enterprise-server/3-0/0.yml b/translations/es-ES/data/release-notes/enterprise-server/3-0/0.yml deleted file mode 100644 index 36d3d58fab..0000000000 --- a/translations/es-ES/data/release-notes/enterprise-server/3-0/0.yml +++ /dev/null @@ -1,160 +0,0 @@ -date: '2021-02-16' -intro: The minimum infrastructure requirements have increased for {% data variables.product.prodname_ghe_server %} 3.0+. For more information, see "[About minimum requirements for GitHub Enterprise Server 3.0 and later](/admin/enterprise-management/upgrading-github-enterprise-server#about-minimum-requirements-for-github-enterprise-server-30-and-later)." -sections: - security_fixes: - - '**HIGH:** A remote code execution vulnerability was identified in {% data variables.product.prodname_ghe_server %} that could be exploited when building a {% data variables.product.prodname_pages %} site. User-controlled configuration of the underlying parsers used by {% data variables.product.prodname_pages %} were not sufficiently restricted and made it possible to execute commands on the {% data variables.product.prodname_ghe_server %} instance. To exploit this vulnerability, an attacker would need permission to create and build a {% data variables.product.prodname_pages %} site on the {% data variables.product.prodname_ghe_server %} instance. This vulnerability has been assigned CVE-2020-10519 and was reported via the [GitHub Bug Bounty Program](https://bounty.github.com).' - features: - - heading: GitHub Actions - notes: - - | - [{% data variables.product.prodname_actions %}](https://github.com/features/actions) is now generally available on {% data variables.product.prodname_ghe_server %} 3.0+. Build, test, and deploy your code from {% data variables.product.prodname_dotcom %}. Submit code reviews, branch management, and issue triaging work the way you want. - - This release includes several improvements from the beta of {% data variables.product.prodname_actions %} on {% data variables.product.prodname_ghe_server %}: - - - Enterprise, organization, and repository admins can create security policies for access to {% data variables.product.prodname_actions %} on {% data variables.product.prodname_dotcom_the_website %}. - - Enterprise, organization, and repository admins can allow public repositories to use self-hosted runners. - - Enterprise, organization, and repository admins can now allow workflows to [run on pull requests raised from forks of private repositories](/enterprise-server@3.0/github/setting-up-and-managing-organizations-and-teams/disabling-or-limiting-github-actions-for-your-organization#enabling-workflows-for-private-repository-forks). - - The `workflow_run` event is [now supported](/enterprise-server@3.0/actions/reference/events-that-trigger-workflows#workflow_run) - - Users now have the ability to [disable workflows and enable them at a later date](/enterprise-server@3.0/actions/managing-workflow-runs/disabling-and-enabling-a-workflow). - - Workflow logs have been enhanced for a [better user experience](/enterprise-server@3.0/actions/managing-workflow-runs/using-workflow-run-logs). - - Users can now use private images in container jobs and services. - - The max retention days for [artifacts and logs can now be customized](/enterprise-server@3.0/github/setting-up-and-managing-your-enterprise/configuring-the-retention-period-for-github-actions-artifacts-and-logs-in-your-enterprise-account). - - The runner group API now includes [labels](/enterprise-server@3.0/actions/hosting-your-own-runners/using-labels-with-self-hosted-runners). - - You can now create reusable actions using shell scripts with compose run steps. - - [Encrypted secrets for an organization](/enterprise-server@3.0/actions/reference/encrypted-secrets#creating-encrypted-secrets-for-an-organization) allows you to consolidate secrets across repositories. - - [Workflow templates for an organization](/enterprise-server@3.0/actions/learn-github-actions/sharing-workflows-with-your-organization) streamlines and promotes best practices and consistency across your organization. - - {% data variables.product.prodname_actions %} is not currently supported for enterprises using cluster configurations. - - - heading: GitHub Packages - notes: - - | - [{% data variables.product.prodname_registry %}](https://github.com/features/packages) is a package hosting service, natively integrated with GitHub APIs, Actions, and webhooks. Create an [end-to-end DevOps workflow](/enterprise/3.0/admin/packages/configuring-packages-support-for-your-enterprise) that includes your code, continuous integration, and deployment solutions. - - Supported storage back ends include AWS S3 and MinIO with support for Azure blob coming in a future release. Please note that the current Docker support will be replaced by a beta of the new GitHub Container Registry in the next release. Please review the [updated minimum requirements for your platform](/enterprise/3.0/admin/installation/setting-up-a-github-enterprise-server-instance) before you turn on {% data variables.product.prodname_registry %}. - - When publishing packages to NuGet, users can now use the `--api-key` option to pass their authentication token instead of writing it into a file. For more information, see [Configuring dotnet CLI for use with GitHub Packages](/enterprise-server@3.0/packages/guides/configuring-dotnet-cli-for-use-with-github-packages#publishing-a-package) - - {% data variables.product.prodname_registry %} is not currently supported for enterprises using cluster configurations. - - - heading: GitHub Mobile beta - notes: - - | - [{% data variables.product.prodname_mobile %}](https://github.com/features/) beta allows you to triage notifications and manage issues and pull requests from your device. You can be simultaneously signed into mobile with one user account on {% data variables.product.prodname_dotcom_the_website %} and one user account on {% data variables.product.prodname_ghe_server %}. - - {% data variables.product.prodname_mobile %} beta is now available for {% data variables.product.prodname_ghe_server %}. Sign in with our [Android](https://play.google.com/store/apps/details?id=com.github.android) and [iOS](https://apps.apple.com/app/github/id1477376905) apps to triage notifications and manage issues and pull requests on the go. Administrators can disable mobile support for their Enterprise using the management console or by running `ghe-config app.mobile.enabled false`. - - - heading: Advanced Security Secret Scanning beta - notes: - - | - [Secret Scanning beta](https://github.com/features/security) scans public and private repositories for committed credentials, finds secrets, and notifies the secret provider or admin the moment they are committed into a repository. - - Administrators using {% data variables.product.prodname_GH_advanced_security %} can [enable and configure](/enterprise-server@3.0/admin/configuration/configuring-secret-scanning-for-your-appliance) {% data variables.product.prodname_GH_advanced_security %} secret scanning. You can review the [updated minimum requirements for your platform](/enterprise/3.0/admin/installation/setting-up-a-github-enterprise-server-instance) before you turn on {% data variables.product.prodname_GH_advanced_security %} secret scanning. - - - heading: Advanced Security Code Scanning - notes: - - | - [GitHub Advanced Security code scanning](https://github.com/features/security) is now generally available on GitHub Enterprise Server. Organizations who have purchased Advanced Security can use this capability to do static analysis security testing against their code, and prevent vulnerabilities from making it to their production code using CodeQL, our semantic analysis engine. For more information, see "[Configuring code scanning on your appliance](/en/enterprise-server@3.0/admin/configuration/configuring-code-scanning-for-your-appliance#running-code-scanning-using-github-actions)" - - changes: - - heading: Administration Changes - notes: - - The webhook events delivery system has been rearchitected for higher throughput, faster deliveries, and fewer delayed messages. It also uses less CPU and memory in {% data variables.product.prodname_ghe_server %} 3.0+. - - Organization and Enterprise owners can now see when a team member has been promoted to or demoted from being a team maintainer in the audit log through the new `team.promote_maintainer` and `team.demote_maintainer` audit log events. For more information, see "[Audited actions](/enterprise-server@3.0/admin/user-management/audited-actions)." - - Repository maintainers with existing {% data variables.product.prodname_pages %} sites can [easily update their prior default branch name](/enterprise-server@3.0/github/working-with-github-pages/about-github-pages#publishing-sources-for-github-pages-sites). - - Additional hardware resources are required to run {% data variables.product.prodname_ghe_server %} with any of Actions, Packages or Advanced Security enabled. For more information on the minimum required resources for each supported platform, see "[Setting up a {% data variables.product.prodname_ghe_server %} instance](/enterprise-server@3.0/admin/installation/setting-up-a-github-enterprise-server-instance)." - - Administrators can now [publish a message](/enterprise-server@3.0/admin/user-management/customizing-user-messages-for-your-enterprise), which all users must accept. This can help to onboard new users and surface other organization-specific information and policies. - - - heading: Security Changes - notes: - - Organization owners can now disable publication of {% data variables.product.prodname_pages %} sites from repositories in the organization. Disabling {% data variables.product.prodname_pages %} for the organization will prevent members from creating new Pages sites but will not unpublish existing sites. For more information, see "[Disabling publication of {% data variables.product.prodname_pages %} sites for your organization](/enterprise-server@3.0/github/setting-up-and-managing-organizations-and-teams/disabling-publication-of-github-pages-sites-for-your-organization)." - - A datacenter must be explicitly defined on all nodes before enabling an active replica. - - All usage of SSH fingerprints has been switched to use SHA256 fingerprints as they are used with OpenSSH since version 6.8 as well. This applies to the web interface and also the API where fingerprints are returned such as in GraphQL. The fingerprints follow the OpenSSH format. - - SHA-1 and SHA-256 signature headers (two headers) are sent on webhooks. - - - heading: Developer Changes - notes: - - Majority of the services running in {% data variables.product.prodname_ghe_server %} 3.0+ are now on containers which internally enables GitHub to iterate fast and ship high quality releases - - The webhook events delivery system has been rearchitected for higher throughput, faster deliveries, and fewer delayed messages. - - - heading: API Changes - notes: - - Administrators can now configure and manage the site-wide announcement banner via the REST API. For more information, see the endpoints for "[GitHub Enterprise administration](/enterprise-server@3.0/rest/reference/enterprise-admin#annoucements)." - - A new API endpoint enables the exchange of a user to server token for a user to server token scoped to specific repositories. For more information, see "[Apps](/enterprise-server@3.0/rest/reference/apps#create-a-scoped-access-token)" in the {% data variables.product.prodname_dotcom %} REST API documentation. - - - 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).' diff --git a/translations/es-ES/data/release-notes/enterprise-server/3-0/1.yml b/translations/es-ES/data/release-notes/enterprise-server/3-0/1.yml deleted file mode 100644 index b298260e62..0000000000 --- a/translations/es-ES/data/release-notes/enterprise-server/3-0/1.yml +++ /dev/null @@ -1,71 +0,0 @@ -date: '2021-03-02' -intro: The minimum infrastructure requirements have increased for {% data variables.product.prodname_ghe_server %} 3.0+. For more information, see "[About minimum requirements for GitHub Enterprise Server 3.0 and later](/admin/enterprise-management/upgrading-github-enterprise-server#about-minimum-requirements-for-github-enterprise-server-30-and-later)." -sections: - security_fixes: - - '**HIGH:** An improper access control vulnerability was identified in GitHub Enterprise Server that allowed authenticated users of the instance to gain write access to unauthorized repositories via specifically crafted pull requests and REST API requests. An attacker would need to be able to fork the targeted repository, a setting that is disabled by default for organization owned private repositories. Branch protections such as required pull request reviews or status checks would prevent unauthorized commits from being merged without further review or validation. This vulnerability has been assigned CVE-2021-22861. This issue was reported via the [GitHub Bug Bounty Program](https://bounty.github.com).' - - '**HIGH:** An improper access control vulnerability was identified in the GitHub Enterprise Server GraphQL API that allowed authenticated users of the instance to modify the maintainer collaboration permission of a pull request without proper authorization. By exploiting this vulnerability, an attacker would be able to gain access to head branches of pull requests opened on repositories of which they are a maintainer. Forking is disabled by default for organization owned private repositories and would prevent this vulnerability. Additionally, branch protections such as required pull request reviews or status checks would prevent unauthorized commits from being merged without further review or validation. This vulnerability has been assigned CVE-2021-22863. This issue was reported via the [GitHub Bug Bounty Program](https://bounty.github.com).' - - '**HIGH:** An improper access control vulnerability was identified in GitHub Enterprise Server that allowed an authenticated user with the ability to fork a repository to disclose Actions secrets for the parent repository of the fork. This vulnerability existed due to a flaw that allowed the base reference of a pull request to be updated to point to an arbitrary SHA or another pull request outside of the fork repository. By establishing this incorrect reference in a PR, the restrictions that limit the Actions secrets sent a workflow from forks could be bypassed. This vulnerability affected GitHub Enterprise Server versions 3.0.0, 3.0.0.rc2, and 3.0.0.rc1 and has been assigned CVE-2021-22862. This vulnerability was reported via the GitHub Bug Bounty program.' - - '**MEDIUM:** GitHub Tokens from GitHub Pages builds could end up in logs.' - - 'Packages have been updated to the latest security versions.' - bugs: - - 'The load-balancer health checks in some cases could cause the babeld logs to fill up with errors about the PROXY protocol.' - - 'The HTTP headers were not compliant with HTTP RFC standards in specific responses like 304 status for archives.' - - 'On instances that host Python repositories with the Dependency Graph feature enabled, the instance could become unresponsive due to the root disk filling with error logs.' - - 'An informational message was unintentionally logged as an error during GitHub Enterprise Backup Utilities snapshots, which resulted in unnecessary emails being sent when backups were scheduled by cron jobs that listen for output to stderr.' - - 'On VMWare ESX 6.7 the initial configuration could hang while creating host keys which left the instance inaccessible via SSH.' - - 'When GitHub Actions was enabled, disabling maintenance mode in the management console failed.' - - 'The Package creation setting was shown on the organization member settings page, though this feature is not yet available.' - - 'While enabling secret scanning on the Security & Analysis page the dialog incorrectly mentions private repositories.' - - 'When editing a wiki page a user could experience a 500 error when clicking the Save button.' - - 'An S/MIME signed commit using a certificate with multiple names in the subject alternative name would incorrectly show as "Unverified" in the commit badge.' - - 'User saw 500 error when executing git operations on an instance configured with LDAP authentication.' - - 'Suspended user was sent emails when added to a team.' - - 'When a repository had a large number of manifests an error `You have reached the maximum number of allowed manifest files (20) for this repository.` was shown on the Insights -> Dependency graph tab. For more information, see [Visualization limits](https://docs.github.com/en/github/managing-security-vulnerabilities/troubleshooting-the-detection-of-vulnerable-dependencies#are-there-limits-which-affect-the-dependency-graph-data).' - - 'Fixes users being shown the option to set up the Code Scanning CodeQL Action even if Actions was not enabled for their repository.' - - 'The "Prevent repository admins from changing anonymous Git read access" checkbox available in the enterprise account settings could not be successfully enabled or disabled.' - - 'The modal used to display a mandatory message contained no vertical scrollbar, meaning longer messages could not be viewed in full.' - - 'Redis would sometimes fail to start after a hard reboot or application crash.' - - '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.' - changes: - - 'Satisfy requests concurrently when multiple users are downloading the same archive, resulting in improved performance.' - known_issues: - - 'On a freshly set up GitHub Enterprise 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.' - - '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 [GitHub Enterprise Support](https://support.github.com/contact).' - - '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 `yarn.lock` Javascript manifest files, resulting in HTTP 500 errors in logs.' - - '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.' - - | - Users may experience assets such as avatars not loading, or a failure to push/pull code. This may be caused by a PID mismatch in the `haproxy-cluster-proxy` service. To determine if you have an affected instance: - - **Single instance** - - 1. Run this in the [administrative shell](https://docs.github.com/en/enterprise-server/admin/configuration/accessing-the-administrative-shell-ssh) (SSH): - - ``` - if [ $(cat /var/run/haproxy-cluster-proxy.pid) -ne $(systemctl show --property MainPID --value haproxy-cluster-proxy) ]; then echo 'Main PID of haproxy-cluster-proxy does not match /var/run/haproxy-cluster-proxy.pid'; fi - ``` - - 2. If it shows that there is a mismatch, reboot the instance. - - **Cluster or High Availability configuration** - - 1. Run this in the [administrative shell](https://docs.github.com/en/enterprise-server/admin/configuration/accessing-the-administrative-shell-ssh) (SSH): - - ``` - ghe-cluster-each -- 'if [ $(cat /var/run/haproxy-cluster-proxy.pid) -ne $(systemctl show --property MainPID --value haproxy-cluster-proxy) ]; then echo 'Main PID of haproxy-cluster-proxy does not match /var/run/haproxy-cluster-proxy.pid'; fi' - ``` - - 2. If it shows one or more nodes are affected, reboot the affected nodes. - - '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. diff --git a/translations/es-ES/data/release-notes/enterprise-server/3-0/10.yml b/translations/es-ES/data/release-notes/enterprise-server/3-0/10.yml deleted file mode 100644 index e1019c8ff5..0000000000 --- a/translations/es-ES/data/release-notes/enterprise-server/3-0/10.yml +++ /dev/null @@ -1,19 +0,0 @@ -date: '2021-06-24' -sections: - security_fixes: - - 'Los paquetes se han actualizado a las últimas versiones de seguridad.' - bugs: - - 'Una cantidad más grande de métricas "gauge-dependency-graph-api-dispatch_dispatch" pudo acumularse en la consola de administración.' - - 'El servicio de sshd algunas veces falló en iniciar en instancias que se estaban ejecutando en Google Cloud Platform.' - - 'Los archivos de actualización antiguos persistieron en el disco del usuario, lo cual algunas veces dio como resultado tener condiciones de falta de espacio.' - - 'La rotación de registros algunas veces interrumpía los trabajos en segundo plano.' - - '"gh-migrator" mostró una ruta incorrecta a su registro de salida.' - - 'Un archivo de exportación fallaba al importarse si las solicitudes de revisión contenidas venían de equipos que no estaban presentes en el archivo.' - known_issues: - - 'En un servidor de GitHub Enterprise recién configurado sin usuarios, un atacante podría crear el primer usuario administrador.' - - 'Las reglas de cortafuegos personalizadas se eliminan durante el proceso de actualización.' - - 'Los archivos supervisados de Git LFS [cargados desde la interface web](https://github.com/blog/2105-upload-files-to-your-repositories) se han agregado de manera incorrecta y directa al repositorio.' - - "Las incidencias no se pueden cerrar si contienen un enlace permanente a un blob del mismo repositorio en el que la ruta es mayor de 255\_caracteres." - - 'Cuando se habilita "Los usuarios pueden buscar en GitHub.com" con GitHub Connect, las incidencias en los repositorios privados e internos no se incluyen en los resultados de la búsqueda de GitHub.com.' - - 'Cuando un nodo de réplica está sin conexión en una configuración de disponibilidad alta, es posible que {% data variables.product.product_name %} todavía enrute las solicitudes a {% data variables.product.prodname_pages %} al nodo sin conexión, lo que reduce la disponibilidad de {% data variables.product.prodname_pages %} para los usuarios.' - - 'Los límites de recursos que son específicos para procesar enlaces previos a la recepción podrían ocasionar errores en algunos de ellos.' diff --git a/translations/es-ES/data/release-notes/enterprise-server/3-0/11.yml b/translations/es-ES/data/release-notes/enterprise-server/3-0/11.yml deleted file mode 100644 index f7d5036278..0000000000 --- a/translations/es-ES/data/release-notes/enterprise-server/3-0/11.yml +++ /dev/null @@ -1,26 +0,0 @@ -date: '2021-07-14' -sections: - security_fixes: - - "**ALTO RIESGO:** se ha identificado una vulnerabilidad de salto de directorio en el servidor de GitHub Enterprise que podría explotarse al crear un sitio de GitHub Pages. Las opciones de configuración controladas por el usuario utilizadas por GitHub Pages no estaba lo suficientemente restringida y permitía leer archivos en la instancia del servidor de GitHub Enterprise. Para aprovechar esta vulnerabilidad de seguridad, un atacante necesitaría permiso para crear un sitio de GitHub Pages en la instancia del servidor de GitHub Enterprise. Esta vulnerabilidad afectaba a todas las versiones del servidor de GitHub Enterprise anteriores a la\_3.1.3 y se le ha asignado CVE-2021-22867. Se informó de esta vulnerabilidad mediante el programa de GitHub Bug Bounty." - - 'Los paquetes se han actualizado a las últimas versiones de seguridad.' - bugs: - - 'La variable de vencimiento de fecha de SAML no se pudo configurar.' - - 'Los servicios de aplicación fallaron en sus verificaciones de salud durante una aplicación de configuración antes de que pudieran ingresar a un estado saludable.' - - 'El "ghe-cluster-config-node-init" falló durante la configuración de clúster si se había habilitado el proxy de HTTP.' - - 'Los enlaces previos a la recepción podían encontrar un error de tipo "Failed to resolve full path of the current executable" debido a que un "/proc" no se pudo montar en el contenedor.' - - 'Collectd no resolvió el nombre de host de destino que se estaba reenviando después del inicio principal.' - - 'El trabajo que purgó los repositorios inactivos borrados pudo haber fallado en hacer progreso si alguno de estos repositorios estaba protegido contra borrado debido a las retenciones legales.' - - 'Se producía un error al ejecutar "git nw-gc --pristine".' - - 'Los trabajos en segundo plano se pusieron en la fila de "spam", los cuales no se estaban procesando.' - - 'El método de fusión preferido se restablecerá cuando se reintente después de una fusión fallida de solicitud de cambio.' - - 'Las subidas de Git dieron como resultado un Error de servidor interno 500 durante el proceso de reconciliación del usuario en las instancias que utilizaban el modo de autenticación de LDAP.' - changes: - - 'Se mejoró la eficiencia de la aplicación de configuraciones al omitir las reglas de cortafuegos para permitir IP, las cuales no hubieran cambiado, lo cual ahorró tiempo significativo en los clústeres grandes.' - known_issues: - - 'En un servidor de GitHub Enterprise recién configurado sin usuarios, un atacante podría crear el primer usuario administrador.' - - 'Las reglas de cortafuegos personalizadas se eliminan durante el proceso de actualización.' - - 'Los archivos supervisados de Git LFS [cargados desde la interface web](https://github.com/blog/2105-upload-files-to-your-repositories) se agregan de manera incorrecta y directa al repositorio.' - - "Las incidencias no se pueden cerrar si contienen un enlace permanente a un blob del mismo repositorio en el que la ruta es mayor de 255\_caracteres." - - 'Cuando se habilita "Los usuarios pueden buscar en GitHub.com" con GitHub Connect, las incidencias en los repositorios privados e internos no se incluyen en los resultados de la búsqueda de GitHub.com.' - - 'Cuando un nodo de réplica está sin conexión en una configuración de disponibilidad alta, es posible que {% data variables.product.product_name %} todavía enrute las solicitudes a {% data variables.product.prodname_pages %} al nodo sin conexión, lo que reduce la disponibilidad de {% data variables.product.prodname_pages %} para los usuarios.' - - 'Los límites de recursos que son específicos para procesar enlaces previos a la recepción podrían ocasionar errores en algunos de ellos.' diff --git a/translations/es-ES/data/release-notes/enterprise-server/3-0/12.yml b/translations/es-ES/data/release-notes/enterprise-server/3-0/12.yml deleted file mode 100644 index 235199ee19..0000000000 --- a/translations/es-ES/data/release-notes/enterprise-server/3-0/12.yml +++ /dev/null @@ -1,21 +0,0 @@ -date: '2021-07-27' -sections: - security_fixes: - - 'Los paquetes se han actualizado a las últimas versiones de seguridad.' - bugs: - - 'Los enlaces previos a la recepción personalizados podrían llevar a un error como "error: object directory /data/user/repositories/0/nw/12/34/56/7890/network.git/objects does not exist; check .git/objects/info/alternates".' - - 'El proxy HTTP no autenticado para la compilación de contenedores de las páginas no era compatible para ningún usuario que utilizara proxys HTTP.' - - "Una cantidad significativa de errores\_503 se registraba cada vez que un usuario visitaba la página \"/settings\" de un repositorio si la gráfica de dependencias no estaba habilitada." - - 'Los repositorios internos solo se devolvían cuando un usuario había tenido afiliaciones con el repositorio mediante un equipo o estado de colaborador o cuando se consultaban con el parámetro "?type=internal".' - - 'Los trabajos en segundo plano fallidos tienen reintentos ilimitados, los cuales podrían causar filas muy largas.' - - "Si el trabajo programado para sincronizar vulnerabilidades con GitHub.com intentaba ejecutarse cuando la gráfica de dependencias no estaba habilitada y el análisis de contenido sí estaba habilitado, se creaban una cantidad significativa de errores\_503." - changes: - - 'Los registros de "babeld" ahora incluyen un campo "cmd" para las solicitudes de publicidad de referencia de HTTP en vez de incluirlo únicamente durante las solicitudes de negociación.' - known_issues: - - 'En una instalación nueva de {% data variables.product.prodname_ghe_server %} que no tenga ningún usuario, cualquier atacante podría crear el primer usuario administrativo.' - - 'Las reglas de cortafuegos personalizadas se eliminan durante el proceso de actualización.' - - 'Los archivos supervisados de Git LFS [cargados desde la interface web](https://github.com/blog/2105-upload-files-to-your-repositories) se han agregado de manera incorrecta y directa al repositorio.' - - "Las incidencias no se pueden cerrar si contienen un enlace permanente a un blob del mismo repositorio en el que la ruta es mayor de 255\_caracteres." - - 'Cuando se habilita "Los usuarios pueden buscar en GitHub.com" con GitHub Connect, las incidencias en los repositorios privados e internos no se incluyen en los resultados de la búsqueda de GitHub.com.' - - 'Cuando un nodo de réplica está sin conexión en una configuración de disponibilidad alta, es posible que {% data variables.product.product_name %} todavía enrute las solicitudes a {% data variables.product.prodname_pages %} al nodo sin conexión, lo que reduce la disponibilidad de {% data variables.product.prodname_pages %} para los usuarios.' - - 'Los límites de recursos que son específicos para procesar enlaces previos a la recepción podrían ocasionar errores en algunos de ellos.' diff --git a/translations/es-ES/data/release-notes/enterprise-server/3-0/13.yml b/translations/es-ES/data/release-notes/enterprise-server/3-0/13.yml deleted file mode 100644 index 1edf0379db..0000000000 --- a/translations/es-ES/data/release-notes/enterprise-server/3-0/13.yml +++ /dev/null @@ -1,17 +0,0 @@ -date: '2021-08-10' -sections: - bugs: - - "Cuando se habilitaron las Acciones de GitHub sin ejecutar los respaldos con programación frecuente, el registro de transacción de MSSQL pudo haber crecido más allá de los límites y consumido todo el espacio disponible en el disco de datos del aplicativo, causando una posible interrupción del servicio." - - "Las entradas de registro de auditoría para los cambios realizados a los ajustes de la organización de \"Creación de repositorios\" eran inexactas." - - "El registro excesivo de las excepciones de \"ActionController::UnknownFormat\" causa un uso innecesario de disco." - - "Los valores de \"group_dn\"de LDAP de más de 255 caracteres dieron como resultado que los errores se registraran: \"Datos truncados para la columna 'group_dn' en la fila 1\"." - changes: - - "Los límites de frecuencia abusiva ahora se llaman límites de frecuencia secundarios, ya que el comportamiento que limitan no siempre es abusivo." - known_issues: - - "En una instalación nueva de {% data variables.product.prodname_ghe_server %} que no tenga ningún usuario, cualquier atacante podría crear el primer usuario administrativo." - - Las reglas de cortafuegos personalizadas se eliminan durante el proceso de actualización. - - "Los archivos supervisados de Git LFS [cargados desde la interface web](https://github.com/blog/2105-upload-files-to-your-repositories) se han agregado de manera incorrecta y directa al repositorio." - - Las incidencias no se pueden cerrar si contienen un enlace permanente a un blob del mismo repositorio en el que la ruta es mayor de 255 caracteres. - - "Cuando se habilita \"Los usuarios pueden buscar en GitHub.com\" con GitHub Connect, las incidencias en los repositorios privados e internos no se incluyen en los resultados de la búsqueda de GitHub.com." - - "Cuando un nodo de réplica está sin conexión en una configuración de disponibilidad alta, es posible que {% data variables.product.product_name %} todavía enrute las solicitudes a {% data variables.product.prodname_pages %} al nodo sin conexión, lo que reduce la disponibilidad de {% data variables.product.prodname_pages %} para los usuarios." - - Los límites de recursos que son específicos para procesar enlaces previos a la recepción podrían ocasionar errores en algunos de ellos. diff --git a/translations/es-ES/data/release-notes/enterprise-server/3-0/14.yml b/translations/es-ES/data/release-notes/enterprise-server/3-0/14.yml deleted file mode 100644 index c5f4c4cd63..0000000000 --- a/translations/es-ES/data/release-notes/enterprise-server/3-0/14.yml +++ /dev/null @@ -1,21 +0,0 @@ -date: '2021-08-24' -sections: - security_fixes: - - Los paquetes se han actualizado a las últimas versiones de seguridad. - bugs: - - La agregación de imágenes muy grandes o GIF animados a las imágenes o solicitudes de cambio producía un error. - - "Los mensajes de Journald con relación a las actualizaciones automáticas (\"Agregar una hora aleatoria en h/m/s\".) se registraban en syslog." - - 'Los enlaces previos a la recepción que utilizaron un subshell de bash devolvieron un error de tipo: "No such file or directory".' - - "Los enlaces previos a la recepción que crearon canalizaciones nombradas (FIFO) fallaban o se colgaban, lo cual resultó en un error de tiempo de espera." - - Agregar filtros para que la página de búsqueda avanzada de registros de auditoría no llene la caja de texto de consultas en tiempo real con el valor y prefijo de faceta correcto. - - "Los enlaces de Git hacia la API interna que dio como resultado solicitudes fallidas devolvieron la excepción \"undefined method body for \"success\":String (NoMethodError)\" en vez de devolver un \"nil\" explícito." - - "Cuando se eliminó una integración, fue posible que una aplicación OAuth o integración no relacionadas también se eliminaran." - - "Cuando se agregó un mensaje obligatorio que contenía un caracter de emoji que intentaba ver o cambiar el mensaje, se devolvió un error tipo \"500 Internal Server Error\"." - known_issues: - - "En una instalación nueva de {% data variables.product.prodname_ghe_server %} que no tenga ningún usuario, cualquier atacante podría crear el primer usuario administrativo." - - Las reglas de cortafuegos personalizadas se eliminan durante el proceso de actualización. - - "Los archivos supervisados de Git LFS [cargados desde la interface web](https://github.com/blog/2105-upload-files-to-your-repositories) se han agregado de manera incorrecta y directa al repositorio." - - Las incidencias no se pueden cerrar si contienen un enlace permanente a un blob del mismo repositorio en el que la ruta es mayor de 255 caracteres. - - "Cuando se habilita \"Los usuarios pueden buscar en GitHub.com\" con GitHub Connect, las incidencias en los repositorios privados e internos no se incluyen en los resultados de la búsqueda de GitHub.com." - - "Cuando un nodo de réplica está sin conexión en una configuración de disponibilidad alta, es posible que {% data variables.product.product_name %} todavía enrute las solicitudes a {% data variables.product.prodname_pages %} al nodo sin conexión, lo que reduce la disponibilidad de {% data variables.product.prodname_pages %} para los usuarios." - - Los límites de recursos que son específicos para procesar enlaces previos a la recepción podrían ocasionar errores en algunos de ellos. diff --git a/translations/es-ES/data/release-notes/enterprise-server/3-0/15.yml b/translations/es-ES/data/release-notes/enterprise-server/3-0/15.yml deleted file mode 100644 index 44828b8c03..0000000000 --- a/translations/es-ES/data/release-notes/enterprise-server/3-0/15.yml +++ /dev/null @@ -1,17 +0,0 @@ -date: '2021-09-07' -sections: - security_fixes: - - 'Los paquetes se han actualizado a las últimas versiones de seguridad.' - bugs: - - 'Intentar anular un nodo de réplica recién agregado especificando su UUID con "ghe-repl-teardown" falló sin reportar un error en caso de que la replicación no se hubiera iniciado.' - - 'Las compilaciones de GitHub Pages se estaban pasando por un proxy externo si es que había alguno configurado.' - - 'Los enlaces previos a la recepción que crearon subprocesos no tenían una variable de "PATH" en su entorno, lo cual dio como resultado un error de tipo "No such file or directory".' - - 'MySQL pudo haberse recuperado de un desastre durante una actualización si se hubiera habilitado "mysql-auto-failover".' - known_issues: - - 'En una instalación nueva de {% data variables.product.prodname_ghe_server %} que no tenga ningún usuario, cualquier atacante podría crear el primer usuario administrativo.' - - 'Las reglas de cortafuegos personalizadas se eliminan durante el proceso de actualización.' - - 'Los archivos supervisados de Git LFS [cargados desde la interface web](https://github.com/blog/2105-upload-files-to-your-repositories) se agregan de manera incorrecta y directa al repositorio.' - - "Las incidencias no se pueden cerrar si contienen un enlace permanente a un blob del mismo repositorio en el que la ruta es mayor de 255\_caracteres." - - 'Cuando se habilita "Los usuarios pueden buscar en GitHub.com" con GitHub Connect, las incidencias en los repositorios privados e internos no se incluyen en los resultados de la búsqueda de GitHub.com.' - - 'Cuando un nodo de réplica está sin conexión en una configuración de disponibilidad alta, es posible que {% data variables.product.product_name %} todavía enrute las solicitudes a {% data variables.product.prodname_pages %} al nodo sin conexión, lo que reduce la disponibilidad de {% data variables.product.prodname_pages %} para los usuarios.' - - 'Los límites de recursos que son específicos para procesar enlaces previos a la recepción podrían ocasionar errores en algunos de ellos.' diff --git a/translations/es-ES/data/release-notes/enterprise-server/3-0/16.yml b/translations/es-ES/data/release-notes/enterprise-server/3-0/16.yml deleted file mode 100644 index 45e0386a28..0000000000 --- a/translations/es-ES/data/release-notes/enterprise-server/3-0/16.yml +++ /dev/null @@ -1,18 +0,0 @@ -date: '2021-09-24' -sections: - security_fixes: - - "**ALTO RIESGO:** se ha identificado una vulnerabilidad de salto de directorio en {% data variables.product.prodname_ghe_server %} que podía aprovecharse al compilar un sitio {% data variables.product.prodname_pages %}. Las opciones de configuración controladas por el usuario utilizadas por {% data variables.product.prodname_pages %} no estaban lo suficientemente restringidas y permitían leer archivos en la instancia de {% data variables.product.prodname_ghe_server %}. Para aprovecharse de esta vulnerabilidad, el atacante necesitaba permiso para crear y compilar un sitio de {% data variables.product.prodname_pages %} en la instancia de {% data variables.product.prodname_ghe_server %}. Esta vulnerabilidad afectó a todas las versiones de {% data variables.product.prodname_ghe_server %} anteriores a la\_3.1.8 y se corrigió en las versiones\_3.1.8, 3.0.16 y 2.22.22. Esto se debe a una corrección incompleta para CVE-2021-22867. La vulnerabilidad se reportó mediante el programa GitHub Bug Bounty y se le ha asignado el código CVE-2021-22868. {% comment %} https://github.com/github/pages/pull/3360, https://github.com/github/pages/pull/3357 {% endcomment %}" - - '**RIESGO MEDIO:** una vulnerabilidad de control de acceso inadecuado en {% data variables.product.prodname_ghe_server %} permitía a un trabajo de flujo de trabajo ejecutarse en un grupo de ejecutor autohospedado al que no debería tener acceso. Esto afecta a los clientes que utilizan grupos de ejecutores autohospedados para el control de acceso. Un repositorio con acceso a un grupo de ejecutores de empresa podía acceder a todos los grupos de ejecutores de empresa dentro de la organización a causa de comprobaciones de autenticación incorrectas durante la solicitud. Esto podía causar que el código lo ejecutara no intencionalmente el grupo de ejecutor incorrecto. Esta vulnerabilidad afectó a las versiones de {% data variables.product.prodname_ghe_server %} de 3.0.0 a 3.0.15 y 3.1.0 a 3.1.7 y se corrigió en las versiones 3.0.16 y 3.1.8. Se le asignó CVE-2021-22869. {% comment %} https://github.com/github/enterprise2/pull/27003 {% endcomment %}' - bugs: - - 'Los conteos del trabajador de Resque se mostraron incorrectamente durante el modo de mantenimiento. {% comment %} https://github.com/github/enterprise2/pull/26898, https://github.com/github/enterprise2/pull/26883 {% endcomment %}' - - 'La memoria memcached asignada pudo haber sido cero en el modo de agrupación en clústeres. {% comment %} https://github.com/github/enterprise2/pull/26927, https://github.com/github/enterprise2/pull/26832 {% endcomment %}' - - 'Se han corregido las compilaciones de {% data variables.product.prodname_pages %} para que tengan en cuenta el ajuste NO_PROXY del dispositivo. Esto es importante para dispositivos configurados solo con un proxy HTTP. (actualizado el 30-09-2021) {% comment %} https://github.com/github/pages/pull/3360 {% endcomment %}' - - 'La configuración de GitHub Connect de la instancia de origen siempre se restauraba en instancias nuevas, aunque no se utilizara la opción "--config" de "ghe-restore". Esto causaría un conflicto con la conexión y sincronización de licencia de GitHub Connect si las instancias de origen y destino estuvieran en línea al mismo tiempo. La corrección también requiere actualizar backup-utils a 3.2.0 o posterior. [actualizado el 18-11-2021]' - known_issues: - - 'En una instalación nueva de {% data variables.product.prodname_ghe_server %} que no tenga ningún usuario, cualquier atacante podría crear el primer usuario administrativo.' - - 'Las reglas de cortafuegos personalizadas se eliminan durante el proceso de actualización.' - - 'Los archivos supervisados de Git LFS [cargados desde la interface web](https://github.com/blog/2105-upload-files-to-your-repositories) se han agregado de manera incorrecta y directa al repositorio.' - - "Las incidencias no se pueden cerrar si contienen un enlace permanente a un blob del mismo repositorio en el que la ruta es mayor de 255\_caracteres." - - 'Cuando se habilita "Los usuarios pueden buscar en GitHub.com" con GitHub Connect, las incidencias en los repositorios privados e internos no se incluyen en los resultados de la búsqueda de GitHub.com.' - - 'Cuando un nodo de réplica está sin conexión en una configuración de disponibilidad alta, es posible que {% data variables.product.product_name %} todavía enrute las solicitudes a {% data variables.product.prodname_pages %} al nodo sin conexión, lo que reduce la disponibilidad de {% data variables.product.prodname_pages %} para los usuarios.' - - 'Los límites de recursos que son específicos para procesar enlaces previos a la recepción podrían ocasionar errores en algunos de ellos.' diff --git a/translations/es-ES/data/release-notes/enterprise-server/3-0/17.yml b/translations/es-ES/data/release-notes/enterprise-server/3-0/17.yml deleted file mode 100644 index 4869ff2cde..0000000000 --- a/translations/es-ES/data/release-notes/enterprise-server/3-0/17.yml +++ /dev/null @@ -1,25 +0,0 @@ -date: '2021-10-12' -sections: - security_fixes: - - 'Los paquetes se han actualizado a sus últimas versiones de seguridad. {% comment %} https://github.com/github/enterprise2/pull/27034, https://github.com/github/enterprise2/pull/27010 {% endcomment %}' - bugs: - - 'Los enlaces previos a la recepción personalizados fallaron debido a los límites demasiado restrictivos en la memoria virtual o CPU. {% comment %}https://github.com/github/enterprise2/pull/26971, https://github.com/github/enterprise2/pull/26955 {% endcomment %}' - - 'Al intentar borrar todos los ajustes de configuración existentes con "ghe-cleanup-settings", se producía un error al reiniciar el servicio de la Consola de administración. {% comment %} https://github.com/github/enterprise2/pull/26986, https://github.com/github/enterprise2/pull/26901 {% endcomment %}' - - 'Durante el desmonte de replicación mediante "ghe-repl-teardown", Memcached producía un error al reiniciarse. {% comment %} https://github.com/github/enterprise2/pull/26992, https://github.com/github/enterprise2/pull/26983 {% endcomment %}' - - "Durante los periodos de carga alta, los usuarios recibían códigos de estado HTTP\_503 cuando los servicios ascendentes fallaban en sus revisiones de salud interna. {% comment %} https://github.com/github/enterprise2/pull/27081, https://github.com/github/enterprise2/pull/26999 {% endcomment %}" - - 'Se prohibía que los entornos de los enlaces previos a la recepción llamaran al comando cat mediante BusyBox en Alpine.{% comment %} https://github.com/github/enterprise2/pull/27114, https://github.com/github/enterprise2/pull/27094 {% endcomment %}' - - 'La contraseña de la base de datos externa se registraba en texto simple. {% comment %} https://github.com/github/enterprise2/pull/27172, https://github.com/github/enterprise2/pull/26413 {% endcomment %}' - - 'Podía mostrarse un mensaje de error de "jq" erróneo al ejecutar "ghe-config-apply". {% comment %} https://github.com/github/enterprise2/pull/27203, https://github.com/github/enterprise2/pull/26784 {% endcomment %}' - - 'La recuperación de fallos desde un centro de datos de un clúster primario hacia uno de un clúster secundario fue exitosa, pero al recuperarse de los fallos nuevamente hacia el centro de datos del clúster primario original, no se podían promover los índices de Elasticsearch. {% comment %} https://github.com/github/github/pull/193180, https://github.com/github/github/pull/192447 {% endcomment %}' - - "La página de administrador de sitio para los ejecutores auto-hospedados del repositorio devolvía un error HTTP\_500 {% comment %} https://github.com/github/github/pull/194205 {% endcomment %}" - - 'En algunos casos, los administradores de GitHub Enterprise que intentaban visitar la página "Usuarios inactivos" recibían una respuesta de tipo "502 Bad Gateway" o "504 Gateway Timeout".{% comment %} https://github.com/github/github/pull/194259, https://github.com/github/github/pull/193609 {% endcomment %}' - changes: - - 'Se borran registros de webhook de forma más efectiva que salen de la ventana de retención de bitácoras de webhook. {% comment %} https://github.com/github/enterprise2/pull/27157 {% endcomment %}' - known_issues: - - 'En una instalación nueva de {% data variables.product.prodname_ghe_server %} que no tenga ningún usuario, cualquier atacante podría crear el primer usuario administrativo.' - - 'Las reglas de cortafuegos personalizadas se eliminan durante el proceso de actualización.' - - 'Los archivos supervisados de Git LFS [cargados desde la interface web](https://github.com/blog/2105-upload-files-to-your-repositories) se agregan de manera incorrecta y directa al repositorio.' - - "Las incidencias no se pueden cerrar si contienen un enlace permanente a un blob del mismo repositorio en el que la ruta es mayor de 255\_caracteres." - - 'Cuando se habilita "Los usuarios pueden buscar en GitHub.com" con GitHub Connect, las incidencias en los repositorios privados e internos no se incluyen en los resultados de la búsqueda de GitHub.com.' - - 'Cuando un nodo de réplica está sin conexión en una configuración de disponibilidad alta, es posible que {% data variables.product.product_name %} todavía enrute las solicitudes a {% data variables.product.prodname_pages %} al nodo sin conexión, lo que reduce la disponibilidad de {% data variables.product.prodname_pages %} para los usuarios.' - - 'Los límites de recursos que son específicos para procesar enlaces previos a la recepción podrían ocasionar errores en algunos de ellos.' diff --git a/translations/es-ES/data/release-notes/enterprise-server/3-0/18.yml b/translations/es-ES/data/release-notes/enterprise-server/3-0/18.yml deleted file mode 100644 index 6f1dd208ff..0000000000 --- a/translations/es-ES/data/release-notes/enterprise-server/3-0/18.yml +++ /dev/null @@ -1,15 +0,0 @@ -date: '2021-10-28' -sections: - security_fixes: - - 'Se han añadido a la lista de denegaciones diversas claves públicas SSH que se sabe que son débiles y ya no se pueden registrar. Además, las versiones de GitKraken conocidas por generar claves de SSH débiles (7.6.x, 7.7.x y 8.0.0) tienen bloqueada la función de registro de nuevas claves públicas.' - - 'Los paquetes se han actualizado a las últimas versiones de seguridad.' - bugs: - - 'Los usuarios que eran propietarios de muchas organizaciones no podían utilizar varias partes de la aplicación.' - known_issues: - - 'En una instalación nueva de {% data variables.product.prodname_ghe_server %} que no tenga ningún usuario, cualquier atacante podría crear el primer usuario administrativo.' - - 'Las reglas de cortafuegos personalizadas se eliminan durante el proceso de actualización.' - - 'Los archivos supervisados de Git LFS [cargados desde la interface web](https://github.com/blog/2105-upload-files-to-your-repositories) se agregan de manera incorrecta y directa al repositorio.' - - "Las incidencias no se pueden cerrar si contienen un enlace permanente a un blob del mismo repositorio en el que la ruta es mayor de 255\_caracteres." - - 'Cuando se habilita "Los usuarios pueden buscar en GitHub.com" con GitHub Connect, las incidencias en los repositorios privados e internos no se incluyen en los resultados de la búsqueda de GitHub.com.' - - 'Cuando un nodo de réplica está sin conexión en una configuración de disponibilidad alta, es posible que {% data variables.product.product_name %} todavía enrute las solicitudes a {% data variables.product.prodname_pages %} al nodo sin conexión, lo que reduce la disponibilidad de {% data variables.product.prodname_pages %} para los usuarios.' - - 'Los límites de recursos que son específicos para procesar enlaces previos a la recepción podrían ocasionar errores en algunos de ellos.' diff --git a/translations/es-ES/data/release-notes/enterprise-server/3-0/19.yml b/translations/es-ES/data/release-notes/enterprise-server/3-0/19.yml deleted file mode 100644 index a5b796aa23..0000000000 --- a/translations/es-ES/data/release-notes/enterprise-server/3-0/19.yml +++ /dev/null @@ -1,23 +0,0 @@ -date: '2021-11-09' -sections: - security_fixes: - - A path traversal vulnerability was identified in {% data variables.product.prodname_pages %} builds on {% data variables.product.prodname_ghe_server %} that could allow an attacker to read system files. To exploit this vulnerability, an attacker needed permission to create and build a {% data variables.product.prodname_pages %} site on the {% data variables.product.prodname_ghe_server %} instance. This vulnerability affected all versions of {% data variables.product.prodname_ghe_server %} prior to 3.3, and was fixed in versions 3.0.19, 3.1.11, and 3.2.3. This vulnerability was reported through the {% data variables.product.company_short %} Bug Bounty program and has been assigned CVE-2021-22870. - - Packages have been updated to the latest security versions. - bugs: - - Some Git operations failed after upgrading a {% data variables.product.prodname_ghe_server %} 3.x cluster because of the HAProxy configuration. - - Unicorn worker counts might have been set incorrectly in clustering mode. - - Resqued worker counts might have been set incorrectly in clustering mode. - - If Ubuntu's Uncomplicated Firewall (UFW) status was inactive, a client could not clearly see it in the logs. - - Some pages and Git-related background jobs might not run in cluster mode with certain cluster configurations. - - The enterprise audit log page would not display audit events for {% data variables.product.prodname_secret_scanning %}. - - 'Users were not warned about potentially dangerous bidirectional unicode characters when viewing files. For more information, see "[Warning about bidirectional Unicode text](https://github.co/hiddenchars)" in {% data variables.product.prodname_blog %}.' - - Hookshot Go sent distribution type metrics that Collectd could not handle, which caused a ballooning of parsing errors. - - Public repositories displayed unexpected results from {% data variables.product.prodname_secret_scanning %} with a type of `Unknown Token`. - 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. - - 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. diff --git a/translations/es-ES/data/release-notes/enterprise-server/3-0/2.yml b/translations/es-ES/data/release-notes/enterprise-server/3-0/2.yml deleted file mode 100644 index c50eeb2eb9..0000000000 --- a/translations/es-ES/data/release-notes/enterprise-server/3-0/2.yml +++ /dev/null @@ -1,57 +0,0 @@ -date: '2021-03-16' -intro: The minimum infrastructure requirements have increased for {% data variables.product.prodname_ghe_server %} 3.0+. For more information, see "[About minimum requirements for GitHub Enterprise Server 3.0 and later](/admin/enterprise-management/upgrading-github-enterprise-server#about-minimum-requirements-for-github-enterprise-server-30-and-later)." -sections: - security_fixes: - - Packages have been updated to the latest security versions. - bugs: - - During a backup an error "Warning: One or more storage objects were not found on the source appliance." was occurring when attempting to clean up purgeable storage objects. - - Dependency graph failed to parse `yarn.lock` JavaScript manifest files, resulting in HTTP 500 errors in logs. - - Disabling GitHub Actions would sometimes fail. - - Custom pre-receive hooks weren't allowed to write to `/tmp`, preventing some scripts from running correctly. - - Systemd journal logs were duplicated in multiple places. - - A timezone set on GitHub Enterprise 11.10.x or earlier was reset to UTC time after upgrading to 3.0 which caused timestamps to shift in some instances. - - Clicking "Publish your first package" in the packages sidebar on a repository would lead to an empty page. - - A site admin could get a 500 error page while trying to view issues referenced from private repositories. - - After disabling GitHub Packages, some organization pages would return an HTTP 500 error response. - - Importing of repository archives from GitHub Enterprise Server that are missing repository files would fail with an error. - - Repository [deploy keys](/developers/overview/managing-deploy-keys) were unable to be used with repositories containing LFS objects. - - In the packages sidebar of a repository, the Docker icon was gray and a tool tip displayed "This service is deprecated". - - Webhooks configured with a content type of `application/x-www-form-urlencoded` did not receive query parameters in the POST request body. - - Users could dismiss a mandatory message without checking all checkboxes. - - In some cases after upgrading from a 2.22.X instance, the web interface assets were missing and the page would not render correctly. - - Running `ghe-config-apply` could time out with `Failure waiting for nomad jobs to apply` due to `'job' stanza not found`. - known_issues: - - On a freshly set up GitHub Enterprise 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. - - 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 [GitHub Enterprise Support](https://support.github.com/contact). - - 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. - - 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. - - | - Users may experience assets such as avatars not loading, or a failure to push/pull code. This may be caused by a PID mismatch in the `haproxy-cluster-proxy` service. To determine if you have an affected instance: - - **Single instance** - - 1. Run this in the [administrative shell](https://docs.github.com/en/enterprise-server/admin/configuration/accessing-the-administrative-shell-ssh) (SSH): - - ``` - if [ $(cat /var/run/haproxy-cluster-proxy.pid) -ne $(systemctl show --property MainPID --value haproxy-cluster-proxy) ]; then echo 'Main PID of haproxy-cluster-proxy does not match /var/run/haproxy-cluster-proxy.pid'; fi - ``` - - 2. If it shows that there is a mismatch, reboot the instance. - - **Cluster or High Availability configuration** - - 1. Run this in the [administrative shell](https://docs.github.com/en/enterprise-server/admin/configuration/accessing-the-administrative-shell-ssh) (SSH): - - ``` - ghe-cluster-each -- 'if [ $(cat /var/run/haproxy-cluster-proxy.pid) -ne $(systemctl show --property MainPID --value haproxy-cluster-proxy) ]; then echo 'Main PID of haproxy-cluster-proxy does not match /var/run/haproxy-cluster-proxy.pid'; fi' - ``` - - 2. If it shows one or more nodes are affected, reboot the affected nodes. - - 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. diff --git a/translations/es-ES/data/release-notes/enterprise-server/3-0/20.yml b/translations/es-ES/data/release-notes/enterprise-server/3-0/20.yml deleted file mode 100644 index 5669a57168..0000000000 --- a/translations/es-ES/data/release-notes/enterprise-server/3-0/20.yml +++ /dev/null @@ -1,21 +0,0 @@ -date: '2021-11-23' -sections: - security_fixes: - - 'Los paquetes se han actualizado a las últimas versiones de seguridad.' - bugs: - - 'Los enlaces previos a la recepción fallaron debido a un "PATH" sin definir.' - - 'La ejecución de "ghe-repl-setup" devolvió un error de tipo: "cannot create directory /data/user/elasticsearch: File exists" si la instancia se había configurado anteriormente como una réplica.' - - 'En ambientes de clúster grandes, el backend de autenticación podría no estar disponible en un subconjunto de nodos de frontend.' - - 'Algunos servicios críticos pudieron no haber estado disponibles en los nodos del backend en el clúster de GHES.' - changes: - - 'Una capa exterior adicional de compresión de "gzip" al crear un conjunto de soporte de clústeres con "ghe-cluster-suport-bundle" ahora está desactivado de manera predeterminada. Esta compresión exterior puede aplicarse opcionalmente con la opción de la línea de comandos "ghe-cluster-suport-bundle -c".' - - 'Agregamos texto extra a la consola de administración para recordarles a los usuarios sobre la recolección de datos de las apps móviles para propósitos de mejora de la experiencia.' - - 'El registro de conexión de datos de {% data variables.product.prodname_github_connect %} ahora incluye una lista de características de {% data variables.product.prodname_github_connect %} habilitadas. [Actualizado el 2021-12-09]' - known_issues: - - 'En una instalación nueva de {% data variables.product.prodname_ghe_server %} que no tenga ningún usuario, cualquier atacante podría crear el primer usuario administrativo.' - - 'Las reglas de cortafuegos personalizadas se eliminan durante el proceso de actualización.' - - 'Los archivos supervisados de Git LFS [cargados desde la interface web](https://github.com/blog/2105-upload-files-to-your-repositories) se agregan de manera incorrecta y directa al repositorio.' - - "Las incidencias no se pueden cerrar si contienen un enlace permanente a un blob del mismo repositorio en el que la ruta es mayor de 255\_caracteres." - - 'Cuando se habilita "Los usuarios pueden buscar en GitHub.com" con GitHub Connect, las incidencias en los repositorios privados e internos no se incluyen en los resultados de la búsqueda de GitHub.com.' - - 'Cuando un nodo de réplica está sin conexión en una configuración de disponibilidad alta, es posible que {% data variables.product.product_name %} todavía enrute las solicitudes a {% data variables.product.prodname_pages %} al nodo sin conexión, lo que reduce la disponibilidad de {% data variables.product.prodname_pages %} para los usuarios.' - - 'Los límites de recursos que son específicos para procesar enlaces previos a la recepción podrían ocasionar errores en algunos de ellos.' diff --git a/translations/es-ES/data/release-notes/enterprise-server/3-0/21.yml b/translations/es-ES/data/release-notes/enterprise-server/3-0/21.yml deleted file mode 100644 index eb4de56212..0000000000 --- a/translations/es-ES/data/release-notes/enterprise-server/3-0/21.yml +++ /dev/null @@ -1,22 +0,0 @@ -date: '2021-12-07' -sections: - security_fixes: - - 'Los paquetes de soporte podrían incluir archivos sensibles si cumplen con un conjunto de características específicas.' - - "Se identificó una vulnerabilidad de representación incorrecta en la IU en el servidor de GitHub Enterprise que permitía otorgar más permisos de los que se mostraban al usuario en la aprobación durante el flujo web de autorización de usuarios en una GitHub App. Esta vulnerabilidad afectaba a todas las versiones de GitHub\_Enterprise Server anteriores a la\_3.3 y se ha corregido en las versiones\_3.2.5, 3.1.13 y 3.0.21. Esta vulnerabilidad se notificó mediante el programa de recompensas de GitHub por la detección de errores y se le ha asignado [CVE-2021-41598](https://www.cve.org/CVERecord?id=CVE-2021-41598)." - - "Se identificó una vulnerabilidad de ejecución de código remoto en el servidor de GitHub Enterprise que podría aprovecharse al crear un sitio de GitHub Pages. Esta vulnerabilidad afectaba a todas las versiones de GitHub\_Enterprise Server anteriores a la\_3.3 y se ha corregido en las versiones\_3.0.21, 3.1.13 y 3.2.5. Esta vulnerabilidad se notificó mediante el programa de recompensas de GitHub por la detección de errores y se le ha asignado [CVE-2021-41599](https://www.cve.org/CVERecord?id=CVE-2021-41599). Actualizado el 17 de febrero de 2022." - bugs: - - 'La ejecución "ghe-config-apply" pudo fallar en ocasiones debido a problemas con los permisos en "/data/user/tmp/pages".' - - 'Una mala configuración en la consola de administración causó errores de programación.' - - 'Docker retenía los archivos de registro abiertos después de una rotación de registros.' - - 'Las solicitudes de GraphQL no configuraban la variable GITHUB_USER_IP en los entornos de enlaces previos a la recepción.' - changes: - - 'Se clarificó una explicación del estilo de ruta de Acciones en la documentación.' - - 'Se han actualizado las URL de contacto de soporte técnico para utilizar el sitio de soporte actual, support.github.com.' - known_issues: - - 'En una instalación nueva de {% data variables.product.prodname_ghe_server %} que no tenga ningún usuario, cualquier atacante podría crear el primer usuario administrativo.' - - 'Las reglas de cortafuegos personalizadas se eliminan durante el proceso de actualización.' - - 'Los archivos supervisados de Git LFS [cargados desde la interface web](https://github.com/blog/2105-upload-files-to-your-repositories) se han agregado de manera incorrecta y directa al repositorio.' - - "Las incidencias no se pueden cerrar si contienen un enlace permanente a un blob del mismo repositorio en el que la ruta es mayor de 255\_caracteres." - - 'Cuando se habilita "Los usuarios pueden buscar en GitHub.com" con GitHub Connect, las incidencias en los repositorios privados e internos no se incluyen en los resultados de la búsqueda de GitHub.com.' - - 'Cuando un nodo de réplica está sin conexión en una configuración de disponibilidad alta, es posible que {% data variables.product.product_name %} todavía enrute las solicitudes a {% data variables.product.prodname_pages %} al nodo sin conexión, lo que reduce la disponibilidad de {% data variables.product.prodname_pages %} para los usuarios.' - - 'Los límites de recursos que son específicos para procesar enlaces previos a la recepción podrían ocasionar errores en algunos de ellos.' diff --git a/translations/es-ES/data/release-notes/enterprise-server/3-0/22.yml b/translations/es-ES/data/release-notes/enterprise-server/3-0/22.yml deleted file mode 100644 index 392d6bb81c..0000000000 --- a/translations/es-ES/data/release-notes/enterprise-server/3-0/22.yml +++ /dev/null @@ -1,13 +0,0 @@ -date: '2021-12-13' -sections: - security_fixes: - - '{% octicon "alert" aria-label="The alert icon" %} **RIESGO CRÍTICO:** una vulnerabilidad de ejecución de código remoto en la biblioteca Log4j, identificada como [CVE-2021-44228](https://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2021-44228), afectaba a todas las versiones de {% data variables.product.prodname_ghe_server %} anteriores a 3.3.1. La biblioteca Log4j se utiliza en un servicio de código abierto que se ejecuta en instancias {% data variables.product.prodname_ghe_server %}. Esta vulnerabilidad se corrigió en las versiones 3.0.22, 3.1.14, 3.2.6 y 3.3.1 de {% data variables.product.prodname_ghe_server %}. Para obtener más información, consulta [esta publicación](https://github.blog/2021-12-13-githubs-response-to-log4j-vulnerability-cve-2021-44228/) en el blog de GitHub.' - - '**Actualización del 17 de diciembre de 2021**: las correcciones de esta versión también solucionan [CVE-2021-45046](https://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2021-45046), que también se publicó después de esta versión. No se requiere ninguna actualización adicional de {% data variables.product.prodname_ghe_server %} para mitigar CVE-2021-44228 y CVE-2021-45046.' - known_issues: - - "En una instalación nueva de {% data variables.product.prodname_ghe_server %} que no tenga ningún usuario, cualquier atacante podría crear el primer usuario administrativo." - - Las reglas de cortafuegos personalizadas se eliminan durante el proceso de actualización. - - "Los archivos supervisados de Git LFS [cargados desde la interface web](https://github.com/blog/2105-upload-files-to-your-repositories) se han agregado de manera incorrecta y directa al repositorio." - - Las incidencias no se pueden cerrar si contienen un enlace permanente a un blob del mismo repositorio en el que la ruta es mayor de 255 caracteres. - - "Cuando se habilita \"Los usuarios pueden buscar en GitHub.com\" con GitHub Connect, las incidencias en los repositorios privados e internos no se incluyen en los resultados de la búsqueda de GitHub.com." - - "Cuando un nodo de réplica está sin conexión en una configuración de disponibilidad alta, es posible que {% data variables.product.product_name %} todavía enrute las solicitudes a {% data variables.product.prodname_pages %} al nodo sin conexión, lo que reduce la disponibilidad de {% data variables.product.prodname_pages %} para los usuarios." - - Los límites de recursos que son específicos para procesar enlaces previos a la recepción podrían ocasionar errores en algunos de ellos. diff --git a/translations/es-ES/data/release-notes/enterprise-server/3-0/23.yml b/translations/es-ES/data/release-notes/enterprise-server/3-0/23.yml deleted file mode 100644 index 004246f9cd..0000000000 --- a/translations/es-ES/data/release-notes/enterprise-server/3-0/23.yml +++ /dev/null @@ -1,19 +0,0 @@ -date: '2022-01-18' -sections: - security_fixes: - - "Los paquetes se han actualizado a las últimas versiones de seguridad. En estas actualizaciones, Log4j se ha actualizado a la versión 2.17.1. Nota: las mitigaciones anteriores publicadas en\_3.3.1, 3.2.6, 3.1.14, y 3.0.22 son suficientes para abordar el impacto de CVE-2021-44228, CVE-2021-45046, CVE-2021-45105 y CVE-2021-44832 en estas versiones del servidor de GitHub Enterprise." - - 'Sanitizar más secretos en los paquetes de soporte generados' - - 'Los paquetes se han actualizado a las últimas versiones de seguridad.' - bugs: - - 'La ejecución "ghe-config-apply" pudo fallar en ocasiones debido a problemas con los permisos en "/data/user/tmp/pages".' - - 'El botón de guardar en la consola de almacenamiento no se pudo alcanzar desplazándose en navegadores de menor resolución.' - - 'Las gráficas de monitoreo de tráfico de almacenamiento e IOPS no se actualizaron después de la actualización de la versión de collectd.' - - 'Algunos trabajos relacionados con webhooks pudieron haber generado una gran cantidad de registros.' - known_issues: - - 'En una instalación nueva de {% data variables.product.prodname_ghe_server %} que no tenga ningún usuario, cualquier atacante podría crear el primer usuario administrativo.' - - 'Las reglas de cortafuegos personalizadas se eliminan durante el proceso de actualización.' - - 'Los archivos supervisados de Git LFS [cargados desde la interface web](https://github.com/blog/2105-upload-files-to-your-repositories) se han agregado de manera incorrecta y directa al repositorio.' - - "Las incidencias no se pueden cerrar si contienen un enlace permanente a un blob del mismo repositorio en el que la ruta es mayor de 255\_caracteres." - - 'Cuando se habilita "Los usuarios pueden buscar en GitHub.com" con GitHub Connect, las incidencias en los repositorios privados e internos no se incluyen en los resultados de la búsqueda de GitHub.com.' - - 'Cuando un nodo de réplica está sin conexión en una configuración de disponibilidad alta, es posible que {% data variables.product.product_name %} todavía enrute las solicitudes a {% data variables.product.prodname_pages %} al nodo sin conexión, lo que reduce la disponibilidad de {% data variables.product.prodname_pages %} para los usuarios.' - - 'Los límites de recursos que son específicos para procesar enlaces previos a la recepción podrían ocasionar errores en algunos de ellos.' diff --git a/translations/es-ES/data/release-notes/enterprise-server/3-0/24.yml b/translations/es-ES/data/release-notes/enterprise-server/3-0/24.yml deleted file mode 100644 index c933dc8361..0000000000 --- a/translations/es-ES/data/release-notes/enterprise-server/3-0/24.yml +++ /dev/null @@ -1,20 +0,0 @@ -date: '2022-02-01' -sections: - security_fixes: - - 'Los paquetes se han actualizado a las últimas versiones de seguridad.' - bugs: - - 'Las páginas no estaban disponibles después de una rotación de secretos de MySQL hasta que "nginx" se restablecía manualmente.' - - 'Al configurar la programación de mantenimiento con una fecha ISO 8601, el tiempo programado real no coincidía debido a que la zona horaria no se transformaba a UTC.' - - 'El número de versión no se actualizaba correctamente después de instalar una revisión en caliente utilizando "ghe-cluster-each".' - - 'Los mensajes de errores espurios relacionados con "cloud-config.service" se generaban en la consola.' - - 'Al utilizar la autenticación CAS y activar la opción "Reactivar usuarios suspendidos", dichos usuarios no se reactivaban automáticamente.' - changes: - - 'El registro de conexión de datos de GitHub Connect ahora incluye un recuento de la cantidad de usuarios activos e inactivos y el periodo de inactividad configurado.' - known_issues: - - 'En una instalación nueva de {% data variables.product.prodname_ghe_server %} que no tenga ningún usuario, cualquier atacante podría crear el primer usuario administrativo.' - - 'Las reglas de cortafuegos personalizadas se eliminan durante el proceso de actualización.' - - 'Los archivos supervisados de Git LFS [cargados desde la interface web](https://github.com/blog/2105-upload-files-to-your-repositories) se han agregado de manera incorrecta y directa al repositorio.' - - "Las incidencias no se pueden cerrar si contienen un enlace permanente a un blob del mismo repositorio en el que la ruta es mayor de 255\_caracteres." - - 'Cuando se habilita "Los usuarios pueden buscar en GitHub.com" con GitHub Connect, las incidencias en los repositorios privados e internos no se incluyen en los resultados de la búsqueda de GitHub.com.' - - 'Cuando un nodo de réplica está sin conexión en una configuración de disponibilidad alta, es posible que {% data variables.product.product_name %} todavía enrute las solicitudes a {% data variables.product.prodname_pages %} al nodo sin conexión, lo que reduce la disponibilidad de {% data variables.product.prodname_pages %} para los usuarios.' - - 'Los límites de recursos que son específicos para procesar enlaces previos a la recepción podrían ocasionar errores en algunos de ellos.' diff --git a/translations/es-ES/data/release-notes/enterprise-server/3-0/25.yml b/translations/es-ES/data/release-notes/enterprise-server/3-0/25.yml deleted file mode 100644 index 8cab7ef1df..0000000000 --- a/translations/es-ES/data/release-notes/enterprise-server/3-0/25.yml +++ /dev/null @@ -1,12 +0,0 @@ -date: '2022-02-17' -sections: - security_fixes: - - 'Los paquetes se han actualizado a las últimas versiones de seguridad.' - known_issues: - - 'En una instancia recién configurada de {% data variables.product.prodname_ghe_server %} sin ningún usuario, un atacante podría crear el primer usuario administrador.' - - 'Las reglas de cortafuegos personalizadas se eliminan durante el proceso de actualización.' - - 'Los archivos supervisados de Git LFS [cargados desde la interface web](https://github.com/blog/2105-upload-files-to-your-repositories) se han agregado de manera incorrecta y directa al repositorio.' - - "Las incidencias no se pueden cerrar si contienen un enlace permanente a un blob del mismo repositorio en el que la ruta es mayor de 255\_caracteres." - - 'Cuando se habilita "Los usuarios pueden buscar en GitHub.com" con GitHub Connect, las incidencias en los repositorios privados e internos no se incluyen en los resultados de la búsqueda de GitHub.com.' - - 'Cuando un nodo de réplica está sin conexión en una configuración de disponibilidad alta, es posible que {% data variables.product.product_name %} todavía enrute las solicitudes a {% data variables.product.prodname_pages %} al nodo sin conexión, lo que reduce la disponibilidad de {% data variables.product.prodname_pages %} para los usuarios.' - - 'Los límites de recursos que son específicos para procesar enlaces previos a la recepción podrían ocasionar errores en algunos de ellos.' diff --git a/translations/es-ES/data/release-notes/enterprise-server/3-0/3.yml b/translations/es-ES/data/release-notes/enterprise-server/3-0/3.yml deleted file mode 100644 index 468174853d..0000000000 --- a/translations/es-ES/data/release-notes/enterprise-server/3-0/3.yml +++ /dev/null @@ -1,42 +0,0 @@ -date: '2021-03-23' -intro: Downloads have been disabled due to a major bug affecting multiple customers. A fix will be available in the next patch. -sections: - security_fixes: - - '**HIGH:** A remote code execution vulnerability was identified in GitHub Enterprise Server that could be exploited when building a GitHub Pages site. User-controlled configuration options used by GitHub Pages were not sufficiently restricted and made it possible to override environment variables leading to code execution on the GitHub Enterprise Server instance. To exploit this vulnerability, an attacker would need permission to create and build a GitHub Pages site on the GitHub Enterprise Server instance. This vulnerability affected all versions of GitHub Enterprise Server prior to 3.0.3 and was fixed in 3.0.3, 2.22.9, and 2.21.17. This vulnerability was reported via the GitHub Bug Bounty program and has been assigned CVE-2021-22864.' - - Packages have been updated to the latest security versions. - bugs: - - Running `ghe-cluster-config-init` could cause a cluster to become inoperable. - - Resolving merge conflicts in the GUI would fail when custom pre-receive hooks are configured on the repository. - - '`launch-deployer` and `launch-receiver` were logging at DEBUG level and filling logs with unnecessary information.' - - Systemd could lose track of HAProxy's PID. - - When Actions was configured to use S3 storage, the logs for an action would sometimes fail to load. - - The mysql-failover warning was displayed indefinitely after a successful failover. - - The `ghe-cluster-config-init` run was not fully accounting for the exit code of background jobs leading to improper handling of preflight checks. - - When enabling GitHub Actions, initialization could fail silently. - - When vulnerability alerting is enabled, upgrades to the 3.0 series would fail. - - Jobs related to Codespaces were being enqueued leading to an accumulation of unprocessed jobs. - changes: - - Use a relative number for consul and nomad `bootstrap_expect` allowing for a cluster to bootstrap even if a handful of nodes are down. - - Logs will rotate based on size in addition to time. - - Added kafka-lite to the `ghe-cluster-status` command. - known_issues: - - On a freshly set up GitHub Enterprise 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. - - 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 [GitHub Enterprise Support](https://support.github.com/contact). - - 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. - - 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. - - | - Log rotation may fail to signal services to transition to new log files, leading to older log files continuing to be used, and eventual root disk space exhaustion. - To remedy and/or prevent this issue, run the following commands in the [administrative shell](https://docs.github.com/en/enterprise-server/admin/configuration/accessing-the-administrative-shell-ssh) (SSH), or contact [GitHub Enterprise Support](https://support.github.com/) for assistance: - - ``` - printf "PATH=/usr/local/sbin:/usr/local/bin:/usr/local/share/enterprise:/usr/sbin:/usr/bin:/sbin:/bin\n29,59 * * * * root /usr/sbin/logrotate /etc/logrotate.conf\n" | sudo sponge /etc/cron.d/logrotate - sudo /usr/sbin/logrotate -f /etc/logrotate.conf - ``` - - 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. diff --git a/translations/es-ES/data/release-notes/enterprise-server/3-0/4.yml b/translations/es-ES/data/release-notes/enterprise-server/3-0/4.yml deleted file mode 100644 index 10bf0045ba..0000000000 --- a/translations/es-ES/data/release-notes/enterprise-server/3-0/4.yml +++ /dev/null @@ -1,27 +0,0 @@ -date: '2021-04-01' -intro: "Los requisitos mínimos de infraestructura han aumentado para {% data variables.product.prodname_ghe_server %}\_3.0+. Para obtener más información, consulta \"[Acerca de los requisitos mínimos para GitHub Enterprise Server\_3.0 y versiones posteriores](/admin/enterprise-management/upgrading-github-enterprise-server#about-minimum-requirements-for-github-enterprise-server-30-and-later)\"" -sections: - security_fixes: - - "**RIEGO ALTO:** se ha identificado una vulnerabilidad de control de acceso incorrecta en GitHub\_Enterprise Server que permitía que tokens de acceso generados desde el [flujo de autenticación web] de una GitHub App (https://docs.github.com/en/developers/apps/identifying-and-authorizing-users-for-github-apps#web-application-flow) leyeran metadatos de repositorios privados mediante la API de REST sin tener los permisos correctos asignados. Para aprovechar esta vulnerabilidad, un atacante tendría que crear una aplicación de GitHub en la instancia y hacer que el usuario la autorice mediante el flujo de autenticación web. Los metadatos de repositorio privado devueltos estarían limitados a repositorios propiedad del usuario identificado por el token. Esta vulnerabilidad afectaba a todas las versiones de GitHub\_Enterprise Server anteriores a la\_3.0.4 y se ha corregido en las versiones\_3.0.4, 2.22.10 y 2.21.18. Esta vulnerabilidad se ha asignado a CVE-2021-22865 y se ha notificado mediante [GitHub\_Bug Bounty Program](https://bounty.github.com)." - - 'Los paquetes se han actualizado a las últimas versiones de seguridad.' - bugs: - - 'Cuando se habilitaba el modo de mantenimiento, algunos servicios se seguían mostrando como "procesos activos", aún cuando se esperaba que estuvieran ejecutándose y no deberían mostrarse.' - - 'Después de actualizar de una versión 2.22.x a una 3.0.x con Acciones de GitHub habilitado, la versión del ejecutor auto-hospedado no se actualizaba y no se realizaban actualizaciones auto-hospedadas.' - - 'Las compilaciones de las páginas antiguas de GitHub no se limpiaban y esto llevaba a un incremento en el uso de disco.' - - '"memcached" no se estaba ejecutando en las réplicas activas.' - - 'La actualización fallaba al actualizar los permisos de archivo cuando se habilitaba Acciones de GitHub.' - - 'Algunos servicios que daban la hora UTC de manera predeterminada no utilizaban la zona horaria definida en GitHub Enterprise 11.10.x o una versión anterior.' - - 'Los servicios no realizaban la transición a los nuevos archivos de registro como parte de la rotación de registros, lo que generaba un aumento del uso de disco.' - - 'La utilidad de línea de comando "ghe-saml-mapping-csv" producía un mensaje de advertencia.' - - 'La etiqueta de los resultados de la búsqueda para los repositorios internos se mostraba como "Privada" en vez de como "Interna".' - known_issues: - - 'En un servidor de GitHub Enterprise recién configurado sin usuarios, un atacante podría crear el primer usuario administrador.' - - 'Las reglas de firewall personalizadas no se mantienen durante una actualización.' - - 'Los archivos supervisados de Git LFS [cargados desde la interface web](https://github.com/blog/2105-upload-files-to-your-repositories) se han agregado de manera incorrecta y directa al repositorio.' - - "Las incidencias no se pueden cerrar si contienen un vínculo permanente a un blob en el mismo repositorio en el que la ruta de acceso de archivo del blob tiene más de 255\_caracteres." - - 'Cuando se habilita "Los usuarios pueden buscar en GitHub.com" con GitHub Connect, las incidencias en los repositorios privados e internos no se incluyen en los resultados de la búsqueda de GitHub.com.' - - 'La interpretación de Jupyter Notebook en la IU web podría fallar si el bloc de notas incluye caracteres diferentes a los de ASCII UTF-8.' - - 'El reStructuredText (RST) que se representa en la IU web podría fallar y mostrar un texto de marcado RST sin procesar.' - - 'Cuando borras una rama después de fusionar una solicitud de cambios, se mostrará un mensaje de error aunque el borrado de la rama sea exitoso.' - - 'Cuando un nodo de réplica está sin conexión en una configuración de disponibilidad alta, es posible que {% data variables.product.product_name %} todavía enrute las solicitudes a {% data variables.product.prodname_pages %} al nodo sin conexión, lo que reduce la disponibilidad de {% data variables.product.prodname_pages %} para los usuarios.' - - 'Los límites de recursos que son específicos para procesar enlaces previos a la recepción podrían ocasionar errores en algunos de ellos.' diff --git a/translations/es-ES/data/release-notes/enterprise-server/3-0/5.yml b/translations/es-ES/data/release-notes/enterprise-server/3-0/5.yml deleted file mode 100644 index b27e6cdbd6..0000000000 --- a/translations/es-ES/data/release-notes/enterprise-server/3-0/5.yml +++ /dev/null @@ -1,28 +0,0 @@ -date: '2021-04-14' -intro: "Los requisitos mínimos de infraestructura han aumentado para {% data variables.product.prodname_ghe_server %} 3.0+. Para más información, consulta \"[Acerca de los requisitos mínimos para GitHub Enterprise Server 3.0 y versiones posteriores](/admin/enterprise-management/upgrading-github-enterprise-server#about-minimum-requirements-for-github-enterprise-server-30-and-later)\"" -sections: - security_fixes: - - Los paquetes se han actualizado a las versiones de seguridad más recientes. - bugs: - - Algunos registros no se incluyeron en la configuración de reenvío de registros. - - 'Un mensaje de advertencia "jq: error (en :0): No se puede indexar el número con la cadena "configuración"" podría aparecer durante la promoción de la réplica.' - - La restauración continua de copias de seguridad en un clúster podría dar error debido a que las réplicas de MySQL no se pueden conectar al principal. - - Las páginas no se publicaban cuando se usaba un certificado CA personalizado. - - "Los subdominios relacionados con los paquetes no aparecían en el mensaje \"Probar la configuración del dominio\" para el aislamiento del subdominio." - - "El encabezado \"X-GitHub-Enterprise-Host\" enviado con webhooks incluía una cadena aleatoria, en lugar del nombre de host de la instancia de GitHub Enterprise Server que envió la carga HTTP POST." - - "La actualización de 2.22.x a 3.0.x fallaría si Acciones de GitHub se hubiera habilitado previamente, pero se deshabilitó antes de la actualización." - - "Visitar la página \"/settings/emails\" almacenaría un estado que podría causar redireccionamientos inapropiados al cerrar sesión y volver a iniciar sesión." - - Las aplicaciones de integración de GitHub no pudieron notificar a los equipos cuando se mencionaron directamente a través de una @mención en un comentario de incidencia. - - "La representación de reStructuredText (RST) en la UI web daría error y, en su lugar, mostraría texto de marcado RST sin procesar." - - Las notificaciones por correo electrónico de las alertas de exploración de secretos no se enviaban a los usuarios autorizados cuando el gráfico de dependencia no estaba completamente habilitado. - - "Cuando ghe-migrator encontraba errores de importación, a veces anulaba todo el proceso y los registros no incluían suficiente contexto." - - Los cuadernos de Jupyter Notebook con caracteres que no son ASCII podrían dar error al representarse. - known_issues: - - "En una instancia de GitHub Enterprise Server recién configurada sin usuarios, un atacante podría crear el primer usuario administrador." - - Las reglas de firewall personalizadas no se mantienen durante una actualización. - - "Los archivos supervisados de Git LFS [cargados a través la interfaz web](https://github.com/blog/2105-upload-files-to-your-repositories) se agregaron incorrecta y directamente al repositorio." - - Las incidencias no se pueden cerrar si contienen un vínculo permanente a un blob en el mismo repositorio en el que la ruta de acceso de archivo tiene más de 255 caracteres. - - "Cuando se habilita \"Los usuarios pueden buscar en GitHub.com\" con GitHub Connect, las incidencias en los repositorios privados e internos no se incluyen en los resultados de la búsqueda de GitHub.com." - - "Cuando se elimina una rama después de fusionar una solicitud de cambios, se muestra un mensaje de error aunque la eliminación de la rama se realice correctamente." - - "Cuando un nodo de réplica está sin conexión en una configuración de alta disponibilidad, {% data variables.product.product_name %} aún se pueden enrutar solicitudes de {% data variables.product.prodname_pages %} al nodo sin conexión, lo que reduce la disponibilidad de {% data variables.product.prodname_pages %} para los usuarios." - - Los límites de recursos que son específicos para el procesamiento de enlaces previos a la recepción pueden provocar un error en algunos enlaces previos a la recepción. diff --git a/translations/es-ES/data/release-notes/enterprise-server/3-0/6.yml b/translations/es-ES/data/release-notes/enterprise-server/3-0/6.yml deleted file mode 100644 index ee963fe385..0000000000 --- a/translations/es-ES/data/release-notes/enterprise-server/3-0/6.yml +++ /dev/null @@ -1,31 +0,0 @@ -date: '2021-04-28' -sections: - security_fixes: - - 'Los paquetes se han actualizado a las últimas versiones de seguridad.' - bugs: - - 'Durante las actualizaciones, el proceso se pausaba de forma indefinida después de un "cleanup nomad job".' - - 'Error "ghe-cluster-failover" con el mensaje de error "Trilogy::Error: trilogy_connect".' - - '"ghe-cluster-status-mysql" mostraba advertencias sobre conmutaciones por error como errores.' - - 'El script de configuración que se ejecuta en la replica de MySQL puede haber causado un resembrado innecesario de la base de datos durante la conmutación por errores de la base de datos.' - - 'Las actualizaciones no incluían la última versión del ejecutor de Acciones instalado adecuadamente.' - - 'La configuración de "github-env" podía dar como resultado procesos zombie.' - - '"config-apply" podía tomar más tiempo del necesario debido a que llamaba a "rake db:migrate" innecesariamente.' - - 'Orchestrator podía no conmutarse por error a una réplica de MySQL que no se estaba replicando desde la principal durante la fase de inicialización cuando la principal no se podía conectar.' - - 'Las organizaciones o proyectos con errores bloqueaban la migración y no podían excluirse.' - - "El botón Crear repositorio se desactivaba para los usuarios que pertenecían a más de 50\_organizaciones." - - 'El borrado de una rama mostraba un mensaje de error temporal que indicaba que algo había salido mal cuando el borrado era exitoso.' - - 'El índice "rms-packages" se mostraba en el panel de información del administrador del sitio.' - - 'El propietario de la organización no podía crear un repositorio interno debido a que las opciones correctas de visibilidad no se mostraban en el formulario.' - - 'Las pestaña de acciones de los repositorios mostraban un error 500 en los casos en donde los flujos de trabajo iniciales de las acciones estaban mal configurados.' - - 'Los clientes con más de tres hosts de almacenamiento no podían restablecer su clúster de recuperación de desastres debido a que se seleccionaban los discos más llenos en vez de los nodos vacíos.' - - 'Los servicios de backend con el escaneo de código no se iniciaban confiablemente después de aplicar las revisiones en caliente.' - changes: - - 'Las verificaciones preliminares permiten todos los tipos de instancia de AWS de manera predeterminada.' - known_issues: - - 'En un servidor de GitHub Enterprise recién configurado sin usuarios, un atacante podría crear el primer usuario administrador.' - - 'Las reglas de firewall personalizadas no se mantienen durante una actualización.' - - 'Los archivos supervisados de Git LFS [cargados desde la interface web](https://github.com/blog/2105-upload-files-to-your-repositories) se han agregado de manera incorrecta y directa al repositorio.' - - "Las incidencias no se pueden cerrar si contienen un vínculo permanente a un blob en el mismo repositorio en el que la ruta de acceso de archivo del blob tiene más de 255\_caracteres." - - 'Cuando se habilita "Los usuarios pueden buscar en GitHub.com" con GitHub Connect, las incidencias en los repositorios privados e internos no se incluyen en los resultados de la búsqueda de GitHub.com.' - - 'Cuando un nodo de réplica está sin conexión en una configuración de disponibilidad alta, es posible que {% data variables.product.product_name %} todavía enrute las solicitudes a {% data variables.product.prodname_pages %} al nodo sin conexión, lo que reduce la disponibilidad de {% data variables.product.prodname_pages %} para los usuarios.' - - 'Los límites de recursos que son específicos para procesar enlaces previos a la recepción podrían ocasionar errores en algunos de ellos.' diff --git a/translations/es-ES/data/release-notes/enterprise-server/3-0/7.yml b/translations/es-ES/data/release-notes/enterprise-server/3-0/7.yml deleted file mode 100644 index 0aa1079a11..0000000000 --- a/translations/es-ES/data/release-notes/enterprise-server/3-0/7.yml +++ /dev/null @@ -1,24 +0,0 @@ -date: '2021-05-13' -sections: - security_fixes: - - "**ALTO RIESGO:** se identificó una vulnerabilidad de representación incorrecta en la IU en el servidor de GitHub Enterprise que permitía otorgar más permisos de los que se mostraban al usuario en la aprobación durante el flujo web de autorización de usuarios en una aplicación de GitHub. Para aprovechar esta vulnerabilidad, un atacante tendría que crear una aplicación de GitHub en la instancia y hacer que el usuario la autorice mediante el flujo de autenticación web. Todos los permisos que se otorgaran se mostrarían correctamente durante la primera autorización, pero en ciertas circunstancias, si el usuario volvía a visitar el flujo de autorización después de haber configurado los permisos de nivel de usuario en la aplicación de GitHub, los permisos adicionales podían no mostrarse, lo que causaba que el usuario otorgara más permisos de los previstos. Esta vulnerabilidad afectó a las versiones del servidor de GitHub Enterprise desde la\_3.0.x hasta la\_3.0.7 y la\_2.22.x hasta la\_2.22.13. Se corrigió en las versiones 3.0.7 y 2.22.13. Esta vulnerabilidad se ha asignado a CVE-2021-22866 y se ha notificado mediante [GitHub\_Bug Bounty Program](https://bounty.github.com/)." - - 'Los paquetes se han actualizado a las últimas versiones de seguridad.' - bugs: - - 'Las citas que se incluyen en la configuración del almacenamiento de paquetes o acciones podían causar errores.' - - 'Los enlaces previos a la recepción personalizados podrían fallar debido a la cantidad o tamaño de archivo muy restringido de los límites de archivo abiertos.' - - 'La conmutación por error automática de Orchestrator se puede habilitar durante la fase de aplicación de configuración.' - - 'A los usuarios con permiso de mantenedor en un repositorio se les mostraba una advertencia de verificación por correo electrónico en vez de una compilación de página correcta en la página de configuración de Pages del repositorio.' - - 'El propietario del código de una regla de comodín se agregaba incorrectamente a la lista de propietarios para la insignia de propietarios de código, incluso si una regla tardía prevalecía en dicha ruta.' - - 'La documentación de OpenAPI conducía a un encabezado inválido.' - - 'Al crear o editar enlaces previos a la recepción, una condición de carrera en la interfaz de usuario significaba que, después de seleccionar un repositorio, los archivos dentro de este a veces no se llenaban en el menú desplegable de los archivos.' - changes: - - 'Se agregó el registro para cambios de configuración en una recarga de HAProxy.' - - 'Se agregó el registro para la creación de repositorios.' - known_issues: - - 'En un servidor de GitHub Enterprise recién configurado sin usuarios, un atacante podría crear el primer usuario administrador.' - - 'Las reglas de firewall personalizadas no se mantienen durante una actualización.' - - 'Los archivos supervisados de Git LFS [cargados desde la interface web](https://github.com/blog/2105-upload-files-to-your-repositories) se han agregado de manera incorrecta y directa al repositorio.' - - "Las incidencias no se pueden cerrar si contienen un vínculo permanente a un blob en el mismo repositorio en el que la ruta de acceso de archivo del blob tiene más de 255\_caracteres." - - 'Cuando se habilita "Los usuarios pueden buscar en GitHub.com" con GitHub Connect, las incidencias en los repositorios privados e internos no se incluyen en los resultados de la búsqueda de GitHub.com.' - - 'Cuando un nodo de réplica está sin conexión en una configuración de disponibilidad alta, es posible que {% data variables.product.product_name %} todavía enrute las solicitudes a {% data variables.product.prodname_pages %} al nodo sin conexión, lo que reduce la disponibilidad de {% data variables.product.prodname_pages %} para los usuarios.' - - 'Los límites de recursos que son específicos para procesar enlaces previos a la recepción podrían ocasionar errores en algunos de ellos.' diff --git a/translations/es-ES/data/release-notes/enterprise-server/3-0/8.yml b/translations/es-ES/data/release-notes/enterprise-server/3-0/8.yml deleted file mode 100644 index a81b1c7752..0000000000 --- a/translations/es-ES/data/release-notes/enterprise-server/3-0/8.yml +++ /dev/null @@ -1,27 +0,0 @@ -date: '2021-05-25' -sections: - security_fixes: - - '**RIESGO MEDIO:** bajo ciertas circunstancias, los usuarios que se eliminaban de un equipo u organización podían retener el acceso de escritura a las ramas en las cuales tenían solicitudes de incorporación de cambios existentes abiertas.' - - 'Los paquetes se han actualizado a las últimas versiones de seguridad.' - bugs: - - 'En la página "Configurar acciones y paquetes" del proceso de instalación inicial, cuando un administrador hacía clic en el botón "Probar configuración de dominio", la prueba no se completaba.' - - 'La ejecución de "ghe-btop" producía un error "cannot find a ''babeld'' container".' - - 'Los usuarios experimentaban una falta de disponibilidad del servicio después de actualizar debido a un desajuste de valores de tiempo de espera internos y externos.' - - 'Los retrasos en la replicación normal en MSSQL generaban advertencias.' - - 'El enlace para la Guía de agrupación en clústeres de GitHub Enterprise sobre la consola de administración era incorrecto.' - - 'Una dirección IP agregada por un administrador mediante el botón "Crear entrada de lista de admisión" seguía pudiendo bloquearse.' - - 'Se mostraban referencias a las características "Gráfica de dependencias" y "Alertas del dependabot" en los repositorios en donde no se habían habilitado.' - - 'Las solicitudes de tipo HTTP POST al punto de conexión "/hooks" podían fallar con una respuesta 401 si la "hookID" se había configurado incorrectamente.' - - 'El proceso "build-server" producía un error a la hora de limpiar los procesos, dejándolos en estado "defunct".' - - '"spokesd" creaba entradas de registro excesivas, incluyendo la frase "fixing placement skipped".' - changes: - - "Se archivarán las anotaciones de verificación más viejas de 4\_meses." - known_issues: - - 'El acceso a un repositorio mediante el shell administrativo utilizando "ghe-repo /" se colgaba. Como solución, utiliza "`ghe-repo / -c "bash -i"`" hasta que haya disponible una solución en la siguiente versión.' - - 'En un servidor de GitHub Enterprise recién configurado sin usuarios, un atacante podría crear el primer usuario administrador.' - - 'Las reglas de firewall personalizadas no se mantienen durante una actualización.' - - 'Los archivos supervisados de Git LFS [cargados desde la interface web](https://github.com/blog/2105-upload-files-to-your-repositories) se han agregado de manera incorrecta y directa al repositorio.' - - "Las incidencias no se pueden cerrar si contienen un vínculo permanente a un blob en el mismo repositorio en el que la ruta de acceso de archivo del blob tiene más de 255\_caracteres." - - 'Cuando se habilita "Los usuarios pueden buscar en GitHub.com" con GitHub Connect, las incidencias en los repositorios privados e internos no se incluyen en los resultados de la búsqueda de GitHub.com.' - - 'Cuando un nodo de réplica está sin conexión en una configuración de disponibilidad alta, es posible que {% data variables.product.product_name %} todavía enrute las solicitudes a {% data variables.product.prodname_pages %} al nodo sin conexión, lo que reduce la disponibilidad de {% data variables.product.prodname_pages %} para los usuarios.' - - 'Los límites de recursos que son específicos para procesar enlaces previos a la recepción podrían ocasionar errores en algunos de ellos.' diff --git a/translations/es-ES/data/release-notes/enterprise-server/3-0/9.yml b/translations/es-ES/data/release-notes/enterprise-server/3-0/9.yml deleted file mode 100644 index 43355aab97..0000000000 --- a/translations/es-ES/data/release-notes/enterprise-server/3-0/9.yml +++ /dev/null @@ -1,24 +0,0 @@ -date: '2021-06-10' -sections: - security_fixes: - - 'Los paquetes se han actualizado a las últimas versiones de seguridad.' - bugs: - - 'El proceso de actualización podría fallar al actualizar las acciones si la instancia no pudo hacer auto-solicitudes utilizando el nombre de host configurado.' - - 'El SVN 1.7 y los clientes más antiguos mostraron un error cuando se utilizaron los comandos "svn co" y "svn export".' - - 'El acceso a un repositorio mediante el shell administrativo utilizando "ghe-repo /" provocaba bloqueos.' - - 'Después de la actualización, los usuarios experimentaron disponibilidad reducida durante el uso intensivo, porque los servicios se reiniciaron con demasiada frecuencia. Esto sucedería a causa del error de coincidencia de tiempo de expiración entre la configuración nómada y la de los servicios internos.' - - 'En algunas instancias, la ejecución de "ghe-repl-status" después de haber configurado las Acciones de GitHub produjo un error y "ghe-actions-teardown" falló.' - - '"ghe-dbconsole" devolvió errores en algunas circunstancias.' - - 'Los errores de importación de organizaciones o repositorios desde orígenes distintos a GitHub podrían producir un error de tipo "método sin definir "[]" para nil:NilClass".' - - 'Los nombres de perfil de GitHub podrían haber cambiado accidentalmente al utilizar la autenticación de SAML, si el nombre de perfil de GitHub no coincidió con el valor del atributo que se asignó en el campo "Full name" de la consola de administración.' - changes: - - 'El campo "firstPatchedVersion" ahora está disponible en los objetos de "SecurityVulnerability" en la API de GraphQL.' - - "Los usuarios de GraphQL\_API pueden consultar el campo público \"closingIssuesReferences\" en el objeto \"PullRequest\". Este campo recupera incidencias que se cerrarán de forma automática cuando se combine la solicitud de incorporación de cambios relacionada. Este enfoque también permitirá migrar estos datos en el futuro, como parte de un proceso de migración más fiel." - known_issues: - - 'En un servidor de GitHub Enterprise recién configurado sin usuarios, un atacante podría crear el primer usuario administrador.' - - 'Las reglas de cortafuegos personalizadas se eliminan durante el proceso de actualización.' - - 'Los archivos supervisados de Git LFS [cargados desde la interface web](https://github.com/blog/2105-upload-files-to-your-repositories) se han agregado de manera incorrecta y directa al repositorio.' - - "Las incidencias no se pueden cerrar si contienen un enlace permanente a un blob del mismo repositorio en el que la ruta es mayor de 255\_caracteres." - - 'Cuando se habilita "Los usuarios pueden buscar en GitHub.com" con GitHub Connect, las incidencias en los repositorios privados e internos no se incluyen en los resultados de la búsqueda de GitHub.com.' - - 'Cuando un nodo de réplica está sin conexión en una configuración de disponibilidad alta, es posible que {% data variables.product.product_name %} todavía enrute las solicitudes a {% data variables.product.prodname_pages %} al nodo sin conexión, lo que reduce la disponibilidad de {% data variables.product.prodname_pages %} para los usuarios.' - - 'Los límites de recursos que son específicos para procesar enlaces previos a la recepción podrían ocasionar errores en algunos de ellos.' diff --git a/translations/es-ES/data/release-notes/enterprise-server/3-1/0-rc1.yml b/translations/es-ES/data/release-notes/enterprise-server/3-1/0-rc1.yml deleted file mode 100644 index 520bfd612f..0000000000 --- a/translations/es-ES/data/release-notes/enterprise-server/3-1/0-rc1.yml +++ /dev/null @@ -1,20 +0,0 @@ -date: '2021-05-06' -release_candidate: true -deprecated: true -intro: If {% data variables.location.product_location %} is running a release candidate build, you can't upgrade with a hotpatch. We recommend only running release candidates on test environments. -sections: - 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: - - 'A scheduled cleanup job can cause performance to degrade on an instance with a very large `check_annotations` table.' - changes: - - Check annotations older than 4 months will be archived. - - 'The `firstPatchedVersion` field is now available on `SecurityVulnerability` objects in the GraphQL API.' - known_issues: - - The GitHub Packages 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 GitHub Enterprise 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. diff --git a/translations/es-ES/data/release-notes/enterprise-server/3-1/0.yml b/translations/es-ES/data/release-notes/enterprise-server/3-1/0.yml deleted file mode 100644 index 3b24968dd8..0000000000 --- a/translations/es-ES/data/release-notes/enterprise-server/3-1/0.yml +++ /dev/null @@ -1,173 +0,0 @@ -date: '2021-06-03' -intro: For minimum infrastructure requirements, see "[About minimum requirements for {% data variables.product.prodname_ghe_server %} 3.0 and later](/admin/enterprise-management/upgrading-github-enterprise-server#about-minimum-requirements-for-github-enterprise-server-30-and-later)." -sections: - features: - - heading: GitHub Advanced Security Secret Scanning - notes: - - | - [Secret Scanning](https://github.com/features/security) is now generally available on {% data variables.product.prodname_ghe_server %} 3.1+. Scan public and private repositories for committed credentials, find secrets, and notify the secret provider or admin the moment they are committed into a repository. - - This release includes several improvements from the beta of Secret Scanning on {% data variables.product.prodname_ghe_server %}: - - - Expanded our [pattern coverage](/enterprise-server@3.1/code-security/secret-security/about-secret-scanning#about-secret-scanning-for-private-repositories) from 24 partners to 37 - - Added an [API](/rest/reference/secret-scanning) and [webhooks](/developers/webhooks-and-events/webhook-events-and-payloads#secret_scanning_alert) - - Added [notifications for commit authors](https://github.blog/changelog/2021-03-05-secret-scanning-notifications-for-commit-authors-on-private-repositories/) when they commit secrets - - Updated the index view to made it easy to triage secrets in bulk - - Reduced the false positive rate on many patterns - - Administrators using {% data variables.product.prodname_GH_advanced_security %} can [enable and configure](/enterprise-server@3.1/admin/configuration/configuring-secret-scanning-for-your-appliance) {% data variables.product.prodname_GH_advanced_security %} secret scanning. You can review the [updated minimum requirements for your platform](/enterprise-server@3.1/admin/installation/setting-up-a-github-enterprise-server-instance) before you turn on {% data variables.product.prodname_GH_advanced_security %} secret scanning. - - - heading: GitHub Advanced Security billing improvements - notes: - - | - This release includes several improvements to {% data variables.product.prodname_GH_advanced_security %} billing in {% data variables.product.prodname_ghe_server %}: - - - {% data variables.product.prodname_GH_advanced_security %} customers can now view their active committer count and the remaining number of unused committer seats on their organization or enterprise account’s Billing page. If Advanced Security is purchased for an enterprise, administrators can also view the active committer seats which are being used by other organizations within their enterprise. For more information, see "[About GitHub Advanced Security licensing](/enterprise-server@3.1/admin/advanced-security/about-licensing-for-github-advanced-security)" and "[Viewing your GitHub Advanced Security usage](/enterprise-server@3.1/admin/advanced-security/viewing-your-github-advanced-security-usage)." - - GitHub Advanced Security customers can now view their active committer count for any Advanced Security enabled repositories on their organization or enterprise account's Billing page. These changes help billing administrators track their usage against how many committer licenses they purchased. For more information see "[Managing security and analysis settings for your organization](/enterprise-server@3.1/organizations/keeping-your-organization-secure/managing-security-and-analysis-settings-for-your-organization)." - - - heading: Dependabot improvements - notes: - - | - This release includes improvements to Dependabot alerts in {% data variables.product.prodname_ghe_server %}: - - - Users with Dependabot alerts enabled can see which of their repositories are impacted by a given vulnerability by navigating to its entry in the [GitHub Advisory Database](https://github.com/advisories). This feature is available in public beta. For more information, see "[Viewing and updating vulnerable dependencies in your repository](/enterprise-server@3.1/code-security/supply-chain-security/viewing-and-updating-vulnerable-dependencies-in-your-repository)." - - When a vulnerability is added to GitHub Advisory Database, you will no longer receive [email and web notifications](https://github.com/notifications) for Dependabot alerts on low and moderate severity vulnerabilities. These alerts are still accessible from the repository's Security tab. For more information, see "[Viewing and updating vulnerable dependencies in your repository](/enterprise-server@3.1/code-security/supply-chain-security/viewing-and-updating-vulnerable-dependencies-in-your-repository)." - - You can now give people instructions on how to responsibly report security vulnerabilities in your project by adding a `SECURITY.md` file to your repository's `root`, `docs`, or `.github` folder. When someone creates an issue in your repository, they will see a link to your project's security policy. For more information, see "[Adding a security policy to your repository](/enterprise-server@3.1/code-security/getting-started/adding-a-security-policy-to-your-repository)." - - - heading: GitHub Actions Workflow Visualization beta - notes: - - | - {% data variables.product.prodname_actions %} can now generate a visual graph of your workflow on every run. With workflow visualization, you can: - - View and understand complex workflows - - Track progress of workflows in real-time - - Troubleshoot runs quickly by easily accessing logs and jobs metadata - - Monitor progress of deployment jobs and easily access deployment targets - - For more information, see "[Using the visualization graph](/actions/managing-workflow-runs/using-the-visualization-graph)." - - - heading: OAuth 2.0 Device Authorization Grant - notes: - - | - [OAuth 2.0 Device Authorization Grant](https://github.com/login/device) allows any CLI client or developer tool to authenticate using a secondary system with a browser. - - Administrators using [OAuth Apps](/developers/apps/authorizing-oauth-apps#device-flow) and [GitHub Apps](/developers/apps/authorizing-oauth-apps#device-flow) can enable and configure OAuth 2.0 Device Authorization Flow, in addition to the existing Web Application Flow. You can review the [updated minimum requirements for your platform](/enterprise-server@3.1/admin/installation/setting-up-a-github-enterprise-server-instance) before you enable OAuth 2.0 Device Authorization Flow. - - - heading: Pull request auto-merge - notes: - - | - With auto-merge, pull requests can be set to merge automatically when all merge requirements have been satisfied. This saves users from needing to constantly check the state of their pull requests just to merge them. Auto-merge can be enabled by a user with permission to merge and on pull requests that have unsatisfied merge requirements. For more information, see "[Automatically merging a pull request](/enterprise-server@3.1/github/collaborating-with-issues-and-pull-requests/automatically-merging-a-pull-request)." - - - heading: Custom notifications - notes: - - | - You can customize the types of notifications you want to receive from individual repositories. For more information, see "[Configuring notifications](/enterprise-server@3.1/github/managing-subscriptions-and-notifications-on-github/configuring-notifications#configuring-your-watch-settings-for-an-individual-repository)." - - - heading: GitHub Mobile filtering - notes: - - | - [{% data variables.product.prodname_mobile %}](https://github.com/mobile) filtering allows you to search for and find issues, pull requests, and discussions from your device. New metadata for issues and pull request list items allow you to filter by assignees, checks status, review states, and comment counts. - - {% data variables.product.prodname_mobile %} beta is available for {% data variables.product.prodname_ghe_server %}. Sign in with our [Android](https://play.google.com/store/apps/details?id=com.github.android) and [iOS](https://apps.apple.com/app/github/id1477376905) apps to triage notifications and manage issues and pull requests on the go. Administrators can disable mobile support for their Enterprise using the management console or by running `ghe-config app.mobile.enabled false`. For more information, see "[GitHub Mobile](/get-started/using-github/github-mobile)." - - changes: - - heading: Administration Changes - notes: - - By precomputing checksums, the amount of time a repository is under the lock has reduced dramatically, allowing more write operations to succeed immediately and improving monorepo performance. - - The latest release of the CodeQL CLI supports uploading analysis results to GitHub. This makes it easier to run code analysis for customers who wish to use CI/CD systems other than {% data variables.product.prodname_actions %}. Previously, such users had to use the separate CodeQL runner, which will continue to be available. For more information, see "[About CodeQL code scanning in your CI system](/enterprise-server@3.1/code-security/secure-coding/about-codeql-code-scanning-in-your-ci-system)." - - '{% data variables.product.prodname_actions %} now supports skipping `push` and `pull_request` workflows by looking for some common keywords in your commit message.' - - Check annotations older than four months will be archived. - - Scaling of worker allocation for background tasks has been revised. We recommend validating that the new defaults are appropriate for your workload. Custom background worker overrides should be unset in most cases. [Updated 2022-03-18] - - - heading: Security Changes - notes: - - Following feedback, display of Code Scanning results on a pull request without submitting with a pull request ID will remain supported. For more information, see "[Configuring code scanning](/enterprise-server@3.1/code-security/secure-coding/configuring-code-scanning#scanning-pull-requests)" and "[Configuring CodeQL code scanning in your CI system](/enterprise-server@3.1/code-security/secure-coding/configuring-codeql-code-scanning-in-your-ci-system#scanning-pull-requests). - - SARIF upload support increased to a maximum of 5000 results per upload. - - - heading: Developer Changes - notes: - - You can specify multiple callback URLs while configuring a GitHub App. This can be used in services with multiple domains or subdomains. GitHub will always deny authorization if the callback URL from the request is not in the authorization callback URL list. - - The GitHub App file permission has been updated to allow an app developer to specify up to 10 files for read-only or read-write access that their app can request access to. - - CodeQL now supports more [libraries and frameworks](https://codeql.github.com/docs/codeql-overview/supported-languages-and-frameworks/) for a variety of 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),[Java](https://github.com/github/codeql/tree/main/java), [Go](https://github.com/github/codeql-go/tree/main)). The CodeQL engine can now detect more sources of untrusted user data, which improves the quality and depth of the code scanning alerts. For more information, see "[About CodeQL](https://codeql.github.com/docs/codeql-overview/about-codeql/)." - - When configuring a GitHub App, the authorization callback URL is a required field. Now, we allow the developer to specify multiple callback URLs. This can be used in services with multiple domains or subdomains. GitHub will always deny authorization if the callback URL from the request is not in the authorization callback URL list. - - Delete an entire directory of files, including subdirectories, from your web browser. For more information, see "[Deleting a file or directory](/enterprise-server@3.1/github/managing-files-in-a-repository/deleting-files-in-a-repository#deleting-a-directory)." - - 'Include multiple words after the `#` in an issue, discussion, or pull request comment to further narrow your search.' - - 'When you’re writing an issue, pull request, or discussion comment the list syntax for bullets, numbers, and tasks autocompletes after you press `return` or `enter`.' - - - 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).' diff --git a/translations/es-ES/data/release-notes/enterprise-server/3-1/1.yml b/translations/es-ES/data/release-notes/enterprise-server/3-1/1.yml deleted file mode 100644 index 81341e76c4..0000000000 --- a/translations/es-ES/data/release-notes/enterprise-server/3-1/1.yml +++ /dev/null @@ -1,30 +0,0 @@ -date: '2021-06-10' -sections: - security_fixes: - - Packages have been updated to the latest security versions. - bugs: - - SVN 1.7 and older clients showed an error when using the `svn co` and `svn export` commands. - - Accessing a repository through the administrative shell using `ghe-repo /` would hang. - - After upgrading, users experienced reduced availability during heavy usage, because services restarted too frequently. This would occur due to timeout mismatches between the nomad configuration and that of the internal services. - - In some instances, running `ghe-repl-status` after setting up GitHub Actions would produce an error and `ghe-actions-teardown` would fail. - - '`ghe-dbconsole` would return errors under some circumstances.' - - Import failures of organizations or repositories from non-GitHub sources could produce an `undefined method '[]' for nil:NilClass` error. - - GitHub profile names might have changed unintentionally when using SAML authentication, if the GitHub profile name did not match the value of the attribute mapped to the `Full name` field in the Management Console. - - Upgrading an instance that had previously ran a 2.13 release, but not a 2.14 release, resulted in a database migration error relating to the `AddRepositoryIdToCheckRuns` data transition. - changes: - - Users of the GraphQL API can query the public field `closingIssuesReferences` on the `PullRequest` object. This field retrieves issues that will be automatically closed when the related pull request is merged. This approach will also allow this data to be migrated in future, as part of a higher fidelity migration process. - known_issues: - - The {% data variables.product.prodname_registry %} npm registry no longer returns a time value in metadata responses. This was done to allow for substantial performance improvements. We continue to have all the data necessary to return a time value as part of the metadata response and will resume returning this value in the future once we have solved the existing performance issues. - - 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. - - | - 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. - - If {% data variables.product.prodname_actions %} is enabled for {% data variables.product.prodname_ghe_server %}, teardown of a replica node with `ghe-repl-teardown` will succeed, but may return `ERROR:Running migrations`. - - Resource limits that are specific to processing pre-receive hooks may cause some pre-receive hooks to fail. diff --git a/translations/es-ES/data/release-notes/enterprise-server/3-1/10.yml b/translations/es-ES/data/release-notes/enterprise-server/3-1/10.yml deleted file mode 100644 index bc9286147d..0000000000 --- a/translations/es-ES/data/release-notes/enterprise-server/3-1/10.yml +++ /dev/null @@ -1,21 +0,0 @@ -date: '2021-10-28' -sections: - security_fixes: - - 'Era posible que las contraseñas de texto claro terminaran en algunos archivos de registro.' - - 'Se han añadido a la lista de denegaciones diversas claves públicas SSH que se sabe que son débiles y ya no se pueden registrar. Además, las versiones de GitKraken conocidas por generar claves de SSH débiles (7.6.x, 7.7.x y 8.0.0) tienen bloqueada la función de registro de nuevas claves públicas.' - - 'Los paquetes se han actualizado a las últimas versiones de seguridad.' - bugs: - - 'El restablecimiento podía fallar para el servidor empresarial en modo de asignación de clústeres si el orquestador no estaba en buen estado.' - - 'Los usuarios que eran propietarios de muchas organizaciones no podían utilizar varias partes de la aplicación.' - - 'Se corrigió un enlace a https://docs.github.com.' - changes: - - 'Optimizaciones de navegación y rendimiento de trabajos para los repositorios con muchas referencias.' - known_issues: - - 'El registro npm de {% data variables.product.prodname_registry %} ya no devuelve un valor de hora en las respuestas de metadatos. Esto se hacía para permitir mejoras de rendimiento importantes. Seguimos teniendo todos los datos necesarios para devolver un valor de tiempo como parte de la respuesta de metadatos y reanudaremos la devolución de este valor en el futuro una vez que hayamos resuelto las incidencias de rendimiento existentes.' - - 'En una instalación nueva de {% data variables.product.prodname_ghe_server %} que no tenga ningún usuario, cualquier atacante podría crear el primer usuario administrativo.' - - 'Las reglas de cortafuegos personalizadas se eliminan durante el proceso de actualización.' - - 'Los archivos supervisados de Git LFS [cargados desde la interface web](https://github.com/blog/2105-upload-files-to-your-repositories) se han agregado de manera incorrecta y directa al repositorio.' - - "Las incidencias no se pueden cerrar si contienen un enlace permanente a un blob del mismo repositorio en el que la ruta es mayor de 255\_caracteres." - - 'Cuando se habilita "Los usuarios pueden buscar en GitHub.com" con GitHub Connect, las incidencias en los repositorios privados e internos no se incluyen en los resultados de la búsqueda de GitHub.com.' - - 'Si se habilitan las {% data variables.product.prodname_actions %} para {% data variables.product.prodname_ghe_server %}, desmontar un nodo de réplica con "ghe-repl-teardown" tendrá éxito, pero podría devolver un "ERROR:Running migrations".' - - 'Los límites de recursos que son específicos para procesar enlaces previos a la recepción podrían ocasionar errores en algunos de ellos.' diff --git a/translations/es-ES/data/release-notes/enterprise-server/3-1/11.yml b/translations/es-ES/data/release-notes/enterprise-server/3-1/11.yml deleted file mode 100644 index 724c3efc7c..0000000000 --- a/translations/es-ES/data/release-notes/enterprise-server/3-1/11.yml +++ /dev/null @@ -1,28 +0,0 @@ -date: '2021-11-09' -sections: - security_fixes: - - A path traversal vulnerability was identified in {% data variables.product.prodname_pages %} builds on {% data variables.product.prodname_ghe_server %} that could allow an attacker to read system files. To exploit this vulnerability, an attacker needed permission to create and build a {% data variables.product.prodname_pages %} site on the {% data variables.product.prodname_ghe_server %} instance. This vulnerability affected all versions of {% data variables.product.prodname_ghe_server %} prior to 3.3, and was fixed in versions 3.0.19, 3.1.11, and 3.2.3. This vulnerability was reported through the {% data variables.product.company_short %} Bug Bounty program and has been assigned CVE-2021-22870. - - Packages have been updated to the latest security versions. - bugs: - - Some Git operations failed after upgrading a {% data variables.product.prodname_ghe_server %} 3.x cluster because of the HAProxy configuration. - - Unicorn worker counts might have been set incorrectly in clustering mode. - - Resqued worker counts might have been set incorrectly in clustering mode. - - If Ubuntu's Uncomplicated Firewall (UFW) status was inactive, a client could not clearly see it in the logs. - - Upgrading from {% data variables.product.prodname_ghe_server %} 2.x to 3.x failed when there were UTF8 characters in an LDAP configuration. - - Some pages and Git-related background jobs might not run in cluster mode with certain cluster configurations. - - When a new tag was created, the [push](/developers/webhooks-and-events/webhooks/webhook-events-and-payloads#push) webhook payload did not display a correct `head_commit` object. Now, when a new tag is created, the 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. - - The enterprise audit log page would not display audit events for {% data variables.product.prodname_secret_scanning %}. - - There was an insufficient job timeout for replica repairs. - - 'Users were not warned about potentially dangerous bidirectional unicode characters when viewing files. For more information, see "[Warning about bidirectional Unicode text](https://github.co/hiddenchars)" in {% data variables.product.prodname_blog %}.' - - Hookshot Go sent distribution type metrics that Collectd could not handle, which caused a ballooning of parsing errors. - changes: - - Kafka configuration improvements have been added. When deleting repositories, package files are now immediately deleted from storage account to free up space. `DestroyDeletedPackageVersionsJob` now deletes package files from storage account for stale packages along with metadata records. - known_issues: - - The {% data variables.product.prodname_registry %} npm registry no longer returns a time value in metadata responses. This was done to allow for substantial performance improvements. We continue to have all the data necessary to return a time value as part of the metadata response and will resume returning this value in the future once we have solved the existing performance issues. - - 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. - - If {% data variables.product.prodname_actions %} is enabled for {% data variables.product.prodname_ghe_server %}, teardown of a replica node with `ghe-repl-teardown` will succeed, but may return `ERROR:Running migrations`. - - Resource limits that are specific to processing pre-receive hooks may cause some pre-receive hooks to fail. diff --git a/translations/es-ES/data/release-notes/enterprise-server/3-1/12.yml b/translations/es-ES/data/release-notes/enterprise-server/3-1/12.yml deleted file mode 100644 index 0ecb3822e8..0000000000 --- a/translations/es-ES/data/release-notes/enterprise-server/3-1/12.yml +++ /dev/null @@ -1,24 +0,0 @@ -date: '2021-11-23' -sections: - security_fixes: - - 'Los paquetes se han actualizado a las últimas versiones de seguridad.' - bugs: - - 'La ejecución de "ghe-repl-start" o "ghe-repl-status" algunas veces devolvió errores para conectarse a la base de datos cuando se habilitó Acciones de GitHub.' - - 'Los enlaces previos a la recepción fallaron debido a un "PATH" sin definir.' - - 'La ejecución de "ghe-repl-setup" devolvió un error de tipo: "cannot create directory /data/user/elasticsearch: File exists" si la instancia se había configurado anteriormente como una réplica.' - - 'Después de configurar una réplica de disponibilidad alta, "ghe-repl-status" incluyó un error en la salida: "unexpected unclosed action in command".' - - 'En ambientes de clúster grandes, el backend de autenticación podría no estar disponible en un subconjunto de nodos de frontend.' - - 'Algunos servicios críticos pudieron no haber estado disponibles en los nodos del backend en el clúster de GHES.' - changes: - - 'Una capa exterior adicional de compresión de "gzip" al crear un conjunto de soporte de clústeres con "ghe-cluster-suport-bundle" ahora está desactivado de manera predeterminada. Esta compresión exterior puede aplicarse opcionalmente con la opción de la línea de comandos "ghe-cluster-suport-bundle -c".' - - 'Agregamos texto extra a la consola de administración para recordarles a los usuarios sobre la recolección de datos de las apps móviles para propósitos de mejora de la experiencia.' - - 'El registro de conexión de datos de {% data variables.product.prodname_github_connect %} ahora incluye una lista de características de {% data variables.product.prodname_github_connect %} habilitadas. [Actualizado el 2021-12-09]' - known_issues: - - 'El registro npm de {% data variables.product.prodname_registry %} ya no devuelve un valor de hora en las respuestas de metadatos. Esto se hacía para permitir mejoras de rendimiento importantes. Seguimos teniendo todos los datos necesarios para devolver un valor de tiempo como parte de la respuesta de metadatos y reanudaremos la devolución de este valor en el futuro una vez que hayamos resuelto las incidencias de rendimiento existentes.' - - 'En una instalación nueva de {% data variables.product.prodname_ghe_server %} que no tenga ningún usuario, cualquier atacante podría crear el primer usuario administrativo.' - - 'Las reglas de cortafuegos personalizadas se eliminan durante el proceso de actualización.' - - 'Los archivos supervisados de Git LFS [cargados desde la interface web](https://github.com/blog/2105-upload-files-to-your-repositories) se han agregado de manera incorrecta y directa al repositorio.' - - "Las incidencias no se pueden cerrar si contienen un enlace permanente a un blob del mismo repositorio en el que la ruta es mayor de 255\_caracteres." - - 'Cuando se habilita "Los usuarios pueden buscar en GitHub.com" con GitHub Connect, las incidencias en los repositorios privados e internos no se incluyen en los resultados de la búsqueda de GitHub.com.' - - 'Si se habilitan las {% data variables.product.prodname_actions %} para {% data variables.product.prodname_ghe_server %}, desmontar un nodo de réplica con "ghe-repl-teardown" tendrá éxito, pero podría devolver un "ERROR:Running migrations".' - - 'Los límites de recursos que son específicos para procesar enlaces previos a la recepción podrían ocasionar errores en algunos de ellos.' diff --git a/translations/es-ES/data/release-notes/enterprise-server/3-1/13.yml b/translations/es-ES/data/release-notes/enterprise-server/3-1/13.yml deleted file mode 100644 index 98cb383d7c..0000000000 --- a/translations/es-ES/data/release-notes/enterprise-server/3-1/13.yml +++ /dev/null @@ -1,23 +0,0 @@ -date: '2021-12-07' -sections: - security_fixes: - - 'Los paquetes de soporte podrían incluir archivos sensibles si cumplen con un conjunto de características específicas.' - - "Se identificó una vulnerabilidad de representación incorrecta en la IU en el servidor de GitHub Enterprise que permitía otorgar más permisos de los que se mostraban al usuario en la aprobación durante el flujo web de autorización de usuarios en una GitHub App. Esta vulnerabilidad afectaba a todas las versiones de GitHub\_Enterprise Server anteriores a la\_3.3 y se ha corregido en las versiones\_3.2.5, 3.1.13 y 3.0.21. Esta vulnerabilidad se notificó mediante el programa de recompensas de GitHub por la detección de errores y se le ha asignado [CVE-2021-41598](https://www.cve.org/CVERecord?id=CVE-2021-41598)." - - "Se identificó una vulnerabilidad de ejecución de código remoto en el servidor de GitHub Enterprise que podría aprovecharse al crear un sitio de GitHub Pages. Esta vulnerabilidad afectaba a todas las versiones de GitHub\_Enterprise Server anteriores a la\_3.3 y se ha corregido en las versiones\_3.0.21, 3.1.13 y 3.2.5. Esta vulnerabilidad se notificó mediante el programa de recompensas de GitHub por la detección de errores y se le ha asignado [CVE-2021-41599](https://www.cve.org/CVERecord?id=CVE-2021-41599). Actualizado el 17 de febrero de 2022." - bugs: - - 'La ejecución de "ghe-config-apply" en ocasiones podía producir errores debido a problemas con los permisos en "/data/user/tmp/pages".' - - 'Una mala configuración en la consola de administración causó errores de programación.' - - 'Docker retenía los archivos de registro abiertos después de una rotación de registros.' - - 'Las solicitudes de GraphQL no configuraban la variable GITHUB_USER_IP en los entornos de enlaces previos a la recepción.' - changes: - - 'Clarifica una explicación del estilo de ruta de Acciones en la documentación.' - - 'Actualiza las direcciones URL de contacto de soporte técnico para utilizar el sitio de soporte técnico actual, support.github.com.' - known_issues: - - 'El registro npm de {% data variables.product.prodname_registry %} ya no devuelve un valor de tiempo en las respuestas de metadatos. Esto se hacía para permitir mejoras de rendimiento importantes. Seguimos teniendo todos los datos necesarios para devolver un valor de tiempo como parte de la respuesta de metadatos y reanudaremos la devolución de este valor en el futuro una vez que hayamos resuelto las incidencias de rendimiento existentes.' - - 'En una instalación nueva de {% data variables.product.prodname_ghe_server %} que no tenga ningún usuario, un atacante podría crear el primer usuario administrador.' - - 'Las reglas de cortafuegos personalizadas se eliminan durante el proceso de actualización.' - - 'Los archivos supervisados de Git LFS [cargados desde la interfaz web](https://github.com/blog/2105-upload-files-to-your-repositories) se agregan de manera incorrecta y directa al repositorio.' - - "Las incidencias no se pueden cerrar si contienen un enlace permanente a un blob del mismo repositorio en el que la ruta es mayor de 255\_caracteres." - - 'Cuando se habilita "Los usuarios pueden buscar en GitHub.com" con GitHub Connect, las incidencias en los repositorios privados e internos no se incluyen en los resultados de la búsqueda de GitHub.com.' - - 'Si se habilitan las {% data variables.product.prodname_actions %} para {% data variables.product.prodname_ghe_server %}, desmontar un nodo de réplica con "ghe-repl-teardown" tendrá éxito, pero podría devolver un "ERROR:Running migrations".' - - 'Los límites de recursos que son específicos para procesar enlaces previos a la recepción podrían ocasionar errores en algunos de ellos.' diff --git a/translations/es-ES/data/release-notes/enterprise-server/3-1/14.yml b/translations/es-ES/data/release-notes/enterprise-server/3-1/14.yml deleted file mode 100644 index 66bc224dda..0000000000 --- a/translations/es-ES/data/release-notes/enterprise-server/3-1/14.yml +++ /dev/null @@ -1,14 +0,0 @@ -date: '2021-12-13' -sections: - security_fixes: - - '{% octicon "alert" aria-label="The alert icon" %} **RIESGO CRÍTICO:** una vulnerabilidad de ejecución de código remoto en la biblioteca Log4j, identificada como [CVE-2021-44228](https://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2021-44228), afectaba a todas las versiones de {% data variables.product.prodname_ghe_server %} anteriores a 3.3.1. La biblioteca Log4j se utiliza en un servicio de código abierto que se ejecuta en instancias {% data variables.product.prodname_ghe_server %}. Esta vulnerabilidad se corrigió en las versiones 3.0.22, 3.1.14, 3.2.6 y 3.3.1 de {% data variables.product.prodname_ghe_server %}. Para obtener más información, consulta [esta publicación](https://github.blog/2021-12-13-githubs-response-to-log4j-vulnerability-cve-2021-44228/) en el blog de GitHub.' - - '**Actualización del 17 de diciembre de 2021**: las correcciones de esta versión también solucionan [CVE-2021-45046](https://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2021-45046), que también se publicó después de esta versión. No se requiere ninguna actualización adicional de {% data variables.product.prodname_ghe_server %} para mitigar CVE-2021-44228 y CVE-2021-45046.' - known_issues: - - "El registro npm de {% data variables.product.prodname_registry %} ya no devuelve un valor de hora en las respuestas de metadatos. Esto se hacía para permitir mejoras de rendimiento importantes. Seguimos teniendo todos los datos necesarios para devolver un valor de tiempo como parte de la respuesta de metadatos y reanudaremos la devolución de este valor en el futuro una vez que hayamos resuelto las incidencias de rendimiento existentes." - - "En una instalación nueva de {% data variables.product.prodname_ghe_server %} que no tenga ningún usuario, cualquier atacante podría crear el primer usuario administrativo." - - Las reglas de cortafuegos personalizadas se eliminan durante el proceso de actualización. - - "Los archivos supervisados de Git LFS [cargados desde la interface web](https://github.com/blog/2105-upload-files-to-your-repositories) se han agregado de manera incorrecta y directa al repositorio." - - Las incidencias no se pueden cerrar si contienen un enlace permanente a un blob del mismo repositorio en el que la ruta es mayor de 255 caracteres. - - "Cuando se habilita \"Los usuarios pueden buscar en GitHub.com\" con GitHub Connect, las incidencias en los repositorios privados e internos no se incluyen en los resultados de la búsqueda de GitHub.com." - - "Si se habilitan las {% data variables.product.prodname_actions %} para {% data variables.product.prodname_ghe_server %}, desmontar un nodo de réplica con \"ghe-repl-teardown\" tendrá éxito, pero podría devolver un \"ERROR:Running migrations\"." - - Los límites de recursos que son específicos para procesar enlaces previos a la recepción podrían ocasionar errores en algunos de ellos. diff --git a/translations/es-ES/data/release-notes/enterprise-server/3-1/15.yml b/translations/es-ES/data/release-notes/enterprise-server/3-1/15.yml deleted file mode 100644 index 1f47c2db85..0000000000 --- a/translations/es-ES/data/release-notes/enterprise-server/3-1/15.yml +++ /dev/null @@ -1,21 +0,0 @@ -date: '2022-01-18' -sections: - security_fixes: - - "Los paquetes se han actualizado a las últimas versiones de seguridad. En estas actualizaciones, Log4j se ha actualizado a la versión 2.17.1. Nota: las mitigaciones anteriores publicadas en\_3.3.1, 3.2.6, 3.1.14, y 3.0.22 son suficientes para abordar el impacto de CVE-2021-44228, CVE-2021-45046, CVE-2021-45105 y CVE-2021-44832 en estas versiones del servidor de GitHub Enterprise." - - 'Sanitizar más secretos en los paquetes de soporte generados' - - 'Los paquetes se han actualizado a las últimas versiones de seguridad.' - bugs: - - 'La ejecución "ghe-config-apply" pudo fallar en ocasiones debido a problemas con los permisos en "/data/user/tmp/pages".' - - 'El botón de guardar en la consola de almacenamiento no se pudo alcanzar desplazándose en navegadores de menor resolución.' - - 'Las gráficas de monitoreo de tráfico de almacenamiento e IOPS no se actualizaron después de la actualización de la versión de collectd.' - - 'Algunos trabajos relacionados con webhooks pudieron haber generado una gran cantidad de registros.' - - 'Los permisos de repositorio para el usuario que devolvió la API de "/repos" no devolvieron la lista completa.' - known_issues: - - 'El registro npm de {% data variables.product.prodname_registry %} ya no devuelve un valor de hora en las respuestas de metadatos. Esto se hacía para permitir mejoras de rendimiento importantes. Seguimos teniendo todos los datos necesarios para devolver un valor de tiempo como parte de la respuesta de metadatos y reanudaremos la devolución de este valor en el futuro una vez que hayamos resuelto las incidencias de rendimiento existentes.' - - 'En una instalación nueva de {% data variables.product.prodname_ghe_server %} que no tenga ningún usuario, cualquier atacante podría crear el primer usuario administrativo.' - - 'Las reglas de cortafuegos personalizadas se eliminan durante el proceso de actualización.' - - 'Los archivos supervisados de Git LFS [cargados desde la interface web](https://github.com/blog/2105-upload-files-to-your-repositories) se han agregado de manera incorrecta y directa al repositorio.' - - "Las incidencias no se pueden cerrar si contienen un enlace permanente a un blob del mismo repositorio en el que la ruta es mayor de 255\_caracteres." - - 'Cuando se habilita "Los usuarios pueden buscar en GitHub.com" con GitHub Connect, las incidencias en los repositorios privados e internos no se incluyen en los resultados de la búsqueda de GitHub.com.' - - 'Si se habilitan las {% data variables.product.prodname_actions %} para {% data variables.product.prodname_ghe_server %}, desmontar un nodo de réplica con "ghe-repl-teardown" tendrá éxito, pero podría devolver un "ERROR:Running migrations".' - - 'Los límites de recursos que son específicos para procesar enlaces previos a la recepción podrían ocasionar errores en algunos de ellos.' diff --git a/translations/es-ES/data/release-notes/enterprise-server/3-1/16.yml b/translations/es-ES/data/release-notes/enterprise-server/3-1/16.yml deleted file mode 100644 index 0c326f9823..0000000000 --- a/translations/es-ES/data/release-notes/enterprise-server/3-1/16.yml +++ /dev/null @@ -1,24 +0,0 @@ -date: '2022-02-01' -sections: - security_fixes: - - 'Los paquetes se han actualizado a las últimas versiones de seguridad.' - bugs: - - 'Las páginas no estaban disponibles después de una rotación de secretos de MySQL hasta que "nginx" se restablecía manualmente.' - - 'Al configurar la programación de mantenimiento con una fecha ISO 8601, el tiempo programado real no coincidía debido a que la zona horaria no se transformaba a UTC.' - - 'Los mensajes de errores espurios relacionados con "cloud-config.service" se generaban en la consola.' - - 'El número de versión no se actualizaba correctamente después de instalar una revisión en caliente utilizando "ghe-cluster-each".' - - 'Los trabajos de limpieza de tabla de webhook pueden ejecutarse simultáneamente ocasionando contención de recursos e incrementando el tiempo de ejecución del job.' - - 'Al utilizar la autenticación CAS y activar la opción "Reactivar usuarios suspendidos", dichos usuarios no se reactivaban automáticamente.' - - 'La capacidad de limitar las notificaciones basadas en correos electrónicos para los usuarios con correos electrónicos en un dominio aprobado o verificado no funcionaba correctamente.' - - 'Varios enlaces de documentación daban como resultado un error de tipo "404 Not Found".' - changes: - - 'El registro de conexión de datos de GitHub Connect ahora incluye un recuento de la cantidad de usuarios activos e inactivos y el periodo de inactividad configurado.' - known_issues: - - 'El registro npm de {% data variables.product.prodname_registry %} ya no devuelve un valor de hora en las respuestas de metadatos. Esto se hacía para permitir mejoras de rendimiento importantes. Seguimos teniendo todos los datos necesarios para devolver un valor de tiempo como parte de la respuesta de metadatos y reanudaremos la devolución de este valor en el futuro una vez que hayamos resuelto las incidencias de rendimiento existentes.' - - 'En una instalación nueva de {% data variables.product.prodname_ghe_server %} que no tenga ningún usuario, cualquier atacante podría crear el primer usuario administrativo.' - - 'Las reglas de cortafuegos personalizadas se eliminan durante el proceso de actualización.' - - 'Los archivos supervisados de Git LFS [cargados desde la interface web](https://github.com/blog/2105-upload-files-to-your-repositories) se han agregado de manera incorrecta y directa al repositorio.' - - "Las incidencias no se pueden cerrar si contienen un enlace permanente a un blob del mismo repositorio en el que la ruta es mayor de 255\_caracteres." - - 'Cuando se habilita "Los usuarios pueden buscar en GitHub.com" con GitHub Connect, las incidencias en los repositorios privados e internos no se incluyen en los resultados de la búsqueda de GitHub.com.' - - 'Si se habilitan las {% data variables.product.prodname_actions %} para {% data variables.product.prodname_ghe_server %}, desmontar un nodo de réplica con "ghe-repl-teardown" tendrá éxito, pero podría devolver un "ERROR:Running migrations".' - - 'Los límites de recursos que son específicos para procesar enlaces previos a la recepción podrían ocasionar errores en algunos de ellos.' diff --git a/translations/es-ES/data/release-notes/enterprise-server/3-1/17.yml b/translations/es-ES/data/release-notes/enterprise-server/3-1/17.yml deleted file mode 100644 index cbbd6d7aae..0000000000 --- a/translations/es-ES/data/release-notes/enterprise-server/3-1/17.yml +++ /dev/null @@ -1,15 +0,0 @@ -date: '2022-02-17' -sections: - security_fixes: - - 'Los paquetes se han actualizado a las últimas versiones de seguridad.' - bugs: - - 'Corrige SystemStackError (se apilaron demasiado profundamente) al obtener más de 2^16 llaves del memcached.' - known_issues: - - 'El registro npm de {% data variables.product.prodname_registry %} ya no devuelve un valor de hora en las respuestas de metadatos. Esto se hacía para permitir mejoras de rendimiento importantes. Seguimos teniendo todos los datos necesarios para devolver un valor de tiempo como parte de la respuesta de metadatos y reanudaremos la devolución de este valor en el futuro una vez que hayamos resuelto las incidencias de rendimiento existentes.' - - 'En una instancia recién configurada de {% data variables.product.prodname_ghe_server %} sin ningún usuario, un atacante podría crear el primer usuario administrador.' - - 'Las reglas de cortafuegos personalizadas se eliminan durante el proceso de actualización.' - - 'Los archivos supervisados de Git LFS [cargados desde la interface web](https://github.com/blog/2105-upload-files-to-your-repositories) se han agregado de manera incorrecta y directa al repositorio.' - - "Las incidencias no se pueden cerrar si contienen un enlace permanente a un blob del mismo repositorio en el que la ruta es mayor de 255\_caracteres." - - 'Cuando se habilita "Los usuarios pueden buscar en GitHub.com" con GitHub Connect, las incidencias en los repositorios privados e internos no se incluyen en los resultados de la búsqueda de GitHub.com.' - - 'Si se habilitan las {% data variables.product.prodname_actions %} para {% data variables.product.prodname_ghe_server %}, desmontar un nodo de réplica con "ghe-repl-teardown" tendrá éxito, pero podría devolver un "ERROR:Running migrations".' - - 'Los límites de recursos que son específicos para procesar enlaces previos a la recepción podrían ocasionar errores en algunos de ellos.' diff --git a/translations/es-ES/data/release-notes/enterprise-server/3-1/18.yml b/translations/es-ES/data/release-notes/enterprise-server/3-1/18.yml deleted file mode 100644 index 4e2c2eedfd..0000000000 --- a/translations/es-ES/data/release-notes/enterprise-server/3-1/18.yml +++ /dev/null @@ -1,16 +0,0 @@ -date: '2022-03-01' -sections: - security_fixes: - - 'RIESGO ALTO: se identificó una vulnerabilidad de desbordamiento de entero en el analizador de Markdown de GitHub que potencialmente podía causar filtraciones de información y RCE. Felix Wilhelm de Project Zero de Google informó de esta vulnerabilidad mediante el programa Bug Bounty de GitHub y se le asignó CVE-2022-24724.' - bugs: - - 'A veces, las actualizaciones podían producir errores si un reloj de réplica de alta disponibilidad no estaba sincronizado con el principal.' - - 'Las aplicaciones de OAuth creadas después del 1 de septiembre de 2020 no podían usar el punto de conexión de la API [Comprobación de una autorización](https://docs.github.com/en/enterprise-server@3.1/rest/reference/apps#check-an-authorization).' - known_issues: - - 'El registro npm de {% data variables.product.prodname_registry %} ya no devuelve un valor de hora en las respuestas de metadatos. Esto se hacía para permitir mejoras de rendimiento importantes. Seguimos teniendo todos los datos necesarios para devolver un valor de tiempo como parte de la respuesta de metadatos y reanudaremos la devolución de este valor en el futuro una vez que hayamos resuelto las incidencias de rendimiento existentes.' - - 'En una instancia recién configurada de {% data variables.product.prodname_ghe_server %} sin ningún usuario, un atacante podría crear el primer usuario administrador.' - - 'Las reglas de cortafuegos personalizadas se eliminan durante el proceso de actualización.' - - 'Los archivos supervisados de Git LFS [cargados desde la interface web](https://github.com/blog/2105-upload-files-to-your-repositories) se han agregado de manera incorrecta y directa al repositorio.' - - "Las incidencias no se pueden cerrar si contienen un enlace permanente a un blob del mismo repositorio en el que la ruta es mayor de 255\_caracteres." - - 'Cuando se habilita "Los usuarios pueden buscar en GitHub.com" con GitHub Connect, las incidencias en los repositorios privados e internos no se incluyen en los resultados de la búsqueda de GitHub.com.' - - 'Si se habilitan las {% data variables.product.prodname_actions %} para {% data variables.product.prodname_ghe_server %}, desmontar un nodo de réplica con "ghe-repl-teardown" tendrá éxito, pero podría devolver un "ERROR:Running migrations".' - - 'Los límites de recursos que son específicos para procesar enlaces previos a la recepción podrían ocasionar errores en algunos de ellos.' diff --git a/translations/es-ES/data/release-notes/enterprise-server/3-1/19.yml b/translations/es-ES/data/release-notes/enterprise-server/3-1/19.yml deleted file mode 100644 index e02034ac76..0000000000 --- a/translations/es-ES/data/release-notes/enterprise-server/3-1/19.yml +++ /dev/null @@ -1,41 +0,0 @@ -date: '2022-04-04' -sections: - security_fixes: - - "RIESGO MEDIO: se ha identificado una vulnerabilidad de salto de directorio en la consola de administración de {% data variables.product.prodname_ghe_server %} que permitía la omisión de las protecciones contra CSRF. Esta vulnerabilidad afectó a todas las versiones de {% data variables.product.prodname_ghe_server %} anteriores a la\_3.5 y se corrigió en las versiones\_3.1.19, 3.2.11, 3.3.6 y 3.4.1. Esta vulnerabilidad se notificó mediante el programa de recompensas de {% data variables.product.prodname_dotcom %} por la detección de errores y se le ha asignado CVE-2022-23732." - - 'RIESGO MEDIO: se ha identificado una vulnerabilidad de desbordamiento de enteros en la rama 1.x y la rama 2.x de "yajil" que posteriormente provoca daños en la memoria de montón al tratar con entradas grandes (~2GB). Esta vulnerabilidad se notificó de forma interna y se le ha asignado CVE-2022-24795. ' - - 'Los conjuntos de soporte técnico podrían incluir archivos confidenciales si {% data variables.product.prodname_actions %} estuviera habilitada.' - - 'Los paquetes se han actualizado a las últimas versiones de seguridad.' - bugs: - - 'Se mostraron las opciones para habilitar "TLS 1.0" y "TLS 1.1" en la configuración de privacidad de la consola de administración, aunque la eliminación de esas versiones de protocolo se produjo en una versión anterior.' - - 'En un entorno de alta disponibilidad, configurar la replicación de MSSQL podría requerir pasos manuales adicionales tras habilitar {% data variables.product.prodname_actions %} por primera vez.' - - 'Un subconjunto de archivos de configuración interna se actualizan de forma más confiable tras una revisión en caliente.' - - 'Habría ocasiones en las que el script "ghe-run-migrations" no generaría nombres de certificados temporales correctamente.' - - 'En un entorno de clúster, podría producirse un error en las operaciones de Git LFS con llamadas API internas fallidas que cruzaran varios nodos web.' - - 'Se agotó el tiempo de espera de los enlaces de recepción previa que usaron "gpg --import" debido a la insuficiencia de privilegios "syscall".' - - 'En algunas topologías de clúster, la información de entrega de webhook no estaba disponible.' - - 'En las configuraciones de alta disponibilidad, no se anularía ninguna réplica si {% data variables.product.prodname_actions %} se hubiera habilitado anteriormente.' - - 'Las comprobaciones de estado de Elasticsearch no permitirían un estado del clúster amarillo al ejecutar migraciones.' - - 'Las organizaciones creadas como resultado de un usuario que transforma su cuenta de usuario en una organización no se agregaron a la cuenta empresarial global.' - - 'Al usar "ghe-migrator" o exportar desde {% data variables.product.prodname_dotcom_the_website %}, se produciría un error en una exportación de larga duración al eliminarse los datos en mitad de la exportación.' - - 'Los vínculos a páginas inaccesibles se han eliminado.' - - 'Al agregar un equipo como revisor a una solicitud de incorporación de cambios se mostraría en ocasiones el número incorrecto de miembros de ese equipo.' - - 'Un número elevado de usuarios inactivos podría hacer que se produjera un error en una configuración de {% data variables.product.prodname_github_connect %}.' - - 'La página "Inscripciones a características y beta" de la interfaz de usuario web de administración del sitio no estaba correctamente disponible.' - - 'El vínculo del "Modo de administrador del sitio" del pie de página del sitio no cambió el estado al hacer clic.' - changes: - - 'Los límites de conexión Memcached aumentaron para adaptarse mejor a topologías de clúster de gran tamaño.' - - 'Identifica y elimina registros de webhooks fuera de la ventana de retención de registros de webhook de forma más eficiente.' - - 'Dependency Graph API se ejecutaba anteriormente con un puerto definido estáticamente.' - - 'Se han actualizado los recuentos de particiones predeterminados para la configuración de particiones de Elasticsearch relacionadas con el clúster.' - - 'Los roles de "Evaluación de prioridades" y "Mantenimiento" de los equipos se conservan durante las migraciones de repositorio.' - - 'Las excepciones "NotProcessedError" se producían de manera innecesaria.' - - 'Se ha mejorado el rendimiento de las solicitudes web realizadas por propietarios empresariales.' - known_issues: - - 'El registro npm de {% data variables.product.prodname_registry %} ya no devuelve un valor de hora en las respuestas de metadatos. Esto se hacía para permitir mejoras de rendimiento importantes. Seguimos teniendo todos los datos necesarios para devolver un valor de tiempo como parte de la respuesta de metadatos y reanudaremos la devolución de este valor en el futuro una vez que hayamos resuelto las incidencias de rendimiento existentes.' - - 'En una instancia recién configurada de {% data variables.product.prodname_ghe_server %} sin ningún usuario, un atacante podría crear el primer usuario administrador.' - - 'Las reglas de cortafuegos personalizadas se eliminan durante el proceso de actualización.' - - 'Los archivos supervisados de Git LFS [cargados desde la interface web](https://github.com/blog/2105-upload-files-to-your-repositories) se han agregado de manera incorrecta y directa al repositorio.' - - "Las incidencias no se pueden cerrar si contienen un enlace permanente a un blob del mismo repositorio en el que la ruta es mayor de 255\_caracteres." - - 'Cuando se habilita "Los usuarios pueden buscar en GitHub.com" con {% data variables.product.prodname_github_connect %}, las incidencias en los repositorios privados e internos no se incluyen en los resultados de búsqueda de {% data variables.product.prodname_dotcom_the_website %}.' - - 'Si se habilitan las {% data variables.product.prodname_actions %} para {% data variables.product.prodname_ghe_server %}, desmontar un nodo de réplica con "ghe-repl-teardown" tendrá éxito, pero podría devolver un "ERROR:Running migrations".' - - 'Los límites de recursos que son específicos para procesar enlaces previos a la recepción podrían ocasionar errores en algunos de ellos.' diff --git a/translations/es-ES/data/release-notes/enterprise-server/3-1/2.yml b/translations/es-ES/data/release-notes/enterprise-server/3-1/2.yml deleted file mode 100644 index 015a7300ab..0000000000 --- a/translations/es-ES/data/release-notes/enterprise-server/3-1/2.yml +++ /dev/null @@ -1,26 +0,0 @@ -date: '2021-06-24' -sections: - security_fixes: - - Packages have been updated to the latest security versions. - bugs: - - A large number of `gauge-dependency-graph-api-dispatch_dispatch` metrics could accumulate in the Management Console. - - The sshd service would sometimes fail to start on instances running on Google Cloud Platform. - - Old upgrade files would persist on the user disk, sometimes resulting in out of space conditions. - - '`gh-migrator` displayed an incorrect path to its log output.' - - An export archive would silently fail to import pull requests if they contained review requests from teams not present in the archive. - changes: - - Update the {% data variables.product.prodname_actions %} Runner version in GHES 3.1 to [v2.278.0](https://github.com/actions/runner/releases/tag/v2.278.0) - known_issues: - - The {% data variables.product.prodname_registry %} npm registry no longer returns a time value in metadata responses. This was done to allow for substantial performance improvements. We continue to have all the data necessary to return a time value as part of the metadata response and will resume returning this value in the future once we have solved the existing performance issues. - - 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. - - | - 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" - ``` - - If {% data variables.product.prodname_actions %} is enabled for {% data variables.product.prodname_ghe_server %}, teardown of a replica node with `ghe-repl-teardown` will succeed, but may return `ERROR:Running migrations`. - - Resource limits that are specific to processing pre-receive hooks may cause some pre-receive hooks to fail. diff --git a/translations/es-ES/data/release-notes/enterprise-server/3-1/20.yml b/translations/es-ES/data/release-notes/enterprise-server/3-1/20.yml deleted file mode 100644 index 9a00aa37b5..0000000000 --- a/translations/es-ES/data/release-notes/enterprise-server/3-1/20.yml +++ /dev/null @@ -1,22 +0,0 @@ -date: '2022-04-20' -sections: - security_fixes: - - 'Los paquetes se han actualizado a las últimas versiones de seguridad.' - bugs: - - 'La actualización de los nodos en un par de alta disponibilidad con un paquete de actualización podía hacer que Elasticsearch entrara en un estado incoherente en algunos casos.' - - 'En algunas topologías de clúster, las utilidades de la línea de comandos "ghe-spokesctl" y "ghe-btop" no se ejecutaban.' - - 'Los índices de Elasticsearch podían duplicarse durante una actualización de paquetes debido a la ejecución de un servicio "elasticsearch-upgrade" varias veces en paralelo.' - - 'Las colas de trabajo de "maint_host_low" no se procesaban, lo que causaba que algunas tareas de mantenimiento no se ejecutaran.' - - 'Al convertir una cuenta de usuario en una organización, si la cuenta de usuario era propietaria de la cuenta de empresa de {% data variables.product.prodname_ghe_server %}, la organización convertida aparecía de forma incorrecta en la lista de propietarios de la empresa.' - - 'La creación de un token de OAuth de suplantación mediante la API de REST de administración empresarial generaba un error al existir ya una integración coincidente con el identificador de aplicación OAuth.' - changes: - - 'Al intentar copiar en caché un valor más grande que el máximo permitido por Memcached, se producía un error, pero no se registraba la clave.' - known_issues: - - 'El registro npm de {% data variables.product.prodname_registry %} ya no devuelve un valor de hora en las respuestas de metadatos. Esto se hacía para permitir mejoras de rendimiento importantes. Seguimos teniendo todos los datos necesarios para devolver un valor de tiempo como parte de la respuesta de metadatos y reanudaremos la devolución de este valor en el futuro una vez que hayamos resuelto las incidencias de rendimiento existentes.' - - 'En una instancia recién configurada de {% data variables.product.prodname_ghe_server %} sin ningún usuario, un atacante podría crear el primer usuario administrador.' - - 'Las reglas de cortafuegos personalizadas se eliminan durante el proceso de actualización.' - - 'Los archivos supervisados de Git LFS [cargados desde la interface web](https://github.com/blog/2105-upload-files-to-your-repositories) se han agregado de manera incorrecta y directa al repositorio.' - - "Las incidencias no se pueden cerrar si contienen un enlace permanente a un blob del mismo repositorio en el que la ruta es mayor de 255\_caracteres." - - 'Cuando se habilita "Los usuarios pueden buscar en GitHub.com" con {% data variables.product.prodname_github_connect %}, las incidencias en los repositorios privados e internos no se incluyen en los resultados de búsqueda de {% data variables.product.prodname_dotcom_the_website %}.' - - 'Si se habilitan las {% data variables.product.prodname_actions %} para {% data variables.product.prodname_ghe_server %}, desmontar un nodo de réplica con "ghe-repl-teardown" tendrá éxito, pero podría devolver un "ERROR:Running migrations".' - - 'Los límites de recursos que son específicos para procesar enlaces previos a la recepción podrían ocasionar errores en algunos de ellos.' diff --git a/translations/es-ES/data/release-notes/enterprise-server/3-1/21.yml b/translations/es-ES/data/release-notes/enterprise-server/3-1/21.yml deleted file mode 100644 index 2aaa766bcb..0000000000 --- a/translations/es-ES/data/release-notes/enterprise-server/3-1/21.yml +++ /dev/null @@ -1,25 +0,0 @@ -date: '2022-05-17' -sections: - security_fixes: - - '**MEDIO:** Se ha identificado una incidencia de seguridad en el solucionador nginx, por la que un atacante que puede falsificar paquetes UDP del servidor DNS puede dar lugar a una sobrescritura de memoria de 1 byte, lo que provoca el bloqueo del proceso de trabajo u otros impactos potencialmente perjudiciales. Se ha asignado la vulnerabilidad [CVE-2021-23017](https://nvd.nist.gov/vuln/detail/CVE-2021-23017).' - - "Se han actualizado las acciones \"actions/checkout@v2\" y \"actions/checkout@v3\" para resolver nuevas vulnerabilidades anunciadas en la [entrada de blog sobre el cumplimiento de la seguridad de Git](https://github.blog/2022-04-12-git-security-vulnerability-announced/)." - - Los paquetes se han actualizado a las versiones de seguridad más recientes. - bugs: - - "En algunas topologías de clúster, el comando \"ghe-cluster-status\" generó directorios vacíos en \"/tmp\"." - - "SNMP registró incorrectamente un gran número de mensajes de error \"Cannot statfs\" en syslog." - - "En el caso de las instancias configuradas con la autenticación SAML y la reserva integrada habilitada, los usuarios integrados se quedarían bloqueados en un bucle de “inicio de sesión” al tratar de iniciar sesión desde la página generada después de cerrar la sesión." - - "Al usar aserciones cifradas SAML, algunas aserciones no marcaban correctamente las claves SSH como comprobadas." - - 'La página Versiones devolvería un error 500 si el repositorio tuviera etiquetas con caracteres no ASCII. [Actualizado: 2022-06-10]' - changes: - - "En el caso de las configuraciones de alta disponibilidad, deja claro que en la página de información general de replicación de la consola de administración solo se muestra la configuración de replicación actual, no el estado de replicación actual." - - "Al habilitar {% data variables.product.prodname_registry %}, deja claro que usar un token de firma de acceso compartido (SAS) como cadena de conexión no se admite." - - Los conjuntos de soporte técnico ahora incluyen el recuento de filas de las tablas almacenadas en MySQL. - known_issues: - - "El registro npm de {% data variables.product.prodname_registry %} ya no devuelve un valor de tiempo en las respuestas de metadatos. Esto se hacía para permitir mejoras de rendimiento importantes. Seguimos teniendo todos los datos necesarios para devolver un valor de tiempo como parte de la respuesta de metadatos y reanudaremos la devolución de este valor en un futuro una vez que hayamos resuelto las incidencias de rendimiento existentes." - - "En una instancia recién configurada de {% data variables.product.prodname_ghe_server %} sin ningún usuario, un atacante podría crear el primer usuario administrador." - - Las reglas de firewall personalizadas se eliminan durante el proceso de actualización. - - "Los archivos supervisados de Git LFS [cargados a través la interfaz web](https://github.com/blog/2105-upload-files-to-your-repositories) se agregaron incorrecta y directamente al repositorio." - - Las incidencias no se pueden cerrar si contienen un vínculo permanente a un blob en el mismo repositorio en el que la ruta de acceso del archivo del blob tiene más de 255 caracteres. - - "Cuando se habilita \"Los usuarios pueden buscar en GitHub.com\" con {% data variables.product.prodname_github_connect %}, las incidencias en los repositorios privados e internos no se incluyen en los resultados de la búsqueda de {% data variables.product.prodname_dotcom_the_website %}." - - "Si se habilita {% data variables.product.prodname_actions %} para {% data variables.product.prodname_ghe_server %}, el desmontaje de un nodo de réplica con \"ghe-repl-teardown\" se realizará correctamente, pero puede devolver \"ERROR: Ejecutando migraciones\"." - - Los límites de recursos que son específicos para el procesamiento de enlaces previos a la recepción pueden provocar un error en algunos enlaces previos a la recepción. diff --git a/translations/es-ES/data/release-notes/enterprise-server/3-1/22.yml b/translations/es-ES/data/release-notes/enterprise-server/3-1/22.yml deleted file mode 100644 index 112b5fa12e..0000000000 --- a/translations/es-ES/data/release-notes/enterprise-server/3-1/22.yml +++ /dev/null @@ -1,20 +0,0 @@ -date: '2022-06-09' -sections: - security_fixes: - - Los paquetes se han actualizado a las versiones de seguridad más recientes. - bugs: - - "Un script interno para validar nombres de host en el archivo de configuración {% data variables.product.prodname_ghe_server %} devolvería un error si la cadena del nombre de host comenzara con \".\" (carácter de punto)." - - "En configuraciones de alta disponibilidad en las que el nombre de host del nodo principal tenía más de 60 caracteres, no se podía configurar MySQL." - - "El cálculo de \"confirmadores máximos en toda la instancia\" notificado en el panel de administración del sitio era incorrecto." - - "Una entrada de base de datos incorrecta para las réplicas del repositorio provocó daños en la base de datos al realizar una restauración mediante {% data variables.product.prodname_enterprise_backup_utilities %}." - changes: - - "En las configuraciones de alta disponibilidad donde Elasticsearch notificó un estado amarillo válido, los cambios introducidos en una corrección anterior bloquearían el comando \"ghe-repl-stop\" y no permitirían que se detuviera la replicación. El uso de \"ghe-repo-stop --force\" exigirá la detección de Elasticsearch cuando el servicio se encuentre en un estado amarillo normal o válido." - known_issues: - - "El registro npm de {% data variables.product.prodname_registry %} ya no devuelve un valor de tiempo en las respuestas de metadatos. Esto se hacía para permitir mejoras de rendimiento importantes. Seguimos teniendo todos los datos necesarios para devolver un valor de tiempo como parte de la respuesta de metadatos y reanudaremos la devolución de este valor en un futuro una vez que hayamos resuelto las incidencias de rendimiento existentes." - - "En una instancia recién configurada de {% data variables.product.prodname_ghe_server %} sin ningún usuario, un atacante podría crear el primer usuario administrador." - - Las reglas de firewall personalizadas se eliminan durante el proceso de actualización. - - "Los archivos supervisados de Git LFS [cargados a través la interfaz web](https://github.com/blog/2105-upload-files-to-your-repositories) se agregaron incorrecta y directamente al repositorio." - - Las incidencias no se pueden cerrar si contienen un vínculo permanente a un blob en el mismo repositorio en el que la ruta de acceso del archivo del blob tiene más de 255 caracteres. - - "Cuando se habilita \"Los usuarios pueden buscar en GitHub.com\" con {% data variables.product.prodname_github_connect %}, las incidencias en los repositorios privados e internos no se incluyen en los resultados de la búsqueda de {% data variables.product.prodname_dotcom_the_website %}." - - "Si se habilita {% data variables.product.prodname_actions %} para {% data variables.product.prodname_ghe_server %}, el desmontaje de un nodo de réplica con \"ghe-repl-teardown\" se realizará correctamente, pero puede devolver \"ERROR: Ejecutando migraciones\"." - - Los límites de recursos que son específicos para el procesamiento de enlaces previos a la recepción pueden provocar un error en algunos enlaces previos a la recepción. diff --git a/translations/es-ES/data/release-notes/enterprise-server/3-1/3.yml b/translations/es-ES/data/release-notes/enterprise-server/3-1/3.yml deleted file mode 100644 index 66fb21fb2a..0000000000 --- a/translations/es-ES/data/release-notes/enterprise-server/3-1/3.yml +++ /dev/null @@ -1,27 +0,0 @@ -date: '2021-07-14' -sections: - security_fixes: - - "**ALTO RIESGO:** se ha identificado una vulnerabilidad de salto de directorio en el servidor de GitHub Enterprise que podría explotarse al crear un sitio de GitHub Pages. Las opciones de configuración controladas por el usuario utilizadas por GitHub Pages no estaba lo suficientemente restringida y permitía leer archivos en la instancia del servidor de GitHub Enterprise. Para aprovechar esta vulnerabilidad de seguridad, un atacante necesitaría permiso para crear un sitio de GitHub Pages en la instancia del servidor de GitHub Enterprise. Esta vulnerabilidad afectaba a todas las versiones del servidor de GitHub Enterprise anteriores a la\_3.1.3 y se le ha asignado CVE-2021-22867. Se informó de esta vulnerabilidad mediante el programa de GitHub Bug Bounty." - - 'Los paquetes se han actualizado a las últimas versiones de seguridad.' - bugs: - - 'La variable de vencimiento de fecha de SAML no se pudo configurar.' - - 'Los servicios de aplicación fallaron en sus verificaciones de salud durante una aplicación de configuración antes de que pudieran ingresar a un estado saludable.' - - 'El "ghe-cluster-config-node-init" falló durante la configuración de clúster si se había habilitado el proxy de HTTP.' - - 'Los enlaces previos a la recepción podían encontrar un error de tipo "Failed to resolve full path of the current executable" debido a que un "/proc" no se pudo montar en el contenedor.' - - 'Collectd no resolvió el nombre de host de destino que se estaba reenviando después del inicio principal.' - - 'El trabajo que purgó los repositorios inactivos borrados pudo haber fallado en hacer progreso si alguno de estos repositorios estaba protegido contra borrado debido a las retenciones legales.' - - 'Los trabajos en segundo plano se pusieron en la fila de "spam", los cuales no se estaban procesando.' - - 'El método de fusión preferido se restablecerá cuando se reintente después de una fusión fallida de solicitud de cambio.' - - 'Las subidas de Git dieron como resultado un Error de servidor interno 500 durante el proceso de reconciliación del usuario en las instancias que utilizaban el modo de autenticación de LDAP.' - - "Después de mejorar la versión\_3.0.x a la 3.1.x, en algunos casos, las Acciones de GitHub fallarían con un error: \"An unexpected error occurred when executing this workflow\"." - changes: - - 'Se mejoró la eficiencia de la aplicación de configuraciones al omitir las reglas de cortafuegos para permitir IP, las cuales no hubieran cambiado, lo cual ahorró tiempo significativo en los clústeres grandes.' - known_issues: - - 'El registro npm de {% data variables.product.prodname_registry %} ya no devuelve un valor de hora en las respuestas de metadatos. Esto se hacía para permitir mejoras de rendimiento importantes. Seguimos teniendo todos los datos necesarios para devolver un valor de tiempo como parte de la respuesta de metadatos y reanudaremos la devolución de este valor en el futuro una vez que hayamos resuelto las incidencias de rendimiento existentes.' - - 'En una instalación nueva de {% data variables.product.prodname_ghe_server %} que no tenga ningún usuario, cualquier atacante podría crear el primer usuario administrativo.' - - 'Las reglas de cortafuegos personalizadas se eliminan durante el proceso de actualización.' - - 'Los archivos supervisados de Git LFS [cargados desde la interface web](https://github.com/blog/2105-upload-files-to-your-repositories) se han agregado de manera incorrecta y directa al repositorio.' - - "Las incidencias no se pueden cerrar si contienen un enlace permanente a un blob del mismo repositorio en el que la ruta es mayor de 255\_caracteres." - - 'Cuando se habilita "Los usuarios pueden buscar en GitHub.com" con GitHub Connect, las incidencias en los repositorios privados e internos no se incluyen en los resultados de la búsqueda de GitHub.com.' - - 'Si se habilitan las {% data variables.product.prodname_actions %} para {% data variables.product.prodname_ghe_server %}, desmontar un nodo de réplica con "ghe-repl-teardown" tendrá éxito, pero podría devolver un "ERROR:Running migrations".' - - 'Los límites de recursos que son específicos para procesar enlaces previos a la recepción podrían ocasionar errores en algunos de ellos.' diff --git a/translations/es-ES/data/release-notes/enterprise-server/3-1/4.yml b/translations/es-ES/data/release-notes/enterprise-server/3-1/4.yml deleted file mode 100644 index 4846e1652c..0000000000 --- a/translations/es-ES/data/release-notes/enterprise-server/3-1/4.yml +++ /dev/null @@ -1,36 +0,0 @@ -date: '2021-07-27' -sections: - security_fixes: - - Packages have been updated to the latest security versions. - bugs: - - The counts on packages pages were not being incremented when a package was downloaded. - - '`ghe-config-apply` would timeout, ask for a prompt or fail for a customer that had {% data variables.product.prodname_secret_scanning %} enabled, and had either disabled or never enabled {% data variables.product.prodname_actions %} on their instance.' - - Log files were not reopened after rotation in some cases leading to high disk space usage on instances with high uptime. - - Upgrade could fail from older version of {% data variables.product.prodname_ghe_server %} due to a missing job in {% data variables.product.prodname_actions %}. - - 'Custom pre-receive hooks could lead to an error like `error: object directory /data/user/repositories/0/nw/12/34/56/7890/network.git/objects does not exist; check .git/objects/info/alternates`.' - - Unauthenticated HTTP proxy for the pages containers build was not supported for any users that use HTTP proxies. - - A significant number of 503 errors were logged every time a user visited a repository's `/settings` page if the dependency graph was not enabled. - - Internal repositories were only returned when a user had affiliations with the repository through a team or through collaborator status, or queried with the `?type=internal` parameter. - - Failed background jobs had unlimited retries which could cause large queue depths. - - A significant number of 503 errors were being created if the scheduled job to sync vulnerabilities with GitHub.com attempted to run when dependency graph was not enabled and content analysis was enabled. - - | - When {% data variables.product.prodname_actions %} is enabled without running regular scheduled backups, the MSSQL transaction log could grow unbounded and can consume all available space on the appliance's data disk, causing a possible outage. - - If you have configured regularly scheduled MSSQL backups, no further actions is required. Otherwise, if you have {% data variables.product.prodname_actions %} previously enabled, run the following commands after installing this patch. - - ``` - ghe-actions-console -s Mps -c 'Update-Service -Force' - ghe-actions-console -s Token -c 'Update-Service -Force' - ghe-actions-console -s Actions -c 'Update-Service -Force' - ``` - changes: - - The logs for `babeld` now include a `cmd` field for HTTP ref advertisement requests instead of only including it during the negotiation requests. - known_issues: - - The {% data variables.product.prodname_registry %} npm registry no longer returns a time value in metadata responses. This was done to allow for substantial performance improvements. We continue to have all the data necessary to return a time value as part of the metadata response and will resume returning this value in the future once we have solved the existing performance issues. - - 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. - - If {% data variables.product.prodname_actions %} is enabled for {% data variables.product.prodname_ghe_server %}, teardown of a replica node with `ghe-repl-teardown` will succeed, but may return `ERROR:Running migrations`. - - Resource limits that are specific to processing pre-receive hooks may cause some pre-receive hooks to fail. diff --git a/translations/es-ES/data/release-notes/enterprise-server/3-1/5.yml b/translations/es-ES/data/release-notes/enterprise-server/3-1/5.yml deleted file mode 100644 index 3fab7fd335..0000000000 --- a/translations/es-ES/data/release-notes/enterprise-server/3-1/5.yml +++ /dev/null @@ -1,20 +0,0 @@ -date: '2021-08-10' -sections: - bugs: - - 'Los enlaces previos a la recepción que utilizaban un subshell de bash devolvían un error de tipo: "No such file or directory".' - - "Cuando se habilitaba Acciones de GitHub sin ejecutar copias de seguridad programadas periódicamente, el registro de transacciones de MSSQL podía crecer más allá de los límites y consumir todo el espacio disponible en el disco de datos del dispositivo, lo que ocasionaba una posible interrupción del servicio." - - El registro innecesario en las bases de datos consumía una gran cantidad de espacio en disco en las instancias con un uso elevado de LFS. - - "Las entradas de registro de auditoría para los cambios realizados en los ajustes de la organización de \"Creación de repositorios\" eran inexactas." - - "El registro excesivo de las excepciones de \"ActionController::UnknownFormat\" causa un uso innecesario de disco." - - "Los valores de \"group_dn\"de LDAP de más de 255 caracteres dieron como resultado que los errores se registraran: \"Datos truncados para la columna 'group_dn' en la fila 1\"." - changes: - - "Los límites de frecuencia abusiva ahora se llaman límites de frecuencia secundarios, ya que el comportamiento que limitan no siempre es abusivo." - known_issues: - - "El registro npm de {% data variables.product.prodname_registry %} ya no devuelve un valor de tiempo en las respuestas de metadatos. Esto se hacía para permitir mejoras de rendimiento importantes. Seguimos teniendo todos los datos necesarios para devolver un valor de tiempo como parte de la respuesta de metadatos y reanudaremos la devolución de este valor en el futuro una vez que hayamos resuelto las incidencias de rendimiento existentes." - - "En una instalación nueva de {% data variables.product.prodname_ghe_server %} que no tenga ningún usuario, un atacante podría crear el primer usuario administrador." - - Las reglas de cortafuegos personalizadas se eliminan durante el proceso de actualización. - - "Los archivos supervisados de Git LFS [cargados desde la interfaz web](https://github.com/blog/2105-upload-files-to-your-repositories) se agregan de manera incorrecta y directa al repositorio." - - Las incidencias no se pueden cerrar si contienen un enlace permanente a un blob del mismo repositorio en el que la ruta es mayor de 255 caracteres. - - "Cuando se habilita \"Los usuarios pueden buscar en GitHub.com\" con GitHub Connect, las incidencias en los repositorios privados e internos no se incluyen en los resultados de la búsqueda de GitHub.com." - - "Si se habilitan las {% data variables.product.prodname_actions %} para {% data variables.product.prodname_ghe_server %}, desmontar un nodo de réplica con \"ghe-repl-teardown\" tendrá éxito, pero podría devolver un \"ERROR:Running migrations\"." - - Los límites de recursos que son específicos para procesar enlaces previos a la recepción podrían ocasionar errores en algunos de ellos. diff --git a/translations/es-ES/data/release-notes/enterprise-server/3-1/6.yml b/translations/es-ES/data/release-notes/enterprise-server/3-1/6.yml deleted file mode 100644 index 050d49fce0..0000000000 --- a/translations/es-ES/data/release-notes/enterprise-server/3-1/6.yml +++ /dev/null @@ -1,23 +0,0 @@ -date: '2021-08-24' -sections: - security_fixes: - - Los paquetes se han actualizado a las últimas versiones de seguridad. - bugs: - - La agregación de imágenes muy grandes o GIF animados a las imágenes o solicitudes de cambio producía un error. - - "Los mensajes de Journald con relación a las actualizaciones automáticas (\"Agregar una hora aleatoria en h/m/s\".) se registraban en syslog." - - "Los enlaces previos a la recepción que crearon canalizaciones nombradas (FIFO) fallaban o se colgaban, lo cual resultó en un error de tiempo de espera." - - Agregar filtros para que la página de búsqueda avanzada de registros de auditoría no llene la caja de texto de consultas en tiempo real con el valor y prefijo de faceta correcto. - - "Los enlaces de Git hacia la API interna que dio como resultado solicitudes fallidas devolvieron la excepción \"undefined method body for \"success\":String (NoMethodError)\" en vez de devolver un \"nil\" explícito." - - "Cuando se eliminó una integración, fue posible que una aplicación OAuth o integración no relacionadas también se eliminaran." - - "Cuando se agregó un mensaje obligatorio que contenía un caracter de emoji que intentaba ver o cambiar el mensaje, se devolvió un error tipo \"500 Internal Server Error\"." - changes: - - "Agrega \"triage\" y \"maintain\" a la lista de permisos que devuelve la API de REST." - known_issues: - - "El registro npm de {% data variables.product.prodname_registry %} ya no devuelve un valor de hora en las respuestas de metadatos. Esto se hacía para permitir mejoras de rendimiento importantes. Seguimos teniendo todos los datos necesarios para devolver un valor de tiempo como parte de la respuesta de metadatos y reanudaremos la devolución de este valor en el futuro una vez que hayamos resuelto las incidencias de rendimiento existentes." - - "En una instalación nueva de {% data variables.product.prodname_ghe_server %} que no tenga ningún usuario, cualquier atacante podría crear el primer usuario administrativo." - - Las reglas de cortafuegos personalizadas se eliminan durante el proceso de actualización. - - "Los archivos supervisados de Git LFS [cargados desde la interface web](https://github.com/blog/2105-upload-files-to-your-repositories) se han agregado de manera incorrecta y directa al repositorio." - - Las incidencias no se pueden cerrar si contienen un enlace permanente a un blob del mismo repositorio en el que la ruta es mayor de 255 caracteres. - - "Cuando se habilita \"Los usuarios pueden buscar en GitHub.com\" con GitHub Connect, las incidencias en los repositorios privados e internos no se incluyen en los resultados de la búsqueda de GitHub.com." - - "Si se habilitan las {% data variables.product.prodname_actions %} para {% data variables.product.prodname_ghe_server %}, desmontar un nodo de réplica con \"ghe-repl-teardown\" tendrá éxito, pero podría devolver un \"ERROR:Running migrations\"." - - Los límites de recursos que son específicos para procesar enlaces previos a la recepción podrían ocasionar errores en algunos de ellos. diff --git a/translations/es-ES/data/release-notes/enterprise-server/3-1/7.yml b/translations/es-ES/data/release-notes/enterprise-server/3-1/7.yml deleted file mode 100644 index b34fe5368c..0000000000 --- a/translations/es-ES/data/release-notes/enterprise-server/3-1/7.yml +++ /dev/null @@ -1,18 +0,0 @@ -date: '2021-09-07' -sections: - security_fixes: - - 'Los paquetes se han actualizado a las últimas versiones de seguridad.' - bugs: - - 'Intentar anular un nodo de réplica recién agregado especificando su UUID con "ghe-repl-teardown" falló sin reportar un error en caso de que la replicación no se hubiera iniciado.' - - 'Las compilaciones de GitHub Pages se estaban pasando por un proxy externo si es que había alguno configurado.' - - 'Los enlaces previos a la recepción que crearon subprocesos no tenían una variable de "PATH" en su entorno, lo cual dio como resultado un error de tipo "No such file or directory".' - - 'MySQL pudo haberse recuperado de un desastre durante una actualización si se hubiera habilitado "mysql-auto-failover".' - known_issues: - - 'El registro npm de {% data variables.product.prodname_registry %} ya no devuelve un valor de hora en las respuestas de metadatos. Esto se hacía para permitir mejoras de rendimiento importantes. Seguimos teniendo todos los datos necesarios para devolver un valor de tiempo como parte de la respuesta de metadatos y reanudaremos la devolución de este valor en el futuro una vez que hayamos resuelto las incidencias de rendimiento existentes.' - - 'En una instalación nueva de {% data variables.product.prodname_ghe_server %} que no tenga ningún usuario, cualquier atacante podría crear el primer usuario administrativo.' - - 'Las reglas de cortafuegos personalizadas se eliminan durante el proceso de actualización.' - - 'Los archivos supervisados de Git LFS [cargados desde la interface web](https://github.com/blog/2105-upload-files-to-your-repositories) se han agregado de manera incorrecta y directa al repositorio.' - - "Las incidencias no se pueden cerrar si contienen un enlace permanente a un blob del mismo repositorio en el que la ruta es mayor de 255\_caracteres." - - 'Cuando se habilita "Los usuarios pueden buscar en GitHub.com" con GitHub Connect, las incidencias en los repositorios privados e internos no se incluyen en los resultados de la búsqueda de GitHub.com.' - - 'Si se habilitan las {% data variables.product.prodname_actions %} para {% data variables.product.prodname_ghe_server %}, desmontar un nodo de réplica con "ghe-repl-teardown" tendrá éxito, pero podría devolver un "ERROR:Running migrations".' - - 'Los límites de recursos que son específicos para procesar enlaces previos a la recepción podrían ocasionar errores en algunos de ellos.' diff --git a/translations/es-ES/data/release-notes/enterprise-server/3-1/8.yml b/translations/es-ES/data/release-notes/enterprise-server/3-1/8.yml deleted file mode 100644 index 1faf7ac7f0..0000000000 --- a/translations/es-ES/data/release-notes/enterprise-server/3-1/8.yml +++ /dev/null @@ -1,20 +0,0 @@ -date: '2021-09-24' -sections: - security_fixes: - - "**ALTO RIESGO:** se ha identificado una vulnerabilidad de salto de directorio en {% data variables.product.prodname_ghe_server %} que podía aprovecharse al compilar un sitio {% data variables.product.prodname_pages %}. Las opciones de configuración controladas por el usuario utilizadas por {% data variables.product.prodname_pages %} no estaban lo suficientemente restringidas y permitían leer archivos en la instancia de {% data variables.product.prodname_ghe_server %}. Para aprovecharse de esta vulnerabilidad, el atacante necesitaba permiso para crear y compilar un sitio de {% data variables.product.prodname_pages %} en la instancia de {% data variables.product.prodname_ghe_server %}. Esta vulnerabilidad afectó a todas las versiones de {% data variables.product.prodname_ghe_server %} anteriores a la\_3.1.8 y se corrigió en las versiones\_3.1.8, 3.0.16 y 2.22.22. Esto se debe a una corrección incompleta para CVE-2021-22867. La vulnerabilidad se reportó mediante el programa GitHub Bug Bounty y se le ha asignado el código CVE-2021-22868. {% comment %} https://github.com/github/pages/pull/3361, https://github.com/github/pages/pull/3357 {% endcomment %}" - - '**RIESGO MEDIO:** una vulnerabilidad de control de acceso inadecuado en {% data variables.product.prodname_ghe_server %} permitía a un trabajo de flujo de trabajo ejecutarse en un grupo de ejecutor autohospedado al que no debería tener acceso. Esto afecta a los clientes que utilizan grupos de ejecutores autohospedados para el control de acceso. Un repositorio con acceso a un grupo de ejecutores de empresa podía acceder a todos los grupos de ejecutores de empresa dentro de la organización a causa de comprobaciones de autenticación incorrectas durante la solicitud. Esto podía causar que el código lo ejecutara no intencionalmente el grupo de ejecutor incorrecto. Esta vulnerabilidad afectó a las versiones de {% data variables.product.prodname_ghe_server %} de 3.0.0 a 3.0.15 y 3.1.0 a 3.1.7 y se corrigió en las versiones 3.0.16 y 3.1.8. Se le asignó CVE-2021-22869. {% comment %} https://github.com/github/enterprise2/pull/27013 {% endcomment %}' - bugs: - - 'Los recuentos del trabajador de Resque se mostraron incorrectamente durante el modo de mantenimiento. {% comment %} https://github.com/github/enterprise2/pull/26899, https://github.com/github/enterprise2/pull/26883 {% endcomment %}' - - 'La memoria memcached asignada pudo haber sido cero en el modo de agrupación en clústeres. {% comment %} https://github.com/github/enterprise2/pull/26928, https://github.com/github/enterprise2/pull/26832 {% endcomment %}' - - 'Los archivos binarios no vacíos mostraron un tipo y tamaño de archivo incorrectos en la pestaña "Archivos" de una solicitud de cambios. {% comment %} https://github.com/github/github/pull/192810, https://github.com/github/github/pull/172284, https://github.com/github/coding/issues/694 {% endcomment %}' - - 'Se han corregido las compilaciones de {% data variables.product.prodname_pages %} para que tengan en cuenta el ajuste NO_PROXY del dispositivo. Esto es importante para dispositivos configurados solo con un proxy HTTP. (actualizado el 30-09-2021) {% comment %} https://github.com/github/pages/pull/3360 {% endcomment %}' - - 'La configuración de GitHub Connect de la instancia de origen siempre se restauraba en instancias nuevas, aunque no se utilizara la opción "--config" de "ghe-restore". Esto causaría un conflicto con la conexión y sincronización de licencia de GitHub Connect si las instancias de origen y destino estuvieran en línea al mismo tiempo. La corrección también requiere actualizar backup-utils a 3.2.0 o posterior. [actualizado el 18-11-2021]' - known_issues: - - 'El registro npm de {% data variables.product.prodname_registry %} ya no devuelve un valor de hora en las respuestas de metadatos. Esto se hacía para permitir mejoras de rendimiento importantes. Seguimos teniendo todos los datos necesarios para devolver un valor de tiempo como parte de la respuesta de metadatos y reanudaremos la devolución de este valor en el futuro una vez que hayamos resuelto las incidencias de rendimiento existentes.' - - 'En una instalación nueva de {% data variables.product.prodname_ghe_server %} que no tenga ningún usuario, cualquier atacante podría crear el primer usuario administrativo.' - - 'Las reglas de cortafuegos personalizadas se eliminan durante el proceso de actualización.' - - 'Los archivos supervisados de Git LFS [cargados desde la interface web](https://github.com/blog/2105-upload-files-to-your-repositories) se han agregado de manera incorrecta y directa al repositorio.' - - "Las incidencias no se pueden cerrar si contienen un enlace permanente a un blob del mismo repositorio en el que la ruta es mayor de 255\_caracteres." - - 'Cuando se habilita "Los usuarios pueden buscar en GitHub.com" con GitHub Connect, las incidencias en los repositorios privados e internos no se incluyen en los resultados de la búsqueda de GitHub.com.' - - 'Si se habilitan las {% data variables.product.prodname_actions %} para {% data variables.product.prodname_ghe_server %}, desmontar un nodo de réplica con "ghe-repl-teardown" tendrá éxito, pero podría devolver un "ERROR:Running migrations".' - - 'Los límites de recursos que son específicos para procesar enlaces previos a la recepción podrían ocasionar errores en algunos de ellos.' diff --git a/translations/es-ES/data/release-notes/enterprise-server/3-1/9.yml b/translations/es-ES/data/release-notes/enterprise-server/3-1/9.yml deleted file mode 100644 index 1762fa80eb..0000000000 --- a/translations/es-ES/data/release-notes/enterprise-server/3-1/9.yml +++ /dev/null @@ -1,28 +0,0 @@ -date: '2021-10-12' -sections: - security_fixes: - - 'Los paquetes se han actualizado a sus últimas versiones de seguridad. {% comment %} https://github.com/github/enterprise2/pull/27035, https://github.com/github/enterprise2/pull/27010 {% endcomment %}' - bugs: - - 'Los enlaces previos a la recepción personalizados fallaban debido a los límites demasiado restrictivos en la memoria virtual o CPU.{% comment %} https://github.com/github/enterprise2/pull/26972, https://github.com/github/enterprise2/pull/26955 {% endcomment %}' - - 'Al intentar borrar todos los ajustes de configuración existentes con "ghe-cleanup-settings", se producía un error al reiniciar el servicio de la Consola de Administración. {% comment %} https://github.com/github/enterprise2/pull/26987, https://github.com/github/enterprise2/pull/26901 {% endcomment %}' - - 'Durante el desmonte de replicación mediante "ghe-repl-teardown", Memcached fallaba al reiniciarse. {% comment %} https://github.com/github/enterprise2/pull/26993, https://github.com/github/enterprise2/pull/26983 {% endcomment %}' - - 'Durante los periodos de carga alta, los usuarios recibían códigos de estado HTTP 503 cuando los servicios ascendentes fallaban sus revisiones de salud interna. {% comment %} https://github.com/github/enterprise2/pull/27082, https://github.com/github/enterprise2/pull/26999 {% endcomment %}' - - 'Con Acciones configuradas, la replicación de MSSQL fallaba después de restablecer desde una captura de pantalla de las Utilidades de Respaldo de GitHub Enterprise. {% comment %} https://github.com/github/enterprise2/pull/27097, https://github.com/github/enterprise2/pull/26254 {% endcomment %}' - - 'Pudo haberse mostrado un mensaje de error de "jq" erróneo al ejecutar "ghe-config-apply". {% comment %} https://github.com/github/enterprise2/pull/27194, https://github.com/github/enterprise2/pull/26784 {% endcomment %}' - - 'Se prohibía que los entornos de los enlaces previos a la recepción llamaran el comando cat mediante BusyBox en Alpine.{% comment %} https://github.com/github/enterprise2/pull/27115, https://github.com/github/enterprise2/pull/27094 {% endcomment %}' - - 'La contraseña de la base de datos externa se registraba en texto simple. {% comment %} https://github.com/github/enterprise2/pull/27173, https://github.com/github/enterprise2/pull/26413 {% endcomment %}' - - 'La recuperación de fallos desde un centro de datos de un clúster primario hacia uno de un clúster secundario era exitosa, pero tras la conmutación por error de vuelta al centro de datos del clúster primario original, se producía un error al promover los índices de Elasticsearch. {% comment %} https://github.com/github/github/pull/193181, https://github.com/github/github/pull/192447 {% endcomment %}' - - 'El botón "Importar equipos" en la página de equipos de las organizaciones devolvía un error HTTP 404. {% comment %} https://github.com/github/github/pull/193302 {% endcomment %}' - - 'En algunos casos, los administradores de GitHub Enterprise que intentaban ver la página "Usuarios inactivos" recibían una respuesta de tipo "502 Bad Gateway" o "504 Gateway Timeout". {% comment %} https://github.com/github/github/pull/194260, https://github.com/github/github/pull/193609 {% endcomment %}' - - 'Se impactó el rendimiento de forma negativa en algunas situaciones de carga alta como resultado del aumento en la cantidad de trabajos de "SynchronizePullRequestJob". {% comment %} https://github.com/github/github/pull/195253, https://github.com/github/github/pull/194591 {% endcomment %}' - changes: - - 'Se borran registros de webhook de forma más efectiva que salen de la ventana de retención de registros de webhook. {% comment %} https://github.com/github/enterprise2/pull/27158 {% endcomment %}' - known_issues: - - 'El registro npm de {% data variables.product.prodname_registry %} ya no devuelve un valor de hora en las respuestas de metadatos. Esto se hacía para permitir mejoras de rendimiento importantes. Seguimos teniendo todos los datos necesarios para devolver un valor de tiempo como parte de la respuesta de metadatos y reanudaremos la devolución de este valor en el futuro una vez que hayamos resuelto las incidencias de rendimiento existentes.' - - 'En una instalación nueva de {% data variables.product.prodname_ghe_server %} que no tenga ningún usuario, cualquier atacante podría crear el primer usuario administrativo.' - - 'Las reglas de cortafuegos personalizadas se eliminan durante el proceso de actualización.' - - 'Los archivos supervisados de Git LFS [cargados desde la interface web](https://github.com/blog/2105-upload-files-to-your-repositories) se han agregado de manera incorrecta y directa al repositorio.' - - "Las incidencias no se pueden cerrar si contienen un enlace permanente a un blob del mismo repositorio en el que la ruta es mayor de 255\_caracteres." - - 'Cuando se habilita "Los usuarios pueden buscar en GitHub.com" con GitHub Connect, las incidencias en los repositorios privados e internos no se incluyen en los resultados de la búsqueda de GitHub.com.' - - 'Si se habilitan las {% data variables.product.prodname_actions %} para {% data variables.product.prodname_ghe_server %}, desmontar un nodo de réplica con "ghe-repl-teardown" tendrá éxito, pero podría devolver un "ERROR:Running migrations".' - - 'Los límites de recursos que son específicos para procesar enlaces previos a la recepción podrían ocasionar errores en algunos de ellos.' diff --git a/translations/es-ES/data/release-notes/enterprise-server/3-2/0-rc1.yml b/translations/es-ES/data/release-notes/enterprise-server/3-2/0-rc1.yml deleted file mode 100644 index 634366e5e1..0000000000 --- a/translations/es-ES/data/release-notes/enterprise-server/3-2/0-rc1.yml +++ /dev/null @@ -1,309 +0,0 @@ -date: '2021-09-09' -release_candidate: true -deprecated: true -intro: If {% data variables.location.product_location %} is running a release candidate build, you can't upgrade with a hotpatch. We recommend only running release candidates on test environments. -sections: - features: - - heading: Custom patterns for secret scanning - notes: - # https://github.com/github/releases/issues/1426 - - | - {% data variables.product.prodname_GH_advanced_security %} customers can now specify custom patterns for secret scanning. When a new pattern is specified, secret scanning searches a repository's entire Git history for the pattern, as well as any new commits. - - User defined patterns are in beta for {% data variables.product.prodname_ghe_server %} 3.2. They can be defined at the repository, organization, and enterprise levels. For more information, see "[Defining custom patterns for secret scanning](/code-security/secret-scanning/defining-custom-patterns-for-secret-scanning)." - - - heading: Security overview for Advanced Security (beta) - notes: - # https://github.com/github/releases/issues/1381 - - | - {% data variables.product.prodname_GH_advanced_security %} customers now have an organization-level view of the application security risks detected by {% data variables.product.prodname_code_scanning %}, {% data variables.product.prodname_dependabot %}, and {% data variables.product.prodname_secret_scanning %}. The security overview shows the enablement status of security features on each repository, as well as the number of alerts detected. - - In addition, the security overview lists all {% data variables.product.prodname_secret_scanning %} alerts at the organization level. Similar views for {% data variables.product.prodname_dependabot %} and {% data variables.product.prodname_code_scanning %} alerts are coming in future releases. For more information, see "[About the security overview](/code-security/security-overview/about-the-security-overview)." - - ![Screenshot of security overview](/assets/images/enterprise/3.2/release-notes/security-overview-UI.png) - - - heading: Dependency review (beta) - notes: - # https://github.com/github/releases/issues/1364 - - | - {% data variables.product.prodname_GH_advanced_security %} customers can now see a rich diff of the dependencies changed in a pull request. 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 these dependencies. 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)." - - - heading: GitHub Actions environments - notes: - # https://github.com/github/releases/issues/1308 - - | - Environments, environment protection rules, and environment secrets are now generally available for {% data variables.product.prodname_actions %} on {% data variables.product.product_name %}. For more information, see "[Environments](/actions/reference/environments)." - - ![Environment protection rules](/assets/images/enterprise/3.2/release-notes/actions-environments.png) - - - heading: SSH authentication with security keys - notes: - # https://github.com/github/releases/issues/1276 - - | - SSH authentication using a FIDO2 security key is now supported when you add a `sk-ecdsa-sha2-nistp256@openssh.com` or `sk-ssh-ed25519@openssh.com` SSH key to your account. SSH security keys store secret key material on a separate hardware device that requires verification, such as a tap, to operate. For more information, see "[Generating a new SSH key and adding it to the ssh-agent](/github/authenticating-to-github/connecting-to-github-with-ssh/generating-a-new-ssh-key-and-adding-it-to-the-ssh-agent#generating-a-new-ssh-key-for-a-hardware-security-key)." - - - heading: 'Dark and dark dimmed themes' - notes: - # https://github.com/github/releases/issues/1260 - - | - Dark and dark dimmed themes are now available for the web UI. {% data variables.product.product_name %} will match your system preferences when you haven't set theme preferences in {% data variables.product.product_name %}. You can also choose which themes are active during the day and night. For more information, see "[Managing your theme settings](/github/setting-up-and-managing-your-github-user-account/managing-user-account-settings/managing-your-theme-settings)." - - ![Dark and dark dimmed themes](https://user-images.githubusercontent.com/33528647/114629560-d2231f80-9c86-11eb-9bde-cc301a97040d.gif) - - - heading: 'Approving unverified domains for email notifications' - notes: - # https://github.com/github/releases/issues/1244 - - Domains that are not able to be verified can now be approved for email notification routing. Enterprise and organization owners will be able to approve domains and immediately augment their email notification restriction policy, allowing notifications to be sent to collaborators, consultants, acquisitions, or other partners. For more information, see "[Verifying or approving a domain for your enterprise](/admin/configuration/configuring-your-enterprise/verifying-or-approving-a-domain-for-your-enterprise#about-approval-of-domains)" and "[Restricting email notifications for your enterprise](/admin/policies/enforcing-policies-for-your-enterprise/restricting-email-notifications-for-your-enterprise#restricting-email-notifications-for-your-enterprise-account)." - - - heading: 'Git Credential Manager (GCM) secure credential storage and multi-factor authentication support' - notes: - # https://github.com/github/releases/issues/1406 - - | - Git Credential Manager (GCM) versions 2.0.452 and later now provide security-hardened credential storage and multi-factor authentication support for {% data variables.product.product_name %}. - - GCM with support for {% data variables.product.product_name %} is included with [Git for Windows](https://gitforwindows.org) versions 2.32 and later. GCM is not included with Git for macOS or Linux, but can be installed separately. For more information, see the [latest release](https://github.com/GitCredentialManager/git-credential-manager/releases/) and [installation instructions](https://github.com/GitCredentialManager/git-credential-manager/releases/) in the `GitCredentialManager/git-credential-manager` repository. - - changes: - - heading: Administration Changes - notes: - # https://github.com/github/releases/issues/1309 - - A 'User Agent Referrer Policy' setting has been added to the enterprise settings. This allows an admin to set a stricter `Referrer-Policy` to hide the hostname of a {% data variables.product.prodname_ghe_server %} installation from external sites. The setting is disabled by default and is tracked by audit log events for staff and enterprise owners when enabled or disabled. For more information, see "[Configuring Referrer Policy for your enterprise](/admin/configuration/configuring-your-enterprise/configuring-the-referrer-policy-for-your-enterprise)." - - # https://github.com/github/releases/issues/1515 - - The MySQL health check was changed to use `mysqladmin ping` instead of TCP checks, which removes some unnecessary noise in the MySQL error log. Also, Orchestrator failover checks were improved to prevent unnecessary MySQL failovers when applying cluster config changes. - - # https://github.com/github/releases/issues/1287 - - The Resque service, which supports background job processing, has been replaced with Aqueduct Lite. This change makes the job system easier to manage and should not affect the user experience. For the new administration and debugging commands for Aqueduct, see "[Command-line utilities](/admin/configuration/configuring-your-enterprise/command-line-utilities#ghe-aqueduct)." - - - heading: Token Changes - notes: - # https://github.com/github/releases/issues/1235 - - | - The format of authentication tokens for {% data variables.product.product_name %} has changed. The change affects the format of personal access tokens and access tokens for {% data variables.product.prodname_oauth_apps %}, as well as user-to-server, server-to-server, and refresh tokens for {% data variables.product.prodname_github_apps %}. - - The different token types now have unique identifiable prefixes, which allows for secret scanning to detect the tokens so that you can mitigate the impact of someone accidentally committing a token to a repository. {% data variables.product.company_short %} recommends updating existing tokens as soon as possible. For more information, see "[About authentication to {% data variables.product.prodname_dotcom %}](/github/authenticating-to-github/keeping-your-account-and-data-secure/about-authentication-to-github#githubs-token-formats)" and "[About {% data variables.product.prodname_secret_scanning %}](/code-security/secret-security/about-secret-scanning)." - - - heading: 'Repositories changes' - notes: - # https://github.com/github/releases/issues/1295 - - Repositories on user profiles and organization profiles now support sorting by star count. - - # https://github.com/github/releases/issues/1327 - - When viewing the commit history of a single file, you can now click {% octicon "file-code" aria-label="The code icon" %} to view that file at the selected point in history. - - # https://github.com/github/releases/issues/1254 - - When a submodule is defined with a relative path in {% data variables.location.product_location %}, the submodule is now clickable in the web UI. Clicking the submodule in the web UI will take you to the linked repository. Previously, only submodules with absolute URLs were clickable. This is supported for relative paths for repositories with the same owner that follow the pattern ../REPOSITORY or relative paths for repositories with a different owner that follow the pattern ../OWNER/REPOSITORY. For more information about working with submodules, see [Working with submodules](https://github.blog/2016-02-01-working-with-submodules/) on {% data variables.product.prodname_blog %}. - - # https://github.com/github/releases/issues/1250 - - The web UI can now be used to synchronize an out-of-date branch of a fork with the fork's upstream branch. If there are no merge conflicts between the branches, the branch is updated either by fast-forwarding or by merging from upstream. If there are conflicts, you will be prompted to create a pull request to resolve the conflicts. For more information, see "[Syncing a fork](/github/collaborating-with-pull-requests/working-with-forks/syncing-a-fork#syncing-a-fork-from-the-web-ui)." - - - heading: 'Markdown changes' - notes: - # https://github.com/github/releases/issues/1477 - - 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).' diff --git a/translations/es-ES/data/release-notes/enterprise-server/3-2/0.yml b/translations/es-ES/data/release-notes/enterprise-server/3-2/0.yml deleted file mode 100644 index 708b798394..0000000000 --- a/translations/es-ES/data/release-notes/enterprise-server/3-2/0.yml +++ /dev/null @@ -1,317 +0,0 @@ -date: '2021-09-28' -intro: For upgrade instructions, see "[Upgrading {% data variables.product.prodname_ghe_server %}](/admin/enterprise-management/updating-the-virtual-machine-and-physical-resources/upgrading-github-enterprise-server)." -sections: - features: - - heading: Custom patterns for secret scanning - notes: - # https://github.com/github/releases/issues/1426 - - | - {% data variables.product.prodname_GH_advanced_security %} customers can now specify custom patterns for secret scanning. When a new pattern is specified, secret scanning searches a repository's entire Git history for the pattern, as well as any new commits. - - User defined patterns are in beta for {% data variables.product.prodname_ghe_server %} 3.2. They can be defined at the repository, organization, and enterprise levels. For more information, see "[Defining custom patterns for secret scanning](/code-security/secret-scanning/defining-custom-patterns-for-secret-scanning)." - - - heading: Security overview for Advanced Security (beta) - notes: - # https://github.com/github/releases/issues/1381 - - | - {% data variables.product.prodname_GH_advanced_security %} customers now have an organization-level view of the application security risks detected by {% data variables.product.prodname_code_scanning %}, {% data variables.product.prodname_dependabot %}, and {% data variables.product.prodname_secret_scanning %}. The security overview shows the enablement status of security features on each repository, as well as the number of alerts detected. - - In addition, the security overview lists all {% data variables.product.prodname_secret_scanning %} alerts at the organization level. Similar views for {% data variables.product.prodname_dependabot %} and {% data variables.product.prodname_code_scanning %} alerts are coming in future releases. For more information, see "[About the security overview](/code-security/security-overview/about-the-security-overview)." - - ![Screenshot of security overview](/assets/images/enterprise/3.2/release-notes/security-overview-UI.png) - - - heading: Dependency review (beta) - notes: - # https://github.com/github/releases/issues/1364 - - | - {% data variables.product.prodname_GH_advanced_security %} customers can now see a rich diff of the dependencies changed in a pull request. 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 these dependencies. 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)." - - - heading: GitHub Actions environments - notes: - # https://github.com/github/releases/issues/1308 - - | - Environments, environment protection rules, and environment secrets are now generally available for {% data variables.product.prodname_actions %} on {% data variables.product.product_name %}. For more information, see "[Environments](/actions/reference/environments)." - - ![Environment protection rules](/assets/images/enterprise/3.2/release-notes/actions-environments.png) - - - heading: SSH authentication with security keys - notes: - # https://github.com/github/releases/issues/1276 - - | - SSH authentication using a FIDO2 security key is now supported when you add a `sk-ecdsa-sha2-nistp256@openssh.com` or `sk-ssh-ed25519@openssh.com` SSH key to your account. SSH security keys store secret key material on a separate hardware device that requires verification, such as a tap, to operate. For more information, see "[Generating a new SSH key and adding it to the ssh-agent](/github/authenticating-to-github/connecting-to-github-with-ssh/generating-a-new-ssh-key-and-adding-it-to-the-ssh-agent#generating-a-new-ssh-key-for-a-hardware-security-key)." - - - heading: 'Dark and dark dimmed themes' - notes: - # https://github.com/github/releases/issues/1260 - - | - Dark and dark dimmed themes are now available for the web UI. {% data variables.product.product_name %} will match your system preferences when you haven't set theme preferences in {% data variables.product.product_name %}. You can also choose which themes are active during the day and night. For more information, see "[Managing your theme settings](/github/setting-up-and-managing-your-github-user-account/managing-user-account-settings/managing-your-theme-settings)." - - ![Dark and dark dimmed themes](https://user-images.githubusercontent.com/33528647/114629560-d2231f80-9c86-11eb-9bde-cc301a97040d.gif) - - - heading: 'Approving unverified domains for email notifications' - notes: - # https://github.com/github/releases/issues/1244 - - Domains that are not able to be verified can now be approved for email notification routing. Enterprise and organization owners will be able to approve domains and immediately augment their email notification restriction policy, allowing notifications to be sent to collaborators, consultants, acquisitions, or other partners. For more information, see "[Verifying or approving a domain for your enterprise](/admin/configuration/configuring-your-enterprise/verifying-or-approving-a-domain-for-your-enterprise#about-approval-of-domains)" and "[Restricting email notifications for your enterprise](/admin/policies/enforcing-policies-for-your-enterprise/restricting-email-notifications-for-your-enterprise#restricting-email-notifications-for-your-enterprise-account)." - - - heading: 'Git Credential Manager (GCM) secure credential storage and multi-factor authentication support' - notes: - # https://github.com/github/releases/issues/1406 - - | - Git Credential Manager (GCM) versions 2.0.452 and later now provide security-hardened credential storage and multi-factor authentication support for {% data variables.product.product_name %}. - - GCM with support for {% data variables.product.product_name %} is included with [Git for Windows](https://gitforwindows.org) versions 2.32 and later. GCM is not included with Git for macOS or Linux, but can be installed separately. For more information, see the [latest release](https://github.com/GitCredentialManager/git-credential-manager/releases/) and [installation instructions](https://github.com/GitCredentialManager/git-credential-manager/releases/) in the `GitCredentialManager/git-credential-manager` repository. - - changes: - - heading: Administration Changes - notes: - # https://github.com/github/releases/issues/1309 - - A 'User Agent Referrer Policy' setting has been added to the enterprise settings. This allows an admin to set a stricter `Referrer-Policy` to hide the hostname of a {% data variables.product.prodname_ghe_server %} installation from external sites. The setting is disabled by default and is tracked by audit log events for staff and enterprise owners when enabled or disabled. For more information, see "[Configuring Referrer Policy for your enterprise](/admin/configuration/configuring-your-enterprise/configuring-the-referrer-policy-for-your-enterprise)." - - # https://github.com/github/releases/issues/1515 - - The MySQL health check was changed to use `mysqladmin ping` instead of TCP checks, which removes some unnecessary noise in the MySQL error log. Also, Orchestrator failover checks were improved to prevent unnecessary MySQL failovers when applying cluster config changes. - - # https://github.com/github/releases/issues/1287 - - The Resque service, which supports background job processing, has been replaced with Aqueduct Lite. This change makes the job system easier to manage and should not affect the user experience. For the new administration and debugging commands for Aqueduct, see "[Command-line utilities](/admin/configuration/configuring-your-enterprise/command-line-utilities#ghe-aqueduct)." - - - heading: Token Changes - notes: - # https://github.com/github/releases/issues/1235 - - | - The format of authentication tokens for {% data variables.product.product_name %} has changed. The change affects the format of personal access tokens and access tokens for {% data variables.product.prodname_oauth_apps %}, as well as user-to-server, server-to-server, and refresh tokens for {% data variables.product.prodname_github_apps %}. - - The different token types now have unique identifiable prefixes, which allows for secret scanning to detect the tokens so that you can mitigate the impact of someone accidentally committing a token to a repository. {% data variables.product.company_short %} recommends updating existing tokens as soon as possible. For more information, see "[About authentication to {% data variables.product.prodname_dotcom %}](/github/authenticating-to-github/keeping-your-account-and-data-secure/about-authentication-to-github#githubs-token-formats)" and "[About {% data variables.product.prodname_secret_scanning %}](/code-security/secret-security/about-secret-scanning)." - - - heading: 'Repositories changes' - notes: - # https://github.com/github/releases/issues/1295 - - Repositories on user profiles and organization profiles now support sorting by star count. - - # https://github.com/github/releases/issues/1327 - - When viewing the commit history of a single file, you can now click {% octicon "file-code" aria-label="The code icon" %} to view that file at the selected point in history. - - # https://github.com/github/releases/issues/1254 - - When a submodule is defined with a relative path in {% data variables.location.product_location %}, the submodule is now clickable in the web UI. Clicking the submodule in the web UI will take you to the linked repository. Previously, only submodules with absolute URLs were clickable. This is supported for relative paths for repositories with the same owner that follow the pattern ../REPOSITORY or relative paths for repositories with a different owner that follow the pattern ../OWNER/REPOSITORY. For more information about working with submodules, see [Working with submodules](https://github.blog/2016-02-01-working-with-submodules/) on {% data variables.product.prodname_blog %}. - - # https://github.com/github/releases/issues/1250 - - The web UI can now be used to synchronize an out-of-date branch of a fork with the fork's upstream branch. If there are no merge conflicts between the branches, the branch is updated either by fast-forwarding or by merging from upstream. If there are conflicts, you will be prompted to create a pull request to resolve the conflicts. For more information, see "[Syncing a fork](/github/collaborating-with-pull-requests/working-with-forks/syncing-a-fork#syncing-a-fork-from-the-web-ui)." - - - heading: 'Markdown changes' - notes: - # https://github.com/github/releases/issues/1477 - - 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).' diff --git a/translations/es-ES/data/release-notes/enterprise-server/3-2/1.yml b/translations/es-ES/data/release-notes/enterprise-server/3-2/1.yml deleted file mode 100644 index 4ab6caeaca..0000000000 --- a/translations/es-ES/data/release-notes/enterprise-server/3-2/1.yml +++ /dev/null @@ -1,28 +0,0 @@ -date: '2021-10-12' -sections: - security_fixes: - - 'Los paquetes se han actualizado a sus últimas versiones de seguridad. {% comment %} https://github.com/github/enterprise2/pull/27118, https://github.com/github/enterprise2/pull/27110 {% endcomment %}' - bugs: - - 'Los enlaces previos a la recepción personalizados podrían haber fallado debido a los límites demasiado restrictivos en la memoria virtual o CPU.{% comment %} https://github.com/github/enterprise2/pull/26973, https://github.com/github/enterprise2/pull/26955 {% endcomment %}' - - 'En una configuración de agrupación de servidores de GitHub Enterprise, la configuración del gráfico de dependencias podría haberse aplicado incorrectamente. {% comment %} https://github.com/github/enterprise2/pull/26981, https://github.com/github/enterprise2/pull/26861 {% endcomment %}' - - 'El intento de borrar todos los ajustes de configuración existentes con "ghe-cleanup-settings" no pudo reiniciar el servicio de la consola de administración. {% comment %} https://github.com/github/enterprise2/pull/26988, https://github.com/github/enterprise2/pull/26901 {% endcomment %}' - - 'Durante el desmontaje de replicación mediante "ghe-repl-teardown", Memcached no pudo reiniciarse. {% comment %} https://github.com/github/enterprise2/pull/26994, https://github.com/github/enterprise2/pull/26983 {% endcomment %}' - - 'Durante los periodos de carga alta, los usuarios recibían códigos de estado HTTP 503 cuando los servicios ascendentes no superaban las comprobaciones de estado internas. {% comment %} https://github.com/github/enterprise2/pull/27083, https://github.com/github/enterprise2/pull/26999 {% endcomment %}' - - 'Se prohibió que los entornos de los enlaces previos a la recepción llamaran al comando cat a través de BusyBox en Alpine.{% comment %} https://github.com/github/enterprise2/pull/27116, https://github.com/github/enterprise2/pull/27094 {% endcomment %}' - - 'La conmutación por error desde un centro de datos de un clúster primario hacia un centro de datos de un clúster secundario se realizaba correctamente, pero la conmutación por error de nuevo al centro de datos del clúster primario original no podía promover los índices de Elasticsearch. {% comment %} https://github.com/github/github/pull/193182, https://github.com/github/github/pull/192447 {% endcomment %}' - - 'El botón "Importar equipos" de la página de Teams de una organización devolvía un HTTP 404. {% comment %} https://github.com/github/github/pull/193303 {% endcomment %}' - - 'El uso de la API para inhabilitar el análisis de secretos deshabilitaba correctamente la propiedad, pero devolvía incorrectamente un HTTP 422 y un mensaje de error. {% comment %} https://github.com/github/github/pull/193455, https://github.com/github/github/pull/192907 {% endcomment %}' - - 'En algunos casos, los administradores de GitHub Enterprise que intentaban ver la página de "Usuarios inactivos" recibían una respuesta del tipo "502 Puerta de enlace incorrecta" o "504 Se agotó el tiempo de espera de la puerta de enlace". {% comment %} https://github.com/github/github/pull/194262, https://github.com/github/github/pull/193609 {% endcomment %}' - - 'Se produjo un impacto negativo en el rendimiento en algunas situaciones de carga alta como resultado del aumento en la cantidad de trabajos "SynchronizePullRequestJob". {% comment %} https://github.com/github/github/pull/195256, https://github.com/github/github/pull/194591 {% endcomment %}' - - 'Un patrón definido por el usuario creado para el análisis de secretos se seguía analizando incluso después de haberse eliminado. {% comment %} https://github.com/github/token-scanning-service/pull/1039, https://github.com/github/token-scanning-service/pull/822 {% endcomment %}' - changes: - - 'Las aplicaciones de GitHub ahora configuran la característica de análisis de secretos en un repositorio de manera coherente con la API. {% comment %} https://github.com/github/github/pull/193456, https://github.com/github/github/pull/193125 {% endcomment %}' - known_issues: - - 'En una instalación nueva de {% data variables.product.prodname_ghe_server %} que no tenga ningún usuario, un atacante podría crear el primer usuario administrador.' - - 'Las reglas de cortafuegos personalizadas se eliminan durante el proceso de actualización.' - - 'Los archivos supervisados de Git LFS [cargados desde la interfaz web](https://github.com/blog/2105-upload-files-to-your-repositories) se agregan de manera incorrecta y directa al repositorio.' - - "Las incidencias no se pueden cerrar si contienen un enlace permanente a un blob del mismo repositorio en el que la ruta es mayor de 255\_caracteres." - - 'Cuando se habilita "Los usuarios pueden buscar en GitHub.com" con GitHub Connect, las incidencias en los repositorios privados e internos no se incluyen en los resultados de la búsqueda de GitHub.com.' - - 'El registro npm de {% data variables.product.prodname_registry %} ya no devuelve un valor de hora en las respuestas de metadatos. Esto se hacía para permitir mejoras de rendimiento importantes. Seguimos teniendo todos los datos necesarios para devolver un valor de tiempo como parte de la respuesta de metadatos y reanudaremos la devolución de este valor en el futuro una vez que hayamos resuelto las incidencias de rendimiento existentes.' - - 'Los límites de recursos que son específicos para procesar enlaces previos a la recepción podrían ocasionar errores en algunos de ellos.' - - '{% data reusables.release-notes.ghas-3.4-secret-scanning-known-issue %}' diff --git a/translations/es-ES/data/release-notes/enterprise-server/3-2/10.yml b/translations/es-ES/data/release-notes/enterprise-server/3-2/10.yml deleted file mode 100644 index c5b10412c6..0000000000 --- a/translations/es-ES/data/release-notes/enterprise-server/3-2/10.yml +++ /dev/null @@ -1,16 +0,0 @@ -date: '2022-03-01' -sections: - security_fixes: - - "RIESGO ALTO: se identificó una vulnerabilidad de desbordamiento de entero en el analizador de Markdown de GitHub que potencialmente podía causar filtraciones de información y RCE. Felix Wilhelm de Project Zero de Google informó de esta vulnerabilidad mediante el programa Bug Bounty de GitHub y se le asignó CVE-2022-24724." - bugs: - - "A veces, las actualizaciones podían producir errores si un reloj de réplica de alta disponibilidad no estaba sincronizado con el principal." - - "Las aplicaciones de OAuth creadas después del 1 de septiembre de 2020 no podían usar el punto de conexión de la API [Comprobación de una autorización](https://docs.github.com/en/enterprise-server@3.2/rest/reference/apps#check-an-authorization)." - known_issues: - - "En una instancia recién configurada de {% data variables.product.prodname_ghe_server %} sin ningún usuario, un atacante podría crear el primer usuario administrador." - - Las reglas de cortafuegos personalizadas se eliminan durante el proceso de actualización. - - "Los archivos supervisados de Git LFS [cargados desde la interfaz web](https://github.com/blog/2105-upload-files-to-your-repositories) se agregan de manera incorrecta y directa al repositorio." - - Las incidencias no se pueden cerrar si contienen un enlace permanente a un blob del mismo repositorio en el que la ruta es mayor de 255 caracteres. - - "Cuando se habilita \"Los usuarios pueden buscar en GitHub.com\" con GitHub Connect, las incidencias en los repositorios privados e internos no se incluyen en los resultados de la búsqueda de GitHub.com." - - "El registro npm de {% data variables.product.prodname_registry %} ya no devuelve un valor de hora en las respuestas de metadatos. Esto se hacía para permitir mejoras de rendimiento importantes. Seguimos teniendo todos los datos necesarios para devolver un valor de tiempo como parte de la respuesta de metadatos y reanudaremos la devolución de este valor en el futuro una vez que hayamos resuelto las incidencias de rendimiento existentes." - - Los límites de recursos que son específicos para procesar enlaces previos a la recepción podrían ocasionar errores en algunos de ellos. - - '{% data reusables.release-notes.ghas-3.4-secret-scanning-known-issue %}' diff --git a/translations/es-ES/data/release-notes/enterprise-server/3-2/11.yml b/translations/es-ES/data/release-notes/enterprise-server/3-2/11.yml deleted file mode 100644 index 26cab8f345..0000000000 --- a/translations/es-ES/data/release-notes/enterprise-server/3-2/11.yml +++ /dev/null @@ -1,44 +0,0 @@ -date: '2022-04-04' -sections: - security_fixes: - - 'MEDIA: Se ha identificado una vulnerabilidad de recorrido de ruta en la consola de administración de {% data variables.product.prodname_ghe_server %} que permitía la omisión de las protecciones contra CSRF. Esta vulnerabilidad afectó a todas las versiones de {% data variables.product.prodname_ghe_server %} anteriores a la 3.5 y se corrigió en las versiones 3.1.19, 3.2.11, 3.3.6 y 3.4.1. Esta vulnerabilidad se notificó a través del programa de recompensas de {% data variables.product.prodname_dotcom %} por la detección de errores y se le ha asignado CVE-2022-23732.' - - 'MEDIA: Se ha identificado una vulnerabilidad de desbordamiento de enteros en la rama 1.x y la rama 2.x de "yajil" que posteriormente provoca daños en la memoria de montón al tratar con entradas grandes (~2GB). Esta vulnerabilidad se notificó de forma interna y se le ha asignado CVE-2022-24795. ' - - "Los conjuntos de soporte técnico podrían incluir archivos confidenciales si {% data variables.product.prodname_actions %} estuviera habilitada." - - Los paquetes se actualizaron a las últimas versiones de seguridad. - bugs: - - "Los procesos de MinIO tendrían un uso elevado de CPU si una opción de configuración anterior estuviera presente tras actualizar {% data variables.product.prodname_ghe_server %}." - - "Se mostraron las opciones para habilitar \"TLS 1.0\" y \"TLS 1.1\" en la configuración de privacidad de la consola de administración, aunque la eliminación de esas versiones de protocolo se produjo en una versión anterior." - - "En un entorno de alta disponibilidad, configurar la replicación de MSSQL podría requerir pasos manuales adicionales tras habilitar {% data variables.product.prodname_actions %} por primera vez." - - Un subconjunto de archivos de configuración interna se actualizan de forma más confiable tras una revisión en caliente. - - "Habría ocasiones en las que el script \"ghe-run-migrations\" no generaría nombres de certificados temporales correctamente." - - "En un entorno de clúster, podría producirse un error en las operaciones de Git LFS con llamadas API internas fallidas que cruzaran varios nodos web." - - "Se agotó el tiempo de espera de los enlaces de recepción previa que usaron \"gpg --import\" debido a la insuficiencia de privilegios \"syscall\"." - - "En algunas topologías de clúster, la información de entrega de webhook no estaba disponible." - - "En las configuraciones de alta disponibilidad, no se anularía ninguna réplica si {% data variables.product.prodname_actions %} se hubiera habilitado anteriormente." - - Las comprobaciones de estado de Elasticsearch no permitirían un estado del clúster amarillo al ejecutar migraciones. - - Las organizaciones creadas como resultado de un usuario que transforma su cuenta de usuario en una organización no se agregaron a la cuenta empresarial global. - - "Al usar \"ghe-migrator\" o exportar desde {% data variables.product.prodname_dotcom_the_website %}, se produciría un error en una exportación de larga duración al eliminarse los datos en mitad de la exportación." - - "Se mostraría un error en el grafo de implementación de {% data variables.product.prodname_actions %} al representar un trabajo pendiente." - - Los vínculos a páginas inaccesibles se han eliminado. - - Salir de una comparación de dos confirmaciones en la interfaz de usuario web haría que la diferencia persistiera en otras páginas. - - Al agregar un equipo como revisor a una solicitud de incorporación de cambios se mostraría en ocasiones el número incorrecto de miembros de ese equipo. - - "El [Quitar la pertenencia a un equipo de un usuario](/rest/reference/teams#remove-team-membership-for-a-user) punto de conexión de API respondería con un error al intentar quitar un miembro administrado de forma externa por un grupo de SCIM." - - "Un número elevado de usuarios inactivos podría hacer que se produjera un error en una configuración de {% data variables.product.prodname_github_connect %}." - - La página de inscripciones a características y beta de la interfaz de usuario web de administración del sitio no estaba correctamente disponible. - - El vínculo del modo de administrador del sitio del pie de página del sitio no cambió el estado al hacer clic. - - 'Ya no se produce ningún error en el comando "spokesctl cache-policy rm" con el mensaje "error: failed to delete cache policy".' - changes: - - Los límites de conexión Memcached aumentaron para adaptarse mejor a topologías de clúster de gran tamaño. - - Dependency Graph API se ejecutaba anteriormente con un puerto definido estáticamente. - - Se han actualizado los recuentos de particiones predeterminados para la configuración de particiones de Elasticsearch relacionada con el clúster. - - Los roles de evaluación de prioridades y de mantenimiento de los equipos se conservan durante las migraciones de repositorio. - - Se ha mejorado el rendimiento de las solicitudes web realizadas por propietarios empresariales. - known_issues: - - "En una instancia recién configurada de {% data variables.product.prodname_ghe_server %} sin ningún usuario, un atacante podría crear el primer usuario administrador." - - Las reglas de firewall personalizadas se eliminan durante el proceso de actualización. - - "Los archivos supervisados de Git LFS [cargados desde la interfaz web](https://github.com/blog/2105-upload-files-to-your-repositories) se han agregado de manera incorrecta y directa al repositorio." - - Las incidencias no se pueden cerrar si contienen un vínculo permanente a un blob en el mismo repositorio en el que la ruta de acceso de archivo del blob tiene más de 255 caracteres. - - "Cuando se habilita \"Los usuarios pueden buscar en GitHub.com\" con {% data variables.product.prodname_github_connect %}, las incidencias en los repositorios privados e internos no se incluyen en los resultados de búsqueda de {% data variables.product.prodname_dotcom_the_website %}." - - "El registro npm de {% data variables.product.prodname_registry %} ya no devuelve un valor de tiempo en las respuestas de metadatos. Esto se hacía para permitir mejoras de rendimiento importantes. Seguimos teniendo todos los datos necesarios para devolver un valor de tiempo como parte de la respuesta de metadatos y reanudaremos la devolución de este valor en el futuro una vez que hayamos resuelto las incidencias de rendimiento existentes." - - Los límites de recursos que son específicos para procesar enlaces de recepción previa podrían ocasionar errores en algunos de ellos. - - '{% data reusables.release-notes.ghas-3.4-secret-scanning-known-issue %}' diff --git a/translations/es-ES/data/release-notes/enterprise-server/3-2/12.yml b/translations/es-ES/data/release-notes/enterprise-server/3-2/12.yml deleted file mode 100644 index 9bdc5f7b71..0000000000 --- a/translations/es-ES/data/release-notes/enterprise-server/3-2/12.yml +++ /dev/null @@ -1,24 +0,0 @@ -date: '2022-04-20' -sections: - security_fixes: - - 'Los paquetes se han actualizado a las últimas versiones de seguridad.' - bugs: - - 'La actualización de los nodos en un par de alta disponibilidad con un paquete de actualización podía hacer que Elasticsearch entrara en un estado incoherente en algunos casos.' - - 'En algunas topologías de clúster, las utilidades de la línea de comandos "ghe-spokesctl" y "ghe-btop" no se ejecutaban.' - - 'Los índices de Elasticsearch podían duplicarse durante una actualización de paquetes debido a la ejecución de un servicio "elasticsearch-upgrade" varias veces en paralelo.' - - 'Al convertir una cuenta de usuario en una organización, si la cuenta de usuario era propietaria de la cuenta de empresa de {% data variables.product.prodname_ghe_server %}, la organización convertida aparecía de forma incorrecta en la lista de propietarios de la empresa.' - - 'La creación de un token de OAuth de suplantación mediante la API de REST de administración empresarial funcionaba de forma incorrecta cuando ya existía una integración coincidente con el identificador de aplicación de OAuth.' - changes: - - 'Los errores de configuración que detienen una ejecución de aplicación de configuración ahora se envían al terminal, además del registro de configuración.' - - 'Al intentar copiar en caché un valor más grande que el máximo permitido por Memcached, se producía un error, pero no se notificaba la clave.' - - 'El flujo de trabajo de iniciador de {% data variables.product.prodname_codeql %} ya no produce errores incluso aunque no se usen los permisos de token predeterminados para {% data variables.product.prodname_actions %}.' - - 'Si las características de {% data variables.product.prodname_GH_advanced_security %} están habilitadas en tu instancia, el rendimiento de los trabajos en segundo plano ha mejorado al procesar lotes para las contribuciones al repositorio.' - known_issues: - - 'En una instancia recién configurada de {% data variables.product.prodname_ghe_server %} sin ningún usuario, un atacante podría crear el primer usuario administrador.' - - 'Las reglas de cortafuegos personalizadas se eliminan durante el proceso de actualización.' - - 'Los archivos supervisados de Git LFS [cargados desde la interfaz web](https://github.com/blog/2105-upload-files-to-your-repositories) se agregan de manera incorrecta y directa al repositorio.' - - "Las incidencias no se pueden cerrar si contienen un enlace permanente a un blob del mismo repositorio en el que la ruta es mayor de 255\_caracteres." - - 'Cuando se habilita "Los usuarios pueden buscar en GitHub.com" con {% data variables.product.prodname_github_connect %}, las incidencias en los repositorios privados e internos no se incluyen en los resultados de búsqueda de {% data variables.product.prodname_dotcom_the_website %}.' - - 'El registro npm de {% data variables.product.prodname_registry %} ya no devuelve un valor de hora en las respuestas de metadatos. Esto se hacía para permitir mejoras de rendimiento importantes. Seguimos teniendo todos los datos necesarios para devolver un valor de tiempo como parte de la respuesta de metadatos y reanudaremos la devolución de este valor en el futuro una vez que hayamos resuelto las incidencias de rendimiento existentes.' - - 'Los límites de recursos que son específicos para procesar enlaces previos a la recepción podrían ocasionar errores en algunos de ellos.' - - '{% data reusables.release-notes.ghas-3.4-secret-scanning-known-issue %}' diff --git a/translations/es-ES/data/release-notes/enterprise-server/3-2/13.yml b/translations/es-ES/data/release-notes/enterprise-server/3-2/13.yml deleted file mode 100644 index e5725baf3e..0000000000 --- a/translations/es-ES/data/release-notes/enterprise-server/3-2/13.yml +++ /dev/null @@ -1,28 +0,0 @@ -date: '2022-05-17' -sections: - security_fixes: - - '**MEDIA:** Se ha identificado una incidencia de seguridad en el solucionador nginx, por la que un atacante que puede falsificar paquetes UDP del servidor DNS puede dar lugar a una sobrescritura de memoria de 1 byte, lo que hace que se bloquee el proceso de trabajo o provoca otros impactos potencialmente perjudiciales. Se ha asignado la vulnerabilidad [CVE-2021-23017](https://nvd.nist.gov/vuln/detail/CVE-2021-23017).' - - "Se han actualizado las acciones \"actions/checkout@v2\" y \"actions/checkout@v3\" para resolver nuevas vulnerabilidades anunciadas en la [entrada de blog sobre el cumplimiento de la seguridad de Git](https://github.blog/2022-04-12-git-security-vulnerability-announced/)." - - Los paquetes se actualizaron a las últimas versiones de seguridad. - bugs: - - "En algunas topologías de clúster, el comando \"ghe-cluster-status\" generó directorios vacíos en \"/tmp\"." - - "Protocolo simple de administración de redes registró incorrectamente un gran número de mensajes de error \"Cannot statfs\" en syslog." - - "En el caso de las instancias configuradas con la autenticación SAML y la reserva integrada habilitada, los usuarios integrados se quedarían bloqueados en un bucle de \"inicio de sesión\" al tratar de iniciar sesión desde la página generada después de cerrar la sesión." - - Los vídeos cargados para emitir comentarios no se representarían correctamente. - - "Al usar aserciones cifradas SAML, algunas aserciones no marcaban correctamente las claves SSH como comprobadas." - - "Al usar \"ghe-migrator\", una migración produciría un error al importar datos adjuntos de archivos de vídeo en incidencias y solicitudes de incorporación de cambios." - - 'La página Versiones devolvería un error 500 si el repositorio tuviera etiquetas con caracteres no ASCII. [Actualizado: 2022-06-10]' - changes: - - "En el caso de las configuraciones de alta disponibilidad, deja claro que en la página de información general de replicación de la consola de administración solo se muestra la configuración de replicación actual, no el estado de replicación actual." - - "Al habilitar {% data variables.product.prodname_registry %}, deja claro que usar un token de firma de acceso compartido (SAS) como cadena de conexión no se admite actualmente." - - Los conjuntos de soporte técnico ahora incluyen el recuento de filas de las tablas almacenadas en MySQL. - - "El gráfico de dependencias ahora se puede habilitar sin datos de vulnerabilidad, permitiéndote ver las dependencias que se encuentran en uso y en qué versiones. Habilitar el gráfico de dependencias sin habilitar {% data variables.product.prodname_github_connect %} **no** proporcionará información de vulnerabilidad." - known_issues: - - "En una instancia recién configurada de {% data variables.product.prodname_ghe_server %} sin ningún usuario, un atacante podría crear el primer usuario administrador." - - Las reglas de firewall personalizadas se eliminan durante el proceso de actualización. - - "Los archivos supervisados de Git LFS [cargados desde la interfaz web](https://github.com/blog/2105-upload-files-to-your-repositories) se han agregado de manera incorrecta y directa al repositorio." - - Las incidencias no se pueden cerrar si contienen un vínculo permanente a un blob en el mismo repositorio en el que la ruta de acceso de archivo del blob tiene más de 255 caracteres. - - "Cuando se habilita \"Los usuarios pueden buscar en GitHub.com\" con {% data variables.product.prodname_github_connect %}, las incidencias en los repositorios privados e internos no se incluyen en los resultados de búsqueda de {% data variables.product.prodname_dotcom_the_website %}." - - "El registro npm de {% data variables.product.prodname_registry %} ya no devuelve un valor de tiempo en las respuestas de metadatos. Esto se hacía para permitir mejoras de rendimiento importantes. Seguimos teniendo todos los datos necesarios para devolver un valor de tiempo como parte de la respuesta de metadatos y reanudaremos la devolución de este valor en el futuro una vez que hayamos resuelto las incidencias de rendimiento existentes." - - Los límites de recursos que son específicos para procesar enlaces de recepción previa podrían ocasionar errores en algunos de ellos. - - '{% data reusables.release-notes.ghas-3.4-secret-scanning-known-issue %}' diff --git a/translations/es-ES/data/release-notes/enterprise-server/3-2/14.yml b/translations/es-ES/data/release-notes/enterprise-server/3-2/14.yml deleted file mode 100644 index 7cf4278916..0000000000 --- a/translations/es-ES/data/release-notes/enterprise-server/3-2/14.yml +++ /dev/null @@ -1,23 +0,0 @@ -date: '2022-06-09' -sections: - security_fixes: - - 'Los paquetes se han actualizado a las últimas versiones de seguridad.' - bugs: - - 'Un script interno para validar nombres de host en el archivo de configuración {% data variables.product.prodname_ghe_server %} devolvería un error si la cadena del nombre de host comenzara por "." (carácter de punto).' - - 'En configuraciones de alta disponibilidad en las que el nombre de host del nodo principal tenía más de 60 caracteres, no se podía configurar MySQL.' - - 'Se agregó el argumento "--gateway" al comando "ghe-setup-network" para permitir pasar la dirección de la puerta de enlace al configurar los ajustes de red mediante la línea de comandos.' - - 'Los datos adjuntos de imagen que se eliminaban devolvían un error "500 Error de servidor interno" en lugar de un "404 No encontrado".' - - 'El cálculo de "confirmadores máximos en toda la instancia" notificado en el panel de administración del sitio era incorrecto.' - - 'Una entrada de base de datos incorrecta para las réplicas del repositorio provocó daños en la base de datos al realizar una restauración mediante {% data variables.product.prodname_enterprise_backup_utilities %}.' - changes: - - 'Se optimizó la inclusión de métricas al generar un conjunto de soporte del clúster.' - - 'En las configuraciones de alta disponibilidad donde Elasticsearch notificaba un estado amarillo válido, los cambios introducidos en una corrección anterior bloqueaban el comando "ghe-repl-stop" y no permitían que se detuviera la replicación. El uso de "ghe-repo-stop --force" ahora exigirá la detención de Elasticsearch cuando el servicio se encuentre en un estado amarillo normal o válido.' - known_issues: - - 'En una instancia recién configurada de {% data variables.product.prodname_ghe_server %} sin ningún usuario, un atacante podría crear el primer usuario administrador.' - - 'Las reglas de cortafuegos personalizadas se eliminan durante el proceso de actualización.' - - 'Los archivos supervisados de Git LFS [cargados desde la interfaz web](https://github.com/blog/2105-upload-files-to-your-repositories) se agregan de manera incorrecta y directa al repositorio.' - - "Las incidencias no se pueden cerrar si contienen un enlace permanente a un blob del mismo repositorio en el que la ruta es mayor de 255\_caracteres." - - 'Cuando se habilita "Los usuarios pueden buscar en GitHub.com" con {% data variables.product.prodname_github_connect %}, las incidencias en los repositorios privados e internos no se incluyen en los resultados de búsqueda de {% data variables.product.prodname_dotcom_the_website %}.' - - 'El registro npm de {% data variables.product.prodname_registry %} ya no devuelve un valor de hora en las respuestas de metadatos. Esto se hacía para permitir mejoras de rendimiento importantes. Seguimos teniendo todos los datos necesarios para devolver un valor de tiempo como parte de la respuesta de metadatos y reanudaremos la devolución de este valor en el futuro una vez que hayamos resuelto las incidencias de rendimiento existentes.' - - 'Los límites de recursos que son específicos para procesar enlaces previos a la recepción podrían ocasionar errores en algunos de ellos.' - - '{% data reusables.release-notes.ghas-3.4-secret-scanning-known-issue %}' diff --git a/translations/es-ES/data/release-notes/enterprise-server/3-2/15.yml b/translations/es-ES/data/release-notes/enterprise-server/3-2/15.yml deleted file mode 100644 index 12016900a8..0000000000 --- a/translations/es-ES/data/release-notes/enterprise-server/3-2/15.yml +++ /dev/null @@ -1,20 +0,0 @@ -date: '2022-06-28' -sections: - security_fixes: - - "**MEDIA**: Garantiza que servicios internos no evalúen \"github.company.com\" ni \"github-company.com\" como nombres de host idénticos, lo que evita un posible ataque de falsificación de la seguridad del lado servidor (SSRF)." - - "*BAJA**: Un atacante podía acceder a la consola de administración con un ataque punto a punto barra a través de HTTP incluso si las reglas de firewall externas bloqueaban el acceso HTTP." - - Los paquetes se han actualizado a las últimas versiones de seguridad. - bugs: - - "En algunos casos, los administradores de sitios no se agregaban automáticamente como propietarios empresariales." - - "Después de combinar una rama en la rama predeterminada, el vínculo \"Historial\" de un archivo seguía vinculado a la rama anterior en lugar de estar vinculado a la rama de destino." - changes: - - "La creación o actualización de ejecuciones de comprobación o conjuntos de comprobaciones podía devolver \"500 Error de servidor interno\" si el valor de determinados campos, como el nombre, era demasiado largo." - known_issues: - - "En una instancia recién configurada de {% data variables.product.prodname_ghe_server %} sin ningún usuario, un atacante podría crear el primer usuario administrador." - - Las reglas de cortafuegos personalizadas se eliminan durante el proceso de actualización. - - "Los archivos supervisados de Git LFS [cargados desde la interfaz web](https://github.com/blog/2105-upload-files-to-your-repositories) se agregan de manera incorrecta y directa al repositorio." - - Las incidencias no se pueden cerrar si contienen un enlace permanente a un blob del mismo repositorio en el que la ruta es mayor de 255 caracteres. - - "Cuando se habilita \"Los usuarios pueden buscar en GitHub.com\" con {% data variables.product.prodname_github_connect %}, las incidencias en los repositorios privados e internos no se incluyen en los resultados de búsqueda de {% data variables.product.prodname_dotcom_the_website %}." - - "El registro npm de {% data variables.product.prodname_registry %} ya no devuelve un valor de hora en las respuestas de metadatos. Esto se hacía para permitir mejoras de rendimiento importantes. Seguimos teniendo todos los datos necesarios para devolver un valor de tiempo como parte de la respuesta de metadatos y reanudaremos la devolución de este valor en el futuro una vez que hayamos resuelto las incidencias de rendimiento existentes." - - Los límites de recursos que son específicos para procesar enlaces previos a la recepción podrían ocasionar errores en algunos de ellos. - - '{% data reusables.release-notes.ghas-3.4-secret-scanning-known-issue %}' diff --git a/translations/es-ES/data/release-notes/enterprise-server/3-2/16.yml b/translations/es-ES/data/release-notes/enterprise-server/3-2/16.yml deleted file mode 100644 index c71997e09b..0000000000 --- a/translations/es-ES/data/release-notes/enterprise-server/3-2/16.yml +++ /dev/null @@ -1,26 +0,0 @@ -date: '2022-07-21' -sections: - security_fixes: - - '**MEDIA**: Evita un ataque en el que una falsificación de solicitud del lado servidor (SSRF) podría hacer que el puente de Subversion (SVN) ejecutara código remoto mediante la inyección de datos arbitrarios en Memcached.' - - 'Actualiza Grafana a la versión 7.5.16, que resuelve varias vulnerabilidades de seguridad, entre las que se incluyen [CVE-2020-13379](https://github.com/advisories/GHSA-wc9w-wvq2-ffm9) y [CVE-2022-21702](https://github.com/grafana/grafana/security/advisories/GHSA-xc3p-28hw-q24g).' - - 'Los paquetes se han actualizado a las últimas versiones de seguridad.' - bugs: - - 'Se ha reparado un error por el que los archivos dentro de los archivos zip del artefacto tenían permisos de 000 cuando se desempaquetaban mediante una herramienta de descompresión. Ahora los archivos tendrán los permisos establecidos en 644, tal y como funciona en GitHub.com.' - - 'En algunos casos, el demonio collectd podría consumir un exceso de memoria.' - - 'En algunos casos, las copias de seguridad de los archivos de registro rotados podrían acumular y consumir un exceso de almacenamiento.' - - 'Tras una actualización a una nueva versión de actualización de características y la posterior ejecución de configuración, Elasticsearch podría registrar un exceso de excepciones mientras vuelve a generar índices.' - - 'En algunos casos en los que una rama protegida requería más de una revisión de aprobación, una solicitud de incorporación de cambios podría combinarse con un número de revisiones de aprobación inferior al requerido.' - - 'En las instancias que utilizaban la autenticación LDAP, la solicitud de autenticación para el modo sudo colocaba el cursor incorrectamente en el campo de contraseña de manera predeterminada cuando los campos de texto para un nombre de usuario y una contraseña estaban visibles.' - changes: - - 'La utilidad de la línea de comandos "ghe-set-password" inicia los servicios necesarios automáticamente cuando la instancia se arranca en el modo de recuperación.' - - 'Las métricas para procesos en segundo plano "aqueduct" se reúnen para el reenvío de Collectd y se muestran en la consola de administración.' - - 'La ubicación del registro de ejecución de configuración y migración de base de datos, "/data/user/common/ghe-config.log", ahora se muestra en la página en la que se detalla una migración en curso.' - known_issues: - - 'En una instancia recién configurada de {% data variables.product.prodname_ghe_server %} sin ningún usuario, un atacante podría crear el primer usuario administrador.' - - 'Las reglas de cortafuegos personalizadas se eliminan durante el proceso de actualización.' - - 'Los archivos supervisados de Git LFS [cargados desde la interfaz web](https://github.com/blog/2105-upload-files-to-your-repositories) se agregan de manera incorrecta y directa al repositorio.' - - "Las incidencias no se pueden cerrar si contienen un enlace permanente a un blob del mismo repositorio en el que la ruta es mayor de 255\_caracteres." - - 'Cuando se habilita "Los usuarios pueden buscar en GitHub.com" con {% data variables.product.prodname_github_connect %}, las incidencias en los repositorios privados e internos no se incluyen en los resultados de búsqueda de {% data variables.product.prodname_dotcom_the_website %}.' - - 'El registro npm de {% data variables.product.prodname_registry %} ya no devuelve un valor de hora en las respuestas de metadatos. Esto se hacía para permitir mejoras de rendimiento importantes. Seguimos teniendo todos los datos necesarios para devolver un valor de tiempo como parte de la respuesta de metadatos y reanudaremos la devolución de este valor en el futuro una vez que hayamos resuelto las incidencias de rendimiento existentes.' - - 'Los límites de recursos que son específicos para procesar enlaces previos a la recepción podrían ocasionar errores en algunos de ellos.' - - '{% data reusables.release-notes.ghas-3.4-secret-scanning-known-issue %}' diff --git a/translations/es-ES/data/release-notes/enterprise-server/3-2/17.yml b/translations/es-ES/data/release-notes/enterprise-server/3-2/17.yml deleted file mode 100644 index 38943c2361..0000000000 --- a/translations/es-ES/data/release-notes/enterprise-server/3-2/17.yml +++ /dev/null @@ -1,18 +0,0 @@ -date: '2022-08-11' -sections: - security_fixes: - - | - **CRITICAL**: GitHub Enterprise Server's Elasticsearch container used a version of OpenJDK 8 that was vulnerable to an integer truncation issue when processing malicious XSLT stylesheets. The vulnerability is tracked as [CVE-2022-34169](https://github.com/advisories/GHSA-9339-86wc-4qgf). - - | - **HIGH**: Previously installed apps on user accounts were automatically granted permission to access an organization on scoped access tokens after the user account was transformed into an organization account. This vulnerability was reported via the [GitHub Bug Bounty program](https://bounty.github.com). - bugs: - - When a custom dormancy threshold was set for the instance, suspending all dormant users did not reliably respect the threshold. For more information about dormancy, see "[Managing dormant users](/admin/user-management/managing-users-in-your-enterprise/managing-dormant-users)." - known_issues: - - On a freshly set up {% data variables.product.prodname_ghe_server %} instance without any users, an attacker could create the first admin user. - - Custom firewall rules are removed during the upgrade process. - - Git LFS tracked files [uploaded through the web interface](https://github.com/blog/2105-upload-files-to-your-repositories) are incorrectly added directly to the repository. - - Issues cannot be closed if they contain a permalink to a blob in the same repository, where the blob's file path is longer than 255 characters. - - When "Users can search GitHub.com" is enabled with {% data variables.product.prodname_github_connect %}, issues in private and internal repositories are not included in {% data variables.product.prodname_dotcom_the_website %} search results. - - The {% data variables.product.prodname_registry %} npm registry no longer returns a time value in metadata responses. This was done to allow for substantial performance improvements. We continue to have all the data necessary to return a time value as part of the metadata response and will resume returning this value in the future once we have solved the existing performance issues. - - Resource limits that are specific to processing pre-receive hooks may cause some pre-receive hooks to fail. - - '{% data reusables.release-notes.ghas-3.4-secret-scanning-known-issue %}' diff --git a/translations/es-ES/data/release-notes/enterprise-server/3-2/18.yml b/translations/es-ES/data/release-notes/enterprise-server/3-2/18.yml deleted file mode 100644 index b055b0e6e8..0000000000 --- a/translations/es-ES/data/release-notes/enterprise-server/3-2/18.yml +++ /dev/null @@ -1,16 +0,0 @@ -date: '2022-08-30' -sections: - bugs: - - 'Podían aparecer claves SSH administrativas duplicadas en la consola de administración y en el archivo "/home/admin/.ssh/authorized_keys".' - - 'En algunos casos, las tareas en segundo plano se bloqueaban porque se utilizaba una biblioteca simultáneamente a pesar de no ser segura para subprocesos.' - changes: - - 'Se ha acelerado la generación de conjuntos de soporte gracias a un saneamiento de registros en paralelo. Para obtener más información sobre los conjuntos de soporte, consulta "[Facilitar información al equipo de soporte de GitHub](/support/contacting-github-support/providing-data-to-github-support)".' - known_issues: - - 'En una instancia recién configurada de {% data variables.product.prodname_ghe_server %} sin ningún usuario, un atacante podría crear el primer usuario administrador.' - - 'Las reglas de cortafuegos personalizadas se eliminan durante el proceso de actualización.' - - 'Los archivos supervisados de Git LFS [cargados desde la interfaz web](https://github.com/blog/2105-upload-files-to-your-repositories) se agregan de manera incorrecta y directa al repositorio.' - - "Las incidencias no se pueden cerrar si contienen un enlace permanente a un blob del mismo repositorio en el que la ruta es mayor de 255\_caracteres." - - 'Cuando se habilita "Los usuarios pueden buscar en GitHub.com" con {% data variables.product.prodname_github_connect %}, las incidencias en los repositorios privados e internos no se incluyen en los resultados de búsqueda de {% data variables.product.prodname_dotcom_the_website %}.' - - 'El registro npm de {% data variables.product.prodname_registry %} ya no devuelve un valor de hora en las respuestas de metadatos. Esto se hacía para permitir mejoras de rendimiento importantes. Seguimos teniendo todos los datos necesarios para devolver un valor de tiempo como parte de la respuesta de metadatos y reanudaremos la devolución de este valor en el futuro una vez que hayamos resuelto las incidencias de rendimiento existentes.' - - 'Los límites de recursos que son específicos para procesar enlaces previos a la recepción podrían ocasionar errores en algunos de ellos.' - - '{% data reusables.release-notes.ghas-3.4-secret-scanning-known-issue %}' diff --git a/translations/es-ES/data/release-notes/enterprise-server/3-2/2.yml b/translations/es-ES/data/release-notes/enterprise-server/3-2/2.yml deleted file mode 100644 index 5c0a995d03..0000000000 --- a/translations/es-ES/data/release-notes/enterprise-server/3-2/2.yml +++ /dev/null @@ -1,23 +0,0 @@ -date: '2021-10-28' -sections: - security_fixes: - - 'Era posible que las contraseñas de texto claro terminaran en algunos archivos de registro.' - - 'Se han añadido a la lista de denegaciones diversas claves públicas SSH que se sabe que son débiles y ya no se pueden registrar. Además, las versiones de GitKraken conocidas por generar claves de SSH débiles (7.6.x, 7.7.x y 8.0.0) tienen bloqueada la función de registro de nuevas claves públicas.' - - 'Los paquetes se han actualizado a las últimas versiones de seguridad.' - bugs: - - 'Se podían producir errores en la restauración para el servidor empresarial en modo de agrupación en clústeres si el orquestador no estaba en buen estado.' - - 'Los vínculos de los codespaces se mostraban en la configuración de la organización.' - - 'Los usuarios que eran propietarios de muchas organizaciones no podían utilizar varias partes de la aplicación.' - - 'Se corrigió un enlace a https://docs.github.com.' - changes: - - 'Optimizaciones de navegación y rendimiento de trabajos para los repositorios con muchas referencias.' - known_issues: - - 'Después de guardar una nueva versión en un repositorio, la página "/releases" muestra un error 500. Se espera tener una corrección para este problema en la versión 3.2.3.' - - 'En una instalación nueva de {% data variables.product.prodname_ghe_server %} que no tenga ningún usuario, un atacante podría crear el primer usuario administrador.' - - 'Las reglas de cortafuegos personalizadas se eliminan durante el proceso de actualización.' - - 'Los archivos supervisados de Git LFS [cargados desde la interfaz web](https://github.com/blog/2105-upload-files-to-your-repositories) se agregan de manera incorrecta y directa al repositorio.' - - "Las incidencias no se pueden cerrar si contienen un enlace permanente a un blob del mismo repositorio en el que la ruta es mayor de 255\_caracteres." - - 'Cuando se habilita "Los usuarios pueden buscar en GitHub.com" con GitHub Connect, las incidencias en los repositorios privados e internos no se incluyen en los resultados de la búsqueda de GitHub.com.' - - 'El registro npm de {% data variables.product.prodname_registry %} ya no devuelve un valor de hora en las respuestas de metadatos. Esto se hacía para permitir mejoras de rendimiento importantes. Seguimos teniendo todos los datos necesarios para devolver un valor de tiempo como parte de la respuesta de metadatos y reanudaremos la devolución de este valor en el futuro una vez que hayamos resuelto las incidencias de rendimiento existentes.' - - 'Los límites de recursos que son específicos para procesar enlaces previos a la recepción podrían ocasionar errores en algunos de ellos.' - - '{% data reusables.release-notes.ghas-3.4-secret-scanning-known-issue %}' diff --git a/translations/es-ES/data/release-notes/enterprise-server/3-2/3.yml b/translations/es-ES/data/release-notes/enterprise-server/3-2/3.yml deleted file mode 100644 index 1d68a8ef65..0000000000 --- a/translations/es-ES/data/release-notes/enterprise-server/3-2/3.yml +++ /dev/null @@ -1,31 +0,0 @@ -date: '2021-11-09' -sections: - security_fixes: - - A path traversal vulnerability was identified in {% data variables.product.prodname_pages %} builds on {% data variables.product.prodname_ghe_server %} that could allow an attacker to read system files. To exploit this vulnerability, an attacker needed permission to create and build a {% data variables.product.prodname_pages %} site on the {% data variables.product.prodname_ghe_server %} instance. This vulnerability affected all versions of {% data variables.product.prodname_ghe_server %} prior to 3.3, and was fixed in versions 3.0.19, 3.1.11, and 3.2.3. This vulnerability was reported through the {% data variables.product.company_short %} Bug Bounty program and has been assigned CVE-2021-22870. - - Packages have been updated to the latest security versions. - bugs: - - Some Git operations failed after upgrading a {% data variables.product.prodname_ghe_server %} 3.x cluster because of the HAProxy configuration. - - Unicorn worker counts might have been set incorrectly in clustering mode. - - Resqued worker counts might have been set incorrectly in clustering mode. - - If Ubuntu's Uncomplicated Firewall (UFW) status was inactive, a client could not clearly see it in the logs. - - Upgrading from {% data variables.product.prodname_ghe_server %} 2.x to 3.x failed when there were UTF8 characters in an LDAP configuration. - - Some pages and Git-related background jobs might not run in cluster mode with certain cluster configurations. - - The documentation link for Server Statistics was broken. - - When a new tag was created, the [push](/developers/webhooks-and-events/webhooks/webhook-events-and-payloads#push) webhook payload did not display a correct `head_commit` object. Now, when a new tag is created, the 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. - - The enterprise audit log page would not display audit events for {% data variables.product.prodname_secret_scanning %}. - - There was an insufficient job timeout for replica repairs. - - A repository's releases page would return a 500 error when viewing releases. - - 'Users were not warned about potentially dangerous bidirectional unicode characters when viewing files. For more information, see "[Warning about bidirectional Unicode text](https://github.co/hiddenchars)" in {% data variables.product.prodname_blog %}.' - - Hookshot Go sent distribution type metrics that Collectd could not handle, which caused a ballooning of parsing errors. - - Public repositories displayed unexpected results from {% data variables.product.prodname_secret_scanning %} with a type of `Unknown Token`. - changes: - - Kafka configuration improvements have been added. When deleting repositories, package files are now immediately deleted from storage account to free up space. `DestroyDeletedPackageVersionsJob` now deletes package files from storage account for stale packages along with metadata records. - 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 %}' \ No newline at end of file diff --git a/translations/es-ES/data/release-notes/enterprise-server/3-2/4.yml b/translations/es-ES/data/release-notes/enterprise-server/3-2/4.yml deleted file mode 100644 index 169bee30c7..0000000000 --- a/translations/es-ES/data/release-notes/enterprise-server/3-2/4.yml +++ /dev/null @@ -1,30 +0,0 @@ -date: '2021-11-23' -intro: 'Se han deshabilitado las descargas debido a un error importante que afectaba a varios clientes. Se proporcionará una solución en la siguiente revisión.' -sections: - security_fixes: - - 'Los paquetes se han actualizado a las últimas versiones de seguridad.' - bugs: - - 'La ejecución de "ghe-repl-start" o "ghe-repl-status" algunas veces devolvió errores para conectarse a la base de datos cuando se habilitó Acciones de GitHub.' - - 'Los enlaces previos a la recepción fallaron debido a un "PATH" sin definir.' - - 'La ejecución de "ghe-repl-setup" devolvía un error de tipo: "cannot create directory /data/user/elasticsearch: File exists" si la instancia se había configurado anteriormente como una réplica.' - - 'La ejecución de "ghe-support-bundle" devolvía un error de tipo: "integer expression expected".' - - 'Después de configurar una réplica de disponibilidad alta, "ghe-repl-status" incluía un error en la salida: "unexpected unclosed action in command".' - - 'En ambientes de clúster grandes, el backend de autenticación podría no estar disponible en un subconjunto de nodos de frontend.' - - 'Puede que algunos servicios críticos no estuvieran disponibles en los nodos del back-end en el clúster de GHES.' - - 'Los permisos de repositorio para el usuario que devolvía la API de "/repos" no devolvían la lista completa.' - - 'La conexión de "childTeams" en el objeto "Team" del esquema de GraphQL producía resultados incorrectos en algunas circunstancias.' - - 'En una configuración de disponibilidad alta, el mantenimiento de repositorio siempre se mostraba como fallido en las stafftools, incluso cuando se había realizado correctamente.' - - 'Los patrones definidos por el usuario no detectaban secretos en archivos como "package.json" o "yarn.lock".' - changes: - - 'Una capa exterior adicional de compresión de "gzip" al crear un conjunto de soporte de clústeres con "ghe-cluster-suport-bundle" ahora está desactivada de manera predeterminada. Esta compresión exterior puede aplicarse opcionalmente con la opción de la línea de comandos "ghe-cluster-suport-bundle -c".' - - 'Agregamos texto extra a la consola de administración para recordarles a los usuarios sobre la recolección de datos de las apps móviles para propósitos de mejora de la experiencia.' - - 'El registro de conexión de datos de {% data variables.product.prodname_github_connect %} ahora incluye una lista de características de {% data variables.product.prodname_github_connect %} habilitadas. [Actualizado el 2021-12-09]' - known_issues: - - 'En una instalación nueva de {% data variables.product.prodname_ghe_server %} que no tenga ningún usuario, un atacante podría crear el primer usuario administrador.' - - 'Las reglas de cortafuegos personalizadas se eliminan durante el proceso de actualización.' - - 'Los archivos supervisados de Git LFS [cargados desde la interfaz web](https://github.com/blog/2105-upload-files-to-your-repositories) se agregan de manera incorrecta y directa al repositorio.' - - "Las incidencias no se pueden cerrar si contienen un enlace permanente a un blob del mismo repositorio en el que la ruta es mayor de 255\_caracteres." - - 'Cuando se habilita "Los usuarios pueden buscar en GitHub.com" con GitHub Connect, las incidencias en los repositorios privados e internos no se incluyen en los resultados de la búsqueda de GitHub.com.' - - 'El registro npm de {% data variables.product.prodname_registry %} ya no devuelve un valor de hora en las respuestas de metadatos. Esto se hacía para permitir mejoras de rendimiento importantes. Seguimos teniendo todos los datos necesarios para devolver un valor de tiempo como parte de la respuesta de metadatos y reanudaremos la devolución de este valor en el futuro una vez que hayamos resuelto las incidencias de rendimiento existentes.' - - 'Los límites de recursos que son específicos para procesar enlaces previos a la recepción podrían ocasionar errores en algunos de ellos.' - - '{% data reusables.release-notes.ghas-3.4-secret-scanning-known-issue %}' diff --git a/translations/es-ES/data/release-notes/enterprise-server/3-2/5.yml b/translations/es-ES/data/release-notes/enterprise-server/3-2/5.yml deleted file mode 100644 index 6144c9544f..0000000000 --- a/translations/es-ES/data/release-notes/enterprise-server/3-2/5.yml +++ /dev/null @@ -1,28 +0,0 @@ -date: '2021-12-07' -sections: - security_fixes: - - 'Los paquetes de soporte podrían incluir archivos sensibles si cumplen con un conjunto de características específicas.' - - "Se identificó una vulnerabilidad de representación incorrecta en la IU en el servidor de GitHub Enterprise que permitía otorgar más permisos de los que se mostraban al usuario en la aprobación durante el flujo web de autorización de usuarios en una GitHub App. Esta vulnerabilidad afectaba a todas las versiones de GitHub\_Enterprise Server anteriores a la\_3.3 y se ha corregido en las versiones\_3.2.5, 3.1.13 y 3.0.21. Esta vulnerabilidad se notificó mediante el programa de recompensas de GitHub por la detección de errores y se le ha asignado [CVE-2021-41598](https://www.cve.org/CVERecord?id=CVE-2021-41598)." - - "Se identificó una vulnerabilidad de ejecución de código remoto en el servidor de GitHub Enterprise que podría aprovecharse al crear un sitio de GitHub Pages. Esta vulnerabilidad afectaba a todas las versiones de GitHub\_Enterprise Server anteriores a la\_3.3 y se ha corregido en las versiones\_3.0.21, 3.1.13 y 3.2.5. Esta vulnerabilidad se notificó mediante el programa de recompensas de GitHub por la detección de errores y se le ha asignado [CVE-2021-41599](https://www.cve.org/CVERecord?id=CVE-2021-41599). Actualizado el 17 de febrero de 2022." - bugs: - - 'En algunos casos, cuando Acciones no estaba habilitado, "ghe-support-bundle" notificaba un mensaje inesperado de "No se puede encontrar el contenedor de MS SQL".' - - 'La ejecución de "ghe-config-apply" en ocasiones podía producir errores debido a problemas con los permisos en "/data/user/tmp/pages".' - - 'Una mala configuración en la consola de administración causó errores de programación.' - - 'Docker retenía los archivos de registro abiertos después de una rotación de registros.' - - 'Las migraciones podían bloquearse debido a un manejo incorrecto de los valores de "blob_path" que no son compatibles con UTF-8.' - - 'Las solicitudes de GraphQL no configuraban la variable GITHUB_USER_IP en los entornos de enlaces previos a la recepción.' - - 'Los vínculos de paginación en los registros de auditoría de la organización no persistían a los parámetros de consulta.' - - 'Durante una revisión en caliente, era posible duplicar los hashes si una transición se ejecutaba más de una vez.' - changes: - - 'Clarifica una explicación del estilo de ruta de Acciones en la documentación.' - - 'Actualiza las direcciones URL de contacto de soporte técnico para utilizar el sitio de soporte técnico actual, support.github.com.' - - 'Se ha proporcionado una solución de problemas adicional al ejecutar "ghe-mssql-diagnostic".' - known_issues: - - 'En una instalación nueva de {% data variables.product.prodname_ghe_server %} que no tenga ningún usuario, un atacante podría crear el primer usuario administrador.' - - 'Las reglas de cortafuegos personalizadas se eliminan durante el proceso de actualización.' - - 'Los archivos supervisados de Git LFS [cargados desde la interfaz web](https://github.com/blog/2105-upload-files-to-your-repositories) se agregan de manera incorrecta y directa al repositorio.' - - "Las incidencias no se pueden cerrar si contienen un enlace permanente a un blob del mismo repositorio en el que la ruta es mayor de 255\_caracteres." - - 'Cuando se habilita "Los usuarios pueden buscar en GitHub.com" con GitHub Connect, las incidencias en los repositorios privados e internos no se incluyen en los resultados de la búsqueda de GitHub.com.' - - 'El registro npm de {% data variables.product.prodname_registry %} ya no devuelve un valor de hora en las respuestas de metadatos. Esto se hacía para permitir mejoras de rendimiento importantes. Seguimos teniendo todos los datos necesarios para devolver un valor de tiempo como parte de la respuesta de metadatos y reanudaremos la devolución de este valor en el futuro una vez que hayamos resuelto las incidencias de rendimiento existentes.' - - 'Los límites de recursos que son específicos para procesar enlaces previos a la recepción podrían ocasionar errores en algunos de ellos.' - - '{% data reusables.release-notes.ghas-3.4-secret-scanning-known-issue %}' diff --git a/translations/es-ES/data/release-notes/enterprise-server/3-2/6.yml b/translations/es-ES/data/release-notes/enterprise-server/3-2/6.yml deleted file mode 100644 index fe6c803a05..0000000000 --- a/translations/es-ES/data/release-notes/enterprise-server/3-2/6.yml +++ /dev/null @@ -1,14 +0,0 @@ -date: '2021-12-13' -sections: - security_fixes: - - '{% octicon "alert" aria-label="The alert icon" %} **RIESGO CRÍTICO:** una vulnerabilidad de ejecución de código remoto en la biblioteca Log4j, identificada como [CVE-2021-44228](https://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2021-44228), afectaba a todas las versiones de {% data variables.product.prodname_ghe_server %} anteriores a 3.3.1. La biblioteca Log4j se utiliza en un servicio de código abierto que se ejecuta en instancias {% data variables.product.prodname_ghe_server %}. Esta vulnerabilidad se corrigió en las versiones 3.0.22, 3.1.14, 3.2.6 y 3.3.1 de {% data variables.product.prodname_ghe_server %}. Para obtener más información, consulta [esta publicación](https://github.blog/2021-12-13-githubs-response-to-log4j-vulnerability-cve-2021-44228/) en el blog de GitHub.' - - '**Actualización del 17 de diciembre de 2021**: las correcciones de esta versión también solucionan [CVE-2021-45046](https://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2021-45046), que también se publicó después de esta versión. No se requiere ninguna actualización adicional de {% data variables.product.prodname_ghe_server %} para mitigar CVE-2021-44228 y CVE-2021-45046.' - known_issues: - - "En una instalación nueva de {% data variables.product.prodname_ghe_server %} que no tenga ningún usuario, un atacante podría crear el primer usuario administrador." - - Las reglas de cortafuegos personalizadas se eliminan durante el proceso de actualización. - - "Los archivos supervisados de Git LFS [cargados desde la interfaz web](https://github.com/blog/2105-upload-files-to-your-repositories) se agregan de manera incorrecta y directa al repositorio." - - Las incidencias no se pueden cerrar si contienen un enlace permanente a un blob del mismo repositorio en el que la ruta es mayor de 255 caracteres. - - "Cuando se habilita \"Los usuarios pueden buscar en GitHub.com\" con GitHub Connect, las incidencias en los repositorios privados e internos no se incluyen en los resultados de la búsqueda de GitHub.com." - - "El registro npm de {% data variables.product.prodname_registry %} ya no devuelve un valor de hora en las respuestas de metadatos. Esto se hacía para permitir mejoras de rendimiento importantes. Seguimos teniendo todos los datos necesarios para devolver un valor de tiempo como parte de la respuesta de metadatos y reanudaremos la devolución de este valor en el futuro una vez que hayamos resuelto las incidencias de rendimiento existentes." - - Los límites de recursos que son específicos para procesar enlaces previos a la recepción podrían ocasionar errores en algunos de ellos. - - '{% data reusables.release-notes.ghas-3.4-secret-scanning-known-issue %}' diff --git a/translations/es-ES/data/release-notes/enterprise-server/3-2/7.yml b/translations/es-ES/data/release-notes/enterprise-server/3-2/7.yml deleted file mode 100644 index 491591ca1e..0000000000 --- a/translations/es-ES/data/release-notes/enterprise-server/3-2/7.yml +++ /dev/null @@ -1,23 +0,0 @@ -date: '2022-01-18' -sections: - security_fixes: - - "Los paquetes se han actualizado a las últimas versiones de seguridad. En estas actualizaciones, Log4j se ha actualizado a la versión 2.17.1. Nota: las mitigaciones anteriores publicadas en\_3.3.1, 3.2.6, 3.1.14, y 3.0.22 son suficientes para abordar el impacto de CVE-2021-44228, CVE-2021-45046, CVE-2021-45105 y CVE-2021-44832 en estas versiones del servidor de GitHub Enterprise." - - 'Sanitizar más secretos en los paquetes de soporte generados' - - 'Los paquetes se han actualizado a las últimas versiones de seguridad.' - bugs: - - 'Los ejecutores autohospedados de Acciones no podían autoactualizarse ni ejecutar nuevos trabajos después de actualizarse desde una instalación de GHES anterior.' - - 'La configuración de almacenamiento no se podía validar cuando se configuraba MinIO como almacenamiento de blobs para GitHub Packages.' - - 'La ejecución de "ghe-config-apply" en ocasiones podía producir errores debido a problemas con los permisos en "/data/user/tmp/pages".' - - 'El botón de guardar en la consola de almacenamiento no se pudo alcanzar desplazándose en navegadores de menor resolución.' - - 'Las gráficas de monitoreo de tráfico de almacenamiento e IOPS no se actualizaron después de la actualización de la versión de collectd.' - - 'Algunos trabajos relacionados con webhooks podían generar una gran cantidad de registros.' - - 'Varios vínculos de documentación daban como resultado un error de tipo "404 No encontrado".' - known_issues: - - 'En una instalación nueva de {% data variables.product.prodname_ghe_server %} que no tenga ningún usuario, un atacante podría crear el primer usuario administrador.' - - 'Las reglas de cortafuegos personalizadas se eliminan durante el proceso de actualización.' - - 'Los archivos supervisados de Git LFS [cargados desde la interfaz web](https://github.com/blog/2105-upload-files-to-your-repositories) se agregan de manera incorrecta y directa al repositorio.' - - "Las incidencias no se pueden cerrar si contienen un enlace permanente a un blob del mismo repositorio en el que la ruta es mayor de 255\_caracteres." - - 'Cuando se habilita "Los usuarios pueden buscar en GitHub.com" con GitHub Connect, las incidencias en los repositorios privados e internos no se incluyen en los resultados de la búsqueda de GitHub.com.' - - 'El registro npm de {% data variables.product.prodname_registry %} ya no devuelve un valor de hora en las respuestas de metadatos. Esto se hacía para permitir mejoras de rendimiento importantes. Seguimos teniendo todos los datos necesarios para devolver un valor de tiempo como parte de la respuesta de metadatos y reanudaremos la devolución de este valor en el futuro una vez que hayamos resuelto las incidencias de rendimiento existentes.' - - 'Los límites de recursos que son específicos para procesar enlaces previos a la recepción podrían ocasionar errores en algunos de ellos.' - - '{% data reusables.release-notes.ghas-3.4-secret-scanning-known-issue %}' diff --git a/translations/es-ES/data/release-notes/enterprise-server/3-2/8.yml b/translations/es-ES/data/release-notes/enterprise-server/3-2/8.yml deleted file mode 100644 index f15625485c..0000000000 --- a/translations/es-ES/data/release-notes/enterprise-server/3-2/8.yml +++ /dev/null @@ -1,26 +0,0 @@ -date: '2022-02-01' -sections: - security_fixes: - - 'Los paquetes se han actualizado a las últimas versiones de seguridad.' - bugs: - - 'Las páginas no estaban disponibles después de una rotación de secretos de MySQL hasta que "nginx" se reiniciaba manualmente.' - - 'Las migraciones podían producir un error cuando {% data variables.product.prodname_actions %} estaba habilitado.' - - 'Al configurar la programación de mantenimiento con una fecha ISO 8601, la hora programada real no coincidía debido a que la zona horaria no se transformaba a UTC.' - - 'Los mensajes de errores espurios relacionados con "cloud-config.service" se generaban en la consola.' - - 'El número de versión no se actualizaba correctamente después de instalar una revisión en caliente utilizando "ghe-cluster-each".' - - 'Varios trabajos de limpieza de tabla de webhook podían ejecutarse simultáneamente, lo que ocasionaba contención de recursos e incrementaba el tiempo de ejecución del trabajo.' - - 'Cuando se ejecutaba desde la principal, "ghe-repl-teardown" en una réplica no quitaba la réplica del grupo de disponibilidad de MSSQL.' - - 'Al utilizar la autenticación CAS y habilitar la opción "Reactivar usuarios suspendidos", dichos usuarios no se reactivaban automáticamente.' - - 'La capacidad de limitar las notificaciones basadas en correos electrónicos para los usuarios con correos electrónicos en un dominio aprobado o verificado no funcionaba correctamente.' - - 'Una migración de base de datos de duración larga relacionada con los ajustes de alertas de seguridad podía retrasar la finalización de la actualización.' - changes: - - 'El registro de conexión de datos de GitHub Connect ahora incluye un recuento de la cantidad de usuarios activos e inactivos y el periodo de inactividad configurado.' - known_issues: - - 'En una instalación nueva de {% data variables.product.prodname_ghe_server %} que no tenga ningún usuario, un atacante podría crear el primer usuario administrador.' - - 'Las reglas de cortafuegos personalizadas se eliminan durante el proceso de actualización.' - - 'Los archivos supervisados de Git LFS [cargados desde la interfaz web](https://github.com/blog/2105-upload-files-to-your-repositories) se agregan de manera incorrecta y directa al repositorio.' - - "Las incidencias no se pueden cerrar si contienen un enlace permanente a un blob del mismo repositorio en el que la ruta es mayor de 255\_caracteres." - - 'Cuando se habilita "Los usuarios pueden buscar en GitHub.com" con GitHub Connect, las incidencias en los repositorios privados e internos no se incluyen en los resultados de la búsqueda de GitHub.com.' - - 'El registro npm de {% data variables.product.prodname_registry %} ya no devuelve un valor de hora en las respuestas de metadatos. Esto se hacía para permitir mejoras de rendimiento importantes. Seguimos teniendo todos los datos necesarios para devolver un valor de tiempo como parte de la respuesta de metadatos y reanudaremos la devolución de este valor en el futuro una vez que hayamos resuelto las incidencias de rendimiento existentes.' - - 'Los límites de recursos que son específicos para procesar enlaces previos a la recepción podrían ocasionar errores en algunos de ellos.' - - '{% data reusables.release-notes.ghas-3.4-secret-scanning-known-issue %}' diff --git a/translations/es-ES/data/release-notes/enterprise-server/3-2/9.yml b/translations/es-ES/data/release-notes/enterprise-server/3-2/9.yml deleted file mode 100644 index a7917f83d8..0000000000 --- a/translations/es-ES/data/release-notes/enterprise-server/3-2/9.yml +++ /dev/null @@ -1,20 +0,0 @@ -date: '2022-02-17' -sections: - security_fixes: - - 'Un usuario podía registrar a un usuario o una organización con el nombre "saml".' - - 'Los paquetes se han actualizado a las últimas versiones de seguridad.' - bugs: - - 'Al usar Azure Blob Storage, los ajustes de almacenamiento de GitHub Packages no se podían validar y guardar en la consola de administración.' - - 'La opción de configuración mssql.backup.cadence falló la comprobación ghe-config-check con una advertencia de conjunto de caracteres no válido.' - - 'Corrige SystemStackError (se apilaron demasiado profundamente) al obtener más de 2^16 llaves del memcached.' - changes: - - 'EL análisis de secretos dejará de analizar los archivos ZIP y de otros tipos en búsqueda de secretos.' - known_issues: - - 'En una instancia recién configurada de {% data variables.product.prodname_ghe_server %} sin ningún usuario, un atacante podría crear el primer usuario administrador.' - - 'Las reglas de cortafuegos personalizadas se eliminan durante el proceso de actualización.' - - 'Los archivos supervisados de Git LFS [cargados desde la interfaz web](https://github.com/blog/2105-upload-files-to-your-repositories) se agregan de manera incorrecta y directa al repositorio.' - - "Las incidencias no se pueden cerrar si contienen un enlace permanente a un blob del mismo repositorio en el que la ruta es mayor de 255\_caracteres." - - 'Cuando se habilita "Los usuarios pueden buscar en GitHub.com" con GitHub Connect, las incidencias en los repositorios privados e internos no se incluyen en los resultados de la búsqueda de GitHub.com.' - - 'El registro npm de {% data variables.product.prodname_registry %} ya no devuelve un valor de hora en las respuestas de metadatos. Esto se hacía para permitir mejoras de rendimiento importantes. Seguimos teniendo todos los datos necesarios para devolver un valor de tiempo como parte de la respuesta de metadatos y reanudaremos la devolución de este valor en el futuro una vez que hayamos resuelto las incidencias de rendimiento existentes.' - - 'Los límites de recursos que son específicos para procesar enlaces previos a la recepción podrían ocasionar errores en algunos de ellos.' - - '{% data reusables.release-notes.ghas-3.4-secret-scanning-known-issue %}' diff --git a/translations/es-ES/data/reusables/organizations/org_settings.md b/translations/es-ES/data/reusables/organizations/org_settings.md index 4e84c3e807..eecd66ef6c 100644 --- a/translations/es-ES/data/reusables/organizations/org_settings.md +++ b/translations/es-ES/data/reusables/organizations/org_settings.md @@ -1,6 +1,6 @@ 1. Under your organization name, click {% octicon "gear" aria-label="The Settings gear" %} **Settings**. - {% ifversion fpt or ghes or ghec %} +{% ifversion fpt or ghes or ghec %} ![Organization settings button](/assets/images/help/organizations/organization-settings-tab-with-overview-tab.png) - {% else %} +{% else %} ![Organization settings button](/assets/images/help/organizations/organization-settings-tab.png) - {% endif %} +{% endif %} diff --git a/translations/es-ES/data/reusables/repositories/git-lfs.md b/translations/es-ES/data/reusables/repositories/git-lfs.md new file mode 100644 index 0000000000..e34dab1f7c --- /dev/null +++ b/translations/es-ES/data/reusables/repositories/git-lfs.md @@ -0,0 +1,9 @@ +--- +ms.openlocfilehash: f8247d698d2b9a9be09d2dcf8e0492355a377204 +ms.sourcegitcommit: 06726d24e73f1175f10749d6fdcf143d6094c9a5 +ms.translationtype: HT +ms.contentlocale: es-ES +ms.lasthandoff: 10/28/2022 +ms.locfileid: "148118753" +--- +Si superas el límite de 5 GB, Git LFS rechazará silenciosamente los archivos nuevos agregados al repositorio. \ No newline at end of file diff --git a/translations/es-ES/data/reusables/user-settings/password-authentication-deprecation.md b/translations/es-ES/data/reusables/user-settings/password-authentication-deprecation.md index 04a4cbd48e..3cb8481a53 100644 --- a/translations/es-ES/data/reusables/user-settings/password-authentication-deprecation.md +++ b/translations/es-ES/data/reusables/user-settings/password-authentication-deprecation.md @@ -1 +1 @@ -When Git prompts you for your password, enter your {% data variables.product.pat_generic %}. Alternatively, you can use a credential helper like [Git Credential Manager](https://github.com/GitCredentialManager/git-credential-manager/blob/main/README.md).{% ifversion not ghae %} Password-based authentication for Git has been removed in favor of more secure authentication methods.{% endif %} For more information, see "[Creating a {% data variables.product.pat_generic %}](/github/authenticating-to-github/creating-a-personal-access-token)." +When Git prompts you for your password, enter your {% data variables.product.pat_generic %}. Alternatively, you can use a credential helper like [Git Credential Manager](https://github.com/GitCredentialManager/git-credential-manager/blob/main/README.md).{% ifversion not ghae %} Password-based authentication for Git has been removed in favor of more secure authentication methods.{% endif %} For more information, see "[Creating a {% data variables.product.pat_generic %}](/authentication/keeping-your-account-and-data-secure/creating-a-personal-access-token)." diff --git a/translations/log/msft-cn-resets.csv b/translations/log/msft-cn-resets.csv index 1db5b3ad15..eee2f92eff 100644 --- a/translations/log/msft-cn-resets.csv +++ b/translations/log/msft-cn-resets.csv @@ -217,6 +217,129 @@ translations/zh-CN/content/sponsors/receiving-sponsorships-through-github-sponso translations/zh-CN/data/glossaries/internal.yml,file deleted because it no longer exists in main translations/zh-CN/data/graphql/ghes-3.1/graphql_previews.enterprise.yml,file deleted because it no longer exists in main translations/zh-CN/data/graphql/ghes-3.2/graphql_previews.enterprise.yml,file deleted because it no longer exists in main +translations/zh-CN/data/release-notes/enterprise-server/2-20/0.yml,file deleted because it no longer exists in main +translations/zh-CN/data/release-notes/enterprise-server/2-20/1.yml,file deleted because it no longer exists in main +translations/zh-CN/data/release-notes/enterprise-server/2-20/10.yml,file deleted because it no longer exists in main +translations/zh-CN/data/release-notes/enterprise-server/2-20/11.yml,file deleted because it no longer exists in main +translations/zh-CN/data/release-notes/enterprise-server/2-20/12.yml,file deleted because it no longer exists in main +translations/zh-CN/data/release-notes/enterprise-server/2-20/13.yml,file deleted because it no longer exists in main +translations/zh-CN/data/release-notes/enterprise-server/2-20/14.yml,file deleted because it no longer exists in main +translations/zh-CN/data/release-notes/enterprise-server/2-20/16.yml,file deleted because it no longer exists in main +translations/zh-CN/data/release-notes/enterprise-server/2-20/17.yml,file deleted because it no longer exists in main +translations/zh-CN/data/release-notes/enterprise-server/2-20/18.yml,file deleted because it no longer exists in main +translations/zh-CN/data/release-notes/enterprise-server/2-20/19.yml,file deleted because it no longer exists in main +translations/zh-CN/data/release-notes/enterprise-server/2-20/2.yml,file deleted because it no longer exists in main +translations/zh-CN/data/release-notes/enterprise-server/2-20/20.yml,file deleted because it no longer exists in main +translations/zh-CN/data/release-notes/enterprise-server/2-20/21.yml,file deleted because it no longer exists in main +translations/zh-CN/data/release-notes/enterprise-server/2-20/22.yml,file deleted because it no longer exists in main +translations/zh-CN/data/release-notes/enterprise-server/2-20/23.yml,file deleted because it no longer exists in main +translations/zh-CN/data/release-notes/enterprise-server/2-20/24.yml,file deleted because it no longer exists in main +translations/zh-CN/data/release-notes/enterprise-server/2-20/3.yml,file deleted because it no longer exists in main +translations/zh-CN/data/release-notes/enterprise-server/2-20/4.yml,file deleted because it no longer exists in main +translations/zh-CN/data/release-notes/enterprise-server/2-20/5.yml,file deleted because it no longer exists in main +translations/zh-CN/data/release-notes/enterprise-server/2-20/6.yml,file deleted because it no longer exists in main +translations/zh-CN/data/release-notes/enterprise-server/2-20/7.yml,file deleted because it no longer exists in main +translations/zh-CN/data/release-notes/enterprise-server/2-20/8.yml,file deleted because it no longer exists in main +translations/zh-CN/data/release-notes/enterprise-server/2-20/9.yml,file deleted because it no longer exists in main +translations/zh-CN/data/release-notes/enterprise-server/2-21/0.yml,file deleted because it no longer exists in main +translations/zh-CN/data/release-notes/enterprise-server/2-21/1.yml,file deleted because it no longer exists in main +translations/zh-CN/data/release-notes/enterprise-server/2-21/10.yml,file deleted because it no longer exists in main +translations/zh-CN/data/release-notes/enterprise-server/2-21/11.yml,file deleted because it no longer exists in main +translations/zh-CN/data/release-notes/enterprise-server/2-21/12.yml,file deleted because it no longer exists in main +translations/zh-CN/data/release-notes/enterprise-server/2-21/13.yml,file deleted because it no longer exists in main +translations/zh-CN/data/release-notes/enterprise-server/2-21/14.yml,file deleted because it no longer exists in main +translations/zh-CN/data/release-notes/enterprise-server/2-21/15.yml,file deleted because it no longer exists in main +translations/zh-CN/data/release-notes/enterprise-server/2-21/16.yml,file deleted because it no longer exists in main +translations/zh-CN/data/release-notes/enterprise-server/2-21/18.yml,file deleted because it no longer exists in main +translations/zh-CN/data/release-notes/enterprise-server/2-21/19.yml,file deleted because it no longer exists in main +translations/zh-CN/data/release-notes/enterprise-server/2-21/2.yml,file deleted because it no longer exists in main +translations/zh-CN/data/release-notes/enterprise-server/2-21/20.yml,file deleted because it no longer exists in main +translations/zh-CN/data/release-notes/enterprise-server/2-21/21.yml,file deleted because it no longer exists in main +translations/zh-CN/data/release-notes/enterprise-server/2-21/22.yml,file deleted because it no longer exists in main +translations/zh-CN/data/release-notes/enterprise-server/2-21/23.yml,file deleted because it no longer exists in main +translations/zh-CN/data/release-notes/enterprise-server/2-21/3.yml,file deleted because it no longer exists in main +translations/zh-CN/data/release-notes/enterprise-server/2-21/4.yml,file deleted because it no longer exists in main +translations/zh-CN/data/release-notes/enterprise-server/2-21/5.yml,file deleted because it no longer exists in main +translations/zh-CN/data/release-notes/enterprise-server/2-21/7.yml,file deleted because it no longer exists in main +translations/zh-CN/data/release-notes/enterprise-server/2-21/8.yml,file deleted because it no longer exists in main +translations/zh-CN/data/release-notes/enterprise-server/2-21/9.yml,file deleted because it no longer exists in main +translations/zh-CN/data/release-notes/enterprise-server/2-22/10.yml,file deleted because it no longer exists in main +translations/zh-CN/data/release-notes/enterprise-server/2-22/11.yml,file deleted because it no longer exists in main +translations/zh-CN/data/release-notes/enterprise-server/2-22/12.yml,file deleted because it no longer exists in main +translations/zh-CN/data/release-notes/enterprise-server/2-22/13.yml,file deleted because it no longer exists in main +translations/zh-CN/data/release-notes/enterprise-server/2-22/14.yml,file deleted because it no longer exists in main +translations/zh-CN/data/release-notes/enterprise-server/2-22/15.yml,file deleted because it no longer exists in main +translations/zh-CN/data/release-notes/enterprise-server/2-22/16.yml,file deleted because it no longer exists in main +translations/zh-CN/data/release-notes/enterprise-server/2-22/17.yml,file deleted because it no longer exists in main +translations/zh-CN/data/release-notes/enterprise-server/2-22/18.yml,file deleted because it no longer exists in main +translations/zh-CN/data/release-notes/enterprise-server/2-22/19.yml,file deleted because it no longer exists in main +translations/zh-CN/data/release-notes/enterprise-server/2-22/20.yml,file deleted because it no longer exists in main +translations/zh-CN/data/release-notes/enterprise-server/2-22/21.yml,file deleted because it no longer exists in main +translations/zh-CN/data/release-notes/enterprise-server/2-22/22.yml,file deleted because it no longer exists in main +translations/zh-CN/data/release-notes/enterprise-server/2-22/4.yml,file deleted because it no longer exists in main +translations/zh-CN/data/release-notes/enterprise-server/2-22/5.yml,file deleted because it no longer exists in main +translations/zh-CN/data/release-notes/enterprise-server/2-22/6.yml,file deleted because it no longer exists in main +translations/zh-CN/data/release-notes/enterprise-server/3-0/0-rc1.yml,file deleted because it no longer exists in main +translations/zh-CN/data/release-notes/enterprise-server/3-0/0-rc2.yml,file deleted because it no longer exists in main +translations/zh-CN/data/release-notes/enterprise-server/3-0/10.yml,file deleted because it no longer exists in main +translations/zh-CN/data/release-notes/enterprise-server/3-0/11.yml,file deleted because it no longer exists in main +translations/zh-CN/data/release-notes/enterprise-server/3-0/12.yml,file deleted because it no longer exists in main +translations/zh-CN/data/release-notes/enterprise-server/3-0/13.yml,file deleted because it no longer exists in main +translations/zh-CN/data/release-notes/enterprise-server/3-0/14.yml,file deleted because it no longer exists in main +translations/zh-CN/data/release-notes/enterprise-server/3-0/15.yml,file deleted because it no longer exists in main +translations/zh-CN/data/release-notes/enterprise-server/3-0/16.yml,file deleted because it no longer exists in main +translations/zh-CN/data/release-notes/enterprise-server/3-0/17.yml,file deleted because it no longer exists in main +translations/zh-CN/data/release-notes/enterprise-server/3-0/18.yml,file deleted because it no longer exists in main +translations/zh-CN/data/release-notes/enterprise-server/3-0/19.yml,file deleted because it no longer exists in main +translations/zh-CN/data/release-notes/enterprise-server/3-0/20.yml,file deleted because it no longer exists in main +translations/zh-CN/data/release-notes/enterprise-server/3-0/21.yml,file deleted because it no longer exists in main +translations/zh-CN/data/release-notes/enterprise-server/3-0/22.yml,file deleted because it no longer exists in main +translations/zh-CN/data/release-notes/enterprise-server/3-0/23.yml,file deleted because it no longer exists in main +translations/zh-CN/data/release-notes/enterprise-server/3-0/24.yml,file deleted because it no longer exists in main +translations/zh-CN/data/release-notes/enterprise-server/3-0/25.yml,file deleted because it no longer exists in main +translations/zh-CN/data/release-notes/enterprise-server/3-0/4.yml,file deleted because it no longer exists in main +translations/zh-CN/data/release-notes/enterprise-server/3-0/5.yml,file deleted because it no longer exists in main +translations/zh-CN/data/release-notes/enterprise-server/3-0/6.yml,file deleted because it no longer exists in main +translations/zh-CN/data/release-notes/enterprise-server/3-0/7.yml,file deleted because it no longer exists in main +translations/zh-CN/data/release-notes/enterprise-server/3-0/8.yml,file deleted because it no longer exists in main +translations/zh-CN/data/release-notes/enterprise-server/3-0/9.yml,file deleted because it no longer exists in main +translations/zh-CN/data/release-notes/enterprise-server/3-1/0-rc1.yml,file deleted because it no longer exists in main +translations/zh-CN/data/release-notes/enterprise-server/3-1/10.yml,file deleted because it no longer exists in main +translations/zh-CN/data/release-notes/enterprise-server/3-1/11.yml,file deleted because it no longer exists in main +translations/zh-CN/data/release-notes/enterprise-server/3-1/12.yml,file deleted because it no longer exists in main +translations/zh-CN/data/release-notes/enterprise-server/3-1/13.yml,file deleted because it no longer exists in main +translations/zh-CN/data/release-notes/enterprise-server/3-1/14.yml,file deleted because it no longer exists in main +translations/zh-CN/data/release-notes/enterprise-server/3-1/15.yml,file deleted because it no longer exists in main +translations/zh-CN/data/release-notes/enterprise-server/3-1/16.yml,file deleted because it no longer exists in main +translations/zh-CN/data/release-notes/enterprise-server/3-1/17.yml,file deleted because it no longer exists in main +translations/zh-CN/data/release-notes/enterprise-server/3-1/18.yml,file deleted because it no longer exists in main +translations/zh-CN/data/release-notes/enterprise-server/3-1/19.yml,file deleted because it no longer exists in main +translations/zh-CN/data/release-notes/enterprise-server/3-1/20.yml,file deleted because it no longer exists in main +translations/zh-CN/data/release-notes/enterprise-server/3-1/21.yml,file deleted because it no longer exists in main +translations/zh-CN/data/release-notes/enterprise-server/3-1/22.yml,file deleted because it no longer exists in main +translations/zh-CN/data/release-notes/enterprise-server/3-1/3.yml,file deleted because it no longer exists in main +translations/zh-CN/data/release-notes/enterprise-server/3-1/5.yml,file deleted because it no longer exists in main +translations/zh-CN/data/release-notes/enterprise-server/3-1/6.yml,file deleted because it no longer exists in main +translations/zh-CN/data/release-notes/enterprise-server/3-1/7.yml,file deleted because it no longer exists in main +translations/zh-CN/data/release-notes/enterprise-server/3-1/8.yml,file deleted because it no longer exists in main +translations/zh-CN/data/release-notes/enterprise-server/3-1/9.yml,file deleted because it no longer exists in main +translations/zh-CN/data/release-notes/enterprise-server/3-2/1.yml,file deleted because it no longer exists in main +translations/zh-CN/data/release-notes/enterprise-server/3-2/10.yml,file deleted because it no longer exists in main +translations/zh-CN/data/release-notes/enterprise-server/3-2/11.yml,file deleted because it no longer exists in main +translations/zh-CN/data/release-notes/enterprise-server/3-2/12.yml,file deleted because it no longer exists in main +translations/zh-CN/data/release-notes/enterprise-server/3-2/13.yml,file deleted because it no longer exists in main +translations/zh-CN/data/release-notes/enterprise-server/3-2/14.yml,file deleted because it no longer exists in main +translations/zh-CN/data/release-notes/enterprise-server/3-2/15.yml,file deleted because it no longer exists in main +translations/zh-CN/data/release-notes/enterprise-server/3-2/16.yml,file deleted because it no longer exists in main +translations/zh-CN/data/release-notes/enterprise-server/3-2/18.yml,file deleted because it no longer exists in main +translations/zh-CN/data/release-notes/enterprise-server/3-2/2.yml,file deleted because it no longer exists in main +translations/zh-CN/data/release-notes/enterprise-server/3-2/3.yml,file deleted because it no longer exists in main +translations/zh-CN/data/release-notes/enterprise-server/3-2/4.yml,file deleted because it no longer exists in main +translations/zh-CN/data/release-notes/enterprise-server/3-2/5.yml,file deleted because it no longer exists in main +translations/zh-CN/data/release-notes/enterprise-server/3-2/6.yml,file deleted because it no longer exists in main +translations/zh-CN/data/release-notes/enterprise-server/3-2/7.yml,file deleted because it no longer exists in main +translations/zh-CN/data/release-notes/enterprise-server/3-2/8.yml,file deleted because it no longer exists in main +translations/zh-CN/data/release-notes/enterprise-server/3-2/9.yml,file deleted because it no longer exists in main translations/zh-CN/data/reusables/actions/hardware-requirements-3.6.md,file deleted because it no longer exists in main translations/zh-CN/data/reusables/actions/link-to-example-library.md,file deleted because it no longer exists in main translations/zh-CN/data/reusables/actions/perform-blob-storage-precheck.md,file deleted because it no longer exists in main @@ -520,7 +643,6 @@ translations/zh-CN/content/admin/user-management/migrating-data-to-and-from-your translations/zh-CN/content/admin/user-management/migrating-data-to-and-from-your-enterprise/migrating-data-to-your-enterprise.md,broken liquid tags translations/zh-CN/content/authentication/authenticating-with-saml-single-sign-on/authorizing-a-personal-access-token-for-use-with-saml-single-sign-on.md,rendering error translations/zh-CN/content/authentication/authenticating-with-saml-single-sign-on/authorizing-an-ssh-key-for-use-with-saml-single-sign-on.md,rendering error -translations/zh-CN/content/authentication/connecting-to-github-with-ssh/about-ssh.md,broken liquid tags translations/zh-CN/content/authentication/connecting-to-github-with-ssh/adding-a-new-ssh-key-to-your-github-account.md,rendering error translations/zh-CN/content/authentication/connecting-to-github-with-ssh/checking-for-existing-ssh-keys.md,rendering error translations/zh-CN/content/authentication/connecting-to-github-with-ssh/generating-a-new-ssh-key-and-adding-it-to-the-ssh-agent.md,rendering error @@ -543,7 +665,6 @@ translations/zh-CN/content/authentication/managing-commit-signature-verification translations/zh-CN/content/authentication/managing-commit-signature-verification/associating-an-email-with-your-gpg-key.md,broken liquid tags translations/zh-CN/content/authentication/managing-commit-signature-verification/displaying-verification-statuses-for-all-of-your-commits.md,rendering error translations/zh-CN/content/authentication/managing-commit-signature-verification/index.md,broken liquid tags -translations/zh-CN/content/authentication/managing-commit-signature-verification/telling-git-about-your-signing-key.md,broken liquid tags translations/zh-CN/content/authentication/securing-your-account-with-two-factor-authentication-2fa/about-two-factor-authentication.md,broken liquid tags translations/zh-CN/content/authentication/securing-your-account-with-two-factor-authentication-2fa/accessing-github-using-two-factor-authentication.md,broken liquid tags translations/zh-CN/content/authentication/securing-your-account-with-two-factor-authentication-2fa/configuring-two-factor-authentication.md,rendering error @@ -814,6 +935,7 @@ translations/zh-CN/content/organizations/managing-organization-settings/managing translations/zh-CN/content/organizations/managing-organization-settings/managing-the-default-branch-name-for-repositories-in-your-organization.md,rendering error translations/zh-CN/content/organizations/managing-organization-settings/managing-the-forking-policy-for-your-organization.md,broken liquid tags translations/zh-CN/content/organizations/managing-organization-settings/setting-permissions-for-adding-outside-collaborators.md,rendering error +translations/zh-CN/content/organizations/managing-peoples-access-to-your-organization-with-roles/managing-custom-repository-roles-for-an-organization.md,broken liquid tags translations/zh-CN/content/organizations/managing-peoples-access-to-your-organization-with-roles/managing-security-managers-in-your-organization.md,rendering error translations/zh-CN/content/organizations/managing-saml-single-sign-on-for-your-organization/configuring-saml-single-sign-on-and-scim-using-okta.md,broken liquid tags translations/zh-CN/content/organizations/organizing-members-into-teams/about-teams.md,broken liquid tags @@ -894,7 +1016,6 @@ translations/zh-CN/content/repositories/releasing-projects-on-github/comparing-r translations/zh-CN/content/repositories/releasing-projects-on-github/linking-to-releases.md,rendering error translations/zh-CN/content/repositories/releasing-projects-on-github/managing-releases-in-a-repository.md,rendering error translations/zh-CN/content/repositories/working-with-files/managing-files/adding-a-file-to-a-repository.md,broken liquid tags -translations/zh-CN/content/repositories/working-with-files/managing-large-files/about-git-large-file-storage.md,broken liquid tags translations/zh-CN/content/repositories/working-with-files/managing-large-files/about-large-files-on-github.md,broken liquid tags translations/zh-CN/content/repositories/working-with-files/using-files/getting-permanent-links-to-files.md,broken liquid tags translations/zh-CN/content/repositories/working-with-files/using-files/working-with-non-code-files.md,rendering error @@ -948,29 +1069,6 @@ translations/zh-CN/data/glossaries/external.yml,broken liquid tags translations/zh-CN/data/learning-tracks/actions.yml,broken liquid tags translations/zh-CN/data/learning-tracks/admin.yml,broken liquid tags translations/zh-CN/data/learning-tracks/code-security.yml,broken liquid tags -translations/zh-CN/data/release-notes/enterprise-server/2-20/15.yml,rendering error -translations/zh-CN/data/release-notes/enterprise-server/2-21/17.yml,rendering error -translations/zh-CN/data/release-notes/enterprise-server/2-21/6.yml,rendering error -translations/zh-CN/data/release-notes/enterprise-server/2-22/0.yml,rendering error -translations/zh-CN/data/release-notes/enterprise-server/2-22/1.yml,rendering error -translations/zh-CN/data/release-notes/enterprise-server/2-22/2.yml,rendering error -translations/zh-CN/data/release-notes/enterprise-server/2-22/22.yml,broken liquid tags -translations/zh-CN/data/release-notes/enterprise-server/2-22/3.yml,rendering error -translations/zh-CN/data/release-notes/enterprise-server/2-22/7.yml,rendering error -translations/zh-CN/data/release-notes/enterprise-server/2-22/8.yml,rendering error -translations/zh-CN/data/release-notes/enterprise-server/2-22/9.yml,rendering error -translations/zh-CN/data/release-notes/enterprise-server/3-0/0.yml,rendering error -translations/zh-CN/data/release-notes/enterprise-server/3-0/1.yml,rendering error -translations/zh-CN/data/release-notes/enterprise-server/3-0/2.yml,rendering error -translations/zh-CN/data/release-notes/enterprise-server/3-0/3.yml,rendering error -translations/zh-CN/data/release-notes/enterprise-server/3-1/0-rc1.yml,broken liquid tags -translations/zh-CN/data/release-notes/enterprise-server/3-1/0.yml,rendering error -translations/zh-CN/data/release-notes/enterprise-server/3-1/1.yml,rendering error -translations/zh-CN/data/release-notes/enterprise-server/3-1/2.yml,rendering error -translations/zh-CN/data/release-notes/enterprise-server/3-1/4.yml,rendering error -translations/zh-CN/data/release-notes/enterprise-server/3-2/0-rc1.yml,rendering error -translations/zh-CN/data/release-notes/enterprise-server/3-2/0.yml,rendering error -translations/zh-CN/data/release-notes/enterprise-server/3-2/17.yml,rendering error translations/zh-CN/data/release-notes/enterprise-server/3-3/0-rc1.yml,rendering error translations/zh-CN/data/release-notes/enterprise-server/3-3/0.yml,rendering error translations/zh-CN/data/release-notes/enterprise-server/3-3/12.yml,rendering error diff --git a/translations/log/msft-es-resets.csv b/translations/log/msft-es-resets.csv index 79ab92d023..cb5eae60df 100644 --- a/translations/log/msft-es-resets.csv +++ b/translations/log/msft-es-resets.csv @@ -220,6 +220,129 @@ translations/es-ES/content/sponsors/receiving-sponsorships-through-github-sponso translations/es-ES/data/glossaries/internal.yml,file deleted because it no longer exists in main translations/es-ES/data/graphql/ghes-3.1/graphql_previews.enterprise.yml,file deleted because it no longer exists in main translations/es-ES/data/graphql/ghes-3.2/graphql_previews.enterprise.yml,file deleted because it no longer exists in main +translations/es-ES/data/release-notes/enterprise-server/2-20/0.yml,file deleted because it no longer exists in main +translations/es-ES/data/release-notes/enterprise-server/2-20/1.yml,file deleted because it no longer exists in main +translations/es-ES/data/release-notes/enterprise-server/2-20/10.yml,file deleted because it no longer exists in main +translations/es-ES/data/release-notes/enterprise-server/2-20/11.yml,file deleted because it no longer exists in main +translations/es-ES/data/release-notes/enterprise-server/2-20/12.yml,file deleted because it no longer exists in main +translations/es-ES/data/release-notes/enterprise-server/2-20/13.yml,file deleted because it no longer exists in main +translations/es-ES/data/release-notes/enterprise-server/2-20/14.yml,file deleted because it no longer exists in main +translations/es-ES/data/release-notes/enterprise-server/2-20/16.yml,file deleted because it no longer exists in main +translations/es-ES/data/release-notes/enterprise-server/2-20/17.yml,file deleted because it no longer exists in main +translations/es-ES/data/release-notes/enterprise-server/2-20/18.yml,file deleted because it no longer exists in main +translations/es-ES/data/release-notes/enterprise-server/2-20/19.yml,file deleted because it no longer exists in main +translations/es-ES/data/release-notes/enterprise-server/2-20/2.yml,file deleted because it no longer exists in main +translations/es-ES/data/release-notes/enterprise-server/2-20/20.yml,file deleted because it no longer exists in main +translations/es-ES/data/release-notes/enterprise-server/2-20/21.yml,file deleted because it no longer exists in main +translations/es-ES/data/release-notes/enterprise-server/2-20/22.yml,file deleted because it no longer exists in main +translations/es-ES/data/release-notes/enterprise-server/2-20/23.yml,file deleted because it no longer exists in main +translations/es-ES/data/release-notes/enterprise-server/2-20/24.yml,file deleted because it no longer exists in main +translations/es-ES/data/release-notes/enterprise-server/2-20/3.yml,file deleted because it no longer exists in main +translations/es-ES/data/release-notes/enterprise-server/2-20/4.yml,file deleted because it no longer exists in main +translations/es-ES/data/release-notes/enterprise-server/2-20/5.yml,file deleted because it no longer exists in main +translations/es-ES/data/release-notes/enterprise-server/2-20/6.yml,file deleted because it no longer exists in main +translations/es-ES/data/release-notes/enterprise-server/2-20/7.yml,file deleted because it no longer exists in main +translations/es-ES/data/release-notes/enterprise-server/2-20/8.yml,file deleted because it no longer exists in main +translations/es-ES/data/release-notes/enterprise-server/2-20/9.yml,file deleted because it no longer exists in main +translations/es-ES/data/release-notes/enterprise-server/2-21/0.yml,file deleted because it no longer exists in main +translations/es-ES/data/release-notes/enterprise-server/2-21/1.yml,file deleted because it no longer exists in main +translations/es-ES/data/release-notes/enterprise-server/2-21/10.yml,file deleted because it no longer exists in main +translations/es-ES/data/release-notes/enterprise-server/2-21/11.yml,file deleted because it no longer exists in main +translations/es-ES/data/release-notes/enterprise-server/2-21/12.yml,file deleted because it no longer exists in main +translations/es-ES/data/release-notes/enterprise-server/2-21/13.yml,file deleted because it no longer exists in main +translations/es-ES/data/release-notes/enterprise-server/2-21/14.yml,file deleted because it no longer exists in main +translations/es-ES/data/release-notes/enterprise-server/2-21/15.yml,file deleted because it no longer exists in main +translations/es-ES/data/release-notes/enterprise-server/2-21/16.yml,file deleted because it no longer exists in main +translations/es-ES/data/release-notes/enterprise-server/2-21/18.yml,file deleted because it no longer exists in main +translations/es-ES/data/release-notes/enterprise-server/2-21/19.yml,file deleted because it no longer exists in main +translations/es-ES/data/release-notes/enterprise-server/2-21/2.yml,file deleted because it no longer exists in main +translations/es-ES/data/release-notes/enterprise-server/2-21/20.yml,file deleted because it no longer exists in main +translations/es-ES/data/release-notes/enterprise-server/2-21/21.yml,file deleted because it no longer exists in main +translations/es-ES/data/release-notes/enterprise-server/2-21/22.yml,file deleted because it no longer exists in main +translations/es-ES/data/release-notes/enterprise-server/2-21/23.yml,file deleted because it no longer exists in main +translations/es-ES/data/release-notes/enterprise-server/2-21/3.yml,file deleted because it no longer exists in main +translations/es-ES/data/release-notes/enterprise-server/2-21/4.yml,file deleted because it no longer exists in main +translations/es-ES/data/release-notes/enterprise-server/2-21/5.yml,file deleted because it no longer exists in main +translations/es-ES/data/release-notes/enterprise-server/2-21/7.yml,file deleted because it no longer exists in main +translations/es-ES/data/release-notes/enterprise-server/2-21/8.yml,file deleted because it no longer exists in main +translations/es-ES/data/release-notes/enterprise-server/2-21/9.yml,file deleted because it no longer exists in main +translations/es-ES/data/release-notes/enterprise-server/2-22/10.yml,file deleted because it no longer exists in main +translations/es-ES/data/release-notes/enterprise-server/2-22/11.yml,file deleted because it no longer exists in main +translations/es-ES/data/release-notes/enterprise-server/2-22/12.yml,file deleted because it no longer exists in main +translations/es-ES/data/release-notes/enterprise-server/2-22/13.yml,file deleted because it no longer exists in main +translations/es-ES/data/release-notes/enterprise-server/2-22/14.yml,file deleted because it no longer exists in main +translations/es-ES/data/release-notes/enterprise-server/2-22/15.yml,file deleted because it no longer exists in main +translations/es-ES/data/release-notes/enterprise-server/2-22/16.yml,file deleted because it no longer exists in main +translations/es-ES/data/release-notes/enterprise-server/2-22/17.yml,file deleted because it no longer exists in main +translations/es-ES/data/release-notes/enterprise-server/2-22/18.yml,file deleted because it no longer exists in main +translations/es-ES/data/release-notes/enterprise-server/2-22/19.yml,file deleted because it no longer exists in main +translations/es-ES/data/release-notes/enterprise-server/2-22/20.yml,file deleted because it no longer exists in main +translations/es-ES/data/release-notes/enterprise-server/2-22/21.yml,file deleted because it no longer exists in main +translations/es-ES/data/release-notes/enterprise-server/2-22/22.yml,file deleted because it no longer exists in main +translations/es-ES/data/release-notes/enterprise-server/2-22/4.yml,file deleted because it no longer exists in main +translations/es-ES/data/release-notes/enterprise-server/2-22/5.yml,file deleted because it no longer exists in main +translations/es-ES/data/release-notes/enterprise-server/2-22/6.yml,file deleted because it no longer exists in main +translations/es-ES/data/release-notes/enterprise-server/3-0/0-rc1.yml,file deleted because it no longer exists in main +translations/es-ES/data/release-notes/enterprise-server/3-0/0-rc2.yml,file deleted because it no longer exists in main +translations/es-ES/data/release-notes/enterprise-server/3-0/10.yml,file deleted because it no longer exists in main +translations/es-ES/data/release-notes/enterprise-server/3-0/11.yml,file deleted because it no longer exists in main +translations/es-ES/data/release-notes/enterprise-server/3-0/12.yml,file deleted because it no longer exists in main +translations/es-ES/data/release-notes/enterprise-server/3-0/13.yml,file deleted because it no longer exists in main +translations/es-ES/data/release-notes/enterprise-server/3-0/14.yml,file deleted because it no longer exists in main +translations/es-ES/data/release-notes/enterprise-server/3-0/15.yml,file deleted because it no longer exists in main +translations/es-ES/data/release-notes/enterprise-server/3-0/16.yml,file deleted because it no longer exists in main +translations/es-ES/data/release-notes/enterprise-server/3-0/17.yml,file deleted because it no longer exists in main +translations/es-ES/data/release-notes/enterprise-server/3-0/18.yml,file deleted because it no longer exists in main +translations/es-ES/data/release-notes/enterprise-server/3-0/19.yml,file deleted because it no longer exists in main +translations/es-ES/data/release-notes/enterprise-server/3-0/20.yml,file deleted because it no longer exists in main +translations/es-ES/data/release-notes/enterprise-server/3-0/21.yml,file deleted because it no longer exists in main +translations/es-ES/data/release-notes/enterprise-server/3-0/22.yml,file deleted because it no longer exists in main +translations/es-ES/data/release-notes/enterprise-server/3-0/23.yml,file deleted because it no longer exists in main +translations/es-ES/data/release-notes/enterprise-server/3-0/24.yml,file deleted because it no longer exists in main +translations/es-ES/data/release-notes/enterprise-server/3-0/25.yml,file deleted because it no longer exists in main +translations/es-ES/data/release-notes/enterprise-server/3-0/4.yml,file deleted because it no longer exists in main +translations/es-ES/data/release-notes/enterprise-server/3-0/5.yml,file deleted because it no longer exists in main +translations/es-ES/data/release-notes/enterprise-server/3-0/6.yml,file deleted because it no longer exists in main +translations/es-ES/data/release-notes/enterprise-server/3-0/7.yml,file deleted because it no longer exists in main +translations/es-ES/data/release-notes/enterprise-server/3-0/8.yml,file deleted because it no longer exists in main +translations/es-ES/data/release-notes/enterprise-server/3-0/9.yml,file deleted because it no longer exists in main +translations/es-ES/data/release-notes/enterprise-server/3-1/0-rc1.yml,file deleted because it no longer exists in main +translations/es-ES/data/release-notes/enterprise-server/3-1/10.yml,file deleted because it no longer exists in main +translations/es-ES/data/release-notes/enterprise-server/3-1/11.yml,file deleted because it no longer exists in main +translations/es-ES/data/release-notes/enterprise-server/3-1/12.yml,file deleted because it no longer exists in main +translations/es-ES/data/release-notes/enterprise-server/3-1/13.yml,file deleted because it no longer exists in main +translations/es-ES/data/release-notes/enterprise-server/3-1/14.yml,file deleted because it no longer exists in main +translations/es-ES/data/release-notes/enterprise-server/3-1/15.yml,file deleted because it no longer exists in main +translations/es-ES/data/release-notes/enterprise-server/3-1/16.yml,file deleted because it no longer exists in main +translations/es-ES/data/release-notes/enterprise-server/3-1/17.yml,file deleted because it no longer exists in main +translations/es-ES/data/release-notes/enterprise-server/3-1/18.yml,file deleted because it no longer exists in main +translations/es-ES/data/release-notes/enterprise-server/3-1/19.yml,file deleted because it no longer exists in main +translations/es-ES/data/release-notes/enterprise-server/3-1/20.yml,file deleted because it no longer exists in main +translations/es-ES/data/release-notes/enterprise-server/3-1/21.yml,file deleted because it no longer exists in main +translations/es-ES/data/release-notes/enterprise-server/3-1/22.yml,file deleted because it no longer exists in main +translations/es-ES/data/release-notes/enterprise-server/3-1/3.yml,file deleted because it no longer exists in main +translations/es-ES/data/release-notes/enterprise-server/3-1/5.yml,file deleted because it no longer exists in main +translations/es-ES/data/release-notes/enterprise-server/3-1/6.yml,file deleted because it no longer exists in main +translations/es-ES/data/release-notes/enterprise-server/3-1/7.yml,file deleted because it no longer exists in main +translations/es-ES/data/release-notes/enterprise-server/3-1/8.yml,file deleted because it no longer exists in main +translations/es-ES/data/release-notes/enterprise-server/3-1/9.yml,file deleted because it no longer exists in main +translations/es-ES/data/release-notes/enterprise-server/3-2/1.yml,file deleted because it no longer exists in main +translations/es-ES/data/release-notes/enterprise-server/3-2/10.yml,file deleted because it no longer exists in main +translations/es-ES/data/release-notes/enterprise-server/3-2/11.yml,file deleted because it no longer exists in main +translations/es-ES/data/release-notes/enterprise-server/3-2/12.yml,file deleted because it no longer exists in main +translations/es-ES/data/release-notes/enterprise-server/3-2/13.yml,file deleted because it no longer exists in main +translations/es-ES/data/release-notes/enterprise-server/3-2/14.yml,file deleted because it no longer exists in main +translations/es-ES/data/release-notes/enterprise-server/3-2/15.yml,file deleted because it no longer exists in main +translations/es-ES/data/release-notes/enterprise-server/3-2/16.yml,file deleted because it no longer exists in main +translations/es-ES/data/release-notes/enterprise-server/3-2/18.yml,file deleted because it no longer exists in main +translations/es-ES/data/release-notes/enterprise-server/3-2/2.yml,file deleted because it no longer exists in main +translations/es-ES/data/release-notes/enterprise-server/3-2/3.yml,file deleted because it no longer exists in main +translations/es-ES/data/release-notes/enterprise-server/3-2/4.yml,file deleted because it no longer exists in main +translations/es-ES/data/release-notes/enterprise-server/3-2/5.yml,file deleted because it no longer exists in main +translations/es-ES/data/release-notes/enterprise-server/3-2/6.yml,file deleted because it no longer exists in main +translations/es-ES/data/release-notes/enterprise-server/3-2/7.yml,file deleted because it no longer exists in main +translations/es-ES/data/release-notes/enterprise-server/3-2/8.yml,file deleted because it no longer exists in main +translations/es-ES/data/release-notes/enterprise-server/3-2/9.yml,file deleted because it no longer exists in main translations/es-ES/data/reusables/actions/hardware-requirements-3.6.md,file deleted because it no longer exists in main translations/es-ES/data/reusables/actions/jobs/section-using-a-build-matrix-for-your-jobs-strategy.md,file deleted because it no longer exists in main translations/es-ES/data/reusables/actions/link-to-example-library.md,file deleted because it no longer exists in main @@ -353,7 +476,7 @@ translations/es-ES/content/actions/examples/using-concurrency-expressions-and-a- translations/es-ES/content/actions/hosting-your-own-runners/about-self-hosted-runners.md,rendering error translations/es-ES/content/actions/hosting-your-own-runners/adding-self-hosted-runners.md,rendering error translations/es-ES/content/actions/hosting-your-own-runners/autoscaling-with-self-hosted-runners.md,rendering error -translations/es-ES/content/actions/hosting-your-own-runners/managing-access-to-self-hosted-runners-using-groups.md,broken liquid tags +translations/es-ES/content/actions/hosting-your-own-runners/managing-access-to-self-hosted-runners-using-groups.md,rendering error translations/es-ES/content/actions/hosting-your-own-runners/monitoring-and-troubleshooting-self-hosted-runners.md,rendering error translations/es-ES/content/actions/hosting-your-own-runners/removing-self-hosted-runners.md,rendering error translations/es-ES/content/actions/hosting-your-own-runners/running-scripts-before-or-after-a-job.md,broken liquid tags @@ -542,7 +665,6 @@ translations/es-ES/content/admin/user-management/migrating-data-to-and-from-your translations/es-ES/content/admin/user-management/migrating-data-to-and-from-your-enterprise/migrating-data-to-your-enterprise.md,broken liquid tags translations/es-ES/content/authentication/authenticating-with-saml-single-sign-on/authorizing-a-personal-access-token-for-use-with-saml-single-sign-on.md,rendering error translations/es-ES/content/authentication/authenticating-with-saml-single-sign-on/authorizing-an-ssh-key-for-use-with-saml-single-sign-on.md,rendering error -translations/es-ES/content/authentication/connecting-to-github-with-ssh/about-ssh.md,broken liquid tags translations/es-ES/content/authentication/connecting-to-github-with-ssh/adding-a-new-ssh-key-to-your-github-account.md,rendering error translations/es-ES/content/authentication/connecting-to-github-with-ssh/checking-for-existing-ssh-keys.md,rendering error translations/es-ES/content/authentication/connecting-to-github-with-ssh/generating-a-new-ssh-key-and-adding-it-to-the-ssh-agent.md,rendering error @@ -565,7 +687,6 @@ translations/es-ES/content/authentication/managing-commit-signature-verification translations/es-ES/content/authentication/managing-commit-signature-verification/associating-an-email-with-your-gpg-key.md,broken liquid tags translations/es-ES/content/authentication/managing-commit-signature-verification/displaying-verification-statuses-for-all-of-your-commits.md,rendering error translations/es-ES/content/authentication/managing-commit-signature-verification/index.md,broken liquid tags -translations/es-ES/content/authentication/managing-commit-signature-verification/telling-git-about-your-signing-key.md,broken liquid tags translations/es-ES/content/authentication/securing-your-account-with-two-factor-authentication-2fa/about-two-factor-authentication.md,broken liquid tags translations/es-ES/content/authentication/securing-your-account-with-two-factor-authentication-2fa/accessing-github-using-two-factor-authentication.md,broken liquid tags translations/es-ES/content/authentication/securing-your-account-with-two-factor-authentication-2fa/configuring-two-factor-authentication.md,rendering error @@ -596,7 +717,7 @@ translations/es-ES/content/billing/managing-licenses-for-visual-studio-subscript translations/es-ES/content/billing/managing-licenses-for-visual-studio-subscriptions-with-github-enterprise/setting-up-visual-studio-subscriptions-with-github-enterprise.md,broken liquid tags translations/es-ES/content/billing/managing-your-license-for-github-enterprise/about-licenses-for-github-enterprise.md,broken liquid tags translations/es-ES/content/billing/managing-your-license-for-github-enterprise/downloading-your-license-for-github-enterprise.md,broken liquid tags -translations/es-ES/content/billing/managing-your-license-for-github-enterprise/troubleshooting-license-usage-for-github-enterprise.md,broken liquid tags +translations/es-ES/content/billing/managing-your-license-for-github-enterprise/troubleshooting-license-usage-for-github-enterprise.md,rendering error translations/es-ES/content/billing/managing-your-license-for-github-enterprise/uploading-a-new-license-to-github-enterprise-server.md,broken liquid tags translations/es-ES/content/billing/managing-your-license-for-github-enterprise/viewing-license-usage-for-github-enterprise.md,broken liquid tags translations/es-ES/content/code-security/adopting-github-advanced-security-at-scale/phase-6-rollout-and-scale-secret-scanning.md,rendering error @@ -835,6 +956,7 @@ translations/es-ES/content/organizations/managing-organization-settings/managing translations/es-ES/content/organizations/managing-organization-settings/managing-the-default-branch-name-for-repositories-in-your-organization.md,rendering error translations/es-ES/content/organizations/managing-organization-settings/managing-the-forking-policy-for-your-organization.md,broken liquid tags translations/es-ES/content/organizations/managing-organization-settings/setting-permissions-for-adding-outside-collaborators.md,rendering error +translations/es-ES/content/organizations/managing-peoples-access-to-your-organization-with-roles/managing-custom-repository-roles-for-an-organization.md,broken liquid tags translations/es-ES/content/organizations/managing-peoples-access-to-your-organization-with-roles/managing-security-managers-in-your-organization.md,rendering error translations/es-ES/content/organizations/managing-saml-single-sign-on-for-your-organization/about-identity-and-access-management-with-saml-single-sign-on.md,broken liquid tags translations/es-ES/content/organizations/managing-saml-single-sign-on-for-your-organization/configuring-saml-single-sign-on-and-scim-using-okta.md,broken liquid tags @@ -916,7 +1038,6 @@ translations/es-ES/content/repositories/releasing-projects-on-github/comparing-r translations/es-ES/content/repositories/releasing-projects-on-github/linking-to-releases.md,rendering error translations/es-ES/content/repositories/releasing-projects-on-github/managing-releases-in-a-repository.md,rendering error translations/es-ES/content/repositories/working-with-files/managing-files/adding-a-file-to-a-repository.md,broken liquid tags -translations/es-ES/content/repositories/working-with-files/managing-large-files/about-git-large-file-storage.md,broken liquid tags translations/es-ES/content/repositories/working-with-files/managing-large-files/about-large-files-on-github.md,broken liquid tags translations/es-ES/content/repositories/working-with-files/using-files/getting-permanent-links-to-files.md,broken liquid tags translations/es-ES/content/repositories/working-with-files/using-files/working-with-non-code-files.md,rendering error @@ -971,33 +1092,6 @@ translations/es-ES/data/glossaries/external.yml,broken liquid tags translations/es-ES/data/learning-tracks/actions.yml,broken liquid tags translations/es-ES/data/learning-tracks/admin.yml,broken liquid tags translations/es-ES/data/learning-tracks/code-security.yml,broken liquid tags -translations/es-ES/data/release-notes/enterprise-server/2-20/15.yml,rendering error -translations/es-ES/data/release-notes/enterprise-server/2-21/12.yml,broken liquid tags -translations/es-ES/data/release-notes/enterprise-server/2-21/17.yml,rendering error -translations/es-ES/data/release-notes/enterprise-server/2-21/20.yml,broken liquid tags -translations/es-ES/data/release-notes/enterprise-server/2-21/6.yml,rendering error -translations/es-ES/data/release-notes/enterprise-server/2-22/0.yml,rendering error -translations/es-ES/data/release-notes/enterprise-server/2-22/1.yml,rendering error -translations/es-ES/data/release-notes/enterprise-server/2-22/2.yml,rendering error -translations/es-ES/data/release-notes/enterprise-server/2-22/3.yml,rendering error -translations/es-ES/data/release-notes/enterprise-server/2-22/7.yml,rendering error -translations/es-ES/data/release-notes/enterprise-server/2-22/8.yml,rendering error -translations/es-ES/data/release-notes/enterprise-server/2-22/9.yml,rendering error -translations/es-ES/data/release-notes/enterprise-server/3-0/0.yml,rendering error -translations/es-ES/data/release-notes/enterprise-server/3-0/1.yml,rendering error -translations/es-ES/data/release-notes/enterprise-server/3-0/19.yml,broken liquid tags -translations/es-ES/data/release-notes/enterprise-server/3-0/2.yml,rendering error -translations/es-ES/data/release-notes/enterprise-server/3-0/3.yml,rendering error -translations/es-ES/data/release-notes/enterprise-server/3-1/0-rc1.yml,broken liquid tags -translations/es-ES/data/release-notes/enterprise-server/3-1/0.yml,rendering error -translations/es-ES/data/release-notes/enterprise-server/3-1/1.yml,rendering error -translations/es-ES/data/release-notes/enterprise-server/3-1/11.yml,broken liquid tags -translations/es-ES/data/release-notes/enterprise-server/3-1/2.yml,rendering error -translations/es-ES/data/release-notes/enterprise-server/3-1/4.yml,rendering error -translations/es-ES/data/release-notes/enterprise-server/3-2/0-rc1.yml,rendering error -translations/es-ES/data/release-notes/enterprise-server/3-2/0.yml,rendering error -translations/es-ES/data/release-notes/enterprise-server/3-2/17.yml,rendering error -translations/es-ES/data/release-notes/enterprise-server/3-2/3.yml,broken liquid tags translations/es-ES/data/release-notes/enterprise-server/3-3/0-rc1.yml,rendering error translations/es-ES/data/release-notes/enterprise-server/3-3/0.yml,rendering error translations/es-ES/data/release-notes/enterprise-server/3-3/12.yml,rendering error diff --git a/translations/zh-CN/content/authentication/connecting-to-github-with-ssh/about-ssh.md b/translations/zh-CN/content/authentication/connecting-to-github-with-ssh/about-ssh.md index 294dc0dd7d..8f7f33fa98 100644 --- a/translations/zh-CN/content/authentication/connecting-to-github-with-ssh/about-ssh.md +++ b/translations/zh-CN/content/authentication/connecting-to-github-with-ssh/about-ssh.md @@ -1,6 +1,6 @@ --- -title: About SSH -intro: 'Using the SSH protocol, you can connect and authenticate to remote servers and services. With SSH keys, you can connect to {% data variables.product.product_name %} without supplying your username and {% data variables.product.pat_generic %} at each visit.{% ifversion ssh-commit-verification %} You can also use an SSH key to sign commits.{% endif %}' +title: 关于 SSH +intro: '使用 SSH 协议可以连接远程服务器和服务并向它们验证。 利用 SSH 密钥可以连接到 {% data variables.product.product_name %}，而无需在每次访问时都提供用户名和 {% data variables.product.pat_generic %}。{% ifversion ssh-commit-verification %}还可以使用 SSH 密钥对提交进行签名。{% endif %}' redirect_from: - /articles/about-ssh - /github/authenticating-to-github/about-ssh @@ -12,27 +12,29 @@ versions: ghec: '*' topics: - SSH +ms.openlocfilehash: 51a72821217e5d47092ed77e923b38f4cf248010 +ms.sourcegitcommit: a0ad3bfe2a99c3092e76ca9b3d476cf30988ca55 +ms.translationtype: HT +ms.contentlocale: zh-CN +ms.lasthandoff: 10/28/2022 +ms.locfileid: '148118977' --- +{% data reusables.ssh.about-ssh %} 有关 SSH 的详细信息，请参阅 Wikipedia 上的[安全外壳](https://en.wikipedia.org/wiki/Secure_Shell)。 -{% data reusables.ssh.about-ssh %} For more information about SSH, see [Secure Shell](https://en.wikipedia.org/wiki/Secure_Shell) on Wikipedia. +设置 SSH 时，需要生成新的 SSH 私钥并将其添加到 SSH 代理中。 使用密钥进行身份验证{% ifversion ssh-commit-verification %}或对提交进行签名{% endif %}之前，还必须将 SSH 公钥添加到 {% data variables.product.product_name %} 上的帐户中。 有关详细信息，请参阅“[生成新的 SSH 密钥并将其添加到 ssh-agent](/authentication/connecting-to-github-with-ssh/generating-a-new-ssh-key-and-adding-it-to-the-ssh-agent)”{% ifversion ssh-commit-verification %}、{% else %}和{% endif %}“[将新的 SSH 密钥添加到 {% data variables.product.prodname_dotcom %} 帐户](/authentication/connecting-to-github-with-ssh/adding-a-new-ssh-key-to-your-github-account)”{% ifversion ssh-commit-verification %}和“[关于提交签名验证](/articles/about-commit-signature-verification){% endif %}”。 -When you set up SSH, you will need to generate a new private SSH key and add it to the SSH agent. You must also add the public SSH key to your account on {% data variables.product.product_name %} before you use the key to authenticate{% ifversion ssh-commit-verification %} or sign commits{% endif %}. For more information, see "[Generating a new SSH key and adding it to the ssh-agent](/authentication/connecting-to-github-with-ssh/generating-a-new-ssh-key-and-adding-it-to-the-ssh-agent)"{% ifversion ssh-commit-verification %}, {% else %} and{% endif %} "[Adding a new SSH key to your {% data variables.product.prodname_dotcom %} account](/authentication/connecting-to-github-with-ssh/adding-a-new-ssh-key-to-your-github-account){% ifversion ssh-commit-verification %}" and "[About commit signature verification](/articles/about-commit-signature-verification){% endif %}." +您可以使用硬件安全密钥来进一步保护 SSH 密钥，当密钥对用于通过 SSH 进行身份验证时，需要将物理硬件安全密钥附加到计算机上。 您还可以通过将密钥添加到 ssh 代理并使用密码来保护您的 SSH 密钥。 有关详细信息，请参阅“[使用 SSH 密钥密码](/authentication/connecting-to-github-with-ssh/working-with-ssh-key-passphrases)”。 -You can further secure your SSH key by using a hardware security key, which requires the physical hardware security key to be attached to your computer when the key pair is used to authenticate with SSH. You can also secure your SSH key by adding your key to the ssh-agent and using a passphrase. For more information, see "[Working with SSH key passphrases](/authentication/connecting-to-github-with-ssh/working-with-ssh-key-passphrases)." +{% ifversion fpt or ghec %}若要将 SSH 密钥与使用 SAML 单一登录的组织拥有的存储库一起使用，必须授权该密钥。 有关详细信息，请参阅 {% data variables.product.prodname_ghe_cloud %} 文档中的“[授权 SSH 密钥用于 SAML 单一登录](/enterprise-cloud@latest/authentication/authenticating-with-saml-single-sign-on/authorizing-an-ssh-key-for-use-with-saml-single-sign-on){% ifversion fpt %}”。{% else %}."{% endif %}{% endif %} -{% ifversion fpt or ghec %}To use your SSH key with a repository owned by an organization that uses SAML single sign-on, you must authorize the key. For more information, see "[Authorizing an SSH key for use with SAML single sign-on](/enterprise-cloud@latest/authentication/authenticating-with-saml-single-sign-on/authorizing-an-ssh-key-for-use-with-saml-single-sign-on){% ifversion fpt %}" in the {% data variables.product.prodname_ghe_cloud %} documentation.{% else %}."{% endif %}{% endif %} +为了保持帐户安全，您可以定期检查您的 SSH 密钥列表，并撤销任何无效或已泄漏的密钥。 有关详细信息，请参阅“[查看 SSH 密钥](/github/authenticating-to-github/reviewing-your-ssh-keys)”。 -To maintain account security, you can regularly review your SSH keys list and revoke any keys that are invalid or have been compromised. For more information, see "[Reviewing your SSH keys](/github/authenticating-to-github/reviewing-your-ssh-keys)." - -{% ifversion fpt or ghec %} -If you haven't used your SSH key for a year, then {% data variables.product.prodname_dotcom %} will automatically delete your inactive SSH key as a security precaution. For more information, see "[Deleted or missing SSH keys](/articles/deleted-or-missing-ssh-keys)." +{% ifversion fpt or ghec %} 如果一年没有使用 SSH 密钥，则作为安全预防措施，{% data variables.product.prodname_dotcom %} 将自动删除你的非活动 SSH 密钥。 有关详细信息，请参阅“[已删除或缺少的 SSH 密钥](/articles/deleted-or-missing-ssh-keys)”。 {% endif %} -{% ifversion fpt %} -Organizations that use {% data variables.product.prodname_ghe_cloud %} can provide SSH certificates, which members can use to access that organization's repositories without adding the certificate to their account on {% data variables.product.product_name %}. If you're using an SSH certificate, you cannot use the certificate to access forks of the organization's repositories, if the fork is owned by your personal account. For more information, see "[About SSH certificate authorities](/enterprise-cloud@latest/organizations/managing-git-access-to-your-organizations-repositories/about-ssh-certificate-authorities)" in the {% data variables.product.prodname_ghe_cloud %} documentation. -{% else ghec or ghes or ghae %} -If you're a member of an organization that provides SSH certificates, you can use your certificate to access that organization's repositories without adding the certificate to your account on {% data variables.product.product_name %}. You cannot use your certificate to access forks of the organization's repositories, if the forks is owned by your personal account. For more information, see "[About SSH certificate authorities](/organizations/managing-git-access-to-your-organizations-repositories/about-ssh-certificate-authorities)." +{% ifversion fpt %} 使用 {% data variables.product.prodname_ghe_cloud %} 的组织可以提供 SSH 证书，成员可以使用该证书访问组织的存储库，而无需将其添加到他们在 {% data variables.product.product_name %} 上的帐户。 如果使用 SSH 证书，当分支为个人帐户所有时，将无法使用该证书访问组织存储库的分支。 有关详细信息，请参阅 {% data variables.product.prodname_ghe_cloud %} 文档中的“[关于 SSH 证书颁发机构](/enterprise-cloud@latest/organizations/managing-git-access-to-your-organizations-repositories/about-ssh-certificate-authorities)”。 +{% else ghec or ghes or ghae %} 如果你是提供 SSH 证书的组织成员，可以使用证书来访问组织的存储库，而无需添加证书到你在 {% data variables.product.product_name %} 上的帐户。 当分支为个人帐户所有时，将无法使用该证书访问组织存储库的分支。 有关详细信息，请参阅“[关于 SSH 证书颁发机构](/organizations/managing-git-access-to-your-organizations-repositories/about-ssh-certificate-authorities)”。 {% endif %} -## Further reading +## 延伸阅读 -- "[Troubleshooting SSH](/articles/troubleshooting-ssh)" +- [SSH 故障排除](/articles/troubleshooting-ssh) diff --git a/translations/zh-CN/content/authentication/managing-commit-signature-verification/telling-git-about-your-signing-key.md b/translations/zh-CN/content/authentication/managing-commit-signature-verification/telling-git-about-your-signing-key.md index 1b1c1fbd9f..6eccb1a0e3 100644 --- a/translations/zh-CN/content/authentication/managing-commit-signature-verification/telling-git-about-your-signing-key.md +++ b/translations/zh-CN/content/authentication/managing-commit-signature-verification/telling-git-about-your-signing-key.md @@ -1,6 +1,6 @@ --- -title: Telling Git about your signing key -intro: 'To sign commits locally, you need to inform Git that there''s a GPG{% ifversion ssh-commit-verification %}, SSH,{% endif %} or X.509 key you''d like to use.' +title: 将您的签名密钥告知 Git +intro: '要在本地对提交进行签名，需要向 Git 通知你要使用的 GPG{% ifversion ssh-commit-verification %}、SSH{% endif %} 或 X.509 密钥。' redirect_from: - /articles/telling-git-about-your-gpg-key - /articles/telling-git-about-your-signing-key @@ -15,38 +15,39 @@ topics: - Identity - Access management shortTitle: Tell Git your signing key +ms.openlocfilehash: e78306bb1519f2b7f51ab6bc039bff0b982e48cf +ms.sourcegitcommit: a0ad3bfe2a99c3092e76ca9b3d476cf30988ca55 +ms.translationtype: HT +ms.contentlocale: zh-CN +ms.lasthandoff: 10/28/2022 +ms.locfileid: '148118993' --- {% mac %} -## Telling Git about your GPG key +## 将您的 GPG 密钥告知 Git -If you're using a GPG key that matches your committer identity and your verified email address associated with your account on {% ifversion ghae %}{% data variables.product.product_name %}{% else %}{% data variables.location.product_location %}{% endif %}, then you can begin signing commits and signing tags. +如果您使用与您的提交者身份以及 {% ifversion ghae %}{% data variables.product.product_name %}{% else %}{% data variables.location.product_location %}{% endif %} 上帐户关联的已验证电子邮件地址相匹配的 GPG 密钥，则可以开始对提交和标签进行签名。 {% note %} -If you don't have a GPG key that matches your committer identity, you need to associate an email with an existing key. For more information, see "[Associating an email with your GPG key](/articles/associating-an-email-with-your-gpg-key)". +如果您没有与提交者身份匹配的 GPG 密钥，则需要将电子邮件与现有密钥关联。 有关详细信息，请参阅“[将电子邮件与 GPG 密钥关联](/articles/associating-an-email-with-your-gpg-key)”。 {% endnote %} -If you have multiple GPG keys, you need to tell Git which one to use. +如果您有多个 GPG 密钥，则需要告知 Git 要使用哪一个。 -{% data reusables.command_line.open_the_multi_os_terminal %} -{% data reusables.gpg.configure-gpg-signing %} -{% data reusables.gpg.list-keys-with-note %} -{% data reusables.gpg.copy-gpg-key-id %} -{% data reusables.gpg.paste-gpg-key-id %} -{% data reusables.gpg.set-auto-sign %} -1. If you aren't using the GPG suite, run the following command in the `zsh` shell to add the GPG key to your `.zshrc` file, if it exists, or your `.zprofile` file: +{% data reusables.command_line.open_the_multi_os_terminal %} {% data reusables.gpg.configure-gpg-signing %} {% data reusables.gpg.list-keys-with-note %} {% data reusables.gpg.copy-gpg-key-id %} {% data reusables.gpg.paste-gpg-key-id %} {% data reusables.gpg.set-auto-sign %} +1. 如果没有使用 GPG 套件，请在 `zsh` shell 中运行以下命令，将 GPG 密钥添加到 `.zshrc` 文件（如果存在）或 `.zprofile` 文件： ```shell $ if [ -r ~/.zshrc ]; then echo 'export GPG_TTY=$(tty)' >> ~/.zshrc; \ else echo 'export GPG_TTY=$(tty)' >> ~/.zprofile; fi ``` - Alternatively, if you use the `bash` shell, run this command: + 或者，如果使用 `bash` shell，请运行以下命令： ```shell $ if [ -r ~/.bash_profile ]; then echo 'export GPG_TTY=$(tty)' >> ~/.bash_profile; \ else echo 'export GPG_TTY=$(tty)' >> ~/.profile; fi ``` -1. Optionally, to prompt you to enter a PIN or passphrase when required, install `pinentry-mac`. For example, using [Homebrew](https://brew.sh/): +1. （可选）若要在需要时提示你输入 PIN 或密码，请安装 `pinentry-mac`。 例如，使用 [Homebrew](https://brew.sh/)： ```shell $ brew install pinentry-mac $ echo "pinentry-program $(which pinentry-mac)" >> ~/.gnupg/gpg-agent.conf @@ -57,70 +58,56 @@ If you have multiple GPG keys, you need to tell Git which one to use. {% windows %} -## Telling Git about your GPG key +## 将您的 GPG 密钥告知 Git -If you're using a GPG key that matches your committer identity and your verified email address associated with your account on {% ifversion ghae %}{% data variables.product.product_name %}{% else %}{% data variables.location.product_location %}{% endif %}, then you can begin signing commits and signing tags. +如果您使用与您的提交者身份以及 {% ifversion ghae %}{% data variables.product.product_name %}{% else %}{% data variables.location.product_location %}{% endif %} 上帐户关联的已验证电子邮件地址相匹配的 GPG 密钥，则可以开始对提交和标签进行签名。 {% note %} -If you don't have a GPG key that matches your committer identity, you need to associate an email with an existing key. For more information, see "[Associating an email with your GPG key](/articles/associating-an-email-with-your-gpg-key)". +如果您没有与提交者身份匹配的 GPG 密钥，则需要将电子邮件与现有密钥关联。 有关详细信息，请参阅“[将电子邮件与 GPG 密钥关联](/articles/associating-an-email-with-your-gpg-key)”。 {% endnote %} -If you have multiple GPG keys, you need to tell Git which one to use. +如果您有多个 GPG 密钥，则需要告知 Git 要使用哪一个。 -{% data reusables.command_line.open_the_multi_os_terminal %} -{% data reusables.gpg.configure-gpg-signing %} -{% data reusables.gpg.list-keys-with-note %} -{% data reusables.gpg.copy-gpg-key-id %} -{% data reusables.gpg.paste-gpg-key-id %} -{% data reusables.gpg.set-auto-sign %} +{% data reusables.command_line.open_the_multi_os_terminal %} {% data reusables.gpg.configure-gpg-signing %} {% data reusables.gpg.list-keys-with-note %} {% data reusables.gpg.copy-gpg-key-id %} {% data reusables.gpg.paste-gpg-key-id %} {% data reusables.gpg.set-auto-sign %} {% endwindows %} {% linux %} -## Telling Git about your GPG key +## 将您的 GPG 密钥告知 Git -If you're using a GPG key that matches your committer identity and your verified email address associated with your account on {% ifversion ghae %}{% data variables.product.product_name %}{% else %}{% data variables.location.product_location %}{% endif %}, then you can begin signing commits and signing tags. +如果您使用与您的提交者身份以及 {% ifversion ghae %}{% data variables.product.product_name %}{% else %}{% data variables.location.product_location %}{% endif %} 上帐户关联的已验证电子邮件地址相匹配的 GPG 密钥，则可以开始对提交和标签进行签名。 {% note %} -If you don't have a GPG key that matches your committer identity, you need to associate an email with an existing key. For more information, see "[Associating an email with your GPG key](/articles/associating-an-email-with-your-gpg-key)". +如果您没有与提交者身份匹配的 GPG 密钥，则需要将电子邮件与现有密钥关联。 有关详细信息，请参阅“[将电子邮件与 GPG 密钥关联](/articles/associating-an-email-with-your-gpg-key)”。 {% endnote %} -If you have multiple GPG keys, you need to tell Git which one to use. +如果您有多个 GPG 密钥，则需要告知 Git 要使用哪一个。 -{% data reusables.command_line.open_the_multi_os_terminal %} -{% data reusables.gpg.configure-gpg-signing %} -{% data reusables.gpg.list-keys-with-note %} -{% data reusables.gpg.copy-gpg-key-id %} -{% data reusables.gpg.paste-gpg-key-id %} -{% data reusables.gpg.set-auto-sign %} -1. To add your GPG key to your `.bashrc` startup file, run the following command: +{% data reusables.command_line.open_the_multi_os_terminal %} {% data reusables.gpg.configure-gpg-signing %} {% data reusables.gpg.list-keys-with-note %} {% data reusables.gpg.copy-gpg-key-id %} {% data reusables.gpg.paste-gpg-key-id %} {% data reusables.gpg.set-auto-sign %} +1. 若要将 GPG 密钥添加到 `.bashrc` 启动文件，请运行以下命令： ```bash $ [ -f ~/.bashrc ] && echo 'export GPG_TTY=$(tty)' >> ~/.bashrc ``` -{% endlinux %} -{% ifversion ssh-commit-verification %} +{% endlinux %} {% ifversion ssh-commit-verification %} -## Telling Git about your SSH key +## 将 SSH 密钥告知 Git -You can use an existing SSH key to sign commits and tags, or generate a new one specifically for signing. For more information, see "[Generating a new SSH key and adding it to the ssh-agent](/github/authenticating-to-github/generating-a-new-ssh-key-and-adding-it-to-the-ssh-agent)." +可以使用现有 SSH 密钥对提交和标记进行签名，或生成专用于签名的新密钥。 有关详细信息，请参阅“[生成新的 SSH 密钥并将其添加到 ssh-agent](/github/authenticating-to-github/generating-a-new-ssh-key-and-adding-it-to-the-ssh-agent)”。 {% data reusables.gpg.ssh-git-version %} -{% data reusables.command_line.open_the_multi_os_terminal %} -{% data reusables.gpg.configure-ssh-signing %} -{% data reusables.gpg.copy-ssh-public-key %} -{% data reusables.gpg.paste-ssh-public-key %} +{% data reusables.command_line.open_the_multi_os_terminal %} {% data reusables.gpg.configure-ssh-signing %} {% data reusables.gpg.copy-ssh-public-key %} {% data reusables.gpg.paste-ssh-public-key %} {% endif %} {% data reusables.gpg.x-509-key %} -## Further reading +## 延伸阅读 -- "[Adding a new SSH key to your GitHub account](/authentication/connecting-to-github-with-ssh/adding-a-new-ssh-key-to-your-github-account)." -- "[Signing commits](/articles/signing-commits)" -- "[Signing tags](/articles/signing-tags)" +- “[为 GitHub 帐户添加新的 SSH 密钥](/authentication/connecting-to-github-with-ssh/adding-a-new-ssh-key-to-your-github-account)”。 +- [对提交签名](/articles/signing-commits) +- [对标记签名](/articles/signing-tags) diff --git a/translations/zh-CN/content/code-security/security-advisories/guidance-on-reporting-and-writing/best-practices-for-writing-repository-security-advisories.md b/translations/zh-CN/content/code-security/security-advisories/guidance-on-reporting-and-writing/best-practices-for-writing-repository-security-advisories.md new file mode 100644 index 0000000000..0011e75841 --- /dev/null +++ b/translations/zh-CN/content/code-security/security-advisories/guidance-on-reporting-and-writing/best-practices-for-writing-repository-security-advisories.md @@ -0,0 +1,94 @@ +--- +title: 编写存储库安全公告的最佳做法 +intro: 在创建或编辑安全公告时，使用标准格式指定生态系统、包名称和受影响的版本后，更易于其他用户理解你提供的信息。 +versions: + fpt: '*' + ghec: '*' +type: how_to +miniTocMaxHeadingLevel: 3 +topics: + - Security advisories + - Vulnerabilities +shortTitle: Best practices +redirect_from: + - /code-security/repository-security-advisories/best-practices-for-writing-repository-security-advisories +ms.openlocfilehash: af1ab76e13f44f5b319cd560e1ae0aa3081742dc +ms.sourcegitcommit: 27882d9b3f19979c817c25952a2fb4dc4c6f0a65 +ms.translationtype: HT +ms.contentlocale: zh-CN +ms.lasthandoff: 10/27/2022 +ms.locfileid: '148114003' +--- +任何对存储库有管理员权限的人都可以创建和编辑安全公告。 + +{% data reusables.security-advisory.security-researcher-cannot-create-advisory %} + +## 有关存储库的安全公告 + +{% data reusables.security-advisory.security-advisory-overview %} 有关详细信息，请参阅“[关于存储库安全公告](/code-security/repository-security-advisories/about-github-security-advisories-for-repositories)”。 + +## 最佳实践 + +编写存储库安全公告或为全局安全公告做出社区贡献时，建议采用 {% data variables.product.prodname_advisory_database %} 中使用的语法，尤其是版本格式设置。 + +如果按照 {% data variables.product.prodname_advisory_database %} 的语法，尤其是对受影响的版本进行定义时： +- 发布存储库公告时，可以将公告添加到 {% data variables.product.prodname_advisory_database %} 作为“{% data variables.product.company_short %}-已审核”公告，而无需请求更多信息。 +- {% data variables.product.prodname_dependabot %} 将提供信息来准确识别受影响的存储库，并向其发送 {% data variables.product.prodname_dependabot_alerts %} 以通知它们。 +- 社区成员不太可能建议通过编辑公告来修复缺失或不正确的信息。 + +使用“草稿安全公告”表单添加或编辑存储库公告。 有关详细信息，请参阅“[创建存储库安全公告](/code-security/repository-security-advisories/creating-a-repository-security-advisory)”。 + +建议使用“改进安全公告”表单，完善现有全局公告。 有关详细信息，请参阅“[在 {% data variables.product.prodname_advisory_database %} 中编辑安全公告](/code-security/dependabot/dependabot-alerts/editing-security-advisories-in-the-github-advisory-database)”。 + +### 生态系统 + +需要使用“生态系统”字段将公告分配给受支持的生态系统之一。 有关我们支持的生态系统的详细信息，请参阅“[在 {% data variables.product.prodname_advisory_database %} 中浏览安全公告](/code-security/dependabot/dependabot-alerts/browsing-security-advisories-in-the-github-advisory-database#github-reviewed-advisories)”。 + +![突出显示表单上“生态系统”字段的屏幕截图](/assets/images/help/security/security-advisory-ecosystem.png) + +### 包名称 + +建议使用“包名称”字段指定受影响的包，因为 {% data variables.product.prodname_advisory_database %} 中的“{% data variables.product.company_short %}-已审核”公告需要包信息。 包信息对于存储库级安全公告是可选的，但在发布安全公告时尽早包含此信息可简化审核过程。 + +![突出显示表单上“包名称”的屏幕截图](/assets/images/help/security/security-advisory-package-name.png) + +### 受影响版本 + +建议使用“受影响的版本”字段指定受影响的版本，因为 {% data variables.product.prodname_advisory_database %} 中的“{% data variables.product.company_short %}-已审核”公告在需要此信息。 版本信息对于存储库级安全公告是可选的，但在发布安全公告时尽早包含此信息可简化审核过程。 + +![突出显示“受影响的版本”字段的屏幕截图](/assets/images/help/security/security-advisory-affected-versions.png) + +- 有效的受影响的版本字符串包含以下内容之一： + - 下限运算符序列。 + - 上限运算符序列。 + - 上限运算符序列和下限运算符序列。 + - 使用相等 (`=`) 运算符的特定版本序列。 +- 每个运算符序列都必须指定为运算符、单个空格，以及版本。 + - 有效运算符包括 `=`、`<`、`<=`、`>` 或 `>=`。 + - 版本必须以数字开头，其后为任意数量的数字、字母、点、短破折号或下划线字符（空格或逗号以外的任何内容） + - 同时指定上限序列和下限序列后，下限必须先出现，其后为逗号和一个空格，然后是上限。 + {% note %} + + 注意：受影响的版本字符串不能包含前导空格或尾随空格。 + + {% endnote %} + +- 上限运算符可以是非独占运算符或独占运算符，即分别是 `<=` 或 `<`。 +- 下限运算符可以是非独占运算符或独占运算符，即分别是 `>=` 或 `>`。 但是，如果你发布存储库公告，而我们将你的存储库公告升级为全局公告后，则会应用不同的规则：下限运算符只能是非独占的，即 `>=`。仅当版本为 `0` 时才能是独占下限运算符 (`>`)，如 `> 0`。 + + {% note %} + + 注意：下限限制： + - 是因为与 OSV（开放源代码漏洞）架构不兼容。 + - 仅在对 {% data variables.product.prodname_advisory_database %} 中的现有公告提出建议时才适用。 + + {% endnote %} + +- 不能在同一字段中指定多个受影响的版本范围，例如 `> 2.0, < 2.3, > 3.0, < 3.2`。若要指定多个范围，必须通过单击“+ 添加另一个受影响的产品”按钮，为每个范围创建新的“受影响的产品”部分 。 + + ![突出显示用于添加多个受影响的版本范围的按钮的屏幕截图](/assets/images/help/security/security-advisory-add-another-affected-product.png) + - 如果受影响的版本范围仅包含单个上限或下限： + - 如果未显式指定下限，那么隐式值始终为 `> 0`。 + - 如果未显式指定上限，则隐式值始终为无穷大。 + +有关 {% data variables.product.prodname_advisory_database %} 的详细信息，请参阅 [https://github.com/github/advisory-database](https://github.com/github/advisory-database)。 diff --git a/translations/zh-CN/content/code-security/supply-chain-security/understanding-your-software-supply-chain/troubleshooting-the-dependency-graph.md b/translations/zh-CN/content/code-security/supply-chain-security/understanding-your-software-supply-chain/troubleshooting-the-dependency-graph.md index c1879f3d31..2ea290fe37 100644 --- a/translations/zh-CN/content/code-security/supply-chain-security/understanding-your-software-supply-chain/troubleshooting-the-dependency-graph.md +++ b/translations/zh-CN/content/code-security/supply-chain-security/understanding-your-software-supply-chain/troubleshooting-the-dependency-graph.md @@ -48,7 +48,7 @@ Yes, the dependency graph has two categories of limits: Manifests over 0.5 MB in size are only processed for enterprise accounts. For other accounts, manifests over 0.5 MB are ignored and will not create {% data variables.product.prodname_dependabot_alerts %}. - By default, {% data variables.product.prodname_dotcom %} will not process more than 20 manifests per repository. {% data variables.product.prodname_dependabot_alerts %} are not created for manifests beyond this limit. If you need to increase the limit, contact {% data variables.contact.contact_support %}. + By default, {% data variables.product.prodname_dotcom %} will not process more than {% ifversion fpt %}150{% else %}600{% endif %} manifests per repository. {% data variables.product.prodname_dependabot_alerts %} are not created for manifests beyond this limit. If you need to increase the limit, contact {% data variables.contact.contact_support %}. 2. **Visualization limits** diff --git a/translations/zh-CN/content/education/manage-coursework-with-github-classroom/integrate-github-classroom-with-an-ide/using-github-codespaces-with-github-classroom.md b/translations/zh-CN/content/education/manage-coursework-with-github-classroom/integrate-github-classroom-with-an-ide/using-github-codespaces-with-github-classroom.md index 5485268315..d2d9a09f01 100644 --- a/translations/zh-CN/content/education/manage-coursework-with-github-classroom/integrate-github-classroom-with-an-ide/using-github-codespaces-with-github-classroom.md +++ b/translations/zh-CN/content/education/manage-coursework-with-github-classroom/integrate-github-classroom-with-an-ide/using-github-codespaces-with-github-classroom.md @@ -81,7 +81,7 @@ When a student opens an assignment, the repository's README file includes their ![Screenshot of the Codespaces note in the README for a student assignment repository](/assets/images/help/classroom/student-codespaces-readme-link.png) -Students can launch a new or existing codespace by clicking the **{% octicon "code" aria-label="The code icon" %} Code** button on the main page of the assignment repository, then selecting the **Codespaces** tab. For more information, see "[Creating a codespace](/codespaces/developing-in-codespaces/creating-a-codespace#creating-a-codespace)." +Students can launch a new or existing codespace by clicking the **Open in GitHub Codespace** button in the README, or by clicking the **{% octicon "code" aria-label="The code icon" %} Code** button on the main page of the assignment repository, then selecting the **Codespaces** tab. From the **Codespaces** tab you can select an existing codespace or create a new one. For more information, see "[Creating a codespace](/codespaces/developing-in-codespaces/creating-a-codespace#creating-a-codespace)." ![Launch new codespace in assignment repository](/assets/images/help/classroom/student-launch-new-codespace.png) diff --git a/translations/zh-CN/content/get-started/getting-started-with-git/about-remote-repositories.md b/translations/zh-CN/content/get-started/getting-started-with-git/about-remote-repositories.md index 9f811b3086..c1276038d8 100644 --- a/translations/zh-CN/content/get-started/getting-started-with-git/about-remote-repositories.md +++ b/translations/zh-CN/content/get-started/getting-started-with-git/about-remote-repositories.md @@ -34,12 +34,12 @@ You can use the `git remote add` command to match a remote URL with a name. For example, you'd type the following in the command line: ```shell -git remote add origin <REMOTE_URL> +git remote add origin <REMOTE_URL> ``` This associates the name `origin` with the `REMOTE_URL`. -You can use the command `git remote set-url` to [change a remote's URL](/github/getting-started-with-github/managing-remote-repositories). +You can use the command `git remote set-url` to [change a remote's URL](/get-started/getting-started-with-git/managing-remote-repositories). ## Choosing a URL for your remote repository @@ -47,7 +47,7 @@ There are several ways to clone repositories available on {% data variables.loca When you view a repository while signed in to your account, the URLs you can use to clone the project onto your computer are available below the repository details. -For information on setting or changing your remote URL, see "[Managing remote repositories](/github/getting-started-with-github/managing-remote-repositories)." +For information on setting or changing your remote URL, see "[Managing remote repositories](/get-started/getting-started-with-git/managing-remote-repositories)." ## Cloning with HTTPS URLs diff --git a/translations/zh-CN/content/organizations/managing-peoples-access-to-your-organization-with-roles/index.md b/translations/zh-CN/content/organizations/managing-peoples-access-to-your-organization-with-roles/index.md index 700f35edb0..2475bd32db 100644 --- a/translations/zh-CN/content/organizations/managing-peoples-access-to-your-organization-with-roles/index.md +++ b/translations/zh-CN/content/organizations/managing-peoples-access-to-your-organization-with-roles/index.md @@ -15,8 +15,9 @@ topics: - Teams children: - /roles-in-an-organization - - /maintaining-ownership-continuity-for-your-organization + - /about-custom-repository-roles - /managing-custom-repository-roles-for-an-organization + - /maintaining-ownership-continuity-for-your-organization - /adding-a-billing-manager-to-your-organization - /removing-a-billing-manager-from-your-organization - /managing-security-managers-in-your-organization diff --git a/translations/zh-CN/content/organizations/managing-peoples-access-to-your-organization-with-roles/managing-custom-repository-roles-for-an-organization.md b/translations/zh-CN/content/organizations/managing-peoples-access-to-your-organization-with-roles/managing-custom-repository-roles-for-an-organization.md index 97321b910c..0cb62007f0 100644 --- a/translations/zh-CN/content/organizations/managing-peoples-access-to-your-organization-with-roles/managing-custom-repository-roles-for-an-organization.md +++ b/translations/zh-CN/content/organizations/managing-peoples-access-to-your-organization-with-roles/managing-custom-repository-roles-for-an-organization.md @@ -1,176 +1,67 @@ --- -title: 管理组织的自定义存储库角色 -intro: 通过创建自定义存储库角色，可以更精细地控制对组织存储库的访问。 +title: Managing custom repository roles for an organization +intro: You can create, edit, or delete custom repository roles for your organization. permissions: Organization owners can manage custom repository roles. versions: feature: custom-repository-roles topics: - Organizations - Teams -shortTitle: Custom repository roles +shortTitle: Manage custom roles redirect_from: - /early-access/github/articles/managing-custom-repository-roles-for-an-organization -ms.openlocfilehash: e37e7822abc378cd91fb719dd472edaf35af4465 -ms.sourcegitcommit: 478f2931167988096ae6478a257f492ecaa11794 -ms.translationtype: HT -ms.contentlocale: zh-CN -ms.lasthandoff: 09/09/2022 -ms.locfileid: '147858682' --- -## 关于自定义存储库角色 -要对 {% data variables.product.product_name %} 执行任何操作，例如在存储库中创建拉取请求或更改组织的计费设置，人员必须具有对相关帐户或资源的足够访问权限。 此访问由权限控制。 权限是执行特定操作的能力。 例如，删除问题的能力是一种权限。 角色是你可以分配给个人或团队的一组权限。 +{% data reusables.organizations.custom-repo-roles-ghec-only %} -在组织内，您可以在组织、团队和存储库级别分配角色。 有关不同级别角色的详细信息，请参阅“[组织中的角色](/organizations/managing-peoples-access-to-your-organization-with-roles/roles-in-an-organization)”。 +## About custom repository roles -通过创建最多三个自定义存储库角色，可以更精细地控制在存储库级授予的权限。 自定义存储库角色是一组可配置的权限，具有您选择的自定义名称。 创建自定义角色后，对存储库具有管理员访问权限的任何人都可以将该角色分配给个人或团队。 有关详细信息，请参阅“[管理个人对组织存储库的访问](/organizations/managing-access-to-your-organizations-repositories/managing-an-individuals-access-to-an-organization-repository)”和“[管理团队对组织存储库的访问](/organizations/managing-access-to-your-organizations-repositories/managing-team-access-to-an-organization-repository)。” +{% data reusables.organizations.about-custom-repo-roles %} For more information, see "[About custom repository roles](/organizations/managing-peoples-access-to-your-organization-with-roles/about-custom-repository-roles)." -{% ifversion custom-repo-role-api %} +## Creating a repository role -还可以使用 REST API 创建和管理自定义存储库角色。 有关详细信息，请参阅“[自定义存储库角色](/rest/orgs/custom-roles)。” +To create a new repository role, you add permissions to an inherited role and give the custom role a name. -{% else %} +{% data reusables.profile.access_profile %} +{% data reusables.profile.access_org %} +{% data reusables.organizations.org_settings %} +{% data reusables.organizations.org-list %} +{% data reusables.organizations.org-settings-repository-roles %} +5. Click **Create a Role**. + ![Screenshot of "Create a Role" button](/assets/images/help/organizations/repository-role-create-role.png) +4. Under "Name", type the name of your repository role. + ![Field to type a name for the repository role](/assets/images/help/organizations/repository-role-name.png) +5. Under "Description", type a description of your repository role. + ![Field to type a description for the repository role](/assets/images/help/organizations/repository-role-description.png) +6. Under "Choose a role to inherit", select the role you want to inherit. + ![Selecting repository role base role option](/assets/images/help/organizations/repository-role-base-role-option.png) +7. Under "Add Permissions", use the drop-down menu to select the permissions you want your custom role to include. + ![Selecting permission levels from repository role drop-down](/assets/images/help/organizations/repository-role-drop-down.png) +7. Click **Create role**. + ![Confirm creating a repository role](/assets/images/help/organizations/repository-role-creation-confirm.png) -还可以使用 REST API 列出组织中可用的自定义存储库角色。 有关详细信息，请参阅“[自定义存储库角色 API](/rest/orgs/custom-roles)。” +## Editing a repository role -{% endif %} +{% data reusables.profile.access_profile %} +{% data reusables.profile.access_org %} +{% data reusables.organizations.org_settings %} +{% data reusables.organizations.org-list %} +{% data reusables.organizations.org-settings-repository-roles %} +3. To the right of the role you want to edit, click {% octicon "kebab-horizontal" aria-label="The horizontal kebab icon" %}, then click **Edit**. + ![Edit option in drop-down menu for repository roles](/assets/images/help/organizations/repository-role-edit-setting.png) +4. Edit, then click **Update role**. + ![Edit fields and update repository roles](/assets/images/help/organizations/repository-role-update.png) -## 关于继承的角色 +## Deleting a repository role -创建自定义存储库角色时，首先从一组预定义选项中选择继承的角色。 继承的角色确定自定义角色中包含的初始权限集。 然后，您可以通过选择其他权限来授予角色，从而进一步自定义角色。 有关可用权限的完整列表，请参阅“[自定义角色的其他权限](#additional-permissions-for-custom-roles)”。 +If you delete an existing repository role, all pending invitations, teams, and users with the custom role will be reassigned to the organization's base permissions. -继承角色的选项已针对存储库中不同类型的参与者进行了标准化。 - -| 继承的角色 | 用途 | -|----|----| -| **读取** | 想要查看或讨论项目的非代码参与者。 | -| **会审** | 需要主动管理问题和在没有写入访问权限的情况下拉取请求的参与者。 | -| **写入** | 积极推动项目的组织成员和协作者。 | -| **维护** | 需要管理存储库而无法访问敏感或破坏性操作的项目经理。 - -## 自定义角色示例 - -以下是您可以配置的自定义存储库角色的一些示例。 - -| 自定义存储库角色 | 总结 | 继承的角色 | 其他权限 | -|----|----|----|----| -| 安全工程师 | 能够贡献代码并维护安全管道 | **维护** | 删除代码扫描结果 | -| 承办商 | 能够开发 web 挂钩集成 | **写入** | 管理 web 挂钩 | -| 社区经理 | 能够处理所有社区互动，而无需贡献代码 | **读取** | - 将问题标记为重复问题
- 管理 GitHub 页面设置
- 管理 Wiki 设置
- 设置社交预览
- 编辑存储库元数据
- 会审讨论 | - -## 自定义角色的其他权限 - -选择继承角色后，您可以为自定义角色选择其他权限。 - -仅当继承的角色中尚未包含其他权限时，才能选择该权限。 例如，如果继承的角色提供对存储库的写入访问权限，则“关闭拉取请求”权限将已包含在继承的角色中。 - -{% ifversion discussions %} -### 讨论 - -- **创建讨论类别**：能够创建新的讨论类别。 有关详细信息，请参阅“[创建新的讨论类别](/discussions/managing-discussions-for-your-community/managing-categories-for-discussions#creating-a-category)”。 -- **编辑讨论类别**：能够编辑讨论类别。 有关详细信息，请参阅“[编辑讨论类别](/discussions/managing-discussions-for-your-community/managing-categories-for-discussions#editing-a-category)”。 -- **删除讨论类别**：能够删除讨论类别。 有关详细信息，请参阅“[删除讨论类别](/discussions/managing-discussions-for-your-community/managing-categories-for-discussions#deleting-a-category)”。 -- **标记或取消标记讨论答案**：如果讨论的类别可接受答案，则能够标记讨论的答案。 有关详细信息，请参阅“[将讨论中的评论标记或取消标记为答案](/discussions/managing-discussions-for-your-community/moderating-discussions#marking-a-comment-as-an-answer)”。 -- **隐藏或取消隐藏讨论评论**：能够在讨论中隐藏和取消隐藏评论。 有关详细信息，请参阅“[审查讨论](/communities/moderating-comments-and-conversations/managing-disruptive-comments#hiding-a-comment)”。 -- **将问题转换为讨论**：能够将问题转换为讨论。 有关详细信息，请参阅“[将问题转换为讨论](/discussions/managing-discussions-for-your-community/moderating-discussions#converting-an-issue-to-a-discussion)”。 -{% endif %} - -### 议题和拉取请求 - -- **分配或删除用户**：将用户分配给问题或拉取请求，或从问题或拉取请求中删除用户。 -- **添加或删除标签**：向问题或拉取请求添加标签，或从问题或拉取请求中删除标签。 - -### 问题 - -- **关闭问题** -- **重新打开已关闭的问题** -- **删除问题** -- **将问题标记为重复问题** - -### 拉取请求 - -- **关闭拉取请求** -- **重新打开已关闭的拉取请求** -- **请求拉取请求评审**：请求用户或团队进行评审。 - -### 存储库 - -- **设置里程碑**：向问题或拉取请求添加里程碑。 -- **管理 Wiki 设置**：为存储库启用 Wiki。 -- **管理项目设置**：为存储库启用项目。 -- **管理拉取请求合并设置**：选择存储库中允许的合并提交类型，例如合并、压缩或变基。 -- **管理 {% data variables.product.prodname_pages %} 设置**：为存储库启用 {% data variables.product.prodname_pages %}，然后选择要发布的分支。 有关详细信息，请参阅“[为 {% data variables.product.prodname_pages %} 站点配置发布源](/pages/getting-started-with-github-pages/configuring-a-publishing-source-for-your-github-pages-site)”。 -- **管理 Webhook**：将 Webhook 添加到存储库。 -- **管理部署密钥**：将部署密钥添加到存储库。 -- **编辑存储库元数据**：更新存储库说明以及存储库主题。 -{%- ifversion ghec %} -- **设置交互限制**：暂时限制某些用户在公共存储库中发表评论、提出问题或创建拉取请求，以强制在一段时间内执行有限的活动。 有关详细信息，请参阅“[限制存储库中的交互](/communities/moderating-comments-and-conversations/limiting-interactions-in-your-repository)。” -{%- endif %} -- **设置社交预览**：将识别图像添加到存储库，该图像在链接存储库时显示在社交媒体平台上。 有关详细信息，请参阅“[自定义存储库的社交媒体预览](/repositories/managing-your-repositorys-settings-and-features/customizing-your-repository/customizing-your-repositorys-social-media-preview)”。 -- **将提交推送到受保护的分支**：推送到标记为受保护分支的分支。 分支保护规则仍将适用，并可能导致推送遭到拒绝。 -- **创建受保护的标记**：创建符合标记保护规则的标记。 有关详细信息，请参阅“[配置标记保护规则](/repositories/managing-your-repositorys-settings-and-features/managing-repository-settings/configuring-tag-protection-rules)”。 -- **删除受保护的标记**：删除符合标记保护规则的标记。 有关详细信息，请参阅“[配置标记保护规则](/repositories/managing-your-repositorys-settings-and-features/managing-repository-settings/configuring-tag-protection-rules)”。{% ifversion bypass-branch-protections %} -- 绕过分支保护：无需遵守分支保护规则即可推送到受保护分支。{% endif %} - -### 安全性 - -- **查看 {% data variables.product.prodname_code_scanning %} 结果**：能够查看 {% data variables.product.prodname_code_scanning %} 警报。 -- **关闭或重新打开 {% data variables.product.prodname_code_scanning %} 结果**：能够关闭或重新打开 {% data variables.product.prodname_code_scanning %} 警报。 -- **删除 {% data variables.product.prodname_code_scanning %} 结果**：能够删除 {% data variables.product.prodname_code_scanning %} 警报。 -- **查看 {% data variables.product.prodname_dependabot_alerts %}** ：能够查看 {% data variables.product.prodname_dependabot_alerts %}。 -- **关闭或重新打开 {% data variables.product.prodname_dependabot_alerts %}** ：能够关闭或重新打开 {% data variables.product.prodname_dependabot_alerts %}。 -- **查看 {% data variables.product.prodname_secret_scanning %} 结果**：能够查看 {% data variables.product.prodname_secret_scanning %} 警报。 -- **关闭或重新打开 {% data variables.product.prodname_secret_scanning %} 结果**：能够关闭或重新打开 {% data variables.product.prodname_secret_scanning %} 警报。 - -## 不同级别访问的优先级 - -如果通过不同的途径（如团队成员身份和组织的基本权限）为某人授予不同级别的访问权限，则最高访问权限将覆盖其他访问权限。 例如，如果组织所有者向组织成员提供使用“读取”继承角色的自定义角色，然后组织所有者将组织的基本权限设置为“写入”，则此自定义角色将具有写入权限以及自定义角色中包含的任何其他权限。 - -{% data reusables.organizations.mixed-roles-warning %} - -要解决冲突的访问权限，您可以调整组织的基本权限或团队的访问权限，或编辑自定义角色。 有关详细信息，请参阅： - - [为组织设置基本权限](/github/setting-up-and-managing-organizations-and-teams/setting-base-permissions-for-an-organization) - - “[管理团队对组织存储库的访问](/organizations/managing-access-to-your-organizations-repositories/managing-team-access-to-an-organization-repository)” - - [编辑存储库角色](#editing-a-repository-role) - -## 创建存储库角色 - -要创建新的存储库角色，请向继承的角色添加权限并为自定义角色命名。 - -{% ifversion ghec %} {% note %} - -注意：只有使用 {% data variables.product.prodname_ghe_cloud %} 的组织才能创建自定义存储库角色。 {% data reusables.enterprise.link-to-ghec-trial %} - -{% endnote %} {% endif %} - -{% data reusables.profile.access_profile %} {% data reusables.profile.access_org %} {% data reusables.organizations.org_settings %} {% data reusables.organizations.org-list %} {% data reusables.organizations.org-settings-repository-roles %} -5. 单击“创建角色”。 - ![“创建角色”按钮的屏幕截图](/assets/images/help/organizations/repository-role-create-role.png) -4. 在“Name（名称）”下，键入存储库角色的名称。 - ![用于键入存储库角色名称的字段](/assets/images/help/organizations/repository-role-name.png) -5. 在“Description（描述）”下，键入存储库角色的描述。 - ![用于键入存储库角色说明的字段](/assets/images/help/organizations/repository-role-description.png) -6. 在“Choose a role to inherit（选择要继承的角色）”下，选择要继承的角色。 - ![选择存储库角色基础角色选项](/assets/images/help/organizations/repository-role-base-role-option.png) -7. 在“Add Permissions（添加权限）”下，使用下拉菜单选择您希望自定义角色包含的权限。 - ![从存储库角色下拉列表中选择权限级别](/assets/images/help/organizations/repository-role-drop-down.png) -7. 单击“创建角色”。 - ![确认创建存储库角色](/assets/images/help/organizations/repository-role-creation-confirm.png) - -## 编辑存储库角色 - -{% data reusables.profile.access_profile %} {% data reusables.profile.access_org %} {% data reusables.organizations.org_settings %} {% data reusables.organizations.org-list %} {% data reusables.organizations.org-settings-repository-roles %} -3. 在要编辑的角色右侧，单击 {% octicon "kebab-horizontal" aria-label="The horizontal kebab icon" %}，然后单击“编辑”。 - ![存储库角色下拉菜单中的“编辑”选项](/assets/images/help/organizations/repository-role-edit-setting.png) -4. 编辑，然后单击“更新角色”。 - ![编辑字段和更新存储库角色](/assets/images/help/organizations/repository-role-update.png) - -## 删除存储库角色 - -如果您删除现有存储库角色，则所有具有自定义角色的待处理邀请、团队和用户都将被重新分配给组织的基本权限。 - -{% data reusables.profile.access_profile %} {% data reusables.profile.access_org %} {% data reusables.organizations.org_settings %} {% data reusables.organizations.org-list %} {% data reusables.organizations.org-settings-repository-roles %} -3. 在要删除的角色右侧，单击 {% octicon "kebab-horizontal" aria-label="The horizontal kebab icon" %}，然后单击“删除”。 - ![存储库角色下拉菜单中的“编辑”选项](/assets/images/help/organizations/repository-role-delete-setting.png) -4. 查看要删除的角色的更改，然后单击“删除角色”。 - ![确认删除存储库角色](/assets/images/help/organizations/repository-role-delete-confirm.png) +{% data reusables.profile.access_profile %} +{% data reusables.profile.access_org %} +{% data reusables.organizations.org_settings %} +{% data reusables.organizations.org-list %} +{% data reusables.organizations.org-settings-repository-roles %} +3. To the right of the role you want to delete, click {% octicon "kebab-horizontal" aria-label="The horizontal kebab icon" %}, then click **Delete**. + ![Edit option in drop-down menu for repository roles](/assets/images/help/organizations/repository-role-delete-setting.png) +4. Review changes for the role you want to remove, then click **Delete role**. + ![Confirm deleting a repository role](/assets/images/help/organizations/repository-role-delete-confirm.png) diff --git a/translations/zh-CN/content/repositories/working-with-files/managing-large-files/about-git-large-file-storage.md b/translations/zh-CN/content/repositories/working-with-files/managing-large-files/about-git-large-file-storage.md index 7a6fcdc772..e0957f331a 100644 --- a/translations/zh-CN/content/repositories/working-with-files/managing-large-files/about-git-large-file-storage.md +++ b/translations/zh-CN/content/repositories/working-with-files/managing-large-files/about-git-large-file-storage.md @@ -1,6 +1,6 @@ --- -title: About Git Large File Storage -intro: '{% data variables.product.product_name %} limits the size of files allowed in repositories. To track files beyond this limit, you can use {% data variables.large_files.product_name_long %}.' +title: 关于 Git Large File Storage +intro: '{% data variables.product.product_name %} 限制存储库中允许的文件大小。 要跟踪超出此限制的文件，您可以使用 {% data variables.large_files.product_name_long %}。' redirect_from: - /articles/about-large-file-storage - /articles/about-git-large-file-storage @@ -12,33 +12,37 @@ versions: ghae: '*' ghec: '*' shortTitle: Git Large File Storage +ms.openlocfilehash: f0ab54791645dc5c36cce2880ba3ae5c9b705f35 +ms.sourcegitcommit: 06726d24e73f1175f10749d6fdcf143d6094c9a5 +ms.translationtype: HT +ms.contentlocale: zh-CN +ms.lasthandoff: 10/28/2022 +ms.locfileid: '148118744' --- +## 关于 {% data variables.large_files.product_name_long %} -## About {% data variables.large_files.product_name_long %} +{% data variables.large_files.product_name_short %} 处理大文件的方式是存储对仓库中文件的引用，而不实际文件本身。 为满足 Git 的架构要求，{% data variables.large_files.product_name_short %} 创建了“指针文件”，充当对实际文件（存储在其他位置）的引用。 {% data variables.product.product_name %} 在仓库中管理此指针文件。 克隆仓库时，{% data variables.product.product_name %} 使用指针文件作为映射来查找大文件。 -{% data variables.large_files.product_name_short %} handles large files by storing references to the file in the repository, but not the actual file itself. To work around Git's architecture, {% data variables.large_files.product_name_short %} creates a pointer file which acts as a reference to the actual file (which is stored somewhere else). {% data variables.product.product_name %} manages this pointer file in your repository. When you clone the repository down, {% data variables.product.product_name %} uses the pointer file as a map to go and find the large file for you. +{% ifversion fpt or ghec %} 使用 {% data variables.large_files.product_name_short %}，可以将文件存储到： -{% ifversion fpt or ghec %} -Using {% data variables.large_files.product_name_short %}, you can store files up to: - -| Product | Maximum file size | +| 产品 | 文件大小上限 | |------- | ------- | | {% data variables.product.prodname_free_user %} | 2 GB | | {% data variables.product.prodname_pro %} | 2 GB | | {% data variables.product.prodname_team %} | 4 GB | | {% data variables.product.prodname_ghe_cloud %} | 5 GB |{% else %} -Using {% data variables.large_files.product_name_short %}, you can store files up to 5 GB in your repository. +使用 {% data variables.large_files.product_name_short %}，可在仓库中存储最大 5 GB 的文件。 {% endif %} {% data reusables.repositories.git-lfs %} -You can also use {% data variables.large_files.product_name_short %} with {% data variables.product.prodname_desktop %}. For more information about cloning Git LFS repositories in {% data variables.product.prodname_desktop %}, see "[Cloning a repository from GitHub to GitHub Desktop](/desktop/guides/contributing-to-projects/cloning-a-repository-from-github-to-github-desktop)." +您也可以将 {% data variables.large_files.product_name_short %} 与 {% data variables.product.prodname_desktop %} 结合使用。 有关在 {% data variables.product.prodname_desktop %} 中克隆 Git LFS 存储库的详细信息，请参阅“[将存储库从 GitHub 克隆到 GitHub 桌面](/desktop/guides/contributing-to-projects/cloning-a-repository-from-github-to-github-desktop)”。 {% data reusables.large_files.can-include-lfs-objects-archives %} -## Pointer file format +## 指针文件格式 -{% data variables.large_files.product_name_short %}'s pointer file looks like this: +{% data variables.large_files.product_name_short %} 的指针文件看起来像： ``` version {% data variables.large_files.version_name %} @@ -46,16 +50,16 @@ oid sha256:4cac19622fc3ada9c0fdeadb33f88f367b541f38b89102a3f1261ac81fd5bcb5 size 84977953 ``` -It tracks the `version` of {% data variables.large_files.product_name_short %} you're using, followed by a unique identifier for the file (`oid`). It also stores the `size` of the final file. +它会跟踪所用 {% data variables.large_files.product_name_short %} 的 `version`，后接文件的唯一标识符 (`oid`)。 它还会存储最终文件的 `size`。 {% note %} -**Notes**: -- {% data variables.large_files.product_name_short %} cannot be used with {% data variables.product.prodname_pages %} sites. -- {% data variables.large_files.product_name_short %} cannot be used with template repositories. +**注释**： +- {% data variables.large_files.product_name_short %} 不能用于 {% data variables.product.prodname_pages %} 站点。 +- {% data variables.large_files.product_name_short %} 不能用于模板仓库。 {% endnote %} -## Further reading +## 延伸阅读 -- "[Collaboration with {% data variables.large_files.product_name_long %}](/articles/collaboration-with-git-large-file-storage)" +- [与 {% data variables.large_files.product_name_long %} 协作](/articles/collaboration-with-git-large-file-storage) 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 deleted file mode 100644 index 3fd77690d3..0000000000 --- a/translations/zh-CN/data/release-notes/enterprise-server/2-20/0.yml +++ /dev/null @@ -1,44 +0,0 @@ -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 %}' - - '组织所有者在创建新存储库时可以创建一组默认标签。{% comment %} https://github.com/github/issues-projects/issues/237、https://github.com/github/issues-projects/issues/179 {% endcomment %}' - security_fixes: - - 包已更新到最新的安全版本。 - bugs: - - '当组织的成员尝试查看该组织的公共存储库时，SSO 提示可能会中断页面显示。{% comment %} https://github.com/github/github/issues/126677、https://github.com/github/github/pull/127501 {% endcomment %}' - - "查看用户配置文件时，指向该用户团队的链接可能会断开。{% comment %} https://github.com/github/github/issues/131771、https://github.com/github/github/pull/131865 {% endcomment %}" - - '具有 `maintain` 角色的用户无法编辑存储库主题。{% comment %} https://github.com/github/github/pull/129503、https://github.com/github/github/issues/119456 {% endcomment %}' - - "不是组织管理员的用户在尝试访问注册页面时将收到 500 个错误。{% comment %} https://github.com/github/github/pull/129213、https://github.com/github/github/issues/129210、https://github.com/github/github/issues/129212 {% endcomment %}" - - '编辑历史记录弹出窗口不会显示在 Gist 注释上。{% comment %} https://github.com/github/github/pull/129134、https://github.com/github/github/issues/128496 {% endcomment %}' - - '使用已注册的电子邮件地址可以注册新帐户。{% comment %} https://github.com/github/github/pull/127905、https://github.com/github/github/issues/127858 {% endcomment %}' - - '存储服务达到文件描述符限制，并导致内核挂起和其他服务记录错误。{% comment %} https://github.com/github/enterprise2/pull/18775 {% endcomment %}' - - '当自动链接引用是 URL 的一部分时，可以删除超链接。{% comment %} https://github.com/github/github/pull/126776 {% endcomment %}' - - '向拉取请求添加注释时，侧边栏中的“链接的议题”部分可能会消失。{% comment %} https://github.com/github/issues-projects/issues/384、https://github.com/github/github/pull/130514 {% endcomment %}' - - '编辑用户的现有组织邀请时，`Teams` 表上可能会显示重复的标头。{% comment %} https://github.com/github/github/issues/120381、https://github.com/github/github/pull/128939 {% endcomment %}' - - '当队列变得太大时，`resqued` 服务可能会停止记录事件。{% comment %} https://github.com/github/github/pull/130087、https://github.com/github/business-support/issues/2696 {% endcomment %}' - - '对于群集和高可用性配置运行 `ghe-config-apply` 命令时，不会自动生成自签名证书。{% comment %} https://github.com/github/enterprise2/pull/18773 {% endcomment %}' - changes: - - '如果尚未上传主题，则不会显示徽标。{% comment %} https://github.com/github/github/issues/130513、https://github.com/github/github/pull/130515 {% endcomment %}' - - '在移动浏览器上查看问题时，问题元数据将列在页面顶部。{% comment %} https://github.com/github/github/pull/127560 {% endcomment %}' - - 'Consul 的顶级域已从“.consul”更改为“.ghe.local”。{% comment %} https://github.com/github/enterprise2/pull/17443、https://github.com/github/enterprise2/issues/17701 {% endcomment %}' - - 'Hookshot 服务不再依赖 ElasticSearch，只能使用 MySQL 作为数据库存储。{% comment %} https://github.com/github/enterprise2/pull/18158、https://github.com/github/hookshot/pull/1128、https://github.com/github/enterprise2/pull/15898 {% endcomment %}' - - '在项目说明卡上改进了问题、项目及讨论之间的视觉区分。{% comment %} https://github.com/github/github/pull/132038 {% endcomment %}' - - '在拉取请求审阅中，如果多行注释被截断，将显示通知。{% comment %} https://github.com/github/github/issues/125948、https://github.com/github/github/pull/128677 {% endcomment %}' - - '用户可以在个人设置页面的“安全日志”选项卡上查看其审核日志。{% comment %} https://github.com/github/github/pull/123041{% 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 %}' - - '如果问题包含同一存储库中文件路径长于 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）" - - '如果自定义了后台工作进程配置，则升级和设置更新将失败。{% comment %} https://github.com/github/enterprise2/issues/19119 {% endcomment %}' - - '在 GitHub Connect 中启用了“用户可以搜索 GitHub.com”时，专用和内部存储库中的问题不包括在 GitHub.com 搜索结果中。{% comment %} https://github.com/github/admin-experience/issues/571 {% endcomment %}' - - '从早期版本升级时，可能无法生成后台作业工作进程，从而阻止合并拉取请求等基本功能。（更新时间：2020-04-07）{% comment %} https://github.com/github/enterprise2/issues/19232 {% endcomment %}' - - '推送到命令行上的存储库时，不会报告安全警报。（更新时间：2020-06-23）{% comment %} https://github.com/github/github/issues/143190 {% endcomment %}' - - '依赖项关系图在具有多个 Redis 节点的群集配置中部署时不会检测依赖项。（更新时间：2020-06-30）{% comment %} https://github.com/github/dependency-graph/issues/81 {% 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-20/1.yml b/translations/zh-CN/data/release-notes/enterprise-server/2-20/1.yml deleted file mode 100644 index 3a318e0188..0000000000 --- a/translations/zh-CN/data/release-notes/enterprise-server/2-20/1.yml +++ /dev/null @@ -1,21 +0,0 @@ -date: '2020-02-27' -sections: - security_fixes: - - '包已更新到最新的安全版本。{% comment %} https://github.com/github/enterprise2/pull/19116, https://github.com/github/enterprise2/pull/19110, https://github.com/github/enterprise2/pull/19154, https://github.com/github/enterprise2/pull/19142 {% endcomment %}' - bugs: - - '从备份还原将会失败，并显示“RDB 版本号无效”错误。{% comment %} https://github.com/github/enterprise2/pull/19117, https://github.com/github/enterprise2/pull/19109 {% endcomment %}' - - '升级 HA 副本将停止无限期等待 MySQL 启动。{% comment %} https://github.com/github/enterprise2/pull/19168, https://github.com/github/enterprise2/pull/19101 {% endcomment %}' - - '具有意外“position”或“original_position”值的 PR 审核评论导致导入失败。{% comment %} https://github.com/github/github/pull/135439, https://github.com/github/github/pull/135374 {% endcomment %}' - - '数据库中重复的 Webhook 条目可能导致先前版本的升级失败。{% comment %} https://github.com/github/hookshot/pull/1541, https://github.com/github/hookshot/pull/1426, https://github.com/github/hookshot/pull/1540 {% 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 %}' - - '问题若是包含同一存储库中文件路径长于 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 %}' - - '在 GitHub Connect 中启用了“用户可以搜索 GitHub.com”时，专用和内部存储库中的问题不包括在 GitHub.com 搜索结果中。{% comment %} https://github.com/github/admin-experience/issues/571 {% endcomment %}' - - '从早期版本升级时，可能无法生成后台作业工作进程，从而阻止合并拉取请求等基本功能。（更新时间：2020-04-07）{% comment %} https://github.com/github/enterprise2/issues/19232 {% endcomment %}' - - '推送到命令行上的存储库时，不会报告安全警报。（更新时间于 2020-06-23）{% comment %} https://github.com/github/github/issues/143190 {% endcomment %}' - - '依赖项关系图在具有多个 Redis 节点的群集配置中部署时不会检测依赖项。（更新时间时间：2020-06-30）{% comment %} https://github.com/github/dependency-graph/issues/81 {% 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-20/10.yml b/translations/zh-CN/data/release-notes/enterprise-server/2-20/10.yml deleted file mode 100644 index 2dc1fa1665..0000000000 --- a/translations/zh-CN/data/release-notes/enterprise-server/2-20/10.yml +++ /dev/null @@ -1,21 +0,0 @@ -date: '2020-06-23' -sections: - security_fixes: - - '包已更新到最新的安全版本。{% comment %} https://github.com/github/enterprise2/pull/20746, https://github.com/github/enterprise2/pull/20727 {% endcomment %}' - bugs: - - '当使用 UDP 作为传输机制时，过大的日志事件可能导致日志转发不稳定。{% comment %} https://github.com/github/enterprise2/pull/20457, https://github.com/github/enterprise2/pull/20445 {% endcomment %}' - - "如果 SSH 密钥属性具有已与用户帐户关联的密钥，则用户通过 SSO 进行的自动取消暂停未完成。 {% comment %} https://github.com/github/github/pull/143474, https://github.com/github/github/pull/142927 {% endcomment %}" - - '来自 REST API 的仓库权限哈希表示，对于可拉取访问内部仓库的业务成员，无法访问仓库。 {% comment %} https://github.com/github/github/pull/144755, https://github.com/github/github/pull/144292 {% endcomment %}' - - '预览 Markdown 中写入的 GitHub 应用程序描述未正确呈现。{% comment %} https://github.com/github/github/pull/145038, https://github.com/github/github/pull/133360 {% endcomment %}' - - '审核日志不包括分支保护更改事件。 {% comment %} https://github.com/github/github/pull/145995, https://github.com/github/github/pull/145014 {% endcomment %}' - - "尝试将代码审核分配给空团队成员将导致“500内部服务器错误”。 {% comment %} https://github.com/github/github/pull/146328, https://github.com/github/github/pull/139330 {% endcomment %}" - - '使用负载平衡算法的代码审核分配可能反复分配给同一团队成员。{% comment %} https://github.com/github/github/pull/146329, https://github.com/github/github/pull/136504 {% endcomment %}' - 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 %}' - - '议题若是包含同一仓库中文件路径长于 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 %}' - - '依赖项关系图在多个 Redis 节点的群集配置中部署时不会检测依赖项。（更新于 2020-06-30）{% comment %} https://github.com/github/dependency-graph/issues/81 {% 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-20/11.yml b/translations/zh-CN/data/release-notes/enterprise-server/2-20/11.yml deleted file mode 100644 index 9e09ac9a05..0000000000 --- a/translations/zh-CN/data/release-notes/enterprise-server/2-20/11.yml +++ /dev/null @@ -1,19 +0,0 @@ -date: '2020-07-09' -sections: - security_fixes: - - '**中：** 将 nginx 更新到 1.16.1 并解决了 CV-2019-20372。（更新于 2020-07-22）{% comment %} https://github.com/github/enterprise2/pull/21251 {% endcomment %}' - - '包已更新到最新的安全版本。{% comment %} https://github.com/github/enterprise2/pull/21088, https://github.com/github/enterprise2/pull/21036 {% endcomment %}' - bugs: - - '依赖项关系图在多个 Redis 节点的群集配置中部署时不会检测依赖项。{% comment %} https://github.com/github/enterprise2/pull/21260, https://github.com/github/enterprise2/pull/21102 {% endcomment %}' - - '某些日志文件没有每 7 天轮换一次。 {% comment %} https://github.com/github/enterprise2/pull/21278, https://github.com/github/enterprise2/pull/21264 {% endcomment %}' - - '快速重新使用 web 挂钩源端口导致拒绝连接。 {% comment %} https://github.com/github/enterprise2/pull/21289 {% endcomment %}' - - '不正确的背景作业可能尝试在配置为被动副本的实例上运行。{% comment %} https://github.com/github/enterprise2/pull/21318, https://github.com/github/enterprise2/pull/21212, https://github.com/github/enterprise2/issues/21167 {% endcomment %}' - - '内部仓库未正确地包含在启用 SAML 的组织的搜索结果中。 {% comment %} https://github.com/github/github/pull/147503, https://github.com/github/github/pull/145692 {% endcomment %}' - 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 %}' - - '议题若是包含同一仓库中文件路径长于 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 %}' - - '当副本节点在高可用性配置下离线时，{% 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-20/12.yml b/translations/zh-CN/data/release-notes/enterprise-server/2-20/12.yml deleted file mode 100644 index c370c177fb..0000000000 --- a/translations/zh-CN/data/release-notes/enterprise-server/2-20/12.yml +++ /dev/null @@ -1,17 +0,0 @@ -date: '2020-07-21' -sections: - security_fixes: - - '包已更新到最新的安全版本。{% comment %} https://github.com/github/enterprise2/pull/21437, https://github.com/github/enterprise2/pull/21402, https://github.com/github/enterprise2/pull/21495, https://github.com/github/enterprise2/pull/21479 {% endcomment %}' - bugs: - - '管理控制台监视图有时无法在更大的屏幕上正确显示。 {% comment %} https://github.com/github/enterprise2/pull/21397, https://github.com/github/enterprise2/pull/21381 {% endcomment %}' - - '应用 SameSite Cookie 策略时，GitHub 应用程序清单创建流在某些情况下无法使用。 {% comment %} https://github.com/github/github/pull/147826, https://github.com/github/github/pull/144121 {% endcomment %}' - changes: - - '改进 HAProxy 缩放。 {% comment %} https://github.com/github/enterprise2/pull/21383 {% endcomment %}' - 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 %}' - - '议题若是包含同一仓库中文件路径长于 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 %}' - - '当副本节点在高可用性配置下离线时，{% 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-20/13.yml b/translations/zh-CN/data/release-notes/enterprise-server/2-20/13.yml deleted file mode 100644 index cf56d4e79f..0000000000 --- a/translations/zh-CN/data/release-notes/enterprise-server/2-20/13.yml +++ /dev/null @@ -1,22 +0,0 @@ -date: '2020-08-11' -sections: - security_fixes: - - '{% octicon "alert" aria-label="The alert icon" %} **关键：**在 GitHub Pages 中发现了一个远程执行代码漏洞，攻击者可利用该漏洞在构建 GitHub Pages 站点的过程中执行命令。此问题是由于在 Pages 构建过程中使用过时且易受攻击的依赖项造成的。要利用此漏洞，攻击者需要获得在 GitHub Enterprise Server 实例上创建和构建 GitHub Pages 站点的权限。 此漏洞影响 GitHub Enterprise Server 的所有版本。为了缓解此漏洞，Kramdown 已更新以解决 CVE-2020-14001。{% comment %} https://github.com/github/pages/pull/2836, https://github.com/github/pages/pull/2827 {% endcomment %}' - - '**高：**在 GitHub Enterprise Server 上执行时，攻击者可以将恶意参数注入 Git 子命令。这可能使攻击者能够使用用户控制的部分内容覆盖任意文件，并可能在 GitHub Enterprise Server 实例上执行任意命令。要利用此漏洞，攻击者需要获得访问 GitHub Enterprise Server 实例中存储库的权限。但是，由于存在其他保护措施，我们无法确定积极利用此漏洞的方法。此漏洞通过 GitHub 安全 Bug 悬赏计划报告。{% comment %} https://github.com/github/github/pull/151097 {% endcomment %}' - - '包已更新到最新的安全版本。{% comment %} https://github.com/github/enterprise2/pull/21811, https://github.com/github/enterprise2/pull/21700 {% endcomment %}' - bugs: - - 'Consul 配置错误导致无法在独立实例上处理某些后台作业。{% comment %} https://github.com/github/enterprise2/pull/21464 {% endcomment %}' - - '服务内存分配计算可能会将不正确或无限制的内存分配给某项服务，从而导致系统性能下降。{% comment %} https://github.com/github/enterprise2/pull/21716 {% endcomment %}' - - '未正确检测到 oVirt KVM 系统的虚拟化平台，导致升级过程中出现问题。{% comment %} https://github.com/github/enterprise2/pull/21730, https://github.com/github/enterprise2/pull/21669 {% endcomment %}' - - "通过 Git 命令行使用密码进行无效身份验证的错误消息未填充 URL 链接以添加适当的令牌或 SSH 密钥。{% comment %} https://github.com/github/github/pull/149714 {% endcomment %}" - - 'GitHub Connect 使用的是已弃用的 GitHub.com API 终结点。{% comment %} https://github.com/github/github/pull/150828, https://github.com/github/github/pull/150545 {% endcomment %}' - - '在迁移到新实例的存储库上，无法按 *最近更新* 对问题进行排序。{% comment %} https://github.com/github/github/pull/150843, https://github.com/github/github/pull/149330 {% endcomment %}' - - '404 页面的页脚中包含 GitHub.com 联系人和状态链接。{% comment %} https://github.com/github/github/pull/151316 {% endcomment %}' - 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 %}' - - '如果问题包含指向同一存储库中文件路径长于 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 %}' - - '当副本节点在高可用性配置中脱机时，{% 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-20/14.yml b/translations/zh-CN/data/release-notes/enterprise-server/2-20/14.yml deleted file mode 100644 index 048b4bdd5c..0000000000 --- a/translations/zh-CN/data/release-notes/enterprise-server/2-20/14.yml +++ /dev/null @@ -1,13 +0,0 @@ -date: '2020-08-12' -sections: - bugs: - - '解决了在生成系统配置模板时可能导致高 CPU 使用率的问题。{% comment %} https://github.com/github/enterprise2/pull/21784、https://github.com/github/enterprise2/pull/21741 {% endcomment %}' - - '最近对内存分配的更改可能导致系统性能降低 {% comment %} https://github.com/github/enterprise2/pull/22067 {% 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 %}' - - '如果问题包含同一存储库中文件路径长于 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 %}' - - '当副本节点在高可用性配置下离线时，{% 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-20/15.yml b/translations/zh-CN/data/release-notes/enterprise-server/2-20/15.yml deleted file mode 100644 index 01f9c1eed7..0000000000 --- a/translations/zh-CN/data/release-notes/enterprise-server/2-20/15.yml +++ /dev/null @@ -1,25 +0,0 @@ -date: '2020-08-26' -sections: - security_fixes: - - >- - {% octicon "alert" aria-label="The alert icon" %} **Critical:** A remote code execution vulnerability was identified in GitHub Pages that could be exploited when building a GitHub Pages site. User-controlled configuration of the underlying parsers used by GitHub Pages were not sufficiently restricted and made it possible to execute commands on the GitHub Enterprise Server instance. To exploit this vulnerability, an attacker would need permission to create and build a GitHub Pages site on the GitHub Enterprise Server instance. This vulnerability affected all versions of GitHub Enterprise Server. The underlying issues contributing to this vulnerability were identified both internally and through the GitHub Security Bug Bounty program. We have issued CVE-2020-10518. {% comment %} https://github.com/github/pages/pull/2883, https://github.com/github/pages/pull/2902, https://github.com/github/pages/pull/2894, https://github.com/github/pages/pull/2877, https://github.com/github/pages-gem/pull/700, - https://github.com/github/pages/pull/2890, https://github.com/github/pages/pull/2898, https://github.com/github/pages/pull/2909, https://github.com/github/pages/pull/2891, https://github.com/github/pages/pull/2884, https://github.com/github/pages/pull/2889 {% endcomment %} - - '**MEDIUM:** An improper access control vulnerability was identified that allowed authenticated users of the instance to determine the names of unauthorized private repositories given their numerical IDs. This vulnerability did not allow unauthorized access to any repository content besides the name. This vulnerability affected all versions of GitHub Enterprise Server prior to 2.22 and has been assigned [CVE-2020-10517](https://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2020-10517). The vulnerability was reported via the [GitHub Bug Bounty program](https://bounty.github.com). {% comment %} https://github.com/github/github/pull/151987, https://github.com/github/github/pull/151713 {% endcomment %}' - - 'Packages have been updated to the latest security versions. {% comment %} https://github.com/github/enterprise2/pull/21852, https://github.com/github/enterprise2/pull/21828, https://github.com/github/enterprise2/pull/22153, https://github.com/github/enterprise2/pull/21920, https://github.com/github/enterprise2/pull/22215, https://github.com/github/enterprise2/pull/22190 {% endcomment %}' - bugs: - - 'A message was not logged when the ghe-config-apply process had finished running ghe-es-auto-expand. {% comment %} https://github.com/github/enterprise2/pull/22177, https://github.com/github/enterprise2/pull/22171 {% endcomment %}' - - 'Excessive logging to the `syslog` file could occur on high-availability replicas if the primary appliance is unavailable. {% comment %} https://github.com/github/enterprise2/pull/22267, https://github.com/github/enterprise2/pull/22124 {% endcomment %}' - - "Database re-seeding on a replica could fail with an error: `Got packet bigger than 'max_allowed_packet'` {% comment %} https://github.com/github/enterprise2/pull/22321, https://github.com/github/enterprise2/pull/20063 {% endcomment %}" - - 'In some cases duplicate user data could cause a 500 error while running the ghe-license-usage script. {% comment %} https://github.com/github/github/pull/152638 {% endcomment %}' - changes: - - 'In a high availability or geo-replication configuration, replica instances would exit maintenance mode when ghe-config-apply ran. {% comment %} https://github.com/github/enterprise2/pull/21776, https://github.com/github/enterprise2/pull/21440 {% endcomment %}' - - "We've added support for the R5a and R5n AWS instance types. {% comment %} https://github.com/github/enterprise2/pull/21902, https://github.com/github/enterprise2/pull/21173 {% endcomment %}" - - 'Removed the license seat count information on the administrative SSH MOTD due to a performance issue impacting GitHub Enterprise Server clusters. {% comment %} https://github.com/github/enterprise2/pull/21993, https://github.com/github/enterprise2/pull/21870 {% endcomment %}' - known_issues: - - 'On a freshly set up GitHub Enterprise Server without any users, an attacker could create the first admin user. {% comment %} https://github.com/github/enterprise2/issues/1889 {% endcomment %}' - - 'Custom firewall rules are not maintained during an upgrade. {% comment %} https://github.com/github/enterprise2/issues/2823 {% endcomment %}' - - '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. {% comment %} https://github.com/github/github/issues/54684 {% endcomment %}' - - '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. {% comment %} https://github.com/github/github/issues/107731 {% endcomment %}' - - '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. {% comment %} https://github.com/github/admin-experience/issues/571 {% endcomment %}' - - 'Security alerts are not reported when pushing to a repository on the command line. {% comment %} https://github.com/github/github/issues/143190 {% endcomment %}' - - '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.' 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 deleted file mode 100644 index fa27d40c7b..0000000000 --- a/translations/zh-CN/data/release-notes/enterprise-server/2-20/16.yml +++ /dev/null @@ -1,13 +0,0 @@ -date: '2020-09-08' -sections: - bugs: - - '服务运行状况检查会造成会话增加，从而耗尽文件系统 Inode。{% comment %} https://github.com/github/enterprise2/pull/22480, https://github.com/github/enterprise2/pull/22475 {% endcomment %}' - - "使用热补丁的升级可能会失败，并显示错误：`'libdbi1' was not found` {% comment %} https://github.com/github/enterprise2/pull/22558，https://github.com/github/enterprise2/pull/22552 {% endcomment %}" - 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 %}' - - '如果问题包含指向同一存储库中文件路径长于 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 %}' - - '当副本节点在高可用性配置中脱机时，{% 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-20/17.yml b/translations/zh-CN/data/release-notes/enterprise-server/2-20/17.yml deleted file mode 100644 index 39d615a7f2..0000000000 --- a/translations/zh-CN/data/release-notes/enterprise-server/2-20/17.yml +++ /dev/null @@ -1,13 +0,0 @@ -date: '2020-09-23' -sections: - security_fixes: - - '中****：ImageMagick 已更新，以解决 [DSA-4715-1](https://www.debian.org/security/2020/dsa-4715)。{% comment %} https://github.com/github/enterprise2/pull/22625, https://github.com/github/enterprise2/pull/22610 {% endcomment %}' - - '包已更新到最新安全版本。{% comment %} https://github.com/github/enterprise2/pull/22601, https://github.com/github/enterprise2/pull/22592, https://github.com/github/enterprise2/pull/22605, https://github.com/github/enterprise2/pull/22426, https://github.com/github/enterprise2/pull/22718, https://github.com/github/enterprise2/pull/22699 {% 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 %}' - - '如果问题包含同一存储库中文件路径长于 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 %}' - - '当副本节点在高可用性配置下离线时，{% 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-20/18.yml b/translations/zh-CN/data/release-notes/enterprise-server/2-20/18.yml deleted file mode 100644 index 9bdfe66a37..0000000000 --- a/translations/zh-CN/data/release-notes/enterprise-server/2-20/18.yml +++ /dev/null @@ -1,26 +0,0 @@ -date: '2020-10-09' -sections: - security_fixes: - - 'LDAP 目录用户名标准化为现有 GHES 帐户登录的用户可以验证现有帐户。{% comment %} https://github.com/github/github/pull/156518, https://github.com/github/github/pull/155512 {% endcomment %}' - - '包已更新到最新的安全版本。{% comment %} https://github.com/github/enterprise2/pull/22910, https://github.com/github/enterprise2/pull/22878 {% endcomment %}' - bugs: - - '管理控制台中的 NameID 格式下拉列表将在设置为“持久”之后重置为“未指定”。{% comment %} https://github.com/github/enterprise2/pull/22403, https://github.com/github/enterprise2/pull/22331, https://github.com/github/enterprise2/issues/13446 {% endcomment %}' - - '通过[管理控制台](/admin/configuration/accessing-the-management-console)保存设置将附加一个新行到 [TLS/SSL 证书和密钥](/admin/configuration/configuring-tls)文件，这触发了某些服务的不必要重新加载。{% comment %} https://github.com/github/enterprise2/pull/22607, https://github.com/github/enterprise2/pull/22540 {% endcomment %}' - - '依赖关系图的系统日志没有旋转，允许无限存储增长。{% comment %} https://github.com/github/enterprise2/pull/22765, https://github.com/github/enterprise2/pull/22733 {% endcomment %}' - - '到 GitHub 安全通告的链接将使用 GitHub Enterprise Server 实例主机名的 URL 而不是 GitHub.com，将用户引导到不存在的 URL。{% comment %} https://github.com/github/github/pull/153444, https://github.com/github/github/pull/151301 {% endcomment %}' - - '使用 `ghe-migrator` 导入存储库时，如果数据不一致，可能发生意外异常。{% comment %} https://github.com/github/github/pull/153848, https://github.com/github/github/pull/151552 {% endcomment %}' - - '当使用 `ghe-migrator` 导入 PR 审核请求时，与删除用户相关的记录将产生外部数据库记录。{% comment %} https://github.com/github/github/pull/154958, https://github.com/github/github/pull/153169 {% endcomment %}' - - '使用 `ghe-migrator` 导入用户时，如果系统生成的电子邮件地址超过 100 个字符，则会出现“电子邮件无效”的错误。{% comment %} https://github.com/github/github/pull/155112, https://github.com/github/github/pull/152418 {% endcomment %}' - - '记录 Webhook 活动可能会使用大量的磁盘空间，并导致根盘变满。{% comment %} https://github.com/github/github/pull/155655, https://github.com/github/github/pull/154100 {% endcomment %}' - changes: - - '为 AWS EC2 实例类型 `m5.16xlarge` 添加了支持。{% comment %} https://github.com/github/enterprise2/pull/22500, https://github.com/github/enterprise2/pull/22473 {% endcomment %}' - - '删除 `ghe-migrator` 档案中 SSH 指纹的要求，因为它可以随时计算。{% comment %} https://github.com/github/github/pull/156944, https://github.com/github/github/pull/155387 {% endcomment %}' - - 'GitHub App 清单现在包含 `request_oauth_on_install` 字段。{% comment %} https://github.com/github/github/pull/156996, https://github.com/github/github/pull/155010, https://github.com/github/ecosystem-apps/issues/1055 {% 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 %}' - - '如果问题包含同一存储库中文件路径长于 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 %}' - - '当副本节点在高可用性配置下离线时，{% 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-20/19.yml b/translations/zh-CN/data/release-notes/enterprise-server/2-20/19.yml deleted file mode 100644 index 848ad4fa39..0000000000 --- a/translations/zh-CN/data/release-notes/enterprise-server/2-20/19.yml +++ /dev/null @@ -1,14 +0,0 @@ -date: '2020-10-20' -sections: - security_fixes: - - '包已更新到最新的安全版本。{% comment %} https://github.com/github/enterprise2/pull/23095, https://github.com/github/enterprise2/pull/23081 {% endcomment %}' - bugs: - - '企业帐户“确认双因素要求策略”消息不正确。{% comment %} https://github.com/github/github/pull/158737 {% endcomment %}' - 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 %}' - - '如果问题包含同一存储库中文件路径长于 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 %}' - - '当副本节点在高可用性配置下脱机时，{% 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-20/2.yml b/translations/zh-CN/data/release-notes/enterprise-server/2-20/2.yml deleted file mode 100644 index 76e0513b0c..0000000000 --- a/translations/zh-CN/data/release-notes/enterprise-server/2-20/2.yml +++ /dev/null @@ -1,28 +0,0 @@ -date: '2020-03-10' -sections: - security_fixes: - - '包已更新到最新的安全版本。{% comment %} https://github.com/github/enterprise2/pull/19204, https://github.com/github/enterprise2/pull/19187 {% endcomment %}' - bugs: - - '在某些情况下，转发的日志条目（主要用于 audit.log）被截断。{% comment %} https://github.com/github/enterprise2/pull/19244, https://github.com/github/enterprise2/pull/19192, https://github.com/github/enterprise2/issues/16655 {% endcomment %}' - - '`ghe-license-check` 命令行实用程序对某些有效的许可返回“无效的许可证文件”错误，导致配置更改失败。{% comment %} https://github.com/github/enterprise2/pull/19249, https://github.com/github/enterprise2/pull/19185, https://github.zendesk.com/agent/tickets/549903 {% endcomment %}' - - 'Alambic 异常日志没有被 syslog 转发。{% comment %} https://github.com/github/enterprise2/pull/19263, https://github.com/github/enterprise2/pull/19123, https://github.com/github/enterprise2/issues/18734 {% endcomment %}' - - '[`org_block event`](https://developer.github.com/v3/activity/events/types/#orgblockevent) 并非不可用，但在 GitHub Enterprise Server 上的 GitHub 应用中显示。{% comment %} https://github.com/github/github/pull/136227, https://github.com/github/github/pull/135640, https://github.com/github/ecosystem-apps/issues/693 {% endcomment %}' - - 'GraphQL 查询响应有时返回 `ProtectedBranch` 对象的不匹配节点标识符。{% comment %} https://github.com/github/github/pull/136376, https://github.com/github/github/pull/136214, https://github.com/github/github/issues/135407 {% endcomment %}' - - 'GitHub Connect 使用的 GitHub 应用凭据在过期后未能立即刷新。{% comment %} https://github.com/github/github/pull/136384, https://github.com/github/github/pull/136259 {% endcomment %}' - - '在回复拉请求评论时留下评论会间歇性地创建挂起拉请求审查。{% comment %} https://github.com/github/github/pull/136454, https://github.com/github/github/pull/133697, https://github.com/github/github/issues/127401 {% endcomment %}' - - '使用 ghe-migrator 或从 GitHub.com 导出时，导出非图片附件会自动失败。{% comment %} https://github.com/github/github/pull/136487, https://github.com/github/github/pull/134524, https://github.com/github/github/issues/134358 {% endcomment %}' - - '在遇到 UTF-8 字符时，预接收挂钩会在 Web UI 上返回 500 错误。{% comment %} https://github.com/github/github/pull/136699, https://github.com/github/github/pull/136014, https://github.com/github/github/issues/133501 {% endcomment %}' - changes: - - '` ghe-license-usage ` 命令行实用程序新增了 `--unencrypted` 选项，用于查看导出的许可使用文件。{% comment %} https://github.com/github/github/pull/136134, https://github.com/github/github/pull/136000 {% 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 %}' - - '问题若是包含同一存储库中文件路径长于 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 %}' - - '对 GitHub Connect 启用“用户可以搜索 GitHub.com”后，专用和内部存储库中的问题不包括在 GitHub.com 搜索结果中。{% comment %} https://github.com/github/admin-experience/issues/571 {% endcomment %}' - - '从早期版本升级时，可能无法生成后台作业工作进程，从而阻止合并拉取请求等基本功能。（更新时间：2020-04-07）{% comment %} https://github.com/github/enterprise2/issues/19232 {% endcomment %}' - - '推送到命令行上的仓库时，不会报告安全警报。（更新时间：2020-06-23）{% comment %} https://github.com/github/github/issues/143190 {% endcomment %}' - - '依赖项关系图在多个 Redis 节点的群集配置中部署时不会检测依赖项。（更新时间：2020-06-30）{% comment %} https://github.com/github/dependency-graph/issues/81 {% 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-20/20.yml b/translations/zh-CN/data/release-notes/enterprise-server/2-20/20.yml deleted file mode 100644 index dab45f31dd..0000000000 --- a/translations/zh-CN/data/release-notes/enterprise-server/2-20/20.yml +++ /dev/null @@ -1,16 +0,0 @@ -date: '2020-11-03' -sections: - security_fixes: - - '**中：**高 CPU 使用可能被特殊构建的 SVN 桥请求触发，导致 SVN 桥服务上的拒绝服务 (DoS)。{% comment %} https://github.com/github/slumlord/pull/1003, https://github.com/github/slumlord/pull/1000 {% endcomment %}' - - "**低：**不正确的令牌验证导致身份验证期间匹配令牌的熵减少。分析表明，在实践中，这里没有重大的安全风险。{% comment %} https://github.com/github/github/pull/159453, https://github.com/github/github/pull/159193 {% endcomment %}" - - '包已更新到最新的安全版本。{% comment %} https://github.com/github/enterprise2/pull/23538, https://github.com/github/enterprise2/pull/23171, https://github.com/github/enterprise2/pull/23691, https://github.com/github/enterprise2/pull/23677 {% endcomment %}' - bugs: - - '推荐用户列表中包含已暂停的用户，其中可能隐藏未暂停的用户。{% comment %} https://github.com/github/github/pull/159809, https://github.com/github/github/pull/140563, https://github.com/github/github/pull/142146 {% endcomment %}' - 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 %}' - - '如果问题包含指向同一存储库中文件路径长于 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 %}' - - '当副本节点在高可用性配置中脱机时，{% 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-20/21.yml b/translations/zh-CN/data/release-notes/enterprise-server/2-20/21.yml deleted file mode 100644 index fe9d3649d4..0000000000 --- a/translations/zh-CN/data/release-notes/enterprise-server/2-20/21.yml +++ /dev/null @@ -1,15 +0,0 @@ -date: '2020-11-17' -sections: - security_fixes: - - '包已更新到最新的安全版本。{% comment %} https://github.com/github/enterprise2/pull/23843、https://github.com/github/enterprise2/pull/23712 {% endcomment %}' - bugs: - - 'Babeld 日志在秒与微秒之间缺少分隔符。{% comment %} https://github.com/github/babeld/pull/1004、https://github.com/github/babeld/pull/1002 {% endcomment %}' - - '当企业帐户“存储库可见性更改”策略设置为“启用”时，组织所有者无法更改组织内存储库的可见性。{% comment %} https://github.com/github/github/pull/160922、https://github.com/github/github/pull/160773 {% 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 %}' - - '如果问题包含同一存储库中文件路径长于 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 %}' - - '当副本节点在高可用性配置下离线时，{% 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-20/22.yml b/translations/zh-CN/data/release-notes/enterprise-server/2-20/22.yml deleted file mode 100644 index da27dc46d1..0000000000 --- a/translations/zh-CN/data/release-notes/enterprise-server/2-20/22.yml +++ /dev/null @@ -1,19 +0,0 @@ -date: '2020-12-03' -sections: - bugs: - - '由于启动中的争用条件导致服务重新启动，因此检测到授权服务不正常。{% comment %} https://github.com/github/authzd/pull/1279, {% endcomment %}' - - '在热补丁升级过程中，一种基础行为导致服务不可用。{% comment %} https://github.com/github/enterprise2/pull/24053, https://github.com/github/enterprise2/issues/23947 {% endcomment %}' - - '未正确应用部分日志转发 SSL 证书。{% comment %} https://github.com/github/enterprise2/pull/24112, https://github.com/github/enterprise2/pull/23981 {% endcomment %}' - - '从团队或组织中移除暂停用户时向他们发送电子邮件通知。{% comment %} https://github.com/github/github/pull/163107, https://github.com/github/github/pull/162742 {% endcomment %}' - - '组织和企业之间应用 SSH 证书的方式不一致。{% comment %} https://github.com/github/github/pull/163429, https://github.com/github/github/pull/159538, https://github.com/github/authentication/issues/115 {% endcomment %}' - - '当帐户因使用不正确的密码而受到速率限制时，可能被锁定长达 24 小时。{% comment %} https://github.com/github/github/pull/163456, https://github.com/github/github/pull/162938, https://github.com/github/github-ds/pull/51 {% endcomment %}' - - '在具有许多引用的存储库上进行拉取请求同步可能会导致工作线程队列落后。{% comment %} https://github.com/github/github/pull/163576, https://github.com/github/github/pull/163142 {% endcomment %}' - - '在尝试访问特定页面后登录时，用户将发送到主页，而不是其预期目的地。{% comment %} https://github.com/github/github/pull/163785, https://github.com/github/github/pull/163579, https://github.com/github/github/pull/154117, https://github.com/github/ecosystem-apps/issues/1076 {% endcomment %}' - 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 %}' - - '如果问题包含指向同一存储库中文件路径长于 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 %}' - - '当副本节点在高可用性配置中脱机时，{% 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-20/23.yml b/translations/zh-CN/data/release-notes/enterprise-server/2-20/23.yml deleted file mode 100644 index cbf6780351..0000000000 --- a/translations/zh-CN/data/release-notes/enterprise-server/2-20/23.yml +++ /dev/null @@ -1,13 +0,0 @@ -date: '2020-12-17' -sections: - security_fixes: - - '低：****高 CPU 使用可能被特殊构建的 SVN 桥请求触发，进而导致 SVN 桥服务上的拒绝服务 (DoS)。{% comment %} https://github.com/github/slumlord/pull/1020, https://github.com/github/slumlord/pull/1017 {% endcomment %}' - - '包已更新到最新安全版本。{% comment %} https://github.com/github/enterprise2/pull/24351, https://github.com/github/enterprise2/pull/23866 {% 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 %}' - - '如果问题包含同一存储库中文件路径长于 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 %}' - - '当副本节点在高可用性配置下离线时，{% 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-20/24.yml b/translations/zh-CN/data/release-notes/enterprise-server/2-20/24.yml deleted file mode 100644 index 5c62b29244..0000000000 --- a/translations/zh-CN/data/release-notes/enterprise-server/2-20/24.yml +++ /dev/null @@ -1,28 +0,0 @@ -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/)报告的。' - - '**低：**对 SVN 桥的特别设计请求可能会触发长时间的等待，然后再导致拒绝服务 (DoS)。' - - '包已更新到最新的安全版本。' - bugs: - - '在 GitHub Enterprise 备份实用程序快照期间，信息性消息被无意中记录为错误，这导致在备份由侦听输出到 stderr 的 cron 作业安排时发送不必要的电子邮件。' - - '在恢复大型备份时，与 Redis 内存耗尽相关的异常记录可能导致恢复由于完整磁盘而出现故障。' - - '在编辑 wiki 页面时，用户单击“保存”按钮时可能会遇到 500 错误。' - - '使用主题替代名称中具有多个名称的证书签名的 S/MIME 签名提交将错误地显示为提交徽章中的“未验证”。' - - '被暂停的用户在添加到团队时收到电子邮件。' - - '上传与之前许可证文件不同数量的新许可证文件时，席位差异在企业帐户的“设置”->“许可证”页面中未正确表示。' - - '无法成功启用或禁用企业帐户设置中的“防止存储库管理员更改匿名 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/)支持。' - - '调整的背景队列排列优先顺序，以更均匀地分配作业。' - known_issues: - - '在新建的没有任何用户的 GitHub Enterprise Server 上，攻击者可以创建第一个管理员用户。' - - '在升级期间不会维护自定义防火墙规则。' - - '[通过 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-20/3.yml b/translations/zh-CN/data/release-notes/enterprise-server/2-20/3.yml deleted file mode 100644 index c13bcaf404..0000000000 --- a/translations/zh-CN/data/release-notes/enterprise-server/2-20/3.yml +++ /dev/null @@ -1,15 +0,0 @@ -date: '2020-03-12' -sections: - bugs: - - '如果自定义了后台工作进程配置，升级和设置更新将失败。{% comment %} https://github.com/github/enterprise2/pull/19321, https://github.com/github/enterprise2/pull/19299 {% 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 %}' - - '问题若是包含同一存储库中文件路径长于 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 %}' - - '从早期版本升级时，可能无法生成后台作业工作进程，从而阻止合并拉取请求等基本功能。（更新时间：2020-04-07）{% comment %} https://github.com/github/enterprise2/issues/19232 {% endcomment %}' - - '推送到命令行上的存储库时，不会报告安全警报。（更新时间于 2020-06-23）{% comment %} https://github.com/github/github/issues/143190 {% endcomment %}' - - '依赖项关系图在具有多个 Redis 节点的群集配置中部署时不会检测依赖项。（更新时间时间：2020-06-30）{% comment %} https://github.com/github/dependency-graph/issues/81 {% 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-20/4.yml b/translations/zh-CN/data/release-notes/enterprise-server/2-20/4.yml deleted file mode 100644 index 7322860bb3..0000000000 --- a/translations/zh-CN/data/release-notes/enterprise-server/2-20/4.yml +++ /dev/null @@ -1,18 +0,0 @@ -date: '2020-03-25' -sections: - bugs: - - 'SAML 身份验证请求和元数据没有严格编码，导致一些标识提供者无法正确处理服务提供者发起的身份验证请求。{% comment %} https://github.com/github/github/pull/137150, https://github.com/github/github/pull/136770, https://github.com/github/github/issues/136766 {% endcomment %}' - - '`ghe-migrator` 导出不含里程碑用户，可能会中断导入操作。{% comment %} https://github.com/github/github/pull/138100, https://github.com/github/github/pull/137987, https://github.com/github/github/issues/137779 {% endcomment %}' - - '推送到 Gist 时，可能会在后接收挂钩时触发异常。{% comment %} https://github.com/github/github/pull/138460, https://github.com/github/github/pull/138313 {% endcomment %}' - - '在尝试显示未完全复制的存储库时，`ghe-repl-status` 可能会失败。{% comment %} https://github.com/github/github/pull/138463, https://github.com/github/github/pull/138388 {% 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 %}' - - '问题若是包含同一存储库中文件路径长于 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 %}' - - '从早期版本升级时，可能无法生成后台作业工作进程，从而阻止合并拉取请求等基本功能。（更新时间：2020-04-07）{% comment %} https://github.com/github/enterprise2/issues/19232 {% endcomment %}' - - '推送到命令行上的存储库时，不会报告安全警报。（更新时间于 2020-06-23）{% comment %} https://github.com/github/github/issues/143190 {% endcomment %}' - - '依赖项关系图在具有多个 Redis 节点的群集配置中部署时不会检测依赖项。（更新时间时间：2020-06-30）{% comment %} https://github.com/github/dependency-graph/issues/81 {% 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-20/5.yml b/translations/zh-CN/data/release-notes/enterprise-server/2-20/5.yml deleted file mode 100644 index 79bb908419..0000000000 --- a/translations/zh-CN/data/release-notes/enterprise-server/2-20/5.yml +++ /dev/null @@ -1,20 +0,0 @@ -date: '2020-04-07' -sections: - security_fixes: - - '包已更新到最新的安全版本。{% comment %} https://github.com/github/enterprise2/pull/19536, https://github.com/github/enterprise2/pull/19494 {% endcomment %}' - bugs: - - '当全球企业帐户设置了 100MB 以外的 Git 对象大小选项时，无法为存储库选择 100MB 大小的最大 Git 对象选项。{% comment %} https://github.com/github/github/pull/138805, https://github.com/github/github/pull/138683 {% endcomment %}' - - '当按 `updated_at` 字段排序时，问题和拉取请求 API 的结果可能存在不一致的行为。{% comment %} https://github.com/github/github/pull/139247, https://github.com/github/github/pull/138486 {% endcomment %}' - - '无法通过 GraphQL API 查询 SecurityVulnerability `package` 字段。{% comment %} https://github.com/github/github/pull/139418, https://github.com/github/github/pull/138245 {% endcomment %}' - - '将存储库从*公共*更改为*内部*会显示一条不相关的计费消息。{% comment %} https://github.com/github/github/pull/139531, https://github.com/github/github/pull/139492 {% endcomment %}' - 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 %}' - - '如果问题包含指向同一存储库中文件路径长于 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 %}' - - '从以前的版本升级时，可能不会生成后台作业工作者，从而阻止基本功能，例如合并拉取请求。{% comment %} https://github.com/github/enterprise2/issues/19232 {% endcomment %}' - - '在命令行上推送到存储库时不会报告安全警报。（2020 年 6 月 23 日更新）{% comment %} https://github.com/github/github/issues/143190 {% endcomment %}' - - '依赖项关系图在具有多个 Redis 节点的群集配置中部署时不会检测依赖项。（2020 年 6 月 30 日更新）{% comment %} https://github.com/github/dependency-graph/issues/81 {% 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-20/6.yml b/translations/zh-CN/data/release-notes/enterprise-server/2-20/6.yml deleted file mode 100644 index cef61a882a..0000000000 --- a/translations/zh-CN/data/release-notes/enterprise-server/2-20/6.yml +++ /dev/null @@ -1,27 +0,0 @@ -date: '2020-04-23' -sections: - security_fixes: - - '**高**：OpenSSL 已更新以解决 [CVE-2020-1967](https://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2020-1967)。{% comment %} https://github.com/github/enterprise2/pull/19889、https://github.com/github/enterprise2/pull/19885 {% endcomment %}' - - '**高**：Git 已更新以解决 [CVE-2020-5260](https://github.com/git/git/security/advisories/GHSA-qm7j-c969-7j4q) 和 [CVE-2020-11008](https://github.com/git/git/security/advisories/GHSA-hjc9-x69f-jqj7)。新限制可防止恶意存储库被推入服务器实例，从而保护尚未修补的客户端。{% comment %} https://github.com/github/git/pull/990 {% endcomment %}' - - '**低**：ImageMagick 已更新以解决 [CVE-2019-10131](https://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2019-10131)。{% comment %} https://github.com/github/enterprise2/pull/19655、https://github.com/github/enterprise2/pull/19617 {% endcomment %}' - - '包已更新到最新的安全版本。{% comment %} https://github.com/github/enterprise2/pull/19809、https://github.com/github/enterprise2/pull/19792、https://github.com/github/enterprise2/pull/19899、https://github.com/github/enterprise2/pull/19882 {% endcomment %}' - bugs: - - 'Git 用户没有权限调用使用 Subversion 将现有存储库从 v4 格式转换为 v3 LRS 所需的进程。{% comment %} https://github.com/github/enterprise2/pull/19465、https://github.com/github/enterprise2/pull/19150 {% endcomment %}' - - 'MySQL 配置中的不匹配可能导致备份在大型安装中失败。{% comment %} https://github.com/github/enterprise2/pull/19688、https://github.com/github/enterprise2/pull/19409、https://github.com/github/enterprise2/issues/19055 {% endcomment %}' - - '从以前的版本升级时，后台作业工作进程有时不会生成，从而阻止诸如合并拉取请求等基本功能。{% comment %} https://github.com/github/enterprise2/pull/19771、https://github.com/github/enterprise2/pull/19712 {% endcomment %}' - - "当 GitHub Enterprise Server 许可证包含非 ASCII 字符时，对管理控制台的 API `/setup/api/settings` 终结点的 `GET` 请求将导致内部服务器错误。{% comment %} https://github.com/github/enterprise2/pull/19790 {% endcomment %}" - - '即使根帐户已锁定，恢复控制台也会提示输入根密码。{% comment %} https://github.com/github/enterprise2/pull/19810、https://github.com/github/enterprise2/pull/19788、https://github.com/github/enterprise2/issues/18425 {% endcomment %}' - - '具有前导 UTF-8 字节顺序标记的 CODEOWNERS 文件将导致忽略所有代码所有者规则。{% comment %} https://github.com/github/github/pull/140974、https://github.com/github/github/pull/140729 {% endcomment %}' - changes: - - '当业务流程协调程序-客户端 cron 作业失败时，将向根帐户发送多封电子邮件。{% comment %} https://github.com/github/enterprise2/pull/19761、https://github.com/github/enterprise2/pull/19748 {% endcomment %}' - - "当外部标识提供者控制用户的站点管理员状态时，无法通过命令行实用程序降级用户。{% comment %} https://github.com/github/github/pull/140522、https://github.com/github/github/pull/137807、https://github.com/github/github/issues/42727 {% 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 %}' - - '如果问题包含同一存储库中文件路径长于 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 %}' - - '推送到命令行上的存储库时，不会报告安全警报。（更新时间：2020-06-23）{% comment %} https://github.com/github/github/issues/143190 {% endcomment %}' - - '依赖项关系图在具有多个 Redis 节点的群集配置中部署时不会检测依赖项。（更新时间：2020-06-30）{% comment %} https://github.com/github/dependency-graph/issues/81 {% 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-20/7.yml b/translations/zh-CN/data/release-notes/enterprise-server/2-20/7.yml deleted file mode 100644 index 6755e6d22c..0000000000 --- a/translations/zh-CN/data/release-notes/enterprise-server/2-20/7.yml +++ /dev/null @@ -1,21 +0,0 @@ -date: '2020-05-05' -sections: - security_fixes: - - '包已更新到最新的安全版本。{% comment %} https://github.com/github/enterprise2/pull/20027, https://github.com/github/enterprise2/pull/19997 {% endcomment %}' - bugs: - - '`ghe-repl-start` 和 `ghe-repl-status` 显示了语法错误。{% comment %} https://github.com/github/enterprise2/pull/19954, https://github.com/github/enterprise2/pull/19927 {% endcomment %}' - - '如果仓库启用了“自动删除头分支”设置，则当 GitHub App 安装合并拉取请求时，头部分支不会自动删除。{% comment %} https://github.com/github/github/pull/141588, https://github.com/github/github/pull/133698, https://github.com/github/github/pull/133871, https://github.com/github/github/issues/132588 {% endcomment %}' - - '当组织成员恢复时，web 挂钩有效负载将 `ghost` 用户报告为发送者，而不是执行恢复的实际用户。{% comment %} https://github.com/github/github/pull/141731, https://github.com/github/github/pull/140609 {% endcomment %}' - - '如果仓库启用了“自动删除头部分支”设置，则在头部仓库不同于基础仓库的地方，头部分支不会被自动删除。{% comment %} https://github.com/github/github/pull/142096, https://github.com/github/github/pull/133871 {% endcomment %}' - - '临时文件的垃圾收集可能导致许可证验证错误。{% comment %} https://github.com/github/github/pull/142209, https://github.com/github/github/pull/142189 {% endcomment %}' - - '在某些情况下，包括在首次创建仓库时，接收前挂钩将在没有为 GITHUBHUBB_REPO_PUBLIC 环境变量填写值的情况下运行。{% comment %} https://github.com/github/github/pull/139419, https://github.com/github/github/pull/136228, https://github.com/github/github/pull/134363 {% endcomment %}' - 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 %}' - - '如果问题包含指向同一存储库中文件路径长于 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 %}' - - '推送到命令行上的存储库时，不会报告安全警报。（更新时间：2020-06-23）{% comment %} https://github.com/github/github/issues/143190 {% endcomment %}' - - '依赖项关系图在具有多个 Redis 节点的群集配置中部署时不会检测依赖项。（2020 年 6 月 30 日更新）{% comment %} https://github.com/github/dependency-graph/issues/81 {% 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-20/8.yml b/translations/zh-CN/data/release-notes/enterprise-server/2-20/8.yml deleted file mode 100644 index 3d89e875db..0000000000 --- a/translations/zh-CN/data/release-notes/enterprise-server/2-20/8.yml +++ /dev/null @@ -1,20 +0,0 @@ -date: '2020-05-19' -sections: - security_fixes: - - '包已更新到最新的安全版本。{% comment %} https://github.com/github/enterprise2/pull/20108, https://github.com/github/enterprise2/pull/20086 {% endcomment %}' - bugs: - - '许可证文件更新后，未正确重新加载服务，导致功能丢失。{% comment %} https://github.com/github/enterprise2/pull/20072, https://github.com/github/enterprise2/pull/19989 {% endcomment %}' - - '如果响应正文过大，内部 API 请求更新依赖项关系图信息可能会失败。{% comment %} https://github.com/github/enterprise2/pull/20231, https://github.com/github/enterprise2/pull/20208 {% endcomment %}' - - '未遵从某些 GraphQL 存储库连接的 `affiliations` 参数。{% comment %} https://github.com/github/github/pull/142036, https://github.com/github/github/pull/140658 {% endcomment %}' - - '如果 SAML 电子邮件属性与 GitHub 用户电子邮件大小写形式不同，则无法通过 SSO 自动取消暂停用户。{% comment %} https://github.com/github/github/pull/143321, https://github.com/github/github/pull/142915 {% endcomment %}' - - '将用户的成员身份恢复为组织没有在 Webhook 和审核日志有效负载中检测参与者。{% comment %} https://github.com/github/github/pull/143231, https://github.com/github/github/pull/140849 {% 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 %}' - - '问题若是包含同一存储库中文件路径长于 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 %}' - - '推送到命令行上的仓库时，不会报告安全警报。（更新时间：2020-06-23）{% comment %} https://github.com/github/github/issues/143190 {% endcomment %}' - - '依赖项关系图在多个 Redis 节点的群集配置中部署时不会检测依赖项。（更新时间：2020-06-30）{% comment %} https://github.com/github/dependency-graph/issues/81 {% 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-20/9.yml b/translations/zh-CN/data/release-notes/enterprise-server/2-20/9.yml deleted file mode 100644 index 3e01f8fba2..0000000000 --- a/translations/zh-CN/data/release-notes/enterprise-server/2-20/9.yml +++ /dev/null @@ -1,17 +0,0 @@ -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 %}' - - '包已更新到最新的安全版本。{% 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 %}' - - '问题若是包含同一存储库中文件路径长于 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 %}' - - '推送到命令行上的仓库时，不会报告安全警报。（更新时间：2020-06-23）{% comment %} https://github.com/github/github/issues/143190 {% endcomment %}' - - '依赖项关系图在多个 Redis 节点的群集配置中部署时不会检测依赖项。（更新时间：2020-06-30）{% comment %} https://github.com/github/dependency-graph/issues/81 {% 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-21/0.yml b/translations/zh-CN/data/release-notes/enterprise-server/2-21/0.yml deleted file mode 100644 index 7ff6239c4d..0000000000 --- a/translations/zh-CN/data/release-notes/enterprise-server/2-21/0.yml +++ /dev/null @@ -1,73 +0,0 @@ -date: '2020-06-09' -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://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://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 %}' - - '用户可以[在问题与拉取请求之间创建链接](https://help.github.com/en/enterprise/2.21/user/github/managing-your-work-on-github/linking-a-pull-request-to-an-issue#manually-linking-a-pull-request-to-an-issue)，而无需在拉取请求描述中使用结束关键词。{% comment %} https://github.com/github/releases/issues/704 {% endcomment %}' - 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://developer.github.com/changes/2020-02-26-new-delete-reactions-endpoints/ {% endcomment %}' - bugs: - - "如果具有推送访问权限的用户将另一个用户的评论最小化，则该评论的作者即使特权不足，也可以将其取消减小化。{% comment %} https://github.com/github/github/pull/141237 {% endcomment %}" - - '用户可能会意外地从问题模板编辑器和 Blob 编辑器中合并到主分支。{% comment %} https://github.com/github/github/pull/134483, https://github.com/github/github/pull/134323 {% endcomment %}' - - '当用户从 GitHub 中删除帐户时，审核日志记录没有正确显示组织删除记录。{% comment %} https://github.com/github/github/pull/140940 {% endcomment %}' - - '当前用户的 gist 头像将链接到一个不存在的 URL。{% comment %} https://github.com/github/github/pull/140925 {% endcomment %}' - - '组织存储库选项卡计数不包括内部存储库。{% comment %} https://github.com/github/github/pull/136323 {% endcomment %}' - - '在转移存储库时单击“显示所有团队”按钮造成了 500 错误。{% comment %} https://github.com/github/github/pull/134455 {% endcomment %}' - - "长文件名可能会在显示“自上次查看以来发生的变化”标签或在差异文件视图上显示“显示富”差异时造成溢出问题。{% comment %} https://github.com/github/github/pull/134453 {% endcomment %}" - - '组织团队的悬停卡误报其成员大小。{% comment %} https://github.com/github/github/pull/133879 {% endcomment %}' - - '拉取请求审查评论弹出窗口有滚动问题。{% comment %} https://github.com/github/github/pull/141157 {% endcomment %}' - - 'Haproxy 可能会饱和，导致 git 操作减速。{% comment %} https://github.com/github/enterprise2/issues/19322 {% endcomment %}' - - '在 HA 副本升级后不自动启用依赖关系图功能。{% comment %} https://github.com/github/enterprise2/issues/18698 {% endcomment %}' - - '对于有数千个草稿拉取请求的存储库，在版本索引页面上可能会触发超时。{% comment %} https://github.com/github/github/pull/131802 {% endcomment %}' - - '无法同时通过状态和草稿过滤拉取请求。{% comment %} https://github.com/github/github/pull/132567 {% endcomment %}' - - '如果拉取请求更改了子模块指针，然后从拉取请求页面的“已更改的文件”选项卡单击该子模块文件上的“编辑文件”，会导致 404 错误。{% comment %} https://github.com/github/github/pull/132448 {% endcomment %}' - - '在大量删除该组织的所有用户和管理员之后，无法将用户添加到组织或删除组织。{% comment %} https://github.com/github/github/pull/132238 {% endcomment %}' - - '当页面重新加载时，对“已更改的文件”页面上文件名中包含变音符号和非拉丁字符的文件的审核评论将消失。{% comment %} https://github.com/github/github/pull/131836 {% endcomment %}' - - '“已查看”复选框的状态对“已更改的文件”页面上文件名中包含变音符号和非拉丁字符的文件不会保留。{% comment %} https://github.com/github/github/pull/131836 {% endcomment %}' - - '拉取请求所有必需审查尚未完成时显示“已批准”徽章。{% comment %} https://github.com/github/github/pull/131823 {% endcomment %}' - - '当在拥有超过 100 个标签的存储库中搜索标签时，标签下拉菜单为空。{% comment %} https://github.com/github/github/pull/131914 {% endcomment %}' - - '显示带有非 UTF-8 标题注释的拉取请求页面在视图渲染中可能遇到编码错误。{% comment %} https://github.com/github/github/pull/138534 {% endcomment %}' - - '在 OAuth 页面上刷新的竞争条件可能导致重定向执行两次。{% comment %} https://github.com/github/github/pull/131964 {% endcomment %}' - - '如果有超过 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 %}' - - '现在可以禁用在 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 %}' - - '支持分页作为一种通过 REST API 在与提交相关的差异中获取更多文件的方式。{% comment %} https://github.com/github/github/pull/134341 {% endcomment %}' - - '管理员可以在命令行中使用 `ghe-webhook-manage` 启用、禁用、删除 Webhook 或使用 Webhook ID 搜索 Webhook。{% comment %} https://github.com/github/enterprise2/pull/19027 {% endcomment %}' - - '在手动清理合并的拉取请求的头部引用后，将会进行自动基础重新定位。{% comment %} https://github.com/github/github/pull/142133 {% endcomment %}' - - 'SVG 文件在差异查看器中处理为文本和图像。{% comment %} https://github.com/github/render/pull/1129 {% endcomment %}' - - '使用 REST API 创建和更新存储库时，可以设置“合并时自动删除分支”设置。{% comment %} https://github.com/github/github/pull/131728 {% endcomment %}' - - '已添加一个新的终结点来通过 REST API 删除部署。{% comment %} https://github.com/github/github/pull/128733 {% endcomment %}' - - '管理员可以[启用安全警报](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 %}' - - '用户可以使用 `@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 %}' - - '问题侧边栏、问题卡和问题列表中拉取请求和问题引用的[可见性已改进](https://github.blog/2020-02-06-get-more-information-at-a-glance-with-issue-and-pull-request-linking/)。{% comment %} https://github.com/github/releases/issues/704 {% endcomment %}' - - '用户可以通过 `linked:pr` 或 `linked:issue` 过滤和搜索。{% comment %} https://github.com/github/releases/issues/744 {% endcomment %}' - - 'MySQL 现在可在单个区域内自动故障转移以进行群集部署。{% comment %} https://github.com/github/ghes-infrastructure/issues/136 {% endcomment %}' - - '用户可以比较两个版本之间的标签来确定发行版页面上发生了哪些更改。{% comment %} https://github.com/github/github/issues/107054 {% endcomment %}' - - '默认情况下，过时的评论不再在拉取请求时间线上折叠。它们可以通过解析线程来折叠。{% comment %} https://github.com/github/enterprise-web/pull/6389#issuecomment-634201583 {% endcomment %}' - - '管理员可以通过导航到“保留登录”stafftools 选项卡来查看保留供内部使用的登录列表。{% comment %} https://github.com/github/enterprise-web/pull/6389#issuecomment-637846206 {% 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 %}' - - '如果问题包含同一存储库中文件路径长于 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 %}' - - '推送到命令行上的存储库时，不会报告安全警报。（更新时间：2020-06-23）{% comment %} https://github.com/github/github/issues/143190 {% endcomment %}' - - '审核日志可归因于 127.0.0.1，而不是实际源 IP 地址。（更新时间：2020-11-02）{% comment %} https://github.com/github/enterprise2/issues/21514 {% 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-21/1.yml b/translations/zh-CN/data/release-notes/enterprise-server/2-21/1.yml deleted file mode 100644 index 4550bee32a..0000000000 --- a/translations/zh-CN/data/release-notes/enterprise-server/2-21/1.yml +++ /dev/null @@ -1,21 +0,0 @@ -date: '2020-06-23' -sections: - security_fixes: - - '包已更新到最新的安全版本。{% comment %} https://github.com/github/enterprise2/pull/20747, https://github.com/github/enterprise2/pull/20727 {% endcomment %}' - bugs: - - '当使用 UDP 作为传输机制时，过大的日志事件可能导致日志转发不稳定。{% comment %} https://github.com/github/enterprise2/pull/20458, https://github.com/github/enterprise2/pull/20445 {% endcomment %}' - - '用于访问 MySQL 的内部通信服务可能会比预期更频繁地重启，包括在升级过程中，这可能会导致升级部分失败。我们降低了重启率并使代码更加稳健。{% comment %} https://github.com/github/enterprise2/pull/20957, https://github.com/github/enterprise2/pull/20972, https://github.com/github/github/pull/146974 {% endcomment %}' - - "如果 SSH 密钥属性具有已与用户帐户关联的密钥，则用户通过 SSO 进行的自动取消暂停未完成。{% comment %} https://github.com/github/github/pull/143475, https://github.com/github/github/pull/142927 {% endcomment %}" - - '来自 REST API 的存储库权限哈希表示，对于可拉取访问内部存储库的业务成员，无法访问存储库。{% comment %} https://github.com/github/github/pull/144756, https://github.com/github/github/pull/144292 {% endcomment %}' - - '“存储库问题删除”企业帐户策略未反映当前保存的设置。{% comment %} https://github.com/github/github/pull/145218, https://github.com/github/github/pull/145067 {% endcomment %}' - - '审核日志不包括分支保护更改事件。{% comment %} https://github.com/github/github/pull/145998, https://github.com/github/github/pull/145014 {% 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 %}' - - '问题若是包含同一存储库中文件路径长于 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 %}' - - '审核日志可归因于 127.0.0.1，而不是实际源 IP 地址。（更新时间：2020-11-02）{% comment %} https://github.com/github/enterprise2/issues/21514 {% 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-21/10.yml b/translations/zh-CN/data/release-notes/enterprise-server/2-21/10.yml deleted file mode 100644 index 9241ea8b92..0000000000 --- a/translations/zh-CN/data/release-notes/enterprise-server/2-21/10.yml +++ /dev/null @@ -1,15 +0,0 @@ -date: '2020-10-20' -sections: - security_fixes: - - '包已更新到最新的安全版本。{% comment %} https://github.com/github/enterprise2/pull/23096, https://github.com/github/enterprise2/pull/23081 {% endcomment %}' - bugs: - - '企业帐户“确认双因素要求策略”消息不正确。{% comment %} https://github.com/github/github/pull/158736 {% 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 %}' - - '问题若是包含同一存储库中文件路径长于 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 %}' - - '审核日志可归因于 127.0.0.1，而不是实际源 IP 地址。（更新时间：2020-11-02）{% comment %} https://github.com/github/enterprise2/issues/21514 {% 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-21/11.yml b/translations/zh-CN/data/release-notes/enterprise-server/2-21/11.yml deleted file mode 100644 index de748ef8f0..0000000000 --- a/translations/zh-CN/data/release-notes/enterprise-server/2-21/11.yml +++ /dev/null @@ -1,18 +0,0 @@ -date: '2020-11-03' -sections: - security_fixes: - - '**中：**高 CPU 使用可能被特殊构建的 SVN 桥请求触发，导致 SVN 桥服务上的拒绝服务 (DoS)。{% comment %} https://github.com/github/slumlord/pull/1004, https://github.com/github/slumlord/pull/1000 {% endcomment %}' - - "**低：**不正确的令牌验证导致身份验证期间匹配令牌的熵减少。分析表明，在实践中，这里没有重大的安全风险。{% comment %} https://github.com/github/github/pull/159455, https://github.com/github/github/pull/159193 {% endcomment %}" - - '包已更新到最新的安全版本。{% comment %} https://github.com/github/enterprise2/pull/23539, https://github.com/github/enterprise2/pull/23171, https://github.com/github/enterprise2/pull/23692, https://github.com/github/enterprise2/pull/23677 {% endcomment %}' - bugs: - - '使用包含非 ASCII 字符的文件名编辑问题模板将会失败，并显示“500 内部服务器错误”。{% comment %} https://github.com/github/github/pull/160589, https://github.com/github/github/pull/159747 {% endcomment %}' - - '背景作业的指标收集方法提高了 CPU 利用率。（更新时间：2020-11-03）{% comment %} https://github.com/github/github/pull/160109 {% 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 %}' - - '问题若是包含同一存储库中文件路径长于 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 %}' - - '审核日志可归因于 127.0.0.1，而不是实际源 IP 地址。{% comment %} https://github.com/github/enterprise2/issues/21514 {% 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-21/12.yml b/translations/zh-CN/data/release-notes/enterprise-server/2-21/12.yml deleted file mode 100644 index 7f68292a85..0000000000 --- a/translations/zh-CN/data/release-notes/enterprise-server/2-21/12.yml +++ /dev/null @@ -1,16 +0,0 @@ -date: '2020-11-17' -sections: - security_fixes: - - '包已更新到最新的安全版本。{% comment %} https://github.com/github/enterprise2/pull/23844, https://github.com/github/enterprise2/pull/23712 {% endcomment %}' - bugs: - - 'Babeld 日志在秒与微秒之间缺少分隔符。{% comment %} https://github.com/github/babeld/pull/1005, https://github.com/github/babeld/pull/1002 {% endcomment %}' - - '当企业帐户“存储库可见性更改”策略设置为“启用”时，组织所有者无法更改组织内存储库的可见性。{% comment %} https://github.com/github/github/pull/160921, https://github.com/github/github/pull/160773 {% endcomment %}' - - '审核日志可以归因于 127.0.0.1，而不是实际的源 IP 地址。{% comment %} https://github.com/github/github/pull/162436, https://github.com/github/github/pull/161215 {% endcomment %}' - 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 %}' - - '如果问题包含指向同一存储库中文件路径长于 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 %}' - - '当副本节点在高可用性配置中脱机时，{% 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-21/13.yml b/translations/zh-CN/data/release-notes/enterprise-server/2-21/13.yml deleted file mode 100644 index 23bb387e3b..0000000000 --- a/translations/zh-CN/data/release-notes/enterprise-server/2-21/13.yml +++ /dev/null @@ -1,19 +0,0 @@ -date: '2020-12-03' -sections: - bugs: - - '由于 bootstrap 中的争用条件导致服务重启，授权服务被检测为运行不正常。{% comment %} https://github.com/github/authzd/pull/1278 {% endcomment %}' - - '在热补丁升级过程中，一种潜在的行为导致服务不可用。{% comment %} https://github.com/github/enterprise2/pull/24054, https://github.com/github/enterprise2/issues/23947 {% endcomment %}' - - '未正确应用日志转发 SSL 证书的子集。{% comment %} https://github.com/github/enterprise2/pull/24113, https://github.com/github/enterprise2/pull/23981 {% endcomment %}' - - '发送电子邮件通知给已经从团队或组织中移除的已停用用户。{% comment %} https://github.com/github/github/pull/162971, https://github.com/github/github/pull/162742 {% endcomment %}' - - '组织和企业之间应用 SSH 证书的方式不一致。{% comment %} https://github.com/github/github/pull/163426, https://github.com/github/github/pull/159538, https://github.com/github/authentication/issues/115 {% endcomment %}' - - '当帐户因使用不正确的密码而受到速率限制时，可能被锁定长达 24 小时。{% comment %} https://github.com/github/github/pull/163436, https://github.com/github/github/pull/162938, https://github.com/github/github-ds/pull/51 {% endcomment %}' - - '在具有许多引用的存储库上进行拉取请求同步可能导致工作进程队列落后。{% comment %} https://github.com/github/github/pull/163575, https://github.com/github/github/pull/163142 {% endcomment %}' - - '在尝试访问特定页面后登录时，用户被发送到主页，而不是其预期目的地。{% comment %} https://github.com/github/github/pull/163784, https://github.com/github/github/pull/163579, https://github.com/github/github/pull/154117, https://github.com/github/ecosystem-apps/issues/1076 {% 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 %}' - - '问题若是包含同一存储库中文件路径长于 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 %}' - - '当副本节点在高可用性配置下离线时，{% 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-21/14.yml b/translations/zh-CN/data/release-notes/enterprise-server/2-21/14.yml deleted file mode 100644 index aaf7e30402..0000000000 --- a/translations/zh-CN/data/release-notes/enterprise-server/2-21/14.yml +++ /dev/null @@ -1,13 +0,0 @@ -date: '2020-12-17' -sections: - security_fixes: - - '**低：**高 CPU 使用可能被特殊构建的 SVN 桥请求触发，导致 SVN 桥服务上的拒绝服务 (DoS)。{% comment %} https://github.com/github/slumlord/pull/1021, https://github.com/github/slumlord/pull/1017 {% endcomment %}' - - '包已更新到最新的安全版本。{% comment %} https://github.com/github/enterprise2/pull/24352, https://github.com/github/enterprise2/pull/23866 {% endcomment %}' - 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 %}' - - '如果问题包含指向同一存储库中文件路径长于 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 %}' - - '当副本节点在高可用性配置中脱机时，{% 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-21/15.yml b/translations/zh-CN/data/release-notes/enterprise-server/2-21/15.yml deleted file mode 100644 index 20bd0c49a7..0000000000 --- a/translations/zh-CN/data/release-notes/enterprise-server/2-21/15.yml +++ /dev/null @@ -1,33 +0,0 @@ -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 Pages 生成的 GitHub 令牌最终可能会出现在日志中。' - - '**低：**对 SVN 桥的专门制定请求可能会在失败前触发长时间的等待，从而导致拒绝服务 (DoS)。' - - '包已更新到最新的安全版本。' - bugs: - - '在某些情况下，负载均衡器运行状况检查可能导致 babld 日志全是有关代理协议的错误。' - - '在 GitHub Enterprise 备份实用程序快照期间，信息性消息被无意中记录为错误，这导致侦听输出到 stderr 的 cron 作业在安排备份时发送不必要的电子邮件。' - - '在还原大型备份时，与 Redis 内存耗尽相关的异常记录可能导致还原因磁盘已满而失败。' - - '用户在编辑 wiki 页面时，如果单击“保存”按钮，可能会遇到 500 错误。' - - '使用主题替代名称中具有多个名称的证书签名的 S/MIME 签名提交将在提交提示标记中错误地显示为“未验证”。' - - '已暂停的用户在添加到团队时会收到电子邮件。' - - '当存储库具有大量清单时，“见解 ->依赖项关系图”选项卡上会显示错误“已达到此存储库允许的最大清单文件数 (20)”。有关详细信息，请参阅[可视化效果限制](https://docs.github.com/en/github/managing-security-vulnerabilities/troubleshooting-the-detection-of-vulnerable-dependencies#are-there-limits-which-affect-the-dependency-graph-data)。' - - '上传与之前许可证文件不同席位数的新许可证文件时，企业帐户的“设置”->“许可证”页面中不会正确表示席位差异。' - - '无法成功启用或禁用企业帐户设置中的“禁止存储库管理员更改匿名 Git 读取访问权限”复选框。' - - 'GitHub Pages 生成失败时，电子邮件通知包含了错误的支持位置链接。' - - '在闰年，用户在星期一尝试查看贡献活动时收到 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/)的支持。' - - '调整后台队列优先级，以更均匀地分配作业。' - known_issues: - - '在新建的没有任何用户的 GitHub Enterprise Server 上，攻击者可以创建第一个管理员用户。' - - '在升级期间不会维护自定义防火墙规则。' - - '[通过 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-21/16.yml b/translations/zh-CN/data/release-notes/enterprise-server/2-21/16.yml deleted file mode 100644 index a9364810d0..0000000000 --- a/translations/zh-CN/data/release-notes/enterprise-server/2-21/16.yml +++ /dev/null @@ -1,14 +0,0 @@ -date: '2021-03-16' -sections: - security_fixes: - - 包已更新到最新的安全版本。 - bugs: - - 从 GitHub Enterprise Server 中导入正在丢失存储库文件的存储库存档将失败并报告错误。 - known_issues: - - 在没有任何用户的新设置的 GitHub Enterprise Server 上，攻击者可以创建第一个管理员用户。 - - 在升级期间不会维护自定义防火墙规则。 - - "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-21/17.yml b/translations/zh-CN/data/release-notes/enterprise-server/2-21/17.yml deleted file mode 100644 index 9c2b33be60..0000000000 --- a/translations/zh-CN/data/release-notes/enterprise-server/2-21/17.yml +++ /dev/null @@ -1,27 +0,0 @@ -date: '2021-03-23' -intro: Downloads have been disabled due to a major bug affecting multiple customers. A fix will be available in the next patch. -sections: - security_fixes: - - '**HIGH:** A remote code execution vulnerability was identified in GitHub Enterprise Server that could be exploited when building a GitHub Pages site. User-controlled configuration options used by GitHub Pages were not sufficiently restricted and made it possible to override environment variables leading to code execution on the GitHub Enterprise Server instance. To exploit this vulnerability, an attacker would need permission to create and build a GitHub Pages site on the GitHub Enterprise Server instance. This vulnerability affected all versions of GitHub Enterprise Server prior to 3.0.3 and was fixed in 3.0.3, 2.22.9, and 2.21.17. This vulnerability was reported via the GitHub Bug Bounty program and has been assigned CVE-2021-22864.' - - Packages have been updated to the latest security versions. - bugs: - - The `ghe-cluster-config-init` run was not fully accounting for the exit code of background jobs leading to improper handling of preflight checks. - changes: - - Logs will rotate based on size in addition to time. - - Use a relative number for consul and nomad `bootstrap_expect` allowing for a cluster to bootstrap even if a handful of nodes are down. - known_issues: - - On a freshly set up GitHub Enterprise 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. - - Security alerts are not reported when pushing to a repository on the command line. - - | - Log rotation may fail to signal services to transition to new log files, leading to older log files continuing to be used, and eventual root disk space exhaustion. - To remedy and/or prevent this issue, run the following commands in the [administrative shell](https://docs.github.com/en/enterprise-server/admin/configuration/accessing-the-administrative-shell-ssh) (SSH), or contact [GitHub Enterprise Support](https://support.github.com/contact) for assistance: - - ``` - printf "PATH=/usr/local/sbin:/usr/local/bin:/usr/local/share/enterprise:/usr/sbin:/usr/bin:/sbin:/bin\n29,59 * * * * root /usr/sbin/logrotate /etc/logrotate.conf\n" | sudo sponge /etc/cron.d/logrotate - sudo /usr/sbin/logrotate -f /etc/logrotate.conf - ``` - - 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. 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 deleted file mode 100644 index b6e86259eb..0000000000 --- a/translations/zh-CN/data/release-notes/enterprise-server/2-21/18.yml +++ /dev/null @@ -1,16 +0,0 @@ -date: '2021-04-01' -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/) 进行报告。" - - 包已更新到最新的安全版本。 - bugs: - - 服务未作为日志轮换的一部分转换到新的日志文件，导致磁盘使用量增加。 - - 内部存储库搜索结果上的标签显示为“专用”而不是“内部”。 - known_issues: - - 在没有任何用户的新设置的 GitHub Enterprise Server 上，攻击者可以创建第一个管理员用户。 - - 在升级期间不会维护自定义防火墙规则。 - - "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-21/19.yml b/translations/zh-CN/data/release-notes/enterprise-server/2-21/19.yml deleted file mode 100644 index d9ccb888bb..0000000000 --- a/translations/zh-CN/data/release-notes/enterprise-server/2-21/19.yml +++ /dev/null @@ -1,18 +0,0 @@ -date: '2021-04-14' -sections: - security_fixes: - - 包已更新到最新的安全版本。 - bugs: - - '在副本升级期间可能会出现警告消息 `jq: error (at :0): Cannot index number with string "settings"`。' - - 访问 `/settings/email` 页面会存储在退出登录并重新登录时可能导致错误重定向的状态。 - - 对于其通告在 `vulnerable_version_ranges` 中具有大写包名称的一些组件，未显示依赖项关系图警报。 - - 用户在配置了 LDAP 身份验证的实例上执行 git 操作时会看到 500 错误。 - - 当 ghe-migrator 遇到导入错误时，它有时会中止整个进程，但日志中没有包含足够的上下文。 - known_issues: - - 在没有任何用户的新建 GitHub Enterprise Server 上，攻击者可以创建第一个管理员用户。 - - 在升级期间不会维护自定义防火墙规则。 - - "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-21/2.yml b/translations/zh-CN/data/release-notes/enterprise-server/2-21/2.yml deleted file mode 100644 index f3d8d4e493..0000000000 --- a/translations/zh-CN/data/release-notes/enterprise-server/2-21/2.yml +++ /dev/null @@ -1,21 +0,0 @@ -date: '2020-07-09' -sections: - security_fixes: - - '**中：** 将 nginx 更新到 1.16.1 并解决了 CVE-2019-20372。（更新于 2020-07-22）{% comment %} https://github.com/github/enterprise2/pull/21252 {% endcomment %}' - - '包已更新到最新的安全版本。{% comment %} https://github.com/github/enterprise2/pull/21089, https://github.com/github/enterprise2/pull/21036 {% endcomment %}' - bugs: - - '一些特定日志文件不会每 7 天轮换一次。{% comment %} https://github.com/github/enterprise2/pull/21279, https://github.com/github/enterprise2/pull/21264 {% endcomment %}' - - '快速重新使用 webhook 源端口导致拒绝连接。{% comment %} https://github.com/github/enterprise2/pull/21286, https://github.com/github/enterprise2/pull/21280 {% endcomment %}' - - '不正确的背景作业可能尝试在配置为被动副本的实例上运行。{% comment %} https://github.com/github/enterprise2/pull/21317, https://github.com/github/enterprise2/pull/21212, https://github.com/github/enterprise2/issues/21167 {% endcomment %}' - - '节点之间的 VPN 可能会变得不稳定，导致记录错误并且可用的根卷空间被耗尽。{% comment %} https://github.com/github/enterprise2/pull/21360, https://github.com/github/enterprise2/pull/21357 {% endcomment %}' - - '内部仓库未正确包含在启用 SAML 的组织的搜索结果中。{% comment %} https://github.com/github/github/pull/147505, https://github.com/github/github/pull/145692 {% endcomment %}' - 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 %}' - - '如果问题包含指向同一存储库中文件路径长于 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 %}' - - '审核日志可归因于 127.0.0.1，而不是实际源 IP 地址。（更新时间：2020-11-02）{% comment %} https://github.com/github/enterprise2/issues/21514 {% 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-21/20.yml b/translations/zh-CN/data/release-notes/enterprise-server/2-21/20.yml deleted file mode 100644 index 35cf37ce02..0000000000 --- a/translations/zh-CN/data/release-notes/enterprise-server/2-21/20.yml +++ /dev/null @@ -1,19 +0,0 @@ -date: '2021-04-28' -sections: - security_fixes: - - 包已更新到最新的安全版本。 - bugs: - - 在 MySQL 副本上运行的安装脚本可能导致数据库故障转移期间不必要的数据库重新播种。 - - '由于不必要地调用 `rake db:migrate`，`config-apply` 可能需要更长的时间。' - - Orchestrator 可能已故障转移到 MySQL 副本，当主数据库无法连接时，它无法在播种阶段从主数据库复制。 - - 出现错误的组织或项目阻止了迁移，无法排除。 - changes: - - 默认情况下，预检检查允许所有 AWS 实例类型。 - known_issues: - - 在新建的没有任何用户的 GitHub Enterprise Server 上，攻击者可以创建第一个管理员用户。 - - 在升级期间不会维护自定义防火墙规则。 - - "[通过 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-21/21.yml b/translations/zh-CN/data/release-notes/enterprise-server/2-21/21.yml deleted file mode 100644 index 6f3f8092e2..0000000000 --- a/translations/zh-CN/data/release-notes/enterprise-server/2-21/21.yml +++ /dev/null @@ -1,15 +0,0 @@ -date: '2021-05-13' -sections: - security_fixes: - - 包已更新到最新的安全版本。 - bugs: - - 在配置应用阶段可以启用 Orchestrator 自动故障转移。 - - 具有存储库维护员权限的用户会收到电子邮件验证警告，而不是在存储库 Pages 设置页面上构建成功的页面。 - known_issues: - - 在新建的没有任何用户的 GitHub Enterprise Server 上，攻击者可以创建第一个管理员用户。 - - 在升级期间不会维护自定义防火墙规则。 - - "[通过 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-21/22.yml b/translations/zh-CN/data/release-notes/enterprise-server/2-21/22.yml deleted file mode 100644 index fd1d867027..0000000000 --- a/translations/zh-CN/data/release-notes/enterprise-server/2-21/22.yml +++ /dev/null @@ -1,16 +0,0 @@ -date: '2021-05-25' -sections: - security_fixes: - - '**中：**在某些情况下，从团队或组织中删除的用户可以保留对已打开现有拉取请求的分支的写入权限。' - - 包已更新到最新的安全版本。 - bugs: - - 管理员使用“创建白名单条目”按钮添加的 IP 地址仍可能被锁定。 - - 在群集或 HA 环境中，GitHub Pages 构建可能在将会失败的次要节点上触发。 - known_issues: - - 在新建的没有任何用户的 GitHub Enterprise Server 上，攻击者可能创建第一个管理员用户。 - - 在升级期间不会维护自定义防火墙规则。 - - "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-21/23.yml b/translations/zh-CN/data/release-notes/enterprise-server/2-21/23.yml deleted file mode 100644 index 175ffb0c6a..0000000000 --- a/translations/zh-CN/data/release-notes/enterprise-server/2-21/23.yml +++ /dev/null @@ -1,16 +0,0 @@ -date: '2021-06-10' -sections: - security_fixes: - - 包已更新到最新的安全版本。 - bugs: - - "从 非 GitHub 源导入组织或仓库失败可能会产生 `undefined method '[]' for nil:NilClass` 错误。" - changes: - - GraphQL API 用户可在 `PullRequest` 对象上查询公共字段 `closingIssuesReferences`。该字段检索将在合并拉取请求时自动关闭的问题。这种方法还将允许将来迁移这些数据，作为更高保真度迁移过程的一部分。 - known_issues: - - 在新建的没有任何用户的 GitHub Enterprise Server 上，攻击者可以创建第一个管理员用户。 - - 自定义防火墙规则在升级过程中被删除。 - - "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-21/3.yml b/translations/zh-CN/data/release-notes/enterprise-server/2-21/3.yml deleted file mode 100644 index 61e9cc25c1..0000000000 --- a/translations/zh-CN/data/release-notes/enterprise-server/2-21/3.yml +++ /dev/null @@ -1,18 +0,0 @@ -date: '2020-07-21' -sections: - security_fixes: - - '包已更新到最新的安全版本。{% comment %} https://github.com/github/enterprise2/pull/21438, https://github.com/github/enterprise2/pull/21402, https://github.com/github/enterprise2/pull/21496, https://github.com/github/enterprise2/pull/21479 {% endcomment %}' - bugs: - - '管理控制台监视图有时无法在更大的屏幕上正确显示。{% comment %} https://github.com/github/enterprise2/pull/21398, https://github.com/github/enterprise2/pull/21381 {% endcomment %}' - - '应用 SameSite Cookie 策略时，GitHub 应用部件清单 (manifest) 创建流在某些情况下无法使用。{% comment %} https://github.com/github/github/pull/147829, https://github.com/github/github/pull/144121 {% endcomment %}' - - "在某些情况下，访问“探索”页面会引发应用程序错误。{% comment %} https://github.com/github/github/pull/149605, https://github.com/github/github/pull/148949 {% 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 %}' - - '问题若是包含同一存储库中文件路径长于 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 %}' - - '审核日志可归因于 127.0.0.1，而不是实际源 IP 地址。（更新时间：2020-11-02）{% comment %} https://github.com/github/enterprise2/issues/21514 {% 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-21/4.yml b/translations/zh-CN/data/release-notes/enterprise-server/2-21/4.yml deleted file mode 100644 index fe8a7af32a..0000000000 --- a/translations/zh-CN/data/release-notes/enterprise-server/2-21/4.yml +++ /dev/null @@ -1,28 +0,0 @@ -date: '2020-08-11' -sections: - security_fixes: - - '{% octicon "alert" aria-label="The alert icon" %} **关键：**在 GitHub Pages 中发现了一个远程执行代码漏洞，攻击者可利用该漏洞在构建 GitHub Pages 站点的过程中执行命令。此问题是由于在 Pages 构建过程中使用过时且易受攻击的依赖项造成的。要利用此漏洞，攻击者需要获得在 GitHub Enterprise Server 实例上创建和构建 GitHub Pages 站点的权限。 此漏洞影响 GitHub Enterprise Server 的所有版本。为了缓解此漏洞，Kramdown 已更新以解决 CVE-2020-14001。{% comment %} https://github.com/github/pages/pull/2835, https://github.com/github/pages/pull/2827 {% endcomment %}' - - '**高：**在 GitHub Enterprise Server 上执行时，攻击者可以将恶意参数注入 Git 子命令。这可能使攻击者能够使用部分用户控制的内容覆盖任意文件，并可能在 GitHub Enterprise Server 实例上执行任意命令。要利用此漏洞，攻击者需要获得访问 GHES 实例中存储库的权限。但是，由于存在其他保护措施，我们无法确定积极利用此漏洞的方法。此漏洞通过 GitHub 安全 Bug 悬赏计划报告。{% comment %} https://github.com/github/github/pull/150936, https://github.com/github/github/pull/150634 {% endcomment %}' - - '包已更新到最新的安全版本。{% comment %} https://github.com/github/enterprise2/pull/21679, https://github.com/github/enterprise2/pull/21542, https://github.com/github/enterprise2/pull/21812, https://github.com/github/enterprise2/pull/21700 {% endcomment %}' - bugs: - - 'Consul 配置错误导致无法在独立实例上处理某些后台作业。{% comment %} https://github.com/github/enterprise2/pull/21463 {% endcomment %}' - - '服务内存分配计算可能会将不正确或无限制的内存分配给某项服务，导致系统性能差。{% comment %} https://github.com/github/enterprise2/pull/21689 {% endcomment %}' - - '未正确检测到 oVirt KVM 系统的虚拟化平台，从而在升级过程中造成问题。{% comment %} https://github.com/github/enterprise2/pull/21731, https://github.com/github/enterprise2/pull/21669 {% endcomment %}' - - "通过 Git 命令行使用密码进行无效身份验证的错误消息未填充 URL 链接以添加适当的令牌或 SSH 密钥。{% comment %} https://github.com/github/github/pull/149607, https://github.com/github/github/pull/149351 {% endcomment %}" - - '使用问题模板功能在用户存储库上创建问题可能失败，并出现内部服务器错误。{% comment %} https://github.com/github/github/pull/150173, https://github.com/github/github/pull/149445 {% endcomment %}' - - '访问“探索”部分失败，出现 500 内部服务器错误。{% comment %} https://github.com/github/github/pull/150512, https://github.com/github/github/pull/150504 {% endcomment %}' - - '在迁移到新实例的存储库上，无法按 *最近更新* 对问题进行排序。{% comment %} https://github.com/github/github/pull/150688, https://github.com/github/github/pull/149330 {% endcomment %}' - - 'GitHub Connect 使用的是已弃用的 GitHub.com API 终结点。{% comment %} https://github.com/github/github/pull/150827, https://github.com/github/github/pull/150545 {% endcomment %}' - - '为后台作业收集的内部指标导致不必要的 CPU 和内存使用。{% comment %} https://github.com/github/github/pull/151182, https://github.com/github/github/pull/147695 {% endcomment %}' - - '404 页面的页脚中包含 GitHub.com 联系人和状态链接。{% comment %} https://github.com/github/github/pull/151315 {% endcomment %}' - - '未发布功能的后台作业已排队，尚未处理。{% comment %} https://github.com/github/github/pull/151395, https://github.com/github/github/pull/146248 {% 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 %}' - - '问题若是包含同一存储库中文件路径长于 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 %}' - - '审核日志可归因于 127.0.0.1，而不是实际源 IP 地址。（更新时间：2020-11-02）{% comment %} https://github.com/github/enterprise2/issues/21514 {% 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-21/5.yml b/translations/zh-CN/data/release-notes/enterprise-server/2-21/5.yml deleted file mode 100644 index f80dee5edb..0000000000 --- a/translations/zh-CN/data/release-notes/enterprise-server/2-21/5.yml +++ /dev/null @@ -1,16 +0,0 @@ -date: '2020-08-12' -sections: - bugs: - - '解决了在生成系统配置模板时可能导致高 CPU 使用率的问题。{% comment %} https://github.com/github/enterprise2/pull/21786， https://github.com/github/enterprise2/pull/21741 {% endcomment %}' - - '最近对内存分配的更改可能导致系统性能降低 {% comment %} https://github.com/github/enterprise2/pull/22066 {% endcomment %}' - - '运行数据库迁移时的临时连接问题可能导致数据丢失。{% comment %} https://github.com/github/enterprise2/pull/22128, https://github.com/github/enterprise2/pull/22100 {% endcomment %}' - 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 %}' - - '如果问题包含同一存储库中文件路径长于 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 %}' - - '审核日志可归于 127.0.0.1，而不是实际源 IP 地址。（更新时间：2020-11-02）{% comment %} https://github.com/github/enterprise2/issues/21514 {% 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-21/6.yml b/translations/zh-CN/data/release-notes/enterprise-server/2-21/6.yml deleted file mode 100644 index c9ef772868..0000000000 --- a/translations/zh-CN/data/release-notes/enterprise-server/2-21/6.yml +++ /dev/null @@ -1,28 +0,0 @@ -date: '2020-08-26' -sections: - security_fixes: - - >- - {% octicon "alert" aria-label="The alert icon" %} **Critical:** A remote code execution vulnerability was identified in GitHub Pages that could be exploited when building a GitHub Pages site. User-controlled configuration of the underlying parsers used by GitHub Pages were not sufficiently restricted and made it possible to execute commands on the GitHub Enterprise Server instance. To exploit this vulnerability, an attacker would need permission to create and build a GitHub Pages site on the GitHub Enterprise Server instance. This vulnerability affected all versions of GitHub Enterprise Server. The underlying issues contributing to this vulnerability were identified both internally and through the GitHub Security Bug Bounty program. We have issued CVE-2020-10518. {% comment %} https://github.com/github/pages/pull/2882, https://github.com/github/pages/pull/2902, https://github.com/github/pages/pull/2894, https://github.com/github/pages/pull/2877, https://github.com/github/pages-gem/pull/700, - https://github.com/github/pages/pull/2889, https://github.com/github/pages/pull/2899, https://github.com/github/pages/pull/2903, https://github.com/github/pages/pull/2890, https://github.com/github/pages/pull/2891, https://github.com/github/pages/pull/2884 {% endcomment %} - - '**Medium:** An improper access control vulnerability was identified that allowed authenticated users of the instance to determine the names of unauthorized private repositories given their numerical IDs. This vulnerability did not allow unauthorized access to any repository content besides the name. This vulnerability affected all versions of GitHub Enterprise Server prior to 2.22 and has been assigned [CVE-2020-10517](https://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2020-10517). The vulnerability was reported via the [GitHub Bug Bounty program](https://bounty.github.com). {% comment %} https://github.com/github/github/pull/151986, https://github.com/github/github/pull/151713 {% endcomment %}' - - 'Packages have been updated to the latest security versions. {% comment %} https://github.com/github/enterprise2/pull/21853, https://github.com/github/enterprise2/pull/21828, https://github.com/github/enterprise2/pull/22154, https://github.com/github/enterprise2/pull/21920, https://github.com/github/enterprise2/pull/22216, https://github.com/github/enterprise2/pull/22190 {% endcomment %}' - bugs: - - 'A message was not logged when the ghe-config-apply process had finished running ghe-es-auto-expand. {% comment %} https://github.com/github/enterprise2/pull/22178, https://github.com/github/enterprise2/pull/22171 {% endcomment %}' - - 'Excessive logging to the `syslog` file could occur on high-availability replicas if the primary appliance is unavailable. {% comment %} https://github.com/github/enterprise2/pull/22268, https://github.com/github/enterprise2/pull/22124 {% endcomment %}' - - "Database re-seeding on a replica could fail with an error: `Got packet bigger than 'max_allowed_packet'` {% comment %} https://github.com/github/enterprise2/pull/22322, https://github.com/github/enterprise2/pull/20063 {% endcomment %}" - - 'In some cases duplicate user data could cause a 500 error while running the ghe-license-usage script. {% comment %} https://github.com/github/github/pull/152637 {% endcomment %}' - - 'Using `ghe-migrator`, the `add` command would fail to lock a repository when using the `--lock` flag. {% comment %} https://github.com/github/github/pull/152780, https://github.com/github/github/pull/152588 {% endcomment %}' - changes: - - 'In a high availability or geo-replication configuration, replica instances would exit maintenance mode when ghe-config-apply ran. {% comment %} https://github.com/github/enterprise2/pull/21777, https://github.com/github/enterprise2/pull/21440 {% endcomment %}' - - "We've added support for the R5a and R5n AWS instance types. {% comment %} https://github.com/github/enterprise2/pull/21903, https://github.com/github/enterprise2/pull/21173 {% endcomment %}" - - 'Removed the license seat count information on the administrative SSH MOTD due to a performance issue impacting GitHub Enterprise Server clusters. {% comment %} https://github.com/github/enterprise2/pull/21994, https://github.com/github/enterprise2/pull/21870 {% endcomment %}' - known_issues: - - 'On a freshly set up GitHub Enterprise Server without any users, an attacker could create the first admin user. {% comment %} https://github.com/github/enterprise2/issues/1889 {% endcomment %}' - - 'Custom firewall rules are not maintained during an upgrade. {% comment %} https://github.com/github/enterprise2/issues/2823 {% endcomment %}' - - '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. {% comment %} https://github.com/github/github/issues/54684 {% endcomment %}' - - '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. {% comment %} https://github.com/github/github/issues/107731 {% endcomment %}' - - '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. {% comment %} https://github.com/github/admin-experience/issues/571 {% endcomment %}' - - 'Security alerts are not reported when pushing to a repository on the command line. {% comment %} https://github.com/github/github/issues/143190 {% endcomment %}' - - 'Audit logs may be attributed to 127.0.0.1 instead of the actual source IP address. (updated 2020-11-02) {% comment %} https://github.com/github/enterprise2/issues/21514 {% endcomment %}' - - "Configuring a repository's permission to `Triage` or `Maintain` fails with an error message." - - '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.' 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 deleted file mode 100644 index b3467f5f1c..0000000000 --- a/translations/zh-CN/data/release-notes/enterprise-server/2-21/7.yml +++ /dev/null @@ -1,15 +0,0 @@ -date: '2020-09-08' -sections: - bugs: - - '服务运行状况检查会造成会话增加，从而耗尽文件系统 Inode。{% comment %} https://github.com/github/enterprise2/pull/22481, https://github.com/github/enterprise2/pull/22475 {% endcomment %}' - - "使用热补丁的升级可能会失败，并显示错误：“未找到 'libdbi1'”{% comment %} https://github.com/github/enterprise2/pull/22556, https://github.com/github/enterprise2/pull/22552 {% 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 %}' - - '问题若是包含同一存储库中文件路径长于 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 %}' - - '审核日志可归因于 127.0.0.1，而不是实际源 IP 地址。（更新时间：2020-11-02）{% comment %} https://github.com/github/enterprise2/issues/21514 {% 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-21/8.yml b/translations/zh-CN/data/release-notes/enterprise-server/2-21/8.yml deleted file mode 100644 index 2834cac6c7..0000000000 --- a/translations/zh-CN/data/release-notes/enterprise-server/2-21/8.yml +++ /dev/null @@ -1,16 +0,0 @@ -date: '2020-09-23' -sections: - security_fixes: - - '**中**：ImageMagick 已经更新，可解决 [DSA-4715-1](https://www.debian.org/security/2020/dsa-4715). {% comment %} https://github.com/github/enterprise2/pull/22621, https://github.com/github/enterprise2/pull/22610 {% endcomment %}' - - '包已更新到最新的安全版本。{% comment %} https://github.com/github/enterprise2/pull/22571, https://github.com/github/enterprise2/pull/22426, https://github.com/github/enterprise2/pull/22602, https://github.com/github/enterprise2/pull/22592, https://github.com/github/enterprise2/pull/22719, https://github.com/github/enterprise2/pull/22699 {% endcomment %}' - bugs: - - '管理员无法看到已交付的存储库 Webhook，而是看到“抱歉，出错了，我们无法提取此挂钩的交付”。{% comment %} https://github.com/github/authzd/pull/1181, https://github.com/github/authzd/pull/980 {% 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 %}' - - '问题若是包含同一存储库中文件路径长于 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 %}' - - '审核日志可归因于 127.0.0.1，而不是实际源 IP 地址。（更新时间：2020-11-02）{% comment %} https://github.com/github/enterprise2/issues/21514 {% 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-21/9.yml b/translations/zh-CN/data/release-notes/enterprise-server/2-21/9.yml deleted file mode 100644 index f0aefac3b8..0000000000 --- a/translations/zh-CN/data/release-notes/enterprise-server/2-21/9.yml +++ /dev/null @@ -1,29 +0,0 @@ -date: '2020-10-09' -sections: - security_fixes: - - '**LDAP** 目录用户名标准化为现有 GHES 帐户登录的用户可以验证现有帐户。{% comment %} https://github.com/github/github/pull/156517， https://github.com/github/github/pull/155512 {% endcomment %}' - - '包已更新到最新的安全版本。{% comment %} https://github.com/github/enterprise2/pull/22911, https://github.com/github/enterprise2/pull/22878 {% endcomment %}' - bugs: - - '管理控制台中的 NameID 格式下拉列表将在设置为“持久”之后重置为“未指定”。 {% comment %} https://github.com/github/enterprise2/pull/22402， https://github.com/github/enterprise2/pull/22331， https://github.com/github/enterprise2/issues/13446 {% endcomment %}' - - '通过[管理控制台](/admin/configuration/accessing-the-management-console) 保存设置将附加一个新行到 [TLS/SSL 证书和密钥](/admin/configuration/configuring-tls) 文件，这触发了某些服务的不必要重新加载。 {% comment %} https://github.com/github/enterprise2/pull/22608, https://github.com/github/enterprise2/pull/22540 {% endcomment %}' - - '依赖项关系图的系统日志没有轮换，允许无限存储增长。{% comment %} https://github.com/github/enterprise2/pull/22766， https://github.com/github/enterprise2/pull/22733 {% endcomment %}' - - '如果请求的工人覆盖设置在使用中，升级可能会失败。{% comment %} https://github.com/github/enterprise2/pull/22838, https://github.com/github/enterprise2/pull/22814 {% endcomment %}' - - '使用 `ghe-migrator` 导入仓库时，如果数据不一致，可能发生意外异常。{% comment %} https://github.com/github/github/pull/153849, https://github.com/github/github/pull/151552 {% endcomment %}' - - '到 GitHub 安全通告的链接将使用 GitHub Enterprise Server 实例主机名的 URL 而不是 GitHub.com，将用户引导到不存在的 URL。{% comment %} https://github.com/github/github/pull/153853, https://github.com/github/github/pull/151301 {% endcomment %}' - - '当使用的身份验证模式不支持内置双重身份验证时，企业帐户安全设置页面显示用于“双重身份验证”设置的“查看组织当前配置”链接。{% comment %} https://github.com/github/github/pull/153861 {% endcomment %}' - - '当使用 `ghe-migrator` 导入 PR 审核请求时，与删除用户相关的记录将产生外部数据库记录。 {% comment %} https://github.com/github/github/pull/154959, https://github.com/github/github/pull/153169 {% endcomment %}' - - '使用 "ghe-migrator" 导入用户时，如果系统生成的电子邮件地址超过 100 个字符，则会出现“电子邮件无效”的错误。{% comment %} https://github.com/github/github/pull/155110, https://github.com/github/github/pull/152418 {% endcomment %}' - - '记录 web 挂钩活动可能会使用大量的磁盘空间，并导致根盘变满。{% comment %} https://github.com/github/github/pull/155656, https://github.com/github/github/pull/154100 {% endcomment %}' - changes: - - '为 AWS EC2 实例类型 `m5.16xlarge` 添加了支持。{% comment %} https://github.com/github/enterprise2/pull/22501, https://github.com/github/enterprise2/pull/22473 {% endcomment %}' - - '删除 `ghe-migrator` 档案中 SSH 指纹的要求，因为它可以随时计算。{% comment %} https://github.com/github/github/pull/156945, https://github.com/github/github/pull/155387 {% endcomment %}' - - 'GitHub App 清单现在包含 `request_oauth_on_install` 字段。{% comment %} https://github.com/github/github/pull/156994, https://github.com/github/github/pull/155010, https://github.com/github/ecosystem-apps/issues/1055 {% endcomment %}' - 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 %}' - - '议题若是包含同一仓库中文件路径长于 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 %}' - - '审核日志可归因于 127.0.0.1，而不是实际源 IP 地址。（更新于 2020-11-02） {% comment %} https://github.com/github/enterprise2/issues/21514 {% 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/0.yml b/translations/zh-CN/data/release-notes/enterprise-server/2-22/0.yml deleted file mode 100644 index 8525a93483..0000000000 --- a/translations/zh-CN/data/release-notes/enterprise-server/2-22/0.yml +++ /dev/null @@ -1,143 +0,0 @@ -intro: GitHub is excited to present GitHub Enterprise Server 2.22.0. -date: '2020-09-23' -sections: - features: - - heading: GitHub Actions Beta - notes: - - | - [GitHub Actions](https://github.com/features/actions) is a powerful, flexible solution for CI/CD and workflow automation. GitHub Actions on Enterprise Server includes tools to help you manage the service, including key metrics in the Management Console, audit logs and access controls to help you control the roll out. - - You will need to provide your own [storage](https://docs.github.com/en/enterprise/2.22/admin/github-actions/enabling-github-actions-and-configuring-storage) and runners for GitHub Actions. AWS S3, Azure Blob Storage and MinIO are supported. Please review the [updated minimum requirements for your platform](https://docs.github.com/en/enterprise/2.22/admin/installation/setting-up-a-github-enterprise-server-instance) before you turn on GitHub Actions. To learn more, contact the GitHub Sales team or [sign up for the beta](https://resources.github.com/beta-signup/). {% comment %} https://github.com/github/releases/issues/775 {% endcomment %} - - - heading: GitHub Packages Beta - notes: - - | - [GitHub Packages](https://github.com/features/packages) is a package hosting service, natively integrated with GitHub APIs, Actions, and webhooks. Create an [end-to-end DevOps workflow](https://docs.github.com/en/enterprise/2.22/admin/packages/configuring-packages-support-for-your-enterprise) that includes your code, continuous integration, and deployment solutions. - - Supported storage back ends include AWS S3 and MinIO with support for Azure blob coming in a future release. Please note that the current Docker support will be replaced by a beta of the new GitHub Container Registry in the next release. Please review the [updated minimum requirements for your platform](https://docs.github.com/en/enterprise/2.22/admin/installation/setting-up-a-github-enterprise-server-instance) before you turn on GitHub Packages. To learn more, contact the GitHub Sales team or [sign up for the beta](https://resources.github.com/beta-signup/). {% comment %} https://github.com/github/releases/issues/773 {% endcomment %} - - - heading: Advanced Security Code Scanning Beta - notes: - - | - [GitHub Advanced Security code scanning](https://github.com/features/security) is a developer-first, GitHub-native static application security testing (SAST). Easily find security vulnerabilities before they reach production, all powered by the world’s most powerful code analysis engine: CodeQL. - - Administrators using GitHub Advanced Security can [sign up for](https://resources.github.com/beta-signup/) and [enable](https://docs.github.com/en/enterprise/2.22/admin/configuration/configuring-code-scanning-for-your-appliance) GitHub Advanced Security code scanning beta. Please review the [updated minimum requirements for your platform](https://docs.github.com/en/enterprise/2.22/admin/installation/setting-up-a-github-enterprise-server-instance) before you turn on GitHub Advanced Security code scanning. {% comment %} https://github.com/github/releases/issues/768 {% endcomment %} - - - heading: Pull Request Retargeting - notes: - - | - When a [pull request's head branch](https://docs.github.com/en/enterprise/2.22/user/github/collaborating-with-issues-and-pull-requests/about-branches#working-with-branches) is merged and deleted, all other open pull requests in the same repository that target this branch are now retargeted to the merged pull request's base branch. Previously these pull requests were closed. {% comment %} https://github.com/github/releases/issues/801 {% endcomment %} - - - heading: Suspend and Unsuspend an App Installation - notes: - - | - Administrators and users can [suspend any GitHub App’s access](https://docs.github.com/enterprise/2.22/user/rest/reference/apps#suspend-an-app-installation) for as long as needed, and [unsuspend the app](https://docs.github.com/enterprise/2.22/user/rest/reference/apps#unsuspend-an-app-installation) on command through Settings and the API. Suspended apps cannot access the GitHub API or webhook events. You can use this instead of uninstalling an application, which deauthorises every user. {% comment %} https://github.com/github/github/pull/138316 https://github.com/github/github/pull/150869 {% endcomment %}'' - - - heading: Improved Large Scale Performance - notes: - - | - We have revised the approach we take to scheduling network maintenance for repositories, ensuring large monorepos are able to avoid failure states. {% comment %} https://github.com/github/github/pull/146789, https://github.com/github/github/pull/147931, https://github.com/github/github/pull/146724, https://github.com/github/git-protocols/issues/94 {% endcomment %}'' - - Passive replicas are now [supported and configurable on GitHub Enterprise Server cluster deployments](https://docs.github.com/en/enterprise/2.22/admin/enterprise-management/configuring-high-availability-replication-for-a-cluster). These changes will enable faster failover, reducing RTO and RPO. {% comment %} https://github.com/github/releases/issues/905 {% endcomment %} - - - heading: View All of Your Users - notes: - - | - For exceptionally large teams, administrators can [adjust the 1,500 default maximum for user lists](https://docs.github.com/en/enterprise/2.22/admin/configuration/command-line-utilities#ghe-config). {% comment %} https://github.com/github/github/pull/146508 {% endcomment %}'' - - changes: - - heading: Administration Changes - notes: - - Shared workers have been enabled to make live updates more resilient by sharing connections across tabs. {% comment %} https://github.com/github/releases/issues/914 {% endcomment %} - - The "Contact Support" link on `50x` error pages now links to the support email or link configured in the Management Console. {% comment %} https://github.com/github/github/pull/142123 {% endcomment %} - - It's now possible to [manage global announcements and expiration dates through the enterprise account settings](https://docs.github.com/en/enterprise/2.22/admin/installation/command-line-utilities#ghe-announce). {% comment %} https://github.com/github/releases/issues/945, https://github.com/github/github/pull/148475, https://github.com/github/github/pull/148494 {% endcomment %} - - You can now [exempt certain users from the default API rate limits configured in the management console](https://docs.github.com/en/enterprise/2.22/admin/configuration/configuring-rate-limits), if necessary. {% comment %} https://github.com/github/github/pull/148673 {% endcomment %} - - Repository administrators can now [set their repository to any available visibility option](https://docs.github.com/en/enterprise/2.22/user/github/administering-a-repository/setting-repository-visibility) from a single dialog in the repository's settings. Previously, you had to navigate separate sections, buttons, and dialog boxes for changing between public and private and between private and internal. {% comment %} https://github.com/github/releases/issues/882 {% endcomment %} - - A new Enterprise settings link on the user dropdown menu makes it easier to navigate to Enterprise Account Settings. {% comment %} https://github.com/github/releases/issues/946, https://github.com/github/github/pull/150595, https://github.com/github/github/pull/150520, https://github.com/github/github/pull/151121, https://github.com/github/hydro-schemas/pull/1244 {% endcomment %} - - The legacy "Admin Center" link on the /stafftools page has been removed. The "Enterprise" link is now the best way to navigate to the Enterprise Account from the /stafftools page. {% comment %} https://github.com/github/github/pull/147633 {% endcomment %} - - The Options sub-menu item in the Enterprise Account settings has been moved from the Settings section to the Policies section. {% comment %} https://github.com/github/releases/issues/944, https://github.com/github/github/pull/148477 {% endcomment %} - - '[Accessing resources by using a personal access token or SSH key now counts as user activity](https://docs.github.com/en/enterprise/2.22/admin/user-management/managing-dormant-users). This relieves administrators from the burden of filtering out certain users from the user dormancy reports and makes it safer to use the "Suspend all" button without accidentally suspending users who only accessed GitHub in a read-only way over the APIs with a Personal Access Token (PAT) or SSH key. {% comment %} https://github.com/github/github/pull/140433, https://github.com/github/help-docs/pull/14853, https://github.com/github/customer-feedback/issues/174, https://github.com/github/supportability/issues/14 {% endcomment %}' - - - heading: Security Changes - notes: - - Two-factor recovery codes can no longer be used during the two-factor sign in process. One-Time-Passwords are the only acceptable values. {% comment %} https://github.com/github/github/pull/145016, https://github.com/github/github/pull/140208 {% endcomment %} - - When a user is signed into GitHub Enterprise Server through single sign-on, the [default repository visibility selection is Private](https://docs.github.com/en/enterprise/2.22/user/github/administering-a-repository/setting-repository-visibility). {% comment %} https://github.com/github/releases/issues/872 {% endcomment %} - - Owners of GitHub Apps can now choose to have their [user-to-server access tokens expire after 8 hours](https://developer.github.com/changes/2020-04-30-expiring-user-to-server-access-tokens-for-github-apps/), to help enforce regular token rotation and reduce the impact of a compromised token. {% comment %} https://github.com/github/releases/issues/966 {% endcomment %} - - - heading: Developer Changes - notes: - - '[The GitHub UI has undergone a design refresh](https://github.blog/changelog/2020-06-23-design-updates-to-repositories-and-github-ui/), and the repositories homepage has been redesigned, including a responsive layout and improved mobile web experience. {% comment %} https://github.com/github/releases/issues/886 {% endcomment %}' - - In the "Clone with SSH" repository dropdown menu, users will now be notified if they do not have any keys setup. {% comment %} https://github.com/github/github/pull/149098 {% endcomment %} - - Commits are now ordered chronologically in the pull request timeline and commits tab. This new ordering is also reflected in the ["List commits on a pull request"](https://docs.github.com/en/enterprise/2.22/user/rest/reference/pulls#list-commits-on-a-pull-request) REST API and GraphQL ["PullRequest object"](https://docs.github.com/en/enterprise/2.22/user/graphql/reference/objects#pullrequest) timeline connection. {% comment %} https://github.com/github/releases/issues/867 {% endcomment %} - - Users can now [set a skin tone default for emoji autocomplete results](https://github.blog/changelog/2020-07-17-customizable-skin-tones-in-emoji-autocomplete/) in comment text areas. {% comment %} https://github.com/github/releases/issues/916 {% endcomment %} - - '[Tree-sitter](https://github.com/tree-sitter/tree-sitter) improves syntax highlighting and is now the default library used for language parsing. {% comment %} https://github.com/github/releases/issues/918, https://github.com/github/windrose/issues/44 {% endcomment %}' - - - heading: Users and organizations can add Twitter usernames to their GitHub profiles - notes: - - '[Developers and organizations can now add their Twitter username to their profile](https://github.blog/changelog/2020-07-22-users-and-organizations-can-now-add-twitter-usernames-to-their-github-profiles/) {% comment %} https://github.com/github/github/pull/145127 {% endcomment %}' - - - heading: API Changes - notes: - - | - #### Graduated Previews - - The following previews are now an official part of the API: - * The GitHub Apps API and endpoints that returned the `performed_via_github_app` property no longer require the [`machine-man`](https://developer.github.com/changes/2020-08-20-graduate-machine-man-and-sailor-v-previews/) preview header. {% comment %} https://github.com/github/releases/issues/965 {% endcomment %} - * To add and view a lock reason to an issue, you no longer need to use the [`sailor-v`](https://developer.github.com/changes/2020-08-20-graduate-machine-man-and-sailor-v-previews/) preview header. {% comment %} https://github.com/github/github/pull/143676 {% endcomment %} - - - | - #### GraphQL Schema Changes - - * [The GraphQL schema changes](https://docs.github.com/enterprise/2.22/user/graphql/overview/changelog) include backwards-compatible changes, schema previews, and upcoming breaking changes. - - - heading: VMware Network Driver Changes - notes: - - | - The GitHub Enterprise Server default network adapter type for VMware customers has been changed from E1000 to VMXNET3, starting with release 2.22.0. When upgrading from an earlier release to 2.22.0 or newer, if an E1000 network adapter is detected during the pre-upgrade check, the following message will be displayed at the command line: - - ``` - WARNING: Your virtual appliance is currently using an emulated Intel E1000 network adapter. - For optimal performance, please update the virtual machine configuration on your VMware host to use the VMXNET3 driver. - Proceed with installation? [y/N] - ``` - - The administrator can choose to update the network adapter type to VMXNET3 either before or after the GitHub Enterprise Server upgrade. The virtual appliance will need to be shutdown for this change. Customers should follow the VMware recommended steps for [changing the virtual machine network adapter configuration](https://docs.vmware.com/en/VMware-vSphere/7.0/com.vmware.vsphere.vm_admin.doc/GUID-3719A0BE-4B4A-44FF-8A21-290950918FBD.html) to VMXNET3. Please note that `VMXNET3` will not be an option if the OS version for the virtual appliance is set to `Other Linux (64-bit)`. In that case, the OS version would first need to be changed from `Other Linux (64-bit)` to `Other 2.6.x Linux (64-bit)` or if available, `Debian GNU/Linux 9` . We recommend testing these changes on a [staging instance](https://docs.github.com/en/enterprise-server@2.22/admin/installation/setting-up-a-staging-instance) before it is performed on a production GitHub Enterprise Server. {% comment %} https://github.com/github/ghes-infrastructure/issues/781 {% endcomment %} - - bugs: - - The stafftools page for viewing pending collaborator showed a `500 Internal Server Error` when there was a pending email invite. {% comment %} https://github.com/github/github/pull/150836 {% endcomment %} - - The Repository Health Check in stafftools could give incorrect results on busy repositories. {% comment %} https://github.com/github/github/pull/151160 {% endcomment %} - - A logged in user trying to accept an email invitation could get a `404 Not Found` error. {% comment %} https://github.com/github/github/pull/150848 {% endcomment %} - - If a user navigated to a repository whose name started with "repositories.", they were redirected to the owner's "Repositories" tab instead of landing on the repository overview page. {% comment %} https://github.com/github/github/pull/149704 {% endcomment %} - - Labels in the dashboard timeline did not have enough contrast. {% comment %} https://github.com/github/github/pull/146749 {% endcomment %} - - deprecations: - - heading: Upcoming Deprecation of GitHub Enterprise Server 2.19 - notes: - - '**GitHub Enterprise Server 2.19 will be 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 GitHub Enterprise 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 GitHub Enterprise Server 2.21.0 two legacy GitHub Apps-related webhook events have been deprecated and will be removed in GitHub Enterprise Server 2.25.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/). {% comment %} https://github.com/github/enterprise-web/pull/6419#issuecomment-668303461 {% endcomment %} - - heading: Deprecation of Legacy GitHub Apps Endpoint - notes: - - Starting with GitHub Enterprise Server 2.21.0 the legacy GitHub Apps endpoint for creating installation access tokens was deprecated and will be removed in GitHub Enterprise Server 2.25.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/). {% comment %} https://github.com/github/enterprise-web/pull/6419#issuecomment-668303461 {% endcomment %} - - 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 GitHub Enterprise Server 3.4. For more information, see the [deprecation announcement blog post](https://developer.github.com/changes/2020-02-14-deprecating-oauth-app-endpoint/). - - backups: - - GitHub Enterprise Server 2.22 requires at least [GitHub Enterprise Backup Utilities](https://github.com/github/backup-utils) 2.22.0 for [Backups and Disaster Recovery](https://help.github.com/enterprise/2.22/admin/guides/installation/backups-and-disaster-recovery/). - - known_issues: - - On a freshly set up GitHub Enterprise Server without any users, an attacker could create the first admin user. {% comment %} https://github.com/github/enterprise2/issues/1889 {% endcomment %} - - Custom firewall rules are not maintained during an upgrade. {% comment %} https://github.com/github/enterprise2/issues/2823 {% endcomment %} - - 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. {% comment %} https://github.com/github/github/issues/54684 {% endcomment %} - - 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. {% comment %} https://github.com/github/github/issues/107731 {% endcomment %} - - 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. {% comment %} https://github.com/github/admin-experience/issues/571 {% endcomment %} - - The Name ID Format dropdown in the Management Console resets to "unspecified" after setting instance to "persistent". {% comment %} https://github.com/github/enterprise2/issues/13446 {% endcomment %} - - The repository Settings page of a repository for a user or organization GitHub Pages sites will fail with a "500 Internal Server Error". {% comment %} https://github.com/github/github/issues/156183 {% endcomment %} - - Users may experience slower Git clone and fetch performance on an instance with high availability replicas due to reads being forwarded to a different node. {% comment %} https://github.com/github/spokesd/issues/746 {% endcomment %} - - '[Creating a GitHub App from a manifest](https://docs.github.com/en/enterprise/2.22/user/developers/apps/creating-a-github-app-from-a-manifest) fails. To work around this issue, users can follow the manual instructions for [creating a GitHub App](https://docs.github.com/en/enterprise/2.22/user/developers/apps/creating-a-github-app). {% comment %} https://github.com/github/enterprise2/issues/22849 {% endcomment %}' - - GitHub usernames may change unintentionally when using SAML authentication, if the GitHub username does not match the value of the attribute mapped to the `username` field in the Management Console. (updated 2020-10-08) {% comment %} https://github.com/github/external-identities/issues/335 {% endcomment %} - - On a freshly set up 2.22.0 instance or after upgrading to 2.22.0, the activity feed on an organization's dashboard will no longer update. (updated 2020-10-27) {% comment %}https://github.com/github/enterprise2/issues/23050{% endcomment %} - - Audit logs may be attributed to 127.0.0.1 instead of the actual source IP address. (updated 2020-11-02) {% comment %} https://github.com/github/enterprise2/issues/21514 {% endcomment %} - - 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. diff --git a/translations/zh-CN/data/release-notes/enterprise-server/2-22/1.yml b/translations/zh-CN/data/release-notes/enterprise-server/2-22/1.yml deleted file mode 100644 index 928b7fa41c..0000000000 --- a/translations/zh-CN/data/release-notes/enterprise-server/2-22/1.yml +++ /dev/null @@ -1,74 +0,0 @@ -date: '2020-10-09' -sections: - security_fixes: - - '**MEDIUM**: ImageMagick has been updated to address [DSA-4715-1](https://www.debian.org/security/2020/dsa-4715). {% comment %} https://github.com/github/enterprise2/pull/22623, https://github.com/github/enterprise2/pull/22610 {% endcomment %}' - - 'Requests from a GitHub App integration to refresh an OAuth access token would be accepted if sent with a different, valid OAuth client ID and client secret than was used to create the refresh token. {% comment %} https://github.com/github/github/pull/154921, https://github.com/github/github/pull/154423, https://github.com/github/ecosystem-apps/issues/1066 {% endcomment %}' - - 'A user whose LDAP directory username standardizes to an existing GHES account login could authenticate into the existing account. {% comment %} https://github.com/github/github/pull/156513, https://github.com/github/github/pull/155512 {% endcomment %}' - - 'Packages have been updated to the latest security versions. {% comment %} https://github.com/github/enterprise2/pull/22912, https://github.com/github/enterprise2/pull/22878 {% endcomment %}' - - bugs: - - | - The NameID Format dropdown in the Management Console would be reset to "unspecified" after setting it to "persistent". {% comment %} https://github.com/github/enterprise2/pull/22376, https://github.com/github/enterprise2/pull/22331, https://github.com/github/enterprise2/issues/13446 {% endcomment %} - - | - Upgrading using a hotpatch could fail with an error: `'libdbi1' was not found` {% comment %} https://github.com/github/enterprise2/pull/22557, https://github.com/github/enterprise2/pull/22552 {% endcomment %} - - | - Saving settings via the [management console](/admin/configuration/accessing-the-management-console) would append a newline to the [TLS/SSL certificate and key](/admin/configuration/configuring-tls) files which triggered unnecessary reloading of some services. {% comment %} https://github.com/github/enterprise2/pull/22570, https://github.com/github/enterprise2/pull/22540 {% endcomment %} - - | - System logs for Dependency Graph were not rotating, allowing unbounded storage growth. {% comment %} https://github.com/github/enterprise2/pull/22767, https://github.com/github/enterprise2/pull/22733 {% endcomment %} - - | - The MS SQL Server performance graph showed statistics from the primary instance even when a replica was selected. {% comment %} https://github.com/github/enterprise2/pull/22778, https://github.com/github/enterprise2/pull/22750 {% endcomment %} - - | - `ghe-actions-precheck` would silently exit without running the storage checks if Actions was not enabled. {% comment %} https://github.com/github/enterprise2/pull/22787, https://github.com/github/enterprise2/pull/22742 {% endcomment %} - - | - Upgrade could fail if the resqued workers override setting is in use. {% comment %} https://github.com/github/enterprise2/pull/22836, https://github.com/github/enterprise2/pull/22814 {% endcomment %} - - | - Some services running in containers were not sending logs to the journal. {% comment %} https://github.com/github/enterprise2/pull/22994, https://github.com/github/enterprise2/pull/22518 {% endcomment %} - - | - Links to GitHub Security Advisories would use a URL with the hostname of the GitHub Enterprise Server instance instead of GitHub.com, directing the user to a nonexistent URL. {% comment %} https://github.com/github/github/pull/153316, https://github.com/github/github/pull/151301 {% endcomment %} - - | - When importing a repository with `ghe-migrator`, an unexpected exception could occur when inconsistent data is present. {% comment %} https://github.com/github/github/pull/153850, https://github.com/github/github/pull/151552 {% endcomment %} - - | - The enterprise account security settings page showed a "View your organizations' current configurations" link for the "Two-factor authentication" setting when the authentication mode in use does not support built in two-factor authentication. {% comment %} https://github.com/github/github/pull/153860 {% endcomment %} - - | - OAuth refresh tokens would be removed prematurely. {% comment %} https://github.com/github/github/pull/154271, https://github.com/github/github/pull/153694 {% endcomment %} - - | - Search repair tasks would generate exceptions during the migration phase of configuration. {% comment %} https://github.com/github/github/pull/154573, https://github.com/github/github/pull/153392 {% endcomment %} - - | - On the settings page for GitHub Apps, the "Beta Features" tab was not visible in some circumstances. {% comment %} https://github.com/github/github/pull/154612, https://github.com/github/github/pull/154417 {% endcomment %} - - | - When using `ghe-migrator` to import PR review requests, records associated with deleted users would result in extraneous database records. {% comment %} https://github.com/github/github/pull/154960, https://github.com/github/github/pull/153169 {% endcomment %} - - | - When importing users with `ghe-migrator`, an error of "Emails is invalid" would occur if the system-generated email address were longer than 100 characters. {% comment %} https://github.com/github/github/pull/155109, https://github.com/github/github/pull/152418 {% endcomment %} - - | - Logging webhook activity could use large amounts of disk space and cause the root disk to become full. {% comment %} https://github.com/github/github/pull/155657, https://github.com/github/github/pull/154100 {% endcomment %} - - | - Users experienced slower Git clone and fetch performance on an instance with high availability replicas due to reads being forwarded to a different node. {% comment %} https://github.com/github/github/pull/156195, https://github.com/github/github/pull/156016, https://github.com/github/spokesd/issues/746 {% endcomment %} - - | - The repository Settings page of a repository for a user or organization GitHub Pages sites would fail with a "500 Internal Server Error". {% comment %} https://github.com/github/github/pull/156439, https://github.com/github/github/issues/156183 {% endcomment %} - - | - Repository network maintenance operations could become stuck in a `running` state. {% comment %} https://github.com/github/github/pull/156669, https://github.com/github/github/pull/156036 {% endcomment %} - - | - A repository being deleted immediately after uploading a code scanning result could cause a stall in the processing of code scanning results for all repositories. {% comment %} https://github.com/github/github/pull/157063, https://github.com/github/github/pull/156437 {% endcomment %} - - | - When a large number of code scanning results were submitted at the same time, processing of batches could time out resulting in a stall in processing of code scanning results. {% comment %} https://github.com/github/github/pull/157065, https://github.com/github/github/pull/156462 {% endcomment %} - - | - [Creating a GitHub App from a manifest](https://docs.github.com/en/enterprise/2.22/user/developers/apps/creating-a-github-app-from-a-manifest) would fail. {% comment %} https://github.com/github/github/pull/157133, https://github.com/github/github/pull/156904, https://github.com/github/enterprise2/issues/22849 {% endcomment %} - - | - GitHub usernames were changed unintentionally when using SAML authentication, when the GitHub username did not match the value of the attribute mapped to the `username` field in the Management Console. {% comment %} https://github.com/github/github/pull/158131, https://github.com/github/github/pull/157936, https://github.com/github/external-identities/issues/335 {% endcomment %} - - changes: - - Support is added for the AWS EC2 instance type `m5.16xlarge`. {% comment %} https://github.com/github/enterprise2/pull/22502, https://github.com/github/enterprise2/pull/22473 {% endcomment %} - - Remove the requirement for SSH fingerprints in `ghe-migrator` archives as it can always be computed. {% comment %} https://github.com/github/github/pull/156946, https://github.com/github/github/pull/155387 {% endcomment %} - - GitHub App Manifests now include the `request_oauth_on_install` field. {% comment %} https://github.com/github/github/pull/156991, https://github.com/github/github/pull/155010, https://github.com/github/ecosystem-apps/issues/1055 {% endcomment %} - - known_issues: - - On a freshly set up GitHub Enterprise Server without any users, an attacker could create the first admin user. {% comment %} https://github.com/github/enterprise2/issues/1889 {% endcomment %} - - Custom firewall rules are not maintained during an upgrade. {% comment %} https://github.com/github/enterprise2/issues/2823 {% endcomment %} - - 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. {% comment %} https://github.com/github/github/issues/54684 {% endcomment %} - - 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. {% comment %} https://github.com/github/github/issues/107731 {% endcomment %} - - 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. {% comment %} https://github.com/github/admin-experience/issues/571 {% endcomment %} - - Configuration updates will fail when restoring data to a GitHub Actions-enabled instance if the original backup source did not have the feature enabled. {% comment %} https://github.com/github/c2c-actions-runtime/issues/915 {% endcomment %} - - GitHub Actions can fail to start up successfully if it was previously enabled on an instance running 2.22.0 and is upgraded to 2.22.1. (updated 2020-10-23) {% comment %} https://github.com/github/c2c-actions/issues/1680 {% endcomment %} - - On a freshly set up 2.22.1 instance or after upgrading to 2.22.1, the activity feed on an organization's dashboard will no longer update. (updated 2020-10-27) {% comment %}https://github.com/github/enterprise2/issues/23050{% endcomment %} - - Audit logs may be attributed to 127.0.0.1 instead of the actual source IP address. (updated 2020-11-02) {% comment %} https://github.com/github/enterprise2/issues/21514 {% endcomment %} - - 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. 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 deleted file mode 100644 index 4fbde7ebaa..0000000000 --- a/translations/zh-CN/data/release-notes/enterprise-server/2-22/10.yml +++ /dev/null @@ -1,16 +0,0 @@ -date: '2021-04-01' -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) 进行报告。" - - 包已更新到最新的安全版本。 - bugs: - - 某些默认为 UTC 时间的服务未使用在 GitHub Enterprise 11.10.x 或更早版本上设置的时区。 - - 服务未作为日志轮换的一部分转换到新的日志文件，导致磁盘使用量增加。 - - 内部存储库搜索结果上的标签显示为“专用”而不是“内部”。 - known_issues: - - 在没有任何用户的新建 GitHub Enterprise Server 上，攻击者可以创建第一个管理员用户。 - - 在升级期间不会维护自定义防火墙规则。 - - "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 deleted file mode 100644 index 5c160dca8c..0000000000 --- a/translations/zh-CN/data/release-notes/enterprise-server/2-22/11.yml +++ /dev/null @@ -1,19 +0,0 @@ -date: '2021-04-14' -sections: - security_fixes: - - 包已更新到最新的安全版本。 - bugs: - - '警告消息 `jq: error (at :0): Cannot index number with string "settings"` 可能在副本升级期间出现。' - - 由于 MySQL 副本无法连接到主数据库，因此将备份连续还原到群集可能会失败。 - - 由于 Treelights 容器内存不足，语法高亮可能失败。 - - 访问 `/settings/email` 页面会存储状态，在退出登录并重新登录时可能导致错误的重定向。 - - 对于其通告在 `vulnerable_version_ranges` 中具有大写包名称的一些组件，未显示依赖项关系图警报。 - - 在问题评论中通过提及功能直接提及团队时，GitHub 集成应用程序无法通知团队。 - - 当 ghe-migrator 遇到导入错误时，它有时会中止整个进程，但日志中没有包含足够的上下文。 - known_issues: - - 在新建的没有任何用户的 GitHub Enterprise Server 上，攻击者可以创建第一个管理员用户。 - - 在升级期间不会维护自定义防火墙规则。 - - "[通过 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 deleted file mode 100644 index 5cc9632ff8..0000000000 --- a/translations/zh-CN/data/release-notes/enterprise-server/2-22/12.yml +++ /dev/null @@ -1,22 +0,0 @@ -date: '2021-04-28' -sections: - security_fixes: - - 包已更新到最新的安全版本。 - bugs: - - 在升级过程中，进程将在 `cleanup nomad job` 之后无限期暂停。 - - '`ghe-cluster-failover` 失败，出现错误消息 `Trilogy::Error: trilogy_connect`。' - - '`ghe-cluster-status-mysql` 将有关故障转移的警告显示为错误。' - - 在 MySQL 副本上运行的安装脚本可能导致数据库故障转移期间不必要的数据库重新播种。 - - '由于不必要地调用 `rake db:migrate`，`config-apply` 可能需要更长的时间。' - - Orchestrator 可能已故障转移到 MySQL 副本，当主数据库无法连接时，它无法在播种阶段从主数据库复制。 - - 出现错误的组织或项目阻止了迁移，无法排除。 - - 由于选择了最完整的磁盘而不是空节点，存储主机超过三个的客户无法恢复到其灾难恢复群集。 - changes: - - 默认情况下，预运行检查允许所有 AWS 实例类型。 - known_issues: - - 在没有任何用户的新建 GitHub Enterprise Server 上，攻击者可能创建第一个管理员用户。 - - 在升级期间不会维护自定义防火墙规则。 - - "[通过 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 deleted file mode 100644 index 6b86c7620b..0000000000 --- a/translations/zh-CN/data/release-notes/enterprise-server/2-22/13.yml +++ /dev/null @@ -1,20 +0,0 @@ -date: '2021-05-13' -sections: - security_fixes: - - "**高：**在 GitHub Enterprise Server 中发现 UI 表述错误漏洞，在审批阶段，该问题会导致在 GitHub 应用用户授权 Web 流中授予超过 UI 显示的权限。要利用这个漏洞，攻击者需要在实例上创建 GitHub 应用，并让用户通过 Web 身份验证流对应用程序进行授权。所有被授予的权限将在第一次授权时正确显示，但在某些情况下，如果用户在 GitHub 应用已配置额外的用户级别权限后重新访问授权流，这些额外的权限可能不会显示，这样会导致授予可能超过用户初衷的权限。此漏洞影响 GitHub Enterprise Server 3.0.x 到 3.0.7 版本以及 2.22.x 到 2.22.13 版本。3.0.7 和 2.22.13 版本中修复了该问题。该漏洞编号为 CVE-2021-22866，通过 [GitHub Bug 赏金计划](https://bounty.github.com/) 报告。" - - 包已更新到最新的安全版本。 - bugs: - - 在配置应用阶段可以启用 Orchestrator 自动故障转移。 - - 具有存储库维护员权限的用户会收到电子邮件验证警告，而不是在存储库 Pages 设置页面上构建成功的页面。 - - 通配符规则的代码所有者将被错误地添加到代码所有者徽章的所有者列表中，即使该路径优先使用较新的规则。 - - OpenAPI 文档引用了无效的标头。 - changes: - - 添加了 HAProxy 重载时配置更改的日志记录。 - - 添加了仓库创建的日志记录。 - known_issues: - - 在新建的没有任何用户的 GitHub Enterprise Server 上，攻击者可以创建第一个管理员用户。 - - 在升级期间不会维护自定义防火墙规则。 - - "[通过 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 deleted file mode 100644 index bad192aca2..0000000000 --- a/translations/zh-CN/data/release-notes/enterprise-server/2-22/14.yml +++ /dev/null @@ -1,18 +0,0 @@ -date: '2021-05-25' -sections: - security_fixes: - - '**中：**在某些情况下，从团队或组织中删除的用户可以保留对已打开现有拉取请求的分支的写入权限。' - - 包已更新到最新的安全版本。 - bugs: - - MSSQL 中的正常复制延迟会生成警告。 - - 管理员使用“创建白名单条目”按钮添加的 IP 地址仍可能被锁定。 - - '`spokesd` 创建了过多的日志条目，包括“修复位置已跳过”短语。' - changes: - - 超过 4 个月的检查注释将存档。 - known_issues: - - 在没有任何用户的新建 GitHub Enterprise Server 上，攻击者可能创建第一个管理员用户。 - - 在升级期间不会维护自定义防火墙规则。 - - "[通过 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 deleted file mode 100644 index a15bc73c4a..0000000000 --- a/translations/zh-CN/data/release-notes/enterprise-server/2-22/15.yml +++ /dev/null @@ -1,16 +0,0 @@ -date: '2021-06-10' -sections: - security_fixes: - - 包已更新到最新的安全版本。 - bugs: - - "从非 GitHub 源导入组织或存储库失败可能会产生 `undefined method '[]' for nil:NilClass` 错误。" - - 使用 SAML 身份验证时，如果 GitHub 配置文件名称不匹配管理控制台中映射到 `Full name` 字段的属性值，GitHub 配置文件名称可能已无意中更改。 - changes: - - GraphQL API 用户可在 `PullRequest` 对象上查询公共字段 `closingIssuesReferences`。该字段检索将在合并相关拉取请求时自动关闭的问题。这种方法还将允许将来迁移这些数据，作为更高保真度迁移过程的一部分。 - known_issues: - - 在新建的没有任何用户的 GitHub Enterprise Server 上，攻击者可以创建第一个管理员用户。 - - 自定义防火墙规则在升级过程中被删除。 - - "[通过 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 deleted file mode 100644 index b3ef760893..0000000000 --- a/translations/zh-CN/data/release-notes/enterprise-server/2-22/16.yml +++ /dev/null @@ -1,15 +0,0 @@ -date: '2021-06-24' -sections: - security_fixes: - - 包已更新到最新的安全版本。 - bugs: - - sshd 服务有时无法从 Google Cloud Platform 上运行的实例启动。 - - 旧的升级文件将保留在用户磁盘上，有时会导致空间不足。 - - 如果导出存档包含来自存档中不存在的团队的审查请求，则导出存档将无法导入拉取请求并且无提示。 - known_issues: - - 在没有任何用户的新建 GitHub Enterprise Server 上，攻击者可以创建第一个管理员用户。 - - 将在升级过程中删除自定义防火墙规则。 - - "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 deleted file mode 100644 index e344b6c696..0000000000 --- a/translations/zh-CN/data/release-notes/enterprise-server/2-22/17.yml +++ /dev/null @@ -1,20 +0,0 @@ -date: '2021-07-14' -sections: - security_fixes: - - '**高：**在 GitHub Enterprise Server 中发现了一个在构建 GitHub Pages 站点时可以利用的路径遍历漏洞。GitHub Pages 使用的用户控制配置选项没有受到足够的限制，因此可以读取 GitHub Enterprise Server 实例上的文件。要利用此漏洞，攻击者需要获得在 GitHub Enterprise Server 实例上创建和构建 GitHub Pages 站点的权限。此漏洞影响 3.1.3 之前的所有 GitHub Enterprise Server 版本，编号为 CVE-2021-22867。此漏洞通过 GitHub Bug 赏金计划报告。' - - 包已更新到最新的安全版本。 - bugs: - - '如果启用了 HTTP 代理，则 `ghe-cluster-config-node-init` 会在群集设置期间失败。' - - Collectd 在初始启动后不会解析转发目标主机名。 - - 如果其中部分存储库因受法律保护而无法被删除，则清除陈旧的已删除存储库的作业可能会失败。 - - 在使用 LDAP 身份验证模式的实例的用户协调过程中，Git 推送可能导致 500 内部服务器错误。 - - 如果未启用依赖项关系图，则每当用户访问存储库的 `/settings` 页时，都会记录大量 503 错误。 - changes: - - 通过跳过未更改的 IP 允许防火墙规则，提高了配置应用效率，可在大型群集上节省大量时间。 - known_issues: - - 在新建的没有任何用户的 GitHub Enterprise Server 上，攻击者可能创建第一个管理员用户。 - - 自定义防火墙规则在升级过程中被删除。 - - "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 deleted file mode 100644 index 8438662329..0000000000 --- a/translations/zh-CN/data/release-notes/enterprise-server/2-22/18.yml +++ /dev/null @@ -1,16 +0,0 @@ -date: '2021-07-27' -sections: - security_fixes: - - 包已更新到最新的安全版本。 - bugs: - - 如果在未启用依赖项关系图但启用了内容分析的情况下尝试运行将漏洞与 GitHub.com 同步的计划作业，则会生成大量 503 错误。 - - 对于使用 HTTP 代理的所有用户，不支持使用未经身份验证的 HTTP 代理来进行页面容器构建。 - changes: - - "`babeld` 的日志现在包含一个用于 HTTP ref 广告请求的 `cmd` 字段，而不是仅在协商请求期间包含该字段。" - known_issues: - - "在新建的没有任何用户的 {% data variables.product.prodname_ghe_server %} 上，攻击者可以创建第一个管理员用户。" - - 自定义防火墙规则在升级过程中被删除。 - - "[通过 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 deleted file mode 100644 index 9da19f2fd0..0000000000 --- a/translations/zh-CN/data/release-notes/enterprise-server/2-22/19.yml +++ /dev/null @@ -1,13 +0,0 @@ -date: '2021-08-10' -sections: - bugs: - - 对“存储库创建”组织设置所做更改的审核日志条目不准确。 - changes: - - 滥用速率限制现在称为辅助速率限制，因为它们限制的行为并不总是滥用。 - known_issues: - - "在新建的没有任何用户的 {% data variables.product.prodname_ghe_server %} 上，攻击者可以创建第一个管理员用户。" - - 自定义防火墙规则在升级过程中被删除。 - - "[通过 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/2.yml b/translations/zh-CN/data/release-notes/enterprise-server/2-22/2.yml deleted file mode 100644 index 42e92d228d..0000000000 --- a/translations/zh-CN/data/release-notes/enterprise-server/2-22/2.yml +++ /dev/null @@ -1,31 +0,0 @@ -date: '2020-10-20' -sections: - security_fixes: - - Packages have been updated to the latest security versions. {% comment %} https://github.com/github/enterprise2/pull/23097, https://github.com/github/enterprise2/pull/23081 {% endcomment %} - - bugs: - - | - If the storage account settings failed to validate while configuring GitHub Actions, running `ghe-actions-teardown` was required before making a new attempt. {% comment %} https://github.com/github/enterprise2/pull/23057, https://github.com/github/enterprise2/pull/22981 {% endcomment %} - - | - A custom proxy configuration could adversely affect the GitHub Actions environment. {% comment %} https://github.com/github/enterprise2/pull/23121, https://github.com/github/enterprise2/pull/23092, https://github.com/github/c2c-actions-platform/issues/2254 {% endcomment %} - - | - On a change of an address on eth0, Nomad and Consul could get unresponsive. {% comment %} https://github.com/github/enterprise2/pull/23227, https://github.com/github/enterprise2/pull/23153 {% endcomment %} - - | - When using self-signed certificates, GHES could have SSL validation exceptions upon configuring GitHub Actions. {% comment %} https://github.com/github/enterprise2/pull/23381 {% endcomment %} - - | - Using a GitHub Action from a branch name with a `+` or `/` character resulted in an error: `Unable to resolve action`. {% comment %} https://github.com/github/github/pull/157942, https://github.com/github/github/pull/157819, https://github.com/github/launch/pull/3463 {% endcomment %} - - | - The enterprise account "Confirm two-factor requirement policy" messaging was incorrect. {% comment %} https://github.com/github/github/pull/158735 {% endcomment %} - - | - On certain requests above 100MB, Kafka's buffer could be over-allocated. {% comment %} https://github.com/github/kafka-lite/pull/286, https://github.com/github/kafka-lite/pull/285 {% endcomment %} - - known_issues: - - On a freshly set up GitHub Enterprise Server without any users, an attacker could create the first admin user. {% comment %} https://github.com/github/enterprise2/issues/1889 {% endcomment %} - - Custom firewall rules are not maintained during an upgrade. {% comment %} https://github.com/github/enterprise2/issues/2823 {% endcomment %} - - 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. {% comment %} https://github.com/github/github/issues/54684 {% endcomment %} - - 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. {% comment %} https://github.com/github/github/issues/107731 {% endcomment %} - - 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. {% comment %} https://github.com/github/admin-experience/issues/571 {% endcomment %} - - GitHub Actions can fail to start up successfully if it was previously enabled on an instance running 2.22.0 and is upgraded to 2.22.2. (updated 2020-10-23) {% comment %} https://github.com/github/c2c-actions/issues/1680 {% endcomment %} - - On a freshly set up 2.22.2 instance or after upgrading to 2.22.2, the activity feed on an organization's dashboard will no longer update. (updated 2020-10-27) {% comment %}https://github.com/github/enterprise2/issues/23050{% endcomment %} - - Audit logs may be attributed to 127.0.0.1 instead of the actual source IP address. (updated 2020-11-02) {% comment %} https://github.com/github/enterprise2/issues/21514 {% endcomment %} - - 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. 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 deleted file mode 100644 index de294794b9..0000000000 --- a/translations/zh-CN/data/release-notes/enterprise-server/2-22/20.yml +++ /dev/null @@ -1,14 +0,0 @@ -date: '2021-08-24' -sections: - security_fixes: - - 包已更新到最新的安全版本。 - bugs: - - 与自动更新相关的日志消息（`添加 h/m/s 随机时间。`）被记录到系统日志中。 - - "导致请求失败的内部 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)文件被错误地直接添加到存储库。" - - 如果问题包含同一存储库中文件路径长于 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 deleted file mode 100644 index fb986a4465..0000000000 --- a/translations/zh-CN/data/release-notes/enterprise-server/2-22/21.yml +++ /dev/null @@ -1,11 +0,0 @@ -date: '2021-09-07' -sections: - security_fixes: - - 包已更新到最新的安全版本。 - known_issues: - - "在新建的没有任何用户的 {% data variables.product.prodname_ghe_server %} 上，攻击者可能创建第一个管理员用户。" - - 自定义防火墙规则在升级过程中被删除。 - - "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/22.yml b/translations/zh-CN/data/release-notes/enterprise-server/2-22/22.yml deleted file mode 100644 index 8132ad054a..0000000000 --- a/translations/zh-CN/data/release-notes/enterprise-server/2-22/22.yml +++ /dev/null @@ -1,14 +0,0 @@ -date: '2021-09-24' -sections: - security_fixes: - - '**HIGH:** A path traversal vulnerability was identified in {% data variables.product.prodname_ghe_server %} that could be exploited when building a {% data variables.product.prodname_pages %} site. User-controlled configuration options used by {% data variables.product.prodname_pages %} were not sufficiently restricted and made it possible to read files on the {% data variables.product.prodname_ghe_server %} instance. To exploit this vulnerability, an attacker would need permission to create and build a {% data variables.product.prodname_pages %} site on the {% data variables.product.prodname_ghe_server %} instance. This vulnerability affected all versions of {% data variables.product.prodname_ghe_server %} prior to 3.1.8 and was fixed in 3.1.8, 3.0.16, and 2.22.22. This is the result of an incomplete fix for CVE-2021-22867. This vulnerability was reported via the GitHub Bug Bounty program and has been assigned CVE-2021-22868. {% comment %} https://github.com/github/pages/pull/3359, https://github.com/github/pages/pull/3357 {% endcomment %}' - bugs: - - 'The {% data variables.product.prodname_github_connect %} configuration of the source instance was always restored to new instances even when the `--config` option for `ghe-restore` was not used. This would lead to a conflict with the {% data variables.product.prodname_github_connect %} connection and license synchronization if both the source and destination instances were online at the same time. {% comment %} https://github.com/github/github/pull/192247, https://github.com/github/github/pull/191951, https://github.com/github/enterprise2/pull/26870, https://github.com/github/backup-utils/pull/770, https://github.com/github/connected-enterprise/issues/208 {% endcomment %}' - - 'Fixes {% data variables.product.prodname_pages %} builds so they take into account the NO_PROXY setting of the appliance. This is relevant to appliances configured with an HTTP proxy only. {% comment %} https://github.com/github/github/pull/192380 {% endcomment %}' - 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 {% data variables.product.prodname_github_connect %}, issues in private and internal repositories are not included in GitHub.com search results. - - 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. diff --git a/translations/zh-CN/data/release-notes/enterprise-server/2-22/3.yml b/translations/zh-CN/data/release-notes/enterprise-server/2-22/3.yml deleted file mode 100644 index 83b8ebfa6a..0000000000 --- a/translations/zh-CN/data/release-notes/enterprise-server/2-22/3.yml +++ /dev/null @@ -1,25 +0,0 @@ -date: '2020-11-03' -sections: - security_fixes: - - | - **LOW:** High CPU usage could be triggered by a specially crafted request to the SVN bridge resulting in Denial of Service (DoS) on the SVN bridge service. (updated 2020-11-16) {% comment %} https://github.com/github/slumlord/pull/1005, https://github.com/github/slumlord/pull/1000 {% endcomment %} - - | - **LOW:** Incorrect token validation resulted in a reduced entropy for matching tokens during authentication. Analysis shows that in practice there's no significant security risk here. {% comment %} https://github.com/github/github/pull/159457, https://github.com/github/github/pull/159193 {% endcomment %} - - | - Packages have been updated to the latest security versions. {% comment %} https://github.com/github/enterprise2/pull/23540, https://github.com/github/enterprise2/pull/23171, https://github.com/github/enterprise2/pull/23693, https://github.com/github/enterprise2/pull/23677 {% endcomment %} - - bugs: - - GitHub Actions could fail to start up successfully if it was previously enabled on an instance running 2.22.0 and was upgraded to 2.22.1 or 2.22.2. {% comment %} https://github.com/github/enterprise2/pull/23622, https://github.com/github/enterprise2/pull/23490, https://github.com/github/c2c-actions/issues/1680 {% endcomment %} - - Configuration files for GitHub Actions were not copied to the replica when setting up high availability replicas potentially leading to errors during `ghe-repl-promote`. {% comment %} https://github.com/github/enterprise2/pull/23703, https://github.com/github/enterprise2/pull/23683 {% endcomment %} - - On a freshly set up 2.22.1 or 2.22.2 instance or after upgrading to 2.22.1 or 2.22.2, the activity feed on an organization's dashboard would not update. {% comment %} https://github.com/github/github/pull/159376, https://github.com/github/github/pull/159235, https://github.com/github/enterprise2/issues/23050 {% endcomment %} - - Editing issues templates with filenames containing non-ASCII characters would fail with a "500 Internal Server Error". {% comment %} https://github.com/github/github/pull/160588, https://github.com/github/github/pull/159747 {% endcomment %} - - A metric gathering method for background jobs increased CPU utilization. (updated 2020-11-03) {% comment %} https://github.com/github/github/pull/160109 {% endcomment %} - - known_issues: - - On a freshly set up GitHub Enterprise Server without any users, an attacker could create the first admin user. {% comment %} https://github.com/github/enterprise2/issues/1889 {% endcomment %} - - Custom firewall rules are not maintained during an upgrade. {% comment %} https://github.com/github/enterprise2/issues/2823 {% endcomment %} - - 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. {% comment %} https://github.com/github/github/issues/54684 {% endcomment %} - - 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. {% comment %} https://github.com/github/github/issues/107731 {% endcomment %} - - 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. {% comment %} https://github.com/github/admin-experience/issues/571 {% endcomment %} - - Audit logs may be attributed to 127.0.0.1 instead of the actual source IP address. {% comment %} https://github.com/github/enterprise2/issues/21514 {% endcomment %} - - 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. 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 deleted file mode 100644 index 89218b634d..0000000000 --- a/translations/zh-CN/data/release-notes/enterprise-server/2-22/4.yml +++ /dev/null @@ -1,18 +0,0 @@ -date: '2020-11-17' -sections: - security_fixes: - - "包已更新到最新的安全版本。{% comment %} https://github.com/github/enterprise2/pull/23845, https://github.com/github/enterprise2/pull/23712 {% endcomment %}" - - bugs: - - "babeld 日志在秒与微秒之间缺少分隔符。{% comment %} https://github.com/github/babeld/pull/1006, https://github.com/github/babeld/pull/1002 {% endcomment %}" - - "在使用热补丁升级 GHES 之后，`ghe-actions-precheck` 和 `ghe-packages-precheck` 命令将会失败，并显示错误“\"docker load\" 不接受参数”。{% comment %} https://github.com/github/enterprise2/pull/23760, https://github.com/github/enterprise2/pull/23745 {% endcomment %}" - - "当企业帐户“存储库可见性更改”策略设置为“启用”时，组织所有者无法更改组织内存储库的可见性。{% comment %} https://github.com/github/github/pull/160920, https://github.com/github/github/pull/160773 {% endcomment %}" - - "审核日志可归因于 127.0.0.1，而不是实际源 IP 地址。{% comment %} https://github.com/github/github/pull/162438, https://github.com/github/github/pull/161215 {% 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 %}" - - "问题若是包含同一存储库中文件路径长于 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 deleted file mode 100644 index a4e0915993..0000000000 --- a/translations/zh-CN/data/release-notes/enterprise-server/2-22/5.yml +++ /dev/null @@ -1,22 +0,0 @@ -date: '2020-12-03' -sections: - bugs: - - '由于启动时争用条件导致服务重新启动，因此检测到授权服务不正常。{% comment %} https://github.com/github/authzd/pull/1275, https://github.com/github/authzd/pull/1274 {% endcomment %}' - - 'Ghe-diagnattics 未捕获到 Elasticsearch 的升级过程。{% comment %} https://github.com/github/enterprise2/pull/23905, https://github.com/github/enterprise2/pull/23874 {% endcomment %}' - - '在升级的高可用性配置上启用 GitHub Actions 导致复制出错。{% comment %} https://github.com/github/enterprise2/pull/23979, https://github.com/github/c2c-actions-platform/issues/2479 {% endcomment %}' - - '在热补丁升级过程中，一种潜在的行为导致服务不可用。{% comment %} https://github.com/github/enterprise2/pull/24055 {% endcomment %}' - - '连接到活动副本的用户在连接到实时 Websocket 时出错。{% comment %} https://github.com/github/enterprise2/pull/24079, https://github.com/github/enterprise2/pull/24058 {% endcomment %}' - - '未正确应用部分日志转发 SSL 证书。{% comment %} https://github.com/github/enterprise2/pull/24114, https://github.com/github/enterprise2/pull/23981 {% endcomment %}' - - '发送电子邮件通知给已经从团队或组织中移除的已停用用户。{% comment %} https://github.com/github/github/pull/162973, https://github.com/github/github/pull/162742 {% endcomment %}' - - '组织和企业之间应用 SSH 证书的方式不一致。{% comment %} https://github.com/github/github/pull/163423, https://github.com/github/github/pull/159538, https://github.com/github/authentication/issues/115 {% endcomment %}' - - '当帐户因使用不正确的密码而受到速率限制时，可能被锁定长达 24 小时。{% comment %} https://github.com/github/github/pull/163433, https://github.com/github/github/pull/162938, https://github.com/github/github-ds/pull/51 {% endcomment %}' - - '在具有许多引用的存储库上进行拉取请求同步可能导致工作进程队列落后。{% comment %} https://github.com/github/github/pull/163573, https://github.com/github/github/pull/163142 {% endcomment %}' - - '在尝试访问特定页面后，当使用本地用户名和密码（内置身份验证）登录时，用户将进入到主页，而不是其预期页面。{% comment %} https://github.com/github/github/pull/163782, https://github.com/github/github/pull/163579, https://github.com/github/github/pull/154117, https://github.com/github/ecosystem-apps/issues/1076 {% endcomment %}' - - '对于使用内部 SAML 标识提供者的内置身份验证的 GHES 实例，没有关联电子邮件地址的用户无法从 Web 界面创建提交。{% comment %} https://github.com/github/github/pull/164009, https://github.com/github/github/pull/163530, https://github.com/github/github/issues/163524 {% 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 %}' - - '问题若是包含同一存储库中文件路径长于 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 deleted file mode 100644 index 7a16711fe3..0000000000 --- a/translations/zh-CN/data/release-notes/enterprise-server/2-22/6.yml +++ /dev/null @@ -1,18 +0,0 @@ -date: '2020-12-17' -sections: - security_fixes: - - '**低：**高 CPU 使用可能被特殊构建的 SVN 桥请求触发，导致 SVN 桥服务上的拒绝服务 (DoS)。{% comment %} https://github.com/github/slumlord/pull/1022, https://github.com/github/slumlord/pull/1017 {% endcomment %}' - - '包已更新到最新的安全版本。{% comment %} https://github.com/github/enterprise2/pull/24353, https://github.com/github/enterprise2/pull/23866 {% endcomment %}' - bugs: - - '对某些文件资源（如 zip 存档或原始文件）的请求可能会进入重定向循环。{% comment %} https://github.com/github/enterprise2/pull/24193, https://github.com/github/enterprise2/pull/24075 {% endcomment %}' - - '超时可能会阻止某些问题和拉取请求搜索提供完整的搜索结果。{% comment %} https://github.com/github/github/pull/164155, https://github.com/github/github/pull/163845 {% endcomment %}' - - '小屏幕上带有非字母字符的自定义选项卡未正确呈现。{% comment %} https://github.com/github/github/pull/164310, https://github.com/github/github/pull/164159 {% endcomment %}' - - '当将内容推送到启用 Git LFS 的仓库时，基本行为导致失败。{% comment %} https://github.com/github/github/pull/164663, https://github.com/github/github/pull/150179 {% endcomment %}' - - '在某些罕见情况下，通过 Web 界面访问时，问题可能会导致 500 错误。{% comment %} https://github.com/github/github/pull/165298, https://github.com/github/github/pull/159674 {% 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 %}' - - '问题若是包含同一存储库中文件路径长于 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/7.yml b/translations/zh-CN/data/release-notes/enterprise-server/2-22/7.yml deleted file mode 100644 index 094ce031ed..0000000000 --- a/translations/zh-CN/data/release-notes/enterprise-server/2-22/7.yml +++ /dev/null @@ -1,57 +0,0 @@ -date: '2021-03-02' -sections: - security_fixes: - - '**HIGH:** An improper access control vulnerability was identified in GitHub Enterprise Server that allowed authenticated users of the instance to gain write access to unauthorized repositories via specifically crafted pull requests and REST API requests. An attacker would need to be able to fork the targeted repository, a setting that is disabled by default for organization owned private repositories. Branch protections such as required pull request reviews or status checks would prevent unauthorized commits from being merged without further review or validation. This vulnerability has been assigned CVE-2021-22861. This issue was reported via the [GitHub Bug Bounty Program](https://bounty.github.com).' - - '**HIGH:** An improper access control vulnerability was identified in the GitHub Enterprise Server GraphQL API that allowed authenticated users of the instance to modify the maintainer collaboration permission of a pull request without proper authorization. By exploiting this vulnerability, an attacker would be able to gain access to head branches of pull requests opened on repositories of which they are a maintainer. Forking is disabled by default for organization owned private repositories and would prevent this vulnerability. Additionally, branch protections such as required pull request reviews or status checks would prevent unauthorized commits from being merged without further review or validation. This vulnerability has been assigned CVE-2021-22863. This issue was reported via the [GitHub Bug Bounty Program](https://bounty.github.com).' - - '**HIGH:** A remote code execution vulnerability was identified in GitHub Enterprise Server that could be exploited when building a GitHub Pages site. User-controlled configuration of the underlying parsers used by GitHub Pages were not sufficiently restricted and made it possible to execute commands on the GitHub Enterprise Server instance. To exploit this vulnerability, an attacker would need permission to create and build a GitHub Pages site on the GitHub Enterprise Server instance. This vulnerability has been assigned CVE-2020-10519 and was reported via the [GitHub Bug Bounty Program](https://bounty.github.com).' - - '**MEDIUM:** GitHub Tokens from GitHub Pages builds could end up in logs.' - - '**LOW:** A specially crafted request to the SVN bridge could trigger a long wait before failure resulting in Denial of Service (DoS).' - - 'Packages have been updated to the latest security versions.' - bugs: - - 'The load-balancer health checks in some cases could cause the babeld logs to fill up with errors about the PROXY protocol.' - - 'An informational message was unintentionally logged as an error during GitHub Enterprise Backup Utilities snapshots, which resulted in unnecessary emails being sent when backups were scheduled by cron jobs that listen for output to stderr.' - - 'While restoring a large backup, exception logging related to Redis memory exhaustion could cause the restore to fail due to a full disk.' - - 'When first setting up a new instance, if you selected "Configure as Replica" you would be unable to start replication.' - - 'When GitHub Actions was enabled, disabling maintenance mode in the management console failed.' - - 'When editing a wiki page a user could experience a 500 error when clicking the Save button.' - - 'An S/MIME signed commit using a certificate with multiple names in the subject alternative name would incorrectly show as "Unverified" in the commit badge.' - - 'Suspended user was sent emails when added to a team.' - - 'User saw 500 error when executing git operations on an instance configured with LDAP authentication.' - - 'The `remove_org_member_package_access` background job was visible in the management console and would continually increase.' - - 'When a repository had a large number of manifests an error `You have reached the maximum number of allowed manifest files (20) for this repository.` was shown on the Insights -> Dependency graph tab. For more information, see [Visualization limits](https://docs.github.com/en/github/managing-security-vulnerabilities/troubleshooting-the-detection-of-vulnerable-dependencies#are-there-limits-which-affect-the-dependency-graph-data).' - - 'When uploading a new license file with a different number of seats from the previous license file, the seat difference was not correctly represented in the enterprise account Settings -> License page.' - - 'The "Prevent repository admins from changing anonymous Git read access" checkbox available in the enterprise account settings could not be successfully enabled or disabled.' - - 'When a GitHub Pages build failed, the email notification contained an incorrect link for support location.' - - 'During a leap year, the user was getting a 404 response when trying to view Contribution activity on a Monday.' - changes: - - 'Added support for [AWS EC2 r5b instance types](https://aws.amazon.com/about-aws/whats-new/2020/12/introducing-new-amazon-ec2-r5b-instances-featuring-60-gbps-of-ebs-bandwidth-and-260K-iops/).' - - 'Adjusted background queue prioritization to more evenly distribute jobs.' - known_issues: - - 'On a freshly set up GitHub Enterprise 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.' - - | - Users may experience assets such as avatars not loading, or a failure to push/pull code. This may be caused by a PID mismatch in the `haproxy-cluster-proxy` service. To determine if you have an affected instance: - - **Single instance** - - 1. Run this in the [administrative shell](https://docs.github.com/en/enterprise-server/admin/configuration/accessing-the-administrative-shell-ssh) (SSH): - - ``` - if [ $(cat /var/run/haproxy-cluster-proxy.pid) -ne $(systemctl show --property MainPID --value haproxy-cluster-proxy) ]; then echo 'Main PID of haproxy-cluster-proxy does not match /var/run/haproxy-cluster-proxy.pid'; fi - ``` - - 2. If it shows that there is a mismatch, reboot the instance. - - **Cluster or High Availability configuration** - - 1. Run this in the [administrative shell](https://docs.github.com/en/enterprise-server/admin/configuration/accessing-the-administrative-shell-ssh) (SSH): - - ``` - ghe-cluster-each -- 'if [ $(cat /var/run/haproxy-cluster-proxy.pid) -ne $(systemctl show --property MainPID --value haproxy-cluster-proxy) ]; then echo 'Main PID of haproxy-cluster-proxy does not match /var/run/haproxy-cluster-proxy.pid'; fi' - ``` - - 2. If it shows one or more nodes are affected, reboot the affected nodes. - - 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. diff --git a/translations/zh-CN/data/release-notes/enterprise-server/2-22/8.yml b/translations/zh-CN/data/release-notes/enterprise-server/2-22/8.yml deleted file mode 100644 index cee7e07523..0000000000 --- a/translations/zh-CN/data/release-notes/enterprise-server/2-22/8.yml +++ /dev/null @@ -1,37 +0,0 @@ -date: '2021-03-16' -sections: - security_fixes: - - Packages have been updated to the latest security versions. - bugs: - - Systemd journal logs were duplicated in multiple places. - - A site admin could get a 500 error page while trying to view issues referenced from private repositories. - - Importing of repository archives from GitHub Enterprise Server that are missing repository files would fail with an error. - known_issues: - - On a freshly set up GitHub Enterprise 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. - - | - Users may experience assets such as avatars not loading, or a failure to push/pull code. This may be caused by a PID mismatch in the `haproxy-cluster-proxy` service. To determine if you have an affected instance: - - **Single instance** - - 1. Run this in the [administrative shell](https://docs.github.com/en/enterprise-server/admin/configuration/accessing-the-administrative-shell-ssh) (SSH): - - ``` - if [ $(cat /var/run/haproxy-cluster-proxy.pid) -ne $(systemctl show --property MainPID --value haproxy-cluster-proxy) ]; then echo 'Main PID of haproxy-cluster-proxy does not match /var/run/haproxy-cluster-proxy.pid'; fi - ``` - - 2. If it shows that there is a mismatch, reboot the instance. - - **Cluster or High Availability configuration** - - 1. Run this in the [administrative shell](https://docs.github.com/en/enterprise-server/admin/configuration/accessing-the-administrative-shell-ssh) (SSH): - - ``` - ghe-cluster-each -- 'if [ $(cat /var/run/haproxy-cluster-proxy.pid) -ne $(systemctl show --property MainPID --value haproxy-cluster-proxy) ]; then echo 'Main PID of haproxy-cluster-proxy does not match /var/run/haproxy-cluster-proxy.pid'; fi' - ``` - - 2. If it shows one or more nodes are affected, reboot the affected nodes. - - 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. diff --git a/translations/zh-CN/data/release-notes/enterprise-server/2-22/9.yml b/translations/zh-CN/data/release-notes/enterprise-server/2-22/9.yml deleted file mode 100644 index a7186ca8df..0000000000 --- a/translations/zh-CN/data/release-notes/enterprise-server/2-22/9.yml +++ /dev/null @@ -1,33 +0,0 @@ -date: '2021-03-23' -intro: Downloads have been disabled due to a major bug affecting multiple customers. A fix will be available in the next patch. -sections: - security_fixes: - - '**HIGH:** A remote code execution vulnerability was identified in GitHub Enterprise Server that could be exploited when building a GitHub Pages site. User-controlled configuration options used by GitHub Pages were not sufficiently restricted and made it possible to override environment variables leading to code execution on the GitHub Enterprise Server instance. To exploit this vulnerability, an attacker would need permission to create and build a GitHub Pages site on the GitHub Enterprise Server instance. This vulnerability affected all versions of GitHub Enterprise Server prior to 3.0.3 and was fixed in 3.0.3, 2.22.9, and 2.21.17. This vulnerability was reported via the GitHub Bug Bounty program and has been assigned CVE-2021-22864.' - - Packages have been updated to the latest security versions. - bugs: - - Running `ghe-cluster-config-init` could cause a cluster to become inoperable. - - Systemd could lose track of HAProxy's PID. - - The mysql-failover warning was displayed indefinitely after a successful failover. - - The `ghe-cluster-config-init` run was not fully accounting for the exit code of background jobs leading to improper handling of preflight checks. - - A Security & Analysis link did not appear in the left-side navigation on the Settings page for repositories. - - After disabling GitHub Packages, some organization pages would return an HTTP 500 error response. - changes: - - Improves reliability of nomad services by implementing the same restart policy introduced in GitHub Enterprise Server 3.0. - - Use a relative number for consul and nomad `bootstrap_expect` allowing for a cluster to bootstrap even if a handful of nodes are down. - - Logs will rotate based on size in addition to time. - - Added kafka-lite to the `ghe-cluster-status` command. - known_issues: - - On a freshly set up GitHub Enterprise 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. - - | - Log rotation may fail to signal services to transition to new log files, leading to older log files continuing to be used, and eventual root disk space exhaustion. - To remedy and/or prevent this issue, run the following commands in the [administrative shell](https://docs.github.com/en/enterprise-server/admin/configuration/accessing-the-administrative-shell-ssh) (SSH), or contact [GitHub Enterprise Support](https://support.github.com/contact) for assistance: - - ``` - printf "PATH=/usr/local/sbin:/usr/local/bin:/usr/local/share/enterprise:/usr/sbin:/usr/bin:/sbin:/bin\n29,59 * * * * root /usr/sbin/logrotate /etc/logrotate.conf\n" | sudo sponge /etc/cron.d/logrotate - sudo /usr/sbin/logrotate -f /etc/logrotate.conf - ``` - - '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.' 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 deleted file mode 100644 index f6bc03f21e..0000000000 --- a/translations/zh-CN/data/release-notes/enterprise-server/3-0/0-rc1.yml +++ /dev/null @@ -1,25 +0,0 @@ -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)”。" -sections: - bugs: - - 已更改几个日志文件的格式，包括为不同的日志类型添加了一个 PID。此更改不会影响 GitHub Enterprise Support 使用支持包来解决问题的方法。 - - 对 Web 挂钩配置 API 的 PATCH 请求不再清除 Web 挂钩机密。 - known_issues: - - "在新建的没有任何用户的 {% data variables.product.prodname_ghe_server %} 上，攻击者可以创建第一个管理员用户。" - - 候选发布版 1 不支持群集模式。 - - 在升级期间不会维护自定义防火墙规则。 - - "Git LFS 跟踪的文件[通过 Web 界面上传](https://github.blog/2016-02-18-upload-files-to-your-repositories/)被错误地直接添加到存储库。" - - 对 GitHub Connect 启用“用户可以搜索 GitHub.com”后，专用和内部存储库中的问题不包括在 GitHub.com 搜索结果中。 - - 在尝试设置 Actions 未成功后，如果禁用 Actions，你将无法创建第一个用户，也无法使用设备 - - 未保存“必要消息已查看”审核日志事件 - - '第一次设置时必须在副本上运行 `ghe-config-apply`，然后才可运行 `ghe-repl-setup` 以开始复制。' - - 备份工具可能会触发向管理员发送不必要的电子邮件 - - 在“组织成员”视图页面中显示不正确的 Packages 设置 - - 删除作为企业所有者的自己后，你将被重定向到 404 页面。操作成功。 - - '`ghe-config-apply` 偶尔失败，并出现“错误: 等待 nomad 作业应用失败”，直到 Nomad 作业队列被清除。此问题目前需要以管理员身份删除 `/etc/nomad-jobs/queue`。' - - 在配置多个副本节点时，副本的状态可能会错误同步。 - - 尝试将 3.0 备份还原到新实例的客户不应预先配置实例，因为它可能导致用户登录状态不佳。建议恢复到全新的未配置实例。 - - GitHub Enterprise Server 3.0 候选发布版尚未在 Azure 市场中提供。要在过渡环境中测试候选发布版，请启动 2.21 或 2.22 实例，然后在下载页面上使用 Azure 升级软件包进行。 - - 映像和升级包下载大小已增加。Internet 连接速度较慢的客户可能会发现下载软件包需要更长的时间。 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 deleted file mode 100644 index d3e33bd456..0000000000 --- a/translations/zh-CN/data/release-notes/enterprise-server/3-0/0-rc2.yml +++ /dev/null @@ -1,24 +0,0 @@ -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)”。" -sections: - bugs: - - heading: 修复候选发布 1 中的已知问题 - notes: - - 如果在尝试设置 GitHub Actions 失败后禁用 GitHub Actions，则无法创建第一个用户，也无法使用该设备。 - - 未保存“必要消息已查看”审核日志事件。 - - '初次设置时，需要在副本上运行 `ghe-config-apply`，然后才可运行 `ghe-repl-setup` 以开始复制。' - - 删除作为企业所有者的自己将返回 404。 - - heading: 其他问题的修复 - notes: - - 迁移和升级到 3.0.0 的问题已修复。 - - 备份实用程序版本控制现在适用于候选发布版本。 - - 生成支持包导致业务流程协调程序日志中出现错误。 - - 大型还原可能会导致 Redis 运行内存不足。 - - 现在，使用任何身份验证方法都可以看到管理控制台中启用 GitHub Actions 的复选框。 - - 仅在配置了所需存储时才可启用 GitHub Actions。 - - '如果未配置 MSSQL 复制，`ghe-repl-status` 可能会失败而不出现提示。' - - known_issues: - - 候选发布 1 的已知问题仍然适用，不包括列出的 Bug 修复。 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 deleted file mode 100644 index 36d3d58fab..0000000000 --- a/translations/zh-CN/data/release-notes/enterprise-server/3-0/0.yml +++ /dev/null @@ -1,160 +0,0 @@ -date: '2021-02-16' -intro: The minimum infrastructure requirements have increased for {% data variables.product.prodname_ghe_server %} 3.0+. For more information, see "[About minimum requirements for GitHub Enterprise Server 3.0 and later](/admin/enterprise-management/upgrading-github-enterprise-server#about-minimum-requirements-for-github-enterprise-server-30-and-later)." -sections: - security_fixes: - - '**HIGH:** A remote code execution vulnerability was identified in {% data variables.product.prodname_ghe_server %} that could be exploited when building a {% data variables.product.prodname_pages %} site. User-controlled configuration of the underlying parsers used by {% data variables.product.prodname_pages %} were not sufficiently restricted and made it possible to execute commands on the {% data variables.product.prodname_ghe_server %} instance. To exploit this vulnerability, an attacker would need permission to create and build a {% data variables.product.prodname_pages %} site on the {% data variables.product.prodname_ghe_server %} instance. This vulnerability has been assigned CVE-2020-10519 and was reported via the [GitHub Bug Bounty Program](https://bounty.github.com).' - features: - - heading: GitHub Actions - notes: - - | - [{% data variables.product.prodname_actions %}](https://github.com/features/actions) is now generally available on {% data variables.product.prodname_ghe_server %} 3.0+. Build, test, and deploy your code from {% data variables.product.prodname_dotcom %}. Submit code reviews, branch management, and issue triaging work the way you want. - - This release includes several improvements from the beta of {% data variables.product.prodname_actions %} on {% data variables.product.prodname_ghe_server %}: - - - Enterprise, organization, and repository admins can create security policies for access to {% data variables.product.prodname_actions %} on {% data variables.product.prodname_dotcom_the_website %}. - - Enterprise, organization, and repository admins can allow public repositories to use self-hosted runners. - - Enterprise, organization, and repository admins can now allow workflows to [run on pull requests raised from forks of private repositories](/enterprise-server@3.0/github/setting-up-and-managing-organizations-and-teams/disabling-or-limiting-github-actions-for-your-organization#enabling-workflows-for-private-repository-forks). - - The `workflow_run` event is [now supported](/enterprise-server@3.0/actions/reference/events-that-trigger-workflows#workflow_run) - - Users now have the ability to [disable workflows and enable them at a later date](/enterprise-server@3.0/actions/managing-workflow-runs/disabling-and-enabling-a-workflow). - - Workflow logs have been enhanced for a [better user experience](/enterprise-server@3.0/actions/managing-workflow-runs/using-workflow-run-logs). - - Users can now use private images in container jobs and services. - - The max retention days for [artifacts and logs can now be customized](/enterprise-server@3.0/github/setting-up-and-managing-your-enterprise/configuring-the-retention-period-for-github-actions-artifacts-and-logs-in-your-enterprise-account). - - The runner group API now includes [labels](/enterprise-server@3.0/actions/hosting-your-own-runners/using-labels-with-self-hosted-runners). - - You can now create reusable actions using shell scripts with compose run steps. - - [Encrypted secrets for an organization](/enterprise-server@3.0/actions/reference/encrypted-secrets#creating-encrypted-secrets-for-an-organization) allows you to consolidate secrets across repositories. - - [Workflow templates for an organization](/enterprise-server@3.0/actions/learn-github-actions/sharing-workflows-with-your-organization) streamlines and promotes best practices and consistency across your organization. - - {% data variables.product.prodname_actions %} is not currently supported for enterprises using cluster configurations. - - - heading: GitHub Packages - notes: - - | - [{% data variables.product.prodname_registry %}](https://github.com/features/packages) is a package hosting service, natively integrated with GitHub APIs, Actions, and webhooks. Create an [end-to-end DevOps workflow](/enterprise/3.0/admin/packages/configuring-packages-support-for-your-enterprise) that includes your code, continuous integration, and deployment solutions. - - Supported storage back ends include AWS S3 and MinIO with support for Azure blob coming in a future release. Please note that the current Docker support will be replaced by a beta of the new GitHub Container Registry in the next release. Please review the [updated minimum requirements for your platform](/enterprise/3.0/admin/installation/setting-up-a-github-enterprise-server-instance) before you turn on {% data variables.product.prodname_registry %}. - - When publishing packages to NuGet, users can now use the `--api-key` option to pass their authentication token instead of writing it into a file. For more information, see [Configuring dotnet CLI for use with GitHub Packages](/enterprise-server@3.0/packages/guides/configuring-dotnet-cli-for-use-with-github-packages#publishing-a-package) - - {% data variables.product.prodname_registry %} is not currently supported for enterprises using cluster configurations. - - - heading: GitHub Mobile beta - notes: - - | - [{% data variables.product.prodname_mobile %}](https://github.com/features/) beta allows you to triage notifications and manage issues and pull requests from your device. You can be simultaneously signed into mobile with one user account on {% data variables.product.prodname_dotcom_the_website %} and one user account on {% data variables.product.prodname_ghe_server %}. - - {% data variables.product.prodname_mobile %} beta is now available for {% data variables.product.prodname_ghe_server %}. Sign in with our [Android](https://play.google.com/store/apps/details?id=com.github.android) and [iOS](https://apps.apple.com/app/github/id1477376905) apps to triage notifications and manage issues and pull requests on the go. Administrators can disable mobile support for their Enterprise using the management console or by running `ghe-config app.mobile.enabled false`. - - - heading: Advanced Security Secret Scanning beta - notes: - - | - [Secret Scanning beta](https://github.com/features/security) scans public and private repositories for committed credentials, finds secrets, and notifies the secret provider or admin the moment they are committed into a repository. - - Administrators using {% data variables.product.prodname_GH_advanced_security %} can [enable and configure](/enterprise-server@3.0/admin/configuration/configuring-secret-scanning-for-your-appliance) {% data variables.product.prodname_GH_advanced_security %} secret scanning. You can review the [updated minimum requirements for your platform](/enterprise/3.0/admin/installation/setting-up-a-github-enterprise-server-instance) before you turn on {% data variables.product.prodname_GH_advanced_security %} secret scanning. - - - heading: Advanced Security Code Scanning - notes: - - | - [GitHub Advanced Security code scanning](https://github.com/features/security) is now generally available on GitHub Enterprise Server. Organizations who have purchased Advanced Security can use this capability to do static analysis security testing against their code, and prevent vulnerabilities from making it to their production code using CodeQL, our semantic analysis engine. For more information, see "[Configuring code scanning on your appliance](/en/enterprise-server@3.0/admin/configuration/configuring-code-scanning-for-your-appliance#running-code-scanning-using-github-actions)" - - changes: - - heading: Administration Changes - notes: - - The webhook events delivery system has been rearchitected for higher throughput, faster deliveries, and fewer delayed messages. It also uses less CPU and memory in {% data variables.product.prodname_ghe_server %} 3.0+. - - Organization and Enterprise owners can now see when a team member has been promoted to or demoted from being a team maintainer in the audit log through the new `team.promote_maintainer` and `team.demote_maintainer` audit log events. For more information, see "[Audited actions](/enterprise-server@3.0/admin/user-management/audited-actions)." - - Repository maintainers with existing {% data variables.product.prodname_pages %} sites can [easily update their prior default branch name](/enterprise-server@3.0/github/working-with-github-pages/about-github-pages#publishing-sources-for-github-pages-sites). - - Additional hardware resources are required to run {% data variables.product.prodname_ghe_server %} with any of Actions, Packages or Advanced Security enabled. For more information on the minimum required resources for each supported platform, see "[Setting up a {% data variables.product.prodname_ghe_server %} instance](/enterprise-server@3.0/admin/installation/setting-up-a-github-enterprise-server-instance)." - - Administrators can now [publish a message](/enterprise-server@3.0/admin/user-management/customizing-user-messages-for-your-enterprise), which all users must accept. This can help to onboard new users and surface other organization-specific information and policies. - - - heading: Security Changes - notes: - - Organization owners can now disable publication of {% data variables.product.prodname_pages %} sites from repositories in the organization. Disabling {% data variables.product.prodname_pages %} for the organization will prevent members from creating new Pages sites but will not unpublish existing sites. For more information, see "[Disabling publication of {% data variables.product.prodname_pages %} sites for your organization](/enterprise-server@3.0/github/setting-up-and-managing-organizations-and-teams/disabling-publication-of-github-pages-sites-for-your-organization)." - - A datacenter must be explicitly defined on all nodes before enabling an active replica. - - All usage of SSH fingerprints has been switched to use SHA256 fingerprints as they are used with OpenSSH since version 6.8 as well. This applies to the web interface and also the API where fingerprints are returned such as in GraphQL. The fingerprints follow the OpenSSH format. - - SHA-1 and SHA-256 signature headers (two headers) are sent on webhooks. - - - heading: Developer Changes - notes: - - Majority of the services running in {% data variables.product.prodname_ghe_server %} 3.0+ are now on containers which internally enables GitHub to iterate fast and ship high quality releases - - The webhook events delivery system has been rearchitected for higher throughput, faster deliveries, and fewer delayed messages. - - - heading: API Changes - notes: - - Administrators can now configure and manage the site-wide announcement banner via the REST API. For more information, see the endpoints for "[GitHub Enterprise administration](/enterprise-server@3.0/rest/reference/enterprise-admin#annoucements)." - - A new API endpoint enables the exchange of a user to server token for a user to server token scoped to specific repositories. For more information, see "[Apps](/enterprise-server@3.0/rest/reference/apps#create-a-scoped-access-token)" in the {% data variables.product.prodname_dotcom %} REST API documentation. - - - 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).' diff --git a/translations/zh-CN/data/release-notes/enterprise-server/3-0/1.yml b/translations/zh-CN/data/release-notes/enterprise-server/3-0/1.yml deleted file mode 100644 index b298260e62..0000000000 --- a/translations/zh-CN/data/release-notes/enterprise-server/3-0/1.yml +++ /dev/null @@ -1,71 +0,0 @@ -date: '2021-03-02' -intro: The minimum infrastructure requirements have increased for {% data variables.product.prodname_ghe_server %} 3.0+. For more information, see "[About minimum requirements for GitHub Enterprise Server 3.0 and later](/admin/enterprise-management/upgrading-github-enterprise-server#about-minimum-requirements-for-github-enterprise-server-30-and-later)." -sections: - security_fixes: - - '**HIGH:** An improper access control vulnerability was identified in GitHub Enterprise Server that allowed authenticated users of the instance to gain write access to unauthorized repositories via specifically crafted pull requests and REST API requests. An attacker would need to be able to fork the targeted repository, a setting that is disabled by default for organization owned private repositories. Branch protections such as required pull request reviews or status checks would prevent unauthorized commits from being merged without further review or validation. This vulnerability has been assigned CVE-2021-22861. This issue was reported via the [GitHub Bug Bounty Program](https://bounty.github.com).' - - '**HIGH:** An improper access control vulnerability was identified in the GitHub Enterprise Server GraphQL API that allowed authenticated users of the instance to modify the maintainer collaboration permission of a pull request without proper authorization. By exploiting this vulnerability, an attacker would be able to gain access to head branches of pull requests opened on repositories of which they are a maintainer. Forking is disabled by default for organization owned private repositories and would prevent this vulnerability. Additionally, branch protections such as required pull request reviews or status checks would prevent unauthorized commits from being merged without further review or validation. This vulnerability has been assigned CVE-2021-22863. This issue was reported via the [GitHub Bug Bounty Program](https://bounty.github.com).' - - '**HIGH:** An improper access control vulnerability was identified in GitHub Enterprise Server that allowed an authenticated user with the ability to fork a repository to disclose Actions secrets for the parent repository of the fork. This vulnerability existed due to a flaw that allowed the base reference of a pull request to be updated to point to an arbitrary SHA or another pull request outside of the fork repository. By establishing this incorrect reference in a PR, the restrictions that limit the Actions secrets sent a workflow from forks could be bypassed. This vulnerability affected GitHub Enterprise Server versions 3.0.0, 3.0.0.rc2, and 3.0.0.rc1 and has been assigned CVE-2021-22862. This vulnerability was reported via the GitHub Bug Bounty program.' - - '**MEDIUM:** GitHub Tokens from GitHub Pages builds could end up in logs.' - - 'Packages have been updated to the latest security versions.' - bugs: - - 'The load-balancer health checks in some cases could cause the babeld logs to fill up with errors about the PROXY protocol.' - - 'The HTTP headers were not compliant with HTTP RFC standards in specific responses like 304 status for archives.' - - 'On instances that host Python repositories with the Dependency Graph feature enabled, the instance could become unresponsive due to the root disk filling with error logs.' - - 'An informational message was unintentionally logged as an error during GitHub Enterprise Backup Utilities snapshots, which resulted in unnecessary emails being sent when backups were scheduled by cron jobs that listen for output to stderr.' - - 'On VMWare ESX 6.7 the initial configuration could hang while creating host keys which left the instance inaccessible via SSH.' - - 'When GitHub Actions was enabled, disabling maintenance mode in the management console failed.' - - 'The Package creation setting was shown on the organization member settings page, though this feature is not yet available.' - - 'While enabling secret scanning on the Security & Analysis page the dialog incorrectly mentions private repositories.' - - 'When editing a wiki page a user could experience a 500 error when clicking the Save button.' - - 'An S/MIME signed commit using a certificate with multiple names in the subject alternative name would incorrectly show as "Unverified" in the commit badge.' - - 'User saw 500 error when executing git operations on an instance configured with LDAP authentication.' - - 'Suspended user was sent emails when added to a team.' - - 'When a repository had a large number of manifests an error `You have reached the maximum number of allowed manifest files (20) for this repository.` was shown on the Insights -> Dependency graph tab. For more information, see [Visualization limits](https://docs.github.com/en/github/managing-security-vulnerabilities/troubleshooting-the-detection-of-vulnerable-dependencies#are-there-limits-which-affect-the-dependency-graph-data).' - - 'Fixes users being shown the option to set up the Code Scanning CodeQL Action even if Actions was not enabled for their repository.' - - 'The "Prevent repository admins from changing anonymous Git read access" checkbox available in the enterprise account settings could not be successfully enabled or disabled.' - - 'The modal used to display a mandatory message contained no vertical scrollbar, meaning longer messages could not be viewed in full.' - - 'Redis would sometimes fail to start after a hard reboot or application crash.' - - '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.' - changes: - - 'Satisfy requests concurrently when multiple users are downloading the same archive, resulting in improved performance.' - known_issues: - - 'On a freshly set up GitHub Enterprise 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.' - - '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 [GitHub Enterprise Support](https://support.github.com/contact).' - - '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 `yarn.lock` Javascript manifest files, resulting in HTTP 500 errors in logs.' - - '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.' - - | - Users may experience assets such as avatars not loading, or a failure to push/pull code. This may be caused by a PID mismatch in the `haproxy-cluster-proxy` service. To determine if you have an affected instance: - - **Single instance** - - 1. Run this in the [administrative shell](https://docs.github.com/en/enterprise-server/admin/configuration/accessing-the-administrative-shell-ssh) (SSH): - - ``` - if [ $(cat /var/run/haproxy-cluster-proxy.pid) -ne $(systemctl show --property MainPID --value haproxy-cluster-proxy) ]; then echo 'Main PID of haproxy-cluster-proxy does not match /var/run/haproxy-cluster-proxy.pid'; fi - ``` - - 2. If it shows that there is a mismatch, reboot the instance. - - **Cluster or High Availability configuration** - - 1. Run this in the [administrative shell](https://docs.github.com/en/enterprise-server/admin/configuration/accessing-the-administrative-shell-ssh) (SSH): - - ``` - ghe-cluster-each -- 'if [ $(cat /var/run/haproxy-cluster-proxy.pid) -ne $(systemctl show --property MainPID --value haproxy-cluster-proxy) ]; then echo 'Main PID of haproxy-cluster-proxy does not match /var/run/haproxy-cluster-proxy.pid'; fi' - ``` - - 2. If it shows one or more nodes are affected, reboot the affected nodes. - - '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. 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 deleted file mode 100644 index 1d7b2535a6..0000000000 --- a/translations/zh-CN/data/release-notes/enterprise-server/3-0/10.yml +++ /dev/null @@ -1,19 +0,0 @@ -date: '2021-06-24' -sections: - security_fixes: - - 包已更新到最新的安全版本。 - bugs: - - 管理控制台中可能会积累大量 `gauge-dependency-graph-api-dispatch_dispatch` 指标。 - - sshd 服务有时无法从 Google Cloud Platform 上运行的实例启动。 - - 旧的升级文件将保留在用户磁盘上，有时会导致空间不足。 - - 日志轮换有时会中断后台作业。 - - '`gh-migrator` 显示其日志输出的路径不正确。' - - 如果导出存档包含来自不在存档中的团队的审查请求，则导出存档将无法导入。 - known_issues: - - 在新建的没有任何用户的 GitHub Enterprise Server 上，攻击者可以创建第一个管理员用户。 - - 自定义防火墙规则在升级过程中被删除。 - - "[通过 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 deleted file mode 100644 index 7abc22b1f8..0000000000 --- a/translations/zh-CN/data/release-notes/enterprise-server/3-0/11.yml +++ /dev/null @@ -1,26 +0,0 @@ -date: '2021-07-14' -sections: - security_fixes: - - '**高：**在 GitHub Enterprise Server 中发现了一个在构建 GitHub Pages 站点时可以利用的路径遍历漏洞。GitHub Pages 使用的用户控制配置选项没有受到足够的限制，因此可以读取 GitHub Enterprise Server 实例上的文件。要利用此漏洞，攻击者需要获得在 GitHub Enterprise Server 实例上创建和构建 GitHub Pages 站点的权限。此漏洞影响 3.1.3 之前的所有 GitHub Enterprise Server 版本，编号为 CVE-2021-22867。此漏洞通过 GitHub Bug 悬赏计划报告。' - - 包已更新到最新的安全版本。 - bugs: - - 未配置 SAML 到期日期变量。 - - 应用程序服务在配置应用期间的运行状况检查将失败，然后才能进入正常状态。 - - '如果启用了 HTTP 代理，则 `ghe-cluster-config-node-init` 会在群集设置期间失败。' - - 预接收挂钩可能会遇到错误“未能解析当前可执行文件的完整路径”，因为 `/proc` 未装载至容器上。 - - Collectd 在初始启动后不会解析转发目标主机名。 - - 如果其中部分仓库因受法律保护而无法被清除，则清除陈旧的已删除仓库的作业可能会失败。 - - 运行 `git nw-gc --pristine` 会导致错误。 - - 后台作业将排入 `spam` 队列，这些作业不会得到处理。 - - 当 PR 合并失败后重新尝试时，首选合并方法将被重置。 - - 在使用 LDAP 身份验证模式的实例的用户协调过程中，Git 推送可能导致 500 内部服务器错误。 - changes: - - 通过跳过未更改的 IP 允许防火墙规则，提高了配置应用效率，可在大型集群上节省大量时间。 - known_issues: - - 在没有任何用户的新建 GitHub Enterprise Server 上，攻击者可能创建第一个管理员用户。 - - 自定义防火墙规则在升级过程中被删除。 - - "[通过 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 deleted file mode 100644 index 83ed9e4d38..0000000000 --- a/translations/zh-CN/data/release-notes/enterprise-server/3-0/12.yml +++ /dev/null @@ -1,21 +0,0 @@ -date: '2021-07-27' -sections: - security_fixes: - - 包已更新到最新的安全版本。 - bugs: - - '自定义预接收挂钩可能会导致这样的错误：“错误：/data/user/repositories/0/nw/12/34/56/7890/network.git/objects 对象目录不存在，请查看 .git/objects/info/alternates”。' - - 对于使用 HTTP 代理的所有用户，不支持使用未经身份验证的 HTTP 代理来进行页面容器构建。 - - 如果未启用依赖项关系图，则每当用户访问存储库的 `/settings` 页时，都会记录大量 503 错误。 - - 仅当用户通过团队或通过协作者状态与存储库有关联，或使用 `?type=internal` 参数查询时，才会返回内部存储库。 - - 失败的后台作业有无限制的重试，这可能会导致大的队列深度。 - - 如果在未启用依赖项关系图但启用了内容分析的情况下尝试运行将漏洞与 GitHub.com 同步的计划作业，则会生成大量 503 错误。 - changes: - - "`babeld` 的日志现在包含一个用于 HTTP ref 广告请求的 `cmd` 字段，而不是仅在协商请求期间包含该字段。" - known_issues: - - "在新建的没有任何用户的 {% data variables.product.prodname_ghe_server %} 上，攻击者可以创建第一个管理员用户。" - - 自定义防火墙规则在升级过程中被删除。 - - "[通过 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 deleted file mode 100644 index dbc8a9831c..0000000000 --- a/translations/zh-CN/data/release-notes/enterprise-server/3-0/13.yml +++ /dev/null @@ -1,17 +0,0 @@ -date: '2021-08-10' -sections: - bugs: - - 如果在不运行定期计划备份的情况下启用 GitHub Actions，则 MSSQL 事务日志可能会无限增长，并且会占用设备数据磁盘上的所有可用空间，从而可能导致中断。 - - 对“存储库创建”组织设置所做更改的审核日志条目不准确。 - - "过多记录 `ActionController::UnknownFormat` 异常会导致不必要的磁盘使用。" - - "LDAP `group_dn` 值超过 255 个字符将导致记录错误：`Data truncated for column 'group_dn' at row 1`。" - changes: - - 滥用速率限制现在称为辅助速率限制，因为它们限制的行为并不总是滥用。 - known_issues: - - "在新建的没有任何用户的 {% data variables.product.prodname_ghe_server %} 上，攻击者可能创建第一个管理员用户。" - - 自定义防火墙规则在升级过程中被删除。 - - "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 deleted file mode 100644 index 152449a873..0000000000 --- a/translations/zh-CN/data/release-notes/enterprise-server/3-0/14.yml +++ /dev/null @@ -1,21 +0,0 @@ -date: '2021-08-24' -sections: - security_fixes: - - 包已更新到最新的安全版本。 - bugs: - - 将非常大的图像或动态 GIF 附加到图像或拉取请求将会失败。 - - 与自动更新相关的日志消息 (`Adding h/m/s random time.`) 被记录到系统日志中。 - - '使用 bash 子 shell 的自定义预接收挂钩将返回错误：`No such file or directory`。' - - 创建命名管道 (FIFO) 的自定义预接收挂钩会崩溃或挂起，从而导致超时错误。 - - 向审核日志高级搜索页面添加筛选器时，不会使用正确的 Facet 前缀和值来实时填充查询文本框。 - - "导致请求失败的内部 API 的 Git 挂钩返回异常 `undefined method body for \"success\":String (NoMethodError)`，而不是返回显式的 `nil`。" - - 删除集成时，可能还会删除不相关的 OAuth 应用程序或集成。 - - 添加包含表情符号字符的必填消息后，尝试查看或更改消息将返回 500 内部服务器错误。 - known_issues: - - "在新建的没有任何用户的 {% data variables.product.prodname_ghe_server %} 上，攻击者可以创建第一个管理员用户。" - - 将在升级过程中删除自定义防火墙规则。 - - "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 deleted file mode 100644 index 73505c6421..0000000000 --- a/translations/zh-CN/data/release-notes/enterprise-server/3-0/15.yml +++ /dev/null @@ -1,17 +0,0 @@ -date: '2021-09-07' -sections: - security_fixes: - - 包已更新到最新的安全版本。 - bugs: - - 如果未启动复制，则尝试通过使用 `ghe-repl-teardown` 为新添加的副本节点指定 UUID 来拆解该节点将失败，且不会报告错误。 - - GitHub Pages 生成将通过外部代理（如果配置了外部代理）进行传递。 - - 创建子进程的自定义预接收挂钩在其环境中缺少 `PATH` 变量，从而导致“无此类文件或目录”错误。 - - 如果启用了 `mysql-auto-failover`，则 MySQL 可在升级期间进行故障转移。 - known_issues: - - "在新建的没有任何用户的 {% data variables.product.prodname_ghe_server %} 上，攻击者可以创建第一个管理员用户。" - - 自定义防火墙规则在升级过程中被删除。 - - "[通过 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 deleted file mode 100644 index cf2c76bcb0..0000000000 --- a/translations/zh-CN/data/release-notes/enterprise-server/3-0/16.yml +++ /dev/null @@ -1,18 +0,0 @@ -date: '2021-09-24' -sections: - security_fixes: - - '**高：**在 {% data variables.product.prodname_ghe_server %} 中发现了一个在构建 {% data variables.product.prodname_pages %} 站点时可以利用的路径遍历漏洞。{% data variables.product.prodname_pages %} 使用的用户控制配置选项没有受到足够的限制，因此可以读取 {% data variables.product.prodname_ghe_server %} 实例上的文件。要利用此漏洞，攻击者需要获得在 {% data variables.product.prodname_ghe_server %} 实例上创建和构建 {% data variables.product.prodname_pages %} 站点的权限。此漏洞影响 3.1.8 之前的所有 {% data variables.product.prodname_ghe_server %} 版本，并在 3.1.8、3.0.16 和 2.22.22 中修复。这是 CVE-2021-22867 修复不完整的结果。此漏洞通过 GitHub Bug 悬赏计划报告，编号为 CVE-2021-22868。{% comment %} https://github.com/github/pages/pull/3360, https://github.com/github/pages/pull/3357 {% endcomment %}' - - '**中：**{% data variables.product.prodname_ghe_server %} 中的不正确访问控制漏洞允许工作流作业在其不应访问的自承载运行器组中执行。这会影响使用自承载运行器组进行访问控制的客户。由于请求期间的身份验证检查不正确，有权访问一个企业运行器组的存储库可以访问组织内的所有企业运行器组。这可能会导致代码被不正确的运行器组无意运行。此漏洞影响 3.0.0-3.0.15 以及 3.1.0-3.1.7 的所有 {% data variables.product.prodname_ghe_server %} 版本，并在 3.0.16 和 3.1.8 中修复。其编号为 CVE-2021-22869。{% comment %} https://github.com/github/enterprise2/pull/27003 {% endcomment %}' - bugs: - - '在维护模式期间，Resque 工作进程计数显示不正确。{% comment %} https://github.com/github/enterprise2/pull/26898, https://github.com/github/enterprise2/pull/26883 {% endcomment %}' - - '在群集模式下，分配的 memcached 内存可能为零。{% comment %} https://github.com/github/enterprise2/pull/26927, https://github.com/github/enterprise2/pull/26832 {% endcomment %}' - - '请修复 {% data variables.product.prodname_pages %} 构建，以便考虑设备的 NO_PROXY 设置。这仅与配置了 HTTP 代理的设备有关。（更新时间：2021-09-30）{% comment %} https://github.com/github/pages/pull/3360 {% endcomment %}' - - '即使不使用 `ghe-restore` 的 `--config` 选项，源实例的 GitHub Connect 配置也始终恢复到新实例。如果源实例和目标实例同时联机，这将导致与 GitHub Connect 连接和许可证同步发生冲突。该修复还需要将 backup-utils 更新到 3.2.0 或更高版本。[更新时间：2021-11-18]' - known_issues: - - "在新建的没有任何用户的 {% data variables.product.prodname_ghe_server %} 上，攻击者可以创建第一个管理员用户。" - - 自定义防火墙规则在升级过程中被删除。 - - "[通过 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 deleted file mode 100644 index ce84c24a99..0000000000 --- a/translations/zh-CN/data/release-notes/enterprise-server/3-0/17.yml +++ /dev/null @@ -1,25 +0,0 @@ -date: '2021-10-12' -sections: - security_fixes: - - '包已更新到最新的安全版本。{% comment %} https://github.com/github/enterprise2/pull/27034, https://github.com/github/enterprise2/pull/27010 {% endcomment %}' - bugs: - - '由于过于严格的虚拟内存或 CPU 时间限制，自定义预接收挂钩可能会失败。{% comment %} https://github.com/github/enterprise2/pull/26971, https://github.com/github/enterprise2/pull/26955 {% endcomment %}' - - '通过尝试使用 `ghe-cleanup-settings` 擦除所有现有配置设置，未能重启管理控制台服务。{% comment %} https://github.com/github/enterprise2/pull/26986, https://github.com/github/enterprise2/pull/26901 {% endcomment %}' - - '在通过 `ghe-repl-teardown` 拆解复制期间，Memcached 未能重启。{% comment %} https://github.com/github/enterprise2/pull/26992, https://github.com/github/enterprise2/pull/26983 {% endcomment %}' - - '在高负载期间，当上游服务未通过内部运行状况检查时，用户将收到 HTTP 503 状态代码。{% comment %} https://github.com/github/enterprise2/pull/27081, https://github.com/github/enterprise2/pull/26999 {% endcomment %}' - - '禁止预接收挂钩环境通过 Alpine 上的 BusyBox 调用 cat 命令。{% comment %} https://github.com/github/enterprise2/pull/27114, https://github.com/github/enterprise2/pull/27094 {% endcomment %}' - - '外部数据库密码以明文形式记录。{% comment %} https://github.com/github/enterprise2/pull/27172, https://github.com/github/enterprise2/pull/26413 {% endcomment %}' - - '运行 `ghe-config-apply` 时可能会显示错误的 `jq` 错误消息。{% comment %} https://github.com/github/enterprise2/pull/27203, https://github.com/github/enterprise2/pull/26784 {% endcomment %}' - - '从主群集数据中心故障转移到辅助群集数据中心成功，但随后故障转移回原始主群集数据中心时未能提升 Elasticsearch 索引。{% comment %} https://github.com/github/github/pull/193180, https://github.com/github/github/pull/192447 {% endcomment %}' - - '存储库自承载运行器的“站点管理员”页面返回 HTTP 500。{% comment %} https://github.com/github/github/pull/194205 {% endcomment %}' - - '在某些情况下，尝试查看“休眠用户”页面的 GitHub Enterprise 管理员会收到“502 网关错误”或“504 网关超时”响应。{% comment %} https://github.com/github/github/pull/194259, https://github.com/github/github/pull/193609 {% endcomment %}' - changes: - - '更有效地删除超出 Webhook 日志保留时段的 Webhook 日志。{% comment %} https://github.com/github/enterprise2/pull/27157 {% endcomment %}' - known_issues: - - "在没有任何用户的新建 {% data variables.product.prodname_ghe_server %} 上，攻击者可以创建第一个管理员用户。" - - 自定义防火墙规则在升级过程中被移除。 - - "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 deleted file mode 100644 index 2eb40f01e6..0000000000 --- a/translations/zh-CN/data/release-notes/enterprise-server/3-0/18.yml +++ /dev/null @@ -1,15 +0,0 @@ -date: '2021-10-28' -sections: - security_fixes: - - '多个已知弱 SSH 公钥已添加到拒绝列表中，无法再进行注册。此外，已知会生成弱 SSH 密钥的 GitKraken 版本（7.6.x、7.7.x 和 8.0.0）已被阻止注册新的公钥。' - - '包已更新到最新的安全版本。' - bugs: - - '拥有许多组织的用户无法使用应用程序的多个部分。' - known_issues: - - "在新建的没有任何用户的 {% data variables.product.prodname_ghe_server %} 上，攻击者可以创建第一个管理员用户。" - - 自定义防火墙规则在升级过程中被删除。 - - "[通过 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 deleted file mode 100644 index c474915c0c..0000000000 --- a/translations/zh-CN/data/release-notes/enterprise-server/3-0/19.yml +++ /dev/null @@ -1,23 +0,0 @@ -date: '2021-11-09' -sections: - security_fixes: - - "在 {% data variables.product.prodname_pages %} 中发现了一个在构建 {% data variables.product.prodname_ghe_server %} 时攻击者可利用来读取系统文件的路径遍历漏洞。要利用此漏洞，攻击者需要获得在 {% data variables.product.prodname_ghe_server %} 实例上创建和构建 {% data variables.product.prodname_pages %} 站点的权限。此漏洞影响 3.3 之前的所有 {% data variables.product.prodname_ghe_server %} 版本，并在 3.0.19、3.1.11 和 3.2.3 中修复。该漏洞通过 {% data variables.product.company_short %} Bug 悬赏计划报告，编号为 CVE-2021-22870。" - - 包已更新到最新的安全版本。 - bugs: - - "部分 Git 操作在升级 {% data variables.product.prodname_ghe_server %} 3.x 群集后失败，原因在于 HAProxy 配置。" - - 在群集模式下，Unicorn 工作线程计数可能会设置错误。 - - 在群集模式下，Resqued 工作线程计数可能会设置错误。 - - 如果 Ubuntu 简单防火墙 (UFW) 状态为非活动状态，则客户端无法在日志中清楚地看到它。 - - 某些页面和与 Git 相关的后台作业可能无法在具有某些群集配置的群集模式下运行。 - - "企业审核日志页面不会显示 {% data variables.product.prodname_secret_scanning %} 的审核事件。" - - '在查看文件时，不会警告用户有潜在危险的双向 unicode 字符。有关详细信息，请参阅 {% data variables.product.prodname_blog %} 中的“[有关双向 Unicode 文本的警告](https://github.co/hiddenchars)”。' - - Hookshot Go 发送了 Collectd 无法处理的分布类型指标，这导致解析错误激增。 - - "公共存储库显示来自 {% data variables.product.prodname_secret_scanning %} 的意外结果，类型为“未知令牌”。" - known_issues: - - "在新建的没有任何用户的 {% data variables.product.prodname_ghe_server %} 上，攻击者可以创建第一个管理员用户。" - - 自定义防火墙规则在升级过程中被删除。 - - "[通过 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/2.yml b/translations/zh-CN/data/release-notes/enterprise-server/3-0/2.yml deleted file mode 100644 index c50eeb2eb9..0000000000 --- a/translations/zh-CN/data/release-notes/enterprise-server/3-0/2.yml +++ /dev/null @@ -1,57 +0,0 @@ -date: '2021-03-16' -intro: The minimum infrastructure requirements have increased for {% data variables.product.prodname_ghe_server %} 3.0+. For more information, see "[About minimum requirements for GitHub Enterprise Server 3.0 and later](/admin/enterprise-management/upgrading-github-enterprise-server#about-minimum-requirements-for-github-enterprise-server-30-and-later)." -sections: - security_fixes: - - Packages have been updated to the latest security versions. - bugs: - - During a backup an error "Warning: One or more storage objects were not found on the source appliance." was occurring when attempting to clean up purgeable storage objects. - - Dependency graph failed to parse `yarn.lock` JavaScript manifest files, resulting in HTTP 500 errors in logs. - - Disabling GitHub Actions would sometimes fail. - - Custom pre-receive hooks weren't allowed to write to `/tmp`, preventing some scripts from running correctly. - - Systemd journal logs were duplicated in multiple places. - - A timezone set on GitHub Enterprise 11.10.x or earlier was reset to UTC time after upgrading to 3.0 which caused timestamps to shift in some instances. - - Clicking "Publish your first package" in the packages sidebar on a repository would lead to an empty page. - - A site admin could get a 500 error page while trying to view issues referenced from private repositories. - - After disabling GitHub Packages, some organization pages would return an HTTP 500 error response. - - Importing of repository archives from GitHub Enterprise Server that are missing repository files would fail with an error. - - Repository [deploy keys](/developers/overview/managing-deploy-keys) were unable to be used with repositories containing LFS objects. - - In the packages sidebar of a repository, the Docker icon was gray and a tool tip displayed "This service is deprecated". - - Webhooks configured with a content type of `application/x-www-form-urlencoded` did not receive query parameters in the POST request body. - - Users could dismiss a mandatory message without checking all checkboxes. - - In some cases after upgrading from a 2.22.X instance, the web interface assets were missing and the page would not render correctly. - - Running `ghe-config-apply` could time out with `Failure waiting for nomad jobs to apply` due to `'job' stanza not found`. - known_issues: - - On a freshly set up GitHub Enterprise 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. - - 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 [GitHub Enterprise Support](https://support.github.com/contact). - - 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. - - 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. - - | - Users may experience assets such as avatars not loading, or a failure to push/pull code. This may be caused by a PID mismatch in the `haproxy-cluster-proxy` service. To determine if you have an affected instance: - - **Single instance** - - 1. Run this in the [administrative shell](https://docs.github.com/en/enterprise-server/admin/configuration/accessing-the-administrative-shell-ssh) (SSH): - - ``` - if [ $(cat /var/run/haproxy-cluster-proxy.pid) -ne $(systemctl show --property MainPID --value haproxy-cluster-proxy) ]; then echo 'Main PID of haproxy-cluster-proxy does not match /var/run/haproxy-cluster-proxy.pid'; fi - ``` - - 2. If it shows that there is a mismatch, reboot the instance. - - **Cluster or High Availability configuration** - - 1. Run this in the [administrative shell](https://docs.github.com/en/enterprise-server/admin/configuration/accessing-the-administrative-shell-ssh) (SSH): - - ``` - ghe-cluster-each -- 'if [ $(cat /var/run/haproxy-cluster-proxy.pid) -ne $(systemctl show --property MainPID --value haproxy-cluster-proxy) ]; then echo 'Main PID of haproxy-cluster-proxy does not match /var/run/haproxy-cluster-proxy.pid'; fi' - ``` - - 2. If it shows one or more nodes are affected, reboot the affected nodes. - - 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. 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 deleted file mode 100644 index 1cc77e86b1..0000000000 --- a/translations/zh-CN/data/release-notes/enterprise-server/3-0/20.yml +++ /dev/null @@ -1,21 +0,0 @@ -date: '2021-11-23' -sections: - security_fixes: - - 包已更新到最新的安全版本。 - bugs: - - 如果未定义 `PATH`，预接收挂钩会失败。 - - '如果曾将实例配置为副本，运行 `ghe-repl-setup` 会返回错误：“无法创建目录 /data/user/elasticsearch：文件已存在”。' - - 在大型群集环境中，某部分前端节点可能无法使用身份验证后端。 - - 在 GHES 群集的后端节点上，一些关键服务可能不可用。 - changes: - - 在使用 `ghe-cluster-suport-bundle` 创建群集支持包时，现在会默认关闭额外一层的外部 `gzip` 压缩。使用 `ghe-cluster-suport-bundle -c` 命令行选项可以选择应用此外部压缩。 - - 我们在管理控制台添加了额外的文本，以提醒用户移动应用的数据收集，目的是改善体验。 - - "{% data variables.product.prodname_github_connect %} 数据连接记录现在会列出已启用的 {% data variables.product.prodname_github_connect %} 功能。[更新时间：2021-12-09]" - known_issues: - - "在新建的没有任何用户的 {% data variables.product.prodname_ghe_server %} 上，攻击者可以创建第一个管理员用户。" - - 自定义防火墙规则在升级过程中被删除。 - - "[通过 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/21.yml b/translations/zh-CN/data/release-notes/enterprise-server/3-0/21.yml deleted file mode 100644 index 7300a26391..0000000000 --- a/translations/zh-CN/data/release-notes/enterprise-server/3-0/21.yml +++ /dev/null @@ -1,22 +0,0 @@ -date: '2021-12-07' -sections: - security_fixes: - - 支持包可以包含敏感文件，前提是它们满足一组特定条件。 - - "在 GitHub Enterprise Server 中发现了一个 UI 虚假陈述漏洞，该漏洞允许在 GitHub 应用程序的用户授权 Web 流期间授予比在审批期间向用户显示的更多权限。此漏洞影响 GitHub Enterprise Server 3.3 之前的所有版本，已在 3.2.5、3.1.13 和 3.0.21 中修复。此漏洞通过 GitHub Bug 赏金计划报告，编号为 [CVE-2021-41598](https://www.cve.org/CVERecord?id=CVE-2021-41598)。" - - "在 GitHub Enterprise Server 中发现了一个在构建 GitHub Pages 站点时可以利用的远程代码执行漏洞。此漏洞影响 GitHub Enterprise Server 3.3 之前的所有版本，已在 3.0.21、3.1.13 和 3.2.5 中修复。此漏洞通过 GitHub Bug 赏金计划报告，编号为 [CVE-2021-41599](https://www.cve.org/CVERecord?id=CVE-2021-41599)。更新时间：2022 年 2 月 17 日。" - bugs: - - 由于 `/data/user/tmp/pages` 中存在权限问题，运行 `ghe-config-apply` 有时可能会失败。 - - 管理控制台中的错误配置导致了调度错误。 - - Docker 会在日志轮换后保持日志文件打开。 - - GraphQL 请求未在预接收挂钩环境中设置 GITHUB_USER_IP 变量。 - changes: - - 阐明了文档中对 Actions 路径样式的解释。 - - 更新支持联系 URL 以使用当前支持站点 support.github.com。 - known_issues: - - "在新建的没有任何用户的 {% data variables.product.prodname_ghe_server %} 上，攻击者可以创建第一个管理员用户。" - - 将在升级过程中删除自定义防火墙规则。 - - "Git LFS 跟踪的 [通过 Web 界面上传的](https://github.com/blog/2105-upload-files-to-your-repositories) 文件被错误地直接添加到存储库。" - - 如果问题包含指向同一存储库中 Blob 的永久链接，且 Blob 的文件路径长度超过 255 个字符，则无法关闭问题。 - - 对 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 deleted file mode 100644 index c2407b0ed8..0000000000 --- a/translations/zh-CN/data/release-notes/enterprise-server/3-0/22.yml +++ /dev/null @@ -1,13 +0,0 @@ -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/)。' - - '**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 跟踪文件被错误地直接添加到存储库。" - - 问题若是包含同一存储库中文件路径长于 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 deleted file mode 100644 index 0ea086a5a9..0000000000 --- a/translations/zh-CN/data/release-notes/enterprise-server/3-0/23.yml +++ /dev/null @@ -1,19 +0,0 @@ -date: '2022-01-18' -sections: - security_fixes: - - '包已更新到最新的安全版本。在这些更新中，Log4j 已更新至版本 2.17.1。注意：以前在 3.3.1、3.2.6、3.1.14 和 3.0.22 中发布的缓解措施已经足够解决这些 GitHub Enterprise Server 版本中 CVE-2021-44228、CVE-2021-45046、CVE-2021-45105 和 CVE-2021-44832 的影响。' - - 清理生成的支持包中的更多机密 - - 包已更新到最新的安全版本。 - bugs: - - 由于 `/data/user/tmp/pages` 中存在权限问题，`ghe-config-apply` 的运行有时可能会失败。 - - 在低分辨率的浏览器中滚动，可能无法找到管理控制台中的保存按钮。 - - Collectd 版本升级后，IOPS 和存储流量监视图未更新。 - - 一些与 Webhook 相关的作业可能会产生大量的日志。 - known_issues: - - "在新建的没有任何用户的 {% data variables.product.prodname_ghe_server %} 上，攻击者可以创建第一个管理员用户。" - - 自定义防火墙规则在升级过程中被删除。 - - "[通过 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 deleted file mode 100644 index 6023a57e4c..0000000000 --- a/translations/zh-CN/data/release-notes/enterprise-server/3-0/24.yml +++ /dev/null @@ -1,20 +0,0 @@ -date: '2022-02-01' -sections: - security_fixes: - - 包已更新到最新的安全版本。 - bugs: - - 在 MySQL 机密轮换后，页面将不可用，直到手动重启 `nginx`。 - - 使用 ISO 8601 日期设置维护计划时，由于时区未转换为 UTC，因此实际计划时间将不匹配。 - - 使用 `ghe-cluster-each` 安装热补丁后，版本号将无法正确更新。 - - 有关 `cloud-config.service` 的虚假错误消息将输出到控制台。 - - 使用 CAS 身份验证并启用“重新激活暂停的用户”选项时，暂停的用户不会自动重新激活。 - changes: - - GitHub Connect 数据连接记录现在包括活动和休眠用户数量计数以及配置的休眠期。 - known_issues: - - "在新建的没有任何用户的 {% data variables.product.prodname_ghe_server %} 上，攻击者可以创建第一个管理员用户。" - - 自定义防火墙规则在升级过程中被删除。 - - "[通过 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/25.yml b/translations/zh-CN/data/release-notes/enterprise-server/3-0/25.yml deleted file mode 100644 index 1a2d52c290..0000000000 --- a/translations/zh-CN/data/release-notes/enterprise-server/3-0/25.yml +++ /dev/null @@ -1,12 +0,0 @@ -date: '2022-02-17' -sections: - security_fixes: - - 包已更新到最新的安全版本。 - known_issues: - - "在新建的没有任何用户的 {% data variables.product.prodname_ghe_server %} 实例上，攻击者可以创建第一个管理员用户。" - - 自定义防火墙规则在升级过程中被删除。 - - "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/3.yml b/translations/zh-CN/data/release-notes/enterprise-server/3-0/3.yml deleted file mode 100644 index 468174853d..0000000000 --- a/translations/zh-CN/data/release-notes/enterprise-server/3-0/3.yml +++ /dev/null @@ -1,42 +0,0 @@ -date: '2021-03-23' -intro: Downloads have been disabled due to a major bug affecting multiple customers. A fix will be available in the next patch. -sections: - security_fixes: - - '**HIGH:** A remote code execution vulnerability was identified in GitHub Enterprise Server that could be exploited when building a GitHub Pages site. User-controlled configuration options used by GitHub Pages were not sufficiently restricted and made it possible to override environment variables leading to code execution on the GitHub Enterprise Server instance. To exploit this vulnerability, an attacker would need permission to create and build a GitHub Pages site on the GitHub Enterprise Server instance. This vulnerability affected all versions of GitHub Enterprise Server prior to 3.0.3 and was fixed in 3.0.3, 2.22.9, and 2.21.17. This vulnerability was reported via the GitHub Bug Bounty program and has been assigned CVE-2021-22864.' - - Packages have been updated to the latest security versions. - bugs: - - Running `ghe-cluster-config-init` could cause a cluster to become inoperable. - - Resolving merge conflicts in the GUI would fail when custom pre-receive hooks are configured on the repository. - - '`launch-deployer` and `launch-receiver` were logging at DEBUG level and filling logs with unnecessary information.' - - Systemd could lose track of HAProxy's PID. - - When Actions was configured to use S3 storage, the logs for an action would sometimes fail to load. - - The mysql-failover warning was displayed indefinitely after a successful failover. - - The `ghe-cluster-config-init` run was not fully accounting for the exit code of background jobs leading to improper handling of preflight checks. - - When enabling GitHub Actions, initialization could fail silently. - - When vulnerability alerting is enabled, upgrades to the 3.0 series would fail. - - Jobs related to Codespaces were being enqueued leading to an accumulation of unprocessed jobs. - changes: - - Use a relative number for consul and nomad `bootstrap_expect` allowing for a cluster to bootstrap even if a handful of nodes are down. - - Logs will rotate based on size in addition to time. - - Added kafka-lite to the `ghe-cluster-status` command. - known_issues: - - On a freshly set up GitHub Enterprise 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. - - 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 [GitHub Enterprise Support](https://support.github.com/contact). - - 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. - - 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. - - | - Log rotation may fail to signal services to transition to new log files, leading to older log files continuing to be used, and eventual root disk space exhaustion. - To remedy and/or prevent this issue, run the following commands in the [administrative shell](https://docs.github.com/en/enterprise-server/admin/configuration/accessing-the-administrative-shell-ssh) (SSH), or contact [GitHub Enterprise Support](https://support.github.com/) for assistance: - - ``` - printf "PATH=/usr/local/sbin:/usr/local/bin:/usr/local/share/enterprise:/usr/sbin:/usr/bin:/sbin:/bin\n29,59 * * * * root /usr/sbin/logrotate /etc/logrotate.conf\n" | sudo sponge /etc/cron.d/logrotate - sudo /usr/sbin/logrotate -f /etc/logrotate.conf - ``` - - 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. 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 deleted file mode 100644 index 15a89606aa..0000000000 --- a/translations/zh-CN/data/release-notes/enterprise-server/3-0/4.yml +++ /dev/null @@ -1,27 +0,0 @@ -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)报告。" - - 包已更新到最新的安全版本。 - bugs: - - 启用维护模式时，尽管某些服务应该运行但不应列出，它们仍被列为“活动进程”。 - - 在启用 GitHub Actions 的情况下从 2.22.x 升级到 3.0.x 后，自承载运行器版本没有更新，也没有自承载更新。 - - 旧 GitHub Pages 版本未进行清理，导致磁盘使用量增加。 - - '`memcached` 未在活动的副本上运行。' - - 在启用 GitHub Actions 的情况下更新文件权限时升级失败。 - - 某些默认采用 UTC 时间的服务未使用在 GitHub Enterprise 11.10.x 或更早版本上设置的时区。 - - 服务未在日志轮换过程中转换到新的日志文件，导致磁盘使用量增加。 - - "`ghe-saml-mapping-csv` 命令行实用工具生成了一条警告消息。" - - 内部存储库搜索结果上的标签显示为“专用”而不是“内部”。 - known_issues: - - 在没有任何用户的新建 GitHub Enterprise Server 上，攻击者可以创建第一个管理员用户。 - - 在升级期间不会维护自定义防火墙规则。 - - "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 渲染可能会失败。 - - Web UI 中的 reStructuredText (RST) 渲染可能会失败，并显示原始 RST 标记文本。 - - 在合并拉取请求后删除分支时，尽管分支删除成功，但仍会出现错误消息。 - - "当副本节点在高可用性配置下脱机时，{% 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/5.yml b/translations/zh-CN/data/release-notes/enterprise-server/3-0/5.yml deleted file mode 100644 index e7537e5b79..0000000000 --- a/translations/zh-CN/data/release-notes/enterprise-server/3-0/5.yml +++ /dev/null @@ -1,28 +0,0 @@ -date: '2021-04-14' -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: - - 包已更新到最新的安全版本。 - bugs: - - 有些日志未包含在日志转发配置中。 - - '警告消息 `jq: error (at :0): Cannot index number with string "settings"` 可能在副本升级期间出现。' - - 由于 MySQL 副本无法连接到主数据库，因此将备份连续还原到群集可能会失败。 - - 使用自定义 CA 证书时页面未发布。 - - 与子域相关的包未显示在“测试域设置”提示中以进行子域隔离。 - - 通过 Webhook 发送的 `X-GitHub-Enterprise-Host` 标头包含一个随机字符串，而不是发送 HTTP POST 有效负载的 GitHub Enterprise Server 实例的主机名。 - - 如果先前启用了 GitHub Actions，但在升级之前被禁用，则从 2.22.x 升级到 3.0.x 将会失败。 - - 访问 `/settings/email` 页面会存储状态，在退出登录并重新登录时可能导致错误的重定向。 - - 在问题评论中通过提及功能直接提及团队时，GitHub 集成应用程序无法通知团队。 - - reStructuredText (RST) 渲染在 Web UI 中可能失败，反而显示原始 RST 标记文本。 - - 如果未完全启用依赖项关系图，则不会将密码扫描警报的电子邮件通知发送给授权用户。 - - 当 ghe-migrator 遇到导入错误时，它有时会中止整个进程，但日志中没有包含足够的上下文。 - - 具有非 ASCII 字符的 Jupyter 笔记本可能无法渲染。 - known_issues: - - 在新建的没有任何用户的 GitHub Enterprise Server 上，攻击者可以创建第一个管理员用户。 - - 在升级期间不会维护自定义防火墙规则。 - - "[通过 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/6.yml b/translations/zh-CN/data/release-notes/enterprise-server/3-0/6.yml deleted file mode 100644 index 32d81e475c..0000000000 --- a/translations/zh-CN/data/release-notes/enterprise-server/3-0/6.yml +++ /dev/null @@ -1,31 +0,0 @@ -date: '2021-04-28' -sections: - security_fixes: - - 包已更新到最新的安全版本。 - bugs: - - 在升级过程中，进程将在“清理 Nomad 作业”之后无限期暂停。 - - '`ghe-cluster-failover` 失败，出现错误消息 `Trilogy::Error: trilogy_connect`。' - - '`ghe-cluster-status-mysql` 将有关故障转移的警告显示为错误。' - - 在 MySQL 副本上运行的安装脚本可能已导致数据库故障转移期间不必要的数据库重新播种。 - - 升级未包括正确安装最新版本的 Actions 运行器。 - - '`github-env` 配置可能导致僵停进程。' - - '由于不必要地调用 `rake db:migrate`，`config-apply` 可能需要更长的时间。' - - Orchestrator 可能已故障转移到 MySQL 副本，当主数据库无法连接时，它无法在播种阶段从主数据库复制。 - - 出现错误的组织或项目阻止了迁移，无法排除。 - - 对于所属组织超过 50 个的用户禁用了“创建存储库”按钮。 - - 删除分支会临时闪烁一条错误消息，指示删除成功时出错。 - - "`rms-packages` 索引显示在站点管理员仪表板中。" - - 由于表单上未显示正确的可见性选项，因此组织所有者无法创建内部存储库。 - - 在操作启动工作流程配置错误的情况下，存储库操作选项卡显示 500。 - - 由于选择了最完整的磁盘而不是空节点，存储主机超过三个的客户无法恢复到其灾难恢复群集。 - - 应用热补丁后，代码扫描后端服务无法可靠启动。 - changes: - - 默认情况下，预运行检查允许所有 AWS 实例类型。 - known_issues: - - 在新建的没有任何用户的 GitHub Enterprise Server 上，攻击者可以创建第一个管理员用户。 - - 在升级期间不会维护自定义防火墙规则。 - - "[通过 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/7.yml b/translations/zh-CN/data/release-notes/enterprise-server/3-0/7.yml deleted file mode 100644 index 13f84f66fd..0000000000 --- a/translations/zh-CN/data/release-notes/enterprise-server/3-0/7.yml +++ /dev/null @@ -1,24 +0,0 @@ -date: '2021-05-13' -sections: - security_fixes: - - "**高：**在GitHub Enterprise Server 中发现 UI 表述错误漏洞，在审批阶段，该问题会导致在 GitHub 应用用户授权 Web 流中授予超过 UI 显示的权限。要利用这个漏洞，攻击者需要在实例上创建 GitHub 应用，并让用户通过 Web 身份验证流对应用程序进行授权。所有被授予的权限将在第一次授权时正确显示，但在某些情况下，如果用户在 GitHub 应用已配置额外的用户级别权限后重新访问授权流，这些额外的权限可能不会显示，这样会导致授予可能超过用户初衷的权限。此漏洞影响 GitHub Enterprise Server 3.0.x 到 3.0.7 版本以及 2.22.x 到 2.22.13 版本。3.0.7 和 2.22.13 版本中修复了该问题。该漏洞编号为 CVE-2021-22866，是通过[GitHub Bug 悬赏计划](https://bounty.github.com/) 报告的。" - - 包已更新到最新的安全版本。 - bugs: - - 操作或包存储配置中包含的引号可能会导致错误。 - - 由于文件大小或打开文件数量的限制过于严格，自定义预接收挂钩可能会失败。 - - 在配置应用阶段可以启用 Orchestrator 自动故障转移。 - - 具有仓库维护员权限的用户会收到电子邮件验证警告，而不是在仓库 Pages 设置页面上构建成功的页面。 - - 通配符规则的代码所有者将被错误地添加到代码所有者徽章的所有者列表中，即使该路径优先使用较新的规则。 - - OpenAPI 文档引用了无效的标头。 - - 在创建或编辑预接收挂钩时，用户界面中的竞争情况意味着在选择仓库后，仓库中的文件有时不会填充到文件下拉列表中。 - changes: - - 添加了 HAProxy 重载时配置更改的日志记录。 - - 添加了仓库创建的日志记录。 - known_issues: - - 在新建的没有任何用户的 GitHub Enterprise Server 上，攻击者可以创建第一个管理员用户。 - - 在升级期间不会维护自定义防火墙规则。 - - "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/8.yml b/translations/zh-CN/data/release-notes/enterprise-server/3-0/8.yml deleted file mode 100644 index 52ca8b7cac..0000000000 --- a/translations/zh-CN/data/release-notes/enterprise-server/3-0/8.yml +++ /dev/null @@ -1,27 +0,0 @@ -date: '2021-05-25' -sections: - security_fixes: - - '**中：**在某些情况下，从团队或组织中删除的用户可以保留对已打开现有拉取请求的分支的写入权限。' - - 包已更新到最新的安全版本。 - bugs: - - 在初始安装过程的“配置 Actions 和 Packages”页面，当管理员点击“测试域设置”按钮时，测试未完成。 - - "运行 `ghe-btop` 失败，显示错误“找不到 'babeld' 容器”。" - - 升级后，由于内部和外部超时值不匹配，用户遇到服务不可用问题。 - - MSSQL 中的正常复制延迟会生成警告。 - - 管理控制台上的 GitHub Enterprise Clustering Guide 链接不正确。 - - 管理员使用“创建白名单条目”按钮添加的 IP 地址仍可能被锁定。 - - 对“依赖项关系图”和“Dependabot 警报”功能的引用显示在未启用它们的存储库中。 - - 对 `/hooks` 端点的HTTP POST 请求可能会因为 `hookID` 设置不正确而失败，并出现 401 响应。 - - "`build-server`进程未能清理进程，将它们留在 `defunct` 状态。" - - '`spokesd` 创建了过多的日志条目，包括“修复位置已跳过”短语。' - changes: - - 检查超过 4 个月的注释是否将存档。 - known_issues: - - "使用 `ghe-repo /` 通过管理 shell 访问存储库时将被挂起。解决方法是使用 `ghe-repo / -c \"bash -i\"`，直到下一个版本提供修复为止。" - - 在新建的没有任何用户的 GitHub Enterprise Server 上，攻击者可能创建第一个管理员用户。 - - 在升级期间不会维护自定义防火墙规则。 - - "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 deleted file mode 100644 index 4a27a0b12c..0000000000 --- a/translations/zh-CN/data/release-notes/enterprise-server/3-0/9.yml +++ /dev/null @@ -1,24 +0,0 @@ -date: '2021-06-10' -sections: - security_fixes: - - 包已更新到最新的安全版本。 - bugs: - - 升级 Actions 时，如果实例无法通过其配置的主机名自行提出请求，升级可能会失败。 - - SVN 1.7 及以下客户端在使用 `svn co` 和 `svn export` 命令时出现错误。 - - 使用 `ghe-repo /` 通过管理 shell 访问存储库会挂起。 - - 升级后，由于服务重启过于频繁，用户在重度使用期间可用性降低。这可能是由于 nomad 配置和内部服务的超时不一致造成的。 - - 在某些情况下，设置 GitHub Actions 后运行 `ghe-repl-status` 会产生错误，并且 `ghe-actions-teardown` 会失败。 - - '`ghe-dbconsole` 在某些情况下会返回错误。' - - "从非 GitHub 源导入组织或存储库失败可能会生成 `undefined method '[]' for nil:NilClass` 错误。" - - 使用 SAML 身份验证时，如果 GitHub 配置文件名称不匹配管理控制台中映射到“全名”字段的属性值，GitHub 配置文件名称可能已无意中更改。 - changes: - - "`firstPatchedVersion` 字段现在可以在 GraphQL API 中的 `SecurityVulability` 对象上使用。" - - GraphQL API 用户可在 `PullRequest` 对象上查询公共字段 `closingIssuesReferences`。该字段检索将在合并相关拉取请求时自动关闭的问题。这种方法还将允许将来迁移这些数据，作为更高保真度迁移过程的一部分。 - known_issues: - - 在没有任何用户的新建 GitHub Enterprise Server 上，攻击者可能创建第一个管理员用户。 - - 自定义防火墙规则在升级过程中被删除。 - - "[通过 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-rc1.yml b/translations/zh-CN/data/release-notes/enterprise-server/3-1/0-rc1.yml deleted file mode 100644 index 520bfd612f..0000000000 --- a/translations/zh-CN/data/release-notes/enterprise-server/3-1/0-rc1.yml +++ /dev/null @@ -1,20 +0,0 @@ -date: '2021-05-06' -release_candidate: true -deprecated: true -intro: If {% data variables.location.product_location %} is running a release candidate build, you can't upgrade with a hotpatch. We recommend only running release candidates on test environments. -sections: - 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: - - 'A scheduled cleanup job can cause performance to degrade on an instance with a very large `check_annotations` table.' - changes: - - Check annotations older than 4 months will be archived. - - 'The `firstPatchedVersion` field is now available on `SecurityVulnerability` objects in the GraphQL API.' - known_issues: - - The GitHub Packages 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 GitHub Enterprise 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. 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 deleted file mode 100644 index 3b24968dd8..0000000000 --- a/translations/zh-CN/data/release-notes/enterprise-server/3-1/0.yml +++ /dev/null @@ -1,173 +0,0 @@ -date: '2021-06-03' -intro: For minimum infrastructure requirements, see "[About minimum requirements for {% data variables.product.prodname_ghe_server %} 3.0 and later](/admin/enterprise-management/upgrading-github-enterprise-server#about-minimum-requirements-for-github-enterprise-server-30-and-later)." -sections: - features: - - heading: GitHub Advanced Security Secret Scanning - notes: - - | - [Secret Scanning](https://github.com/features/security) is now generally available on {% data variables.product.prodname_ghe_server %} 3.1+. Scan public and private repositories for committed credentials, find secrets, and notify the secret provider or admin the moment they are committed into a repository. - - This release includes several improvements from the beta of Secret Scanning on {% data variables.product.prodname_ghe_server %}: - - - Expanded our [pattern coverage](/enterprise-server@3.1/code-security/secret-security/about-secret-scanning#about-secret-scanning-for-private-repositories) from 24 partners to 37 - - Added an [API](/rest/reference/secret-scanning) and [webhooks](/developers/webhooks-and-events/webhook-events-and-payloads#secret_scanning_alert) - - Added [notifications for commit authors](https://github.blog/changelog/2021-03-05-secret-scanning-notifications-for-commit-authors-on-private-repositories/) when they commit secrets - - Updated the index view to made it easy to triage secrets in bulk - - Reduced the false positive rate on many patterns - - Administrators using {% data variables.product.prodname_GH_advanced_security %} can [enable and configure](/enterprise-server@3.1/admin/configuration/configuring-secret-scanning-for-your-appliance) {% data variables.product.prodname_GH_advanced_security %} secret scanning. You can review the [updated minimum requirements for your platform](/enterprise-server@3.1/admin/installation/setting-up-a-github-enterprise-server-instance) before you turn on {% data variables.product.prodname_GH_advanced_security %} secret scanning. - - - heading: GitHub Advanced Security billing improvements - notes: - - | - This release includes several improvements to {% data variables.product.prodname_GH_advanced_security %} billing in {% data variables.product.prodname_ghe_server %}: - - - {% data variables.product.prodname_GH_advanced_security %} customers can now view their active committer count and the remaining number of unused committer seats on their organization or enterprise account’s Billing page. If Advanced Security is purchased for an enterprise, administrators can also view the active committer seats which are being used by other organizations within their enterprise. For more information, see "[About GitHub Advanced Security licensing](/enterprise-server@3.1/admin/advanced-security/about-licensing-for-github-advanced-security)" and "[Viewing your GitHub Advanced Security usage](/enterprise-server@3.1/admin/advanced-security/viewing-your-github-advanced-security-usage)." - - GitHub Advanced Security customers can now view their active committer count for any Advanced Security enabled repositories on their organization or enterprise account's Billing page. These changes help billing administrators track their usage against how many committer licenses they purchased. For more information see "[Managing security and analysis settings for your organization](/enterprise-server@3.1/organizations/keeping-your-organization-secure/managing-security-and-analysis-settings-for-your-organization)." - - - heading: Dependabot improvements - notes: - - | - This release includes improvements to Dependabot alerts in {% data variables.product.prodname_ghe_server %}: - - - Users with Dependabot alerts enabled can see which of their repositories are impacted by a given vulnerability by navigating to its entry in the [GitHub Advisory Database](https://github.com/advisories). This feature is available in public beta. For more information, see "[Viewing and updating vulnerable dependencies in your repository](/enterprise-server@3.1/code-security/supply-chain-security/viewing-and-updating-vulnerable-dependencies-in-your-repository)." - - When a vulnerability is added to GitHub Advisory Database, you will no longer receive [email and web notifications](https://github.com/notifications) for Dependabot alerts on low and moderate severity vulnerabilities. These alerts are still accessible from the repository's Security tab. For more information, see "[Viewing and updating vulnerable dependencies in your repository](/enterprise-server@3.1/code-security/supply-chain-security/viewing-and-updating-vulnerable-dependencies-in-your-repository)." - - You can now give people instructions on how to responsibly report security vulnerabilities in your project by adding a `SECURITY.md` file to your repository's `root`, `docs`, or `.github` folder. When someone creates an issue in your repository, they will see a link to your project's security policy. For more information, see "[Adding a security policy to your repository](/enterprise-server@3.1/code-security/getting-started/adding-a-security-policy-to-your-repository)." - - - heading: GitHub Actions Workflow Visualization beta - notes: - - | - {% data variables.product.prodname_actions %} can now generate a visual graph of your workflow on every run. With workflow visualization, you can: - - View and understand complex workflows - - Track progress of workflows in real-time - - Troubleshoot runs quickly by easily accessing logs and jobs metadata - - Monitor progress of deployment jobs and easily access deployment targets - - For more information, see "[Using the visualization graph](/actions/managing-workflow-runs/using-the-visualization-graph)." - - - heading: OAuth 2.0 Device Authorization Grant - notes: - - | - [OAuth 2.0 Device Authorization Grant](https://github.com/login/device) allows any CLI client or developer tool to authenticate using a secondary system with a browser. - - Administrators using [OAuth Apps](/developers/apps/authorizing-oauth-apps#device-flow) and [GitHub Apps](/developers/apps/authorizing-oauth-apps#device-flow) can enable and configure OAuth 2.0 Device Authorization Flow, in addition to the existing Web Application Flow. You can review the [updated minimum requirements for your platform](/enterprise-server@3.1/admin/installation/setting-up-a-github-enterprise-server-instance) before you enable OAuth 2.0 Device Authorization Flow. - - - heading: Pull request auto-merge - notes: - - | - With auto-merge, pull requests can be set to merge automatically when all merge requirements have been satisfied. This saves users from needing to constantly check the state of their pull requests just to merge them. Auto-merge can be enabled by a user with permission to merge and on pull requests that have unsatisfied merge requirements. For more information, see "[Automatically merging a pull request](/enterprise-server@3.1/github/collaborating-with-issues-and-pull-requests/automatically-merging-a-pull-request)." - - - heading: Custom notifications - notes: - - | - You can customize the types of notifications you want to receive from individual repositories. For more information, see "[Configuring notifications](/enterprise-server@3.1/github/managing-subscriptions-and-notifications-on-github/configuring-notifications#configuring-your-watch-settings-for-an-individual-repository)." - - - heading: GitHub Mobile filtering - notes: - - | - [{% data variables.product.prodname_mobile %}](https://github.com/mobile) filtering allows you to search for and find issues, pull requests, and discussions from your device. New metadata for issues and pull request list items allow you to filter by assignees, checks status, review states, and comment counts. - - {% data variables.product.prodname_mobile %} beta is available for {% data variables.product.prodname_ghe_server %}. Sign in with our [Android](https://play.google.com/store/apps/details?id=com.github.android) and [iOS](https://apps.apple.com/app/github/id1477376905) apps to triage notifications and manage issues and pull requests on the go. Administrators can disable mobile support for their Enterprise using the management console or by running `ghe-config app.mobile.enabled false`. For more information, see "[GitHub Mobile](/get-started/using-github/github-mobile)." - - changes: - - heading: Administration Changes - notes: - - By precomputing checksums, the amount of time a repository is under the lock has reduced dramatically, allowing more write operations to succeed immediately and improving monorepo performance. - - The latest release of the CodeQL CLI supports uploading analysis results to GitHub. This makes it easier to run code analysis for customers who wish to use CI/CD systems other than {% data variables.product.prodname_actions %}. Previously, such users had to use the separate CodeQL runner, which will continue to be available. For more information, see "[About CodeQL code scanning in your CI system](/enterprise-server@3.1/code-security/secure-coding/about-codeql-code-scanning-in-your-ci-system)." - - '{% data variables.product.prodname_actions %} now supports skipping `push` and `pull_request` workflows by looking for some common keywords in your commit message.' - - Check annotations older than four months will be archived. - - Scaling of worker allocation for background tasks has been revised. We recommend validating that the new defaults are appropriate for your workload. Custom background worker overrides should be unset in most cases. [Updated 2022-03-18] - - - heading: Security Changes - notes: - - Following feedback, display of Code Scanning results on a pull request without submitting with a pull request ID will remain supported. For more information, see "[Configuring code scanning](/enterprise-server@3.1/code-security/secure-coding/configuring-code-scanning#scanning-pull-requests)" and "[Configuring CodeQL code scanning in your CI system](/enterprise-server@3.1/code-security/secure-coding/configuring-codeql-code-scanning-in-your-ci-system#scanning-pull-requests). - - SARIF upload support increased to a maximum of 5000 results per upload. - - - heading: Developer Changes - notes: - - You can specify multiple callback URLs while configuring a GitHub App. This can be used in services with multiple domains or subdomains. GitHub will always deny authorization if the callback URL from the request is not in the authorization callback URL list. - - The GitHub App file permission has been updated to allow an app developer to specify up to 10 files for read-only or read-write access that their app can request access to. - - CodeQL now supports more [libraries and frameworks](https://codeql.github.com/docs/codeql-overview/supported-languages-and-frameworks/) for a variety of 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),[Java](https://github.com/github/codeql/tree/main/java), [Go](https://github.com/github/codeql-go/tree/main)). The CodeQL engine can now detect more sources of untrusted user data, which improves the quality and depth of the code scanning alerts. For more information, see "[About CodeQL](https://codeql.github.com/docs/codeql-overview/about-codeql/)." - - When configuring a GitHub App, the authorization callback URL is a required field. Now, we allow the developer to specify multiple callback URLs. This can be used in services with multiple domains or subdomains. GitHub will always deny authorization if the callback URL from the request is not in the authorization callback URL list. - - Delete an entire directory of files, including subdirectories, from your web browser. For more information, see "[Deleting a file or directory](/enterprise-server@3.1/github/managing-files-in-a-repository/deleting-files-in-a-repository#deleting-a-directory)." - - 'Include multiple words after the `#` in an issue, discussion, or pull request comment to further narrow your search.' - - 'When you’re writing an issue, pull request, or discussion comment the list syntax for bullets, numbers, and tasks autocompletes after you press `return` or `enter`.' - - - 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).' diff --git a/translations/zh-CN/data/release-notes/enterprise-server/3-1/1.yml b/translations/zh-CN/data/release-notes/enterprise-server/3-1/1.yml deleted file mode 100644 index 81341e76c4..0000000000 --- a/translations/zh-CN/data/release-notes/enterprise-server/3-1/1.yml +++ /dev/null @@ -1,30 +0,0 @@ -date: '2021-06-10' -sections: - security_fixes: - - Packages have been updated to the latest security versions. - bugs: - - SVN 1.7 and older clients showed an error when using the `svn co` and `svn export` commands. - - Accessing a repository through the administrative shell using `ghe-repo /` would hang. - - After upgrading, users experienced reduced availability during heavy usage, because services restarted too frequently. This would occur due to timeout mismatches between the nomad configuration and that of the internal services. - - In some instances, running `ghe-repl-status` after setting up GitHub Actions would produce an error and `ghe-actions-teardown` would fail. - - '`ghe-dbconsole` would return errors under some circumstances.' - - Import failures of organizations or repositories from non-GitHub sources could produce an `undefined method '[]' for nil:NilClass` error. - - GitHub profile names might have changed unintentionally when using SAML authentication, if the GitHub profile name did not match the value of the attribute mapped to the `Full name` field in the Management Console. - - Upgrading an instance that had previously ran a 2.13 release, but not a 2.14 release, resulted in a database migration error relating to the `AddRepositoryIdToCheckRuns` data transition. - changes: - - Users of the GraphQL API can query the public field `closingIssuesReferences` on the `PullRequest` object. This field retrieves issues that will be automatically closed when the related pull request is merged. This approach will also allow this data to be migrated in future, as part of a higher fidelity migration process. - known_issues: - - The {% data variables.product.prodname_registry %} npm registry no longer returns a time value in metadata responses. This was done to allow for substantial performance improvements. We continue to have all the data necessary to return a time value as part of the metadata response and will resume returning this value in the future once we have solved the existing performance issues. - - 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. - - | - 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. - - If {% data variables.product.prodname_actions %} is enabled for {% data variables.product.prodname_ghe_server %}, teardown of a replica node with `ghe-repl-teardown` will succeed, but may return `ERROR:Running migrations`. - - Resource limits that are specific to processing pre-receive hooks may cause some pre-receive hooks to fail. 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 deleted file mode 100644 index 0856cb8115..0000000000 --- a/translations/zh-CN/data/release-notes/enterprise-server/3-1/10.yml +++ /dev/null @@ -1,21 +0,0 @@ -date: '2021-10-28' -sections: - security_fixes: - - '明文密码可能会出现在某些日志文件中。' - - '多个已知弱 SSH 公钥已添加到拒绝列表中，无法再进行注册。此外，已知会生成弱 SSH 密钥的 GitKraken 版本（7.6.x、7.7.x 和 8.0.0）已被阻止注册新的公钥。' - - '包已更新到最新的安全版本。' - bugs: - - '如果业务流程协调程序运行不正常，企业服务器在群集模式下的还原可能会失败。' - - '拥有许多组织的用户无法使用应用程序的多个部分。' - - '修复了 https://docs.github.com 链接。' - changes: - - '具有多个引用的存储库的浏览和作业性能优化。' - known_issues: - - "{% 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)文件被错误地直接添加到存储库。" - - 如果问题包含指向同一存储库中文件路径长于 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/11.yml b/translations/zh-CN/data/release-notes/enterprise-server/3-1/11.yml deleted file mode 100644 index 50d70b18c8..0000000000 --- a/translations/zh-CN/data/release-notes/enterprise-server/3-1/11.yml +++ /dev/null @@ -1,28 +0,0 @@ -date: '2021-11-09' -sections: - security_fixes: - - "在 {% data variables.product.prodname_ghe_server %} 中发现了在构建 {% data variables.product.prodname_pages %} 时出现的路径遍历漏洞，攻击者可利用该漏洞读取系统文件。要利用此漏洞，攻击者需要获得在 {% data variables.product.prodname_ghe_server %} 实例上创建和构建 {% data variables.product.prodname_pages %} 站点的权限。此漏洞影响 3.3 之前的所有 {% data variables.product.prodname_ghe_server %} 版本，并在 3.0.19、3.1.11 和 3.2.3 中修复。该漏洞通过 {% data variables.product.company_short %} Bug 悬赏计划报告，编号为 CVE-2021-22870。" - - 包已更新到最新的安全版本。 - bugs: - - "部分 Git 操作在升级 {% data variables.product.prodname_ghe_server %} 3.x 群集后失败，原因在于 HAProxy 配置。" - - 在群集模式下，Unicorn 辅助角色计数可能会设置错误。 - - 在群集模式下，Resqued 辅助角色计数可能会设置错误。 - - 如果 Ubuntu Uncomplicated Firewall (UFW) 处于不活动状态，客户端可能无法在日志中清楚地看到它。 - - "当 LDAP 配置中存在 UTF8 字符时，从 {% data variables.product.prodname_ghe_server %} 2.x 到 3.x 的升级会失败。" - - 某些页面和与 Git 相关的后台作业可能无法在具有某些群集配置的群集模式下运行。 - - "创建新标记时，[推送](/developers/webhooks-and-events/webhooks/webhook-events-and-payloads#push) webhook 有效负载不显示正确的 `head_commit` 对象。现在，创建新标记时，推送 webhook 有效负载始终包括 `head_commit` 对象，其中包含新标签指向的提交数据。所以 `head_commit` 对象将始终包含有效负载 `after` 提交的提交数据。" - - "企业审核日志页面不会显示 {% data variables.product.prodname_secret_scanning %} 的审核事件。" - - 副本修复的作业超时时间不足。 - - '在查看文件时，不会警告用户有潜在危险的双向 unicode 字符。有关详细信息，请参阅 {% data variables.product.prodname_blog %} 中的“[有关双向 Unicode 文本的警告](https://github.co/hiddenchars)”。' - - Hookshot Go 发送了 Collectd 无法处理的分布类型指标，这导致解析错误激增。 - changes: - - 已添加 Kafka 配置改进。删除仓库时，现在会立即从存储帐户中删除包文件以释放空间。`DestroyDeletedPackageVersionsJob` 现在从存储帐户中删除过期包的包文件以及元数据记录。 - known_issues: - - "{% 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) 被错误地直接添加到仓库。" - - 如果议题包含文件路径长于 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/12.yml b/translations/zh-CN/data/release-notes/enterprise-server/3-1/12.yml deleted file mode 100644 index fea487a964..0000000000 --- a/translations/zh-CN/data/release-notes/enterprise-server/3-1/12.yml +++ /dev/null @@ -1,24 +0,0 @@ -date: '2021-11-23' -sections: - security_fixes: - - 包已更新到最新的安全版本。 - bugs: - - 如果已启用 GitHub Actions，运行 `ghe-repl-start` 或 `ghe-repl-status` 可能会在连接到数据库时返回错误。 - - 如果未定义 `PATH`，预接收挂钩会失败。 - - '如果曾将实例配置为副本，运行 `ghe-repl-setup` 会返回错误：“无法创建目录 /data/user/elasticsearch：文件已存在”。' - - '设置高可用性副本后，`ghe-repl-status` 在输出中包含错误：“命令中未关闭的意外操作”。' - - 在大型群集环境中，某部分前端节点可能无法使用身份验证后端。 - - 在 GHES 群集的后端节点上，一些关键服务可能不可用。 - changes: - - 在使用 `ghe-cluster-suport-bundle` 创建群集支持包时，现在会默认关闭额外一层的外部 `gzip` 压缩。使用 `ghe-cluster-suport-bundle -c` 命令行选项可以选择应用此外部压缩。 - - 我们在管理控制台添加了额外的文本，以提醒用户移动应用的数据收集，目的是改善体验。 - - "{% data variables.product.prodname_github_connect %} 数据连接记录现在会列出已启用的 {% data variables.product.prodname_github_connect %} 功能。[更新日期：2021 年 12 月 9 日]" - known_issues: - - "{% 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) 被错误地直接添加到仓库。" - - 如果议题包含文件路径长于 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 deleted file mode 100644 index b6b479d82a..0000000000 --- a/translations/zh-CN/data/release-notes/enterprise-server/3-1/13.yml +++ /dev/null @@ -1,23 +0,0 @@ -date: '2021-12-07' -sections: - security_fixes: - - 支持包可以包含敏感文件，前提是它们满足一组特定条件。 - - "在 GitHub Enterprise Server 中发现了一个 UI 虚假陈述漏洞，该漏洞允许在 GitHub 应用程序的用户授权 Web 流期间授予比在审批期间向用户显示的更多权限。此漏洞影响 GitHub Enterprise Server 3.3 之前的所有版本，已在 3.2.5、3.1.13 和 3.0.21 中修复。此漏洞通过 GitHub Bug 赏金计划报告，编号为 [CVE-2021-41598](https://www.cve.org/CVERecord?id=CVE-2021-41598)。" - - "在 GitHub Enterprise Server 中发现了一个在构建 GitHub Pages 站点时可以利用的远程代码执行漏洞。此漏洞影响 GitHub Enterprise Server 3.3 之前的所有版本，已在 3.0.21、3.1.13 和 3.2.5 中修复。此漏洞通过 GitHub Bug 赏金计划报告，编号为 [CVE-2021-41599](https://www.cve.org/CVERecord?id=CVE-2021-41599)。更新时间：2022 年 2 月 17 日" - bugs: - - 由于 `/data/user/tmp/pages` 中存在权限问题，运行 `ghe-config-apply` 有时可能会失败。 - - 管理控制台中的错误配置导致了调度错误。 - - Docker 会在日志轮换后保持日志文件打开。 - - GraphQL 请求未在预接收挂钩环境中设置 GITHUB_USER_IP 变量。 - changes: - - 阐明了文档中对 Actions 路径样式的解释。 - - 更新支持联系 URL 以使用当前支持站点 support.github.com。 - known_issues: - - "{% 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 跟踪文件被错误地直接添加到存储库。" - - 如果问题包含文件路径长于 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 deleted file mode 100644 index d820e279f0..0000000000 --- a/translations/zh-CN/data/release-notes/enterprise-server/3-1/14.yml +++ /dev/null @@ -1,14 +0,0 @@ -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/)。' - - '**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 注册表不再返回元数据响应的时间值。这样做是为了大幅改善性能。作为元数据响应的一部分，我们继续拥有返回时间值所需的所有数据，并将在我们解决现有性能问题后恢复返回这个值。" - - "在新建的没有任何用户的 {% data variables.product.prodname_ghe_server %} 上，攻击者可以创建第一个管理员用户。" - - 自定义防火墙规则在升级过程中被删除。 - - "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/15.yml b/translations/zh-CN/data/release-notes/enterprise-server/3-1/15.yml deleted file mode 100644 index 70c45870a6..0000000000 --- a/translations/zh-CN/data/release-notes/enterprise-server/3-1/15.yml +++ /dev/null @@ -1,21 +0,0 @@ -date: '2022-01-18' -sections: - security_fixes: - - '包已更新到最新的安全版本。在这些更新中，Log4j 已更新至版本 2.17.1。注意：以前在 3.3.1、3.2.6、3.1.14 和 3.0.22 中发布的缓解措施已经足够解决这些 GitHub Enterprise Server 版本中 CVE-2021-44228、CVE-2021-45046、CVE-2021-45105 和 CVE-2021-44832 的影响。' - - 清理生成的支持包中的更多机密 - - 包已更新到最新的安全版本。 - bugs: - - 由于 `/data/user/tmp/pages` 中存在权限问题，`ghe-config-apply` 的运行有时可能会失败。 - - 在低分辨率的浏览器中滚动，可能无法找到管理控制台中的保存按钮。 - - Collectd 版本升级后，IOPS 和存储流量监控图未更新。 - - 一些与 Webhook 相关的作业可能会产生大量的日志。 - - "`/repos` API返回给用户的仓库权限不会返回完整的列表。" - known_issues: - - "{% 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) 被错误地直接添加到仓库。" - - 如果议题包含文件路径长于 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/16.yml b/translations/zh-CN/data/release-notes/enterprise-server/3-1/16.yml deleted file mode 100644 index d69a0d05f4..0000000000 --- a/translations/zh-CN/data/release-notes/enterprise-server/3-1/16.yml +++ /dev/null @@ -1,24 +0,0 @@ -date: '2022-02-01' -sections: - security_fixes: - - 包已更新到最新的安全版本。 - bugs: - - 在 MySQL 机密轮换后，页面将不可用，直到手动重启 `nginx`。 - - 使用 ISO 8601 日期设置维护计划时，由于时区未转换为 UTC，因此实际计划时间将不匹配。 - - 有关 `cloud-config.service` 的虚假错误消息将输出到控制台。 - - 使用 `ghe-cluster-each` 安装热补丁后，版本号将无法正确更新。 - - Webhook 表清理作业可能同时运行，导致资源争用并且作业运行时间增加。 - - 使用 CAS 身份验证并启用“重新激活暂停的用户”选项时，暂停的用户不会自动重新激活。 - - 将基于电子邮件的通知限制为在经过验证或批准的域上具有电子邮件的用户的功能无法正常工作。 - - 多个文档链接导致“404 找不到”错误。 - changes: - - GitHub Connect 数据连接记录现在包括活动和休眠用户数量以及配置的休眠期的计数。 - known_issues: - - "{% 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 跟踪文件被错误地直接添加到存储库。" - - 问题若是包含同一存储库中文件路径长于 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 deleted file mode 100644 index 5f85dbc002..0000000000 --- a/translations/zh-CN/data/release-notes/enterprise-server/3-1/17.yml +++ /dev/null @@ -1,15 +0,0 @@ -date: '2022-02-17' -sections: - security_fixes: - - 包已更新到最新的安全版本。 - bugs: - - 修复从 memcached 获取超过 2^16 个密钥时的 SystemStackError（堆栈太深）。 - known_issues: - - "{% 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 跟踪文件被错误地直接添加到存储库。" - - 问题若是包含同一存储库中文件路径长于 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/18.yml b/translations/zh-CN/data/release-notes/enterprise-server/3-1/18.yml deleted file mode 100644 index d75b2f7a06..0000000000 --- a/translations/zh-CN/data/release-notes/enterprise-server/3-1/18.yml +++ /dev/null @@ -1,16 +0,0 @@ -date: '2022-03-01' -sections: - security_fixes: - - "高：在 GitHub 的 Markdown 分析程序中发现了可能会导致信息泄漏和 RCE 的整数溢出漏洞。该漏洞由 Google Project Zero 的成员 Felix Wilhelm 通过 GitHub Bug 悬赏计划报告，编号为 CVE-2022-24724。" - bugs: - - 如果高可用性副本的时钟与主要副本不同步，升级有时会失败。 - - "在 2020 年 9 月 1 日之后创建的 OAuth 应用程序无法使用[检查授权](https://docs.github.com/en/enterprise-server@3.1/rest/reference/apps#check-an-authorization) API 终结点。" - known_issues: - - "{% 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) 被错误地直接添加到仓库。" - - 如果议题包含文件路径长于 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 deleted file mode 100644 index cdd6e15a9e..0000000000 --- a/translations/zh-CN/data/release-notes/enterprise-server/3-1/19.yml +++ /dev/null @@ -1,41 +0,0 @@ -date: '2022-04-04' -sections: - security_fixes: - - '中：在 {% data variables.product.prodname_ghe_server %} 管理控制台中发现了一个允许绕过 CSRF 保护的路径遍历漏洞。此漏洞影响 3.5 之前的所有 {% data variables.product.prodname_ghe_server %} 版本，并在 3.1.19、3.2.11、3.3.6 和 3.4.1 中得到了修复。此漏洞通过 {% data variables.product.prodname_dotcom %} Bug 赏金计划报告，编号为 CVE-2022-23732。' - - '中：在 `yajil` 的 1.x 分支和 2.x 分支中发现了一个整数溢出漏洞，在处理大型 (~2GB) 输入时，该漏洞会导致随后出现堆内存损坏。此漏洞是内部报告的，编号为 CVE-2022-24795。' - - "如果启用了 {% data variables.product.prodname_actions %}，支持包可能包含敏感文件。" - - 包已更新到最新的安全版本。 - bugs: - - 显示了用于在管理控制台的“隐私”设置中启用 `TLS 1.0` 和 `TLS 1.1` 的选项，尽管在早期版本中移除了这些协议版本。 - - "在 HA 环境中，首次启用 {% data variables.product.prodname_actions %} 后，可能需要执行额外的手动步骤才能配置 MSSQL 复制。" - - 经过热补丁，内部配置文件的子集更新会更可靠。 - - "`ghe-run-migrations` 脚本有时无法正确生成临时证书名称。" - - 在群集环境中，Git LFS 操作可能会因跨多个 web 节点的内部 API 调用失败而失败。 - - 由于 `syscall` 权限不足，使用 `gpg --import` 的预接收挂钩超时。 - - 在某些群集拓扑中，Webhook 交付信息不可用。 - - "在 HA 配置中，如果先前已启用 {% data variables.product.prodname_actions %}，副本拆解操作将失败。" - - 运行迁移时，Elasticsearch 运行状况检查不允许出现黄色群集状态。 - - 由于用户将其用户帐户转换为组织而创建的组织未添加到全局企业帐户中。 - - "使用 `ghe-migrator` 或从 {% data variables.product.prodname_dotcom_the_website %} 导出时，如果在导出过程中删除数据，则长时间运行的导出将失败。" - - 无法访问的页面链接已被移除。 - - 将团队添加为拉取请求的审阅者时，有时会显示不正确的团队成员数量。 - - "大量休眠用户可能会导致 {% data variables.product.prodname_github_connect %} 配置失败。" - - 站点管理员 Web UI 中的“功能和 Beta 版本注册”页面无法正确使用。 - - 单击站点页脚中的“站点管理员模式”链接时，其状态未发生更改。 - changes: - - 增加了 Memcached 连接上限，可更好地适应大型群集拓扑。 - - 更有效地识别和删除超出 Webhook 日志保留时段的 Webhook 日志。 - - 依赖项关系图 API 以前使用静态定义的端口运行。 - - 已更新与群集相关的 Elasticsearch 分片设置的默认分片计数。 - - “会审”和“维护”团队角色在存储库迁移期间保留。 - - '出现了不必要的 `NotProcessedError` 异常。' - - 企业所有者提出的 Web 请求的性能已得到改进。 - known_issues: - - "{% 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)文件被错误地直接添加到存储库。" - - 如果问题包含同一存储库中文件路径长于 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/2.yml b/translations/zh-CN/data/release-notes/enterprise-server/3-1/2.yml deleted file mode 100644 index 015a7300ab..0000000000 --- a/translations/zh-CN/data/release-notes/enterprise-server/3-1/2.yml +++ /dev/null @@ -1,26 +0,0 @@ -date: '2021-06-24' -sections: - security_fixes: - - Packages have been updated to the latest security versions. - bugs: - - A large number of `gauge-dependency-graph-api-dispatch_dispatch` metrics could accumulate in the Management Console. - - The sshd service would sometimes fail to start on instances running on Google Cloud Platform. - - Old upgrade files would persist on the user disk, sometimes resulting in out of space conditions. - - '`gh-migrator` displayed an incorrect path to its log output.' - - An export archive would silently fail to import pull requests if they contained review requests from teams not present in the archive. - changes: - - Update the {% data variables.product.prodname_actions %} Runner version in GHES 3.1 to [v2.278.0](https://github.com/actions/runner/releases/tag/v2.278.0) - known_issues: - - The {% data variables.product.prodname_registry %} npm registry no longer returns a time value in metadata responses. This was done to allow for substantial performance improvements. We continue to have all the data necessary to return a time value as part of the metadata response and will resume returning this value in the future once we have solved the existing performance issues. - - 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. - - | - 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" - ``` - - If {% data variables.product.prodname_actions %} is enabled for {% data variables.product.prodname_ghe_server %}, teardown of a replica node with `ghe-repl-teardown` will succeed, but may return `ERROR:Running migrations`. - - Resource limits that are specific to processing pre-receive hooks may cause some pre-receive hooks to fail. 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 deleted file mode 100644 index 98df6f6beb..0000000000 --- a/translations/zh-CN/data/release-notes/enterprise-server/3-1/20.yml +++ /dev/null @@ -1,22 +0,0 @@ -date: '2022-04-20' -sections: - security_fixes: - - 包已更新到最新的安全版本。 - bugs: - - 在某些情况下，使用升级包升级高可用性对中的节点可能会导致 Elasticsearch 进入不一致状态。 - - 在某些群集拓扑中，命令行实用程序 `ghe-spokesctl` 和 `ghe-btop` 无法运行。 - - 由于 `elasticsearch-upgrade` 服务并行运行多次，因此 Elasticsearch 索引可能会在包升级期间重复。 - - "`maint_host_low` 作业队列未处理，导致某些维护任务无法运行。" - - "将用户帐户转换为组织帐户时，如果用户帐户是 {% data variables.product.prodname_ghe_server %} 企业帐户的所有者，则转换后的组织将无法正确显示在企业所有者列表中。" - - 当与 OAuth 应用程序 ID 匹配的集成已存在时，使用企业管理 REST API 创建模拟 OAuth 令牌会导致错误。 - changes: - - 尝试缓存大于 Memcached 中允许的最大值的值时，会引发错误，但不会报告密钥。 - known_issues: - - "{% 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 跟踪文件被错误地直接添加到存储库。" - - 问题若是包含同一存储库中文件路径长于 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 deleted file mode 100644 index da3e9b4d50..0000000000 --- a/translations/zh-CN/data/release-notes/enterprise-server/3-1/21.yml +++ /dev/null @@ -1,25 +0,0 @@ -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/)中公布的新漏洞。" - - 包已更新到最新的安全版本。 - bugs: - - 在某些群集拓扑中，`ghe-cluster-status` 命令会在 `/tmp` 中留下空目录。 - - SNMP 错误地将大量 `Cannot statfs` 错误消息记录到 syslog。 - - 对于配置了 SAML 身份验证和启用内置回退的实例，内置用户在尝试从退出登录后生成的页面登录时会陷入“登录”循环。 - - 使用 SAML 加密断言时，某些断言未正确将 SSH 密钥标记为已验证。 - - '当存储库具有包含非 ASCII 字符的标记时，发布页面将返回 500 错误。[更新时间：2022-06-10]' - changes: - - 在高可用性配置中，阐明管理控制台中的复制概述页面仅显示当前复制配置，而不是当前复制状态。 - - "启用 {% data variables.product.prodname_registry %} 时，阐明不支持使用共享访问签名 (SAS) 令牌作为连接字符串。" - - 支持包现在包括存储在 MySQL 中的表的行数。 - known_issues: - - "{% 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 跟踪文件被错误地直接添加到存储库。" - - 如果问题包含文件路径长于 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 deleted file mode 100644 index aa5edba89b..0000000000 --- a/translations/zh-CN/data/release-notes/enterprise-server/3-1/22.yml +++ /dev/null @@ -1,20 +0,0 @@ -date: '2022-06-09' -sections: - security_fixes: - - 包已更新到最新的安全版本。 - bugs: - - "如果主机名字符串以“.”开头（句点字符），则 {% data variables.product.prodname_ghe_server %} 配置文件中用于验证主机名的内部脚本将返回错误。" - - 在主节点的主机名超过 60 个字符的 HA 配置中，MySQL 将无法配置。 - - 站点管理员仪表板中报告的“跨整个实例的最大提交者”的计算不正确。 - - "使用 {% data variables.product.prodname_enterprise_backup_utilities %} 执行还原时，存储库复制的数据库输入不正确导致数据库损坏。" - changes: - - 在 Elasticsearch 报告有效的标黄状态的 HA 配置中，之前修复中引入的更改将阻止 `ghe-repl-stop` 命令，并且不允许停止复制。当服务处于正常或有效标黄状态时，使用 `ghe-repo-stop --force` 将强制 Elasticsearch 停止运行。 - known_issues: - - "{% 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 跟踪文件被错误地直接添加到存储库。" - - 如果问题包含文件路径长于 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/3.yml b/translations/zh-CN/data/release-notes/enterprise-server/3-1/3.yml deleted file mode 100644 index 13b74382da..0000000000 --- a/translations/zh-CN/data/release-notes/enterprise-server/3-1/3.yml +++ /dev/null @@ -1,27 +0,0 @@ -date: '2021-07-14' -sections: - security_fixes: - - '**高：**在 GitHub Enterprise Server 中发现了一个在构建 GitHub Pages 站点时可以利用的路径遍历漏洞。GitHub Pages 使用的用户控制配置选项没有受到足够的限制，因此可以在 GitHub Enterprise Server 实例上读取文件。要利用此漏洞，攻击者需要获得在 GitHub Enterprise Server 实例上创建和构建 GitHub Pages 站点的权限。此漏洞影响 3.1.3 之前的所有 GitHub Enterprise Server 版本，编号为 CVE-2021-22867。此漏洞通过 GitHub Bug 悬赏计划报告。' - - 包已更新到最新的安全版本。 - bugs: - - 未配置 SAML 到期日期变量。 - - 应用程序服务在配置应用期间的运行状况检查将失败，然后才能进入正常状态。 - - '如果启用了 HTTP 代理，则 `ghe-cluster-config-node-init` 会在群集设置期间失败。' - - 预接收挂钩可能会遇到错误“未能解析当前可执行文件的完整路径”，因为 `/proc` 未装载至容器上。 - - Collectd 在初始启动后不会解析转发目标主机名。 - - 如果其中部分仓库因受法律保护而无法被清除，则清除陈旧的已删除仓库的作业可能会失败。 - - 后台作业将排入 `spam` 队列，这些作业不会得到处理。 - - 当 PR 合并失败后重新尝试时，首选合并方法将被重置。 - - 在使用 LDAP 身份验证模式的实例的用户协调过程中，Git 推送可能导致500 内部服务器错误。 - - '在从 3.0.x 升级到 3.1.x后，GitHub Actions 可能会失败，错误为：“执行此工作流程时发生意外错误。”' - changes: - - 通过跳过未更改的 IP 允许防火墙规则，提高了配置应用效率，可在大型群集上节省大量时间。 - known_issues: - - "{% 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) 被错误地直接添加到仓库。" - - 如果议题包含文件路径长于 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/4.yml b/translations/zh-CN/data/release-notes/enterprise-server/3-1/4.yml deleted file mode 100644 index 4846e1652c..0000000000 --- a/translations/zh-CN/data/release-notes/enterprise-server/3-1/4.yml +++ /dev/null @@ -1,36 +0,0 @@ -date: '2021-07-27' -sections: - security_fixes: - - Packages have been updated to the latest security versions. - bugs: - - The counts on packages pages were not being incremented when a package was downloaded. - - '`ghe-config-apply` would timeout, ask for a prompt or fail for a customer that had {% data variables.product.prodname_secret_scanning %} enabled, and had either disabled or never enabled {% data variables.product.prodname_actions %} on their instance.' - - Log files were not reopened after rotation in some cases leading to high disk space usage on instances with high uptime. - - Upgrade could fail from older version of {% data variables.product.prodname_ghe_server %} due to a missing job in {% data variables.product.prodname_actions %}. - - 'Custom pre-receive hooks could lead to an error like `error: object directory /data/user/repositories/0/nw/12/34/56/7890/network.git/objects does not exist; check .git/objects/info/alternates`.' - - Unauthenticated HTTP proxy for the pages containers build was not supported for any users that use HTTP proxies. - - A significant number of 503 errors were logged every time a user visited a repository's `/settings` page if the dependency graph was not enabled. - - Internal repositories were only returned when a user had affiliations with the repository through a team or through collaborator status, or queried with the `?type=internal` parameter. - - Failed background jobs had unlimited retries which could cause large queue depths. - - A significant number of 503 errors were being created if the scheduled job to sync vulnerabilities with GitHub.com attempted to run when dependency graph was not enabled and content analysis was enabled. - - | - When {% data variables.product.prodname_actions %} is enabled without running regular scheduled backups, the MSSQL transaction log could grow unbounded and can consume all available space on the appliance's data disk, causing a possible outage. - - If you have configured regularly scheduled MSSQL backups, no further actions is required. Otherwise, if you have {% data variables.product.prodname_actions %} previously enabled, run the following commands after installing this patch. - - ``` - ghe-actions-console -s Mps -c 'Update-Service -Force' - ghe-actions-console -s Token -c 'Update-Service -Force' - ghe-actions-console -s Actions -c 'Update-Service -Force' - ``` - changes: - - The logs for `babeld` now include a `cmd` field for HTTP ref advertisement requests instead of only including it during the negotiation requests. - known_issues: - - The {% data variables.product.prodname_registry %} npm registry no longer returns a time value in metadata responses. This was done to allow for substantial performance improvements. We continue to have all the data necessary to return a time value as part of the metadata response and will resume returning this value in the future once we have solved the existing performance issues. - - 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. - - If {% data variables.product.prodname_actions %} is enabled for {% data variables.product.prodname_ghe_server %}, teardown of a replica node with `ghe-repl-teardown` will succeed, but may return `ERROR:Running migrations`. - - Resource limits that are specific to processing pre-receive hooks may cause some pre-receive hooks to fail. 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 deleted file mode 100644 index db2fc553e8..0000000000 --- a/translations/zh-CN/data/release-notes/enterprise-server/3-1/5.yml +++ /dev/null @@ -1,20 +0,0 @@ -date: '2021-08-10' -sections: - bugs: - - '使用 bash 子 shell 的自定义预接收挂钩将返回错误：`No such file or directory`。' - - 如果在不运行定期计划备份的情况下启用 GitHub Actions，则 MSSQL 事务日志可能会无限增长，并且会占用设备数据磁盘上的所有可用空间，从而可能导致中断。 - - 不必要的数据库日志记录在使用大量 LFS 的实例上消耗了大量磁盘空间。 - - 对“存储库创建”组织设置所做更改的审核日志条目不准确。 - - "过多记录 `ActionController::UnknownFormat` 异常会导致不必要的磁盘使用。" - - "LDAP `group_dn` 值超过 255 个字符将导致记录错误：`Data truncated for column 'group_dn' at row 1`。" - changes: - - 滥用速率限制现在称为辅助速率限制，因为它们限制的行为并不总是滥用。 - known_issues: - - "{% 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 跟踪文件被错误地直接添加到存储库。" - - 如果问题包含文件路径长于 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 deleted file mode 100644 index 9890f3ea58..0000000000 --- a/translations/zh-CN/data/release-notes/enterprise-server/3-1/6.yml +++ /dev/null @@ -1,23 +0,0 @@ -date: '2021-08-24' -sections: - security_fixes: - - 包已更新到最新的安全版本。 - bugs: - - 将非常大的图像或动态 GIF 附加到图像或拉取请求将失败。 - - 与自动更新相关的日志消息（`添加 h/m/s 随机时间。`）被记录到系统日志中。 - - 创建命名管道 (FIFO) 的自定义预接收挂钩会崩溃或挂起，从而导致超时错误。 - - 向审核日志高级搜索页面添加筛选器不会使用正确的 facet 前缀和值实时填充查询文本框。 - - "导致请求失败的内部 API 的 Git 挂钩返回异常 `undefined method body for \"success\":String (NoMethodError)`，而不是返回显式的 `nil`。" - - 删除集成后，可能还会删除不相关的 OAuth 应用程序或集成。 - - 添加包含表情符号字符的必填消息后，尝试查看或更改消息将返回 500 内部服务器错误。 - changes: - - 将 `triage` 和 `maintain` 添加到 REST API 返回的权限列表中。 - known_issues: - - "{% 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 跟踪文件被错误地直接添加到存储库。" - - 问题若是包含同一存储库中文件路径长于 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 deleted file mode 100644 index 452ff2faa7..0000000000 --- a/translations/zh-CN/data/release-notes/enterprise-server/3-1/7.yml +++ /dev/null @@ -1,18 +0,0 @@ -date: '2021-09-07' -sections: - security_fixes: - - 包已更新到最新的安全版本。 - bugs: - - 如果未启动复制，则尝试通过使用 `ghe-repl-teardown` 指定新添加副本节点的 UUID 来拆除该节点将失败，且不会报告错误。 - - GitHub Pages 内部版本正通过外部代理（如果已配置）进行传递。 - - 创建子进程的自定义预接收挂钩在其环境中缺少 `PATH` 变量，从而导致“没有此类文件或目录”错误。 - - 如果启用了 `mysql-auto-failover`，则 MySQL 可在升级期间进行故障转移。 - known_issues: - - "{% 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)文件被错误地直接添加到存储库。" - - 如果问题包含指向同一存储库中 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 deleted file mode 100644 index a388d49cbe..0000000000 --- a/translations/zh-CN/data/release-notes/enterprise-server/3-1/8.yml +++ /dev/null @@ -1,20 +0,0 @@ -date: '2021-09-24' -sections: - security_fixes: - - '**高：**在 {% data variables.product.prodname_ghe_server %} 中发现了一个在构建 {% data variables.product.prodname_pages %} 站点时可以利用的路径遍历漏洞。{% data variables.product.prodname_pages %} 使用的用户控制配置选项没有受到足够的限制，因此可以读取 {% data variables.product.prodname_ghe_server %} 实例上的文件。要利用此漏洞，攻击者需要获得在 {% data variables.product.prodname_ghe_server %} 实例上创建和构建 {% data variables.product.prodname_pages %} 站点的权限。此漏洞影响 3.1.8 之前的所有 {% data variables.product.prodname_ghe_server %} 版本，在 3.1.8、3.0.16 和 2.22.22 中得到了修复。这是 CVE-2021-22867 修复不完整的结果。此漏洞通过 GitHub Bug 赏金计划报告，编号为 CVE-2021-22868。{% comment %} https://github.com/github/pages/pull/3361, https://github.com/github/pages/pull/3357 {% endcomment %}' - - '**中：**{% data variables.product.prodname_ghe_server %} 中的不正确访问控制漏洞允许工作流作业在其不应访问的自承载运行器组中执行。这会影响使用自承载运行器组进行访问控制的客户。由于请求期间的身份验证检查不正确，有权访问一个企业运行器组的存储库可以访问组织内的所有企业运行器组。这可能会导致代码被不正确的运行器组无意运行。此漏洞影响 3.0.0-3.0.15 以及 3.1.0-3.1.7 的所有 {% data variables.product.prodname_ghe_server %} 版本，在 3.0.16 和 3.1.8 中得到了修复。其编号为 CVE-2021-22869。{% comment %} https://github.com/github/enterprise2/pull/27013 {% endcomment %}' - bugs: - - '在维护模式期间，Resque 工作进程计数显示不正确。{% comment %} https://github.com/github/enterprise2/pull/26899, https://github.com/github/enterprise2/pull/26883 {% endcomment %}' - - '在群集模式下，分配的 memcached 内存可能为零。{% comment %} https://github.com/github/enterprise2/pull/26928, https://github.com/github/enterprise2/pull/26832 {% endcomment %}' - - '非空二进制文件在拉取请求“文件”选项卡上显示了不正确的文件类型和大小。{% comment %} https://github.com/github/github/pull/192810, https://github.com/github/github/pull/172284, https://github.com/github/coding/issues/694 {% endcomment %}' - - '修复了 {% data variables.product.prodname_pages %} 构建，以便考虑设备的 NO_PROXY 设置。这仅与配置了 HTTP 代理的设备有关。（更新时间：2021-09-30）{% comment %} https://github.com/github/pages/pull/3360 {% endcomment %}' - - '即使不使用 `ghe-restore` 的 `--config` 选项，源实例的 GitHub Connect 配置也始终恢复到新实例。如果源实例和目标实例同时联机，这将导致与 GitHub Connect 连接和许可证同步发生冲突。该修复还需要将 backup-utils 更新到 3.2.0 或更高版本。[更新时间：2021-11-18]' - known_issues: - - "{% 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)文件被错误地直接添加到存储库。" - - 如果问题包含指向同一存储库中文件路径长于 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 deleted file mode 100644 index 9a68debc63..0000000000 --- a/translations/zh-CN/data/release-notes/enterprise-server/3-1/9.yml +++ /dev/null @@ -1,28 +0,0 @@ -date: '2021-10-12' -sections: - security_fixes: - - '包已更新到最新的安全版本。{% comment %} https://github.com/github/enterprise2/pull/27035, https://github.com/github/enterprise2/pull/27010 {% endcomment %}' - bugs: - - '由于过于严格的虚拟内存或 CPU 时间限制，自定义预接收挂钩可能会失败。{% comment %} https://github.com/github/enterprise2/pull/26972, https://github.com/github/enterprise2/pull/26955 {% endcomment %}' - - '尝试使用 `ghe-cleanup-settings` 擦除所有现有配置设置无法重启管理控制台服务。{% comment %} https://github.com/github/enterprise2/pull/26987, https://github.com/github/enterprise2/pull/26901 {% endcomment %}' - - '在通过“ghe-repl-teardown”进行复制拆除期间，Memcached 未能重启。{% comment %} https://github.com/github/enterprise2/pull/26993, https://github.com/github/enterprise2/pull/26983 {% endcomment %}' - - '在高负载期间，当上游服务未通过内部运行状况检查时，用户将收到 HTTP 503 状态代码。{% comment %} https://github.com/github/enterprise2/pull/27082, https://github.com/github/enterprise2/pull/26999 {% endcomment %}' - - '配置 Actions 后，从 GitHub Enterprise 备份实用工具快照还原后，MSSQL 复制将失败。{% comment %} https://github.com/github/enterprise2/pull/27097, https://github.com/github/enterprise2/pull/26254 {% endcomment %}' - - '运行 `ghe-config-apply` 时可能会显示错误的 `jq` 错误消息。{% comment %} https://github.com/github/enterprise2/pull/27194, https://github.com/github/enterprise2/pull/26784 {% endcomment %}' - - '预接收挂钩环境被禁止通过 Alpine 上的 BusyBox 调用 cat 命令。{% comment %} https://github.com/github/enterprise2/pull/27115, https://github.com/github/enterprise2/pull/27094 {% endcomment %}' - - '外部数据库密码以明文形式记录。{% comment %} https://github.com/github/enterprise2/pull/27173, https://github.com/github/enterprise2/pull/26413 {% endcomment %}' - - '从主群集数据中心故障转移到辅助群集数据中心成功，但随后故障转移回原始主群集数据中心时未能提升 Elasticsearch 索引。{% comment %} https://github.com/github/github/pull/193181, https://github.com/github/github/pull/192447 {% endcomment %}' - - '组织的“团队”页面上的“导入团队”按钮返回了 HTTP 404。{% comment %} https://github.com/github/github/pull/193302 {% endcomment %}' - - '在某些情况下，尝试查看“休眠用户”页面的 GitHub Enterprise 管理员会收到“502 网关错误”或“504 网关超时”响应。{% comment %} https://github.com/github/github/pull/194260, https://github.com/github/github/pull/193609 {% endcomment %}' - - '由于“SynchronizePullRequestJob”作业数量的增加，在某些高负载情况下，性能会受到负面影响。{% comment %} https://github.com/github/github/pull/195253, https://github.com/github/github/pull/194591 {% endcomment %}' - changes: - - '更有效地删除超出 Webhook 日志保留时段的 Webhook 日志。{% comment %} https://github.com/github/enterprise2/pull/27158 {% endcomment %}' - known_issues: - - "{% 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)被错误地直接添加到存储库。" - - 如果问题包含文件路径长于 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 deleted file mode 100644 index 634366e5e1..0000000000 --- a/translations/zh-CN/data/release-notes/enterprise-server/3-2/0-rc1.yml +++ /dev/null @@ -1,309 +0,0 @@ -date: '2021-09-09' -release_candidate: true -deprecated: true -intro: If {% data variables.location.product_location %} is running a release candidate build, you can't upgrade with a hotpatch. We recommend only running release candidates on test environments. -sections: - features: - - heading: Custom patterns for secret scanning - notes: - # https://github.com/github/releases/issues/1426 - - | - {% data variables.product.prodname_GH_advanced_security %} customers can now specify custom patterns for secret scanning. When a new pattern is specified, secret scanning searches a repository's entire Git history for the pattern, as well as any new commits. - - User defined patterns are in beta for {% data variables.product.prodname_ghe_server %} 3.2. They can be defined at the repository, organization, and enterprise levels. For more information, see "[Defining custom patterns for secret scanning](/code-security/secret-scanning/defining-custom-patterns-for-secret-scanning)." - - - heading: Security overview for Advanced Security (beta) - notes: - # https://github.com/github/releases/issues/1381 - - | - {% data variables.product.prodname_GH_advanced_security %} customers now have an organization-level view of the application security risks detected by {% data variables.product.prodname_code_scanning %}, {% data variables.product.prodname_dependabot %}, and {% data variables.product.prodname_secret_scanning %}. The security overview shows the enablement status of security features on each repository, as well as the number of alerts detected. - - In addition, the security overview lists all {% data variables.product.prodname_secret_scanning %} alerts at the organization level. Similar views for {% data variables.product.prodname_dependabot %} and {% data variables.product.prodname_code_scanning %} alerts are coming in future releases. For more information, see "[About the security overview](/code-security/security-overview/about-the-security-overview)." - - ![Screenshot of security overview](/assets/images/enterprise/3.2/release-notes/security-overview-UI.png) - - - heading: Dependency review (beta) - notes: - # https://github.com/github/releases/issues/1364 - - | - {% data variables.product.prodname_GH_advanced_security %} customers can now see a rich diff of the dependencies changed in a pull request. 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 these dependencies. 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)." - - - heading: GitHub Actions environments - notes: - # https://github.com/github/releases/issues/1308 - - | - Environments, environment protection rules, and environment secrets are now generally available for {% data variables.product.prodname_actions %} on {% data variables.product.product_name %}. For more information, see "[Environments](/actions/reference/environments)." - - ![Environment protection rules](/assets/images/enterprise/3.2/release-notes/actions-environments.png) - - - heading: SSH authentication with security keys - notes: - # https://github.com/github/releases/issues/1276 - - | - SSH authentication using a FIDO2 security key is now supported when you add a `sk-ecdsa-sha2-nistp256@openssh.com` or `sk-ssh-ed25519@openssh.com` SSH key to your account. SSH security keys store secret key material on a separate hardware device that requires verification, such as a tap, to operate. For more information, see "[Generating a new SSH key and adding it to the ssh-agent](/github/authenticating-to-github/connecting-to-github-with-ssh/generating-a-new-ssh-key-and-adding-it-to-the-ssh-agent#generating-a-new-ssh-key-for-a-hardware-security-key)." - - - heading: 'Dark and dark dimmed themes' - notes: - # https://github.com/github/releases/issues/1260 - - | - Dark and dark dimmed themes are now available for the web UI. {% data variables.product.product_name %} will match your system preferences when you haven't set theme preferences in {% data variables.product.product_name %}. You can also choose which themes are active during the day and night. For more information, see "[Managing your theme settings](/github/setting-up-and-managing-your-github-user-account/managing-user-account-settings/managing-your-theme-settings)." - - ![Dark and dark dimmed themes](https://user-images.githubusercontent.com/33528647/114629560-d2231f80-9c86-11eb-9bde-cc301a97040d.gif) - - - heading: 'Approving unverified domains for email notifications' - notes: - # https://github.com/github/releases/issues/1244 - - Domains that are not able to be verified can now be approved for email notification routing. Enterprise and organization owners will be able to approve domains and immediately augment their email notification restriction policy, allowing notifications to be sent to collaborators, consultants, acquisitions, or other partners. For more information, see "[Verifying or approving a domain for your enterprise](/admin/configuration/configuring-your-enterprise/verifying-or-approving-a-domain-for-your-enterprise#about-approval-of-domains)" and "[Restricting email notifications for your enterprise](/admin/policies/enforcing-policies-for-your-enterprise/restricting-email-notifications-for-your-enterprise#restricting-email-notifications-for-your-enterprise-account)." - - - heading: 'Git Credential Manager (GCM) secure credential storage and multi-factor authentication support' - notes: - # https://github.com/github/releases/issues/1406 - - | - Git Credential Manager (GCM) versions 2.0.452 and later now provide security-hardened credential storage and multi-factor authentication support for {% data variables.product.product_name %}. - - GCM with support for {% data variables.product.product_name %} is included with [Git for Windows](https://gitforwindows.org) versions 2.32 and later. GCM is not included with Git for macOS or Linux, but can be installed separately. For more information, see the [latest release](https://github.com/GitCredentialManager/git-credential-manager/releases/) and [installation instructions](https://github.com/GitCredentialManager/git-credential-manager/releases/) in the `GitCredentialManager/git-credential-manager` repository. - - changes: - - heading: Administration Changes - notes: - # https://github.com/github/releases/issues/1309 - - A 'User Agent Referrer Policy' setting has been added to the enterprise settings. This allows an admin to set a stricter `Referrer-Policy` to hide the hostname of a {% data variables.product.prodname_ghe_server %} installation from external sites. The setting is disabled by default and is tracked by audit log events for staff and enterprise owners when enabled or disabled. For more information, see "[Configuring Referrer Policy for your enterprise](/admin/configuration/configuring-your-enterprise/configuring-the-referrer-policy-for-your-enterprise)." - - # https://github.com/github/releases/issues/1515 - - The MySQL health check was changed to use `mysqladmin ping` instead of TCP checks, which removes some unnecessary noise in the MySQL error log. Also, Orchestrator failover checks were improved to prevent unnecessary MySQL failovers when applying cluster config changes. - - # https://github.com/github/releases/issues/1287 - - The Resque service, which supports background job processing, has been replaced with Aqueduct Lite. This change makes the job system easier to manage and should not affect the user experience. For the new administration and debugging commands for Aqueduct, see "[Command-line utilities](/admin/configuration/configuring-your-enterprise/command-line-utilities#ghe-aqueduct)." - - - heading: Token Changes - notes: - # https://github.com/github/releases/issues/1235 - - | - The format of authentication tokens for {% data variables.product.product_name %} has changed. The change affects the format of personal access tokens and access tokens for {% data variables.product.prodname_oauth_apps %}, as well as user-to-server, server-to-server, and refresh tokens for {% data variables.product.prodname_github_apps %}. - - The different token types now have unique identifiable prefixes, which allows for secret scanning to detect the tokens so that you can mitigate the impact of someone accidentally committing a token to a repository. {% data variables.product.company_short %} recommends updating existing tokens as soon as possible. For more information, see "[About authentication to {% data variables.product.prodname_dotcom %}](/github/authenticating-to-github/keeping-your-account-and-data-secure/about-authentication-to-github#githubs-token-formats)" and "[About {% data variables.product.prodname_secret_scanning %}](/code-security/secret-security/about-secret-scanning)." - - - heading: 'Repositories changes' - notes: - # https://github.com/github/releases/issues/1295 - - Repositories on user profiles and organization profiles now support sorting by star count. - - # https://github.com/github/releases/issues/1327 - - When viewing the commit history of a single file, you can now click {% octicon "file-code" aria-label="The code icon" %} to view that file at the selected point in history. - - # https://github.com/github/releases/issues/1254 - - When a submodule is defined with a relative path in {% data variables.location.product_location %}, the submodule is now clickable in the web UI. Clicking the submodule in the web UI will take you to the linked repository. Previously, only submodules with absolute URLs were clickable. This is supported for relative paths for repositories with the same owner that follow the pattern ../REPOSITORY or relative paths for repositories with a different owner that follow the pattern ../OWNER/REPOSITORY. For more information about working with submodules, see [Working with submodules](https://github.blog/2016-02-01-working-with-submodules/) on {% data variables.product.prodname_blog %}. - - # https://github.com/github/releases/issues/1250 - - The web UI can now be used to synchronize an out-of-date branch of a fork with the fork's upstream branch. If there are no merge conflicts between the branches, the branch is updated either by fast-forwarding or by merging from upstream. If there are conflicts, you will be prompted to create a pull request to resolve the conflicts. For more information, see "[Syncing a fork](/github/collaborating-with-pull-requests/working-with-forks/syncing-a-fork#syncing-a-fork-from-the-web-ui)." - - - heading: 'Markdown changes' - notes: - # https://github.com/github/releases/issues/1477 - - 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).' 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 deleted file mode 100644 index 708b798394..0000000000 --- a/translations/zh-CN/data/release-notes/enterprise-server/3-2/0.yml +++ /dev/null @@ -1,317 +0,0 @@ -date: '2021-09-28' -intro: For upgrade instructions, see "[Upgrading {% data variables.product.prodname_ghe_server %}](/admin/enterprise-management/updating-the-virtual-machine-and-physical-resources/upgrading-github-enterprise-server)." -sections: - features: - - heading: Custom patterns for secret scanning - notes: - # https://github.com/github/releases/issues/1426 - - | - {% data variables.product.prodname_GH_advanced_security %} customers can now specify custom patterns for secret scanning. When a new pattern is specified, secret scanning searches a repository's entire Git history for the pattern, as well as any new commits. - - User defined patterns are in beta for {% data variables.product.prodname_ghe_server %} 3.2. They can be defined at the repository, organization, and enterprise levels. For more information, see "[Defining custom patterns for secret scanning](/code-security/secret-scanning/defining-custom-patterns-for-secret-scanning)." - - - heading: Security overview for Advanced Security (beta) - notes: - # https://github.com/github/releases/issues/1381 - - | - {% data variables.product.prodname_GH_advanced_security %} customers now have an organization-level view of the application security risks detected by {% data variables.product.prodname_code_scanning %}, {% data variables.product.prodname_dependabot %}, and {% data variables.product.prodname_secret_scanning %}. The security overview shows the enablement status of security features on each repository, as well as the number of alerts detected. - - In addition, the security overview lists all {% data variables.product.prodname_secret_scanning %} alerts at the organization level. Similar views for {% data variables.product.prodname_dependabot %} and {% data variables.product.prodname_code_scanning %} alerts are coming in future releases. For more information, see "[About the security overview](/code-security/security-overview/about-the-security-overview)." - - ![Screenshot of security overview](/assets/images/enterprise/3.2/release-notes/security-overview-UI.png) - - - heading: Dependency review (beta) - notes: - # https://github.com/github/releases/issues/1364 - - | - {% data variables.product.prodname_GH_advanced_security %} customers can now see a rich diff of the dependencies changed in a pull request. 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 these dependencies. 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)." - - - heading: GitHub Actions environments - notes: - # https://github.com/github/releases/issues/1308 - - | - Environments, environment protection rules, and environment secrets are now generally available for {% data variables.product.prodname_actions %} on {% data variables.product.product_name %}. For more information, see "[Environments](/actions/reference/environments)." - - ![Environment protection rules](/assets/images/enterprise/3.2/release-notes/actions-environments.png) - - - heading: SSH authentication with security keys - notes: - # https://github.com/github/releases/issues/1276 - - | - SSH authentication using a FIDO2 security key is now supported when you add a `sk-ecdsa-sha2-nistp256@openssh.com` or `sk-ssh-ed25519@openssh.com` SSH key to your account. SSH security keys store secret key material on a separate hardware device that requires verification, such as a tap, to operate. For more information, see "[Generating a new SSH key and adding it to the ssh-agent](/github/authenticating-to-github/connecting-to-github-with-ssh/generating-a-new-ssh-key-and-adding-it-to-the-ssh-agent#generating-a-new-ssh-key-for-a-hardware-security-key)." - - - heading: 'Dark and dark dimmed themes' - notes: - # https://github.com/github/releases/issues/1260 - - | - Dark and dark dimmed themes are now available for the web UI. {% data variables.product.product_name %} will match your system preferences when you haven't set theme preferences in {% data variables.product.product_name %}. You can also choose which themes are active during the day and night. For more information, see "[Managing your theme settings](/github/setting-up-and-managing-your-github-user-account/managing-user-account-settings/managing-your-theme-settings)." - - ![Dark and dark dimmed themes](https://user-images.githubusercontent.com/33528647/114629560-d2231f80-9c86-11eb-9bde-cc301a97040d.gif) - - - heading: 'Approving unverified domains for email notifications' - notes: - # https://github.com/github/releases/issues/1244 - - Domains that are not able to be verified can now be approved for email notification routing. Enterprise and organization owners will be able to approve domains and immediately augment their email notification restriction policy, allowing notifications to be sent to collaborators, consultants, acquisitions, or other partners. For more information, see "[Verifying or approving a domain for your enterprise](/admin/configuration/configuring-your-enterprise/verifying-or-approving-a-domain-for-your-enterprise#about-approval-of-domains)" and "[Restricting email notifications for your enterprise](/admin/policies/enforcing-policies-for-your-enterprise/restricting-email-notifications-for-your-enterprise#restricting-email-notifications-for-your-enterprise-account)." - - - heading: 'Git Credential Manager (GCM) secure credential storage and multi-factor authentication support' - notes: - # https://github.com/github/releases/issues/1406 - - | - Git Credential Manager (GCM) versions 2.0.452 and later now provide security-hardened credential storage and multi-factor authentication support for {% data variables.product.product_name %}. - - GCM with support for {% data variables.product.product_name %} is included with [Git for Windows](https://gitforwindows.org) versions 2.32 and later. GCM is not included with Git for macOS or Linux, but can be installed separately. For more information, see the [latest release](https://github.com/GitCredentialManager/git-credential-manager/releases/) and [installation instructions](https://github.com/GitCredentialManager/git-credential-manager/releases/) in the `GitCredentialManager/git-credential-manager` repository. - - changes: - - heading: Administration Changes - notes: - # https://github.com/github/releases/issues/1309 - - A 'User Agent Referrer Policy' setting has been added to the enterprise settings. This allows an admin to set a stricter `Referrer-Policy` to hide the hostname of a {% data variables.product.prodname_ghe_server %} installation from external sites. The setting is disabled by default and is tracked by audit log events for staff and enterprise owners when enabled or disabled. For more information, see "[Configuring Referrer Policy for your enterprise](/admin/configuration/configuring-your-enterprise/configuring-the-referrer-policy-for-your-enterprise)." - - # https://github.com/github/releases/issues/1515 - - The MySQL health check was changed to use `mysqladmin ping` instead of TCP checks, which removes some unnecessary noise in the MySQL error log. Also, Orchestrator failover checks were improved to prevent unnecessary MySQL failovers when applying cluster config changes. - - # https://github.com/github/releases/issues/1287 - - The Resque service, which supports background job processing, has been replaced with Aqueduct Lite. This change makes the job system easier to manage and should not affect the user experience. For the new administration and debugging commands for Aqueduct, see "[Command-line utilities](/admin/configuration/configuring-your-enterprise/command-line-utilities#ghe-aqueduct)." - - - heading: Token Changes - notes: - # https://github.com/github/releases/issues/1235 - - | - The format of authentication tokens for {% data variables.product.product_name %} has changed. The change affects the format of personal access tokens and access tokens for {% data variables.product.prodname_oauth_apps %}, as well as user-to-server, server-to-server, and refresh tokens for {% data variables.product.prodname_github_apps %}. - - The different token types now have unique identifiable prefixes, which allows for secret scanning to detect the tokens so that you can mitigate the impact of someone accidentally committing a token to a repository. {% data variables.product.company_short %} recommends updating existing tokens as soon as possible. For more information, see "[About authentication to {% data variables.product.prodname_dotcom %}](/github/authenticating-to-github/keeping-your-account-and-data-secure/about-authentication-to-github#githubs-token-formats)" and "[About {% data variables.product.prodname_secret_scanning %}](/code-security/secret-security/about-secret-scanning)." - - - heading: 'Repositories changes' - notes: - # https://github.com/github/releases/issues/1295 - - Repositories on user profiles and organization profiles now support sorting by star count. - - # https://github.com/github/releases/issues/1327 - - When viewing the commit history of a single file, you can now click {% octicon "file-code" aria-label="The code icon" %} to view that file at the selected point in history. - - # https://github.com/github/releases/issues/1254 - - When a submodule is defined with a relative path in {% data variables.location.product_location %}, the submodule is now clickable in the web UI. Clicking the submodule in the web UI will take you to the linked repository. Previously, only submodules with absolute URLs were clickable. This is supported for relative paths for repositories with the same owner that follow the pattern ../REPOSITORY or relative paths for repositories with a different owner that follow the pattern ../OWNER/REPOSITORY. For more information about working with submodules, see [Working with submodules](https://github.blog/2016-02-01-working-with-submodules/) on {% data variables.product.prodname_blog %}. - - # https://github.com/github/releases/issues/1250 - - The web UI can now be used to synchronize an out-of-date branch of a fork with the fork's upstream branch. If there are no merge conflicts between the branches, the branch is updated either by fast-forwarding or by merging from upstream. If there are conflicts, you will be prompted to create a pull request to resolve the conflicts. For more information, see "[Syncing a fork](/github/collaborating-with-pull-requests/working-with-forks/syncing-a-fork#syncing-a-fork-from-the-web-ui)." - - - heading: 'Markdown changes' - notes: - # https://github.com/github/releases/issues/1477 - - 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).' 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 deleted file mode 100644 index 09c7e2745f..0000000000 --- a/translations/zh-CN/data/release-notes/enterprise-server/3-2/1.yml +++ /dev/null @@ -1,28 +0,0 @@ -date: '2021-10-12' -sections: - security_fixes: - - '包已更新到最新的安全版本。{% comment %} https://github.com/github/enterprise2/pull/27118, https://github.com/github/enterprise2/pull/27110 {% endcomment %}' - bugs: - - '由于过于严格的虚拟内存或 CPU 时间限制，自定义预接收挂钩可能会失败。{% comment %} https://github.com/github/enterprise2/pull/26973, https://github.com/github/enterprise2/pull/26955 {% endcomment %}' - - '在 GitHub Enterprise Server 群集配置中，依赖项关系图设置可能未正确应用。{% comment %} https://github.com/github/enterprise2/pull/26981, https://github.com/github/enterprise2/pull/26861 {% endcomment %}' - - '尝试使用 `ghe-cleanup-settings` 擦除所有现有配置设置无法重启管理控制台服务。{% comment %} https://github.com/github/enterprise2/pull/26988, https://github.com/github/enterprise2/pull/26901 {% endcomment %}' - - '利用“ghe-repl-teardown”清理复制期间，Memcached 未能重启。{% comment %} https://github.com/github/enterprise2/pull/26994, https://github.com/github/enterprise2/pull/26983 {% endcomment %}' - - '在高负载期间，当上游服务未通过内部运行状况检查时，用户将收到 HTTP 503 状态代码。{% comment %} https://github.com/github/enterprise2/pull/27083, https://github.com/github/enterprise2/pull/26999 {% endcomment %}' - - '禁止预接收挂钩环境通过 Alpine 上的 BusyBox 调用 cat 命令。{% comment %} https://github.com/github/enterprise2/pull/27116, https://github.com/github/enterprise2/pull/27094 {% endcomment %}' - - '从主群集数据中心故障转移到辅助群集数据中心成功，但随后故障转移回原始主群集数据中心时未能提升 Elasticsearch 索引。{% comment %} https://github.com/github/github/pull/193182, https://github.com/github/github/pull/192447 {% endcomment %}' - - '组织的“团队”页面上的“导入团队”按钮返回了 HTTP 404。{% comment %} https://github.com/github/github/pull/193303 {% endcomment %}' - - '使用 API 禁用机密扫描正确禁用了此属性，但错误地返回了 HTTP 422 和一个错误消息。{% comment %} https://github.com/github/github/pull/193455, https://github.com/github/github/pull/192907 {% endcomment %}' - - '在某些情况下，尝试查看“休眠用户”页面的 GitHub Enterprise 管理员会收到“502 网关错误”或“504 网关超时”响应。{% comment %} https://github.com/github/github/pull/194262, https://github.com/github/github/pull/193609 {% endcomment %}' - - '由于“SynchronizePullRequestJob”作业数量的增加，在某些高负载情况下，性能会受到负面影响。{% comment %} https://github.com/github/github/pull/195256, https://github.com/github/github/pull/194591 {% endcomment %}' - - '针对机密扫描创建的用户定义模式在被删除后也会继续被扫描。{% comment %} https://github.com/github/token-scanning-service/pull/1039, https://github.com/github/token-scanning-service/pull/822 {% endcomment %}' - changes: - - 'GitHub Apps 现在将存储库上的机密扫描功能设置为与 API 一致。{% comment %} https://github.com/github/github/pull/193456, https://github.com/github/github/pull/193125 {% endcomment %}' - known_issues: - - "在新建的没有任何用户的 {% data variables.product.prodname_ghe_server %} 上，攻击者可以创建第一个管理员用户。" - - 自定义防火墙规则在升级过程中被删除。 - - "[通过 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 注册表不再在元数据响应中返回时间值。这样做是为了大幅改善性能。作为元数据响应的一部分，我们继续拥有返回时间值所需的所有数据，并将在我们解决现有性能问题后恢复返回这个值。" - - 特定于处理预接收挂钩的资源限制可能会导致某些预接收挂钩失败。 - - '{% data reusables.release-notes.ghas-3.4-secret-scanning-known-issue %}' 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 deleted file mode 100644 index 654001252d..0000000000 --- a/translations/zh-CN/data/release-notes/enterprise-server/3-2/10.yml +++ /dev/null @@ -1,16 +0,0 @@ -date: '2022-03-01' -sections: - security_fixes: - - "高：在 GitHub 的 Markdown 分析程序中发现了可能会导致信息泄漏和 RCE 的整数溢出漏洞。该漏洞由 Google Project Zero 的成员 Felix Wilhelm 通过 GitHub Bug 悬赏计划报告，编号为 CVE-2022-24724。" - bugs: - - 如果高可用性副本的时钟与主要副本不同步，升级有时会失败。 - - "在 2020 年 9 月 1 日之后创建的 OAuth 应用程序无法使用[检查授权](https://docs.github.com/en/enterprise-server@3.2/rest/reference/apps#check-an-authorization) API 终结点。" - known_issues: - - "在新建的没有任何用户的 {% data variables.product.prodname_ghe_server %} 实例上，攻击者可以创建第一个管理员用户。" - - 自定义防火墙规则在升级过程中被删除。 - - "[通过 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 注册表不再在元数据响应中返回时间值。这样可以大幅改善性能。我们继续拥有将时间值作为元数据响应的一部分返回所需的所有数据，并将在以后解决现有性能问题后恢复返回该值。" - - 特定于处理预接收挂钩的资源限制可能导致部分预接收挂钩失败。 - - '{% data reusables.release-notes.ghas-3.4-secret-scanning-known-issue %}' 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 deleted file mode 100644 index bafb1315de..0000000000 --- a/translations/zh-CN/data/release-notes/enterprise-server/3-2/11.yml +++ /dev/null @@ -1,44 +0,0 @@ -date: '2022-04-04' -sections: - security_fixes: - - '中：在 {% data variables.product.prodname_ghe_server %} 管理控制台中发现了一个允许绕过 CSRF 保护的路径遍历漏洞。此漏洞影响 3.5 之前的所有 {% data variables.product.prodname_ghe_server %} 版本，并在 3.1.19、3.2.11、3.3.6 和 3.4.1 中得到了修复。此漏洞通过 {% data variables.product.prodname_dotcom %} Bug 赏金计划报告，编号为 CVE-2022-23732。' - - '中：在 `yajil` 的 1.x 分支和 2.x 分支中发现了一个整数溢出漏洞，在处理大型 (~2GB) 输入时，该漏洞会导致随后出现堆内存损坏。此漏洞是内部报告的，编号为 CVE-2022-24795。' - - "如果启用了 {% data variables.product.prodname_actions %}，支持包可能包含敏感文件。" - - 包已更新到最新的安全版本。 - bugs: - - "如果升级 {% data variables.product.prodname_ghe_server %} 后存在旧配置选项，Minio 进程的 CPU 使用率会很高。" - - 显示了用于在管理控制台的“隐私”设置中启用 `TLS 1.0` 和 `TLS 1.1` 的选项，尽管在早期版本中移除了这些协议版本。 - - "在 HA 环境中，首次启用 {% data variables.product.prodname_actions %} 后，可能需要执行额外的手动步骤才能配置 MSSQL 复制。" - - 经过热补丁，内部配置文件的子集更新会更可靠。 - - "`ghe-run-migrations` 脚本有时无法正确生成临时证书名称。" - - 在群集环境中，Git LFS 操作可能会因跨多个 Web 节点的内部 API 调用失败而失败。 - - 由于 `syscall` 权限不足，使用 `gpg --import` 的预接收挂钩超时。 - - 在某些群集拓扑中，Webhook 交付信息不可用。 - - "在 HA 配置中，如果先前已启用 {% data variables.product.prodname_actions %}，副本拆解操作将失败。" - - 运行迁移时，Elasticsearch 运行状况检查不允许出现黄色群集状态。 - - 由于用户将其用户帐户转换为组织而创建的组织未添加到全局企业帐户中。 - - "使用 `ghe-migrator` 或从 {% data variables.product.prodname_dotcom_the_website %} 导出时，如果在导出过程中删除数据，则长时间运行的导出将失败。" - - "{% data variables.product.prodname_actions %} 部署图在呈现待处理作业时会显示错误。" - - 无法访问的页面链接已被移除。 - - 远离 Web UI 中两个提交的比较将使差异在其他页面中持续存在。 - - 将团队添加为拉取请求的审阅者时，有时会显示不正确的团队成员数量。 - - "[删除用户的团队成员身份](/rest/reference/teams#remove-team-membership-for-a-user) API 终结点在尝试删除由 SCIM 组在外部管理的成员时会响应错误。" - - "大量休眠用户可能会导致 {% data variables.product.prodname_github_connect %} 配置失败。" - - 站点管理员 Web UI 中的“功能和 Beta 版本注册”页面无法正确使用。 - - 单击站点页脚中的“站点管理员模式”链接时，其状态未发生更改。 - - '`spokesctl cache-policy rm` 命名不再失败且显示消息 `error: failed to delete cache policy`。' - changes: - - 增加了 Memcached 连接上限，可更好地适应大型群集拓扑。 - - 依赖项关系图 API 以前使用静态定义的端口运行。 - - 已更新与群集相关的 Elasticsearch 分片设置的默认分片计数。 - - “会审”和“维护”团队角色在存储库迁移期间保留。 - - 企业所有者提出的 Web 请求的性能已得到改进。 - known_issues: - - "在新建的没有任何用户的 {% data variables.product.prodname_ghe_server %} 实例上，攻击者可以创建第一个管理员用户。" - - 自定义防火墙规则在升级过程中被移除。 - - "[通过 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 注册表不再在元数据响应中返回时间值。这样做是为了大幅改善性能。我们继续拥有将时间值作为元数据响应的一部分返回所需的所有数据，并将在以后解决现有性能问题后恢复返回该值。" - - 特定于处理预接收挂钩的资源限制可能导致部分预接收挂钩失败。 - - '{% data reusables.release-notes.ghas-3.4-secret-scanning-known-issue %}' 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 deleted file mode 100644 index 5543b2fb41..0000000000 --- a/translations/zh-CN/data/release-notes/enterprise-server/3-2/12.yml +++ /dev/null @@ -1,24 +0,0 @@ -date: '2022-04-20' -sections: - security_fixes: - - 包已更新到最新的安全版本。 - bugs: - - 在某些情况下，使用升级包升级高可用性对中的节点可能会导致 Elasticsearch 进入不一致状态。 - - 在某些群集拓扑中，命令行实用程序 `ghe-spokesctl` 和 `ghe-btop` 无法运行。 - - 由于 `elasticsearch-upgrade` 服务并行运行多次，因此 Elasticsearch 索引可能会在包升级期间重复。 - - "将用户帐户转换为组织帐户时，如果用户帐户是 {% data variables.product.prodname_ghe_server %} 企业帐户的所有者，则转换后的组织将无法正确显示在企业所有者列表中。" - - 当与 OAuth 应用程序 ID 匹配的集成已存在时，使用企业管理 REST API 创建模拟 OAuth 令牌会运行不正常。 - changes: - - 除了配置日志之外，停止 config apply 运行的配置错误现在会输出到终端。 - - 尝试缓存大于 Memcached 中允许的最大值的值时，会引发错误，但不会报告密钥。 - - "即使未使用 {% data variables.product.prodname_actions %} 的默认令牌权限，{% data variables.product.prodname_codeql %} 入门工作流程也不会再出错。" - - "如果在实例上启用了 {% data variables.product.prodname_GH_advanced_security %} 功能，则在处理存储库贡献的批次时，后台作业的性能会有所提高。" - known_issues: - - "在新建的没有任何用户的 {% data variables.product.prodname_ghe_server %} 实例上，攻击者可以创建第一个管理员用户。" - - 自定义防火墙规则在升级过程中被删除。 - - "[通过 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 注册表不再在元数据响应中返回时间值。这样可以大幅改善性能。我们继续拥有将时间值作为元数据响应的一部分返回所需的所有数据，并将在以后解决现有性能问题后恢复返回该值。" - - 特定于处理预接收挂钩的资源限制可能会导致某些预接收挂钩失败。 - - '{% data reusables.release-notes.ghas-3.4-secret-scanning-known-issue %}' 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 deleted file mode 100644 index 68abc622b7..0000000000 --- a/translations/zh-CN/data/release-notes/enterprise-server/3-2/13.yml +++ /dev/null @@ -1,28 +0,0 @@ -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/)中公布的新漏洞。" - - 包已更新到最新的安全版本。 - bugs: - - 在某些群集拓扑中，`ghe-cluster-status` 命令会在 `/tmp` 中留下空目录。 - - SNMP 错误地将大量 `Cannot statfs` 错误消息记录到 syslog。 - - 对于配置了 SAML 身份验证和启用内置回退的实例，内置用户在尝试从退出登录后生成的页面登录时会陷入“登录”循环。 - - 上传到问题评论的视频将无法正确呈现。 - - 使用 SAML 加密断言时，某些断言未正确将 SSH 密钥标记为已验证。 - - 使用 `ghe-migrator` 时，迁移将无法在问题和拉取请求中导入视频文件附件。 - - '当存储库具有包含非 ASCII 字符的标记时，发布页面将返回 500 错误。[更新时间：2022-06-10]' - changes: - - 在高可用性配置中，阐明管理控制台中的复制概述页面仅显示当前复制配置，而不是当前复制状态。 - - "启用 {% data variables.product.prodname_registry %} 时，阐明当前不支持使用共享访问签名 (SAS) 令牌作为连接字符串。" - - 支持包现在包括存储在 MySQL 中的表的行数。 - - "现在可以在没有漏洞数据的情况下启用依赖项关系图，允许你查看正在使用的依赖项和版本。启用依赖项关系图而不启用 {% data variables.product.prodname_github_connect %} 不会**提供漏洞信息。" - known_issues: - - "在新建的没有任何用户的 {% data variables.product.prodname_ghe_server %} 实例上，攻击者可以创建第一个管理员用户。" - - 自定义防火墙规则在升级过程中被移除。 - - "[通过 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 注册表不再在元数据响应中返回时间值。这样做是为了大幅改善性能。我们继续拥有将时间值作为元数据响应的一部分返回所需的所有数据，并将在以后解决现有性能问题后恢复返回该值。" - - 特定于处理预接收挂钩的资源限制可能导致部分预接收挂钩失败。 - - '{% data reusables.release-notes.ghas-3.4-secret-scanning-known-issue %}' 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 deleted file mode 100644 index 360c7618fc..0000000000 --- a/translations/zh-CN/data/release-notes/enterprise-server/3-2/14.yml +++ /dev/null @@ -1,23 +0,0 @@ -date: '2022-06-09' -sections: - security_fixes: - - 包已更新到最新的安全版本。 - bugs: - - "如果主机名字符串以“.”开头（句点字符），则 {% data variables.product.prodname_ghe_server %} 配置文件中用于验证主机名的内部脚本将返回错误。" - - 在主节点的主机名超过 60 个字符的 HA 配置中，MySQL 将无法配置。 - - "`--gateway` 参数已添加到 `ghe-setup-network` 命令，以允许使用命令行配置网络设置时传递网关地址。" - - 删除的图像附件将返回 `500 内部服务器错误` 而非 `404 未找到` 错误。 - - 站点管理员仪表板中报告的“跨整个实例的最大提交者”的计算不正确。 - - "使用 {% data variables.product.prodname_enterprise_backup_utilities %} 执行还原时，存储库复制的数据库输入不正确导致数据库损坏。" - changes: - - 优化了生成群集支持包时包含的指标。 - - 在 Elasticsearch 报告有效的标黄状态的 HA 配置中，之前修复中引入的更改将阻止 `ghe-repl-stop` 命令，并且不允许停止复制。当服务处于正常或有效标黄状态时，使用 `ghe-repo-stop --force` 将强制 Elasticsearch 停止运行。 - known_issues: - - "在新建的没有任何用户的 {% data variables.product.prodname_ghe_server %} 实例上，攻击者可以创建第一个管理员用户。" - - 自定义防火墙规则在升级过程中被删除。 - - "[通过 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 注册表不再在元数据响应中返回时间值。这样可以大幅改善性能。我们继续拥有将时间值作为元数据响应的一部分返回所需的所有数据，并将在以后解决现有性能问题后恢复返回该值。" - - 特定于处理预接收挂钩的资源限制可能导致部分预接收挂钩失败。 - - '{% data reusables.release-notes.ghas-3.4-secret-scanning-known-issue %}' 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 deleted file mode 100644 index 84169dfb99..0000000000 --- a/translations/zh-CN/data/release-notes/enterprise-server/3-2/15.yml +++ /dev/null @@ -1,20 +0,0 @@ -date: '2022-06-28' -sections: - security_fixes: - - "中****：确保 `github.company.com` 和 `github-company.com` 不会被内部服务评估为相同的主机名，从而防止潜在的服务器端安全性伪造 (SSRF) 攻击。" - - "低****：即使外部防火墙规则阻止了 HTTP 访问，攻击者也可以使用路径遍历攻击通过 HTTP 访问管理控制台。" - - 包已更新到最新安全版本。 - bugs: - - 在某些情况下，网站管理员未自动添加为企业所有者。 - - 将一个分支合并到默认分支之后，文件的“历史记录”链接仍然会链接到前一个分支，而不是目标分支。 - changes: - - 如果某些字段（如名称）的值过长，则创建或更新检查运行或检查套件可能返回“500 内部服务器错误”。 - known_issues: - - "在新建的没有任何用户的 {% data variables.product.prodname_ghe_server %} 实例上，攻击者可以创建第一个管理员用户。" - - 自定义防火墙规则在升级过程中被删除。 - - "[通过 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 注册表不再在元数据响应中返回时间值。这样可以大幅改善性能。我们继续拥有将时间值作为元数据响应的一部分返回所需的所有数据，并将在以后解决现有性能问题后恢复返回该值。" - - 特定于处理预接收挂钩的资源限制可能导致部分预接收挂钩失败。 - - '{% data reusables.release-notes.ghas-3.4-secret-scanning-known-issue %}' 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 deleted file mode 100644 index 8112ab2044..0000000000 --- a/translations/zh-CN/data/release-notes/enterprise-server/3-2/16.yml +++ /dev/null @@ -1,26 +0,0 @@ -date: '2022-07-21' -sections: - security_fixes: - - "中****：防止服务器端请求伪造 (SSRF) 可能通过向 Memcached 注入任意数据来强制 Subversion (SVN) 桥执行远程代码的攻击。" - - "将 Grafana 更新到版本 7.5.16，这样可以解决各种安全漏洞，包括 [CVE-2020-13379](https://github.com/advisories/GHSA-wc9w-wvq2-ffm9) 和 [CVE-2022-21702](https://github.com/grafana/grafana/security/advisories/GHSA-xc3p-28hw-q24g)。" - - 包已更新到最新安全版本。 - bugs: - - 修复了使用解压缩工具解压缩时项目压缩存档中的文件权限为 000 的问题。现在这些文件的权限将设置为 644，就像在 GitHub.com 中那样。 - - 在某些情况下，collectd 守护进程可能会消耗过多内存。 - - 在某些情况下，旋转日志文件备份可能会累积并消耗过多存储。 - - 在升级到新功能版本并运行后续配置之后，Elasticsearch 可能在重新生成索引时记录过多异常。 - - 在某些情况下，受保护的分支需要多个批准的审查，一个拉取请求可以合并少于所需数量的批准审查。 - - 在使用 LDAP 身份验证的实例中，当用户名和密码的文本字段都可见时，sudo 模式的身份验证提示在默认情况下将光标错误地放置在密码字段中。 - changes: - - "`ghe-set-password` 命令行实用程序在以恢复模式启动实例时自动启动所需的服务。" - - 将收集 `aqueduct` 后台进程指标进行 Collectd 转发并显示在管理控制台中。 - - 数据库迁移和配置运行日志 `/data/user/common/ghe-config.log` 的位置现在显示在详细描述正在进行的迁移的页面上。 - known_issues: - - "在新建的没有任何用户的 {% data variables.product.prodname_ghe_server %} 实例上，攻击者可以创建第一个管理员用户。" - - 自定义防火墙规则在升级过程中被删除。 - - "[通过 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 注册表不再在元数据响应中返回时间值。这样可以大幅改善性能。作为元数据响应的一部分，我们继续拥有返回时间值所需的所有数据，并将在以后解决现有性能问题后恢复返回这个值。" - - 特定于处理预接收挂钩的资源限制可能导致部分预接收挂钩失败。 - - '{% data reusables.release-notes.ghas-3.4-secret-scanning-known-issue %}' diff --git a/translations/zh-CN/data/release-notes/enterprise-server/3-2/17.yml b/translations/zh-CN/data/release-notes/enterprise-server/3-2/17.yml deleted file mode 100644 index 38943c2361..0000000000 --- a/translations/zh-CN/data/release-notes/enterprise-server/3-2/17.yml +++ /dev/null @@ -1,18 +0,0 @@ -date: '2022-08-11' -sections: - security_fixes: - - | - **CRITICAL**: GitHub Enterprise Server's Elasticsearch container used a version of OpenJDK 8 that was vulnerable to an integer truncation issue when processing malicious XSLT stylesheets. The vulnerability is tracked as [CVE-2022-34169](https://github.com/advisories/GHSA-9339-86wc-4qgf). - - | - **HIGH**: Previously installed apps on user accounts were automatically granted permission to access an organization on scoped access tokens after the user account was transformed into an organization account. This vulnerability was reported via the [GitHub Bug Bounty program](https://bounty.github.com). - bugs: - - When a custom dormancy threshold was set for the instance, suspending all dormant users did not reliably respect the threshold. For more information about dormancy, see "[Managing dormant users](/admin/user-management/managing-users-in-your-enterprise/managing-dormant-users)." - known_issues: - - On a freshly set up {% data variables.product.prodname_ghe_server %} instance without any users, an attacker could create the first admin user. - - Custom firewall rules are removed during the upgrade process. - - Git LFS tracked files [uploaded through the web interface](https://github.com/blog/2105-upload-files-to-your-repositories) are incorrectly added directly to the repository. - - Issues cannot be closed if they contain a permalink to a blob in the same repository, where the blob's file path is longer than 255 characters. - - When "Users can search GitHub.com" is enabled with {% data variables.product.prodname_github_connect %}, issues in private and internal repositories are not included in {% data variables.product.prodname_dotcom_the_website %} search results. - - The {% data variables.product.prodname_registry %} npm registry no longer returns a time value in metadata responses. This was done to allow for substantial performance improvements. We continue to have all the data necessary to return a time value as part of the metadata response and will resume returning this value in the future once we have solved the existing performance issues. - - Resource limits that are specific to processing pre-receive hooks may cause some pre-receive hooks to fail. - - '{% data reusables.release-notes.ghas-3.4-secret-scanning-known-issue %}' 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 deleted file mode 100644 index f14a33838f..0000000000 --- a/translations/zh-CN/data/release-notes/enterprise-server/3-2/18.yml +++ /dev/null @@ -1,16 +0,0 @@ -date: '2022-08-30' -sections: - bugs: - - 管理控制台和 `/home/admin/.ssh/authorized_keys` 文件中可能会出现重复的管理 SSH 密钥。 - - 在某些情况下，尽管不是线程安全的，但由于同时使用的库，可能会导致后台任务停止。 - changes: - - "由于并行日志清理，支持包的生成速度更快。有关支持包的详细信息，请参阅“[将数据提供给 GitHub 支持](/support/contacting-github-support/providing-data-to-github-support)”。" - known_issues: - - "在新建的没有任何用户的 {% data variables.product.prodname_ghe_server %} 实例上，攻击者可以创建第一个管理员用户。" - - 自定义防火墙规则在升级过程中被删除。 - - "[通过 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 注册表不再在元数据响应中返回时间值。这样可以大幅改善性能。作为元数据响应的一部分，我们继续拥有返回时间值所需的所有数据，并将在以后解决现有性能问题后恢复返回这个值。" - - 特定于处理预接收挂钩的资源限制可能导致部分预接收挂钩失败。 - - '{% data reusables.release-notes.ghas-3.4-secret-scanning-known-issue %}' 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 deleted file mode 100644 index ca97d64172..0000000000 --- a/translations/zh-CN/data/release-notes/enterprise-server/3-2/2.yml +++ /dev/null @@ -1,23 +0,0 @@ -date: '2021-10-28' -sections: - security_fixes: - - '明文密码可能会出现在某些日志文件中。' - - '多个已知弱 SSH 公钥已添加到拒绝列表中，无法再进行注册。此外，已知会生成弱 SSH 密钥的 GitKraken 版本（7.6.x、7.7.x 和 8.0.0）已被阻止注册新的公钥。' - - '包已更新到最新的安全版本。' - bugs: - - '如果业务流程协调程序运行不正常，企业服务器在群集模式下的还原可能会失败。' - - '代码空间链接显示在组织设置中。' - - '拥有许多组织的用户无法使用应用程序的多个部分。' - - '修复了 https://docs.github.com 链接。' - changes: - - '具有多个引用的存储库的浏览和作业性能优化。' - known_issues: - - 在存储库中保存新版本后，`/releases` 页面显示 500 错误。此问题的修复程序预计将在 3.2.3 中发布。 - - "在新建的没有任何用户的 {% data variables.product.prodname_ghe_server %} 上，攻击者可以创建第一个管理员用户。" - - 自定义防火墙规则在升级过程中被删除。 - - "[通过 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 注册表不再在元数据响应中返回时间值。这样做是为了大幅改善性能。我们继续拥有将时间值作为元数据响应的一部分返回所需的所有数据，并将在以后解决现有性能问题后恢复返回该值。" - - 特定于处理预接收挂钩的资源限制可能导致部分预接收挂钩失败。 - - '{% data reusables.release-notes.ghas-3.4-secret-scanning-known-issue %}' 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 deleted file mode 100644 index cf4f2569ed..0000000000 --- a/translations/zh-CN/data/release-notes/enterprise-server/3-2/3.yml +++ /dev/null @@ -1,31 +0,0 @@ -date: '2021-11-09' -sections: - security_fixes: - - "在 {% data variables.product.prodname_ghe_server %} 上发现了在构建 {% data variables.product.prodname_pages %} 时出现的路径遍历漏洞，攻击者可利用该漏洞读取系统文件。要利用此漏洞，攻击者需要获得在 {% data variables.product.prodname_ghe_server %} 实例上创建和构建 {% data variables.product.prodname_pages %} 站点的权限。此漏洞影响 3.3 之前的所有 {% data variables.product.prodname_ghe_server %} 版本，并在 3.0.19、3.1.11 和 3.2.3 中修复。该漏洞通过 {% data variables.product.company_short %} Bug 悬赏计划报告，编号为 CVE-2021-22870。" - - 包已更新到最新的安全版本。 - bugs: - - "部分 Git 操作在升级 {% data variables.product.prodname_ghe_server %} 3.x 群集后由于 HAProxy 配置而失败。" - - 在群集模式下，Unicorn 辅助角色计数可能会设置错误。 - - 在群集模式下，Resqued 辅助角色计数可能会设置错误。 - - 如果 Ubuntu Uncomplicated Firewall (UFW) 处于不活动状态，客户端可能无法在日志中清楚地看到它。 - - "当 LDAP 配置中存在 UTF8 字符时，从 {% data variables.product.prodname_ghe_server %} 2.x 到 3.x 的升级会失败。" - - 某些页面和与 Git 相关的后台作业可能无法在具有某些群集配置的群集模式下运行。 - - 服务器统计信息的文档链接已损坏。 - - "创建新标记时，[推送](/developers/webhooks-and-events/webhooks/webhook-events-and-payloads#push) Webhook 有效负载不显示正确的 `head_commit` 对象。现在，创建新标记时，推送 Webhook 有效负载始终包括 `head_commit` 对象，其中包含新标记指向的提交数据。因此，`head_commit` 对象将始终包含有效负载 `after` 提交的提交数据。" - - "企业审核日志页面不会显示 {% data variables.product.prodname_secret_scanning %} 的审核事件。" - - 副本修复的作业超时时间不足。 - - 查看版本时，存储库的发布页面将返回 500 错误。 - - '在查看文件时，不会警告用户有潜在危险的双向 Unicode 字符。有关详细信息，请参阅 {% data variables.product.prodname_blog %} 中的“[有关双向 Unicode 文本的警告](https://github.co/hiddenchars)”。' - - Hookshot Go 发送了 Collectd 无法处理的分布类型指标，这导致解析错误激增。 - - "公共存储库显示来自 {% data variables.product.prodname_secret_scanning %} 的意外结果，类型为“未知令牌”。" - changes: - - 已添加 Kafka 配置改进。删除存储库时，现在会立即从存储帐户中删除包文件以释放空间。`DestroyDeletedPackageVersionsJob` 现在从存储帐户中删除过期包的包文件以及元数据记录。 - known_issues: - - "在新建的没有任何用户的 {% data variables.product.prodname_ghe_server %} 上，攻击者可以创建第一个管理员用户。" - - 自定义防火墙规则在升级过程中被删除。 - - "[通过 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 注册表不再在元数据响应中返回时间值。这样做是为了大幅改善性能。作为元数据响应的一部分，我们继续拥有返回时间值所需的所有数据，并将在我们解决现有性能问题后恢复返回这个值。" - - 特定于处理预接收挂钩的资源限制可能会导致某些预接收挂钩失败。 - - '{% data reusables.release-notes.ghas-3.4-secret-scanning-known-issue %}' 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 deleted file mode 100644 index 72cbad67f6..0000000000 --- a/translations/zh-CN/data/release-notes/enterprise-server/3-2/4.yml +++ /dev/null @@ -1,30 +0,0 @@ -date: '2021-11-23' -intro: 由于影响多个客户的重大错误，已禁用下载。修复程序将在下一个补丁中提供。 -sections: - security_fixes: - - 包已更新到最新的安全版本。 - bugs: - - 如果已启用 GitHub Actions，运行 `ghe-repl-start` 或 `ghe-repl-status` 可能会在连接到数据库时返回错误。 - - 如果未定义 `PATH`，预接收挂钩会失败。 - - '如果曾将实例配置为副本，运行 `ghe-repl-setup` 会返回错误：“无法创建目录 /data/user/elasticsearch：文件已存在”。' - - '运行 `ghe-support-bundle` 返回错误：“应为整数表达式”。' - - '设置高可用性副本后，`ghe-repl-status` 在输出中包含错误：“命令中未关闭的意外操作”。' - - 在大型群集环境中，某部分前端节点可能无法使用身份验证后端。 - - 在 GHES 群集的后端节点上，一些关键服务可能不可用。 - - "`/repos` API 返回给用户的存储库权限不会返回完整的列表。" - - 在某些情况下，GraphQL 架构中的 `Team` 对象上的 `childTeams` 连接会产生不正确的结果。 - - 在高可用性配置中，存储库维护在人员工具中总是显示为失败，即使成功了也是如此。 - - 用户定义的模式不会检测 `package.json` 或 `yarn.lock` 等文件中的机密。 - changes: - - 在使用 `ghe-cluster-suport-bundle` 创建群集支持包时，现在会默认关闭额外一层的外部 `gzip` 压缩。使用 `ghe-cluster-suport-bundle -c` 命令行选项可以选择应用此外部压缩。 - - 我们在管理控制台添加了额外的文本，以提醒用户移动应用的数据收集，目的是改善体验。 - - "{% data variables.product.prodname_github_connect %} 数据连接记录现在会列出已启用的 {% data variables.product.prodname_github_connect %} 功能。[更新时间：2021-12-09]" - known_issues: - - "在新建的没有任何用户的 {% data variables.product.prodname_ghe_server %} 上，攻击者可以创建第一个管理员用户。" - - 自定义防火墙规则在升级过程中被删除。 - - "[通过 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 注册表不再在元数据响应中返回时间值。这样做是为了大幅改善性能。我们继续拥有将时间值作为元数据响应的一部分返回所需的所有数据，并将在以后解决现有性能问题后恢复返回该值。" - - 特定于处理预接收挂钩的资源限制可能导致部分预接收挂钩失败。 - - '{% data reusables.release-notes.ghas-3.4-secret-scanning-known-issue %}' 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 deleted file mode 100644 index e3b6aef065..0000000000 --- a/translations/zh-CN/data/release-notes/enterprise-server/3-2/5.yml +++ /dev/null @@ -1,28 +0,0 @@ -date: '2021-12-07' -sections: - security_fixes: - - 支持包可以包含敏感文件，前提是它们满足一组特定条件。 - - "在 GitHub Enterprise Server 中发现了一个 UI 虚假陈述漏洞，该漏洞允许在 GitHub 应用程序的用户授权 Web 流期间授予比在审批期间向用户显示的更多权限。此漏洞影响 GitHub Enterprise Server 3.3 之前的所有版本，已在 3.2.5、3.1.13 和 3.0.21 中修复。此漏洞通过 GitHub Bug 赏金计划报告，编号为 [CVE-2021-41598](https://www.cve.org/CVERecord?id=CVE-2021-41598)。" - - "在 GitHub Enterprise Server 中发现了一个在构建 GitHub Pages 站点时可以利用的远程代码执行漏洞。此漏洞影响 GitHub Enterprise Server 3.3 之前的所有版本，已在 3.0.21、3.1.13 和 3.2.5 中修复。此漏洞通过 GitHub Bug 赏金计划报告，编号为 [CVE-2021-41599](https://www.cve.org/CVERecord?id=CVE-2021-41599)。更新时间：2022 年 2 月 17 日。" - bugs: - - 在某些未启用操作的情况下，`ghe-support-bundle` 报告了意外消息“无法找到 MS SQL 容器”。 - - 由于 `/data/user/tmp/pages` 中存在权限问题，`ghe-config-apply` 的运行有时可能会失败。 - - 管理控制台中的错误配置导致了调度错误。 - - Docker 会在日志轮换后保持日志文件打开。 - - 由于对不兼容 UTF-8 的 `blob_path` 值的错误处理，迁移可能会停滞。 - - GraphQL 请求未在预接收挂钩环境中设置 GITHUB_USER_IP 变量。 - - 组织审计日志上的分页链接不会保留查询参数。 - - 在热补丁期间，如果多次运行转换，则可能会出现重复的哈希。 - changes: - - 阐明了文档中对 Actions 路径样式的解释。 - - 更新支持联系 URL 以使用当前支持站点 support.github.com。 - - 运行 `ghe-mssql-diagnostic` 时提供了其他疑难解答。 - known_issues: - - "在新建的没有任何用户的 {% data variables.product.prodname_ghe_server %} 上，攻击者可以创建第一个管理员用户。" - - 自定义防火墙规则在升级过程中被删除。 - - "[通过 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 注册表不再在元数据响应中返回时间值。这样做是为了大幅改善性能。我们继续拥有将时间值作为元数据响应的一部分返回所需的所有数据，并将在以后解决现有性能问题后恢复返回该值。" - - 特定于处理预接收挂钩的资源限制可能导致部分预接收挂钩失败。 - - '{% data reusables.release-notes.ghas-3.4-secret-scanning-known-issue %}' 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 deleted file mode 100644 index 239c0e710b..0000000000 --- a/translations/zh-CN/data/release-notes/enterprise-server/3-2/6.yml +++ /dev/null @@ -1,14 +0,0 @@ -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/)。' - - '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 跟踪文件被错误地直接添加到存储库。" - - 如果问题包含文件路径长于 255 个字符的同一存储库中 Blob 的永久链接，则问题无法关闭。 - - 在 GitHub Connect 中启用了“用户可以搜索 GitHub.com”时，专用和内部存储库中的问题不包括在 GitHub.com 搜索结果中。 - - "{% data variables.product.prodname_registry %} npm 注册表不再在元数据响应中返回时间值。这样可以大幅改善性能。我们继续拥有将时间值作为元数据响应的一部分返回所需的所有数据，并将在以后解决现有性能问题后恢复返回该值。" - - 特定于处理预接收挂钩的资源限制可能导致部分预接收挂钩失败。 - - '{% data reusables.release-notes.ghas-3.4-secret-scanning-known-issue %}' 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 deleted file mode 100644 index fdb9db199d..0000000000 --- a/translations/zh-CN/data/release-notes/enterprise-server/3-2/7.yml +++ /dev/null @@ -1,23 +0,0 @@ -date: '2022-01-18' -sections: - security_fixes: - - '包已更新到最新的安全版本。在这些更新中，Log4j 已更新至版本 2.17.1。注意：以前在 3.3.1、3.2.6、3.1.14 和 3.0.22 中发布的缓解措施已经足够解决这些 GitHub Enterprise Server 版本中 CVE-2021-44228、CVE-2021-45046、CVE-2021-45105 和 CVE-2021-44832 的影响。' - - 清理生成的支持包中的更多机密 - - 包已更新到最新的安全版本。 - bugs: - - 操作自托管运行器在从较旧的 GHES 安装升级后将无法自我更新或运行新作业。 - - 将 MinIO 配置为 GitHub 包的 Blob 存储时，无法验证存储设置。 - - 由于 `/data/user/tmp/pages` 中存在权限问题，运行 `ghe-config-apply` 有时可能会失败。 - - 在低分辨率的浏览器中滚动，可能无法找到管理控制台中的保存按钮。 - - Collectd 版本升级后，IOPS 和存储流量监视图未更新。 - - 一些与 Webhook 相关的作业可能会产生大量的日志。 - - 多个文档链接导致“404 找不到”错误。 - known_issues: - - "在新建的没有任何用户的 {% data variables.product.prodname_ghe_server %} 上，攻击者可以创建第一个管理员用户。" - - 自定义防火墙规则在升级过程中被删除。 - - "[通过 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 注册表不再在元数据响应中返回时间值。这样做是为了大幅改善性能。我们继续拥有将时间值作为元数据响应的一部分返回所需的所有数据，并将在以后解决现有性能问题后恢复返回该值。" - - 特定于处理预接收挂钩的资源限制可能导致部分预接收挂钩失败。 - - '{% data reusables.release-notes.ghas-3.4-secret-scanning-known-issue %}' 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 deleted file mode 100644 index 5f00f51c99..0000000000 --- a/translations/zh-CN/data/release-notes/enterprise-server/3-2/8.yml +++ /dev/null @@ -1,26 +0,0 @@ -date: '2022-02-01' -sections: - security_fixes: - - 包已更新到最新安全版本。 - bugs: - - 在 MySQL 机密轮换后，页面将不可用，直到手动重启 `nginx`。 - - "如果启用 {% data variables.product.prodname_actions %}，迁移可能会失败。" - - 使用 ISO 8601 日期设置维护计划时，由于时区未转换为 UTC，因此实际计划时间将不匹配。 - - 有关 `cloud-config.service` 的虚假错误消息将输出到控制台。 - - 使用 `ghe-cluster-each` 安装热补丁后，版本号将无法正确更新。 - - Webhook 表清理作业可能同时运行，从而导致资源争用且作业运行时间增加。 - - 从主节点运行时，副本节点上的 `ghe-repl-teardown` 不会将副本节点从 MSSQL 可用性组中删除。 - - 使用 CAS 身份验证并启用“重新激活暂停的用户”选项时，暂停的用户不会自动重新激活。 - - 以下功能无法正常使用：仅限对在经过验证或批准的域上具有电子邮件的用户发送基于电子邮件的通知。 - - 与“安全警报”设置相关的长期数据库迁移可能会延迟升级完成。 - changes: - - GitHub Connect 数据连接记录现在包括活动和休眠用户数量计数以及配置的休眠期。 - known_issues: - - "在新建的没有任何用户的 {% data variables.product.prodname_ghe_server %} 上，攻击者可以创建第一个管理员用户。" - - 自定义防火墙规则在升级过程中被删除。 - - "[通过 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 注册表不再在元数据响应中返回时间值。这样可以大幅改善性能。我们继续拥有将时间值作为元数据响应的一部分返回所需的所有数据，并将在以后解决现有性能问题后恢复返回该值。" - - 特定于处理预接收挂钩的资源限制可能导致部分预接收挂钩失败。 - - '{% data reusables.release-notes.ghas-3.4-secret-scanning-known-issue %}' 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 deleted file mode 100644 index 3230434c37..0000000000 --- a/translations/zh-CN/data/release-notes/enterprise-server/3-2/9.yml +++ /dev/null @@ -1,20 +0,0 @@ -date: '2022-02-17' -sections: - security_fixes: - - 用户可以注册名为“saml”的用户或组织。 - - 包已更新到最新安全版本。 - bugs: - - 使用 Azure Blob 存储时，无法验证 GitHub Packages 存储设置并将其保存在管理控制台中。 - - mssql.backup.cadence 配置选项的 ghe-config-check 失败，并发出无效字符集警告。 - - 修复从 memcached 获取超过 2^16 个密钥时的 SystemStackError（堆栈太深）。 - changes: - - 机密扫描将跳过扫描 ZIP 和其他存档文件的机密。 - known_issues: - - "在新建的没有任何用户的 {% data variables.product.prodname_ghe_server %} 实例上，攻击者可以创建第一个管理员用户。" - - 自定义防火墙规则在升级过程中被删除。 - - "[通过 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 注册表不再在元数据响应中返回时间值。这样可以大幅改善性能。我们继续拥有将时间值作为元数据响应的一部分返回所需的所有数据，并将在以后解决现有性能问题后恢复返回该值。" - - 特定于处理预接收挂钩的资源限制可能导致部分预接收挂钩失败。 - - '{% data reusables.release-notes.ghas-3.4-secret-scanning-known-issue %}' diff --git a/translations/zh-CN/data/reusables/organizations/org_settings.md b/translations/zh-CN/data/reusables/organizations/org_settings.md index 4e84c3e807..eecd66ef6c 100644 --- a/translations/zh-CN/data/reusables/organizations/org_settings.md +++ b/translations/zh-CN/data/reusables/organizations/org_settings.md @@ -1,6 +1,6 @@ 1. Under your organization name, click {% octicon "gear" aria-label="The Settings gear" %} **Settings**. - {% ifversion fpt or ghes or ghec %} +{% ifversion fpt or ghes or ghec %} ![Organization settings button](/assets/images/help/organizations/organization-settings-tab-with-overview-tab.png) - {% else %} +{% else %} ![Organization settings button](/assets/images/help/organizations/organization-settings-tab.png) - {% endif %} +{% endif %} diff --git a/translations/zh-CN/data/reusables/repositories/git-lfs.md b/translations/zh-CN/data/reusables/repositories/git-lfs.md new file mode 100644 index 0000000000..cf76ef096f --- /dev/null +++ b/translations/zh-CN/data/reusables/repositories/git-lfs.md @@ -0,0 +1,9 @@ +--- +ms.openlocfilehash: f8247d698d2b9a9be09d2dcf8e0492355a377204 +ms.sourcegitcommit: 06726d24e73f1175f10749d6fdcf143d6094c9a5 +ms.translationtype: HT +ms.contentlocale: zh-CN +ms.lasthandoff: 10/28/2022 +ms.locfileid: "148118741" +--- +如果超出 5GB 限制，Git LFS 将静默拒绝添加到存储库的任何新文件。 \ No newline at end of file diff --git a/translations/zh-CN/data/reusables/user-settings/password-authentication-deprecation.md b/translations/zh-CN/data/reusables/user-settings/password-authentication-deprecation.md index 04a4cbd48e..3cb8481a53 100644 --- a/translations/zh-CN/data/reusables/user-settings/password-authentication-deprecation.md +++ b/translations/zh-CN/data/reusables/user-settings/password-authentication-deprecation.md @@ -1 +1 @@ -When Git prompts you for your password, enter your {% data variables.product.pat_generic %}. Alternatively, you can use a credential helper like [Git Credential Manager](https://github.com/GitCredentialManager/git-credential-manager/blob/main/README.md).{% ifversion not ghae %} Password-based authentication for Git has been removed in favor of more secure authentication methods.{% endif %} For more information, see "[Creating a {% data variables.product.pat_generic %}](/github/authenticating-to-github/creating-a-personal-access-token)." +When Git prompts you for your password, enter your {% data variables.product.pat_generic %}. Alternatively, you can use a credential helper like [Git Credential Manager](https://github.com/GitCredentialManager/git-credential-manager/blob/main/README.md).{% ifversion not ghae %} Password-based authentication for Git has been removed in favor of more secure authentication methods.{% endif %} For more information, see "[Creating a {% data variables.product.pat_generic %}](/authentication/keeping-your-account-and-data-secure/creating-a-personal-access-token)."