Control GitHub Actions Cache Access with cache-mode
GitHub Actions now supports `cache-mode`, allowing granular control over cache access at the workflow or job level. This feature enables applying least-privilege access, preventing unnecessary restores or saves, and protecting against cache poisoning. It introduces `read`, `write`, `write-only`, and `none` modes, with job-level settings overriding workflow-level configurations. This capability is generally available on all GitHub plans.
Features (1) ›
- Granular Cache Access Control with cache-mode
The new `cache-mode` feature for GitHub Actions allows users to specify `read`, `write`, `write-only`, or `none` cache access at the workflow or job level. This enables least-privilege access, mitigates cache poisoning risks, and helps optimize build times by preventing unnecessary cache operations. The selected mode is enforced by the cache service and propagates through reusable workflows.
https://github.blog/changelog/2026-09-10-control-github-actions-cache-access-with-cache-mode
Related releases
- GitHub AI Scan for PRs: API Management Now in Public Preview GitHub Changelog ·
- GitHub Copilot Deprecates MAI-Code-1-Flash Model GitHub Changelog ·
- npm Extends 72-Hour Recovery-Code Security Holds to All Accounts GitHub Changelog ·
- GitHub's Xcode 27 Runner Image Now Uses macOS 27 GitHub Changelog ·
- CodeQL 2.27.0 Adds Linux ARM64 Support, New Rust Security Query, and Expanded Framework Coverage GitHub Changelog ·
- GitHub Copilot now offers enterprise-managed permissions for agent operations GitHub Changelog ·