Skip to content

Commit ba552da

Browse files
authored
Merge pull request #27366 from github/repo-sync
Repo sync
2 parents 26e6fe4 + 8adf74c commit ba552da

File tree

14 files changed

+207
-20
lines changed

14 files changed

+207
-20
lines changed

content/rest/actions/artifacts.md

Lines changed: 0 additions & 2 deletions
Original file line numberDiff line numberDiff line change
@@ -19,6 +19,4 @@ autogenerated: rest
1919

2020
You can use the REST API to download, delete, and retrieve information about workflow artifacts in {% data variables.product.prodname_actions %}. {% data reusables.actions.about-artifacts %} For more information, see "[AUTOTITLE](/actions/using-workflows/storing-workflow-data-as-artifacts)."
2121

22-
{% data reusables.actions.actions-authentication %} {% data reusables.actions.actions-app-actions-permissions-api %}
23-
2422
<!-- Content after this section is automatically generated -->

content/rest/actions/index.md

Lines changed: 0 additions & 2 deletions
Original file line numberDiff line numberDiff line change
@@ -28,6 +28,4 @@ children:
2828
autogenerated: rest
2929
---
3030

31-
You can use the REST API to manage and control {% data variables.product.prodname_actions %} for an organization or repository. {% data reusables.actions.actions-authentication %} {% data variables.product.prodname_github_apps %} require the permissions mentioned in each endpoint. For more information, see "[AUTOTITLE](/actions)."
32-
3331
<!-- Content after this section is automatically generated -->

content/rest/actions/oidc.md

Lines changed: 2 additions & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -14,6 +14,8 @@ versions: # DO NOT MANUALLY EDIT. CHANGES WILL BE OVERWRITTEN BY A 🤖
1414
autogenerated: rest
1515
---
1616

17+
## About {% data variables.product.prodname_actions %} OIDC
1718

19+
You can use the REST API to query and manage a customization template for an OpenID Connect (OIDC) subject claim. For more information, see "[AUTOTITLE](/actions/deployment/security-hardening-your-deployments/about-security-hardening-with-openid-connect)."
1820

1921
<!-- Content after this section is automatically generated -->

content/rest/actions/secrets.md

Lines changed: 0 additions & 2 deletions
Original file line numberDiff line numberDiff line change
@@ -19,6 +19,4 @@ autogenerated: rest
1919

2020
You can use the REST API to create, update, delete, and retrieve information about encrypted secrets that can be used in workflows in {% data variables.product.prodname_actions %}. {% data reusables.actions.about-secrets %} For more information, see "[AUTOTITLE](/actions/security-guides/encrypted-secrets)."
2121

22-
{% data reusables.actions.actions-authentication %} {% data variables.product.prodname_github_apps %} must have the `secrets` permission to use these endpoints. Authenticated users must have collaborator access to a repository to create, update, or read secrets.
23-
2422
<!-- Content after this section is automatically generated -->

content/rest/actions/self-hosted-runners.md

Lines changed: 0 additions & 2 deletions
Original file line numberDiff line numberDiff line change
@@ -17,6 +17,4 @@ autogenerated: rest
1717

1818
You can use the REST API to register, view, and delete self-hosted runners in {% data variables.product.prodname_actions %}. {% data reusables.actions.about-self-hosted-runners %} For more information, see "[AUTOTITLE](/actions/hosting-your-own-runners)."
1919

20-
{% data reusables.actions.actions-authentication %} {% data variables.product.prodname_github_apps %} must have the `administration` permission for repositories and the `organization_self_hosted_runners` permission for organizations. Authenticated users must have admin access to repositories or organizations, or the `manage_runners:enterprise` scope for enterprises to use these endpoints.
21-
2220
<!-- Content after this section is automatically generated -->

content/rest/actions/variables.md

Lines changed: 1 addition & 3 deletions
Original file line numberDiff line numberDiff line change
@@ -16,8 +16,6 @@ autogenerated: rest
1616

1717
## About variables in {% data variables.product.prodname_actions %}
1818

19-
You can use the REST API to create, update, delete, and retrieve information about variables that can be used in workflows in {% data variables.product.prodname_actions %}. {% data reusables.actions.about-variables %}
20-
21-
{% data reusables.actions.actions-authentication %} {% data variables.product.prodname_github_apps %} must have the `actions_variables/environments/organization_actions_variables` permission to use these endpoints. Authenticated users must have collaborator access to a repository to create, update, or read variables.
19+
You can use the REST API to create, update, delete, and retrieve information about variables that can be used in workflows in {% data variables.product.prodname_actions %}. {% data reusables.actions.about-variables %} For more information, see "[AUTOTITLE](/actions/learn-github-actions/variables)" in the {% data variables.product.prodname_actions %} documentation.
2220

2321
<!-- Content after this section is automatically generated -->

content/rest/actions/workflow-jobs.md

Lines changed: 1 addition & 3 deletions
Original file line numberDiff line numberDiff line change
@@ -15,8 +15,6 @@ autogenerated: rest
1515

1616
## About workflow jobs in {% data variables.product.prodname_actions %}
1717

18-
You can use the REST API to view logs and workflow jobs in {% data variables.product.prodname_actions %}. {% data reusables.actions.about-workflow-jobs %} For more information, see "[AUTOTITLE](/actions/using-workflows/workflow-syntax-for-github-actions)".
19-
20-
{% data reusables.actions.actions-authentication %} {% data reusables.actions.actions-app-actions-permissions-api %}
18+
You can use the REST API to view logs and workflow jobs in {% data variables.product.prodname_actions %}. {% data reusables.actions.about-workflow-jobs %} For more information, see "[AUTOTITLE](/actions/using-workflows/workflow-syntax-for-github-actions)."
2119

2220
<!-- Content after this section is automatically generated -->

content/rest/actions/workflow-runs.md

Lines changed: 0 additions & 2 deletions
Original file line numberDiff line numberDiff line change
@@ -17,6 +17,4 @@ autogenerated: rest
1717

1818
You can use the REST API to view, re-run, cancel, and view logs for workflow runs in {% data variables.product.prodname_actions %}. {% data reusables.actions.about-workflow-runs %} For more information, see "[AUTOTITLE](/actions/managing-workflow-runs)."
1919

20-
{% data reusables.actions.actions-authentication %} {% data reusables.actions.actions-app-actions-permissions-api %}
21-
2220
<!-- Content after this section is automatically generated -->

content/rest/actions/workflows.md

Lines changed: 1 addition & 3 deletions
Original file line numberDiff line numberDiff line change
@@ -15,8 +15,6 @@ autogenerated: rest
1515

1616
## About workflows in {% data variables.product.prodname_actions %}
1717

18-
You can use the REST API to view workflows for a repository in {% data variables.product.prodname_actions %}. {% data reusables.actions.about-workflows %} For more information, see "[AUTOTITLE](/actions)."
19-
20-
{% data reusables.actions.actions-authentication %} {% data reusables.actions.actions-app-actions-permissions-api %}
18+
You can use the REST API to view workflows for a repository in {% data variables.product.prodname_actions %}. {% data reusables.actions.about-workflows %} For more information, see "[AUTOTITLE](/actions/using-workflows/about-workflows)" in the {% data variables.product.prodname_actions %} documentation.
2119

2220
<!-- Content after this section is automatically generated -->
Lines changed: 46 additions & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -0,0 +1,46 @@
1+
date: '2023-08-10'
2+
sections:
3+
security_fixes:
4+
- |
5+
**LOW:** An attacker could circumvent branch protection by changing a PR base branch to an invalid ref name. This vulnerability was reported via the [GitHub Bug Bounty program](https://bounty.github.com/).
6+
- |
7+
Packages have been updated to the latest security versions.
8+
bugs:
9+
- |
10+
On an instance in a high availability configuration, on some platforms, replication could perform poorly over links with very high latency.
11+
- |
12+
On an instance with custom firewall rules defined, a configuration run with `ghe-config-apply` could take longer than expected.
13+
- |
14+
Events related to repository notifications did not appear in the audit log.
15+
- |
16+
A collaborator with the "Set the social preview" permission inherited from the "Read" role couldnt upload the social preview image of a repository.
17+
- |
18+
On an instance in a high availability configuration, existing nodes with out-of-sync repositories prevented new nodes from replicating those repositories.
19+
- |
20+
GitHub Enterprise Server was queuing zip jobs unnecessarily.
21+
changes:
22+
- |
23+
The secondary abuse rate limits of the GraphQL API are now configurable in the Management Console.
24+
- |
25+
The description of the `ghe-cluster-balance` command line utility clarifies that it can be used to balance jobs other than `github-unicorn`.
26+
- |
27+
Administrators can display all repositories in a network with `spokesctl` by using the `repositories` subcommand.
28+
known_issues:
29+
- |
30+
Custom firewall rules are removed during the upgrade process.
31+
- |
32+
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.
33+
- |
34+
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.
35+
- |
36+
In a repository's settings, enabling the option to allow users with read access to create discussions does not enable this functionality.
37+
- |
38+
Custom patterns for secret scanning have `.*` as an end delimiter, specifically in the "After secret" field. This delimiter causes inconsistencies in scans for secrets across repositories, and you may notice gaps in a repository's history where no scans completed. Incremental scans may also be impacted. To prevent issues with scans, modify the end of the pattern to remove the `.*` delimiter.
39+
- |
40+
{% data reusables.release-notes.repository-inconsistencies-errors %}
41+
- |
42+
On an instance in a high-availability configuration, passive replica nodes accept Git client requests and forward the requests to the primary node.
43+
- |
44+
If an instance is configured to forward logs to a target server with TLS enabled, certificate authority (CA) bundles that a site administrator uploads using `ghe-ssl-ca-certificate-install` are not respected, and connections to the server fail.
45+
- |
46+
When running `ghe-config-apply`, the process may stall with the message `Deployment is running pending automatic promotion`.

0 commit comments

Comments
 (0)