Releasesby GlyphRequire 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.
Also shipped Sep 24, 2026GitHub in September 2026 →
DCM Projects capability updates
This release updates the availability of several DCM Projects capabilities. The following capabilities are now generally available: The following capabilities are now available in preview:
Alpha Changelog - 9/23/26
Hi everyone, here are the latest round of changes on alpha.midjourney.com . Many of these came directly from your feedback in #alpha-ideas-and-bugs . Please keep it coming! STYLE PREVIEWS We're experimenting with fast models in the interface.
New project activity feed
As part of our ongoing work to simplify the Netlify dashboard, we’ve added an activity feed to the project overview page. It’s available on all plans and adapts to how your project is set up.
Retool CLI
Live on cloud • Team • Business • Enterprise Public beta 4.62 Edge • Team • Business • Enterprise Public beta 4.34.4 Stable • Team • Business • Enterprise Public beta The Retool CLI is now available in public beta.
Buildkite Cache is now in public preview
Buildkite Cache is now available in public preview. It saves and restores files and directories across pipeline jobs and builds. Use it for package manager download caches, compiled dependencies, and other regenerable data to avoid repeating work.
Service principal Genie usage is billed at standard pricing
Genie usage by service principals is now billed at standard Genie pay-as-you-go pricing. Service principals are excluded from the free monthly usage allowance that applies to individual users. See Manage budgets and cost controls for Genie and Monitor and understand your Genie cost .
More from GitHub ActionsEvery GitHub Actions release →
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.
Node 20 is no longer available in GitHub Actions
This is the final notification that Node 20 is no longer available on GitHub Actions runners. Runners now use Node 24 for JavaScript actions. The temporary ACTIONS_ALLOW_USE_UNSECURE_NODE_VERSION opt-out is no longer available. If you maintain a JavaScript action, update its runs.using value to node24 and publish a new release as soon as possible.
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.
Ubuntu 26 generally available and latest migration
The Ubuntu 26.04 runner image for GitHub Actions is now out of public preview and fully supported for production workflows on both x64 and arm64. As part of this release, the ubuntu-latest label will migrate to Ubuntu 26.04, giving you the latest supported Ubuntu release by default.
Workflow execution protections in GitHub Actions generally available
Workflow execution protections for GitHub Actions, previously in public preview, are now generally available for GitHub Enterprise, organizations, and repositories. Execution protections let you define an allowlist that controls who can trigger an Actions workflow and what events can start it.
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.
Control GitHub Actions cache access with cache-mode
You can now use cache-mode to apply least-privilege access to the GitHub Actions cache at the workflow or job level. By granting each workflow or job only the cache access it needs, you can prevent unnecessary restores or saves and help protect trusted workflows from cache poisoning. This capability is now generally available on all plans.