GitHub Enhances Actions Cache Storage Beyond 10 GB Per Repository
Rongchai Wang Nov 21, 2025 08:17
GitHub now allows Actions cache storage to exceed 10 GB per repository, offering flexibility with a pay-as-you-go model for increased storage needs.
GitHub has announced a significant update to its Actions service, allowing repositories to exceed the previous 10 GB cache size limit. This enhancement provides developers with the ability to store more build dependencies between workflow runs, according to the GitHub blog.
Expanded Cache Storage
The expanded cache storage is facilitated through a pay-as-you-go model, enabling repositories to surpass the former 10 GB cap without incurring additional costs for the initial 10 GB. Enterprise, Organization, and Repository administrators can adjust these limits, and any additional storage usage will be billed accordingly. This new cost structure aligns with the pricing models for Git LFS and Codespaces storage.
Cache Management and Billing Policies
In conjunction with the increased storage capabilities, GitHub introduces two new cache management policies: cache size eviction limit and cache retention limit. The retention limit determines how long cache entries are maintained post-access, while the eviction limit sets the maximum cache size per repository. By default, repositories continue with a 10 GB cache size limit and a seven-day retention period at no extra charge.
Administrators have the flexibility to manage these policies through the Actions settings for Repositories and Organizations or via Policies for Enterprises. Billing owners can also establish budgets based on the new storage SKU, ensuring that cache access becomes read-only once budget limits are reached until the next billing cycle.
Implications for Developers
This development is poised to benefit developers who require substantial storage for build dependencies, potentially enhancing workflow efficiency. The ability to manage cache and billing policies allows for tailored usage, ensuring that storage needs are met without unnecessary expenditure.
For further details on managing cache storage and policies, developers can refer to the GitHub Actions documentation.
Image source: Shutterstock.jpg)