Data and AI releases

548 this month · 176 companies

GitHub Actions holds potentially malicious workflows for approval

UpdateVerified

Recent supply chain attacks use compromised GitHub credentials to push malicious GitHub Actions workflows that steal CI/CD credentials and carry out additional attacks. To help protect public repositories from these attacks, GitHub Actions now holds certain workflow runs for approval before they start.

ObservabilityDeveloper tools

Read on github.blog

Also shipped Jul 28, 2026GitHub in July 2026 →

Snowflake Native Apps support for Virtual Private Snowflake on AWS for apps with containers (General availability)

Snowflake Native App with Snowpark Container Services now support Virtual Private Snowflake (VPS) on Amazon Web Services. Apps with containers can be distributed to Snowflake customers in VPS deployments. Apps running in VPS can use the functionality of Snowpark Container Services, including compute pools, services, jobs, and external access integrations.

GA
Source ↗

More from GitHub ActionsEvery GitHub Actions release →

Xcode 27 runner image now in public preview

You can now build and test your Apple applications against Xcode 27 on GitHub-hosted macOS runners. This is now available in public preview. With early access to the latest Xcode toolchain and Apple SDKs, you can validate your apps against the newest tools, catch compatibility issues sooner, and keep your CI/CD pipelines current.

Preview
Source ↗

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 ↗

Read-only Actions cache for untrusted triggers

GitHub Actions now issues read-only cache tokens to the default branch for workflow events that can be triggered without write permissions to the repository. This applies least privilege to the cache and prevents common privilege-escalation paths through cache poisoning.

Update
Source ↗