Unified GitHub Actions Retention Policy to Prune Runs, Checks, and Statuses

GitHub has announced that effective October 1, 2026, checks, workflow runs, and commit statuses will fall under the unified Actions retention policy that previously governed only build artifacts and execution logs. Historically, GitHub preserved workflow execution metadata, statuses, and check runs for over 400 days, independent of user-configured log eviction cycles. Under the new model, all five components—checks, runs, statuses, logs, and artifacts—will be automatically pruned once they cross the repository, organization, or enterprise retention limit, which defaults to 90 days. This change directly impacts DevOps teams, platform engineers, and release managers who rely on long-tail historical pipeline data for traceability, compliance verification, and post-incident reviews. Many engineering organizations operate under compliance frameworks that mandate retaining deployment verification and audit records for extended periods. If teams depend on GitHub Actions' historical UI or status API as their single source of truth for build attestations and commit statuses, the automated pruning at the 90-day default mark will introduce serious regulatory gaps. The shift reflects a broader, industry-wide modernization in CI/CD platform architectures toward deterministic lifecycle management and strict state hygiene. Over the past few years, as GitHub Actions scaled past tens of millions of daily job executions, retaining semi-infinite execution metadata created massive indexing overhead across backend services. By consolidating metadata retention rules, GitHub aligns itself with modern cloud-native operational principles: keeping the operational plane performant while pushing long-term historical records into dedicated storage and log aggregators. Practitioners must audit their existing GitHub Actions retention configurations before the October 1 cutoff. For private repositories requiring extended retention, platform administrators should elevate organizational retention caps up to allowable enterprise boundaries. However, since public repositories are strictly capped at 90 days and the eviction process is irreversible once applied, teams with regulatory auditing obligations must decouple long-term compliance from GitHub's native run history. Best practices dictate streaming workflow audit telemetry, build provenance metadata, and deployment logs to third-party data warehouses or long-term observability platforms via webhooks and external log forwarders.