Merge branch 'main' into ghes-verify-and-approve-domains
This commit is contained in:
Sarita Iyer
@@ -31701,6 +31701,11 @@ type Repository implements Node & ProjectOwner & RepositoryInfo & Starrable & Su
|
||||
"""
|
||||
viewerSubscription: SubscriptionState
|
||||
|
||||
"""
|
||||
Indicates the repository's visibility level.
|
||||
"""
|
||||
visibility: RepositoryVisibility!
|
||||
|
||||
"""
|
||||
A list of vulnerability alerts that are on this repository.
|
||||
"""
|
||||
@@ -32178,6 +32183,11 @@ interface RepositoryInfo {
|
||||
Whether this repository has a custom image to use with Open Graph as opposed to being represented by the owner's avatar.
|
||||
"""
|
||||
usesCustomOpenGraphImage: Boolean!
|
||||
|
||||
"""
|
||||
Indicates the repository's visibility level.
|
||||
"""
|
||||
visibility: RepositoryVisibility!
|
||||
}
|
||||
|
||||
"""
|
||||
|
||||
@@ -34397,6 +34397,11 @@ type Repository implements Node & PackageOwner & ProjectOwner & RepositoryInfo &
|
||||
"""
|
||||
viewerSubscription: SubscriptionState
|
||||
|
||||
"""
|
||||
Indicates the repository's visibility level.
|
||||
"""
|
||||
visibility: RepositoryVisibility!
|
||||
|
||||
"""
|
||||
A list of vulnerability alerts that are on this repository.
|
||||
"""
|
||||
@@ -34869,6 +34874,11 @@ interface RepositoryInfo {
|
||||
Whether this repository has a custom image to use with Open Graph as opposed to being represented by the owner's avatar.
|
||||
"""
|
||||
usesCustomOpenGraphImage: Boolean!
|
||||
|
||||
"""
|
||||
Indicates the repository's visibility level.
|
||||
"""
|
||||
visibility: RepositoryVisibility!
|
||||
}
|
||||
|
||||
"""
|
||||
|
||||
14
data/release-notes/enterprise-server/2-22/20.yml
Normal file
14
data/release-notes/enterprise-server/2-22/20.yml
Normal file
@@ -0,0 +1,14 @@
|
||||
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.
|
||||
20
data/release-notes/enterprise-server/3-0/14.yml
Normal file
20
data/release-notes/enterprise-server/3-0/14.yml
Normal file
@@ -0,0 +1,20 @@
|
||||
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.
|
||||
21
data/release-notes/enterprise-server/3-1/6.yml
Normal file
21
data/release-notes/enterprise-server/3-1/6.yml
Normal file
@@ -0,0 +1,21 @@
|
||||
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.
|
||||
@@ -1,10 +1,12 @@
|
||||
| Action | Description
|
||||
|------------------|-------------------{% ifversion fpt or ghes > 3.0 or ghae %}
|
||||
| `cancel_workflow_run` | Triggered when a workflow run has been cancelled. For more information, see "[Canceling a workflow](/actions/managing-workflow-runs/canceling-a-workflow)."{% endif %}{% ifversion fpt or ghes > 3.0 or ghae %}
|
||||
| `completed_workflow_run` | Triggered when a workflow status changes to `completed`. Can only be viewed using the REST API; not visible in the UI or the JSON/CSV export. For more information, see "[Viewing workflow run history](/actions/managing-workflow-runs/viewing-workflow-run-history)."{% endif %}{% ifversion fpt or ghes > 3.0 or ghae %}
|
||||
| `created_workflow_run` | Triggered when a workflow run is created. Can only be viewed using the REST API; not visible in the UI or the JSON/CSV export. For more information, see "[Create an example workflow](/actions/learn-github-actions/introduction-to-github-actions#create-an-example-workflow)."{% endif %}
|
||||
|------------------|-------------------{% ifversion fpt or ghes > 3.1 or ghae-issue-1157 %}
|
||||
| `cancel_workflow_run` | Triggered when a workflow run has been cancelled. For more information, see "[Canceling a workflow](/actions/managing-workflow-runs/canceling-a-workflow)."{% endif %}{% ifversion fpt %}
|
||||
| `completed_workflow_run` | Triggered when a workflow status changes to `completed`. Can only be viewed using the REST API; not visible in the UI or the JSON/CSV export. For more information, see "[Viewing workflow run history](/actions/managing-workflow-runs/viewing-workflow-run-history)."{% endif %}{% ifversion fpt %}
|
||||
| `created_workflow_run` | Triggered when a workflow run is created. Can only be viewed using the REST API; not visible in the UI or the JSON/CSV export. For more information, see "[Create an example workflow](/actions/learn-github-actions/introduction-to-github-actions#create-an-example-workflow)."{% endif %}{% ifversion fpt or ghes > 3.1 or ghae-issue-1157 %}
|
||||
| `delete_workflow_run` | Triggered when a workflow run is deleted. For more information, see "[Deleting a workflow run](/actions/managing-workflow-runs/deleting-a-workflow-run)."
|
||||
| `disable_workflow` | Triggered when a workflow is disabled.
|
||||
| `enable_workflow` | Triggered when a workflow is enabled, after previously being disabled by `disable_workflow`.{% ifversion fpt or ghes > 3.0 or ghae %}
|
||||
| `rerun_workflow_run` | Triggered when a workflow run is re-run. For more information, see "[Re-running a workflow](/actions/managing-workflow-runs/re-running-a-workflow)."{% endif %}{% ifversion fpt or ghes > 3.0 or ghae %}
|
||||
| `prepared_workflow_job` | Triggered when a workflow job is started. Includes the list of secrets that were provided to the job. Can only be viewed using the REST API; not visible in the UI or the JSON/CSV export. For more information, see "[Events that trigger workflows](/actions/reference/events-that-trigger-workflows)."{% endif %}
|
||||
| `enable_workflow` | Triggered when a workflow is enabled, after previously being disabled by `disable_workflow`.
|
||||
| `rerun_workflow_run` | Triggered when a workflow run is re-run. For more information, see "[Re-running a workflow](/actions/managing-workflow-runs/re-running-a-workflow)."{% endif %}{% ifversion fpt %}
|
||||
| `prepared_workflow_job` | Triggered when a workflow job is started. Includes the list of secrets that were provided to the job. Can only be viewed using the REST API; not visible in the UI or the JSON/CSV export. For more information, see "[Events that trigger workflows](/actions/reference/events-that-trigger-workflows)."{% endif %}{% ifversion fpt or ghes > 3.1 or ghae-issue-1157 %}
|
||||
| `approve_workflow_job` | Triggered when a workflow job has been approved. For more information, see "[Reviewing deployments](/actions/managing-workflow-runs/reviewing-deployments)."
|
||||
| `reject_workflow_job` | Triggered when a workflow job has been rejected. For more information, see "[Reviewing deployments](/actions/managing-workflow-runs/reviewing-deployments)."{% endif %}
|
||||
|
||||
@@ -15,7 +15,7 @@ Windows Server 2022<sup>[beta]</sup>
|
||||
<code>windows-2022</code>
|
||||
</td>
|
||||
<td>
|
||||
The <code>windows-latest</code> label currently uses the windows server 2019 runner image.
|
||||
The <code>windows-latest</code> label currently uses the Windows Server 2019 runner image.
|
||||
</td>
|
||||
</tr>
|
||||
<tr>
|
||||
|
||||
@@ -0,0 +1,8 @@
|
||||
### Usage limits
|
||||
|
||||
There are usage limits for the team synchonization feature. Exceeding these limits will lead to a degredation in performance and may cause synchronization failures.
|
||||
|
||||
- Maximum number of members in a GitHub team: 5,000
|
||||
- Maximum number of members in a GitHub organization: 10,000
|
||||
- Maximum number of teams in a GitHub organization: 1,500
|
||||
|
||||
Reference in New Issue
Block a user