Skip to content

Commit 8d0264e

Browse files
authored
Public actions via GitHub Connect are available again from 3.20.6 (#62878)
1 parent 35f99b1 commit 8d0264e

8 files changed

Lines changed: 16 additions & 14 deletions

File tree

content/admin/configuring-settings/configuring-github-connect/about-github-connect.md

Lines changed: 2 additions & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -31,6 +31,8 @@ To enable {% data variables.product.prodname_github_connect %}, you configure a
3131

3232
After you configure the connection between {% data variables.location.product_location %} and {% data variables.product.prodname_ghe_cloud %}, you can enable individual features of {% data variables.product.prodname_github_connect %}.
3333

34+
If you're connecting to an enterprise on **{% data variables.enterprise.data_residency_site %}**:
35+
3436
{% data reusables.github-connect.what-is-available-ghecom %}
3537

3638
| Feature | Description | More information |

content/admin/configuring-settings/configuring-github-connect/enabling-github-connect-for-ghecom.md

Lines changed: 1 addition & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -23,7 +23,7 @@ You can access additional features and workflows on {% data variables.location.p
2323
## Prerequisites
2424

2525
* **Administrative access:** You need administrative access to both an enterprise account on {% data variables.enterprise.data_residency_site %} and a {% data variables.product.prodname_ghe_server %} instance.
26-
* **Version requirement:** Your {% data variables.product.prodname_ghe_server %} instance must run {% data variables.product.prodname_ghe_server %} 3.12 or later.
26+
* **Version requirement:** To enable {% data variables.product.prodname_github_connect %} for {% data variables.enterprise.data_residency_site %}, your {% data variables.product.prodname_ghe_server %} instance must be on version 3.12 or later. Certain individual features of {% data variables.product.prodname_github_connect %} require later versions. See [AUTOTITLE](/admin/configuring-settings/configuring-github-connect/about-github-connect#github-connect-features).
2727
* **Proxy configuration:** If using a proxy server, allow connectivity to the following {% data variables.enterprise.data_residency_site %} hostnames (replace SUBDOMAIN with your enterprise's subdomain).
2828

2929
* `{% data variables.enterprise.data_residency_domain %}`

content/admin/data-residency/feature-overview-for-github-enterprise-cloud-with-data-residency.md

Lines changed: 1 addition & 3 deletions
Original file line numberDiff line numberDiff line change
@@ -95,9 +95,7 @@ To allow people to use namespaces that match actions you have used from {% data
9595

9696
You can use {% data variables.product.prodname_github_connect %} to connect to {% data variables.enterprise.data_residency_site %} from {% data variables.product.prodname_ghe_server %}.
9797

98-
* {% data variables.product.prodname_server_statistics %} is not available.
99-
* {% data variables.product.prodname_dotcom_the_website %} actions are not available.
100-
* Automatic user license sync requires {% data variables.product.prodname_ghe_server %} version 3.15 or later.
98+
{% data reusables.github-connect.what-is-available-ghecom %}
10199

102100
To enable {% data variables.product.prodname_github_connect %}, you must configure your {% data variables.product.prodname_ghe_server %} instance to connect to your {% data variables.enterprise.data_residency_site %} subdomain. See [AUTOTITLE](/enterprise-server@latest/admin/configuring-settings/configuring-github-connect/enabling-github-connect-for-ghecom).
103101

content/admin/managing-github-actions-for-your-enterprise/managing-access-to-actions-from-githubcom/enabling-automatic-access-to-githubcom-actions-using-github-connect.md

Lines changed: 3 additions & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -20,6 +20,8 @@ category:
2020

2121
By default, {% data variables.product.prodname_actions %} workflows on {% data variables.product.prodname_ghe_server %} cannot use actions directly from {% data variables.product.prodname_dotcom_the_website %} or [{% data variables.product.prodname_marketplace %}](https://github.com/marketplace?type=actions). To make public actions from {% data variables.product.prodname_dotcom_the_website %} available on your enterprise instance, you can use {% data variables.product.prodname_github_connect %} to integrate {% data variables.product.prodname_ghe_server %} with {% data variables.product.prodname_ghe_cloud %}.
2222

23+
If your cloud deployment is on {% data variables.enterprise.data_residency_site %}, {% data variables.product.prodname_github_connect %} can still resolve public actions from {% data variables.product.prodname_dotcom_the_website %}. This requires {% data variables.product.prodname_ghe_server %} version 3.20.6 or later, or any feature release from 3.21.0.
24+
2325
{% data reusables.actions.self-hosted-runner-networking-to-dotcom %}
2426

2527
Alternatively, if you want stricter control over which actions are allowed in your enterprise, you can manually download and sync public actions onto your enterprise instance using the `actions-sync` tool. For more information, see [AUTOTITLE](/admin/managing-github-actions-for-your-enterprise/managing-access-to-actions-from-githubcom/manually-syncing-actions-from-githubcom).
@@ -34,7 +36,7 @@ If a user has already created an organization and repository in your enterprise
3436

3537
Before enabling access to public actions from {% data variables.product.prodname_dotcom_the_website %} for your enterprise, you must:
3638
* Configure {% data variables.location.product_location %} to use {% data variables.product.prodname_actions %}. For more information, see [AUTOTITLE](/admin/managing-github-actions-for-your-enterprise/getting-started-with-github-actions-for-your-enterprise/getting-started-with-github-actions-for-github-enterprise-server).
37-
* Enable {% data variables.product.prodname_github_connect %}. For more information, see [AUTOTITLE](/admin/configuring-settings/configuring-github-connect/enabling-github-connect-for-githubcom).
39+
* Enable {% data variables.product.prodname_github_connect %}. For more information, see [AUTOTITLE](/admin/configuring-settings/configuring-github-connect/enabling-github-connect-for-githubcom) or [AUTOTITLE](/admin/configuring-settings/configuring-github-connect/enabling-github-connect-for-ghecom).
3840

3941
{% data reusables.enterprise-accounts.access-enterprise %}
4042
{% data reusables.enterprise-accounts.github-connect-tab %}

data/release-notes/enterprise-server/3-20/0.yml

Lines changed: 1 addition & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -32,7 +32,7 @@ sections:
3232
notes:
3333
# https://github.com/github/releases/issues/5765
3434
- |
35-
Site administrators can enable GitHub Connect to resolve open source actions from GitHub.com, even when their GHES instance is connected to a data-resident enterprise on GHE.com. This enables hybrid deployment scenarios during migration to GHE.com. This feature is in public preview and subject to change.
35+
Site administrators can enable GitHub Connect to resolve open source actions from GitHub.com, even when their GHES instance is connected to a data-resident enterprise on GHE.com. This enables hybrid deployment scenarios during migration to GHE.com. This feature is in public preview and subject to change. **Note: This feature was temporarily disabled in 3.20.1 and is generally available from 3.20.6.** [Updated: 2026-08-21]
3636
3737
- heading: Code scanning
3838
notes:

data/release-notes/enterprise-server/3-20/1.yml

Lines changed: 1 addition & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -43,7 +43,7 @@ sections:
4343
- |
4444
When applying a hotpatch or running a configuration with `ghe-config-apply`, the configuration run could fail with "ERROR: Restoring CodeQL Action release tags" if internal Git services were not yet fully available. The error message "SpokesAPI::TwirpServerError: unavailable" appeared in logs.
4545
- |
46-
On instances connected to GitHub Enterprise Cloud with data residency, the "GitHub.com actions" setting appeared in the GitHub Connect configuration despite this feature not being available for data residency deployments.
46+
On instances connected to GitHub Enterprise Cloud with data residency, the "GitHub.com actions" setting appeared in the GitHub Connect configuration despite this feature not being available for data residency deployments. **Note: This feature is available from 3.20.6.** [Updated: 2026-08-21]
4747
- |
4848
On instances with GitHub Actions enabled, errors appeared in logs related to missing Elasticsearch field mappings for workflow runs. The workflow run data included an `archived` field that was not defined in the Elasticsearch index mapping.
4949
- |

data/release-notes/enterprise-server/3-20/6.yml

Lines changed: 4 additions & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -1,10 +1,13 @@
11
date: '2026-08-05'
22
sections:
3+
features:
4+
- |
5+
Site administrators can enable GitHub Connect to resolve open source actions from GitHub.com, even when their GHES instance is connected to a data-resident enterprise on GHE.com. This feature is now generally available. See [AUTOTITLE](/admin/configuring-settings/configuring-github-connect/enabling-github-connect-for-ghecom). [Updated: 2026-08-21]
36
security_fixes:
47
- |
58
**HIGH**: A path traversal vulnerability allowed an unauthenticated attacker to delete the user storage directory on the GitHub Enterprise Server instance, including Git LFS objects, release assets, attachments, and avatars, via the unsanitized X-GitHub-Request-Id request header. Exploitation required network access to the instance and worked when private mode was enabled. GitHub has requested CVE ID [CVE-2026-17556](https://www.cve.org/cverecord?id=CVE-2026-17556) for this vulnerability, which was reported via the [GitHub Bug Bounty program](https://bounty.github.com/).
69
- |
7-
Some internal, auto-generated secrets were not redacted when users compiled a support bundle.
10+
Some internal, auto-generated secrets were not redacted when users compiled a support bundle.
811
bugs:
912
- |
1013
On a {% data variables.product.prodname_ghe_server %} cluster upgrade, if all Consul server nodes restarted concurrently, the cluster could lose its Nomad leader and fail to recover, causing the upgrade to loop and fail rather than complete.
Lines changed: 3 additions & 6 deletions
Original file line numberDiff line numberDiff line change
@@ -1,6 +1,3 @@
1-
{% ifversion ghecom-github-connect %}
2-
If you're connecting to an enterprise on **{% data variables.enterprise.data_residency_site %}**:
3-
* Server Statistics is not available.
4-
* {% data variables.product.prodname_dotcom_the_website %} actions are not available.
5-
6-
{% endif %}
1+
* {% data variables.product.prodname_server_statistics %} is not available.
2+
* Automatic user license sync requires {% data variables.product.prodname_ghe_server %} version 3.15 or later.
3+
* Actions from {% data variables.product.prodname_dotcom_the_website %} require {% data variables.product.prodname_ghe_server %} version 3.20.6 or later, or any feature release from 3.21.0.

0 commit comments

Comments
 (0)