Data and AI releases

811 this month · 176 companies

Changes to query results in the GitHub Actions API and UI

UpdateNot yet verified

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.

SQLObservabilityDeveloper toolsPerformance

Read on github.blog

Also shipped Sep 25, 2026GitHub in September 2026 →

CLI v0.8.1 | CLI

CLI v0.8.1 Continue local work in the cloud: Use cr code handoff --summary to start a new cloud Coding Agent task with your session summary, an optional plan, and an automatically discovered transcript when available. Clearer handoff results: See transfer progress, the branch and commit, transferred filenames, and a direct link to the cloud task.

Preview
Source ↗

What's new in Sigma

AI Assistant in build mode: pivot table styling In workbooks, Sigma Assistant in build mode now creates pivot tables with automatic heatmap and matrix styling based on the type of measures.

GA
Source ↗

Sleeping Sessions Wake on Preview or SSH Traffic

Opening a preview URL or SSHing into a session whose machine has gone to sleep now wakes the machine and completes the request instead of showing "not running". Browser previews come back automatically after a session wakes, and the "Wake Devin up" button on a sleeping preview now shows live progress.

Preview
Source ↗

More from GitHub ActionsEvery GitHub Actions release →

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.

Preview
Source ↗

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.

Deprecation
Source ↗

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...

Deprecation
Source ↗

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.

Update
Source ↗

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.

Update
Source ↗

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.

GA
Source ↗

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.

GA
Source ↗