GitHub Actions Unifies Run Retention at 90 Days, Ending Legacy 400-Day Build History

GitHub has announced an operational change to how GitHub Actions manages build history: beginning October 1, 2026, checks, workflow runs, and commit statuses will follow the same retention policies that currently govern build artifacts and execution logs. Historically, run metadata, commit statuses, and check runs persisted for more than 400 days across repositories, regardless of custom retention configurations. Under the revised policy, these records will default to a 90-day retention window—with public repositories capped strictly at 90 days—and will be automatically cleaned up once they pass their designated threshold. The management interface is being updated to "Check, workflow run, status, artifact and log retention" to reflect this unified governance scope. This update carries major operational and compliance consequences for enterprise CI/CD teams. While pruning legacy records reduces platform-wide database bloat and accelerates UI query performance, it disrupts engineering organizations that rely on historical CI metadata for release audits, compliance certifications, and long-tail vulnerability investigations. Many engineering teams operate under the assumption that historical status checks and deployment records remain permanently attached to historical pull requests and release commits. Because this policy change is not retroactive, once data is evicted after October 1, 2026, it cannot be restored by retroactively adjusting retention sliders. This policy shift aligns with a broader pattern across modern continuous integration systems, where platform providers seek to balance massive scalability with storage efficiency. As developer velocity rises and automated pull request workflows multiply, CI platforms ingest billions of ephemeral test and deployment runs weekly. Retaining relational run metadata for well over a year introduces significant index fragmentation and overhead. By consolidating workflow execution lifecycles with artifact expiration, GitHub is aligning its data model with cloud-native CI best practices, effectively signaling that the CI orchestration layer should not be treated as a permanent compliance archive. Practitioners and platform engineers should audit their organization, enterprise, and repository-level Actions retention settings before the October 1 rollout. Teams managing private repositories that require extended auditability should explicitly raise retention limits to meet internal Service Level Agreements (SLAs), while factoring in that extending artifact and log lifetimes can increase billable Actions storage costs. Most importantly, enterprise teams bound by strict regulatory standards—such as SOC 2, ISO 27001, or FedRAMP—should verify that build receipts, status checks, and workflow run outputs are systematically ingested into long-term data lakes, SIEM platforms, or cold storage via GitHub APIs and webhooks rather than relying on GitHub's native UI history.