Expanded Retention Coverage

GitHub has updated its Actions retention policy to include checks, workflow runs, and statuses under the same governance framework that previously applied only to artifacts and logs. This change, announced on October 1, 2026, ensures consistent data lifecycle management across all GitHub Actions records. Further details are available from GitHub Changelog in the original source material.

The update follows an earlier announcement on August 27, 2026, which first indicated the expansion of retention controls to these record types. The new policy ensures that all records created by GitHub Actions and third-party integrations are subject to the same cleanup processes. Further details are available from Back to changelog in the original source material.

Policy Implementation Details

The retention setting, now labeled "Check, workflow run, status, artifact and log retention" in the user interface, operates at three levels: enterprise, organization, and repository. This hierarchical approach allows administrators to enforce consistent policies while accommodating specific repository requirements.

Records exceeding the configured retention period are automatically cleaned up, ensuring that historical data does not accumulate indefinitely. This process applies uniformly to both native GitHub Actions records and those generated by third-party applications integrated with the platform.

Repository-Level Constraints

While repositories can configure their own retention periods, these settings remain subject to organizational and enterprise-level caps. For public repositories, GitHub maintains a maximum retention limit of 90 days, regardless of any higher-level configurations.

It is important to note that modifying the retention setting will not restore data that has already been removed through the cleanup process. Users must ensure they have archived any critical information before the retention period expires.

Technical Context and Related Updates

The retention expansion coincides with other recent GitHub Actions updates, including the release of Actions Runner Controller version 0.15.0 and changes to query results in the GitHub Actions API and UI. These developments reflect GitHub's ongoing efforts to refine data management and user experience.

Additionally, GitHub has moved the self-hosted runner version enforcement date and discontinued support for Node 20 in Actions workflows. These changes highlight the platform's continuous evolution and commitment to maintaining secure, up-to-date infrastructure.

User Guidance and Best Practices

Users are encouraged to review and update their artifact and log retention periods to align with their operational needs. The expanded retention policy applies to GitHub Actions on github.com, and administrators should consider the implications of data lifecycle management when configuring these settings.

GitHub recommends that organizations establish clear retention policies that balance data accessibility with storage efficiency. For teams requiring longer-term record keeping, proactive archiving strategies should be implemented before the configured retention period elapses.

Sources

• GitHub ChangelogActions retention now covers checks, runs, and statuses