Releasesby Glyphpull_request_target blocked by default December 2
Starting December 2, 2026, GitHub Actions will block pull_request_target events by default in all public repositories, unless an applicable Actions event policy explicitly allows them. Enforcement was previously scheduled for November 2, 2026. GitHub introduced this default rule through workflow execution protections.
Also shipped Nov 2, 2026GitHub in November 2026 →
Managed warehouse for MLflow (Beta)
Managed warehouse for MLflow is available in Beta, enabling users to view Unity Catalog traces in the MLflow UI without manually choosing a SQL warehouse.
Check out GitHub code without long-lived credentials on self-hosted agents
Self-hosted agents can now use temporary, read-only GitHub App tokens for repository checkout. This eliminates the need to distribute and rotate long-lived SSH keys or personal access tokens across your agent fleet.
Serving tuned Gemini 3.x models on global endpoints
Serving tuned Gemini 3.x models on global endpoints is available in General Availability (GA) . You can copy fine-tuned Gemini 3.x models to the global region using the Model Registry models:copy API, deploy them to global serving endpoints, and send inference requests directly to aiplatform.googleapis.com .
[Launched] Generally Available: Change from virtual network integration to a private endpoint capable network configuration in Azure Database for PostgreSQL flexible server
You now have greater flexibility in network design for Azure Database for PostgreSQL Flexible Server workloads. Now you can change existing VNet-integrated servers from delegated-subnet networking to a private endpoint-capable configuration, enabling secu
[Launched] Generally Available: Restart databases in Azure SQL DB via the Azure portal
You can now restart or fail over databases directly from the Azure portal, including single databases, Hyperscale databases, and databases in elastic pools, without writing scripts against the Rest API or contacting support. Learn more.
Lakehouse caching for cross-cloud data access is generally available (GA)
Lakehouse caching for cross-cloud data access is generally available (GA). Cross-cloud caching is disabled by default. You can opt in to caching on a Lakehouse federated catalog or a BigQuery cross-cloud connection to cache remote files in your Google Cloud region. This helps reduce cross-cloud egress costs and accelerate subsequent queries.
More from GitHub ActionsEvery GitHub Actions release →
Meta API endpoints updated for Actions blob storage
GitHub has added new blob storage endpoints for GitHub Actions. Organizations using network allowlists must update their settings to include these new hosts to ensure continued access to job summaries and logs.
Xcode 27 runner image generally available
You can now use the generally available Xcode 27 runner image to build and test your Apple applications in GitHub Actions. Previously in public preview, this GitHub-hosted image runs on macOS 27 and includes the Xcode 27 toolchain and Apple SDKs.
GitHub Actions workflow lockfiles in public preview
GitHub Actions workflow dependency lockfiles are now in public preview for GitHub Enterprise Cloud, GitHub Enterprise Cloud with data residency, Team, and Free plans. Tags and branches can move after you review a workflow, so a later run might execute different code.
Stateless GitHub App installation tokens rolled out
The staged rollout of the stateless GitHub App installation token format, which began on April 27, 2026, is complete. By default, all newly minted GitHub App installation tokens will be in the stateless ghs_APPID_JWT format, which makes token issuance and validation faster and improves the reliability of the GitHub API.
GitHub Actions: macOS 14 runner image retirement
The macOS 14 runner image will be retired on November 2, 2026. To raise awareness of the upcoming removal, jobs using macOS 14 will temporarily fail during the following scheduled brownout periods: October 5, 14:00 UTC to October 6, 00:00 UTC October 12, 14:00 UTC to October 13, 00:00 UTC October 16, 14:00 UTC to October 17, 00:00 UTC October 19, 14:00 UTC...
Actions retention now covers checks, runs, and statuses
As previously announced , checks, workflow runs, and statuses are now governed by the same GitHub Actions retention setting that controls how long artifacts and logs are kept. These records are automatically cleaned up when they exceed the retention period configured for your enterprise, organization, or repository.
Changes to query results in the GitHub Actions API and UI
Queries for workflow runs in the GitHub Actions API and UI now return a less precise but more accurate count of records when you search by workflow, event, status, branch, or actor. We will continue to return paginated results of up to 1,000 items.
Require proof of presence for high-impact actions
You can now require an interactive re-authentication or a multi-factor challenge before members take high-impact actions on GitHub Enterprise Cloud accounts. Proof of presence is an expansion of GitHub’s sudo mode for enterprises, enforcing a higher security bar when it’s needed.