Data and AI releases

548 this month · 176 companies

Separate GitHub Actions path for GitHub Code Quality

Generally availableVerified

A dedicated workflow path for code quality CodeQL actions workflows is now generally available. Your workflow run history and your Actions usage reports now tell GitHub Code Quality runs apart from GitHub code scanning runs.

SecurityPricingBIObservabilityDeveloper tools

Read on github.blog

Also shipped Aug 20, 2026GitHub in August 2026 →

More from GitHub ActionsEvery GitHub Actions release →

Actions retention will cover checks, workflow runs, and statuses

Starting October 1, 2026, checks, workflow runs, and statuses will be governed by the same Actions retention setting that already controls how long artifacts and logs are kept, with a default of 90 days. Until now, checks, workflow runs, and statuses were retained for 400+ days regardless of your retention configuration.

Update
Source ↗

GitHub Actions: Early September 2026 updates

GitHub Actions now includes three updates that give you clearer visibility and finer-grained control over your workflows. New REST API for runner version deprecations A new REST API returns when registration and runtime support end for a given runner version, so you can plan runner upgrades before a version is deprecated.

Update
Source ↗

CodeQL 2.26.4 improves GitHub actions security detections

CodeQL is the static analysis engine behind GitHub code scanning, which finds and remediates security issues in your code. We’ve recently released CodeQL 2.26.4 , which adds support for Go 1.27, improves alert locations for Rust data flow queries, and includes accuracy improvements across C#, Java/Kotlin, and GitHub Actions.

Update
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 ↗

Xcode 27 runner image now runs on macOS 27

You can now validate your Apple apps against macOS 27 using the Xcode 27 runner image for GitHub-hosted macOS runners, available in public preview. The image previously ran on macOS 26. How you target the image stays the same.

Preview
Source ↗